prime95 illegal sumout?

bustinya

Honorable
Nov 7, 2012
102
0
10,680
I have an FX8350 and an asrock 990FX. My cpu cooler is a coolermaster hyper 212 evo and have another 4 fans (3x120mm and 1x240mm). I notched the cpu to 4.2 GHz thinking it would be good but prime95 failed almost inmediately saying something about illegal summout. I put the cpu core voltage up to1.41 V. prime95 failed again but this time it took 3 minutes and it didn't say anything about illegal summout. I'm not sure what the problem is 🙁 Do i have to put the voltage a little bit higher? I tested again and after 2 minutes a core stopped working and the cpu temp on SpeedFan went up to over 50 degrees Celsius. In 2 minutes! It went up very quickly. I am testing again right now with the voltage another 0.125 more but it still heats very quickly. Now, the problem isnt the prime95 test, but simply the temperature. I felt like my computer would be very good against heat but i am being proved wrong. Could it be that SpeedFan is wrong? the temperature on HWMonitor says that CPU is at 38 degrees. SpeedFan is already at 53.... Im not sure which one is the socket and which the core but there must be a problem 🙁 it failed again saying "illegal sumout" exceeded warning limit (100) and that i should read the readme.txt file.
"Could it be a software problem? If the error is ILLEGAL SUMOUT and you are
running Windows 95/98/Me, then there is some chance that this is a software
problem. A device driver or VxD may not be saving and restoring FPU state
correctly. Windows NT/2000/XP/Vista protects prime95 from bad device drivers.
In that case ILLEGAL SUMOUT is very likely a true hardware error. The good news
is that prime95 recovers very well from ILLEGAL SUMOUT errors. Try seeing
if the problem occurs only when a specific device is active or a specific
program is running." That is what the readme.txt file says. I don't get what I should do. Please help!
 
Solution
Go into your BIOS and note your idle temps shown in the BIOS.

Then go into windows and let it sit for a couple minutes to ensure it completes all its start up stuff and goes to idle.

Then check your idle temp with both programs and see which one gets closest to the idle temp shown in your BIOS. I would still try another software program until I got to programs to agree on temps. (Maybe core temp will work with your CPU?)

The kind of error might matter if you are doing extreme overclocking where you want to play with intricate voltages beyond vcore. But if you are just trying to do a straight-forward "sane" overclock, any stress test error like that just means it's unstable.

Chips can get more unstable as temps rise, so nail down...
Go into your BIOS and note your idle temps shown in the BIOS.

Then go into windows and let it sit for a couple minutes to ensure it completes all its start up stuff and goes to idle.

Then check your idle temp with both programs and see which one gets closest to the idle temp shown in your BIOS. I would still try another software program until I got to programs to agree on temps. (Maybe core temp will work with your CPU?)

The kind of error might matter if you are doing extreme overclocking where you want to play with intricate voltages beyond vcore. But if you are just trying to do a straight-forward "sane" overclock, any stress test error like that just means it's unstable.

Chips can get more unstable as temps rise, so nail down your temps first. (make sure you know what your real temps actually are before thinking about more voltage)

 
Solution


sorry for my ignorance but, by idle you mean the temperatures when doing "nothing" (no serious stressing processes)? I saw the temperatures in the BIOS and I will note them down but when you tell me to check the idle temp with both programs you mean HWMonitor and Speedfan and "i would still try another software program" you mean a stress testing one? or a temperature one? I am doing sane overclock.
 
You can't see the stress temps in the BIOS because the OS isn't even running when you are in there, however the temp in your BIOS is most likely accurate. So, what you want to do is compare your BIOS temp to the temps your software shows. (The programs you use to see temps.....speed fan, hwmonitor etc)

In order to have temps comparable to the BIOS, you need to compare "not doing anything" temps.

"Another software program" is in regards to a program that shows temps. (Like core temp, as I mentioned)

I prefer to have two (temperature) programs "agree" on temps before I am confident that I have the right info.