False primes!

[Skligmund]

If I remember correctly, you have an OEM computer (like Dell, Gateway, eMachines ect) so you may not have the option to do so in your BIOS.

I have to ask you a couple questions before I can help, so I know where to go.

1. What make AND model computer do you have?
2. ...

Well, I should be able to figure out everything else after that. Unless you changed something like CPU, RAM or Video card ect. If you did, let me know. We'll go from there.

[KEP]

Originally Posted by Skligmund

If I remember correctly, you have an OEM computer (like Dell, Gateway, eMachines ect) so you may not have the option to do so in your BIOS.

I have to ask you a couple questions before I can help, so I know where to go.

1. What make AND model computer do you have?
2. ...

Well, I should be able to figure out everything else after that. Unless you changed something like CPU, RAM or Video card ect. If you did, let me know. We'll go from there.

The Make and Model is none, since it was a cheap "build by salesman" computer, so it consist of a lot of different types of hardware, properbly a lot of crapy hardware, since i had it for only a year or so, before the mainboard burned off, so I guess the answer to your question has to be a little woobly... maybe when I return to my computer tomorrow afternoon, I can try to see what I can find out...

[Rytis]

This one is by KEP.

(I had the last erroneous prime in mind)

[KEP]

Originally Posted by Rytis

This one is by KEP.

(I had the last erroneous prime in mind)

It may almost have been one of the few primes that I had, that didn't get double checked, but it also has something to do with the LLR program it self, since I have no other errors than download errors when using all other BOINC applications... anyway, Rytis do you think that you have some information on the make and model of my RAM? It would really help a lot, since there isn't much info to gather on the RAM itself, and the hardware list, that came with my computer, is hopelessly outdated, and doesn't contain much info either.

Regards!

[smh]

Originally Posted by KEP

It makes no sence, since it stops after the first test, and then concludes "somekind of hardware error", and that doesn't make me any more alert to what the problem is, so I'm at best left confused by using the Prime95 torture test, and to think that I should run it for 48 hours, first off it's not possible, since it stops as mentioned after the second test, and secondly, i wan't waste time on that, since there are lots of Distributed Computing projects, that my computer can still return perfectly valid results to, despite the apparent hardware error, so I think it also may have something to do with the construction of the LLR 3.7.1 program, since there hasn't been any problems, since I switched to BOINC LLR. Sorry for the long sentence...

I suggested 48 hours, but if the error pops up at the second test, you definitely have a problem. The fact that it doesn't show (you disabled error reporting remember) doesn't mean it's not there.

You did not btw, report all perfectly valid results.

You can't blame LLR for errors that you found with Prime95. You have either a hardware or a software problem if you can't run a prime95 torture test for several hours.

Originally Posted by KEP

I'm by the way glad that you decided not to leave the TPS project anyway smh, you're very welcome to support the project, and I guess that you may have considered me hostile, as well as I considered you to be hostile towards Rytis, because we have no visiuals of one an other, but since this is a new year, I'll offer you my hand as a good guesture, and hope to see ud co-exist on the message board, as well as various prime projects, as friends in stead of enemies. Life is simply to short to be enemies, and sadly not long enough, to accomplish all the prime goals that one can imagine...

I didn't leave TPS, but i haven't decided if i want to run PG. Most hardware i have available is doing NFS factoring anyway.

Anyway, no hard feelings

[Jean Penné]

Here are my results using LLR 3.7.1 :

1227950103*2^195000-1 is not prime. LLR Res64: 5012A1813BAD3E22 Time : 141.080 sec.
1418514507*2^195000-1 is not prime. LLR Res64: 3AD50115CAEA0FC2 Time : 143.033 sec.
1949806593*2^195000-1 is not prime. LLR Res64: 8B770930ABC5E5EA Time : 133.622 sec.

I hope are you now finding the same residues when using LLR!

Let me know if I am wrong...
Thank you by advance,
Jean

[Skligmund]

KEP:

Very small, great little program I install first thing on every computer I own. Use this, and you can even send me the results on the 'HTML Dump' or 'Text Dump' in the 'About' tab, or post them here.

http://www.cpuid.com/cpuz.php

[Padanian]

It's irrelevant whether few primes are invalid. The scope of the project is to find the biggest twin prime, which was found, checked and confirmed.

[MooMoo2]

Originally Posted by Padanian

It's irrelevant whether few primes are invalid. The scope of the project is to find the biggest twin prime, which was found, checked and confirmed.

Having all primes listed accurately will be important for the next n, since the (non-twin) primes will be large enough for the top 5000 list.

[jmblazek]

Reviewing the log file, I found the following k that were only tested once. The 3 k's listed in red were false positives (and match the ones MooooMoo already found). All the rest checked out OK (LLR 3.7.0). PG's total primes found goes from 356 to 353.

Note: one observation is 1949806593*2^195000-1. The rest of the k were grouped together...this one seems to be an outlier...a bit odd???

1080206955*2^195000-1 is prime! Time : 144.405 sec.
1080206955*2^195000+1 is not prime. Proth RES64: CF16DC89B75F0A71 Time: 145.369 sec.
1086943497*2^195000-1 is prime! Time : 144.024 sec.
1086943497*2^195000+1 is not prime. Proth RES64: 0D3EC025C92AD4CB Time: 169.645 sec.
1093603047*2^195000-1 is prime! Time : 143.844 sec.
1093603047*2^195000+1 is not prime. Proth RES64: 504FD016FFCF2458 Time: 143.742 sec.
1096601145*2^195000-1 is prime! Time : 51.317 sec.
1096601145*2^195000+1 is not prime. Proth RES64: 301E787726F990F3 Time: 149.318 sec.
1098500277*2^195000-1 is prime! Time : 154.187 sec.
1098500277*2^195000+1 is not prime. Proth RES64: 405C3C04C35BB682 Time: 162.414 sec.

1227950103*2^195000-1 is not prime. LLR Res64: 5012A1813BAD3E22 Time : 174.359 sec.

1236543297*2^195000-1 is prime! Time : 148.159 sec.
1236543297*2^195000+1 is not prime. Proth RES64: FC3D02B5FECB8C54 Time: 146.868 sec.
1237075263*2^195000-1 is prime! Time : 143.512 sec.
1237075263*2^195000+1 is not prime. Proth RES64: F93FF59D7091E867 Time: 145.419 sec.
1256680185*2^195000-1 is prime! Time : 147.604 sec.
1256680185*2^195000+1 is not prime. Proth RES64: EEABC89118487D59 Time: 145.680 sec.
1258544073*2^195000-1 is prime! Time : 158.770 sec.
1258544073*2^195000+1 is not prime. Proth RES64: A1C70EE8D9A6169B Time: 129.052 sec.
1261066875*2^195000-1 is prime! Time : 146.984 sec.
1261066875*2^195000+1 is not prime. Proth RES64: F02ADE3A121B90F2 Time: 153.958 sec.
1269689493*2^195000-1 is prime! Time : 142.814 sec.
1269689493*2^195000+1 is not prime. Proth RES64: 7862566F6F97569F Time: 142.911 sec.
1287247605*2^195000-1 is prime! Time : 142.751 sec.
1287247605*2^195000+1 is not prime. Proth RES64: 28C125112DF4D3A1 Time: 142.779 sec.
1289575443*2^195000-1 is prime! Time : 143.099 sec.
1289575443*2^195000+1 is not prime. Proth RES64: B4A3CC28EBD0E9A2 Time: 146.202 sec.
1292849397*2^195000-1 is prime! Time : 144.658 sec.
1292849397*2^195000+1 is not prime. Proth RES64: 0A044E8AB74E3F13 Time: 142.513 sec.
1295981997*2^195000-1 is prime! Time : 142.508 sec.
1295981997*2^195000+1 is not prime. Proth RES64: A9C2BBAD9DDDA4B4 Time: 142.496 sec.
1296039687*2^195000-1 is prime! Time : 160.453 sec.
1296039687*2^195000+1 is not prime. Proth RES64: FBE331EF6AA36F7C Time: 171.459 sec.
1313770323*2^195000-1 is prime! Time : 173.823 sec.
1313770323*2^195000+1 is not prime. Proth RES64: 88E40B686C4577D8 Time: 177.823 sec.
1404173505*2^195000-1 is prime! Time : 201.131 sec.
1404173505*2^195000+1 is not prime. Proth RES64: B33F58FE892FB4DB Time: 198.861 sec.

1418514507*2^195000-1 is not prime. LLR Res64: 3AD50115CAEA0FC2 Time : 149.597 sec.

1419416787*2^195000-1 is prime! Time : 206.993 sec.
1419416787*2^195000+1 is not prime. Proth RES64: 97427EE6C3AB38C4 Time: 165.234 sec.
1424654007*2^195000-1 is prime! Time : 177.556 sec.
1424654007*2^195000+1 is not prime. Proth RES64: 740CAD09E61A2614 Time: 1217.605 sec.
1427258607*2^195000-1 is prime! Time : 144.453 sec.
1427258607*2^195000+1 is not prime. Proth RES64: CC8460B8BD4F3448 Time: 144.009 sec.
1438624635*2^195000-1 is prime! Time : 159.770 sec.
1438624635*2^195000+1 is not prime. Proth RES64: 84389B9891E46A90 Time: 156.643 sec.
1440031743*2^195000-1 is prime! Time : 152.407 sec.
1440031743*2^195000+1 is not prime. Proth RES64: DE8D85726028B0AC Time: 152.009 sec.
1444835733*2^195000-1 is prime! Time : 155.562 sec.
1444835733*2^195000+1 is not prime. Proth RES64: CBA166ED88144181 Time: 154.107 sec.

1949806593*2^195000-1 is not prime. LLR Res64: 8B770930ABC5E5EA Time : 156.993 sec.

[Padanian]

Originally Posted by MooooMoo

Having all primes listed accurately will be important for the next n, since the (non-twin) primes will be large enough for the top 5000 list.

Which is NOT the scope of the project nonetheless.