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

:)

 

usb drives

Windows isn't seeing my USB drives i cant format or copy a media to any of the ports for the usbs

* Moved from Insider

* Possibly related USB
drive

 

Constant BSOD, BUGCODE_USB_DRIVER Error. How do I stop this?

Here's some info from a minidump file. The error is consistent:

BugCheck FE, {4, ffffe001e199dcf0, ffffe001e24bca90, ffffe001e68e1a0c}

Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_ProcessURB+1049b )

BUGCODE_USB_DRIVER (fe)

USB Driver bugcheck, first parameter is USB bugcheck code.

Arguments:

Arg1: 0000000000000004, IRP_URB_DOUBLE_SUBMIT The caller has submitted an irp

that is already pending in the USB bus driver.

Arg2: ffffe001e199dcf0, Address of IRP

Arg3: ffffe001e24bca90, Address of URB

Arg4: ffffe001e68e1a0c

The error appears to be software (driver) related:

USB Bugcheck FE: BAD_URB (Double URB Submit) – What is it and how to avoid it?

Can you provide the following file via OneDrive which should contain more information on the crash:

C:\Windows\MEMORY.DMP

The memory.dmp file will be quite large so you could zip and compress the file with a third party application such as 7-Zip.

 

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[/quote] 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.

 

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?

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.[/quote]

 

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

 

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

 

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[/quote] 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.

 

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

 

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

 

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

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