Jump to content

Getting BSOD After 2 years of overlclocking


Luke08

Recommended Posts

Hello,

 

I built my current system about 2 years ago. I'm not all that familiar with overclocking but did some reading up at the time and built it. I have been mildly overclocking the CPU since I built it and within the last few weeks I started getting BSOD Hardware Failures while playing games. I backed off the OC on the CPU and things are stable again. All settings below are what I had while OC, I only changed the CPU clock to back it off.

 

Seeking some help on a few questions:

1. Is it common that over time OC settings need to be adjusted (just curious)

2. Can any of the more experienced members on the boards offer any suggestions on what to tweak (DRAM,SB,NB, ect)

3. I remember there being a very good guide for overclocking quadcores stickied on the boards and I can't find it - is it still around?

 

System build and details from bios:

 

Q6600 G0 - VID is 1.3250V + TRUE heatsink

EVGA 512-P3-N801-AR GeForce 8800 GT 512MB 256-bit GDDR3 PCI Express 2.0 x16 HDCP Ready SLI Support Video Card - Retail

DFI LANPARTY DK P35-T2RS LGA 775 Intel P35 ATX Intel Motherboard - Retail

Antec P182 Gun Metal Black 0.8mm cold rolled steel ATX Mid Tower Computer Case - Retail

OCZ StealthXStream OCZ600SXS 600W ATX12V / EPS12V SLI Ready Active PFC Power Supply - Retail

Mushkin Enhanced Blackline 4GB (2 x 2GB) 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400)

 

Health View:

CPU Voltage 1.29V

DRAM 2.01V

NBcore 1.34V

CPU VTT 1.21V

ATX -3.3V 3.23V

ATX -12V 12.22V

5V Standby 5.08V

Battery Voltage 3.29V

CPU Core 32C

PWM Area 41C

Chipset 34C

 

CPU currently: 9x 266

CPU when OC: 9x 333

DRAM Speed: 266/800

PCIE Clock: 100Mhz

 

DRAM Timing:

Enhance Data Transmitting: Auto

Enhance Adressing: Auto

T2 Dispatch: Auto

tCL 4

tRCD 4

tRP 4

tRAS 12

 

Voltages:

CPU VID Special Add: +12.5mV

DRAM voltage control: 2.000V

SB 2.05 voltage: 1.70V

SB Core/CPU PLL voltage: 1.55V

NB Core voltage: 1.33V

CPU VTT voltage: 1.200V

Clockgen voltage control: 3.45V

CPU GTL 0/2 Ref volt 0.67X

CPU GTL 1/3 Ref volt 0.67X

Nort Bridge GTL Ref volt: 0.67X

 

Thanks

Share this post


Link to post
Share on other sites

I haven't heard of overclocks getting "old", but perhaps capactitatiors and such get worn out after a period of time... Maybe you need to up the voltages a bit.

This is very possible.

 

As caps age, their leakage increases.

 

This not only lowers stability, but increases power usage. You probably need a notch more vcore or to drop the OC a little to compensate.

Share this post


Link to post
Share on other sites

Below is the analysis of one of the dumps generated during the BSODs I was getting. I've looked through them all and they are all the same with the exception of PROCESS_NAME which varies depending on what I was doing at the time, usually it's the *.exe of the game I was playing at the time.

 

 

*******************************************************************************

* *

* 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: fffffa8004f02028, 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

 

CUSTOMER_CRASH_COUNT: 1

 

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

 

PROCESS_NAME: System

 

CURRENT_IRQL: f

 

STACK_TEXT:

fffff880`02f6ba58 fffff800`02c31903 : 00000000`00000124 00000000`00000000 fffffa80`04f02028 00000000`b2000040 : nt!KeBugCheckEx

fffff880`02f6ba60 fffff800`02dee513 : 00000000`00000001 fffffa80`04f03d30 00000000`00000000 fffffa80`04f03d80 : hal!HalBugCheckSystem+0x1e3

fffff880`02f6baa0 fffff800`02c315c8 : 00000000`00000728 fffffa80`04f03d30 fffff880`02f6be30 fffff880`02f6be00 : nt!WheaReportHwError+0x263

fffff880`02f6bb00 fffff800`02c30f1a : fffffa80`04f03d30 fffff880`02f6be30 fffffa80`04f03d30 00000000`00000000 : hal!HalpMcaReportError+0x4c

fffff880`02f6bc50 fffff800`02c30dd5 : 00000000`00000004 00000000`00000001 fffff880`02f6beb0 00000000`00000000 : hal!HalpMceHandler+0x9e

fffff880`02f6bc90 fffff800`02c24e88 : fffffa80`03d26680 fffffa80`03d26788 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55

fffff880`02f6bcc0 fffff800`02cd87ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40

fffff880`02f6bcf0 fffff800`02cd8613 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c

fffff880`02f6be30 fffff800`02cde536 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153

fffff880`03316940 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiTryUnwaitThread+0x86

 

 

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

Share this post


Link to post
Share on other sites

download and run Memtest 4.01. Burn the ISO to a disk and boot to it or make a flash drive bootable and boot to the ISO that way. See if you are having a memory problem first and for most. That's where most of my problems occur

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...