stop error 0x1e on new windows 7 Pro computer

vicblack · 28 Oct 2012

New Lenovo ThinkCentre Edge 72. Added 16gb memory from Crucial using Crusials memory selector tool and added dual DVI graphics card. I do not have the graphics card details with me right now. It was pulled from the users previous WIndows 7 Pro computer.
I have attached the zip file created by the Diagnostic Tool.

Arc · 28 Oct 2012

Welcome aboard.

From your crash dump, I found it: Intel(R) USB 3.0 eXtensible Host Controller Driver. It is of January 2012. You search for an update in Intel Download Center.

Let us know the results.

vicblack · 30 Oct 2012

Thansk for the quick reply. I downloaded teh enw drivers from Intel and I am stil getting a blue screen. I have attached new reports.

Arc · 30 Oct 2012

Code:

 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

Debugging Details:
------------------
CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  System

CURRENT_IRQL:  2

TAG_NOT_DEFINED_c000000f:  FFFFF88003322FB0

EXCEPTION_RECORD:  fffff8800331b338 -- (.exr 0xfffff8800331b338)
ExceptionAddress: fffff800031c49bc (nt!ExDeferredFreePool+0x0000000000000100)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff8800331b3e0 -- (.trap 0xfffff8800331b3e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa801627a5b0 rbx=0000000000000000 rcx=fffff8000321f740
rdx=c001000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800031c49bc rsp=fffff8800331b570 rbp=0000000000000000
 r8=c001000000000000  r9=fffffa80157a4570 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!ExDeferredFreePool+0x100:
fffff800`031c49bc 4c8b02          mov     r8,qword ptr [rdx] ds:c0010000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000308fbbe to fffff80003098190

STACK_TEXT:  
fffff880`0331a418 fffff800`0308fbbe : 00000000`00000000 00000000`00000000 fffff880`0331ab90 fffff800`030c3180 : nt!KeBugCheck
fffff880`0331a420 fffff800`030c2e4d : fffff800`0329e770 fffff800`031db2f0 fffff800`03019000 fffff880`0331b338 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`0331a450 fffff800`030c1c25 : fffff800`031defac fffff880`0331a4c8 fffff880`0331b338 fffff800`03019000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`0331a480 fffff800`030d2bb1 : fffff880`0331b338 fffff880`0331ab90 fffff880`00000000 fffffa80`00000003 : nt!RtlDispatchException+0x415
fffff880`0331ab60 fffff800`03097842 : fffff880`0331b338 00000000`00000000 fffff880`0331b3e0 00000000`00000000 : nt!KiDispatchException+0x135
fffff880`0331b200 fffff800`0309614a : fffff880`009e9180 fffffa80`163f23d8 fffff880`009eb380 fffffa80`163f27a8 : nt!KiExceptionDispatch+0xc2
fffff880`0331b3e0 fffff800`031c49bc : 00000000`0000000f fffff800`03608b7f fffffa80`13e76b58 fffffa80`13bea5f0 : nt!KiGeneralProtectionFault+0x10a
fffff880`0331b570 fffff800`031c41a1 : 00000000`00000000 fffffa80`15ce7660 00000000`00000000 fffff880`009e9180 : nt!ExDeferredFreePool+0x100
fffff880`0331b600 fffff880`071d1e15 : fffffa80`13e85890 fffffa80`00000000 00000000`50425355 00000000`00000000 : nt!ExFreePoolWithTag+0x411
fffff880`0331b6b0 fffff800`0309bbd1 : fffffa80`15ee1e93 00000000`00000000 00000000`00000000 fffffa80`13e85890 : usbprint!USBPRINT_AsyncReadWrite_Complete+0x111
fffff880`0331b700 fffff880`04c9624b : 00000000`00000000 fffff880`04cadf00 fffffa80`1383ab50 00000000`00000000 : nt!IopfCompleteRequest+0x341
fffff880`0331b7f0 00000000`00000000 : fffff880`04cadf00 fffffa80`1383ab50 00000000`00000000 fffffa80`1383ab50 : iusb3xhc+0x6424b


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!ExDeferredFreePool+100
fffff800`031c49bc 4c8b02          mov     r8,qword ptr [rdx]

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  nt!ExDeferredFreePool+100

FOLLOWUP_NAME:  Pool_corruption

IMAGE_NAME:  Pool_Corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: Pool_Corruption

FAILURE_BUCKET_ID:  X64_0x1E_nt!ExDeferredFreePool+100

BUCKET_ID:  X64_0x1E_nt!ExDeferredFreePool+100

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

In such a situation, we may do two things initially ....

1. Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

2. RAM - Test with Memtest86+
Run memtest for at least eight passes, preferably overnight.

Let us know the results.