Bugcheck possibly USB drive related


  1. sangiro
    Posts : 7
    Windows 10
       New #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
    Quote Quote

  3. Ztruker
    Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       New #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
    Quote Quote

  4. sangiro
    Posts : 7
    Windows 10
    Thread Starter
       New #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
    Quote Quote

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

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

  7. sangiro
    Posts : 7
    Windows 10
    Thread Starter
       New #5

    It happened again


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

  8. Ztruker
    Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       New #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
    Quote Quote

  9. sangiro
    Posts : 7
    Windows 10
    Thread Starter
       New #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
    Quote Quote

  10. sangiro
    Posts : 7
    Windows 10
    Thread Starter
       New #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
    Quote Quote

  12. Ztruker
    Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       New #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
    Quote Quote

 

  Related Discussions
Hi there The experts on this forum have been very helpful in the past in solving obscure Windows problems so I thought I'd ask another one: I used to sleep my Win10 machine every night, but a while ago it stopped being able to wake from sleep...
BSOD - Possibly hardware related?
in BSOD Crashes and Debugging

Hi all, I have an MSi GT70 20C Laptop that I've had numerous problems with. When I first ordered this laptop it was dead on arrival, and had to be shipped back for fixing. Since i've gotten it back, I have had BSODs ranging from 0-2 times a...
0x124 - possibly related to NVIDIA drivers?
in BSOD Crashes and Debugging

I've been having a crashing problem recently. So earlier today I finally got a dump file. It's a WHEA_UNCORRECTABLE_ERROR (0x124) but I have no idea how to interpret it. As you can see from my original post, I was having no trouble running...
Hi, I've had some issues with a BSOD for over a year now, first when I was running Windows 8 and now still with Windows 10. It first appeared after I got a USB wi-fi adapter which I replaced with an adapter that connected to the motherboard, but the...
Occasional BSOD - Possibly internet related?
in BSOD Crashes and Debugging

I have had my computer BSOD 5-6 times in roughly the past 2 weeks. The error on the BSOD is always CRITICAL_PROCESS_DIED, and it typically happens when I am surfing the web. Once, it happened while watching a video file on my drive. Before the...
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 15:08.
Find Us




Windows 10 Forums