Liebe PC-Freaks,
da sich die Bluescreens auf meinem PC in letzter Zeit wieder häufen, habe ich mich nun mal mit dem "Debugging-Tool for Windows" befasst und hoffe, dass jemand von Euch aus den unterstehenden Infos schlau wird.
LG Ricardo!
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Symbols\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
Symbol search path is: SRV*C:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Machine Name:
Kernel base = 0xfffff800`04404000 PsLoadedModuleList = 0xfffff800`04648670
Debug session time: Thu Jul 12 08:13:04.503 2012 (GMT+2)
System Uptime: 0 days 10:06:34.705
Page a0000b7 too large to be in the dump file.
Loading Kernel Symbols
...............................................Missing image name, possible paged-out or corrupt data.
.Image path too long, possible corrupt data.
.Image path too long, possible corrupt data.
.*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Unable to add module at 00000000`00000000
Unable to read KLDR_DATA_TABLE_ENTRY at 00000000`00000000 - NTSTATUS 0xC0000147
WARNING: .reload failed, module list may be incomplete
Page 27 not present in the dump file. Type ".hh dbgerr004" for details
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {44cf004, 2, 8, 44cf004}
Missing image name, possible paged-out or corrupt data.
Image path too long, possible corrupt data.
Image path too long, possible corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 00000000`00000000 - NTSTATUS 0xC0000147
WARNING: .reload failed, module list may be incomplete
Missing image name, possible paged-out or corrupt data.
Image path too long, possible corrupt data.
Image path too long, possible corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 00000000`00000000 - NTSTATUS 0xC0000147
WARNING: .reload failed, module list may be incomplete
Probably caused by : ntkrnlmp.exe ( nt!PoIdle+52a )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000000044cf004, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: 00000000044cf004, address which referenced memory
Debugging Details:
------------------
Missing image name, possible paged-out or corrupt data.
Image path too long, possible corrupt data.
Image path too long, possible corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 00000000`00000000 - NTSTATUS 0xC0000147
WARNING: .reload failed, module list may be incomplete
Missing image name, possible paged-out or corrupt data.
Image path too long, possible corrupt data.
Image path too long, possible corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 00000000`00000000 - NTSTATUS 0xC0000147
WARNING: .reload failed, module list may be incomplete
READ_ADDRESS: 00000000044cf004
CURRENT_IRQL: 0
FAULTING_IP:
+0
00000000`044cf004 ?? ???
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
LAST_CONTROL_TRANSFER: from fffff8000448bce9 to fffff8800437f7f2
FAILED_INSTRUCTION_ADDRESS:
+0
00000000`044cf004 ?? ???
STACK_TEXT:
fffff800`00b9cc98 fffff800`0448bce9 : 00000000`002ce770 fffffa80`086e28a8 fffff800`04603cc0 00000000`00000001 : 0xfffff880`0437f7f2
fffff800`00b9cca0 fffff800`0447ae9c : fffff800`045f5e80 fffff800`00000000 00000000`00000000 fffffa80`0863b210 : nt!PoIdle+0x52a
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x2c
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!PoIdle+52a
fffff800`0448bce9 0fba2557e617000f bt dword ptr [nt!PerfGlobalGroupMask+0x8 (fffff800`0460a348)],0Fh
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!PoIdle+52a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4fa390f3
FAILURE_BUCKET_ID: X64_0xD1_CODE_AV_BAD_IP_nt!PoIdle+52a
BUCKET_ID: X64_0xD1_CODE_AV_BAD_IP_nt!PoIdle+52a
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000000044cf004, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: 00000000044cf004, address which referenced memory
Debugging Details:
------------------
Missing image name, possible paged-out or corrupt data.
Image path too long, possible corrupt data.
Image path too long, possible corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 00000000`00000000 - NTSTATUS 0xC0000147
WARNING: .reload failed, module list may be incomplete
Missing image name, possible paged-out or corrupt data.
Image path too long, possible corrupt data.
Image path too long, possible corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 00000000`00000000 - NTSTATUS 0xC0000147
WARNING: .reload failed, module list may be incomplete
READ_ADDRESS: 00000000044cf004
CURRENT_IRQL: 0
FAULTING_IP:
+0
00000000`044cf004 ?? ???
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
LAST_CONTROL_TRANSFER: from fffff8000448bce9 to fffff8800437f7f2
FAILED_INSTRUCTION_ADDRESS:
+0
00000000`044cf004 ?? ???
STACK_TEXT:
fffff800`00b9cc98 fffff800`0448bce9 : 00000000`002ce770 fffffa80`086e28a8 fffff800`04603cc0 00000000`00000001 : 0xfffff880`0437f7f2
fffff800`00b9cca0 fffff800`0447ae9c : fffff800`045f5e80 fffff800`00000000 00000000`00000000 fffffa80`0863b210 : nt!PoIdle+0x52a
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x2c
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!PoIdle+52a
fffff800`0448bce9 0fba2557e617000f bt dword ptr [nt!PerfGlobalGroupMask+0x8 (fffff800`0460a348)],0Fh
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!PoIdle+52a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4fa390f3
FAILURE_BUCKET_ID: X64_0xD1_CODE_AV_BAD_IP_nt!PoIdle+52a
BUCKET_ID: X64_0xD1_CODE_AV_BAD_IP_nt!PoIdle+52a
Followup: MachineOwner
---------
riki1979 Gast |
