Chip4000
2009-09-10, 21:19:51
Hallo!
Habe gerade Bionic Commando gezockt, da bekam ich dann mitten beim Spielen einen Bluescreen.
Hab das Minidump-File mal ausgewertet.
Hoffe hier kann mir mal einer helfen.
Prime und memtest zeigen keine Fehler an.
Microsoft (R) Windows Debugger Version 6.4.0007.2
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\Mini091009-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 Longhorn Kernel Version 6002 (Service Pack 2) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18005.x86fre.lh_sp2rtm.090410-1830
Kernel base = 0x81e08000 PsLoadedModuleList = 0x81f1fc70
Debug session time: Thu Sep 10 20:44:31.407 2009 (GMT+2)
System Uptime: 0 days 2:30:06.069
Loading Kernel Symbols
................................................................................ ...............................................................
Loading unloaded module list
........
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, 84fc53f0, b6004000, 75000135}
Probably caused by : ntkrpamp.exe ( nt!WheaReportHwError+1d0 )
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Unknown bugcheck code (124)
Unknown bugcheck description
Arguments:
Arg1: 00000000
Arg2: 84fc53f0
Arg3: b6004000
Arg4: 75000135
Debugging Details:
------------------
OVERLAPPED_MODULE: umbus
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x124
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 821c79dd to 81ed5b0d
STACK_TEXT:
8b94f488 821c79dd 00000124 00000000 84fc53f0 nt!KeBugCheckEx+0x1e
8b94f4dc 81ec9520 84fc53f0 85716698 85716698 hal!HalBugCheckSystem+0xe1
8b94f508 821c78f1 85716698 821dafb4 8b94f544 nt!WheaReportHwError+0x1d0
8b94f518 821c7fed 00000003 85716698 00000000 hal!HalpReportMachineCheck+0x31
8b94f544 821c399f 8b94a130 00000000 00000000 hal!HalpMcaExceptionHandler+0x115
FOLLOWUP_IP:
nt!WheaReportHwError+1d0
81ec9520 eb50 jmp nt!WheaReportHwError+0x222 (81ec9572)
SYMBOL_STACK_INDEX: 2
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: nt!WheaReportHwError+1d0
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 49e0199e
STACK_COMMAND: kb
FAILURE_BUCKET_ID: 0x124_nt!WheaReportHwError+1d0
BUCKET_ID: 0x124_nt!WheaReportHwError+1d0
Followup: MachineOwner
---------
Habe gerade Bionic Commando gezockt, da bekam ich dann mitten beim Spielen einen Bluescreen.
Hab das Minidump-File mal ausgewertet.
Hoffe hier kann mir mal einer helfen.
Prime und memtest zeigen keine Fehler an.
Microsoft (R) Windows Debugger Version 6.4.0007.2
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\Mini091009-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 Longhorn Kernel Version 6002 (Service Pack 2) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18005.x86fre.lh_sp2rtm.090410-1830
Kernel base = 0x81e08000 PsLoadedModuleList = 0x81f1fc70
Debug session time: Thu Sep 10 20:44:31.407 2009 (GMT+2)
System Uptime: 0 days 2:30:06.069
Loading Kernel Symbols
................................................................................ ...............................................................
Loading unloaded module list
........
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, 84fc53f0, b6004000, 75000135}
Probably caused by : ntkrpamp.exe ( nt!WheaReportHwError+1d0 )
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Unknown bugcheck code (124)
Unknown bugcheck description
Arguments:
Arg1: 00000000
Arg2: 84fc53f0
Arg3: b6004000
Arg4: 75000135
Debugging Details:
------------------
OVERLAPPED_MODULE: umbus
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x124
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 821c79dd to 81ed5b0d
STACK_TEXT:
8b94f488 821c79dd 00000124 00000000 84fc53f0 nt!KeBugCheckEx+0x1e
8b94f4dc 81ec9520 84fc53f0 85716698 85716698 hal!HalBugCheckSystem+0xe1
8b94f508 821c78f1 85716698 821dafb4 8b94f544 nt!WheaReportHwError+0x1d0
8b94f518 821c7fed 00000003 85716698 00000000 hal!HalpReportMachineCheck+0x31
8b94f544 821c399f 8b94a130 00000000 00000000 hal!HalpMcaExceptionHandler+0x115
FOLLOWUP_IP:
nt!WheaReportHwError+1d0
81ec9520 eb50 jmp nt!WheaReportHwError+0x222 (81ec9572)
SYMBOL_STACK_INDEX: 2
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: nt!WheaReportHwError+1d0
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 49e0199e
STACK_COMMAND: kb
FAILURE_BUCKET_ID: 0x124_nt!WheaReportHwError+1d0
BUCKET_ID: 0x124_nt!WheaReportHwError+1d0
Followup: MachineOwner
---------