|
|
|
|
|
|
Droog
offline
OC Newbie 20 Jahre dabei !
AMD T-Bred 2080 MHz @ 2225 MHz 41°C mit 1.65 Volt
|
Nope- geht auch nicht: Auszug aus dem Protokoll: 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. Torture Test ran 1 minutes 14 seconds - 0 errors, 100 warnings. Execution halted.
|
Beiträge gesamt: 29 | Durchschnitt: 0 Postings pro Tag Registrierung: Okt. 2004 | Dabei seit: 7340 Tagen | Erstellt: 15:34 am 29. Okt. 2004
|
|
SPYcorp
offline
OC God 20 Jahre dabei !
AMD Athlon 64 X2 Dual Core 2000 MHz @ 2400 MHz 50°C mit 1.25 Volt
|
wow "illegal sumout" das klingt ja böse ^^ Lies dich mal durch das prime95_help durch. Steht nochn bissel mehr drinne, würde jetz nur das post an text sprengen POSSIBLE HARDWARE FAILURE If the message, "Possible hardware failure, consult the readme file.", appears in the results file, then prime95's error-checking has detected a problem. After waiting 5 minutes, the program will continue testing from the last save file. Could it be a software problem? If the error is ILLEGAL SUMOUT, then there is a good chance that this is a software problem. A device driver or VxD may not be saving and restoring FPU state correctly. 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. The other two errors messages, SUMINP! = SUMOUT and ROUND OFF > 0.40 are caused by one of two things: 1. For reasons too complicated to go into here, the program's error checking is not perfect. Some errors can be missed and some correct results flagged as an error. If you get the message "Disregard last error..." upon continuing from the last save file, then you may have found the rare case where a good result was flagged as an error. 2. A true hardware error. If you do not get the "Disregard last error..." message or this happens more than once, then your machine is a good candidate for a torture test. See the stress.txt file for more information [edit] hmmm. du kannst einfach so multis ändern ? nett ^^. Könnte sein, das die cpu schon die ganze zeit oc´ed läuft, weil der multi zu "hoch" war. Schraub mal den fsb runter auf normale werte (100/133/166) und teste neu. Es kann trotzalledem sein, das es am ram liegt. Oder aber dein agp/pci ist wg. des "krummen" fsb übertaktet und dein pc läuft deshalb (prime-) instable. (Geändert von SPYcorp um 17:30 am Okt. 29, 2004)
|
Beiträge gesamt: 1437 | Durchschnitt: 0 Postings pro Tag Registrierung: Sep. 2004 | Dabei seit: 7389 Tagen | Erstellt: 17:18 am 29. Okt. 2004
|
|
|
|
|
|
|