whea errors and ocing

~>Dg<~

~>Dg<~

~>Dg<~

Caporegime
Joined
1 Jun 2006
Posts
33,994
Location
Notts
okay got better cooling now new better case so deciding to oc higher on my cpu.

pushed on last night and gamed all night on current oc but i checked for whea errors this morning and i had one :p

how many would you except obviously 0 is perfect.

im currently just bumped the volts a notch to see if that is 100 percent.


whats the safe 24/7 for a i3570k ? 1.3 ? 1.4?
 
Hi Dg, Common BSOD Error Codes for Overclocking, handy to have-

0x101 = increase vcore
0x124 = increase/decrease QPI/VTT first, if not increase/decrease vcore...have to test to see which one it is
on i7 45nm, usually means too little VVT/QPI for the speed of Uncore
on i7 32nm SB, usually means too little vCore
0x0A = unstable RAM/IMC, increase QPI first, if that doesn't work increase vcore
0x1A = Memory management error. It usually means a bad stick of Ram. Test with Memtest or whatever you prefer. Try raising your Ram voltage
0x1E = increase vcore
0x3B = increase vcore
0x3D = increase vcore
0xD1 = QPI/VTT, increase/decrease as necessary, can also be unstable Ram, raise Ram voltage
0x9C = QPI/VTT most likely, but increasing vcore has helped in some instances
0x50 = RAM timings/Frequency or uncore multi unstable, increase RAM voltage or adjust QPI/VTT, or lower uncore if you're higher than 2x
0x109 = Not enough or too Much memory voltage
0x116 = Low IOH (NB) voltage, GPU issue (most common when running multi-GPU/overclocking GPU)
0x7E = Corrupted OS file, possibly from overclocking. Run sfc /scannow and chkdsk /r

BSOD Codes for Sandy Bridge

0x124 = add/remove vcore or QPI/VTT voltage (usually Vcore, once it was QPI/VTT)
0x101 = add more vcore
0x50 = RAM timings/Frequency add DDR3 voltage or add QPI/VTT
0x1E = add more vcore
0x3B = add more vcore
0xD1 = add QPI/VTT voltage
“0x9C = QPI/VTT most likely, but increasing vcore has helped in some instances”
0X109 = add DDR3 voltage
0x0A = add QPI/VTT voltage
 
whea errors you only need to worry about cpu and memory warnings/errors

the rest are usually fine unless it still causing crashes/instability but I havn't come across any

anything below 1.4v for cpu voltage is ok
 
Very occassionally whea errors caused me freezes/crashes in games/benchmarks. Bf3 being the main culprit. Raising cpu vcore seemed to cure them. Havent had any on the hw system yet, just a few memory oc related bsods. Which hopefully have been sorted now after a bit more tweaking.
 
Regarding 0x124. On ivy/hw does the same apply with regards vcore or the io/sa voltages? Been playing the bf4 beta tonight and just crashed with a 0x124 bsod. Currently running the ram at 2133mhz, 9-10-10-21 1.55v. ioa, iod and sa all set to 1.200v.
 
A corrected hardware error has occurred.

Reported by component: Processor Core
Error Source: Corrected Machine Check
Error Type: Internal parity error
Processor APIC ID: 2

The details view of this entry contains further information.

24 hrs with this oc and i had one whea error :(

should i just bump one more notch on the volts ?

just looked at the details and googled the error 0x8000000000000000

and some guy was on about it being related to speed step and not a actually machine fault anyone know anything about this?
 
Last edited:
was it parity 19?

yh try one notch more,can be linked to c3/c6 states but cpu won't idle properly if you disable it

just keep raising offset till there's no errors (cpu or memory related)
 
yeah cpu related

if i disable the c3/c6 will this help. also looking for spread spectrum on my board gigbyte d3h and not sure what its called.

its close i think to stable not crashing and can game for hrs its just throwing that odd whea error up not very often.
 
if its stable then its fine,its only if it crashes games ect

spread spectrum should be labelled the same,c3/c6 might help but I leave mine on
 
wazza300 said:
it can be either cpu v and or cpu/vtt (imc related) voltages
Click to expand...
Ive raised ioa/d, sa and cache a few notches. Strangely when dropping the ram to it's stock speed, timings and dram voltage. System blue screened at the windows loading bar. Same io and sa voltages i had with it at 2133mhz?
 
idk,unless cache speed has something to do with it?

on x58 uncore/cache used to be 2x ram multi and add 1,but haswell clocks through cpu multi (fixed bclk)

maybe too much io/sa for lower ram speed caused it?
 
Still blue screened with the above voltage changes, upped vcore a few notches and game ran much longer, managed to complete a round without incident.

@Dg, when you were getting the whea error, are you getting any freezes/crashes etc in games? Quite often with bf3 when it errored on my 3570k/3770k, checking event viewer showed up a 19 cpu parity error round the time of the problem in game.
 
You must log in or register to reply here.
Back
Top Bottom