New
#1
Overclocking Stress Test BSOD?
Hi all, can someone help me "decode" this BSOD I got while stress testing under Orthos? Seems my CPU won't let me overclock to 3.2-3.4 even though people have got higher FSBs than I did. Hoping this BSOD will tell me whats the problem...thanks, sorry for the short post, I'll reply when someone answers.
Results from WinDbg:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [E:\030811-10732-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 x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16695.x86fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0x83405000 PsLoadedModuleList = 0x83544570
Debug session time: Tue Mar 8 15:26:07.430 2011 (UTC - 8:00)
System Uptime: 0 days 0:07:28.147
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
.....
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 00000000, Machine Check Exception
Arg2: 86b6c024, Address of the WHEA_ERROR_RECORD structure.
Arg3: b2000040, High order 32-bits of the MCi_STATUS value.
Arg4: 00000800, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
------------------
BUGCHECK_STR: 0x124_GenuineIntel
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 1f
STACK_TEXT:
83520d0c 83814f3f 00000124 00000000 86b6c024 nt!KeBugCheckEx+0x1e
83520d48 834c8084 86bc2a29 86b6c024 8345a8b0 hal!HalBugCheckSystem+0xab
83520d78 838151f1 86b6cea8 83822e40 00000000 nt!WheaReportHwError+0x230
83520e8c 838152e3 86b6cea8 86b6cef8 00000002 hal!HalpMcaReportError+0x3b
83520eb0 838153ff 00000000 86b6cef8 00000000 hal!HalpMceHandler+0x8b
83520ed0 83815548 00000000 86b6cea8 83520ff0 hal!HalpMceHandlerWithRendezvous+0x4b
83520ee0 8380b5f5 00000000 00000000 00000000 hal!HalpHandleMachineCheck+0x34
83520ff0 83808261 0000001b 801c9000 00000000 hal!HalpMcaExceptionHandler+0x87
83520ff0 00000000 0000001b 801c9000 00000000 hal!HalpMcaExceptionHandlerWrapper+0x89
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: hardware
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_BUS
BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_BUS
Followup: MachineOwner
---------
0: kd> lmvm hardware
start end module name
Quote