Hallo liebe Community,
auf der Suche nach Lösungsansätzen bin ich durch dieses Forum gestolpert, habe jedoch keine passenden Artikel zu meinem Problem gefunden.
Kurz und knapp:
Ich bekomme seid ein paar Tagen zu unterschiedlichen Zeiten Bluescreens mit der Fehlermeldung KERNEL_MODE_EXCEPTION_NOT_HANDLED_M.
Habe mich dann mal ein bisschen schlau gemacht und ein Debugging Tool ausprobiert, das mir diesen Fehlertext ausspuckte.
Microsoft (R) Windows Debugger Version 6.4.0007.2
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\122510-15428-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\Symbols*
Executable search path is:
Windows Longhorn Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Kernel base = 0x83002000 PsLoadedModuleList = 0x8314a810
Debug session time: Sat Dec 25 12:47:52.918 2010 (GMT+1)
System Uptime: 0 days 2:39:08.573
Loading Kernel Symbols
...........................................................................................................................................................
Loading unloaded module list
.....
Loading User Symbols
0: kd> g
^ No runnable debuggees error in 'g'
0: kd> BugCheck
^ Operation not supported by current debuggee error in 'BugCheck'
0: 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: c0000046, The exception code that was not handled
Arg2: 830428f8, The address that the exception occurred at
Arg3: 9deff26c, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
OVERLAPPED_MODULE: srv2
EXCEPTION_CODE: (NTSTATUS) 0xc0000046 - Ein Thread versuchte, ein Mutantobjekt freizugeben, ohne Besitzer des Objekts zu sein.
FAULTING_IP:
nt!KeReleaseMutant+215
830428f8 cc int 3
TRAP_FRAME: 9deff26c -- (.trap ffffffff9deff26c)
ESP EDITED! New esp=9deff61c
ErrCode = 00000000
eax=c0000046 ebx=86757850 ecx=87d10100 edx=00000000 esi=87d10194 edi=00000000
eip=830428f8 esp=9deff2e0 ebp=9deff654 iopl=0 nv up ei ng nz na pe nc
cs=0000 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000282
nt!KeReleaseMutant+0x215:
830428f8 cc int 3
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 830426da to 830428f8
STACK_TEXT:
9deff654 830426da 87d10194 00000001 00000000 nt!KeReleaseMutant+0x215
9deff66c 82cde048 87d10194 00000000 9deff6d0 nt!KeReleaseMutex+0x14
9deff67c 82ce0043 ffb90010 9deff880 9deff720 cdd!LeaveShadowLockCrit+0x1a
9deff6d0 82ce0644 00000008 00000008 9deff8f0 cdd!CDDMULTISURFLOCK::vLockShadowW+0x24d
9deff6f0 82ce4355 ff4ce3e8 9deff88c ffb83460 cdd!CDDMULTISURFLOCK::vInit+0x18c
9deff890 82ce482f ffb83460 ff4ce3e8 00000000 cdd!DrvBitBlt+0x6a3
9deff8c4 82b18fa3 ffb83460 ff4ce3e8 9deffa70 cdd!DrvCopyBits+0x27
9deff90c 82afec34 82ce4808 9deffb9c ffb83460 win32k!OffCopyBits+0x7d
9deffbb0 82b1c580 ffb83460 ff4ce3e8 00000000 win32k!SpBitBlt+0x252
9deffbe4 82b1cdd2 ffb83460 ff4ce3e8 00000000 win32k!SpCopyBits+0x27
9deffccc 82b04fae ffbbd550 82c552f0 ffbbd550 win32k!NtGdiBitBltInternal+0x6ab
9deffd00 8304544a c901075d 0000076b 000003e6 win32k!NtGdiBitBlt+0x2f
9deffd00 77d464f4 c901075d 0000076b 000003e6 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
002aeac0 00000000 00000000 00000000 00000000 0x77d464f4
FOLLOWUP_IP:
cdd!LeaveShadowLockCrit+1a
82cde048 5d pop ebp
SYMBOL_STACK_INDEX: 2
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: cdd!LeaveShadowLockCrit+1a
MODULE_NAME: cdd
IMAGE_NAME: cdd.dll
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bd992
STACK_COMMAND: .trap ffffffff9deff26c ; kb
FAILURE_BUCKET_ID: 0x8E_cdd!LeaveShadowLockCrit+1a
BUCKET_ID: 0x8E_cdd!LeaveShadowLockCrit+1a
Followup: MachineOwner
---------
Ich bin zwar ein Fortgeschrittener PC Nutzer. Jedoch komme ich einfach nicht dahinter, was bei mir schief läuft.
Kurze Systemangaben:
Win 7 32bit
4 gb Ram 800mhz (von dennen nur 3,3 genutzt werden)
Intel Core to Duo 2,66 Mhz
Gigabyte Geforce GTX 460 1Gb speicher
Ich entschuldige mich schonmal wenn ich im falschen Forum bin mit meinem Problem, dachte mir aber Motherboard betrifft ja eigentlich viel^^
Ich hoffe ihr könnt mir helfen.
Grüße
Dome
auf der Suche nach Lösungsansätzen bin ich durch dieses Forum gestolpert, habe jedoch keine passenden Artikel zu meinem Problem gefunden.
Kurz und knapp:
Ich bekomme seid ein paar Tagen zu unterschiedlichen Zeiten Bluescreens mit der Fehlermeldung KERNEL_MODE_EXCEPTION_NOT_HANDLED_M.
Habe mich dann mal ein bisschen schlau gemacht und ein Debugging Tool ausprobiert, das mir diesen Fehlertext ausspuckte.
Microsoft (R) Windows Debugger Version 6.4.0007.2
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\122510-15428-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\Symbols*
Du hast keine Berechtigung, den Link zu sehen, bitte Anmelden oder Registrieren
Executable search path is:
Windows Longhorn Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Kernel base = 0x83002000 PsLoadedModuleList = 0x8314a810
Debug session time: Sat Dec 25 12:47:52.918 2010 (GMT+1)
System Uptime: 0 days 2:39:08.573
Loading Kernel Symbols
...........................................................................................................................................................
Loading unloaded module list
.....
Loading User Symbols
0: kd> g
^ No runnable debuggees error in 'g'
0: kd> BugCheck
^ Operation not supported by current debuggee error in 'BugCheck'
0: 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: c0000046, The exception code that was not handled
Arg2: 830428f8, The address that the exception occurred at
Arg3: 9deff26c, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
OVERLAPPED_MODULE: srv2
EXCEPTION_CODE: (NTSTATUS) 0xc0000046 - Ein Thread versuchte, ein Mutantobjekt freizugeben, ohne Besitzer des Objekts zu sein.
FAULTING_IP:
nt!KeReleaseMutant+215
830428f8 cc int 3
TRAP_FRAME: 9deff26c -- (.trap ffffffff9deff26c)
ESP EDITED! New esp=9deff61c
ErrCode = 00000000
eax=c0000046 ebx=86757850 ecx=87d10100 edx=00000000 esi=87d10194 edi=00000000
eip=830428f8 esp=9deff2e0 ebp=9deff654 iopl=0 nv up ei ng nz na pe nc
cs=0000 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000282
nt!KeReleaseMutant+0x215:
830428f8 cc int 3
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 830426da to 830428f8
STACK_TEXT:
9deff654 830426da 87d10194 00000001 00000000 nt!KeReleaseMutant+0x215
9deff66c 82cde048 87d10194 00000000 9deff6d0 nt!KeReleaseMutex+0x14
9deff67c 82ce0043 ffb90010 9deff880 9deff720 cdd!LeaveShadowLockCrit+0x1a
9deff6d0 82ce0644 00000008 00000008 9deff8f0 cdd!CDDMULTISURFLOCK::vLockShadowW+0x24d
9deff6f0 82ce4355 ff4ce3e8 9deff88c ffb83460 cdd!CDDMULTISURFLOCK::vInit+0x18c
9deff890 82ce482f ffb83460 ff4ce3e8 00000000 cdd!DrvBitBlt+0x6a3
9deff8c4 82b18fa3 ffb83460 ff4ce3e8 9deffa70 cdd!DrvCopyBits+0x27
9deff90c 82afec34 82ce4808 9deffb9c ffb83460 win32k!OffCopyBits+0x7d
9deffbb0 82b1c580 ffb83460 ff4ce3e8 00000000 win32k!SpBitBlt+0x252
9deffbe4 82b1cdd2 ffb83460 ff4ce3e8 00000000 win32k!SpCopyBits+0x27
9deffccc 82b04fae ffbbd550 82c552f0 ffbbd550 win32k!NtGdiBitBltInternal+0x6ab
9deffd00 8304544a c901075d 0000076b 000003e6 win32k!NtGdiBitBlt+0x2f
9deffd00 77d464f4 c901075d 0000076b 000003e6 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
002aeac0 00000000 00000000 00000000 00000000 0x77d464f4
FOLLOWUP_IP:
cdd!LeaveShadowLockCrit+1a
82cde048 5d pop ebp
SYMBOL_STACK_INDEX: 2
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: cdd!LeaveShadowLockCrit+1a
MODULE_NAME: cdd
IMAGE_NAME: cdd.dll
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bd992
STACK_COMMAND: .trap ffffffff9deff26c ; kb
FAILURE_BUCKET_ID: 0x8E_cdd!LeaveShadowLockCrit+1a
BUCKET_ID: 0x8E_cdd!LeaveShadowLockCrit+1a
Followup: MachineOwner
---------
Ich bin zwar ein Fortgeschrittener PC Nutzer. Jedoch komme ich einfach nicht dahinter, was bei mir schief läuft.
Kurze Systemangaben:
Win 7 32bit
4 gb Ram 800mhz (von dennen nur 3,3 genutzt werden)
Intel Core to Duo 2,66 Mhz
Gigabyte Geforce GTX 460 1Gb speicher
Ich entschuldige mich schonmal wenn ich im falschen Forum bin mit meinem Problem, dachte mir aber Motherboard betrifft ja eigentlich viel^^
Ich hoffe ihr könnt mir helfen.
Grüße
Dome