1
Windows Vista Forum / vistaBluescreen 101 ???
« am: 21. Oktober 2008, 00:03:23 »
hi allerseits hoffe ihr könnt mir helfen!!!
habe seit ca 3-4 tagen ganz sporatische PS habe mal von Ms den debugger geladen und die dump auswerten lassen kann aber mit dem ganzen fachchinesisch (englisch)absolut nichts anfangen hier der log
Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\Mini102008-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\windows\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.18145.x86fre.vistasp1_gdr.080917-1612
Kernel base = 0x81a14000 PsLoadedModuleList = 0x81b2bc70
Debug session time: Mon Oct 20 22:00:09.980 2008 (GMT+2)
System Uptime: 0 days 11:54:30.136
Loading Kernel Symbols
...
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 101, {61, 0, 803d1120, 1}
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: 00000061, Clock interrupt time out interval in nominal clock ticks.
Arg2: 00000000, 0.
Arg3: 803d1120, The PRCB address of the hung processor.
Arg4: 00000001, 0.
Debugging Details:
------------------
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x101
PROCESS_NAME: BF2.exe
CURRENT_IRQL: 1c
LAST_CONTROL_TRANSFER: from 81acc271 to 81ae10e3
STACK_TEXT:
a3a2cd20 81acc271 00000101 00000061 00000000 nt!KeBugCheckEx+0x1e
a3a2cd54 81acbf7d 81a6ba00 000000d1 0012f99c nt!KeUpdateRunTime+0xd5
a3a2cd54 725860dc 81a6ba00 000000d1 0012f99c nt!KeUpdateSystemTime+0xed
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012f99c 00000000 00000000 00000000 00000000 0x725860dc
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: 0x101_ANALYSIS_INCONCLUSIVE
BUCKET_ID: 0x101_ANALYSIS_INCONCLUSIVE
Followup: MachineOwner
--------
dazu muss ich sagen das ich vista ultimate draufhabe mit dem ich mich aber bei Microsoft nicht registrieren kann (ihr key ist ungültig) bla bla bla
habe aber den ORIG.-key von einem ausgeschlachteten rechner wo das ORIG-etikett mit hologramm drann war,so wie ich es für die homepremium habe.
denn erst nachdem ich ultimate installiert habe habe ich dieses problem??
Mfg private
habe seit ca 3-4 tagen ganz sporatische PS habe mal von Ms den debugger geladen und die dump auswerten lassen kann aber mit dem ganzen fachchinesisch (englisch)absolut nichts anfangen hier der log
Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\Mini102008-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\windows\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.18145.x86fre.vistasp1_gdr.080917-1612
Kernel base = 0x81a14000 PsLoadedModuleList = 0x81b2bc70
Debug session time: Mon Oct 20 22:00:09.980 2008 (GMT+2)
System Uptime: 0 days 11:54:30.136
Loading Kernel Symbols
...
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 101, {61, 0, 803d1120, 1}
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: 00000061, Clock interrupt time out interval in nominal clock ticks.
Arg2: 00000000, 0.
Arg3: 803d1120, The PRCB address of the hung processor.
Arg4: 00000001, 0.
Debugging Details:
------------------
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x101
PROCESS_NAME: BF2.exe
CURRENT_IRQL: 1c
LAST_CONTROL_TRANSFER: from 81acc271 to 81ae10e3
STACK_TEXT:
a3a2cd20 81acc271 00000101 00000061 00000000 nt!KeBugCheckEx+0x1e
a3a2cd54 81acbf7d 81a6ba00 000000d1 0012f99c nt!KeUpdateRunTime+0xd5
a3a2cd54 725860dc 81a6ba00 000000d1 0012f99c nt!KeUpdateSystemTime+0xed
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012f99c 00000000 00000000 00000000 00000000 0x725860dc
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: 0x101_ANALYSIS_INCONCLUSIVE
BUCKET_ID: 0x101_ANALYSIS_INCONCLUSIVE
Followup: MachineOwner
--------
dazu muss ich sagen das ich vista ultimate draufhabe mit dem ich mich aber bei Microsoft nicht registrieren kann (ihr key ist ungültig) bla bla bla
habe aber den ORIG.-key von einem ausgeschlachteten rechner wo das ORIG-etikett mit hologramm drann war,so wie ich es für die homepremium habe.
denn erst nachdem ich ultimate installiert habe habe ich dieses problem??
Mfg private