• 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.

Weird stuff happening w/ my new 2.4C M0...cpu temps aren't increasing in Prime???

F

ferrarifreak93

Senior member
Well I'm at 12x295=3.54GHz, 1.65v and I'm running two instances of Prime (ver 23.2.1). When I run the torture test my cpu temp isn't increasing, it actually decreases sometimes. I'm using MBM5 and I know the sensor is set up correctly b/c it worked with my last 2.4C. Another thing I noticed is that my cpu usage meter in Windows Task Manager isn't showing near 100% cpu usage when both instances of Prime are running where with my last 2.4C the cpu usage was near 100% under Prime. What IS the deal? Maybe I should d/l a newer version of Prime?

EDIT: just downloaded the latest Prime, cpu usage is still at max 40% (for like a sec).
 
Are you running two instances of P95? That's the only way to get a P4C to 100% with HT off.
 
Try setting the speed back to 2.4c and testing again. If it stops, it might be something to do with your overclock.

Also, I have had issues with the latest Prime95, the latest that worked correctly for me was version 23.5.1.
 
I run good old tried and true version 22 still...I notice some weird stuff with version 23.7 so I would recommend 23.5 or newer version 23.8.....

I am at 3.5ghz or 292fsb but I have ran it at 295fsb and prime95 held 100% with 2 instances.....

Are you running two instances of P95? That's the only way to get a P4C to 100% with HT off.
Click to expand...

Actually you have it backwards....That is the only way to get 100% with HT TURNED ON.....With it off you get 100% with 1 instance....
 
Man this is messed up! I was stress testing w/ 2 instances of Prime at 3.36Ghz. THis is what happened.

1. I start two instances of Prime, in Windows Task Manager I get around 10% CPU Usage when Priming. I let it run for like 10 minutes then manually stop the testing.

2. I restart the test (in both instances of Prime). In Windows Task Manger I now get up to 100% CPU Usage (where it should be) when Priming and then I get an error in around 10 seconds.

BTW, I set my cpu back to default everything and it did the same thing except in didn't fail in step 2 above.
 
Find Prime95 version 23.5.1 and see if that fixes your problem. I have had problems with the newer ones myself
 
Originally posted by: ferrarifreak93
Man this is messed up! I was stress testing w/ 2 instances of Prime at 3.36Ghz. THis is what happened.

1. I start two instances of Prime, in Windows Task Manager I get around 10% CPU Usage when Priming. I let it run for like 10 minutes then manually stop the testing.

2. I restart the test (in both instances of Prime). In Windows Task Manger I now get up to 100% CPU Usage (where it should be) when Priming and then I get an error in around 10 seconds.

BTW, I set my cpu back to default everything and it did the same thing except in didn't fail in step 2 above.
Click to expand...
That means that, assuming you want a 100% stable system, you need to start at slightly less than 3.36ghz, and if it still fails, reboot and try again at a slightly lower fsb.
 
Originally posted by: ferrarifreak93
Originally posted by: drewdogg808
did you set the memory usage right for each instance of prime?
Click to expand...

No, where do I find this?
Click to expand...

Under Options/CPU. I usually set mine so I have about 100 megs free on my 1 gig system (445 megs per instance). This way there is minimal paging to the harddrive, which slows the computer down and doesn't allow prime to stress fully.
 
Originally posted by: myocardia
Originally posted by: ferrarifreak93
Man this is messed up! I was stress testing w/ 2 instances of Prime at 3.36Ghz. THis is what happened.

1. I start two instances of Prime, in Windows Task Manager I get around 10% CPU Usage when Priming. I let it run for like 10 minutes then manually stop the testing.

2. I restart the test (in both instances of Prime). In Windows Task Manger I now get up to 100% CPU Usage (where it should be) when Priming and then I get an error in around 10 seconds.

BTW, I set my cpu back to default everything and it did the same thing except in didn't fail in step 2 above.
Click to expand...
That means that, assuming you want a 100% stable system, you need to start at slightly less than 3.36ghz, and if it still fails, reboot and try again at a slightly lower fsb.
Click to expand...

I don't think you understand. The first time I run two instances of Prime, it passes. If I manually stop the tests and restart them it fails within 10 seconds.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top