![]() |
Prime 95 25.7 and 25.8 crashes on my 233MMX.
'Trial factoring to low limits' using version 25.7 or 25.8 doesn't work on my P233MMX machine.
My assignment was to factor M102962627 from 2^57 to 2^63. After a minute, Prime 95 crashes, and disappears, and a box appears which says "prime95.exe has generated errors and will be closed by Windows. You will need to restart the program. An error log is being created." I have tried running the program several times, and it crashes every time. I already had the same problem with version 25.7b3, so I upgraded to 25.8b2, but that has just the same problem. Incidently, I tried running that assignment using version 24.14, without any problems. No debug information is written to prime.log. Drwtsn32.log has much to say, but unfortunately I don't understand any of it! [CODE]Application exception occurred: App: (pid=884) When: 12/10/2008 @ 18:15:22.391 Exception number: c0000005 (access violation) *----> System Information <----* Computer Name: 54EF1CEBCBFF40A User Name: Administrator Number of Processors: 1 Processor Type: x86 Family 5 Model 4 Stepping 3 Windows 2000 Version: 5.0 Current Build: 2195 Service Pack: 4 Current Type: Uniprocessor Free Registered Organization: Registered Owner: *----> Task List <----* 0 Idle.exe 8 System.exe 160 SMSS.exe 188 CSRSS.exe 208 WINLOGON.exe 236 SERVICES.exe 248 LSASS.exe 428 svchost.exe 456 spoolsv.exe 488 svchost.exe 532 jqs.exe 568 regsvc.exe 592 mstask.exe 672 WinMgmt.exe 704 svchost.exe 780 explorer.exe 736 mixer.exe 896 jusched.exe 904 WZQKPICK.exe 1128 svchost.exe 884 prime95.exe 296 DRWTSN32.exe 0 _Total.exe (00400000 - 0085F000) (77F80000 - 77FFC000) (75030000 - 75044000) (78000000 - 78045000) (7C570000 - 7C623000) (7C2D0000 - 7C335000) (77D30000 - 77DA8000) (75020000 - 75028000) (77570000 - 775A0000) (77E10000 - 77E79000) (77F40000 - 77F7F000) (76B30000 - 76B6E000) (70BD0000 - 70C35000) (71710000 - 71794000) (7CF30000 - 7D186000) (77800000 - 7781E000) (76620000 - 76631000) (681A0000 - 681A7000) (66740000 - 66747000) (69BF0000 - 69C0D000) (77950000 - 7797B000) (75150000 - 75160000) (77BF0000 - 77C01000) (77980000 - 779A4000) (75050000 - 75058000) (7CDC0000 - 7CE13000) (751C0000 - 751C6000) (7C340000 - 7C34F000) (7CE20000 - 7CF21000) (70200000 - 70295000) (7C740000 - 7C7CC000) (77430000 - 77441000) (779B0000 - 77A4B000) (774E0000 - 77514000) (774C0000 - 774D1000) (77530000 - 77552000) (77830000 - 7783E000) (7C0F0000 - 7C154000) (7CA00000 - 7CA23000) (74FD0000 - 74FEE000) (75010000 - 75017000) (782C0000 - 782CC000) (77340000 - 77353000) (77520000 - 77525000) (77320000 - 77337000) (773B0000 - 773DF000) (77380000 - 773A3000) (77880000 - 7790E000) (77360000 - 77379000) (777E0000 - 777E8000) (777F0000 - 777F5000) State Dump for Thread Id 0x378 eax=008dd47c ebx=00000000 ecx=a030d478 edx=00000000 esi=00136428 edi=001363f8 eip=77e41eb3 esp=0012fe60 ebp=0012fe80 iopl=0 nv up ei pl zr na po nc cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00200246 function: DispatchMessageW 77e41e99 e8349dffff call GetFocus+0x50 (77e3bbd2) 77e41e9e e93effffff jmp GetWindowLongW+0x681 (77e41de1) 77e41ea3 90 nop 77e41ea4 90 nop 77e41ea5 90 nop 77e41ea6 90 nop 77e41ea7 90 nop 77e41ea8 b89a110000 mov eax,0x119a 77e41ead 8d542404 lea edx,[esp+0x4] ss:00ba9d47=???????? 77e41eb1 cd2e int 2e 77e41eb3 c21000 ret 0x10 77e41eb6 90 nop 77e41eb7 90 nop 77e41eb8 90 nop 77e41eb9 90 nop 77e41eba 90 nop *----> Stack Back Trace <----* FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name 0012FE80 007D2635 00136428 00000000 00000000 00000000 user32!DispatchMessageW 00000000 00000000 00000000 00000000 00000000 00000000 !<nosymbols> *----> Raw Stack Dump <----* 0012fe60 7d 79 e2 77 28 64 13 00 - 00 00 00 00 00 00 00 00 }y.w(d.......... 0012fe70 00 00 00 00 00 00 00 00 - 28 64 13 00 f8 63 13 00 ........(d...c.. 0012fe80 00 00 00 00 35 26 7d 00 - 28 64 13 00 00 00 00 00 ....5&}.(d...... 0012fe90 00 00 00 00 00 00 00 00 - 28 64 13 00 b8 19 84 00 ........(d...... 0012fea0 8e 23 7d 00 b8 19 84 00 - b8 19 84 00 60 ff 12 00 .#}.........`... 0012feb0 ff ff ff ff 02 00 00 00 - f8 63 13 00 6e 2e 81 00 .........c..n... 0012fec0 93 08 00 00 02 00 00 00 - 01 00 00 00 b4 4d 7f 00 .............M.. 0012fed0 00 00 40 00 00 00 00 00 - 03 35 13 00 01 00 00 00 ..@......5...... 0012fee0 ae 75 53 c3 6f 00 63 00 - 75 00 6d 00 00 f0 fd 7f .uS.o.c.u.m..... 0012fef0 44 00 00 00 08 3f 13 00 - 18 3f 13 00 30 3f 13 00 D....?...?..0?.. 0012ff00 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................ 0012ff10 00 00 00 00 00 00 00 00 - 00 00 00 00 01 04 00 00 ................ 0012ff20 01 00 00 00 00 00 00 00 - 00 00 00 00 01 00 01 00 ................ 0012ff30 00 00 00 00 5c ff 12 00 - 00 00 00 00 05 00 00 00 ....\........... 0012ff40 00 00 00 00 6f 00 63 00 - e0 fe 12 00 d6 84 c9 19 ....o.c......... 0012ff50 e0 ff 12 00 10 99 7f 00 - 7e fd c2 c3 01 00 00 00 ........~....... 0012ff60 c0 ff 12 00 ef 66 40 00 - 44 00 00 00 08 3f 13 00 .....f@.D....?.. 0012ff70 18 3f 13 00 30 3f 13 00 - 00 00 00 00 00 00 00 00 .?..0?.......... 0012ff80 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................ 0012ff90 00 00 00 00 01 04 00 00 - 01 00 00 00 00 00 00 00 ................ State Dump for Thread Id 0x3c4 eax=00841b38 ebx=00f7ff1c ecx=00000000 edx=00000000 esi=77f88f08 edi=000000c0 eip=77f88f13 esp=00f7ff00 ebp=00f7ff24 iopl=0 nv up ei ng nz ac pe cy cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000293 function: ZwWaitForSingleObject 77f88f08 b8ea000000 mov eax,0xea 77f88f0d 8d542404 lea edx,[esp+0x4] ss:019f9de7=002c9d00 77f88f11 cd2e int 2e 77f88f13 c20c00 ret 0xc 77f88f16 8bff mov edi,edi *----> Stack Back Trace <----* FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name 00F7FF24 7C57B3DB 000000C0 001AF270 00000000 0044E007 ntdll!ZwWaitForSingleObject 0000000D 00000000 00000000 00000000 00000000 00000000 kernel32!WaitForSingleObject *----> Raw Stack Dump <----* 00f7ff00 30 a0 59 7c c0 00 00 00 - 00 00 00 00 1c ff f7 00 0.Y|............ 00f7ff10 00 00 00 00 00 00 00 00 - 00 00 00 00 00 c9 61 e3 ..............a. 00f7ff20 fb ff ff ff 0d 00 00 00 - db b3 57 7c c0 00 00 00 ..........W|.... 00f7ff30 70 f2 1a 00 00 00 00 00 - 07 e0 44 00 c0 00 00 00 p.........D..... 00f7ff40 70 f2 1a 00 3e 30 43 00 - 30 1b 84 00 e6 06 00 00 p...>0C.0....... 00f7ff50 22 f9 12 00 d0 5c c8 00 - b0 ff f7 00 e0 5c c8 00 "....\.......\.. 00f7ff60 77 05 40 49 00 00 00 00 - 5d 0c 40 49 00 00 00 00 w.@I....].@I.... 00f7ff70 5d e0 44 00 00 00 00 00 - 00 f9 12 00 8e 9e 7f 00 ].D............. 00f7ff80 d0 5c c8 00 7e 75 b6 c3 - 22 f9 12 00 00 f9 12 00 .\..~u.."....... 00f7ff90 e0 5c c8 00 84 ff f7 00 - 84 ff f7 00 dc ff f7 00 .\.............. 00f7ffa0 dc ff f7 00 10 99 7f 00 - 76 f3 c2 c3 00 00 00 00 ........v....... 00f7ffb0 ec ff f7 00 27 9f 7f 00 - 88 b3 57 7c e0 5c c8 00 ....'.....W|.\.. 00f7ffc0 22 f9 12 00 00 f9 12 00 - e0 5c c8 00 00 c0 fd 7f "........\...... 00f7ffd0 c0 fb 12 00 c0 ff f7 00 - c0 fb 12 00 ff ff ff ff ................ 00f7ffe0 54 1f 5c 7c 08 2b 57 7c - 00 00 00 00 00 00 00 00 T.\|.+W|........ 00f7fff0 00 00 00 00 b4 9e 7f 00 - e0 5c c8 00 00 00 00 00 .........\...... 00f80000 c8 00 00 00 00 01 00 00 - ff ee ff ee 02 10 00 00 ................ 00f80010 00 00 00 00 00 fe 00 00 - 00 00 10 00 00 20 00 00 ............. .. 00f80020 00 02 00 00 00 20 00 00 - 9d 00 00 00 ff ef fd 7f ..... .......... 00f80030 06 00 08 06 00 00 00 00 - 00 00 00 00 00 00 00 00 ................ State Dump for Thread Id 0x2d0 eax=00149000 ebx=00000004 ecx=015bf9cc edx=00000000 esi=77f88ef8 edi=00000004 eip=77f88f03 esp=015bfd24 ebp=015bfd70 iopl=0 nv up ei pl zr na po nc cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000246 function: NtWaitForMultipleObjects 77f88ef8 b8e9000000 mov eax,0xe9 77f88efd 8d542404 lea edx,[esp+0x4] ss:02039c0b=???????? 77f88f01 cd2e int 2e 77f88f03 c21400 ret 0x14 77f88f06 8bff mov edi,edi *----> Stack Back Trace <----* FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name 015BFD70 7C59A10E 015BFD48 00000001 00000000 00000000 ntdll!NtWaitForMultipleObjects 015BFFB4 7C57B388 00000005 7FFDD000 7C3280D0 00146EC8 kernel32!WaitForMultipleObjects 015BFFEC 00000000 00000000 00000000 00000000 00000000 kernel32!lstrcmpiW State Dump for Thread Id 0x3a0 eax=20000008 ebx=0ffa7cbc ecx=fffff5ae edx=0000001d esi=01a50004 edi=fffffffe eip=00404239 esp=019d20fc ebp=5dbcfb89 iopl=0 nv up ei ng nz na pe nc cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00200282 function: <nosymbols> 00404220 d8cb fmul st,st(3) 00404222 dd842420050000 ss:019d261c=2000000043aff4f9 fld qword ptr [esp+0x520] 00404229 d9cc fxch st(4) 0040422b d8c8 fmul st,st(0) 0040422d d9ce fxch st(6) 0040422f dee9 fsubrp st(1),st 00404231 d9cb fxch st(3) 00404233 d8ca fmul st,st(2) 00404235 d9cc fxch st(4) 00404237 d9e1 fabs FAULT ->00404239 d88c8c48080000 fmul dword ptr [esp+ecx*4+0x848] ss:fffffdf6=???????? 00404240 d9cb fxch st(3) 00404242 dec1 faddp st(1),st 00404244 d9c9 fxch st(1) 00404246 dc8c2430050000 ss:019d262c=c1caa998d7800000 fmul qword ptr [esp+0x530] 0040424d d9ca fxch st(2) 0040424f dca42418050000 ss:019d2614=8a00000000000000 fsub qword ptr [esp+0x518] 00404256 d9cb fxch st(3) 00404258 dee9 fsubrp st(1),st 0040425a d9c9 fxch st(1) 0040425c deeb fsubrp st(3),st 0040425e d9c9 fxch st(1) *----> Stack Back Trace <----* FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name 5DBCFB89 00000000 00000000 00000000 00000000 00000000 !<nosymbols> *----> Raw Stack Dump <----* 019d20fc ee 3e 40 00 c3 15 23 06 - 00 00 00 00 00 00 00 00 .>@...#......... 019d210c bc 7c fa 0f 00 00 00 00 - 21 00 00 00 01 00 00 00 .|......!....... 019d211c 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................ 019d212c 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................ 019d213c 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................ 019d214c 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................ 019d215c 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................ 019d216c 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................ 019d217c 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................ 019d218c 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................ 019d219c 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................ 019d21ac 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................ 019d21bc 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................ 019d21cc 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................ 019d21dc 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................ 019d21ec 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................ 019d21fc 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................ 019d220c 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................ 019d221c 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................ 019d222c 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................[/CODE] |
Email your worktodo.txt file and the fXXXXXXX save file. I can't reproduce it here, so it must be data-specific.
In the meantime, place a semicolon in front of the line in worktodo.txt. Hopefully the next exponent won't cause any trouble. |
Sorry, I can't, because I moved the folder from my 233MMX onto my Celeron machine, finished the work and then moved it back onto the 233MMX to report the results.
Shall I download some more similar work and see if it crashes again? Edit: Of course I should! |
Fixed in 25.8 build 3. Available for Windows now
|
Version 25.8 build 3 is now running fine on my 233MMX, so thank you George, for compiling a new build specially for me and my old computer!
As the size of the exponents we are working on grows ever larger, low-level trial factoring is about the only useful work my 233MMX can still do in a reasonable time, so I'm happy that my machine can now continue with this project. |
Build 3 has been working fine now on my 233MMX, so I thought it would be safe to upgrade to Build 4, but after I did I have received a couple of errors, where a wrong factor is found.
[Mon Dec 15 12:46:13 2008] UID: M0CZY/233MMX, M104574091 no factor from 2^62 to 2^63, Wd1: EBB0B7EC, AID: 7B6D708E293AF76D5A39833276DB715A ERROR: Incorrect factor found. [Mon Dec 15 13:02:42 2008] ERROR: Incorrect factor found. UID: M0CZY/233MMX, M104574103 has a factor: 145759997341466624, AID: 4DBD4F3C1B9A75B53F653FED23B2BDAC That must be wrong, how can a Mersenne number have a factor that is an even number? For now, I am going to keep a close eye on the output, as I would hate to be sending incorrect results back to the server. |
ERROR: Incorrect factor found.
The Incorrect factor found error is reproducible on my 233MMX: I ran
Factor=4DBD4F3C1B9A75B53F653FED23B2BDAC,104574103,57,63 several times, and it kept coming up with the same wrong factor ERROR: Incorrect factor found. M104574103 has a factor: 145759997341466624, AID: 4DBD4F3C1B9A75B53F653FED23B2BDAC When I ran the same exponent several times on my Celeron D machine it always came up with M104574103 has a factor: 146210891985618697, AID: 4DBD4F3C1B9A75B53F653FED23B2BDAC which I believe is the correct factor. When I tried using Version 24.14 it also found the correct factor [Mon Dec 15 18:32:35 2008] M104574103 has a factor: 146210891985618697 |
[QUOTE=M0CZY;153559]The Incorrect factor found error is reproducible on my 233MMX: I ran
Factor=4DBD4F3C1B9A75B53F653FED23B2BDAC,104574103,57,63 several times, and it kept coming up with the same wrong factor ERROR: Incorrect factor found. M104574103 has a factor: 145759997341466624, AID: 4DBD4F3C1B9A75B53F653FED23B2BDAC When I ran the same exponent several times on my Celeron D machine it always came up with M104574103 has a factor: 146210891985618697, AID: 4DBD4F3C1B9A75B53F653FED23B2BDAC which I believe is the correct factor. When I tried using Version 24.14 it also found the correct factor [Mon Dec 15 18:32:35 2008] M104574103 has a factor: 146210891985618697[/QUOTE] 146210891985618697 is the correct factor. Luigi |
Yes, I thought that was the correct factor.
I am stopping work with my 233MMX, because I don't want to report any incorrect factors to the server, and also because there is a chance that my machine might be missing factors that it should have found. |
I've been able to reproduce the problem. I'll hunt the bug down this afternoon.
|
Fixed in 25.8 build 5 - now available for Windows only.
The good news is that it wasn't missing any factors - just not reporting found factors properly. |
Build 5 seems to be working on my 233MMX, so it looks like I'm back in the game, so many thanks.
Lets hope that the Prime 95 software doesn't have to go through as many bug fix changes as the BOINC software has! |
would it help if prime95 checked for updates at startup and then installed the updates automatically
is that a route worth going down |
[QUOTE=henryzz;153737]would it help if prime95 checked for updates at startup and then installed the updates automatically
is that a route worth going down[/QUOTE] When that was suggested years ago, the majority were against the idea. |
[QUOTE=Prime95;153748]When that was suggested years ago, the majority were against the idea.[/QUOTE]
I'm still against the idea... Luigi |
[quote=ET_;153750]I'm still against the idea...
Luigi[/quote] Even if it is optional to disable? I think it would be quite helpful for some PC's where you haven't quick access to, ore quite many of them.... |
[QUOTE=Phantomas;153751]Even if it is optional to disable?
I think it would be quite helpful for some PC's where you haven't quick access to, ore quite many of them....[/QUOTE] - I think to Primenet v4-Primenet v5 transition... - Not all versions of Prime95 are indicated to download. - I got a Pentium III happily crunching with version 23.6 when version 24.14 was slower for P III. - "Borged" PCs usually have slow dial-up connections. - Pinging the server for a new version is a loss of crunching time :smile: . - Pushing a new executable version from the server should be programmed from web interface, not from client. Again, bandwidth problems. - The algorithm should be ready to recognize service versions and different OSes. - In some cases the software is run from a batch file. Luigi |
[QUOTE=Prime95;153625]Fixed in 25.8 build 5 - now available for Windows only.
The good news is that it wasn't missing any factors - just not reporting found factors properly.[/QUOTE] George, would it make sense to supplement (or replace) the factor printout with the factor k (i.e. the index k in factor q = 2*k*p+1 of 2^p-1). That could provide a valuable checksum in such cases, and avoid some of the problems with too-long factors in the primenet logs. |
[QUOTE=ewmayer;153774]George, would it make sense to supplement (or replace) the factor printout with the factor k (i.e. the index k in factor q = 2*k*p+1 of 2^p-1). That could provide a valuable checksum in such cases, and avoid some of the problems with too-long factors in the primenet logs.[/QUOTE]
I guess a user of Prime95 would be more excited saying "I got factor x" than computing the factor from k. How many gimpsters would understand it? I had similar doubts using "Factor" (the original one) and learnt the connection between a Mersenne factor and k only after coding my own applet... Luigi |
[QUOTE=ewmayer;153774]George, would it make sense to supplement (or replace) the factor printout with the factor k .[/QUOTE]
I don't see how that is beneficial. The client verifies any factors found (25.8 build 4 had a bug where escaping out of the 5 minute sleep bypassed this check). Plus, the server verifies every incoming factor. |
[QUOTE=Prime95;153748]When that was suggested years ago, the majority were against the idea.[/QUOTE]I thing automagic updating is probably a bad idea, but manual checking and (optional) automatic installation of an updated version on user request could be useful. That is, there could be a [i]Help | Check for updates[/i] menu item that would come back with one of:
> "You already have the latest version (v25.x.x)" or > "You are running v25.x.x, there is a newer version available (v25.y.y) [auto-install] [download & manual install] [visit download webpage] [cancel]". The autoinstall process may take some work to implement, but it should be relatively trivial to add a check-to-see-if-this-version-is-latest feature into Prime95/PrimeNet, with a link to the download page for the latest version, and I think that would be a useful addition. |
| All times are UTC. The time now is 13:59. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2021, Jelsoft Enterprises Ltd.