Error: ILLEGAL SUMOUT

weatherboy · 2003-02-01, 11:43

Hi!

I use prime95 for testing my PC...and get this error:
---
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
---

what really mean this error? is for example my hardware or what? I mean is it a procesor, ram, Hdd, motherboard or what?

I have sound card on board. I read here on this forum, that a problem could be a bad sound card. is this true?

my configuration:
epox 8kha+
amd 1700+ @ 2100mhz
ram 256mb pc3200
hdd WD 80GB 8MB cache

thanks for you answers and help!

bye!

garo · 2003-02-01, 19:55

Looking at the speed of your processor, a bad overclock is the most likely problem. Your processor is probably not stable, try undoing the overclock a bit and running the torture test again. And read the stress.txt file!!

QuintLeo · 2003-02-01, 21:40

2100 Mhz or 2100+ equivilent?

190/380 FSB?!?!?

If so, what the heck are you using for cooling, liquid NO2? I didn't think even Thoroughbreds liked to push THAT hard.

I'd say your're pushing the CPU and RAM *both* way too hard - try backing off some on the FSB.

weatherboy · 2003-02-02, 15:38

Hi.
So..I have Amd XP 1700+ (1470mhz) and overclock my processor to 2100mhz, not amd XP 2100+!!! its Tbred B, core is 0.13 micron.
Vcore is 1,8V, Vdimm is 3,0V. My ram is Samsung PC3200.
Multiplayer is ×12,5. and FSB is 168mhz.
I cooling it with zalman CNPS 6000Al-Cu + 4 other zalman coolers in my case. And temperature are around 45°C at full load (100% processor load). So there couldn't be temps too high?!

But always when I OC my processor, it has shown me error like: "0,49xxx...rounding was expeted 0.4". I never got this error like now.
Is this possible the too big OC...but my friend here OC it more that 2350mhz with air cooled.

Thanks for your help!

Bye!

Prime95 · 2003-02-02, 16:11

Some have reported getting ILLEGAL SUMOUT errors because of bad device drivers - usually audio drivers. I know this can happen in Win 95/98/Me. I'm not sure if the NT/2K/XP Windows are similarly affected.

If this is the cause, then you will get the same error at stock speeds. More likely I think you have pushed the FPU too hard and need to dial it back a little bit.

QuintLeo · 2003-02-02, 19:09

Overclocking capabilities vary widely, even in a specific chip type.

One might go 50% over, while the next chip "of the same model" might only manage 30%.

It's called "manufacturing tolarances", and happens to all CPU types (among other things).

T'breds overclock REAL well - but 50%+ over is pushing it even for them.

You're also pushing the RAM and the MOTHERBOARD way out of spec - even if the CPU is capable, the RAM and the Motherboard might NOT handle that high of a FSB with 100% reliability - and those parts are ALSO subject to manufacturing tolerances....

pakaran · 2003-02-03, 01:58

Quote:

Originally Posted by Prime95

Some have reported getting ILLEGAL SUMOUT errors because of bad device drivers - usually audio drivers. I know this can happen in Win 95/98/Me. I'm not sure if the NT/2K/XP Windows are similarly affected.

I remember a professor mentioning that win9x (don' know about ME) used drivers that operated entirely in real mode, which makes any coding error likely to cause major chaos.

Can someone confirm that?

Nathan

pakaran · 2003-02-28, 17:36

(bump) still waiting for a reply

Prime95 · 2003-02-28, 18:24

I think you are correct. Win 9x/Me have device drivers that run in real mode. This isn't in and of itself bad, it just means that a bug in the driver can corrupt the address space of an application.

outlnder · 2003-02-28, 21:57

I wonder if this is the problem with older ATI video cards. The drivers being put out now cause problems with the older cards causing errors.

I had to move all my older ATI video cards off of Gimps machines because of the bad results the machines were making with them. Even when no mistakes were reported in the residue or whatever those 0000000's are.

2003-03-10, 07:40

An interesting quirk I noticed on my own machine...

If my machine's been powered down for a few hours or so, I get constant ILLEGAL SUMOUTs. They usually persist until:

A) I reboot, or

B) the machine spontaneously reboots itself.

In any case, once the machine has rebooted everything works fine. No ILLEGAL SUMOUTs, no problems.

I've heard of warming-up your car, but this is ridiculous :)

BTW, my system is a retail Athlon XP 1800+ running at its designated speed of 1.53 GHz, no overclocking.

2003-02-01, 11:43	#1
weatherboy Feb 2003 2 Posts	Error: ILLEGAL SUMOUT Hi! I use prime95 for testing my PC...and get this error: --- ERROR: ILLEGAL SUMOUT Possible hardware failure, consult readme.txt file, restarting test. --- what really mean this error? is for example my hardware or what? I mean is it a procesor, ram, Hdd, motherboard or what? I have sound card on board. I read here on this forum, that a problem could be a bad sound card. is this true? my configuration: epox 8kha+ amd 1700+ @ 2100mhz ram 256mb pc3200 hdd WD 80GB 8MB cache thanks for you answers and help! bye!

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Worker #5 and Worker#7 not running (Error ILLEGAL SUMOUT	skrupian08	Information & Answers	9	2016-08-23 16:35
BSOD I Get Illegal Sumout ?? Very Confused?	Timewarpone	Hardware	29	2010-05-23 05:10
Illegal Sumout: MSN Windows Live ?!	John S	Software	6	2007-04-30 21:02
ERROR: ILLEGAL SUMOUT	mush777	Software	13	2007-04-02 17:26
Illegal Sumout... what should I do now? Please help me!	optim	Hardware	1	2004-04-14 11:08

2003-02-01, 19:55	#2
garo Aug 2002 Termonfeckin, IE 2²×691 Posts	Looking at the speed of your processor, a bad overclock is the most likely problem. Your processor is probably not stable, try undoing the overclock a bit and running the torture test again. And read the stress.txt file!!

2003-02-01, 21:40	#3
QuintLeo Oct 2002 Lost in the hills of Iowa 448₁₀ Posts	2100 Mhz or 2100+ equivilent? 190/380 FSB?!?!? If so, what the heck are you using for cooling, liquid NO2? I didn't think even Thoroughbreds liked to push THAT hard. I'd say your're pushing the CPU and RAM both way too hard - try backing off some on the FSB.

2003-02-02, 15:38	#4
weatherboy Feb 2003 2₈ Posts	Hi. So..I have Amd XP 1700+ (1470mhz) and overclock my processor to 2100mhz, not amd XP 2100+!!! its Tbred B, core is 0.13 micron. Vcore is 1,8V, Vdimm is 3,0V. My ram is Samsung PC3200. Multiplayer is ×12,5. and FSB is 168mhz. I cooling it with zalman CNPS 6000Al-Cu + 4 other zalman coolers in my case. And temperature are around 45°C at full load (100% processor load). So there couldn't be temps too high?! But always when I OC my processor, it has shown me error like: "0,49xxx...rounding was expeted 0.4". I never got this error like now. Is this possible the too big OC...but my friend here OC it more that 2350mhz with air cooled. Thanks for your help! Bye!

2003-02-02, 16:11	#5
Prime95 P90 years forever! Aug 2002 Yeehaw, FL 3⁵×31 Posts	Some have reported getting ILLEGAL SUMOUT errors because of bad device drivers - usually audio drivers. I know this can happen in Win 95/98/Me. I'm not sure if the NT/2K/XP Windows are similarly affected. If this is the cause, then you will get the same error at stock speeds. More likely I think you have pushed the FPU too hard and need to dial it back a little bit.

2003-02-02, 19:09	#6
QuintLeo Oct 2002 Lost in the hills of Iowa 111000000₂ Posts	Overclocking capabilities vary widely, even in a specific chip type. One might go 50% over, while the next chip "of the same model" might only manage 30%. It's called "manufacturing tolarances", and happens to all CPU types (among other things). T'breds overclock REAL well - but 50%+ over is pushing it even for them. You're also pushing the RAM and the MOTHERBOARD way out of spec - even if the CPU is capable, the RAM and the Motherboard might NOT handle that high of a FSB with 100% reliability - and those parts are ALSO subject to manufacturing tolerances....

2003-02-28, 17:36	#8
pakaran Aug 2002 F9₁₆ Posts	(bump) still waiting for a reply

2003-02-28, 18:24	#9
Prime95 P90 years forever! Aug 2002 Yeehaw, FL 3⁵×31 Posts	I think you are correct. Win 9x/Me have device drivers that run in real mode. This isn't in and of itself bad, it just means that a bug in the driver can corrupt the address space of an application.

2003-02-28, 21:57	#10
outlnder Aug 2002 13E₁₆ Posts	I wonder if this is the problem with older ATI video cards. The drivers being put out now cause problems with the older cards causing errors. I had to move all my older ATI video cards off of Gimps machines because of the bad results the machines were making with them. Even when no mistakes were reported in the residue or whatever those 0000000's are.

2003-03-10, 07:40	#11
DasBub ABC₁₆ Posts	An interesting quirk I noticed on my own machine... If my machine's been powered down for a few hours or so, I get constant ILLEGAL SUMOUTs. They usually persist until: A) I reboot, or B) the machine spontaneously reboots itself. In any case, once the machine has rebooted everything works fine. No ILLEGAL SUMOUTs, no problems. I've heard of warming-up your car, but this is ridiculous :) BTW, my system is a retail Athlon XP 1800+ running at its designated speed of 1.53 GHz, no overclocking.