Have I just ****** my system up with burn test

Soldato
Joined
17 Dec 2004
Posts
8,743
Yesterday I OC my sys from 3.6 to 3.8, and I tested it with orthos for 12hrs, and came back fine, then I tested it with dreaded burntest for just over 11hrs, cos Cyber-Mav was on an on at me to test it with burntest, anyway I noticed during the end of the test,, there 4 errors.. Now that has got me wrorring that ive caused damage to my hardware, cos why errors at the end of the test and not all the way through. Anyway its back on 3.6, and thats where its staying... thats why I didnt want to use burn test cos it stressing your hardware to ummm destruction, anyway heres the burntest log
What you think guys??
btsm6.jpg
 
Last edited:
wots the point of a stress test if it doesnt stress your system to the max? just watch a few HD films to do your stability testing in the future.
 
I prefer to use orthos (prime) program
I think it less stresses system


Burn test for 11 hours?
I think It's too much

As you know, burn test is massively(might be) stressing computer system
You can check your computer system's stability in several hours
Even one or two hours enough for intel burn test

Orthos prime test takes more time
10 hours might be enough...

by the way, the log seems to be fine, good job, well done
 
You kept on and on tho, and that why I didnt want to use it.. orthos does a perfectly decen job at making ** sys stable, I grant you maybe not 100 % stable but what game or software is gonna push the system to braking point?
 
Have you tried dual orthos test at priority7 ?

Or not only orthos test,
Prime 95 is also really good testing program.
It can stress more


What do you mean?
Accept for the ending bit where something has been pushed too far?????
 
phil i think you shoudl tell everyone your entire story here.

you full system settings to be exact. you have overclocked the ram in your system, 422mz its running at when its specced for 400mhz, and with 4 sticks making 8gb which i suspect is the issue here. you didnt even run a memory test after doing your overclock. you went straight into windows which is risky business and you could have corrupted some data on your drive and nuked the OS.

my system has no issues with intel burntest, ran it for 52hours and no errors. machines are designed to run majority of the time 24/7 with no problems/errors at STOCK speeds. it all depends on how you value your systems usage, id rather have a 3.6ghz system thats making no errors than a 3.8ghz system thats making errors.

remember intel themselves make and use the linpack binaries that are in intel burntest for thier own testing regieme.

as for stress testing, what better way to find errors than to run the most stressful tester you can get. if im not mistaken you ran orthos overnight and got no errors, yet intel burntest found errors. shows the difference right there.

but if your happy with your setup making a few errors now and then then stick to 3.8gh mate ;)
 
Cyber-mav, cheers
I think that's a good advice

The errors might be due to Ram

There are several Ram testing program...

I prefer to use MEmset program to find fast ram timing speed
and I afterwards stress my ram with mem test program...

Of course, you knew this informations... but just in case....
 
but its the errors at the end of the test,, yeh 1 error is ok but 4 errors close to gether like that tells me that something been pushed too much and now its failing,,, bet if I test it for another 12hrs it would fail all the way through at 3.8
 
[Accept for the ending bit where something has been pushed too far?????]

Might not be perfect but it might be time to take a rest

after 10 hours prime testing, errors found,
repeating this work...
people then normally get tired after two days...
Might be..
 
I am now stablising my computing system with many test for long time......
It has now been third days...

I am bit tired...

However I am proud of my system.
 
I am usning XMS2 8500 1GBX2 rams
It's brillient.. really good

However Ram default settings sometimes may not match to some computers
For example, due to voltage fluctuation....
 
your errors comming at later on in the test look like ram errors to me, dont forget intel burntest hold a lot of data in the ram then feeds it to the cpu, any ram errors will change the data in the memory and alter the test results and give you different numbers. the reason i think you have ram errors is because iv had errors show up in very late testing on my single core opteron setup, it would get 1 random error every 30-40 passes sometimes more frequent, it was the command rate, 1T wasnt stable, drop to 2T had no errors at all. and memtest didnt pickup the error since memtest isnt 100% reliable when it comes to memory testing in my experience.

man iv had a 57 hour prime stable system in the past which used to crash 20 mins into a game called dawn of war. turns out that the cpu was getting overheated in the game, yet prime was lower in temps than the game. turns out prime is a crap cpu testing program. thats why i have always sought to test my systems with the most demanding program i can find, it not only reduces testing time but also ensures the systems i build for clients are 100% reliable.
 
just to add, if it was your cpu that was unstable, intel burntest would be picking up errors a lot soon and a lot more frequently. hence why i suspect your ram may not be coping overclocked. in my experience ram is far harder to clock up than a cpu.
 
I would have thought my mem would have taken a measly 22mhz more with it being xms2.. Another thing poped in to my head could i have caused damage to the the mem controller at all, cos ppl say using all slots stressing the controller out more
 
it stresses out the memcontroller but no it wont damage it. as a rule of thumb you arent going to bust anything unless you run silly volts into it or if you run it at 100c or more for long periods of time.

if you still have worries about intelburntest i suggest you wander over to xtremesystems where the creator of intel burntester has a larger thread on it and you could post your worries there.
 
Back
Top Bottom