bsod in BFBC2 caused by OC?

topher

topher

topher

Soldato
Joined
3 Jan 2003
Posts
3,728
not sure if this being caused by my OC
ip35
e2160 @ 2.8ghz temps under load 55 - 60c

only seems to crash in bfbc2, stable running of games and orthos for 5hrs

bug says possible hardware error, but then says vista driver fault!

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: fffffa8004af8038, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b2000040, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000800, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


BUGCHECK_STR: 0x124_GenuineIntel

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: f

STACK_TEXT:
fffff880`009ee9d8 fffff800`02c1b903 : 00000000`00000124 00000000`00000000 fffffa80`04af8038 00000000`b2000040 : nt!KeBugCheckEx
fffff880`009ee9e0 fffff800`02dd8593 : 00000000`00000001 fffffa80`049e58f0 00000000`00000000 fffffa80`049e5940 : hal!HalBugCheckSystem+0x1e3
fffff880`009eea20 fffff800`02c1b5c8 : 00000000`00000728 fffffa80`049e58f0 fffff880`009eedb0 fffff880`009eed00 : nt!WheaReportHwError+0x263
fffff880`009eea80 fffff800`02c1af1a : fffffa80`049e58f0 fffff880`009eedb0 fffffa80`049e58f0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`009eebd0 fffff800`02c1add5 : 00000000`00000002 00000000`00000001 fffff880`009eee30 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`009eec10 fffff800`02c0ee88 : 00000000`00000000 fffff880`009e6180 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`009eec40 fffff800`02cc0fec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`009eec70 fffff800`02cc0e53 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`009eedb0 fffff880`03b9c9c2 : fffff800`02cd024a 00000000`002aea67 fffffa80`05216818 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`02f1bc98 fffff800`02cd024a : 00000000`002aea67 fffffa80`05216818 00000000`00000000 00000000`00000000 : intelppm!C1Halt+0x2
fffff880`02f1bca0 fffff800`02ccaebc : fffff880`009e6180 fffff880`00000000 00000000`00000000 fffff880`00f68b1c : nt!PoIdle+0x53a
fffff880`02f1bd80 00000000`00000000 : fffff880`02f1c000 fffff880`02f16000 fffff880`02f1bd40 00000000`00000000 : nt!KiIdleLoop+0x2c


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
 
Assuming your graphics/chipset drivers are up to date, BSOD 124 usually points to lack of memory controller volts.

Try upping it a notch or lower your clock slightly keeping same volts and report back.

You couls also check your RAM, are you running within spec? Correct divider, latencies etc?
 
Last edited:
vcore is set to 1.35v but according to cpuz it between 1.18 and 1.2v

dram freqL 368Mhz
FSBLDram 4:5
latency etc is as specified on kingstons website
 
You must log in or register to reply here.
Back
Top Bottom