Weird TF Behavior Prime95 64 bit v24.13, WinXP 64

RMAC9.5 · 2009-03-05, 05:52

I have an AMD Athlon X2 6400 PC running at 3.2 GHz doing TF. This PC has been running Prime95 24.13 with few problems since Dec. 2007. Recently, I have been getting Prime95 application errors when Prime95 tries to factor a number greater than M61853387. The error occurs when Prime95 tries to write out the first save file after it starts factoring. I have sent the Error reports to Microsoft but have not received any feedback. No information is saved in the Results.txt or Prime.log files. Is there a start up parameter that I can use to capture more information?

James Heinrich · 2009-03-05, 13:06

Have you tried another version of Prime95? (v25.9.2 is the most current x64 version right now)

mognuts · 2009-03-05, 16:21

Quote:

Originally Posted by James Heinrich

Have you tried another version of Prime95? (v25.9.2 is the most current x64 version right now)

I thought we were up to build 3?

James Heinrich · 2009-03-06, 05:26

Quote:

Originally Posted by mognuts

I thought we were up to build 3?

32-bit is on build 3, 64-bit is on build 2.

S485122 · 2009-03-06, 06:42

Quote:

Originally Posted by James Heinrich

32-bit is on build 3, 64-bit is on build 2.

No it is build 3 for both 32 and 64 bits : if you look at the properties of the exe included in the compressed file you pointed to, the version is 25.9.3.0. It is also the version reported by Help / About Prime95.

Jacob

RMAC9.5 · 2009-03-06, 09:00

No I haven't had time to try any of the Prime95 25.x versions, but I agree that it is a logical next step. Hopefully I will be able to do so during the upcoming weekend. However, since George has mentioned several times that he really hasn't modified the TF code in the Prime95 25.x versions, I remain cautiously optimistic.
I can report another failure (Factor=62019047,65) on a completely different PC using Prime95, version 24.13, (32 bit) and Windows XP SP 2 (32 bit).

James Heinrich · 2009-03-06, 12:42

Quote:

Originally Posted by S485122

No it is build 3 for both 32 and 64 bits

You're right -- apparently I missed the latest x64 version

Prime95 · 2009-03-06, 19:07

This is likely fixed in v25. From the code in commonc.c that generates temporary file names:

Code:

/* WARNING:  Version 24 had a bug where exponents between 61 million and */
/* 70 million used funky characters in the file name.  I've fixed the bug */
/* here, but users will have to rename some intermediate files. */

Apparently, the funky characters in the file name are causing a crash (probably from more bad code of mine where errors creating the save file aren't handled properly?).

RMAC9.5 · 2009-03-15, 09:21

George is correct about this error being fixed in v25 (verified in 25.9 build 3).
This leads to the following two questions:
1. Can the server be programmed to hand out TF assignments to v24.xx PCs which are outside of the 61 million to 70 million range? If so, TF assignments greater than 70 million could be efficiently factored to low bit levels by the v24.xx TF PCs that otherwise will stop contributing. I am making this suggestion because I have a few borged 24.xx PCs that are outside of my control, and I am sure that other long time Prime95 contributors are in the same boat.
2. Are v25 assignments "locked" to the specific PC that registered them with the the V5 server or to the user id associated with that PC? In other words, can I trade v25 assignments among the PCs that I have access to like I can with v24 assignments or do I have to unreserve them? I know how to move the "bad" unreserved v24 TF assignments from my 24.xx PCs to my v25.9 PCs by using the worktodo.add trick, but I am not sure how to proceed after the TF assignments have been registered with the V5 server.

Prime95 · 2009-03-15, 14:48

Quote:

Originally Posted by RMAC9.5

1. Can the server be programmed to hand out TF assignments to v24.xx PCs which are outside of the 61 million to 70 million range?

I've tried to implement this. It is untested.

Quote:

2. Are v25 assignments "locked" to the specific PC that registered them with the the V5 server or to the user id associated with that PC?

You can move the assignments to any other PC with the same userid. Be sure to copy that 32 hex digit assignment id too.

RMAC9.5 · 2009-03-17, 04:33

George,
I am happy to report that the server is sending out TF assignments greater than 70 million to some of my v24.13 TF PCs. The one 70 million assignment that I checked so far stopped and started normally.

Here are two more v25.9 questions.
1. What does SendAllFactorData=1 in Prime.txt do? All of the PCs that I have direct access to use dial-up modems and will continue to do so for the foreseeable future. If I set it =0, will v25.9 act like v24.13 and send the TF results at the end of the assignment, instead of at the end of each bit level?
2. Does v25.9 put a greater demand on the memory subsystem than v24.13? The reason for this question has to do with my new Phenom II X4 940 PC which happily did DCs at 3.3 GHz using v24.13 but gets "SUM(INPUTS) != SUM(OUTPUTS)" errors for LLs at anything over 3.0 GHz using v25.9.

2009-03-05, 05:52	#1
RMAC9.5 Jun 2003 3²·17 Posts	Weird TF Behavior Prime95 64 bit v24.13, WinXP 64 I have an AMD Athlon X2 6400 PC running at 3.2 GHz doing TF. This PC has been running Prime95 24.13 with few problems since Dec. 2007. Recently, I have been getting Prime95 application errors when Prime95 tries to factor a number greater than M61853387. The error occurs when Prime95 tries to write out the first save file after it starts factoring. I have sent the Error reports to Microsoft but have not received any feedback. No information is saved in the Results.txt or Prime.log files. Is there a start up parameter that I can use to capture more information?

2009-03-06, 19:07	#8
Prime95 P90 years forever! Aug 2002 Yeehaw, FL 10000001010111₂ Posts	This is likely fixed in v25. From the code in commonc.c that generates temporary file names: Code: /* WARNING: Version 24 had a bug where exponents between 61 million and / / 70 million used funky characters in the file name. I've fixed the bug / / here, but users will have to rename some intermediate files. */ Apparently, the funky characters in the file name are causing a crash (probably from more bad code of mine where errors creating the save file aren't handled properly?).

2009-03-15, 09:21	#9
RMAC9.5 Jun 2003 153₁₀ Posts	George is correct about this error being fixed in v25 (verified in 25.9 build 3). This leads to the following two questions: 1. Can the server be programmed to hand out TF assignments to v24.xx PCs which are outside of the 61 million to 70 million range? If so, TF assignments greater than 70 million could be efficiently factored to low bit levels by the v24.xx TF PCs that otherwise will stop contributing. I am making this suggestion because I have a few borged 24.xx PCs that are outside of my control, and I am sure that other long time Prime95 contributors are in the same boat. 2. Are v25 assignments "locked" to the specific PC that registered them with the the V5 server or to the user id associated with that PC? In other words, can I trade v25 assignments among the PCs that I have access to like I can with v24 assignments or do I have to unreserve them? I know how to move the "bad" unreserved v24 TF assignments from my 24.xx PCs to my v25.9 PCs by using the worktodo.add trick, but I am not sure how to proceed after the TF assignments have been registered with the V5 server. Last fiddled with by RMAC9.5 on 2009-03-15 at 09:22

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
mfaktc slows on WinXP after about an hour	Christenson	GPU Computing	5	2011-05-27 21:47
Weird Version 24.6 Trial Factoring Behavior	RMAC9.5	Software	0	2005-06-11 04:57
Prime95 create Local Disk (Z:) on WinXP?	Unregistered	Software	3	2005-02-05 16:51
crazy WinXP scheduling	stippix	Software	0	2004-04-22 08:55
WinXP P95 slowdown	sgrupp	Software	21	2003-12-28 18:48

2009-03-05, 13:06	#2
James Heinrich "James Heinrich" May 2004 ex-Northern Ontario 7×13×47 Posts	Have you tried another version of Prime95? (v25.9.2 is the most current x64 version right now)

2009-03-06, 09:00	#6
RMAC9.5 Jun 2003 3²×17 Posts	No I haven't had time to try any of the Prime95 25.x versions, but I agree that it is a logical next step. Hopefully I will be able to do so during the upcoming weekend. However, since George has mentioned several times that he really hasn't modified the TF code in the Prime95 25.x versions, I remain cautiously optimistic. I can report another failure (Factor=62019047,65) on a completely different PC using Prime95, version 24.13, (32 bit) and Windows XP SP 2 (32 bit).

2009-03-17, 04:33	#11
RMAC9.5 Jun 2003 231₈ Posts	George, I am happy to report that the server is sending out TF assignments greater than 70 million to some of my v24.13 TF PCs. The one 70 million assignment that I checked so far stopped and started normally. Here are two more v25.9 questions. 1. What does SendAllFactorData=1 in Prime.txt do? All of the PCs that I have direct access to use dial-up modems and will continue to do so for the foreseeable future. If I set it =0, will v25.9 act like v24.13 and send the TF results at the end of the assignment, instead of at the end of each bit level? 2. Does v25.9 put a greater demand on the memory subsystem than v24.13? The reason for this question has to do with my new Phenom II X4 940 PC which happily did DCs at 3.3 GHz using v24.13 but gets "SUM(INPUTS) != SUM(OUTPUTS)" errors for LLs at anything over 3.0 GHz using v25.9.