Hey all,
I was hoping someone could take a look at this dump file for me, I'm on a Mac and don't have the appropriate tools or a means to get them on my PC right now. I've uploaded the dump file here:
http://eden.rutgers.edu/~neoraven/images/120710-15568-01.dmp
Just a heads up, it's a Windows 7 Pro 32-bit install on a partition using bootcamp. Thanks!
This was caused by mdfsysnt.sys part of the macdrive utility.
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\120710-15568-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: C:\symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x82e40000 PsLoadedModuleList = 0x82f88810
Debug session time: Tue Dec 7 11:12:18.657 2010 (GMT-5)
System Uptime: 0 days 0:03:39.844
Loading Kernel Symbols
.
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
..............................................................
................................................................
........................................
Loading User Symbols
Loading unloaded module list
........
0: kd> !analyze -v
*******************************************************************************
* *
* 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: 85318de0, Address of the IRP
Arg2: 00000eae
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------
IRP_ADDRESS: 85318de0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x44
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 897a2735 to 82ea8ebd
STACK_TEXT:
8b588c3c 897a2735 8b588ca8 8979eba1 86207710 nt!IopfCompleteRequest+0x4b0
WARNING: Stack unwind information not available. Following frames may be wrong.
8b588c44 8979eba1 86207710 85318de0 00000000 MDFSYSNT+0x3b735
8b588ca8 897a25c2 86207710 85318de0 02207dc2 MDFSYSNT+0x37ba1
8b588d00 82eadf3b 86207710 00000000 85237a70 MDFSYSNT+0x3b5c2
8b588d50 8304e6d3 00000000 a8fe1a61 00000000 nt!ExpWorkerThread+0x10d
8b588d90 82f000f9 82eade2e 00000000 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
STACK_COMMAND: kb
FOLLOWUP_IP:
MDFSYSNT+3b735
897a2735 ?? ???
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: MDFSYSNT+3b735
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: MDFSYSNT
IMAGE_NAME: MDFSYSNT.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a3fef3f
FAILURE_BUCKET_ID: 0x44_MDFSYSNT+3b735
BUCKET_ID: 0x44_MDFSYSNT+3b735
Followup: MachineOwner
---------
Quote