Stress Prime 2004 Orthos Ed. Errors
Pterocarpous
Rosie the Riveter Lives On in CA, USA! New
Originally user had issue w/ file corruption and slow unstable system
Ran FULL Seagate Tools diag. on HDD - passed ok
Ran > 3 passes of MEMTEST86 w/ no errors
Decided to run SP2004 Orthos Ed. over night (w/in OS (XP PROSP2))
Started Test: BLEND-STRESS CPU AND RAM
Kept getting the error (w/ minor variations w/ respect to duration)
Duration: 39 seconds (varied w/in a few seconds w/ ea. test)
CPU Speed: 2992 MHz
Test: Blend- stress CPU and RAM
Message:
Press Stop to end this test
Test 1, 4000 Lucas-Lehmer iterations of M19922945 using 1024K FFT length
FATAL ERROR: Writing to temp file.
Torture Test ran 0 minutes 35 seconds - 1 errors, 0 warnings.
Execution halted.
Switched to test:
StressCPU-stress CPU with Gromacs core (So far running ok)
Other test options are:
Small FFTs-stress CPU
Large, in-place FFTs-stress some RAM
I'd be greatful for ya'll's feedback.
I'd think RAM but why would it make more than 3 passes of MEMTEST86 ok and fail almost immediately w/in OS.
Thankyou in advance
Ran FULL Seagate Tools diag. on HDD - passed ok
Ran > 3 passes of MEMTEST86 w/ no errors
Decided to run SP2004 Orthos Ed. over night (w/in OS (XP PROSP2))
Started Test: BLEND-STRESS CPU AND RAM
Kept getting the error (w/ minor variations w/ respect to duration)
Duration: 39 seconds (varied w/in a few seconds w/ ea. test)
CPU Speed: 2992 MHz
Test: Blend- stress CPU and RAM
Message:
Press Stop to end this test
Test 1, 4000 Lucas-Lehmer iterations of M19922945 using 1024K FFT length
FATAL ERROR: Writing to temp file.
Torture Test ran 0 minutes 35 seconds - 1 errors, 0 warnings.
Execution halted.
Switched to test:
StressCPU-stress CPU with Gromacs core (So far running ok)
Other test options are:
Small FFTs-stress CPU
Large, in-place FFTs-stress some RAM
I'd be greatful for ya'll's feedback.
I'd think RAM but why would it make more than 3 passes of MEMTEST86 ok and fail almost immediately w/in OS.
Thankyou in advance
0
Comments
Note: When I first started the test, I may have initiated it from my pen drive. That shouldn't matter, however, once it's in memory, right? Except it's gonna want to put the log file somewhere. When I remove the pen drive it might balk (which I did).
Later, I copied the diag off the pen drive and onto the HDD and ran it from there.
I'm going to shut it down for an hour. Unplug power. Let it cool down. Then run Orthos again in blended mode on next startup. (to see if there's a thermal-related problem....)
I'm still open to feed back. This is the first time that I've used this utility and encountered an error. In fact, this is only the 2nd system I've ever run the utility on. (I just learned about it recently here on SM.)
TIA, ya'll!
Usually more voltage is needed somewhere ...as thrax mentioned. Sometimes in mem timings can be the culprit though.
I would guess that if memtest runs fine at certain settings then ram could be ruled out.
Thankyou again.
"CPU w/ Gromacs core" test
ran 7hrs w/ no errors
"Blend - stress CPU and RAM" test
ran 2hrs 29mins w/ no errors
Shut system down and removed power for > 2hrs
"Blend - stress CPU and RAM" test
ran 18hrs 59mins w/ no errors
"Large, in-place FFTs - stress some RAM" test
ran 4hrs w/ no errors
I've come to the conclusion that yours truly introduced the errors initially generated by removing the USB pen drive that I, at first, initiated the test from. In any case I was unable to repeat those results that caused me concern in the beginning.
Thanx again!