Prime95 version 25.8 - Page 15

cheesehead · 2009-07-13, 05:22

Quote:

Originally Posted by petrw1

... who would have thought???

Thermodynamics RULZ!

garo · 2009-07-13, 09:42

Quote:

Originally Posted by petrw1

Well I got a chance to dust it ... both the back and side vents were complete blocked. It is now running more than twice as fast as before ... who would have thought???

I had a similar experience and I was surprised too. But yes, dust in the heatsink can significantly slow down the CPU due to thermal throttling. Now I clean my CPU heatsinks at least once a quarter

asdenoile · 2009-08-04, 23:42

I am under the impression that on multicore machines the rolling average is computed based on the last worker. When you have for instance core 0, 1 and 3 doing LL tests and core 2 doing TF, the rolling average based on core 3 is very optimitic for cores 0 and 1. (Core 3 has a much better access to memory, while core 0 and 1 are competing for memory throughput.) This means that to compute a reliable ETA there should be a rolling average per core (or per worker). Another solution would be a rolling average based on all cores.

1997rj7 · 2009-08-27, 00:43

I'm not sure if this is a bug or not, but Prime95 25.9.4 (32-bit) crashed on one of my machines. The crash occured 2 seconds after one of the cores had found a factor in stage 2 of P-1.

The machine is a Core i7 920. The operating system is Windows XP. It is not connected to the internet, so I get and report assignments manually. Three cores are running double checks, and the fourth is running P-1. This machine has previously found P-1 factors in stage 2 with no problem.

The error messages in the event log say:

Faulting application Prime95.exe version 25.9.4.0 faulting module ntdll.dll version 5.1.2600.2180, fault address 0x00011e58.

The exeption generated was C0000005 at address 7C911E58 (ntdll!RtInitializeCriticalSection)

edron1011 · 2009-09-21, 14:21

I've seen prime95 crash on several machines now with the following log event

Faulting application prime95.exe, version 25.9.4.0, faulting module ntdll.dll, version 5.1.2600.5755, fault address 0x00010a19.

I saw a similar event posted in the forum does anybody know why prime95 version 25.9
is causing this.

Any help would be appreciated

ed

lfm · 2009-09-21, 16:30

I am pretty sure this was fixed long ago in version 25.11 (current) or earlier.

2009-09-21, 14:21	#159
edron1011 Oct 2008 Annapolis, Md 7 Posts	Fault in ntdll.dll reported by USER32 I've seen prime95 crash on several machines now with the following log event Faulting application prime95.exe, version 25.9.4.0, faulting module ntdll.dll, version 5.1.2600.5755, fault address 0x00010a19. I saw a similar event posted in the forum does anybody know why prime95 version 25.9 is causing this. Any help would be appreciated ed

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Prime95 version 27.3	Prime95	Software	148	2012-03-18 19:24
Prime95 version 26.3	Prime95	Software	76	2010-12-11 00:11
Prime95 version 25.5	Prime95	PrimeNet	369	2008-02-26 05:21
Prime95 version 25.4	Prime95	PrimeNet	143	2007-09-24 21:01
When the next prime95 version ?	pacionet	Software	74	2006-12-07 20:30

2009-08-04, 23:42	#157
asdenoile Aug 2009 3 Posts	I am under the impression that on multicore machines the rolling average is computed based on the last worker. When you have for instance core 0, 1 and 3 doing LL tests and core 2 doing TF, the rolling average based on core 3 is very optimitic for cores 0 and 1. (Core 3 has a much better access to memory, while core 0 and 1 are competing for memory throughput.) This means that to compute a reliable ETA there should be a rolling average per core (or per worker). Another solution would be a rolling average based on all cores.

2009-08-27, 00:43	#158
1997rj7 Sep 2003 352₁₀ Posts	I'm not sure if this is a bug or not, but Prime95 25.9.4 (32-bit) crashed on one of my machines. The crash occured 2 seconds after one of the cores had found a factor in stage 2 of P-1. The machine is a Core i7 920. The operating system is Windows XP. It is not connected to the internet, so I get and report assignments manually. Three cores are running double checks, and the fourth is running P-1. This machine has previously found P-1 factors in stage 2 with no problem. The error messages in the event log say: Faulting application Prime95.exe version 25.9.4.0 faulting module ntdll.dll version 5.1.2600.2180, fault address 0x00011e58. The exeption generated was C0000005 at address 7C911E58 (ntdll!RtInitializeCriticalSection)

2009-09-21, 16:30	#160
lfm Jul 2006 Calgary 5²×17 Posts	I am pretty sure this was fixed long ago in version 25.11 (current) or earlier.