Has anyone seen a BSOD like this?

roaf85

2[H]4U
Joined
Jan 8, 2005
Messages
2,766
I figured to post here in OC forums because I believe my BSOD is OC related.

Computer is prime stable, memtest the works. 2.66 at 3.2 on the specs on the sig. No voltage increase.

I have never gotten a BSOD like this even after I did. Basically I just went to get some food, had the game at the Old Republic splash screen and come back to see a BSOD that is related to this:

Of course I threw it through a mini dump finder.


Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03049000 PsLoadedModuleList = 0xfffff800`0328e670
Debug session time: Sat Mar 10 15:11:04.498 2012 (UTC - 5:00)
System Uptime: 0 days 0:26:54.121
*******************************************************************************
* *
* 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: 0000000000000000, Machine Check Exception
Arg2: fffffa80055c4028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b620000e, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000080a01, 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: plugin-contain

CURRENT_IRQL: f

STACK_TEXT:
fffff880`02fdba58 fffff800`03012a3b : 00000000`00000124 00000000`00000000 fffffa80`055c4028 00000000`b620000e : nt!KeBugCheckEx
fffff880`02fdba60 fffff800`031d6513 : 00000000`00000001 fffffa80`055aaa60 00000000`00000000 fffffa80`055aaab0 : hal!HalBugCheckSystem+0x1e3
fffff880`02fdbaa0 fffff800`03012700 : 00000000`00000728 fffffa80`055aaa60 fffff880`02fdbe30 fffff880`02fdbe00 : nt!WheaReportHwError+0x263
fffff880`02fdbb00 fffff800`03012052 : fffffa80`055aaa60 fffff880`02fdbe30 fffffa80`055aaa60 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`02fdbc50 fffff800`03011f0d : 00000000`00000004 00000000`00000001 fffff880`02fdbeb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`02fdbc90 fffff800`03005e88 : 00000000`00000040 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`02fdbcc0 fffff800`030c452c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`02fdbcf0 fffff800`030c4393 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`02fdbe30 00000000`67b9f843 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`0048bb74 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x67b9f843


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_BUS

BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_BUS

Followup: MachineOwner
---------
 

Falkentyne

[H]ard|Gawd
Joined
Jul 19, 2000
Messages
1,634
It's just a 0x124 error.
CPU related.
Probably had a different string due to what was going on in the system.
0x124's and 0x101's are always related to something on the processor.
 

roaf85

2[H]4U
Joined
Jan 8, 2005
Messages
2,766
It's just a 0x124 error.
CPU related.
Probably had a different string due to what was going on in the system.
0x124's and 0x101's are always related to something on the processor.
OC or application related?
 

roaf85

2[H]4U
Joined
Jan 8, 2005
Messages
2,766
Well it did it again. It must be system/board related.

I backed down to stock settings and put the ram at 1333 9-9-9-24.

I was running for 2 years at 3.2 400 fsb and ram at 533 (1066) 6-6-6-16. I tried seeing if it was the ram on a 7-7-7-18 timing, but it still crashed with the same BSOD. The BSODs are random.

Outside of the mainboard just being defective it runs Prime95 just fine and memtest passes with flashing colors. So it leads me to believe it is the process or board.

That being said I would still like to shoot for the 3.0 ghz at 375, but I am not sure the ratio to 533 or 667 will work out?

Suggestions?
 

Pitbully

[H]ard|Gawd
Joined
Nov 29, 2011
Messages
1,155
0x124 is usually your CPU not getting enough Vcore, (voltage) while overclocking.
 

roaf85

2[H]4U
Joined
Jan 8, 2005
Messages
2,766
0x124 is usually your CPU not getting enough Vcore, (voltage) while overclocking.
It has ran at 1.2 (stock for 2 years).

Assuming it isn't the power supply which I do not believe it is, am I left to assume the board. I want to shy away from pumping anything to the vcore, because I don't legally own my processor (no I didn't steal it).
 

roaf85

2[H]4U
Joined
Jan 8, 2005
Messages
2,766
Err I should have been more clear, but stock I mean 1.2v set to auto. Not sure what the board was measuring for the voltage.
 
Top