Daran beteiligt ist aber fast immer ntkrnlmp.exe als "IMAGE_NAME" und "VISTA_DRIVER_FAULT" als default bucket it.
Fakten:
=> Seit Wochen keine neuen Treiber installiert
=> Nur 2 Ontrack Softwares installiert die eine Zeit alt sind und Dynamic Drive Overlay auf einer Laptopfestplatte einrichten sollten (beide deinstalliert mittlerweile)
=> Nach dem Ausführen der einen Ontrack Software kam SOFORT ein Blue Screen (der erste). Seitdem sind sie da. Kann das Zufall gewesen sein?
Hat irgendejemande eine Idee was das Problem ist?
Anbei erstmal das gesamte ausgewertete Crash Dump:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\112309-19687-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c17000 PsLoadedModuleList = 0xfffff800`02e54e50
Debug session time: Mon Nov 23 14:56:09.083 2009 (GMT+1)
System Uptime: 0 days 4:57:06.956
Loading Kernel Symbols
..................................................
.............
..................................................
..............
................................
Loading User Symbols
Loading unloaded module list
.....
**************************************************
*****************************
* *
* Bugcheck Analysis *
* *
**************************************************
*****************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000046, fffff80002cb77f8, fffffa800bce3c02, fffffa800bce3c20}
Probably caused by : ntkrnlmp.exe ( nt!RtlRaiseStatus+18 )
Followup: MachineOwner
---------
1: kd> !analyze -v
**************************************************
*****************************
* *
* Bugcheck Analysis *
* *
**************************************************
*****************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: ffffffffc0000046, The exception code that was not handled
Arg2: fffff80002cb77f8, The address that the exception occurred at
Arg3: fffffa800bce3c02, Parameter 0 of the exception
Arg4: fffffa800bce3c20, Parameter 1 of the exception
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000046 - An attempt to release a mutant object was made by a thread that was not the owner of the mutant object.
FAULTING_IP:
nt!RtlRaiseStatus+18
fffff800`02cb77f8 488b8424b8010000 mov rax,qword ptr [rsp+1B8h]
EXCEPTION_PARAMETER1: fffffa800bce3c02
EXCEPTION_PARAMETER2: fffffa800bce3c20
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x1E
PROCESS_NAME: System
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff80002cc8a17 to fffff80002c88f00
STACK_TEXT:
fffff880`0331a318 fffff800`02cc8a17 : 00000000`0000001e ffffffff`c0000046 fffff800`02cb77f8 fffffa80`0bce3c02 : nt!KeBugCheckEx
fffff880`0331a320 fffff800`02d8b3d9 : fffff880`0331adf0 fffff880`0331adf0 fffff880`0331ac30 fffff880`0331ae90 : nt! ? ::FNODOBFM::`string'+0x460da
fffff880`0331a9c0 fffff800`02c8abfb : fffff880`0331adf0 fffff880`009f1f40 00000000`00000001 fffff880`00d7178e : nt!KiRaiseException+0x1b9
fffff880`0331aaf0 fffff800`02c88153 : 00000000`00000000 fffff880`00d96ab4 fffffa80`07fdac50 fffffa80`08054db0 : nt!NtRaiseException+0x7b
fffff880`0331ac30 fffff800`02cb77f8 : fffff880`0331adf0 fffff880`0331ae90 fffffa80`00000001 fffff880`0575715a : nt!KiSystemServiceCopyEnd+0x13
fffff880`0331add0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!RtlRaiseStatus+0x18
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!RtlRaiseStatus+18
fffff800`02cb77f8 488b8424b8010000 mov rax,qword ptr [rsp+1B8h]
SYMBOL_STACK_INDEX: 5
SYMBOL_NAME: nt!RtlRaiseStatus+18
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600
FAILURE_BUCKET_ID: X64_0x1E_nt!RtlRaiseStatus+18
BUCKET_ID: X64_0x1E_nt!RtlRaiseStatus+18
Followup: MachineOwner
---------

Hilfe
Neues Thema
Antworten

Nach oben



