View Single Post
Old 2013-01-27, 19:17   #11
Jorge
 
Jan 2013

32 Posts
Default

I've used P95 for years on many PCs along with OCCT and I understand that both of these test programs are very severe. That is precisely why I use them and make sure all of my PCs will run for 24 hours without any errors.

IME every PC that P95 would error on, would also error on OCCT. This PC does not error on any stress test but P95. I'm not convinced it's the PC, especially with quite a few people reporting the same situation with AMD FX processors - even at stock CPU settings. There may be some monitoring issue with AMD FX processors, I don't know. That's why I'm providing test logs to try and resolve the issue.

The run log below shows this system ran perfectly with small FFF for 9 hours and 50 minutes then suddenly halted based on "100 warnings", not based on an actual error. No errors are reported. That's 424 test and almost 10 solid hours of P95 with no errors and then all of a sudden it stops working based on (100) possible hardware "warnings".

Notice the BLUE highlighted message at the end... ZERO ERRORS, 100 Warnings. If there are zero errors, then the test should not have stopped. If there was an error it would be displayed. The test stopped based on "100 warnings". The hardware warnings might be an issue with the AMD FX processors since there are zero errors for the tests?

During the 9 hours and 50 minutes of testing, they system has already run the same string several times without fail. With the FX processors being a totally new X86 CPU design, there may be some monitoring issues that create "warnings" ? I don't know but I know that OCCT uses a very similar stress testing methodology and appears to be as severe, yet this PC runs OCCT for hours without errors. Even in this P95 test it never showed an error after almost 10 hours of testing, it showed "100 warnings", but no errors. The warnings only occur at the beginning of a new test string, just as in the previous P95 test, after ~47 minutes. P95 completed almost 10 hours of tests on this PC without a single error. The only time it shows an indicated issue is at the beginning of a test when launching a new string.

Whomever is responsible for the P95 stress testing program might want to take a look and/or conduct their own tests with an AMD FX processor to see if they can determine why there are (100) warnings, but no errors. If this is a signal ringing issue, maybe the warning threshold needs to be raised to (1000) or something to compensation for false warnings and improper stoppage of the test?

Code:
[Jan 27 02:44] Worker starting
[Jan 27 02:44] Setting affinity to run worker on logical CPU #7
[Jan 27 02:44] Beginning a continuous self-test to check your computer.
[Jan 27 02:44] Please read stress.txt. Choose Test/Stop to end this test.
[Jan 27 02:44] Test 1, 180000 Lucas-Lehmer iterations of M580673 using AMD K10 type-1 FFT length 28K, Pass1=112, Pass2=256.
[Jan 27 02:45] Test 2, 180000 Lucas-Lehmer iterations of M573441 using AMD K10 type-1 FFT length 28K, Pass1=112, Pass2=256.
[Jan 27 02:46] Test 3, 180000 Lucas-Lehmer iterations of M565247 using AMD K10 type-1 FFT length 28K, Pass1=112, Pass2=256.
 
SNIP
 
[Jan 27 03:00] Self-test 28K passed!
[Jan 27 03:00] Test 1, 800000 Lucas-Lehmer iterations of M172031 using AMD K10 type-1 FFT length 8K, Pass1=32, Pass2=256.
[Jan 27 03:01] Test 2, 800000 Lucas-Lehmer iterations of M163839 using AMD K10 type-1 FFT length 8K, Pass1=32, Pass2=256.
[Jan 27 03:02] Test 3, 800000 Lucas-Lehmer iterations of M159745 using AMD K10 type-1 FFT length 8K, Pass1=32, Pass2=256.
[Jan 27 03:03] Test 4, 800000 Lucas-Lehmer iterations of M157695 using AMD K10 type-1 FFT length 8K, Pass1=32, Pass2=256.
[Jan 27 03:15] Self-test 8K passed!
 
SNIP
 
[Jan 27 07:41] Test 1, 800000 Lucas-Lehmer iterations of M159745 using AMD K10 type-0 FFT length 10K, Pass1=40, Pass2=256.
[Jan 27 07:43] Test 2, 800000 Lucas-Lehmer iterations of M157695 using AMD K10 type-0 FFT length 10K, Pass1=40, Pass2=256.
[Jan 27 07:45] Test 3, 800000 Lucas-Lehmer iterations of M155649 using AMD K10 type-0 FFT length 10K, Pass1=40, Pass2=256.
[Jan 27 07:47] Test 4, 800000 Lucas-Lehmer iterations of M153599 using [Jan 27 07:56] Test 9, 560000 Lucas-Lehmer iterations of M212991 using AMD K10 type-0 FFT length 10K, Pass1=40, Pass2=256.
[Jan 27 07:57] Self-test 10K passed!
 
SNIP
 
[Jan 27 09:48] Test 1, 800000 Lucas-Lehmer iterations of M159745 using AMD K10 type-0 FFT length 12K, Pass1=48, Pass2=256.
[Jan 27 09:50] Test 2, 800000 Lucas-Lehmer iterations of M157695 using AMD K10 type-0 FFT length 12K, Pass1=48, Pass2=256.
[Jan 27 09:52] Test 3, 800000 Lucas-Lehmer iterations of M155649 using AMD K10 type-0 FFT length 12K, Pass1=48, Pass2=256.
[Jan 27 09:55] Test 4, 800000 Lucas-Lehmer iterations of M153599 using [Jan 27 10:03] Test 8, 800000 Lucas-Lehmer iterations of M135169 using AMD K10 type-0 FFT length 12K, Pass1=48, Pass2=256.
[Jan 27 10:05] Self-test 12K passed!
 
SNIP
 
[Jan 27 10:05] Test 1, 120000 Lucas-Lehmer iterations of M778241 using AMD K10 type-1 FFT length 56K, Pass1=224, Pass2=256.
[Jan 27 10:07] Test 2, 120000 Lucas-Lehmer iterations of M753663 using AMD K10 type-1 FFT length 56K, Pass1=224, Pass2=256.
[Jan 27 10:08] Test 3, 120000 Lucas-Lehmer iterations of M745473 using AMD K10 type-1 FFT length 56K, Pass1=224, Pass2=256.
[Jan 27 10:10] Test 4, 120000 Lucas-Lehmer iterations of M737279 using [Jan 27 10:19] Test 9, 160000 Lucas-Lehmer iterations of M644399 using AMD K10 type-1 FFT length 56K, Pass1=224, Pass2=256.
[Jan 27 10:21] Self-test 56K passed!
 
SNIP
 
[Jan 27 10:21] Test 1, 380000 Lucas-Lehmer iterations of M278527 using AMD K10 type-1 FFT length 20K, Pass1=80, Pass2=256.
[Jan 27 10:23] Test 2, 380000 Lucas-Lehmer iterations of M274335 using AMD K10 type-1 FFT length 20K, Pass1=80, Pass2=256.
[Jan 27 10:24] Test 3, 380000 Lucas-Lehmer iterations of M270335 using AMD K10 type-1 FFT length 20K, Pass1=80, Pass2=256.
[Jan 27 10:26] Test 4, 380000 Lucas-Lehmer iterations of M266241 using [Jan 27 10:34] Test 9, 460000 Lucas-Lehmer iterations of M245281 using AMD K10 type-1 FFT length 20K, Pass1=80, Pass2=256.
[Jan 27 10:36] Self-test 20K passed!
 
SNIP
 
[Jan 27 10:36] Test 1, 210000 Lucas-Lehmer iterations of M442369 using AMD K10 type-2 FFT length 32K, Pass1=128, Pass2=256.
[Jan 27 10:38] Test 2, 210000 Lucas-Lehmer iterations of M441041 using AMD K10 FFT length 32K, Pass1=128, Pass2=256.
[Jan 27 10:39] Test 3, 210000 Lucas-Lehmer iterations of M436943 using AMD K10 type-2 FFT length 32K, Pass1=128, Pass2=256.
[Jan 27 10:40] Test 4, 270000 Lucas-Lehmer iterations of M420217 using [Jan 27 10:51] Test 10, 270000 Lucas-Lehmer iterations of M376833 using AMD K10 FFT length 32K, Pass1=128, Pass2=256.
[Jan 27 10:52] Self-test 32K passed!
 
SNIP
 
[Jan 27 10:52] Test 1, 560000 Lucas-Lehmer iterations of M210415 using AMD K10 type-0 FFT length 10K, Pass1=40, Pass2=256.
[Jan 27 10:54] Test 2, 560000 Lucas-Lehmer iterations of M208897 using AMD K10 type-0 FFT length 10K, Pass1=40, Pass2=256.
[Jan 27 10:55] Test 3, 560000 Lucas-Lehmer iterations of M204799 using AMD K10 type-0 FFT length 10K, Pass1=40, Pass2=256.
[Jan 27 10:56] Test 4, 560000 Lucas-Lehmer iterations of M200705 using [Jan 27 11:07] Test 12, 800000 Lucas-Lehmer iterations of M159745 using AMD K10 type-0 FFT length 10K, Pass1=40, Pass2=256.
[Jan 27 11:09] Self-test 10K passed!
 
SNIP
 
[Jan 27 12:30] Test 1, 800000 Lucas-Lehmer iterations of M135169 using AMD K10 type-1 FFT length 8K, Pass1=32, Pass2=256.
[Jan 27 12:31] Test 2, 800000 Lucas-Lehmer iterations of M172031 using AMD K10 type-1 FFT length 8K, Pass1=32, Pass2=256.
[Jan 27 12:32] Test 3, 800000 Lucas-Lehmer iterations of M163839 using AMD K10 type-1 FFT length 8K, Pass1=32, Pass2=256.
[Jan 27 12:33] Test 4, 800000 Lucas-Lehmer iterations of M159745 using AMD K10 type-1 FFT length 8K, Pass1=32, Pass2=256.
[Jan 27 12:34] ERROR: ILLEGAL SUMOUT
[Jan 27 12:34] Possible hardware failure, consult readme.txt file, restarting test.
[Jan 27 12:34] ERROR: ILLEGAL SUMOUT
[Jan 27 12:34] Possible hardware failure, consult readme.txt file, restarting test.
 
*SNIP*
 
[Jan 27 12:34] Possible hardware failure, consult readme.txt file, restarting test.
[Jan 27 12:34] ERROR: ILLEGAL SUMOUT
[Jan 27 12:34] Maximum number of warnings exceeded.
[Jan 27 12:34] Torture Test completed 424 tests in 9 hours, 50 minutes - 0 errors, 100 warnings.
[Jan 27 12:34] Worker stopped.

Last fiddled with by Batalov on 2013-01-27 at 21:23 Reason: wrapped in a [code] block
Jorge is offline   Reply With Quote