Time error

8 ball · 2003-03-18, 12:50

Hi, i'm torture testing a system here, it ran the test 15 hrs before i decided to call it quits, only anomally was the time taken was 10555 hours or something like that after i ended it

Its 100% stable and runs its hours on end, only thing wrong is the damn time report! Now, little history, the RAM was set too too agressive timings and caused constant failures, and it used to report the time correct, but once i had that same error after it failed on too low latency settings, now its 100% stable but the timings are still whacked lol, could the memory error at the time have damaged the program files some way? if i run it for an hour or 2 it reports right. System is a MSI K7n2L and XP 2700+ with 2 sticks of corsair xms 2700 cas 2, hercules radeon 9700 and a 430w antec truepower. The problem was not heat related as my temps are 51c load, i'm not too stressed about this as it runs the torture fine, just fascinated as to why it reported the time wrong. Thanks!

8 ball · 2003-03-19, 20:16

No one? :(

xtreme2k · 2003-03-19, 20:51

Try download the latest Prime95 again and see if it helps. Personally I wouldn't be worrying too much if that is the ONLY problem.

Prime95 · 2003-03-19, 21:54

You're apparently alone with this problem. I looked at the code and can't see where a bogus time would come from. Two possible scenarios:

1) The start_time local variable on the stack was trashed. Unlikely that
a bug or memory corruption would trash this one value and cause no
other problems.

2) The system time was reset during the torture test.

Is the bogus time repeatable? Does it happen on a short torture test run?

8 ball · 2003-03-20, 00:59

solved then! i remember changing the time cause i had reset the BIOS, probably when P95 was active as well!

2003-03-18, 12:50	#1
8 ball Mar 2003 11 Posts	Time error Hi, i'm torture testing a system here, it ran the test 15 hrs before i decided to call it quits, only anomally was the time taken was 10555 hours or something like that after i ended it Its 100% stable and runs its hours on end, only thing wrong is the damn time report! Now, little history, the RAM was set too too agressive timings and caused constant failures, and it used to report the time correct, but once i had that same error after it failed on too low latency settings, now its 100% stable but the timings are still whacked lol, could the memory error at the time have damaged the program files some way? if i run it for an hour or 2 it reports right. System is a MSI K7n2L and XP 2700+ with 2 sticks of corsair xms 2700 cas 2, hercules radeon 9700 and a 430w antec truepower. The problem was not heat related as my temps are 51c load, i'm not too stressed about this as it runs the torture fine, just fascinated as to why it reported the time wrong. Thanks!

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
ERROR: cudaGetLastError() returned 30: unknown error	garo	GPU Computing	10	2013-04-27 19:01
Problem / Error using the "Time..." option	petrw1	PrimeNet	1	2011-07-04 17:04
Ran Prime For The First Time With Fatal Error	SethNKC	Information & Answers	3	2009-02-22 19:38
Error 5 causes userid change and error 17 updates for exponents	Old man PrimeNet	PrimeNet	0	2006-02-05 02:27
ERROR: Primenet error 2252. Q: which tcp/ip ports are being used for the transfer?	nevillednz	PrimeNet	15	2004-05-17 23:08

2003-03-19, 20:51	#3
xtreme2k Aug 2002 2×3×29 Posts	Try download the latest Prime95 again and see if it helps. Personally I wouldn't be worrying too much if that is the ONLY problem.

2003-03-19, 21:54	#4
Prime95 P90 years forever! Aug 2002 Yeehaw, FL 3⁵×31 Posts	You're apparently alone with this problem. I looked at the code and can't see where a bogus time would come from. Two possible scenarios: 1) The start_time local variable on the stack was trashed. Unlikely that a bug or memory corruption would trash this one value and cause no other problems. 2) The system time was reset during the torture test. Is the bogus time repeatable? Does it happen on a short torture test run?

2003-03-20, 00:59	#5
8 ball Mar 2003 11 Posts	solved then! i remember changing the time cause i had reset the BIOS, probably when P95 was active as well!