BSOD, seems random, usually 0x0000001e

BMarrow · 04 Mar 2013

Hi, I have a laptop (Dell E6530, Win7 Prox64) that has been getting a BSOD every few days, sometimes twice a day.

Usually it is this:

The bugcheck was: 0x0000001e (0x0000000000000000, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 022013-9516-01.

Most recently it was:

The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff80002a74b45, 0xfffff880077becd0, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 022713-8767-01.

I have already done SFC, and several MemTest86 passes. All come back clean.

I looked at a dmp file in WinDbg, but can't make much sense of it. After telling me a number of symbols couldn't be loaded I get: Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+100 )

I have attached a BMarrow.zip as described in the posting instructions.

any ideas?

Saurabh A · 04 Mar 2013

Hi BMarrow,

The crash dump that you shared points at the USB 3.0 Host controller driver (Intel(R) USB 3.0 eXtensible Host Controller Driver) in the system.

Code:

Unable to load image \SystemRoot\system32\DRIVERS\iusb3xhc.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for iusb3xhc.sys
*** ERROR: Module load completed but symbols could not be loaded for iusb3xhc.sys
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+100 )

Followup: Pool_corruption
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

Follow the steps listed below:
- Unplug the external drive/peripheral(s) if connected > Open Device Manager > Right click and remove the USB 3.0 Host Controller (As in the image below) > Restart the computer (Refer to the image below: The image is only for reference and you'll find 'Intel' instead of Renesas)

- Click http://downloadcenter.intel.com/Deta...ivers&lang=eng > Download and install the given file > Follow through with the install and finish

Do reply with the findings; will take it further.

BMarrow · 05 Mar 2013

Ahh, thank you! I noticed that driver coming up a few times, and I did reinstall it from support.dell.com, however, the version offered there is older than the one you linked to. I've just updated it from your Intel link and we'll keep an eye on it.

Saurabh A · 05 Mar 2013

Hi BMarrow,

Thank you for the reply.

The 'USB 3.0 Host Controller Driver' from 'Intel' may produce better results. Please observe the system performance to verify. If you still experience any 'Blue screen errors', please reply with a fresh copy of system crash data; will take it forward from there.