Dec 2 2011, 06:51 AM, updated 13y ago
This is Intel LGA2011 aka Sandy Bridge-E (SB-E) overclocking thread.
Please share your benchmark, stability, OC guides etc...
Reviews & Benchmarks:
» Click to show Spoiler - click again to hide... «
Latest Overclocking Programs, System Info, Benchmarking, & Stability Tools
LINK - credit to stasio
Monitoring Tools:
CPU-Z 1.64
RealTemp 3.70
ReadlTemp TI
CoreTemp 1.0 RC5
HWiNFO 4.14-1880
Mem TweakIT 1.01.7
CPU-Tweaker 2.0 Beta 15
Stability/Stressing Tools: - Please use Win7 Service Pack 1 (SP1), take a screenshot before the test finished.
LinX 0.6.4 (11.0.1.005) - set memory to "ALL" preset
LinX 0.6.4 (11.0.3.008) - set memory to "ALL" preset
Intel BurnTest 2.54 (11.0.1.005)
Intel BurnTest 2.54 Linpack (11.0.3.008)
Prime95 27.9 Build 1 X64
Prime95 27.9 Build 1 X86
QUOTE(owikh84 @ Aug 31 2012, 08:59 AM)
Open RealTemp
Execute Task Manager > Performance tab
Launch Prime95 27.7
Choose custom, min FFT 128k, mem to use (see task manager for available mem)
Start stressing
Monitor the max temp make sure it doesn't exceed 105C (TJmax) - speed will go down (throttled) if TJmax is hit to protect the CPU from overheating
Stress it for 3 hours +
Don't stop priming & open CPU-Z
Take screenshot including Prime95 + CPU-Z + Task Manager + RealTemp
Execute Task Manager > Performance tab
Launch Prime95 27.7
Choose custom, min FFT 128k, mem to use (see task manager for available mem)
Start stressing
Monitor the max temp make sure it doesn't exceed 105C (TJmax) - speed will go down (throttled) if TJmax is hit to protect the CPU from overheating
Stress it for 3 hours +
Don't stop priming & open CPU-Z
Take screenshot including Prime95 + CPU-Z + Task Manager + RealTemp
» Click to show Spoiler - click again to hide... «
QUOTE(eXnikaru @ Apr 26 2013, 04:18 PM)
some tips for sandy bridge user..
U all can test the system stability in shorter time with prime95..
Just select custom and test with
1344fft 1344fft 1minute 80-90% available ram for 15mins
If can passed the test u can test with 1792fft 1792fft 1minute 80-90% available ram for 15mins too..
If passed 2 tests on certain vcore..then your system should stable for 12hours prime95 blend test.
the 1344 and 1792 fft is the extremely hard and best test for sb`stability
Normally,if your system is unstable..one of the workers in prime95 will stop/BSOD will happen within 10mins of both test
Benchmark Tools:U all can test the system stability in shorter time with prime95..
Just select custom and test with
1344fft 1344fft 1minute 80-90% available ram for 15mins
If can passed the test u can test with 1792fft 1792fft 1minute 80-90% available ram for 15mins too..
If passed 2 tests on certain vcore..then your system should stable for 12hours prime95 blend test.
the 1344 and 1792 fft is the extremely hard and best test for sb`stability
Normally,if your system is unstable..one of the workers in prime95 will stop/BSOD will happen within 10mins of both test
SuperPI Mod XS 1.5
HyperPI 0.99 Beta
AIDA64 2.85.2400
Cinebench 11.5
wprime 2.09
pifast
maxxmem
AquaMark 3.1
BSOD codes for overclocking
QUOTE
0x101 = increase vcore
0x124 = increase vcore
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
0x124 = increase vcore
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
LGA2011 BIOS, facts, stats and and list of mainboards
This post has been edited by owikh84: May 13 2013, 07:01 AM
Quote
0.0232sec
0.42
6 queries
GZIP Disabled