Bugcheck possibly USB drive related


  1. Posts : 7
    Windows 10
       #1

    Bugcheck possibly USB drive related


    Hi find attached the bug check report, only two things that I can think of that would have caused this is USB drives attached, using KeepAliveHD to have my Western Digital My Book Drive not go to sleep or the GEFORCE drivers, which is updated but I do know there is issues with the new GEFORCE drivers. I include another programs diagnostics for DMP files if it can be of possible help
      My Computer


  2. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #2

    The dump indicates a problem with Comodo firewall:

    Code:
     *** WARNING: Unable to verify timestamp for cmdguard.sys
    *** ERROR: Module load completed but symbols could not be loaded for cmdguard.sys
    Please uninstall Comodo Firewall, see if that resolves the problem.
    Make sure the built-in Windows Firewall is running (Control Panel, Windows Firewall).

    If problems continue, enable Driver Verifier and let's see what that tells us.

    Driver Verifier is a diagnostic tool built into Windows 10, it is designed to verify both native Microsoft drivers and third party drivers. Driver Verifier's verification process involves putting heavy stress on drivers with the intention of making bad, outdated, incompatible or misbehaving drivers fail. The required result is a BSOD (Blue Screen of Death) which will generate a crash dump for debugging purposes.
    Machines exposed to Driver Verifier will run very sluggishly due to the stress being applied to the drivers.

    Driver Verifier - Enable and Disable in Windows 10

    Warning:
    It is not advised to run Driver Verifier for more than 48 hours at a time. Disable Driver Verifier after 48 hours or after receiving a BSOD, whichever happens soonest.

    Always create a Restore Point prior to enabling Driver Verifier.

    What we're looking for is a BSOD with a mini dump that will tell us what driver caused it.
      My Computers


  3. Posts : 7
    Windows 10
    Thread Starter
       #3

    Hi Ztruker, it is possible. I updated Comodo after the BSOD. Do you think I must run the Driver Verifier in order to see if it still give hiccups or let it run for 72 hours and see what will happen?

    Ztruker said:
    The dump indicates a problem with Comodo firewall:

    Code:
     *** WARNING: Unable to verify timestamp for cmdguard.sys
    *** ERROR: Module load completed but symbols could not be loaded for cmdguard.sys
    Please uninstall Comodo Firewall, see if that resolves the problem.
    Make sure the built-in Windows Firewall is running (Control Panel, Windows Firewall).

    If problems continue, enable Driver Verifier and let's see what that tells us.

    Driver Verifier is a diagnostic tool built into Windows 10, it is designed to verify both native Microsoft drivers and third party drivers. Driver Verifier's verification process involves putting heavy stress on drivers with the intention of making bad, outdated, incompatible or misbehaving drivers fail. The required result is a BSOD (Blue Screen of Death) which will generate a crash dump for debugging purposes.
    Machines exposed to Driver Verifier will run very sluggishly due to the stress being applied to the drivers.

    Driver Verifier - Enable and Disable in Windows 10

    Warning:
    It is not advised to run Driver Verifier for more than 48 hours at a time. Disable Driver Verifier after 48 hours or after receiving a BSOD, whichever happens soonest.

    Always create a Restore Point prior to enabling Driver Verifier.

    What we're looking for is a BSOD with a mini dump that will tell us what driver caused it.
      My Computer


  4. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #4

    I'd say wait and see what happens. Run DV if more problems.
      My Computers


  5. Posts : 7
    Windows 10
    Thread Starter
       #5

    It happened again


    Hi the laptop was running OK till today. Herewith the latest dump report
      My Computer


  6. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #6

    The last dump points to nldrv.sys:
    Code:
    BugCheck 133, {0, 501, 500, 0}
    
    *** WARNING: Unable to verify timestamp for nldrv.sys
    *** ERROR: Module load completed but symbols could not be loaded for nldrv.sys
    This belongs to Qualcomm Atheros Extensible Wireless LAN device driver. The one you have is dated 14-Mar-16 which is newer than the latest 8.1 driver on the ASUS web site. No Win 10 drivers offered. Where and when did you get this driver.
      My Computers


  7. Posts : 7
    Windows 10
    Thread Starter
       #7

    Hi Rich it was installed by DriverDr software, I rolled back to what is most probably the standard Windows driver 10.0.0.321 dated June 2014
      My Computer


  8. Posts : 7
    Windows 10
    Thread Starter
       #8

    Crashed again twice after rollback.


    It crashed twice after roll back. I had a good run with Windows 10 but I need stability so I am thinking of reinstalling Windows 8 specifically 8.1. I cannot go on like this
      My Computer


  9. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #9

    Try the 8.1 X64 driver from ASUS: ASUSTeK Computer Inc. -Support- Driver & Tools - G75VX

    Both dumps point to nldrv.sys, the Qualcom driver.
      My Computers


 

  Related Discussions
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 06:48.
Find Us




Windows 10 Forums