hallo,
ich habe mir letztens einen neuen pc gekauft.
ich bekomme immer bluescreens meistens wenn ich age of conan spiele.
dann habe ich mir mal dieses debugging tool runtergeladen und gestartet nur irgentwie werde ich daraus nicht so ganz schlau.
kann mir vieleicht einer sagen was das heisst?
vieleicht habe ich ja auch etwas falsch eingestellt.
mfg René
ich habe mir letztens einen neuen pc gekauft.
ich bekomme immer bluescreens meistens wenn ich age of conan spiele.
dann habe ich mir mal dieses debugging tool runtergeladen und gestartet nur irgentwie werde ich daraus nicht so ganz schlau.
kann mir vieleicht einer sagen was das heisst?
Microsoft (R) Windows Debugger Version 6.9.0003.113 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\Mini061908-03.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*c:\cache*Symbol information
Executable search path is:
Windows Vista Kernel Version 6000 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6000.16584.amd64fre.vista_gdr.071023-1545
Kernel base = 0xfffff800`01c00000 PsLoadedModuleList = 0xfffff800`01d9af70
Debug session time: Thu Jun 19 14:07:45.142 2008 (GMT+2)
System Uptime: 0 days 0:45:33.062
Loading Kernel Symbols
................................................................................................................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 101, {30, 0, fffff98000a8e180, 2}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000030, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff98000a8e180, The PRCB address of the hung processor.
Arg4: 0000000000000002, 0.
Debugging Details:
------------------
BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT
CUSTOMER_CRASH_COUNT: 3
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: Idle
CURRENT_IRQL: d
STACK_TEXT:
fffff800`03e49698 fffff800`01c36739 : 00000000`00000101 00000000`00000030 00000000`00000000 fffff980`00a8e180 : nt!KeBugCheckEx
fffff800`03e496a0 fffff800`01c50bba : fffff6fc`c025c940 00000000`00000000 00000000`00000002 fffff800`03e497d0 : nt! ?? ::FNODOBFM::`string'+0x41d4
fffff800`03e496f0 fffff800`020e922f : fffff980`4b928f60 fffff800`02107320 00000000`00000002 00000002`bf19026a : nt!KeUpdateSystemTime+0xea
fffff800`03e49720 fffff800`01c4f3dd : fffff980`4b928f60 fffff800`02107320 fffff800`03e4a000 fffffa80`07ef32d0 : hal!HalpRtcClockInterrupt+0x127
fffff800`03e49750 fffff800`01c993b5 : fffff800`00000000 fffff980`4b928f60 fffff800`03e49950 ffffffff`ffffffff : nt!KiInterruptDispatchNoLock+0x14d
fffff800`03e498e0 fffff800`01cea9b4 : fffff980`4b928f60 fffff800`01cea8c1 00000000`00000001 fffff800`03e49950 : nt!KeFlushSingleTb+0x75
fffff800`03e49910 fffff800`01d3c1cc : 00000000`000c9ac0 00000000`00000000 00000000`206c6148 00000000`00000000 : nt!MmFreeSpecialPool+0x354
fffff800`03e499b0 fffff800`020df6ef : fffff980`4b928f60 00000000`00000ff0 00000000`00000008 fffffa80`08231b80 : nt!ExDeferredFreePool+0x701
fffff800`03e49a70 fffff800`0201e6e1 : 00000000`00000001 fffffa80`06cef730 fffffa80`06cf6630 fffffa80`06b06050 : hal!HalPutScatterGatherList+0x10f
fffff800`03e49ad0 fffff980`0a1d33bf : fffffa80`06b061a0 fffffa80`06b06050 fffff800`0201e5d0 fffff980`6c930c30 : nt!VfPutScatterGatherList+0x111
fffff800`03e49b20 fffff980`0a1d3d98 : fffff980`31466d64 fffff980`0fe80dc0 fffff800`32466d64 fffffa80`00000000 : USBPORT!USBPORT_Core_iCompleteDoneTransfer+0x577
fffff800`03e49c00 fffff980`0a1d1276 : fffffa80`39585043 fffffa80`06b061a0 fffffa80`06b07080 fffffa80`06b061a0 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x514
fffff800`03e49c70 fffff980`0a1be0cf : fffffa80`31636f49 fffffa80`06b07080 00000000`00000002 fffffa80`06b061a0 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0x13a
fffff800`03e49cc0 fffff800`01c50512 : 000005f5`42f93cac 00000000`34776478 00000000`00000000 fffffa80`06b06050 : USBPORT!USBPORT_Xdpc_Worker+0x26f
fffff800`03e49d10 fffff800`01c4fc2f : fffff980`0a1bde60 fffff800`01d4a980 00000000`00000001 fffff800`01d4fc80 : nt!KiRetireDpcList+0x155
fffff800`03e49d80 fffff800`01e00724 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5f
fffff800`03e49db0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemStartup+0x1d4
STACK_COMMAND: kb
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_ANALYSIS_INCONCLUSIVE
BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_ANALYSIS_INCONCLUSIVE
Followup: MachineOwner
---------
0: kd> lmvm Unknown_Module
start end module name
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\Mini061908-03.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*c:\cache*Symbol information
Executable search path is:
Windows Vista Kernel Version 6000 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6000.16584.amd64fre.vista_gdr.071023-1545
Kernel base = 0xfffff800`01c00000 PsLoadedModuleList = 0xfffff800`01d9af70
Debug session time: Thu Jun 19 14:07:45.142 2008 (GMT+2)
System Uptime: 0 days 0:45:33.062
Loading Kernel Symbols
................................................................................................................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 101, {30, 0, fffff98000a8e180, 2}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000030, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff98000a8e180, The PRCB address of the hung processor.
Arg4: 0000000000000002, 0.
Debugging Details:
------------------
BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT
CUSTOMER_CRASH_COUNT: 3
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: Idle
CURRENT_IRQL: d
STACK_TEXT:
fffff800`03e49698 fffff800`01c36739 : 00000000`00000101 00000000`00000030 00000000`00000000 fffff980`00a8e180 : nt!KeBugCheckEx
fffff800`03e496a0 fffff800`01c50bba : fffff6fc`c025c940 00000000`00000000 00000000`00000002 fffff800`03e497d0 : nt! ?? ::FNODOBFM::`string'+0x41d4
fffff800`03e496f0 fffff800`020e922f : fffff980`4b928f60 fffff800`02107320 00000000`00000002 00000002`bf19026a : nt!KeUpdateSystemTime+0xea
fffff800`03e49720 fffff800`01c4f3dd : fffff980`4b928f60 fffff800`02107320 fffff800`03e4a000 fffffa80`07ef32d0 : hal!HalpRtcClockInterrupt+0x127
fffff800`03e49750 fffff800`01c993b5 : fffff800`00000000 fffff980`4b928f60 fffff800`03e49950 ffffffff`ffffffff : nt!KiInterruptDispatchNoLock+0x14d
fffff800`03e498e0 fffff800`01cea9b4 : fffff980`4b928f60 fffff800`01cea8c1 00000000`00000001 fffff800`03e49950 : nt!KeFlushSingleTb+0x75
fffff800`03e49910 fffff800`01d3c1cc : 00000000`000c9ac0 00000000`00000000 00000000`206c6148 00000000`00000000 : nt!MmFreeSpecialPool+0x354
fffff800`03e499b0 fffff800`020df6ef : fffff980`4b928f60 00000000`00000ff0 00000000`00000008 fffffa80`08231b80 : nt!ExDeferredFreePool+0x701
fffff800`03e49a70 fffff800`0201e6e1 : 00000000`00000001 fffffa80`06cef730 fffffa80`06cf6630 fffffa80`06b06050 : hal!HalPutScatterGatherList+0x10f
fffff800`03e49ad0 fffff980`0a1d33bf : fffffa80`06b061a0 fffffa80`06b06050 fffff800`0201e5d0 fffff980`6c930c30 : nt!VfPutScatterGatherList+0x111
fffff800`03e49b20 fffff980`0a1d3d98 : fffff980`31466d64 fffff980`0fe80dc0 fffff800`32466d64 fffffa80`00000000 : USBPORT!USBPORT_Core_iCompleteDoneTransfer+0x577
fffff800`03e49c00 fffff980`0a1d1276 : fffffa80`39585043 fffffa80`06b061a0 fffffa80`06b07080 fffffa80`06b061a0 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x514
fffff800`03e49c70 fffff980`0a1be0cf : fffffa80`31636f49 fffffa80`06b07080 00000000`00000002 fffffa80`06b061a0 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0x13a
fffff800`03e49cc0 fffff800`01c50512 : 000005f5`42f93cac 00000000`34776478 00000000`00000000 fffffa80`06b06050 : USBPORT!USBPORT_Xdpc_Worker+0x26f
fffff800`03e49d10 fffff800`01c4fc2f : fffff980`0a1bde60 fffff800`01d4a980 00000000`00000001 fffff800`01d4fc80 : nt!KiRetireDpcList+0x155
fffff800`03e49d80 fffff800`01e00724 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5f
fffff800`03e49db0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemStartup+0x1d4
STACK_COMMAND: kb
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_ANALYSIS_INCONCLUSIVE
BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_ANALYSIS_INCONCLUSIVE
Followup: MachineOwner
---------
0: kd> lmvm Unknown_Module
start end module name
vieleicht habe ich ja auch etwas falsch eingestellt.
mfg René
Zuletzt bearbeitet von einem Moderator: