1.    22 Jun 2016 #1
    Join Date : May 2016
    Posts : 7
    Windows 10

    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 ComputerSystem Spec
  2.    22 Jun 2016 #2
    Join Date : Apr 2014
    Space coast of Florida
    Posts : 5,340
    Windows 10 Pro X64 16299.19

    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 ComputersSystem Spec
  3.    22 Jun 2016 #3
    Join Date : May 2016
    Posts : 7
    Windows 10
    Thread Starter

    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?

    Quote Originally Posted by Ztruker View Post
    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 ComputerSystem Spec
  4.    22 Jun 2016 #4
    Join Date : Apr 2014
    Space coast of Florida
    Posts : 5,340
    Windows 10 Pro X64 16299.19

    I'd say wait and see what happens. Run DV if more problems.
      My ComputersSystem Spec
  5.    27 Jun 2016 #5
    Join Date : May 2016
    Posts : 7
    Windows 10
    Thread Starter

    It happened again


    Hi the laptop was running OK till today. Herewith the latest dump report
      My ComputerSystem Spec
  6.    27 Jun 2016 #6
    Join Date : Apr 2014
    Space coast of Florida
    Posts : 5,340
    Windows 10 Pro X64 16299.19

    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 ComputersSystem Spec
  7.    27 Jun 2016 #7
    Join Date : May 2016
    Posts : 7
    Windows 10
    Thread Starter

    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 ComputerSystem Spec
  8.    27 Jun 2016 #8
    Join Date : May 2016
    Posts : 7
    Windows 10
    Thread Starter

    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 ComputerSystem Spec
  9.    28 Jun 2016 #9
    Join Date : Apr 2014
    Space coast of Florida
    Posts : 5,340
    Windows 10 Pro X64 16299.19

    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 ComputersSystem Spec

 


Similar Threads
Thread Forum
BSOD - Possibly hardware related?
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...
BSOD Crashes and Debugging
BSOD with VPN - possibly related to network drivers
Hi, I am experiencing BSOD on the University network-eduroam, which have not happened before. It happens few minutes after I am connected to my Okayfreedom VPN, but I do not have this problem at home with my wifi which is strange. There is no...
BSOD Crashes and Debugging
0x124 - possibly related to NVIDIA drivers?
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...
BSOD Crashes and Debugging
BSOD bad_pool_caller, possibly related to wi-fi adapter
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...
BSOD Crashes and Debugging
Occasional BSOD - Possibly internet related?
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...
BSOD Crashes and Debugging
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 20:32.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums