bob4432
Lifer
Originally posted by: Vyruz
hmm, i came home right now, and when i looked at the pc, prime 95 had encoutered an error:
[Thu Aug 18 23:49:28 2005]
Compare your results to other computers at http://www.mersenne.org/bench.htm
That web page also contains instructions on how your results can be included.
AMD Athlon(tm) 64 X2 Dual Core Processor 4400+
CPU speed: 2211.11 MHz
CPU features: RDTSC, CMOV, Prefetch, 3DNow!, MMX, SSE, SSE2
L1 cache size: 64 KB
L2 cache size: 1024 KB
L1 cache line size: 64 bytes
L2 cache line size: 64 bytes
L1 TLBS: 32
L2 TLBS: 512
Prime95 32-bit version 24.13, RdtscTiming=1
Best time for 512K FFT length: 21.135 ms.
Best time for 640K FFT length: 27.596 ms.
Best time for 768K FFT length: 33.539 ms.
Best time for 896K FFT length: 40.072 ms.
Best time for 1024K FFT length: 44.796 ms.
Best time for 1280K FFT length: 57.031 ms.
[Fri Aug 19 08:54:51 2005]
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
so i had a look at the nMonitor log files:
it seems that at 3.20PM this afternoon, the program stopped logging my CPU temperature, only me 2 GPU temps
take a look at these excel sheets :
www.fastlikehell.com/temp/p95.xls
you can see that the in the first logfile in the beginning there are still loggings of my CPU temp, then suddenly it disappears and moves to two GPU temps to the left
in the second log file it even removes the "cpu temperature" column completely
also, after i saw the prime 95 error, i wanted to post it on this board, and when i tried to open up firefox i got a bluescreen directly followed by a reboot
event viewer shows the following things:
_________________________________________________________________________________________________
"Error code 1000008e, parameter1 c000001d, parameter2 805bc341, parameter3 b9fc9b3c, parameter4 00000000.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp."
_________________________________________________________________________________________________
The server {51FA2736-5DEE-11D4-98E8-006008BF430C} did not register with DCOM within the required timeout.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
_________________________________________________________________________________________________
i guess i kinda found the bug, now i just need to find out why and what exactly happens
when i had an issue like that in prime95, i had a memory problem, one was bad the other was good. maybe take out 3 sticks and run memtest overnight again on each stick and see who is the culprit (but the error will probably show up in less than 1 hour). i know it sounds like a pain in the ass, but that is what i did. also, did you do the tortue test?