• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Prime5 with quad core

P

Paintedeyes

Member
Hello, I've been having some issues with my quad core system and my friend told me to run memtest and prime 5. althought he was not sure how to do prime 5 for all 4 processors, how would i go about doing htat?
 
I do it by creating 4 separate folders with prime95.exe installed into each of them. I name each folder prime95-0, and then prime95-1 and so forth to prime95-3. I rename the exe of each folder to same as folder ....I launch the exe in each folder, but dont start the torture test yet....Then I go into task manager and processes and click on prime95-0.exe and set affininty to cpu 0 only...Then I do the same for the rest of the prime95-x executables making sure each exe has its associated number core assigned to it...

By keeping the numbers of the cores assigned to each executable I can find what core fails and then track it if that core is the one more predominantly to fail.


it may be long roundabout way, but I like the setup and I can monitor and track things well....
 
Duvie, have you tried Orthos with your Kentsfield yet? I've been wondering if it will stress all four cores, or if you'd need to do a dual Orthos setup. I like your reasoning with the four instances of Prime, though.
 
I found I had to use the single-core Orthos, but setup 4 of them exactly as Duvie is outlaying above, to lock orthos to a core.

The beta orthos for dual-core does not seem to let you assign to cores 3 and 4 on quad-cores.
 
I can't seem to get that to work for me biostud, I soooo wish it would, but adding the -A0 and -A# in genreal does not set the affinity on my systems. Not sure why, am irritated that it doesn't work.
 
Originally posted by: biostud
run "prime95.exe -A0" to run on core 0, then "prime95.exe -A1" to run on core 1 etc.
Click to expand...

You need to create seperate shortcuts for each core to test and within the shortcuts, you add the -aX switches.
 
Originally posted by: Duvie
I do it by creating 4 separate folders with prime95.exe installed into each of them. I name each folder prime95-0, and then prime95-1 and so forth to prime95-3. I rename the exe of each folder to same as folder ....I launch the exe in each folder, but dont start the torture test yet....Then I go into task manager and processes and click on prime95-0.exe and set affininty to cpu 0 only...Then I do the same for the rest of the prime95-x executables making sure each exe has its associated number core assigned to it...

By keeping the numbers of the cores assigned to each executable I can find what core fails and then track it if that core is the one more predominantly to fail.


it may be long roundabout way, but I like the setup and I can monitor and track things well....
Click to expand...

OR oyu could make shortcuts to the orgnal p95 exe and modify the target. LIKE IT SAYS IN THE README.
 
So do we know if it sets a core to each instance running or is it thrashing around like I see in certain apps if you dont set the affinity...I like to do my way so I can track if it is the same core that constantly fails...I can look at it versus its vcore and coretemps as well...
 
Originally posted by: Duvie
So do we know if it sets a core to each instance running or is it thrashing around like I see in certain apps if you dont set the affinity...I like to do my way so I can track if it is the same core that constantly fails...I can look at it versus its vcore and coretemps as well...
Click to expand...

Yes you can set each worker thread to which ever core you wish or you can select the auto feature
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top