Overclock.net › Forums › AMD › AMD CPUs › Need help Is my cpu stable
New Posts  All Forums:Forum Nav:

Need help Is my cpu stable

post #1 of 14
Thread Starter 
my cpu is in my sig, from 2.8 to 3.25
I used prime95 for stress testing and heres my results

bios for cpu is set at
cpu voltage-1.3750, but reads 1.424 on cpu-z, can someone help me on this
cpu frequency-210
multiplier-15.5x

sorry but it was overnight

[Mon Dec 22 03:35:19 2008]
Self-test 1024K passed!
Self-test 1024K passed!
[Mon Dec 22 03:50:54 2008]
Self-test 8K passed!
Self-test 8K passed!
[Mon Dec 22 04:07:41 2008]
Self-test 10K passed!
Self-test 10K passed!
[Mon Dec 22 04:24:11 2008]
Self-test 896K passed!
Self-test 896K passed!
[Mon Dec 22 04:39:59 2008]
Self-test 768K passed!
Self-test 768K passed!
[Mon Dec 22 04:56:41 2008]
Self-test 12K passed!
Self-test 12K passed!
[Mon Dec 22 05:13:14 2008]
Self-test 14K passed!
Self-test 14K passed!
[Mon Dec 22 05:29:12 2008]
Self-test 640K passed!
Self-test 640K passed!
[Mon Dec 22 05:45:29 2008]
Self-test 512K passed!
Self-test 512K passed!
[Mon Dec 22 06:01:46 2008]
Self-test 16K passed!
Self-test 16K passed!
[Mon Dec 22 06:18:20 2008]
Self-test 20K passed!
Self-test 20K passed!
[Mon Dec 22 06:33:29 2008]
Self-test 448K passed!
Self-test 448K passed!
[Mon Dec 22 06:50:59 2008]
Self-test 384K passed!
Self-test 384K passed!
[Mon Dec 22 07:06:41 2008]
Self-test 24K passed!
Self-test 24K passed!
[Mon Dec 22 07:22:59 2008]
Self-test 28K passed!
Self-test 28K passed!
[Mon Dec 22 07:40:06 2008]
Self-test 320K passed!
Self-test 320K passed!
[Mon Dec 22 07:55:53 2008]
Self-test 256K passed!
Self-test 256K passed!
[Mon Dec 22 08:11:16 2008]
Self-test 32K passed!
Self-test 32K passed!
[Mon Dec 22 08:22:08 2008]
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Maximum number of warnings exceeded.
[Mon Dec 22 08:27:37 2008]
Self-test 40K passed!



just want to know if thats bad

the other thread that was started was still going and no errors
Edited by v8killaz - 12/22/08 at 1:38pm
Giant
(12 items)
 
  
CPUMotherboardGraphicsRAM
i7 3930k@4.5ghz asus p9x79 asus r9 290 16gb kingston hyperx 1600mhz 
Hard DriveCoolingOSMonitor
samsung 840 evo 250gb xspc liquid cooled cpu/gpu win 7 64bit 24" 1080p 
KeyboardPowerCaseMouse
logitech g510s hx1059 corsair corsair 900d g500s logitech 
  hide details  
Reply
Giant
(12 items)
 
  
CPUMotherboardGraphicsRAM
i7 3930k@4.5ghz asus p9x79 asus r9 290 16gb kingston hyperx 1600mhz 
Hard DriveCoolingOSMonitor
samsung 840 evo 250gb xspc liquid cooled cpu/gpu win 7 64bit 24" 1080p 
KeyboardPowerCaseMouse
logitech g510s hx1059 corsair corsair 900d g500s logitech 
  hide details  
Reply
post #2 of 14
Thread Starter 
I would think its my ram, but it was so long till prime noticed a hardware failure
I might up the voltage see what happens
Giant
(12 items)
 
  
CPUMotherboardGraphicsRAM
i7 3930k@4.5ghz asus p9x79 asus r9 290 16gb kingston hyperx 1600mhz 
Hard DriveCoolingOSMonitor
samsung 840 evo 250gb xspc liquid cooled cpu/gpu win 7 64bit 24" 1080p 
KeyboardPowerCaseMouse
logitech g510s hx1059 corsair corsair 900d g500s logitech 
  hide details  
Reply
Giant
(12 items)
 
  
CPUMotherboardGraphicsRAM
i7 3930k@4.5ghz asus p9x79 asus r9 290 16gb kingston hyperx 1600mhz 
Hard DriveCoolingOSMonitor
samsung 840 evo 250gb xspc liquid cooled cpu/gpu win 7 64bit 24" 1080p 
KeyboardPowerCaseMouse
logitech g510s hx1059 corsair corsair 900d g500s logitech 
  hide details  
Reply
post #3 of 14
Try lowering your HT link or lower your ram settings.
Set them to 667 if they are 800 on stock.
and decrease your HT link by 1x and try the test again.

No idea if this might change anything, Ive only tried OC'ing a few time so.

Tho, i'd try lowering the ram speeds first, if that dousn't work then the ram won't be the problem

If anyone else has better suggestions, feel free to bash me & correct me
Home rig
(15 items)
 
  
CPUMotherboardGraphicsRAM
i5 2500K @ 4.5ghz Asus P8P67-Pro EVGA 560ti Corsair Vengeance 2x 4GB DDR3 1600 CL9 
Hard DriveHard DriveOSMonitor
Samsung Spinpoint F4 - 2TB  Crucial M500 120GB (to be added soon) Win7 64bit Acer V223HQ 
KeyboardPowerCaseMouse
Default Corsair 750THX CM690 II Basic Logitech G400 
Mouse PadAudio
steelseries qck mini / qck normal / qck mass Traktor audio 2  
  hide details  
Reply
Home rig
(15 items)
 
  
CPUMotherboardGraphicsRAM
i5 2500K @ 4.5ghz Asus P8P67-Pro EVGA 560ti Corsair Vengeance 2x 4GB DDR3 1600 CL9 
Hard DriveHard DriveOSMonitor
Samsung Spinpoint F4 - 2TB  Crucial M500 120GB (to be added soon) Win7 64bit Acer V223HQ 
KeyboardPowerCaseMouse
Default Corsair 750THX CM690 II Basic Logitech G400 
Mouse PadAudio
steelseries qck mini / qck normal / qck mass Traktor audio 2  
  hide details  
Reply
post #4 of 14
Did you try makinhg that jump all at once? or did you take it a step at a time? Because if you took it all at once, by that i mean from 2.8 to 3.2 at once you probably don't have enough vcore. Stock is 1.35, I would go off what bios says for your voltage.

Try backing off to 3.0 with 1.37 vcore and see if you can get it stable from there. Then work your way up. When you make such a big jump there are all kinds of places that it could be erroring. And it is sometimes hard to be able to tell.

I would use Orthos test priorty 9 To test as well. I have never used prime 95 so i cannot attest to it. But im sure it is a good program.

Hope I helped! Good Luck!
Work in Progress
(15 items)
 
  
CPUMotherboardGraphicsRAM
AMD FX-8350 BE Vishera GIGABYTE 990FXA SAPPHIRE FleX-2 7950 G.SKILL Ripjaws X Series 
Hard DriveOptical DriveCoolingOS
OCZ Vertex 4 HP 20X DVD±R DVD Burner CORSAIR H100i Windows 8 
MonitorMonitorKeyboardPower
22in Widescreen Samsung 24in Widescreen Asus Microsoft Corsair 650TX 
CaseMouse
Corsair Vengeance C70 in Gunmetal Black Logitech G700 
  hide details  
Reply
Work in Progress
(15 items)
 
  
CPUMotherboardGraphicsRAM
AMD FX-8350 BE Vishera GIGABYTE 990FXA SAPPHIRE FleX-2 7950 G.SKILL Ripjaws X Series 
Hard DriveOptical DriveCoolingOS
OCZ Vertex 4 HP 20X DVD±R DVD Burner CORSAIR H100i Windows 8 
MonitorMonitorKeyboardPower
22in Widescreen Samsung 24in Widescreen Asus Microsoft Corsair 650TX 
CaseMouse
Corsair Vengeance C70 in Gunmetal Black Logitech G700 
  hide details  
Reply
post #5 of 14
Thread Starter 
Quote:
Originally Posted by Ike View Post
Did you try makinhg that jump all at once? or did you take it a step at a time? Because if you took it all at once, by that i mean from 2.8 to 3.2 at once you probably don't have enough vcore. Stock is 1.35, I would go off what bios says for your voltage.

Try backing off to 3.0 with 1.37 vcore and see if you can get it stable from there. Then work your way up. When you make such a big jump there are all kinds of places that it could be erroring. And it is sometimes hard to be able to tell.

I would use Orthos test priorty 9 To test as well. I have never used prime 95 so i cannot attest to it. But im sure it is a good program.

Hope I helped! Good Luck!
might lower to 3.1-

i got you
of course i didnt just jump to 3.2
i went really slow but then again i only tested lower ghz for 2 hour stress tests and then felt comfortable with this and tested it for all night

ill try orthos right now, or tonight
well see
Edited by v8killaz - 12/22/08 at 4:47pm
Giant
(12 items)
 
  
CPUMotherboardGraphicsRAM
i7 3930k@4.5ghz asus p9x79 asus r9 290 16gb kingston hyperx 1600mhz 
Hard DriveCoolingOSMonitor
samsung 840 evo 250gb xspc liquid cooled cpu/gpu win 7 64bit 24" 1080p 
KeyboardPowerCaseMouse
logitech g510s hx1059 corsair corsair 900d g500s logitech 
  hide details  
Reply
Giant
(12 items)
 
  
CPUMotherboardGraphicsRAM
i7 3930k@4.5ghz asus p9x79 asus r9 290 16gb kingston hyperx 1600mhz 
Hard DriveCoolingOSMonitor
samsung 840 evo 250gb xspc liquid cooled cpu/gpu win 7 64bit 24" 1080p 
KeyboardPowerCaseMouse
logitech g510s hx1059 corsair corsair 900d g500s logitech 
  hide details  
Reply
post #6 of 14
Thread Starter 
hey guys ran orthos for 1 hour and some minutes and no errors. cpu is cool and steady
i
is that enough or no
using 100% cpu load btw
Giant
(12 items)
 
  
CPUMotherboardGraphicsRAM
i7 3930k@4.5ghz asus p9x79 asus r9 290 16gb kingston hyperx 1600mhz 
Hard DriveCoolingOSMonitor
samsung 840 evo 250gb xspc liquid cooled cpu/gpu win 7 64bit 24" 1080p 
KeyboardPowerCaseMouse
logitech g510s hx1059 corsair corsair 900d g500s logitech 
  hide details  
Reply
Giant
(12 items)
 
  
CPUMotherboardGraphicsRAM
i7 3930k@4.5ghz asus p9x79 asus r9 290 16gb kingston hyperx 1600mhz 
Hard DriveCoolingOSMonitor
samsung 840 evo 250gb xspc liquid cooled cpu/gpu win 7 64bit 24" 1080p 
KeyboardPowerCaseMouse
logitech g510s hx1059 corsair corsair 900d g500s logitech 
  hide details  
Reply
post #7 of 14
Keep going, sometimes you dont get an error untill over 4/5 hours.
Some people do 24h tests to make sure it stable for 24/7 use.

Just scale your test time to the ammount of time your actually using the CPU on load.
Home rig
(15 items)
 
  
CPUMotherboardGraphicsRAM
i5 2500K @ 4.5ghz Asus P8P67-Pro EVGA 560ti Corsair Vengeance 2x 4GB DDR3 1600 CL9 
Hard DriveHard DriveOSMonitor
Samsung Spinpoint F4 - 2TB  Crucial M500 120GB (to be added soon) Win7 64bit Acer V223HQ 
KeyboardPowerCaseMouse
Default Corsair 750THX CM690 II Basic Logitech G400 
Mouse PadAudio
steelseries qck mini / qck normal / qck mass Traktor audio 2  
  hide details  
Reply
Home rig
(15 items)
 
  
CPUMotherboardGraphicsRAM
i5 2500K @ 4.5ghz Asus P8P67-Pro EVGA 560ti Corsair Vengeance 2x 4GB DDR3 1600 CL9 
Hard DriveHard DriveOSMonitor
Samsung Spinpoint F4 - 2TB  Crucial M500 120GB (to be added soon) Win7 64bit Acer V223HQ 
KeyboardPowerCaseMouse
Default Corsair 750THX CM690 II Basic Logitech G400 
Mouse PadAudio
steelseries qck mini / qck normal / qck mass Traktor audio 2  
  hide details  
Reply
post #8 of 14
Quote:
Originally Posted by v8killaz View Post
hey guys ran orthos for 1 hour and some minutes and no errors. cpu is cool and steady
i
is that enough or no
using 100% cpu load btw
use intel burn test ( im not sure if its AMD compatible )
but that test will let you know in 10 mins whether ur cpu /ram is stable or not

10 mins of intel burn test is equivalent to 40hrs on prime95
the budget system
(13 items)
 
  
CPUMotherboardGraphicsRAM
wolfdale e7300 Biostar P43 Msi gtx260 Crucial Ballistx ddr2 800mhz 
Hard DriveOptical DriveOSMonitor
500GB Seagate Barracuda Lite-on dvdrw/cdrw Windows XP 64 Pro Hanns G 17'' widescreen 
PowerCase
Rosewill 500W Cooler Master 590 
  hide details  
Reply
the budget system
(13 items)
 
  
CPUMotherboardGraphicsRAM
wolfdale e7300 Biostar P43 Msi gtx260 Crucial Ballistx ddr2 800mhz 
Hard DriveOptical DriveOSMonitor
500GB Seagate Barracuda Lite-on dvdrw/cdrw Windows XP 64 Pro Hanns G 17'' widescreen 
PowerCase
Rosewill 500W Cooler Master 590 
  hide details  
Reply
post #9 of 14
Thread Starter 
Quote:
Originally Posted by askareem24 View Post
use intel burn test ( im not sure if its AMD compatible )
but that test will let you know in 10 mins whether ur cpu /ram is stable or not

10 mins of intel burn test is equivalent to 40hrs on prime95
it is compatible with amd
have you ever used it
my system stays stable on that for 1 hour at 3.2 ghz

it seems to give me the blue screen when i try it at 3.25

i want to get this damn thing to 3.3 flat
Giant
(12 items)
 
  
CPUMotherboardGraphicsRAM
i7 3930k@4.5ghz asus p9x79 asus r9 290 16gb kingston hyperx 1600mhz 
Hard DriveCoolingOSMonitor
samsung 840 evo 250gb xspc liquid cooled cpu/gpu win 7 64bit 24" 1080p 
KeyboardPowerCaseMouse
logitech g510s hx1059 corsair corsair 900d g500s logitech 
  hide details  
Reply
Giant
(12 items)
 
  
CPUMotherboardGraphicsRAM
i7 3930k@4.5ghz asus p9x79 asus r9 290 16gb kingston hyperx 1600mhz 
Hard DriveCoolingOSMonitor
samsung 840 evo 250gb xspc liquid cooled cpu/gpu win 7 64bit 24" 1080p 
KeyboardPowerCaseMouse
logitech g510s hx1059 corsair corsair 900d g500s logitech 
  hide details  
Reply
post #10 of 14
All of those tests are BS IMO. Download S&M and run that test at 100%/long.
S&M is BY FAR the MOST greuling stress test out there. Also, itll tell you exactly what failed, wether it be L1, L2, MMX, SSE, etc. This WILL get your CPU hotter than any other test out there. So make sure you keep an eye on your temps using Coretemp. I find this test to be the most accurate when it comes to stability testing.
Some of my OC's have failed Orthos and OCCT but have passed S&M, and are perfectly stable, no crashes. Ever since then I havent used Orthos or OCCT.
Black Box
(16 items)
 
  
CPUMotherboardGraphicsRAM
i7 3770k Asus P8Z77-Vpro Evga 780 Classified Crucial Ballistix 
Hard DriveHard DriveOptical DriveCooling
A-Data 128GB SSD Samsung Spinpoint F3 1TB Pioneer BDR-207DBK Corsair H80 
OSMonitorKeyboardPower
Win 7 pro 64 Hannspree 25" 1080p LCD 2ms Razer Lycosa PC Power & Cooling 760w 
CaseMouseMouse PadAudio
Corsair 550D MX 518 Allsop Creative XFi Xtreme music 
  hide details  
Reply
Black Box
(16 items)
 
  
CPUMotherboardGraphicsRAM
i7 3770k Asus P8Z77-Vpro Evga 780 Classified Crucial Ballistix 
Hard DriveHard DriveOptical DriveCooling
A-Data 128GB SSD Samsung Spinpoint F3 1TB Pioneer BDR-207DBK Corsair H80 
OSMonitorKeyboardPower
Win 7 pro 64 Hannspree 25" 1080p LCD 2ms Razer Lycosa PC Power & Cooling 760w 
CaseMouseMouse PadAudio
Corsair 550D MX 518 Allsop Creative XFi Xtreme music 
  hide details  
Reply
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: AMD CPUs
Overclock.net › Forums › AMD › AMD CPUs › Need help Is my cpu stable