usbport.sys/usbehci.sys BSODs have skyrocketed in last few days

Bilge · 11 Mar 2015

Arc, replaced my USB NETGEAR adapter with an internal PCI adapter, and have been minimizing the time when I've got my Smart Card reader plugged in ... and I still managed to get a recent BSOD claiming USBPORT.SYS as the culprit (the most recent dump file).

At this point, my only USB connections are a Dell RF keyboard receiver and 4-port USB hub with a MS Arc mouse adapter plugged into it ... unless some drivers are still running services despite the devices being disconnected.

Thanks,
Bilge

Arc · 12 Mar 2015

Code:

BugCheck D1, {fffffa8019c76109, 2, 1, fffff88005841803}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption

Followup: memory_corruption
---------

It repoets memory corruption, so we need to check for it. It causes for not only a failing memory but also a misbehaving driver.

Test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+

Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

If it does not show any error, enable Driver Verifier to monitor the drivers.

Driver Verifier - Enable and Disable

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

Tip

If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

Bilge · 16 Mar 2015

Arc, I ran the memTest for 10 passes with no errors, then ran the CCleaner pro cleanup/registry tweak, and finally finished up about 2 days worth of Driver Verifier with no BSODs.

Thanks,
Bilge

Arc · 17 Mar 2015

Well, apparently there is no more reasons for a stop 0xD1 left unchecked.

Bilge · 31 May 2015

It's been a while since I last posted, but I've still been experiencing a lot of BSODs, kicking out a usbport.sys or occasionally another code.

If DM Log Collector v1.2 no longer generates a final output file on the desktop (despite running flawlessly), is there another way to present the log collection for analysis?

Thanks!
Bilge

Arc · 01 Jun 2015

Bilge said:

If DM Log Collector v1.2 no longer generates a final output file on the desktop (despite running flawlessly), is there another way to present the log collection for analysis?

Yes, there is. Try SF Diag tool.

Bilge · 01 Jun 2015

Arc, Norton keeps blasting the SF Tool off the hard drive. Would WinDbg or another program provide the same visibility?

Also, despite 1-5 BSODs a day, it looked like I only had one 820MB Memory.dmp and one Minidump from March. I went in yesterday and ensured Win7 was configured to generate minidumps, but it would seem that all of the recent BSODs weren't generating minidumps. Do they tend to produce one file per event?

Bilge · 01 Jun 2015

Sorry for the double-tap, but in the one minidump file I have, windbg highlights ntoskrnl.exe and usbport.sys as likely culprits (though I didn't have time to figure out how to properly load the symbols for windbg).

V/r,
Bilge

Arc · 01 Jun 2015

Bilge said:

Arc, Norton keeps blasting the SF Tool off the hard drive.

Thats false.

Bilge · 01 Jun 2015

Arc, before I can get to the log collector it appears that the BSODs are no longer generating minidump files. Any tips for how to restore this? I've had it configured for minidumps under the Startup & Recovery menu, so I'm uncertain why they are no longer produced.

Bilge