Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [E:\Temp\Rar$DI00.618\110910-60247-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x8224a000 PsLoadedModuleList = 0x82392810
Debug session time: Tue Nov 9 14:15:52.688 2010 (UTC - 5:00)
System Uptime: 0 days 1:35:31.204
Loading Kernel Symbols
...............................................................
................................................................
................................................
Loading User Symbols
Loading unloaded module list
................
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000047, The exception code that was not handled
Arg2: 822d46b7, The address that the exception occurred at
Arg3: 8078aa70, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000047 - An attempt was made to release a semaphore such that its maximum count would have been exceeded.
FAULTING_IP:
nt!KeReleaseSemaphore+a7
822d46b7 cc int 3
TRAP_FRAME: 8078aa70 -- (.trap 0xffffffff8078aa70)
ESP EDITED! New esp=8078ae20
ErrCode = 00000000
eax=00000000 ebx=82373d20 ecx=00000002 edx=00000000 esi=880573b8 edi=00000064
eip=822d46b7 esp=8078aae4 ebp=8078ae30 iopl=0 nv up ei pl nz na po nc
cs=0000 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000202
nt!KeReleaseSemaphore+0xa7:
822d46b7 cc int 3
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: DeviceDisplayO
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from bf27cb74 to 822d46b7
STACK_TEXT:
8078ae30 bf27cb74 880573b8 00000000 00000001 nt!KeReleaseSemaphore+0xa7
WARNING: Stack unwind information not available. Following frames may be wrong.
8078ae5c 822b2b33 88941020 0191be28 889410d8 Salmosa+0xb74
8078aea0 90317868 8228a354 84c4a008 00000000 nt!IopfCompleteRequest+0x128
8078aed0 90318178 88577ea8 8891be28 88335398 USBPORT!USBPORT_Core_iCompleteDoneTransfer+0x6e0
8078aefc 9031b9af 85b55028 85b550f0 85b55a98 USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x33b
8078af24 90315d18 85b55028 85b55a98 85b55002 USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xbc
8078af48 822b23b5 85b55aa4 85b55002 00000000 USBPORT!USBPORT_Xdpc_Worker+0x173
8078afa4 822b2218 82373d20 87f74d48 00000000 nt!KiExecuteAllDpcs+0xf9
8078aff4 822b19dc ab893bec 00000000 00000000 nt!KiRetireDpcList+0xd5
8078aff8 ab893bec 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2c
822b19dc 00000000 0000001a 00d6850f bb830000 0xab893bec
STACK_COMMAND: kb
FOLLOWUP_IP:
Salmosa+b74
bf27cb74 ?? ???
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: Salmosa+b74
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Salmosa
IMAGE_NAME: Salmosa.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 47e2275b
FAILURE_BUCKET_ID: 0x8E_Salmosa+b74
BUCKET_ID: 0x8E_Salmosa+b74
Followup: MachineOwner