Minidump Analysis

175 pts.
Tags:
BSOD
Bugcheck
Drivers
Hi all,

I've come across a minidump file that's pretty cryptic, so I'm having a tough time with it. Lately, I've been getting some bsod, and unfortunately the minidumps are pointing more to driver faults within the stack (which makes it difficult to find, for me anyway). If someone wouldn't mind having a look, I'd appreciate it!

Details: ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* 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: 896a5008, Address of the IRP

Arg2: 00001bc0

Arg3: 00000000

Arg4: 00000000

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

IRP_ADDRESS: 896a5008

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x44

PROCESS_NAME: System

LOCK_ADDRESS: 8055b4e0 -- (!locks 8055b4e0)

Resource @ nt!PiEngineLock (0x8055b4e0) Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.

WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks PNP_TRIAGE:

Lock address : 0x8055b4e0

Thread Count : 0

Thread address: 0x00000000

Thread wait : 0x0

LAST_CONTROL_TRANSFER: from 804ef4d4 to 804f9f43

STACK_TEXT: b8507998 804ef4d4 00000044 896a5008 00001bc0 nt!KeBugCheckEx+0x1b b85079c0 b813e3fd 896a5008 b85079e8 b813e948 nt!IopFreeIrp+0x22 b85079cc b813e948 8a297bb0 896a5008 8a5110e8 usbhub!USBH_HubCancelIdleIrp+0x2d b85079e8 804f1605 8a286de8 896e1008 8a5110e8 usbhub!USBH_PortIdleNotificationCancelRoutine+0x4c b8507a00 b823ab16 896e1008 89877ad4 898779f8 nt!IoCancelIrp+0x65 WARNING: Stack unwind information not available. Following frames may be wrong. b8507a14 b824398d 005110e8 89877af8 8a56d360 oz776+0x2b16 b8507a2c 804ef19f 00000007 898779f8 b8507aac oz776+0xb98d b8507a3c 80592b63 00000000 8a254af8 8a254bd8 nt!IopfCallDriver+0x31 b8507a68 804f6de7 8a511030 b8507a88 8a254bd8 nt!IopSynchronousCall+0xb7 b8507ab0 8058ee79 00000000 8a286de8 00000001 nt!IopQueryDeviceRelations+0x45 b8507ac8 805922db 8a254af8 00000001 8a1f4b50 nt!PipEnumerateDevice+0x23 b8507d20 8059271a 8a7dadc8 00000001 00000000 nt!PipProcessDevNodeTree+0x21b b8507d54 804f6981 00000003 8055b5c0 8056485c nt!PiProcessReenumeration+0x60 b8507d7c 80538789 00000000 00000000 8a7bc3c8 nt!PipDeviceActionWorker+0x14b b8507dac 805cff62 00000000 00000000 00000000 nt!ExpWorkerThread+0xef b8507ddc 8054611e 8053869a 00000001 00000000 nt!PspSystemThreadStartup+0x34 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

STACK_COMMAND: kb

FOLLOWUP_IP: oz776+2b16 b823ab16 ?? ???

SYMBOL_STACK_INDEX: 5 SYMBOL_NAME: oz776+2b16 FOLLOWUP_NAME: MachineOwner MODULE_NAME: oz776 IMAGE_NAME: oz776.sys DEBUG_FLR_IMAGE_TIMESTAMP: 476b05be FAILURE_BUCKET_ID: 0x44_oz776+2b16 BUCKET_ID: 0x44_oz776+2b16 Followup: MachineOwner



Software/Hardware used:
Dell Latitude D830
ASKED: March 17, 2011  1:36 PM
UPDATED: May 11, 2011  9:57 PM

Answer Wiki

Thanks. We'll let you know when a new response is added.

Looks like a smartcard reader is causing the problem: oz776.sys Check the computer vendor for updated drivers.

<a href=”http://support.dell.com/support/downloads/download.aspx?c=us&l=en&s=gen&releaseid=R182329&SystemID=PREC_M6300&servicetag=&os=WW1&osl=en&deviceid=13406&devlib=0&typecnt=0&vercnt=2&catid=&impid=&formatcnt=1&libid=50&typeid=-1&dateid=-1&formatid=-1&fileid=248520″>Dell link</a>

Discuss This Question: 1  Reply

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • Egberts
    This is the fault of the power manager who is changing the USB idle state TWICE. A microsoft bug.
    10 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following