++ ATOT official NEF thread part IV ++

[fjmeat]

90901

 

[fjmeat]

90902

 

[fjmeat]

90903

 

[fjmeat]

90904

 

[fjmeat]

90905

 

[fjmeat]

90906

 

[fjmeat]

90907

 

[fjmeat]

90908

 

[fjmeat]

90909

 

[fjmeat]

90910

 

[fjmeat]

90911

 

[fjmeat]

90912

 

[fjmeat]

90913

 

[fjmeat]

90914

 

[fjmeat]

90915

 

[fjmeat]

90916

 

[mnewsham]

anyone care to help me pin down the driver causing my BSOD's?

MULTIPLE_IRP_COMPLETE_REQUESTS (44)
A driver has requested that an IRP be completed (IoCompleteRequest()), but
the packet has already been completed. This is a tough bug to find because
the easiest case, a driver actually attempted to complete its own packet
twice, is generally not what happened. Rather, two separate drivers each
believe that they own the packet, and each attempts to complete it. The
first actually works, and the second fails. Tracking down which drivers
in the system actually did this is difficult, generally because the trails
of the first driver have been covered by the second. However, the driver
stack for the current request can be found by examining the DeviceObject
fields in each of the stack locations.
Arguments:
Arg1: ffffe00000de3d90, Address of the IRP
Arg2: 0000000000000f8a
Arg3: 0000000000000000
Arg4: 0000000000000000

Debugging Details:
------------------

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

IRP_ADDRESS: ffffe00000de3d90

FOLLOWUP_IP:
Hamdrv+1f0a
fffff800`01a59f0a ?? ???

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x44

PROCESS_NAME: svchost.exe

CURRENT_IRQL: 2

DEVICE_OBJECT: ffffe000021467a0

LAST_CONTROL_TRANSFER: from fffff801eeffdb4b to fffff801eefc2ca0

STACK_TEXT:
ffffd000`23b3b958 fffff801`eeffdb4b : 00000000`00000044 ffffe000`00de3d90 00000000`00000f8a 00000000`00000000 : nt!KeBugCheckEx
ffffd000`23b3b960 fffff800`01a59f0a : 00000000`00000000 ffffd000`2ac38000 ffffe000`021283c0 ffffe000`021283c0 : nt! ?? ::FNODOBFM::`string'+0x2a9ab
ffffd000`23b3ba70 00000000`00000000 : ffffd000`2ac38000 ffffe000`021283c0 ffffe000`021283c0 ffffd000`00000020 : Hamdrv+0x1f0a


STACK_COMMAND: kb

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: Hamdrv+1f0a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Hamdrv

IMAGE_NAME: Hamdrv.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 52e10c23

FAILURE_BUCKET_ID: X64_0x44_Hamdrv+1f0a

BUCKET_ID: X64_0x44_Hamdrv+1f0a

Followup: MachineOwner
---------

 

[mnewsham]

Figured out which was the offending driver (I think) will have to wait and see if another BSOD crops up, but hoping not.

 

[Bubbleawsome]

Have you run who crashed?

 

[rudeguy]

It could be lupus

 

[mnewsham]

Have you run who crashed?

"consider using the professional edition"

 

[eldorado99]

ned

 

[fjmeat]

what is who crashed?

 

[eldorado99]

u cradhes

 

[rudeguy]

Have you tested for syphilis?