I just saved my first 2 LL tests near the wavefront. (GPU272)

M61665733 has a factor: 1242867428216309008697

k= 2*2*11*229033092049

M995699 has a factor: 714989201981049862823489485269929
k=2^2 x 13 x 61 x 3301 x 24001 x 2033287 x !702,642,949!
I *THINK* this is a B-S factor since it was found with B1=10M B2=250M E=12
109.14 bits :) My first above 100 bits!

I know it is useless but still
M8803577 completed P-1, B1=105000, B2=1916250, E=6
P-1 found a factor in stage #1, B1=105000.
UID: firejuggler, M8803573 has a factor: 589495498411470532681
k=2^2*3*5*2857*4831*40429

last pm1 was @ B1=40000, B2=B1, so it didn't need 'much' more to get it

[QUOTE=firejuggler;302622]I know it is useless but still
M8803577 completed P-1, B1=105000, B2=1916250, E=6
P-1 found a factor in stage #1, B1=105000.
UID: firejuggler, M8803573 has a factor: 589495498411470532681
k=2^2*3*5*2857*4831*40429

last pm1 was @ B1=40000, B2=B1, so it didn't need 'much' more to get it[/QUOTE]
Wow, that wasn't missed by much at all the first time!

M115674281 has a factor: 40339344939109680617
M115661719 has a factor: 40122317215718082599
found consecutively on a system that takes 129 mins for these assignments for full length, 17 mins apart :)

[code]
[Sun Jun 24 21:24:31 2012]
P-1 found a factor in stage #2, B1=100000, B2=1925000.
UID: firejuggler, M7930861 has a factor: 6680754188444328044071639,
[/code]
factor is 82.466 bit. Rather large for this exponent.
k=3 × 19 × 137 × 2161 × 80789 × 308939

M3243839 has a factor: 802301222696287988092559711
M3244867 has a factor: 556924867429225023624318383
M3245537 has a factor: 25502181971466624689
90 bits k=5 x 71 x 97 x 2837 x 233159 x 5429209
89 bits k=59 x 89 x 1433 x 518717 x 21986243 , and
65 bits, k=2 ^ 3 x 11 x 47 x 53 x 17922739 , respectively.
Found using P-1 bounds B1=1M B2=30M, all found stage 2, no B-S.

[Sat Jun 30 02:28:44 2012]
P-1 found a factor in stage #1, B1=110000.
UID: firejuggler, M9251881 has a factor: 126328218334013927786152730351

96.673 bit, k=5^2*31*139*1867*9247*56827*95621

Bad TF results?
 

[URL="http://www.mersenne.org/report_exponent/?exp_lo=601983997&exp_hi=10000&B1=Get+status"]M601983997[/URL] has a factor: 60136908979114760311 (65.705 bits)
[URL="http://www.mersenne.org/report_exponent/?exp_lo=601986001&exp_hi=&B1=Get+status"]M601986001[/URL] has a factor: 41955526838838866881 (65.185 bits)

Both were found by trial factoring using Prime 95. However, the interesting part is that both had been TFed using mfakto up to 67 bits, but reported no factors. It leads me to think is it necessary to double check trial factoring results?

[QUOTE=dabaichi;303932]It leads me to think is it necessary to double check trial factoring results?[/QUOTE]

It depends. If it is a reproducible error (i.e. bug) in mfakto, then maybe. If it is a hardware issue, then no. AFAICT, "gpu 2 72" has been finding the expected number of factors.

So someone should rerun those with mfakto, but I'd only be worried if they were different users.