Figured I'd take the plunge and start my first club.
Rules.
1. 1hr blend stable run. This is still by far the only program that TRULY stresses the imperfections of this chip.
2. MUST have a screenie WHILE UNDER LOAD with your OCN name, CPU-Z 1.57.1 and realtemp 3.67 ONLY!!
3. List your overclock, voltage, ram, cooling, and Batch number.
Cpu-z 1.57.1 download link: ftp://ftp.cpuid.com/cpu-z/cpu-z_1.57.1-setup-en.exe
Realtemp 3.67 download link: http://www.mediafire.com/?n99nq4kn95u6i6a
Prime95 link: http://files.extremeoverclocking.com...5f20c454fd87a7
Other than that, show me what you got!!
.-[SandyBridge]-.
.5ghz Pl+s Club.
.5ghz Pl+s Club.
Code:
[CENTER].-[SIZE="3"][SandyBridge][/SIZE]-.
.5ghz Pl[URL="http://www.overclock.net/intel-cpus/914262-sandy-bridge-5ghz-club.html"]+[/URL]s Club.[/CENTER]
This may also help some of you with stability.
Quote:
|
Originally Posted by coolhandluke41
I think this may be helpful for some of you,found this on XS
The OverClockers BSOD code list BSOD codes for overclocking 0x101 = increase vcore 0x124 = increase/decrease vcore or QPI/VTT...have to test to see which one it is 0x0A = unstable RAM/IMC, increase QPI first, if that doesn't work increase vcore 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 and for all of you with GB mobos you should read this; http://www.overclock.net/intel-gener...uide-p67a.html |
Edited by Jonesey I7 - 4/28/11 at 3:10pm
BYE BYE SANDY BRIDGE
(13 items) |
|
BYE BYE SANDY BRIDGE
(13 items) |
