Windows 10: Daily BSODs, most IRQ_NOT_LESS_OR_EQUAL Solved

  1.    15 Jul 2017 #1

    Daily BSODs, most IRQ_NOT_LESS_OR_EQUAL


    Hello everyone, hoping someone can help shed some light into what is going on. I am considering a full reformat / reinstall, but obviously would rather avoid if at all possible.

    A bit regarding the use: Computer is mostly used for design and production purposes, I actually don't recall it crashing while playing a game, which doesn't happen very often.
    Crashes seem to occur randomly, sometimes when I am working (photoshop, or browsing, or one of many software), as well as when it is left alone. Pretty much if I leave the computer on overnight, it WILL be rebooted after a crash in the morning.

    I have done a few passes (6) of memtest, including one full set last night (4) overnight, no errors found in any.
    I have uninstalled a bunch of stuff I thought might be causing issues, but the crashes remain.

    I have disabled the sleep functionality as it seems it was a sure fire way to come back to a completely unresponsive computer.

    Computer is an i7-6800K machine, windows 10 is installed in a M.2 960 EVO drive (NVMe interface) with a secondary 2TB ssd (SATA). NO HDDs on this build. 64GB of ram. Bios, windows and vid card drivers all updated to the most recent releases, no yellow marks on any device on device manager.

    Hope that's enough info (And the attached zip) is enough to point someone with far more knowledge than I possess to the cause of my headaches. Thanks in advance!
      My ComputerSystem Spec


  2. Posts : 8,721
    windows 10 professional version 1607 build 14393.969 64 bit
       16 Jul 2017 #2

    Hi TMA1

    Welcome to the BSOD forum.

    There were 22 bsod minidump files submitted.
    All of the bsod from 07/04/2017 (14 bsod) to date when debugged displayed a misbehaving Intel driver.
    One displayed a misbehaving Nvidia driver.
    Prior to 07/04 there was 1 additional misbehaving Wacom router driver.
    Windows multiple times has failed fast startup.
    Nvidia was identified many times as a faulting application and this should be fixed with the steps below
    Malwarebytes was also identified as a faulting application.


    Open administrative command prompt and type or copy and paste:

    1) winver (in the pop up about windows > view your windows version and build > type this information into the thread)

    2) sfc /scannow

    3) dism /online /cleanup-image /restorehealth

    4) chkdsk /scan

    When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on copy > paste into the thread


    5) perform windows updates and post any failed KB# with error code into the thread.

    6) Open the ASUS web site and enter your computers serial or product number with operating system and find the latest drivers for your configuration.
    a) download: IntelTurboBoostMax
    b) download: Nvidia drivers (before doing this see the information immediately below on uninstallation)
    c) download: Wacom Hid Router

    Uninstall all Nvidia drivers/software
    The best way to do this is to uninstall everything of Nvidia using Display Driver Uninstaller and install new drivers from the Asus website or from the NVidia website.
    Computer manufacturer approved drivers are preferred.
    If you do not find a suitable Nvidia driver on the Asus website and if you use the Nvidia website be sure the "clean install" box is checked and only install the Graphics driver and the PhysX driver.
    Display Driver Uninstaller Download version 17.0.6.7: Official Display Driver Uninstaller DDU Download

    If any of the above non-Nvidia downloads present a message that the driver is already installed and prevents you from downloading an undated driver go to either device manager to identify the driver and click update or go to the control panel to uninstall and reinstall.

    7) uninstall and reinstall malwarebytes

    8) turn off Windows fast startup:
    Turn On or Off Fast Startup in Windows 10 Windows 10 Performance Maintenance Tutorials

    Make sure that there is no over clocking while troubleshooting.


    Sometimes there are problems in the bios that produce bsod.


    To ensure that there are no improper bios settings please reset the bios.


    Sometimes there can be failure to boot after resetting the bios.

    So please make sure your files are backed up.

    Please make a backup image with Macrium:


    Macrium Software | Macrium Reflect Free: Macrium Software | Your image is everything


    And please create a restore point.




    How to Clear Your Computers CMOS to Reset BIOS Settings:


    How to Clear Your Computers CMOS to Reset BIOS Settings


    3 Ways to Reset Your BIOS - wikiHow:


    3 Ways to Reset Your BIOS - wikiHow






    Code:
    Windows failed fast startup with error status 0xC00000D4.
    Code:
    BugCheck A, {ffffb28a75c200c0, 2, 1, fffff80048c5f7f8}*** WARNING: Unable to verify timestamp for IntelNit.sys*** ERROR: Module load completed but symbols could not be loaded for IntelNit.sys*** WARNING: Unable to verify checksum for win32k.sysProbably caused by : memory_corruption

    Code:
    BugCheck A, {ffff87869d7760c0, 2, 1, fffff8035ffd97f8}*** WARNING: Unable to verify timestamp for IntelNit.sys*** ERROR: Module load completed but symbols could not be loaded for IntelNit.sys*** WARNING: Unable to verify checksum for win32k.sysProbably caused by : memory_corruption
    Code:
    BugCheck A, {ffffdf0ede356800, 2, 1, fffff800510567f8}*** WARNING: Unable to verify timestamp for IntelNit.sys*** ERROR: Module load completed but symbols could not be loaded for IntelNit.sys*** WARNING: Unable to verify checksum for win32k.sysProbably caused by : memory_corruption
    Code:
    BugCheck A, {ffffa38cc99740c0, 2, 1, fffff80304dc87f8}*** WARNING: Unable to verify timestamp for IntelNit.sys*** ERROR: Module load completed but symbols could not be loaded for IntelNit.sys*** WARNING: Unable to verify checksum for win32k.sysProbably caused by : memory_corruption
    Code:
    BugCheck A, {ffffb40f9cbf9800, 2, 1, fffff801afbcb7f8}*** WARNING: Unable to verify timestamp for IntelNit.sys*** ERROR: Module load completed but symbols could not be loaded for IntelNit.sys*** WARNING: Unable to verify checksum for win32k.sysProbably caused by : memory_corruption

    iorate
    fvevol

    Code:
    BugCheck A, {ffffe70c8dcaf0c0, 2, 1, fffff80076a5a7f8}*** WARNING: Unable to verify timestamp for IntelNit.sys*** ERROR: Module load completed but symbols could not be loaded for IntelNit.sys*** WARNING: Unable to verify checksum for win32k.sysProbably caused by : memory_corruption
    Code:
    BugCheck A, {ffffd286f18770c0, 2, 1, fffff803b44637f8}*** WARNING: Unable to verify timestamp for IntelNit.sys*** ERROR: Module load completed but symbols could not be loaded for IntelNit.sys*** WARNING: Unable to verify checksum for win32k.sysProbably caused by : memory_corruption

    Code:
    BugCheck A, {ffffbc078e2180c0, 2, 1, fffff8006e7e387a}*** WARNING: Unable to verify timestamp for IntelNit.sys*** ERROR: Module load completed but symbols could not be loaded for IntelNit.sys*** WARNING: Unable to verify checksum for win32k.sysProbably caused by : memory_corruption

    Code:
    BugCheck A, {ffffbf8985b40080, 2, 1, fffff8009065887a}*** WARNING: Unable to verify timestamp for IntelNit.sys*** ERROR: Module load completed but symbols could not be loaded for IntelNit.sys*** WARNING: Unable to verify checksum for win32k.sysProbably caused by : memory_corruption

    Code:
    BugCheck A, {ffffc38f329b8780, 2, 1, fffff8038e7ce87a}*** WARNING: Unable to verify timestamp for IntelNit.sys*** ERROR: Module load completed but symbols could not be loaded for IntelNit.sys*** WARNING: Unable to verify checksum for win32k.sysProbably caused by : memory_corruption

    Code:
    BugCheck A, {ffffaa8f6a0100c0, 2, 1, fffff801c0c4d87a}*** WARNING: Unable to verify timestamp for IntelNit.sys*** ERROR: Module load completed but symbols could not be loaded for IntelNit.sys*** WARNING: Unable to verify checksum for win32k.sysProbably caused by : memory_corruption

    Code:
    BugCheck A, {ffffa98dd1d55800, 2, 1, fffff800083e787a}*** WARNING: Unable to verify timestamp for IntelNit.sys*** ERROR: Module load completed but symbols could not be loaded for IntelNit.sys*** WARNING: Unable to verify checksum for win32k.sysProbably caused by : memory_corruption

    Code:
    BugCheck A, {fffff804ac9fe2e8, 2, 0, fffff803fea488e5}*** WARNING: Unable to verify timestamp for IntelNit.sys*** ERROR: Module load completed but symbols could not be loaded for IntelNit.sysProbably caused by : IntelNit.sys ( IntelNit+660a )

    Code:
    ffffde80`f0a0e8a8  fffff803`00000030Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_2386fda73b467ac8\nvlddmkm.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for nvlddmkm.sys*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys nvlddmkm+0x380030
    Code:
    BugCheck A, {ffffa30cc4c4f800, 2, 1, fffff8014444c87a}*** WARNING: Unable to verify timestamp for IntelNit.sys*** ERROR: Module load completed but symbols could not be loaded for IntelNit.sys*** WARNING: Unable to verify checksum for win32k.sysProbably caused by : memory_corruption

    Code:
    IntelTurboBo IntelTurboBoostMax     IntelTurboBoostMax     Kernel        Manual     Running    OK         TRUE        FALSE        4,096             98,304      0          10/27/2016 10:43:44 AM C:\WINDOWS\system32\DRIVERS\IntelNit.sys         4,096

    Code:
    BugCheck 139, {3, fffff80271261da0, fffff80271261cf8, 0}*** WARNING: Unable to verify timestamp for wachidrouter.sys*** ERROR: Module load completed but symbols could not be loaded for wachidrouter.sysProbably caused by : HIDCLASS.SYS ( HIDCLASS!DequeueInterruptReadIrp+ef )

    Code:
    BugCheck 139, {3, fffff8026065aa50, fffff8026065a9a8, 0}*** WARNING: Unable to verify timestamp for wachidrouter.sys*** ERROR: Module load completed but symbols could not be loaded for wachidrouter.sys*** WARNING: Unable to verify checksum for win32k.sysProbably caused by : memory_corruption
    Code:
    WacHidRouter Wacom Hid Router       Wacom Hid Router       Kernel        Manual     Running    OK         TRUE        FALSE        16,384            73,728      0          11/30/2015 12:33:37 PM C:\WINDOWS\system32\drivers\wachidrouter.sys     4,096


    Code:
    fffff802`6065a028  fffff80f`f125b71fUnable to load image \SystemRoot\System32\DriverStore\FileRepository\nv_ref_pubwu.inf_amd64_f9309145156afb40\nvlddmkm.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for nvlddmkm.sys*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys nvlddmkm+0x9b71f
    Code:
    BugCheck 139, {3, fffff80177a5aa50, fffff80177a5a9a8, 0}*** WARNING: Unable to verify timestamp for wachidrouter.sys*** ERROR: Module load completed but symbols could not be loaded for wachidrouter.sys*** WARNING: Unable to verify checksum for win32k.sysProbably caused by : memory_corruption
    Code:
    fffff801`77a5a028  fffff804`ccfcb71fUnable to load image \SystemRoot\System32\DriverStore\FileRepository\nv_ref_pubwu.inf_amd64_f9309145156afb40\nvlddmkm.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for nvlddmkm.sys*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys nvlddmkm+0x9b71f

    Code:
    7/11/2017 1:29 AM    Application Error    Faulting application name: NVIDIA GeForce Experience.exe, version: 56.2924.1538.1, time stamp: 0x590a368e
    Faulting module name: libcef.dll, version: 3.2924.1538.0, time stamp: 0x586e28d8
    Exception code: 0x80000003
    Fault offset: 0x00e64389
    Faulting process id: 0x28b8
    Faulting application start time: 0x01d2f9e5178a85d3
    Faulting application path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\NVIDIA GeForce Experience.exe
    Faulting module path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\libcef.dll
    Report Id: f105f14b-c999-4b34-bcf6-4138837b92af
    Faulting package full name: 
    Faulting package-relative application ID:7/11/2017 1:05 AM    Application Error    Faulting application name: NVIDIA GeForce Experience.exe, version: 56.2924.1538.1, time stamp: 0x590a368e
    Faulting module name: libcef.dll, version: 3.2924.1538.0, time stamp: 0x586e28d8
    Exception code: 0x80000003
    Fault offset: 0x00e64389
    Faulting process id: 0x2c3c
    Faulting application start time: 0x01d2f9e1d53104d5
    Faulting application path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\NVIDIA GeForce Experience.exe
    Faulting module path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\libcef.dll
    Report Id: b0ba313b-b1cb-4992-a70a-518cc2897d30
    Faulting package full name: 
    Faulting package-relative application ID:
    7/11/2017 1:27 AM    Application Error    Faulting application name: NVIDIA GeForce Experience.exe, version: 56.2924.1538.1, time stamp: 0x590a368e
    Faulting module name: libcef.dll, version: 3.2924.1538.0, time stamp: 0x586e28d8
    Exception code: 0x80000003
    Fault offset: 0x00e64389
    Faulting process id: 0x4644
    Faulting application start time: 0x01d2f9e4d6d80124
    Faulting application path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\NVIDIA GeForce Experience.exe
    Faulting module path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\libcef.dll
    Report Id: 882b05d6-bf59-4b5b-a888-4c234a28306b
    Faulting package full name: 
    Faulting package-relative application ID:
    7/11/2017 1:29 AM    Application Error    Faulting application name: NVIDIA Share.exe, version: 56.2924.1538.1, time stamp: 0x590a36a6
    Faulting module name: libcef.dll, version: 3.2924.1538.0, time stamp: 0x586e28d8
    Exception code: 0x80000003
    Fault offset: 0x00e64389
    Faulting process id: 0x1a5c
    Faulting application start time: 0x01d2f9e51c2bd3b1
    Faulting application path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\NVIDIA Share.exe
    Faulting module path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\libcef.dll
    Report Id: bf1b04cc-d26c-4eca-92f1-8459311647ee
    Faulting package full name: 
    Faulting package-relative application ID:
    7/11/2017 1:27 AM    Application Error    Faulting application name: NVIDIA Share.exe, version: 56.2924.1538.1, time stamp: 0x590a36a6
    Faulting module name: libcef.dll, version: 3.2924.1538.0, time stamp: 0x586e28d8
    Exception code: 0x80000003
    Fault offset: 0x00e64389
    Faulting process id: 0x27e0
    Faulting application start time: 0x01d2f9e4d3bce084
    Faulting application path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\NVIDIA Share.exe
    Faulting module path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\libcef.dll
    Report Id: eaed6086-1ba3-4089-b13c-127764616f78
    Faulting package full name: 
    Faulting package-relative application ID:
    7/11/2017 1:03 AM    Application Error    Faulting application name: NVIDIA Share.exe, version: 56.2924.1538.1, time stamp: 0x590a36a6
    Faulting module name: libcef.dll, version: 3.2924.1538.0, time stamp: 0x586e28d8
    Exception code: 0x80000003
    Fault offset: 0x00e64389
    Faulting process id: 0x29f8
    Faulting application start time: 0x01d2f9e17ced20ba
    Faulting application path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\NVIDIA Share.exe
    Faulting module path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\libcef.dll
    Report Id: f786e3a2-b53e-48b1-8310-e8a5ae16f31d
    Faulting package full name: 
    Faulting package-relative application ID:
    7/11/2017 1:27 AM    Application Error    Faulting application name: NVIDIA Share.exe, version: 56.2924.1538.1, time stamp: 0x590a36a6
    Faulting module name: libcef.dll, version: 3.2924.1538.0, time stamp: 0x586e28d8
    Exception code: 0x80000003
    Fault offset: 0x00e64389
    Faulting process id: 0x2b74
    Faulting application start time: 0x01d2f9e4de62bf0f
    Faulting application path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\NVIDIA Share.exe
    Faulting module path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\libcef.dll
    Report Id: 6e05c2c8-e9a1-4ced-8af2-959d16a5e841
    Faulting package full name: 
    Faulting package-relative application ID:
    7/11/2017 1:16 AM    Application Error    Faulting application name: NVIDIA Share.exe, version: 56.2924.1538.1, time stamp: 0x590a36a6
    Faulting module name: libcef.dll, version: 3.2924.1538.0, time stamp: 0x586e28d8
    Exception code: 0x80000003
    Fault offset: 0x00e64389
    Faulting process id: 0x3340
    Faulting application start time: 0x01d2f9e36344b12f
    Faulting application path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\NVIDIA Share.exe
    Faulting module path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\libcef.dll
    Report Id: 8c5b4a84-2173-4864-93b5-0b3622784c07
    Faulting package full name: 
    Faulting package-relative application ID:
    7/11/2017 1:02 AM    Application Error    Faulting application name: NVIDIA Share.exe, version: 56.2924.1538.1, time stamp: 0x590a36a6
    Faulting module name: libcef.dll, version: 3.2924.1538.0, time stamp: 0x586e28d8
    Exception code: 0x80000003
    Fault offset: 0x00e64389
    Faulting process id: 0x36e4
    Faulting application start time: 0x01d2f9e15c60c37e
    Faulting application path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\NVIDIA Share.exe
    Faulting module path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\libcef.dll
    Report Id: e0d1bd87-c110-4611-97b9-7c90c63f37d2
    Faulting package full name: 
    Faulting package-relative application ID:
    7/11/2017 1:03 AM    Application Error    Faulting application name: NVIDIA Share.exe, version: 56.2924.1538.1, time stamp: 0x590a36a6
    Faulting module name: libcef.dll, version: 3.2924.1538.0, time stamp: 0x586e28d8
    Exception code: 0x80000003
    Fault offset: 0x00e64389
    Faulting process id: 0x380c
    Faulting application start time: 0x01d2f9e1739d4937
    Faulting application path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\NVIDIA Share.exe
    Faulting module path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\libcef.dll
    Report Id: 2f9c0bda-f646-4d48-8646-ab5b140f6ad3
    Faulting package full name: 
    Faulting package-relative application ID:
    7/11/2017 1:04 AM    Application Error    Faulting application name: NVIDIA Share.exe, version: 56.2924.1538.1, time stamp: 0x590a36a6
    Faulting module name: libcef.dll, version: 3.2924.1538.0, time stamp: 0x586e28d8
    Exception code: 0x80000003
    Fault offset: 0x00e64389
    Faulting process id: 0x39a8
    Faulting application start time: 0x01d2f9e1b43948da
    Faulting application path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\NVIDIA Share.exe
    Faulting module path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\libcef.dll
    Report Id: 0628c08c-95cc-4f42-974b-7a035575d3ee
    Faulting package full name: 
    Faulting package-relative application ID:
    7/11/2017 1:26 AM    Application Error    Faulting application name: NVIDIA Share.exe, version: 56.2924.1538.1, time stamp: 0x590a36a6
    Faulting module name: libcef.dll, version: 3.2924.1538.0, time stamp: 0x586e28d8
    Exception code: 0x80000003
    Fault offset: 0x00e64389
    Faulting process id: 0x3d64
    Faulting application start time: 0x01d2f9e4c06895fc
    Faulting application path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\NVIDIA Share.exe
    Faulting module path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\libcef.dll
    Report Id: 56d856e9-f658-440b-bc20-a6903a1ed8a0
    Faulting package full name: 
    Faulting package-relative application ID:
    7/11/2017 1:02 AM    Application Error    Faulting application name: NVIDIA Share.exe, version: 56.2924.1538.1, time stamp: 0x590a36a6
    Faulting module name: libcef.dll, version: 3.2924.1538.0, time stamp: 0x586e28d8
    Exception code: 0x80000003
    Fault offset: 0x00e64389
    Faulting process id: 0x4180
    Faulting application start time: 0x01d2f9e167b624a0
    Faulting application path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\NVIDIA Share.exe
    Faulting module path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\libcef.dll
    Report Id: 64b5e5bb-f75d-4383-addb-dc451d4edf3b
    Faulting package full name: 
    Faulting package-relative application ID:
    7/11/2017 1:03 AM    Application Error    Faulting application name: NVIDIA Share.exe, version: 56.2924.1538.1, time stamp: 0x590a36a6
    Faulting module name: libcef.dll, version: 3.2924.1538.0, time stamp: 0x586e28d8
    Exception code: 0x80000003
    Fault offset: 0x00e64389
    Faulting process id: 0x4260
    Faulting application start time: 0x01d2f9e188f9cb29
    Faulting application path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\NVIDIA Share.exe
    Faulting module path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\libcef.dll
    Report Id: 5f6829c8-f5ac-44e1-9919-3e901ae2e012
    Faulting package full name: 
    Faulting package-relative application ID:
    7/11/2017 1:26 AM    Application Error    Faulting application name: NVIDIA Share.exe, version: 56.2924.1538.1, time stamp: 0x590a36a6
    Faulting module name: libcef.dll, version: 3.2924.1538.0, time stamp: 0x586e28d8
    Exception code: 0x80000003
    Fault offset: 0x00e64389
    Faulting process id: 0x4660
    Faulting application start time: 0x01d2f9e4c9c1bdd8
    Faulting application path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\NVIDIA Share.exe
    Faulting module path: C:\Program Files (x86)\NVIDIA Corporation\NVIDIA GeForce Experience\libcef.dll
    Report Id: 3223fac1-f240-425f-9eaf-cb727312aa14
    Faulting package full name: 
    Faulting package-relative application ID:
    7/11/2017 1:28 AM    Application Error    Faulting application name: NVIDIA Web Helper.exe, version: 6.9.5.0, time stamp: 0x58fa0ea2
    Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
    Exception code: 0xc0000005
    Fault offset: 0x00000000
    Faulting process id: 0x196c
    Faulting application start time: 0x01d2f9e4fed680e8
    Faulting application path: C:\Program Files (x86)\NVIDIA Corporation\NvNode\NVIDIA Web Helper.exe
    Faulting module path: unknown
    Report Id: 11074389-1e08-497e-ae04-26e2fb94dc64
    Faulting package full name: 
    Faulting package-relative application ID:
    7/11/2017 1:04 AM    Application Error    Faulting application name: NVIDIA Web Helper.exe, version: 6.9.5.0, time stamp: 0x58fa0ea2
    Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
    Exception code: 0xc0000005
    Fault offset: 0x00000000
    Faulting process id: 0x2030
    Faulting application start time: 0x01d2f9e19b5b8fa7
    Faulting application path: C:\Program Files (x86)\NVIDIA Corporation\NvNode\NVIDIA Web Helper.exe
    Faulting module path: unknown
    Report Id: 6ef6ebe5-67cc-4e51-a620-d4a7ee04ad9c
    Faulting package full name: 
    Faulting package-relative application ID:

    Code:
    7/7/2017 10:03 AM    Application Error    Faulting application name: mbamservice.exe, version: 3.1.0.479, time stamp: 0x58f6af02
    Faulting module name: mbamservice.exe, version: 3.1.0.479, time stamp: 0x58f6af02
    Exception code: 0xc0000005
    Fault offset: 0x0000000000065d25
    Faulting process id: 0x33b4
    Faulting application start time: 0x01d2f708401dc6b9
    Faulting application path: C:\Program Files\Malwarebytes\Anti-Malware\mbamservice.exe
    Faulting module path: C:\Program Files\Malwarebytes\Anti-Malware\mbamservice.exe
    Report Id: 8ea7a7f5-9b28-44b4-a653-7d1c7bde1677
    Faulting package full name: 
    Faulting package-relative application ID:
    Code:
    7/12/2017 3:29 PM    Application Error    Faulting application name: mbam.exe, version: 3.0.0.1068, time stamp: 0x59125ef2
    Faulting module name: Qt5Core.dll, version: 5.6.2.0, time stamp: 0x58ed4d4f
    Exception code: 0xc0000005
    Fault offset: 0x001a497b
    Faulting process id: 0x42ac
    Faulting application start time: 0x01d2fb23b41b9fa6
    Faulting application path: C:\Program Files\Malwarebytes\Anti-Malware\mbam.exe
    Faulting module path: C:\Program Files\Malwarebytes\Anti-Malware\Qt5Core.dll
    Report Id: 8008068b-0912-4879-908f-89ba0cfcf09e
    Faulting package full name: 
    Faulting package-relative application ID:
    Last edited by zbook; 16 Jul 2017 at 00:36.
      My ComputerSystem Spec

  3.    16 Jul 2017 #3

    Hello zbook! thank you so much for your reply
    Some things I had already done (some before posting, some in the days leading up to posting)
    - Disabled windows fast startup (right before you posted your reply actually)
    - Completely removed Malwarebytes from computer (around 7/13 I believe)
    - Reset BIOS, Updated BIOS to newest version available from Asus website
    Things I somehow managed to avoid doing:
    -Defenestrating computer from second floor home office window

    Steps followed below:

    1) winver
    Version 1703 (OS Build 15063.483)

    2) sfc /scannow

    Beginning system scan. This process will take some time.Beginning verification phase of system scan.Verification 100% complete.
    3) dism /online /cleanup-image /restore
    Deployment Image Servicing and Management toolVersion: 10.0.15063.0Image Version: 10.0.15063.0[==========================100.0%==========================] The restore operation completed successfully.The operation completed successfully.
    4) C:\WINDOWS\system32>chkdsk /scan
    The type of the file system is NTFS.
    Stage 1: Examining basic file system structure ...
    848384 file records processed.
    File verification completed.
    7580 large file records processed.
    0 bad file records processed.
    Stage 2: Examining file name linkage ...
    1074462 index entries processed.
    Index verification completed.
    0 unindexed files scanned.
    0 unindexed files recovered to lost and found.
    Stage 3: Examining security descriptors ...
    Security descriptor verification completed.
    113040 data files processed.
    CHKDSK is verifying Usn Journal...
    41212520 USN bytes processed.
    Usn Journal verification completed.
    Windows has scanned the file system and found no problems.
    No further action is required.
    976273062 KB total disk space.
    525861180 KB in 565453 files.
    289012 KB in 113041 indexes.
    0 KB in bad sectors.
    990270 KB in use by the system.
    65536 KB occupied by the log file.
    449132600 KB available on disk.
    4096 bytes in each allocation unit.
    244068265 total allocation units on disk.
    112283150 allocation units available on disk.
    5) windows updates:

    Already up to date. Latest updates showing to be from 7/11, KB4025376 and KB4025342, don't see any failures.

    6) Drivers
    Various drivers from mobo manufacturer updated, (USB, audio, chipset id stuff, MEI, SATA)
    Nvidia drivers removed and clean install
    Uninstalled and reinstalled Intel Performance Boost Max
    NOTE: Wacom driver link on your post is a dead link.
    Due to an issue on recent wacom drivers, I am unable to have latest release (it makes only one device work, cintiq. Only way for both (Cintiq, Intous3) to work is to have an older version of driver. Wacom = terribad regarding drivers. Hopefuly (doesn't seem to be) this isn't the principal culprit. If this causes issues, I may have to upgrade my non-screen tablet to a newer model.


    7) Malwarebytes

    removed prior to post, still off system until I have a stable one
    8) Fast boot
    disabled shortly after original post. BIOS was previously reset and updated to latest release (couple of days ago)


    I just finished all of these, and I am doing a shutdown / boot up cycle and then keeping an eye on the system to see uptime. Unfortunately not a regular use today, but monday will definitely be one (in spades), so will definitely keep an eye on stability, overnight crashes, etc and report back with any problems and/or photos of a pile of computer parts on the driveway with confused neighbors standing around.

    Thank you so much again for the help so far!
      My ComputerSystem Spec

  4.    16 Jul 2017 #4

    @zbook Unfortunately, looks like still something is broken, had another crash around 3pm today, computer was unattended, only task manager was opened i believe.

    file below (removed the other 22 dumps from earlier from this zip)
      My ComputerSystem Spec


  5. Posts : 8,721
    windows 10 professional version 1607 build 14393.969 64 bit
       16 Jul 2017 #5

    The Intel turbo boost max continues to produce bsod after re-installation.
    When you re-installed it was the source Asus or Intel?
    See if there is an older version of this driver to roll back to.
    Intel has customer service and consider making an OP there to see if they have any suggestions to find a working driver in the computer environment.
    Contact Support
    They have a driver update utility. it may have an alternative.
    IntelĀ® Driver Update Utility
    Asus may have a support options depending on the warranty status and approaching it with them to may be useful.
    If there is no older driver to roll back to it would have to be uninstalled to prevent the bsod.
    If there is an older driver you could see what happens over time or you could stress the CPU with the Intel processor diagnostic tool kit.


    This is the misbehaving driver information:
    Code:
    IntelTurboBo IntelTurboBoostMax     IntelTurboBoostMax     Kernel        Manual     Running    OK         TRUE        FALSE        4,096             98,304      0          6/10/2017 3:58:53 AM   C:\WINDOWS\system32\DRIVERS\IntelNit.sys         4,096
    This is the debugging information:

    Code:
    BugCheck A, {ffffac0e775e30c0, 2, 1, fffff803231dc87a}*** WARNING: Unable to verify timestamp for IntelNit.sys*** ERROR: Module load completed but symbols could not be loaded for IntelNit.sys*** WARNING: Unable to verify checksum for win32k.sysProbably caused by : memory_corruption
      My ComputerSystem Spec

  6.    17 Jul 2017 #6

    Darn,
    Yeah it was direct from Intel, I couldn't find any version of this from the Asus website.
    I have uninstalled it for now as I need a stable computer for the work week (and not have it bsod in the middle of a screenshare with a client like last week, that was fun)

    On that note however, seeing "win32k" mentioned on the degugging info there, could this be related? I see a lot of Win32k warnings on event viewer right after a boot up?

    (come to think of it, a LOT of warnings and errors in event viewer directly after bootup, the Asus USB drivers also seem to now be causing a ton more than the windows default ones)
    Attachment 144293
      My ComputerSystem Spec

  7.    17 Jul 2017 #7

    Additional information: I actually just found the ITBM drivers on the asus site for this motherboard, not sure how I completelly missed them there. I will try installing those later tonight and see if there's any crashes over night with that installed
      My ComputerSystem Spec

  8.    18 Jul 2017 #8

    @zbook well, it has been 30 hours since the last crash, which is far longer than has been stable in a while. I will be marking this as solved since I think at least we neutralized the culprit.

    FYI some issues installing the Asus one. For one the download they have seems to only install the driver, not the app (so if you uninstall the whole thing then you don't have access.)
    However, in the downloads I found an Asus app that essentially serves the same function (AI Suite 3, Asus Power Core) so no need for the ITBM to be installed. One thing I noticed is that even though the app was uninstalled, its driver component still showed in the services, so I disabled that for now, and so far haven't had any issues.

    Thanks again for all the help!
      My ComputerSystem Spec


  9. Posts : 8,721
    windows 10 professional version 1607 build 14393.969 64 bit
       18 Jul 2017 #9

    Your welcome.
    Once you have the updated software/driver installed make a brand new restore point
    Backup files to the cloud or another drive.
    Make a new image using Macrium and save the image to another drive.
    With all of the above you will be in great shape should there be any future computer problems.
      My ComputerSystem Spec


 

Related Threads
Solved 0x139 BSODs daily when waking up from sleep in BSOD Crashes and Debugging
Hello and thank you in advance for your assistance, if you have any. I'm open to any suggestions at this point. See my DM files attached at the bottom of this post. This is my Dell Inspiron 13 7359. The problem started about a week ago; 0x139...
86517 Hey. So, I built my computer in August of 2015, and since then I've had nearly daily problems with BSODs. For a few months (between October 2015 and March 2016) they had gone away (no idea what happened to make them stop), but then randomly...
Getting Random BSODs daily in BSOD Crashes and Debugging
Hi, I've been having constant BSODs ever since I got windows 10. Already did clean install and I'm really just going crazy. Any help would be really apreciated.
SuperFetch and Prefetch are disabled. Memcheck gives no errors. The computer ran almost 24/7 for ~~10 months before the Win 10 upgrade, not a single BSOD. Since 10, I've gotten 15-20. I've followed all the steps in this article: Windows 10: How...
Daily BSODs, brand new HD and windows 10 in BSOD Crashes and Debugging
Hi, I recently got a new HD and have a fresh install of Windows 10 on it. It's less than a week old. I get a BSOD about once a day. They all appear to be caused by ntoskrnl.exe. Googling suggests that this is usually caused by bad RAM. I've run...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 18:14.
Find Us