getting all cores to work on Win7

[wildrabbitt]

Thanks.

[MatWur-S530113]

Originally Posted by wildrabbitt

Thanks a million guys. It's great to know there's lots of knowledgeable people on this site.

I managed to get all 8 cores working :) :)

I'm a bit worried about the CPU overheating.

I've got a Noctua HN-D14 cooler on it.

What's your reckoning - is it going to break?

/* EDIT */

What I did was add a variable called WorkerThreads to the list in local.txt because there wasn't one there.
I set it to 8, and lo and behold, all 8 cores have a job BUT, the expected completion dates are Nov 2016.

Since I can do 4 similarly sized Mersenne number tests on a slower machine in 3 months I'm wondering why these ones are set to take so long.

Batalov seems to have more experiences with AMD Processors, my last one is gone 5 years now...
The completion dates depends on some other values, too. Have a look at
'Options' -> 'CPU...' -> 'Hours per day this program will run' and set it to 24 if needed.
A benchmark could be helpful as Mini-Geek suggestet. With some information about the temperatures reached.
I don't know the Noctua NH-D14 by myself (I think you meant 'NH', not 'HN'), it seems to be a very good air-cooler.
I hope that such an oven with 220W will be cooled enough, but not sure. Please look carefully at CoreTemp for some time
Hm, what does prime95 say about the CPU-architecture in the 'Main Thread' worker window? Which other information about the CPU you can get with prime95?
Somehow I still think that prime95 does not recognize your CPU correct.

[Batalov]

Well, I've stopped at Phenoms: I have a sleeper 940 box (on the shelf, for a backup) and a 1055T (the latter was a real six-core; it still runs ...but even a 3570K runs around it in circles and warms the home less).

Here's what the brains said a couple of years ago after testing the Bulldozer/Piledriver: thread 1, thread 2.

[wildrabbitt]

Before I read those two threads........
.........here's the output of the main thread :

[Main thread Jul 15 19:36] Mersenne number primality test program version 28.5
[Main thread Jul 15 19:36] Too many sections in worktodo.txt.  Line #13
[Main thread Jul 15 19:36] Optimizing for CPU architecture: AMD K10, L2 cache size: 2 MB, L3 cache size: 8 MB
[Comm thread Jul 15 19:36] Exchanging program options with server
[Main thread Jul 15 19:36] Starting workers.
[Main thread Jul 15 19:36] Too many sections in worktodo.txt.  Line #13
[Comm thread Jul 15 19:36] Done communicating with server.
[Comm thread Jul 15 19:38] Exchanging program options with server
[Comm thread Jul 15 19:38] Done communicating with server.
[Comm thread Jul 15 22:17] Exchanging program options with server
[Comm thread Jul 15 22:17] Done communicating with server.
[Comm thread Jul 15 22:18] Updating computer information on the server
[Comm thread Jul 15 22:18] Sending expected completion date for M68017633: Sep 19 2015
[Comm thread Jul 15 22:18] PrimeNet success code with additional info:
[Comm thread Jul 15 22:18] WARNING: Estimated completion date is more than one year away.  The assignment may be reassigned to another user after one year.
[Comm thread Jul 15 22:18] Sending expected completion date for M66987859: Sep 12 2015
[Comm thread Jul 15 22:19] PrimeNet success code with additional info:
[Comm thread Jul 15 22:19] WARNING: Estimated completion date is more than one year away.  The assignment may be reassigned to another user after one year.
[Comm thread Jul 15 22:19] Sending expected completion date for M68017879: Sep 19 2015
[Comm thread Jul 15 22:19] PrimeNet success code with additional info:
[Comm thread Jul 15 22:19] WARNING: Estimated completion date is more than one year away.  The assignment may be reassigned to another user after one year.
[Comm thread Jul 15 22:19] Sending expected completion date for M68017907: Sep 19 2015
[Comm thread Jul 15 22:19] PrimeNet success code with additional info:
[Comm thread Jul 15 22:19] WARNING: Estimated completion date is more than one year away.  The assignment may be reassigned to another user after one year.
[Comm thread Jul 15 22:19] Done communicating with server.

[TheMawn]

That Noctua cooler has been benchmarked against a number of all-in-one liquid coolers and produces similar results to the lower end (like an H60 or something).

The advantage of an eight "core" CPU is that the die is so much bigger that it CAN dissipate the heat better.

All around you will be much better off running four cores only. Hopefully, this isn't too much of a disappointment :(

[LaurV]

Just to add on it, related to the "too many sections" errors in the worktodo file, you will have to stop P95 (from test/stop, or test/exit, be careful that clicking the red x does not stop P95, but only send it to work in background). Then open worktodo.txt file from the P95's folder, with any text editor at your choice, notepad is ok if no other better.

You will see (more than 4, probably 8) "sections" inside, every section starts with

[worker n]

where n is from 1 to 8, and under each section you see the work that is queued for each worker.

As you used 8 workers before, there will be 8 sections. Later you switched to 4 workers, but P95 doesn't know how to re-distribute the work. You have to re-distribute the work from workers 5, 6, 7, 8, to workers 1, 2, 3, 4, at your choice (i.e. move the lines "Test=..." or "Factor=...", whatever you have there, cut and paste to other workers) then you can safely delete the lines "[worker 5]"... "[worker 8]" (those are now empty sections).

Restart P95 (from test/continue, or if you exited, just restart it normally by doubleclicking it from its folder).

When you extend the number of workers, new sections are added to worktodo, but when you shrink the number of workers, you have to re-distribute the work manually.

If there is too much work under some worker section, you can unreserve the one with less or no progress, using advanced/unreserve in the menu.