Back on a stock cooler, are these temps safe for a week?

[Atnevon]

Ok. So I went to put my Arctic 7 back on after putting on some new thermal paste. Then those damn little pins broke. 2 of them. I'm pissed. I just need 2 things.

1. Are these temps safe for a week or so?

http://img120.imageshack.us/img120/2264/screenbe3.jpg (http://imageshack.us)
http://img120.imageshack.us/img120/2264/screenbe3.1b8651bc46.jpg (http://g.imageshack.us/g.php?h=120&i=screenbe3.jpg)

2. I have a q6600, g0. If I were to spend 50 bucks on a cooler, what would you all reccomend? I like the quiet nature of it, and really liked it. But is there a little better.

Case: Antec 900.
MB: 680i

Thank you for any input on this issue.

-Andrew

[Kursah]

Temps look okay, try Coretemp or Realtemp tho and see what their readouts are for the cores (believed by many to be more accurate). But the 50's and 60's are safe for the Q6600, so no sweat there.

I recommend the Xigmatec S1283, great cooler. Sorry to hear you broke the pins on your AC, great cooler mine is still in use on my G/F's rig, I've installed it over a dozen times w/o issue...but there's gotta be that "one" that has the crappy parts on it. One note about the Xig is it comes with the Push-pin install, and requires a little more force than the AC, but I still found it easier than the Stock Intel cooler to install (same with the AC), and mine seats tight, I can't wiggle it after installed. You can get a bolt kit for it from Xig, but from what I've heard they're slow to respond to requests for it...like I said I've had no issues with the push-pin design, both AC and Xig have done a great job making decent holding force with easy install.

Keeps my Q6600 OC'd in the mid 50's atm (3.6 @ 1.45, G/F has the damn heat turned up again! lol!). Check out Newegg for prices on it. Hope that helps!

:toast:

[hat]

XIGMATEK all the way :rockout:
http://www.newegg.com/Product/Product.aspx?Item=N82E16835233018

[newtekie1]

I would rather see load temps, idle temps like that don't really tell us much.

Download Prime95 v25 and put all 4 cores under load and then get a temp reading. As long as it stays under 70°C you are fine, 65°C would be best though, just to be safe.

[Atnevon]

Well. Here is a load. I have a WoW window open, with a superpi in the background doing 4mil. Hope that is load enough.

http://img187.imageshack.us/img187/6608/screenmc5.jpg (http://imageshack.us)
http://img187.imageshack.us/img187/6608/screenmc5.a8a2bb8024.jpg (http://g.imageshack.us/g.php?h=187&i=screenmc5.jpg)

Now what is the longest you think I should have this thing on at at time. I was thinking 8 hours on, 1 hour rest rotation.

Thanks for the link too. Right now I don't OC. May in the future. But content with 2.4. Way better than my last lappy. (College student).

Anyway, Thank you all for your help.
-Andrew

[jonmcc33]

I would rather see load temps, idle temps like that don't really tell us much.

Download Prime95 v25 and put all 4 cores under load and then get a temp reading. As long as it stays under 70°C you are fine, 65°C would be best though, just to be safe.

1. Those are in fact load temps. I don't see a single core on there idle. Well, maybe the 4th is on a break.
2. NOTHING comes close to pushing a core the way Prime95 does and that is why it's a bit overboard to ask of. Even video encoding will not push it that hard. Gaming won't come close to pushing it that hard, even if the game supports multiple cores.

[Creatre]

Do Prime95 for a stress test. I sit at 47 idle 70 load with my arctic cooler 7 pro, but I'm at 3.51ghz. Had to crank the volts way up to get it stable unfortunately. Need a better cooler here soon. Luckily, nothing I have maxes the cpu out other than Prime95. :rolleyes:

[jonmcc33]

Luckily, nothing I have maxes the cpu out other than Prime95. :rolleyes:

Name one thing that you do that does. :rolleyes:

[ex_reven]

Name one thing that you do that does. :rolleyes:

orthos :laugh:

[newtekie1]

1. Those are in fact load temps. I don't see a single core on there idle. Well, maybe the 4th is on a break.
2. NOTHING comes close to pushing a core the way Prime95 does and that is why it's a bit overboard to ask of. Even video encoding will not push it that hard. Gaming won't come close to pushing it that hard, even if the game supports multiple cores.

1.) No those aren't load temps. Not a single core is at 100%, 46% overall load is not load temperatures. 100% load is load temperatures.

2.) When dealing with load temperatures you always assume the worst. Even if the processor will never see 100% load, I wouldn't feel comfortable unless it was cooler under 100% load because you never know. If he starts Folding it could kill the processor if he doesn't know it runs cool enough under the stress.

Name one thing that you do that does. :rolleyes:

Fold

[spearman914]

I recomend the red scorpion. Trenmendous performance and absolutely excellent design.

[francis511]

Wow twilight zone music. I had a arctic freezer pro - broke one of the pins and replaced with a xigmatek. It takes 10-20 degrees off and my oc got a lot more stable. Prime 95 is just like setting fire to a q6600 !

[jonmcc33]

1.) No those aren't load temps. Not a single core is at 100%, 46% overall load is not load temperatures. 100% load is load temperatures.

2.) When dealing with load temperatures you always assume the worst. Even if the processor will never see 100% load, I wouldn't feel comfortable unless it was cooler under 100% load because you never know. If he starts Folding it could kill the processor if he doesn't know it runs cool enough under the stress.

Fold

1. You're a bit confused about what a "load" is. Maxing out the core isn't "load". Putting it under use is a "load". It's not idle is it? A game will put a processor under load but does it max it out? Each core might be 50% load but it's still under "load". Got it? Not max load but under load. AnandTech doesn't (http://www.anandtech.com/casecoolingpsus/showdoc.aspx?i=3268&p=4) use Prime95 with temperature benchmarks. They tend to stick to real world results and not extremes, which is the same case as the OP in this thread.

Correct me if I am wrong but you said that his temps were idle even though they were under 50% load? Hopefully if your car is running it isn't idle at 4000RPM. :p

2. Always assume the worst? I do not agree. Prime95 is good to test the stability of an overclock and perhaps the effectiveness of a heatsink to dissipate heat, but it doesn't represent real world use even remotely.

He's also running his Q6600 at stock clock speeds. I doubt that Folding would do anything to his CPU at stock speeds to be honest. Not sure where you'd think it would but then again you think 50% load is idle. :rolleyes:

[cdawall]

your temps are fine

go fro a xigmatek ;)

[newtekie1]

1. You're a bit confused about what a "load" is. Maxing out the core isn't "load". Putting it under use is a "load". It's not idle is it? A game will put a processor under load but does it max it out? Each core might be 50% load but it's still under "load". Got it? Not max load but under load. AnandTech doesn't (http://www.anandtech.com/casecoolingpsus/showdoc.aspx?i=3268&p=4) use Prime95 with temperature benchmarks. They tend to stick to real world results and not extremes, which is the same case as the OP in this thread.

Correct me if I am wrong but you said that his temps were idle even though they were under 50% load? Hopefully if your car is running it isn't idle at 4000RPM. :p

2. Always assume the worst? I do not agree. Prime95 is good to test the stability of an overclock and perhaps the effectiveness of a heatsink to dissipate heat, but it doesn't represent real world use even remotely.

He's also running his Q6600 at stock clock speeds. I doubt that Folding would do anything to his CPU at stock speeds to be honest. Not sure where you'd think it would but then again you think 50% load is idle. :rolleyes:

1.) IMO, maxing out the core is "load" when you are talking about temperatures. I don't care what Anandtech does, if you like they way they do things so much go over there. Read some real reviews, load means 100% load. We don't know how long the processor was running at 46%, for all we know it was a spike in CPU usage when he took the screenshot. If I don't see 100% load and proof that it has been under that load for some time, then it is an idle temp. End of story.

2.) Actually it does represent several real world usages. Just because they don't represent any thing you use the computer for doesn't mean it doesn't represent any real world useage. People do a lot more on their computer than just what you do. My processors see 100% load daily, as do millions of others. You don't know what he is using his computer for, so when dealing with temperatures and safety of the hardware you ALWAYS assume the worse. You can't go "well I never turn my computer on, so I'm going to assume that everyone else doesn't turn theirs on either, so it will always be safe." Which is only a minor exaggeration of what you are doing right now.

The quads can get pretty hot under the stock cooler. 50C idle is already pretty toasty, and yes I am still assuming the first shot is an idle shot as we don't know how long that 50% load was on the CPU, and we don't even know he was running anything to actually put the CPU under load as he only mentions that he tried to put it under load in the second shot, which was actually less load than the first. It wouldn't be a stretch for 70C under Folding load with the stock cooler, which is too high IMO.

If you want to get insulting I can do it back, but I'll be the bigger person for now. You can disagree with someone and make the argument against them without being insulting. By trying to be insulting you just make yourself look stupid, especially when you are wrong like this case.

[jonmcc33]

1.) IMO, maxing out the core is "load" when you are talking about temperatures. I don't care what Anandtech does, if you like they way they do things so much go over there. Read some real reviews, load means 100% load. We don't know how long the processor was running at 46%, for all we know it was a spike in CPU usage when he took the screenshot. If I don't see 100% load and proof that it has been under that load for some time, then it is an idle temp. End of story.

2.) Actually it does represent several real world usages. Just because they don't represent any thing you use the computer for doesn't mean it doesn't represent any real world useage. People do a lot more on their computer than just what you do. My processors see 100% load daily, as do millions of others. You don't know what he is using his computer for, so when dealing with temperatures and safety of the hardware you ALWAYS assume the worse. You can't go "well I never turn my computer on, so I'm going to assume that everyone else doesn't turn theirs on either, so it will always be safe." Which is only a minor exaggeration of what you are doing right now.

The quads can get pretty hot under the stock cooler. 50C idle is already pretty toasty, and yes I am still assuming the first shot is an idle shot as we don't know how long that 50% load was on the CPU, and we don't even know he was running anything to actually put the CPU under load as he only mentions that he tried to put it under load in the second shot, which was actually less load than the first. It wouldn't be a stretch for 70C under Folding load with the stock cooler, which is too high IMO.

If you want to get insulting I can do it back, but I'll be the bigger person for now. You can disagree with someone and make the argument against them without being insulting. By trying to be insulting you just make yourself look stupid, especially when you are wrong like this case.

100% load is not realistic. My point was that his temps are not idle like you claim, that's all. Idle means ~1% CPU load or less. No need to further debate this.

[cdawall]

100% load is not realistic. My point was that his temps are not idle like you claim, that's all. Idle means ~1% CPU load or less. No need to further debate this.

actually 100% load is realistic if you game or fold or anything stressful you hit 100% so why would you not stress test @ 100%? that just seems stupid

[[I.R.A]_FBi]

XIGMATEK all the way :rockout:
http://www.newegg.com/Product/Product.aspx?Item=N82E16835233018

ill cosign this ...

[jonmcc33]

actually 100% load is realistic if you game or fold or anything stressful you hit 100% so why would you not stress test @ 100%? that just seems stupid

Gaming does not hit 100% CPU load on any multicore processor. Folding? Supposedly it doesn't use up any processor at all...

http://en.wikipedia.org/wiki/Folding%40home

The closest I have ever came to maxing out my processors was video encoding. One core will be maxed to 100% and the other average 50-70%.

[cdawall]

Gaming does not hit 100% CPU load on any multicore processor. Folding? Supposedly it doesn't use up any processor at all...

http://en.wikipedia.org/wiki/Folding%40home

The closest I have ever came to maxing out my processors was video encoding. One core will be maxed to 100% and the other average 50-70%.

i have hit 100% in games but i'm only using a DC...

video encoding also maxed 100/100 on mine

i don't fold so no clue on that one

[jonmcc33]

i have hit 100% in games but i'm only using a DC...

video encoding also maxed 100/100 on mine

i don't fold so no clue on that one

COD4 in the middle of a match...the numbers before the CPU clock speed are processor load.

21:36:03 05/01/08 CPU#0 (Core#0): 48 31 48 80 3200.00
21:36:03 05/01/08 CPU#0 (Core#1): 46 32 48 48 3200.00
21:36:04 05/01/08 CPU#0 (Core#0): 48 31 48 88 3200.00
21:36:04 05/01/08 CPU#0 (Core#1): 47 32 48 51 3200.00
21:36:05 05/01/08 CPU#0 (Core#0): 46 31 48 86 3200.00
21:36:05 05/01/08 CPU#0 (Core#1): 47 32 48 46 3200.00
21:36:06 05/01/08 CPU#0 (Core#0): 47 31 48 87 3200.00
21:36:06 05/01/08 CPU#0 (Core#1): 46 32 48 44 3200.00
21:36:07 05/01/08 CPU#0 (Core#0): 47 31 48 83 3200.00
21:36:07 05/01/08 CPU#0 (Core#1): 46 32 48 57 3200.00
21:36:08 05/01/08 CPU#0 (Core#0): 47 31 48 89 3200.00
21:36:08 05/01/08 CPU#0 (Core#1): 47 32 48 50 3200.00
21:36:09 05/01/08 CPU#0 (Core#0): 47 31 48 83 3200.00
21:36:09 05/01/08 CPU#0 (Core#1): 47 32 48 47 3200.00
21:36:10 05/01/08 CPU#0 (Core#0): 48 31 48 87 3200.00
21:36:10 05/01/08 CPU#0 (Core#1): 45 32 48 53 3200.00
21:36:11 05/01/08 CPU#0 (Core#0): 47 31 48 83 3200.00
21:36:11 05/01/08 CPU#0 (Core#1): 47 32 48 49 3200.00
21:36:12 05/01/08 CPU#0 (Core#0): 46 31 48 81 3200.00
21:36:12 05/01/08 CPU#0 (Core#1): 48 32 48 58 3200.00
21:36:13 05/01/08 CPU#0 (Core#0): 48 31 48 77 3200.00
21:36:13 05/01/08 CPU#0 (Core#1): 46 32 48 47 3200.00
21:36:14 05/01/08 CPU#0 (Core#0): 47 31 48 95 3200.00
21:36:14 05/01/08 CPU#0 (Core#1): 48 32 48 51 3200.00
21:36:15 05/01/08 CPU#0 (Core#0): 47 31 48 81 3200.00
21:36:15 05/01/08 CPU#0 (Core#1): 48 32 48 61 3200.00
21:36:16 05/01/08 CPU#0 (Core#0): 48 31 48 77 3200.00
21:36:16 05/01/08 CPU#0 (Core#1): 45 32 48 53 3200.00
21:36:17 05/01/08 CPU#0 (Core#0): 47 31 48 87 3200.00
21:36:17 05/01/08 CPU#0 (Core#1): 46 32 48 44 3200.00
21:36:18 05/01/08 CPU#0 (Core#0): 48 31 48 88 3200.00
21:36:18 05/01/08 CPU#0 (Core#1): 47 32 48 66 3200.00
21:36:19 05/01/08 CPU#0 (Core#0): 48 31 48 86 3200.00
21:36:19 05/01/08 CPU#0 (Core#1): 48 32 48 46 3200.00
21:36:20 05/01/08 CPU#0 (Core#0): 47 31 48 83 3200.00
21:36:20 05/01/08 CPU#0 (Core#1): 48 32 48 58 3200.00
21:36:21 05/01/08 CPU#0 (Core#0): 48 31 48 81 3200.00
21:36:21 05/01/08 CPU#0 (Core#1): 46 32 48 48 3200.00
21:36:22 05/01/08 CPU#0 (Core#0): 48 31 48 83 3200.00
21:36:22 05/01/08 CPU#0 (Core#1): 47 32 48 56 3200.00
21:36:23 05/01/08 CPU#0 (Core#0): 48 31 48 86 3200.00
21:36:23 05/01/08 CPU#0 (Core#1): 46 32 48 52 3200.00

[hat]

88 huh... kinda scary

[jonmcc33]

Overlord: Raising Hell on a normal map...

21:43:18 05/01/08 CPU#0 (Core#0): 45 31 50 89 3200.00
21:43:18 05/01/08 CPU#0 (Core#1): 44 32 50 30 3200.00
21:43:19 05/01/08 CPU#0 (Core#0): 45 31 50 89 3200.00
21:43:19 05/01/08 CPU#0 (Core#1): 44 32 50 28 3200.00
21:43:20 05/01/08 CPU#0 (Core#0): 45 31 50 87 3200.00
21:43:20 05/01/08 CPU#0 (Core#1): 44 32 50 27 3200.00
21:43:21 05/01/08 CPU#0 (Core#0): 45 31 50 86 3200.00
21:43:21 05/01/08 CPU#0 (Core#1): 43 32 50 25 3200.00
21:43:22 05/01/08 CPU#0 (Core#0): 45 31 50 95 3200.00
21:43:22 05/01/08 CPU#0 (Core#1): 45 32 50 33 3200.00
21:43:23 05/01/08 CPU#0 (Core#0): 45 31 50 84 3200.00
21:43:23 05/01/08 CPU#0 (Core#1): 44 32 50 24 3200.00
21:43:24 05/01/08 CPU#0 (Core#0): 45 31 50 87 3200.00
21:43:24 05/01/08 CPU#0 (Core#1): 46 32 50 40 3200.00
21:43:25 05/01/08 CPU#0 (Core#0): 45 31 50 81 3200.00
21:43:25 05/01/08 CPU#0 (Core#1): 46 32 50 39 3200.00
21:43:26 05/01/08 CPU#0 (Core#0): 46 31 50 81 3200.00
21:43:26 05/01/08 CPU#0 (Core#1): 45 32 50 44 3200.00
21:43:27 05/01/08 CPU#0 (Core#0): 46 31 50 83 3200.00
21:43:27 05/01/08 CPU#0 (Core#1): 44 32 50 42 3200.00
21:43:28 05/01/08 CPU#0 (Core#0): 44 31 50 83 3200.00
21:43:28 05/01/08 CPU#0 (Core#1): 44 32 50 37 3200.00
21:43:29 05/01/08 CPU#0 (Core#0): 46 31 50 76 3200.00
21:43:29 05/01/08 CPU#0 (Core#1): 46 32 50 36 3200.00
21:43:30 05/01/08 CPU#0 (Core#0): 46 31 50 89 3200.00
21:43:30 05/01/08 CPU#0 (Core#1): 44 32 50 38 3200.00
21:43:31 05/01/08 CPU#0 (Core#0): 45 31 50 81 3200.00
21:43:31 05/01/08 CPU#0 (Core#1): 45 32 50 34 3200.00
21:43:32 05/01/08 CPU#0 (Core#0): 45 31 50 89 3200.00
21:43:32 05/01/08 CPU#0 (Core#1): 44 32 50 42 3200.00
21:43:33 05/01/08 CPU#0 (Core#0): 45 31 50 82 3200.00
21:43:33 05/01/08 CPU#0 (Core#1): 44 32 50 29 3200.00
21:43:34 05/01/08 CPU#0 (Core#0): 46 31 50 70 3200.00
21:43:34 05/01/08 CPU#0 (Core#1): 45 32 50 35 3200.00

[jonmcc33]

Timeshift in the middle of a fire fight...

21:46:55 05/01/08 CPU#0 (Core#0): 45 31 50 75 3200.00
21:46:55 05/01/08 CPU#0 (Core#1): 47 32 50 80 3200.00
21:46:56 05/01/08 CPU#0 (Core#0): 45 31 50 76 3200.00
21:46:56 05/01/08 CPU#0 (Core#1): 47 32 50 64 3200.00
21:46:57 05/01/08 CPU#0 (Core#0): 45 31 50 77 3200.00
21:46:57 05/01/08 CPU#0 (Core#1): 45 32 50 67 3200.00
21:46:58 05/01/08 CPU#0 (Core#0): 46 31 50 69 3200.00
21:46:58 05/01/08 CPU#0 (Core#1): 47 32 50 62 3200.00
21:46:59 05/01/08 CPU#0 (Core#0): 45 31 50 66 3200.00
21:46:59 05/01/08 CPU#0 (Core#1): 45 32 50 63 3200.00
21:47:00 05/01/08 CPU#0 (Core#0): 47 31 50 69 3200.00
21:47:00 05/01/08 CPU#0 (Core#1): 46 32 50 64 3200.00
21:47:01 05/01/08 CPU#0 (Core#0): 46 31 50 64 3200.00
21:47:01 05/01/08 CPU#0 (Core#1): 45 32 50 74 3200.00
21:47:02 05/01/08 CPU#0 (Core#0): 46 31 50 75 3200.00
21:47:02 05/01/08 CPU#0 (Core#1): 47 32 50 71 3200.00
21:47:03 05/01/08 CPU#0 (Core#0): 46 31 50 67 3200.00
21:47:03 05/01/08 CPU#0 (Core#1): 47 32 50 62 3200.00
21:47:04 05/01/08 CPU#0 (Core#0): 46 31 50 77 3200.00
21:47:04 05/01/08 CPU#0 (Core#1): 45 32 50 77 3200.00
21:47:05 05/01/08 CPU#0 (Core#0): 46 31 50 77 3200.00
21:47:05 05/01/08 CPU#0 (Core#1): 47 32 50 63 3200.00
21:47:06 05/01/08 CPU#0 (Core#0): 45 31 50 67 3200.00
21:47:06 05/01/08 CPU#0 (Core#1): 45 32 50 66 3200.00
21:47:07 05/01/08 CPU#0 (Core#0): 46 31 50 70 3200.00
21:47:07 05/01/08 CPU#0 (Core#1): 48 32 50 66 3200.00
21:47:08 05/01/08 CPU#0 (Core#0): 46 31 50 73 3200.00
21:47:08 05/01/08 CPU#0 (Core#1): 47 32 50 67 3200.00
21:47:09 05/01/08 CPU#0 (Core#0): 45 31 50 63 3200.00
21:47:09 05/01/08 CPU#0 (Core#1): 47 32 50 66 3200.00
21:47:10 05/01/08 CPU#0 (Core#0): 46 31 50 75 3200.00
21:47:10 05/01/08 CPU#0 (Core#1): 47 32 50 58 3200.00
21:47:11 05/01/08 CPU#0 (Core#0): 45 31 50 67 3200.00
21:47:11 05/01/08 CPU#0 (Core#1): 47 32 50 67 3200.00
21:47:12 05/01/08 CPU#0 (Core#0): 46 31 50 70 3200.00
21:47:12 05/01/08 CPU#0 (Core#1): 47 32 50 61 3200.00
21:47:13 05/01/08 CPU#0 (Core#0): 46 31 50 72 3200.00
21:47:13 05/01/08 CPU#0 (Core#1): 46 32 50 75 3200.00
21:47:14 05/01/08 CPU#0 (Core#0): 47 31 50 78 3200.00
21:47:14 05/01/08 CPU#0 (Core#1): 48 32 50 72 3200.00
21:47:15 05/01/08 CPU#0 (Core#0): 46 31 50 78 3200.00
21:47:15 05/01/08 CPU#0 (Core#1): 46 32 50 75 3200.00
21:47:16 05/01/08 CPU#0 (Core#0): 45 31 50 68 3200.00
21:47:16 05/01/08 CPU#0 (Core#1): 47 32 50 72 3200.00
21:47:17 05/01/08 CPU#0 (Core#0): 46 31 50 77 3200.00
21:47:17 05/01/08 CPU#0 (Core#1): 45 32 50 56 3200.00

[jonmcc33]

Black & White 2...in the beginning of a game where it circles an island and zooms in so you can pick your creature.

21:50:23 05/01/08 CPU#0 (Core#0): 45 31 50 64 3200.00
21:50:23 05/01/08 CPU#0 (Core#1): 43 32 50 47 3200.00
21:50:24 05/01/08 CPU#0 (Core#0): 44 31 50 56 3200.00
21:50:24 05/01/08 CPU#0 (Core#1): 45 32 50 61 3200.00
21:50:25 05/01/08 CPU#0 (Core#0): 44 31 50 55 3200.00
21:50:25 05/01/08 CPU#0 (Core#1): 46 32 50 55 3200.00
21:50:26 05/01/08 CPU#0 (Core#0): 45 31 50 67 3200.00
21:50:26 05/01/08 CPU#0 (Core#1): 44 32 50 52 3200.00
21:50:27 05/01/08 CPU#0 (Core#0): 44 31 50 53 3200.00
21:50:27 05/01/08 CPU#0 (Core#1): 45 32 50 61 3200.00
21:50:28 05/01/08 CPU#0 (Core#0): 43 31 50 62 3200.00
21:50:28 05/01/08 CPU#0 (Core#1): 46 32 50 55 3200.00
21:50:29 05/01/08 CPU#0 (Core#0): 44 31 50 56 3200.00
21:50:29 05/01/08 CPU#0 (Core#1): 45 32 50 61 3200.00
21:50:30 05/01/08 CPU#0 (Core#0): 43 31 50 67 3200.00
21:50:30 05/01/08 CPU#0 (Core#1): 46 32 50 54 3200.00
21:50:31 05/01/08 CPU#0 (Core#0): 45 31 50 67 3200.00
21:50:31 05/01/08 CPU#0 (Core#1): 44 32 50 55 3200.00
21:50:32 05/01/08 CPU#0 (Core#0): 44 31 50 70 3200.00
21:50:32 05/01/08 CPU#0 (Core#1): 44 32 50 56 3200.00
21:50:33 05/01/08 CPU#0 (Core#0): 45 31 50 58 3200.00
21:50:33 05/01/08 CPU#0 (Core#1): 44 32 50 47 3200.00
21:50:34 05/01/08 CPU#0 (Core#0): 44 31 50 53 3200.00
21:50:34 05/01/08 CPU#0 (Core#1): 45 32 50 52 3200.00
21:50:35 05/01/08 CPU#0 (Core#0): 43 31 50 53 3200.00
21:50:35 05/01/08 CPU#0 (Core#1): 47 32 50 53 3200.00
21:50:36 05/01/08 CPU#0 (Core#0): 44 31 50 66 3200.00
21:50:36 05/01/08 CPU#0 (Core#1): 45 32 50 53 3200.00
21:50:37 05/01/08 CPU#0 (Core#0): 46 31 50 67 3200.00
21:50:37 05/01/08 CPU#0 (Core#1): 45 32 50 56 3200.00
21:50:38 05/01/08 CPU#0 (Core#0): 44 31 50 63 3200.00
21:50:38 05/01/08 CPU#0 (Core#1): 45 32 50 52 3200.00
21:50:39 05/01/08 CPU#0 (Core#0): 45 31 50 62 3200.00
21:50:39 05/01/08 CPU#0 (Core#1): 44 32 50 42 3200.00
21:50:40 05/01/08 CPU#0 (Core#0): 44 31 50 61 3200.00
21:50:40 05/01/08 CPU#0 (Core#1): 45 32 50 50 3200.00
21:50:41 05/01/08 CPU#0 (Core#0): 44 31 50 61 3200.00
21:50:41 05/01/08 CPU#0 (Core#1): 45 32 50 53 3200.00
21:50:42 05/01/08 CPU#0 (Core#0): 45 31 50 70 3200.00
21:50:42 05/01/08 CPU#0 (Core#1): 44 32 50 58 3200.00
21:50:43 05/01/08 CPU#0 (Core#0): 45 31 50 61 3200.00
21:50:43 05/01/08 CPU#0 (Core#1): 46 32 50 51 3200.00
21:50:44 05/01/08 CPU#0 (Core#0): 46 31 50 64 3200.00
21:50:44 05/01/08 CPU#0 (Core#1): 44 32 50 48 3200.00
21:50:45 05/01/08 CPU#0 (Core#0): 45 31 50 60 3200.00
21:50:45 05/01/08 CPU#0 (Core#1): 45 32 50 46 3200.00
21:50:46 05/01/08 CPU#0 (Core#0): 43 31 50 48 3200.00
21:50:46 05/01/08 CPU#0 (Core#1): 46 32 50 51 3200.00
21:50:47 05/01/08 CPU#0 (Core#0): 45 31 50 64 3200.00

Battlefield 2 on a 64 player Gulf of Oman map...

21:57:51 05/01/08 CPU#0 (Core#0): 47 31 50 58 3200.00
21:57:51 05/01/08 CPU#0 (Core#1): 47 32 50 78 3200.00
21:57:52 05/01/08 CPU#0 (Core#0): 47 31 50 59 3200.00
21:57:52 05/01/08 CPU#0 (Core#1): 48 32 50 78 3200.00
21:57:53 05/01/08 CPU#0 (Core#0): 47 31 50 62 3200.00
21:57:53 05/01/08 CPU#0 (Core#1): 48 32 50 77 3200.00
21:57:54 05/01/08 CPU#0 (Core#0): 47 31 50 59 3200.00
21:57:54 05/01/08 CPU#0 (Core#1): 48 32 50 59 3200.00
21:57:55 05/01/08 CPU#0 (Core#0): 47 31 50 59 3200.00
21:57:55 05/01/08 CPU#0 (Core#1): 48 32 50 88 3200.00
21:57:56 05/01/08 CPU#0 (Core#0): 47 31 50 45 3200.00
21:57:56 05/01/08 CPU#0 (Core#1): 48 32 50 72 3200.00
21:57:57 05/01/08 CPU#0 (Core#0): 47 31 50 51 3200.00
21:57:57 05/01/08 CPU#0 (Core#1): 48 32 50 89 3200.00
21:57:58 05/01/08 CPU#0 (Core#0): 47 31 50 58 3200.00
21:57:58 05/01/08 CPU#0 (Core#1): 48 32 50 78 3200.00
21:57:59 05/01/08 CPU#0 (Core#0): 47 31 50 47 3200.00
21:57:59 05/01/08 CPU#0 (Core#1): 48 32 50 77 3200.00
21:58:00 05/01/08 CPU#0 (Core#0): 47 31 50 59 3200.00
21:58:00 05/01/08 CPU#0 (Core#1): 47 32 50 77 3200.00
21:58:01 05/01/08 CPU#0 (Core#0): 46 31 50 55 3200.00
21:58:01 05/01/08 CPU#0 (Core#1): 47 32 50 49 3200.00
21:58:02 05/01/08 CPU#0 (Core#0): 45 31 50 36 3200.00
21:58:02 05/01/08 CPU#0 (Core#1): 47 32 50 52 3200.00
21:58:03 05/01/08 CPU#0 (Core#0): 45 31 50 36 3200.00
21:58:03 05/01/08 CPU#0 (Core#1): 46 32 50 55 3200.00
21:58:04 05/01/08 CPU#0 (Core#0): 47 31 50 48 3200.00
21:58:04 05/01/08 CPU#0 (Core#1): 47 32 50 66 3200.00
21:58:05 05/01/08 CPU#0 (Core#0): 46 31 50 38 3200.00
21:58:05 05/01/08 CPU#0 (Core#1): 48 32 50 76 3200.00
21:58:06 05/01/08 CPU#0 (Core#0): 46 31 50 38 3200.00
21:58:06 05/01/08 CPU#0 (Core#1): 48 32 50 78 3200.00
21:58:07 05/01/08 CPU#0 (Core#0): 46 31 50 36 3200.00
21:58:07 05/01/08 CPU#0 (Core#1): 47 32 50 78 3200.00
21:58:08 05/01/08 CPU#0 (Core#0): 46 31 50 34 3200.00
21:58:08 05/01/08 CPU#0 (Core#1): 47 32 50 59 3200.00
21:58:09 05/01/08 CPU#0 (Core#0): 47 31 50 42 3200.00
21:58:09 05/01/08 CPU#0 (Core#1): 47 32 50 58 3200.00
21:58:10 05/01/08 CPU#0 (Core#0): 46 31 50 53 3200.00
21:58:10 05/01/08 CPU#0 (Core#1): 47 32 50 59 3200.00

Frontlines: Fuel of War in the middle of combat...

22:02:15 05/01/08 CPU#0 (Core#0): 48 31 52 80 3200.00
22:02:15 05/01/08 CPU#0 (Core#1): 48 32 54 75 3200.00
22:02:16 05/01/08 CPU#0 (Core#0): 47 31 52 71 3200.00
22:02:16 05/01/08 CPU#0 (Core#1): 48 32 54 75 3200.00
22:02:17 05/01/08 CPU#0 (Core#0): 47 31 52 67 3200.00
22:02:17 05/01/08 CPU#0 (Core#1): 48 32 54 75 3200.00
22:02:18 05/01/08 CPU#0 (Core#0): 48 31 52 76 3200.00
22:02:18 05/01/08 CPU#0 (Core#1): 50 32 54 76 3200.00
22:02:19 05/01/08 CPU#0 (Core#0): 51 31 52 87 3200.00
22:02:19 05/01/08 CPU#0 (Core#1): 51 32 54 78 3200.00
22:02:20 05/01/08 CPU#0 (Core#0): 50 31 52 89 3200.00
22:02:20 05/01/08 CPU#0 (Core#1): 51 32 54 91 3200.00
22:02:21 05/01/08 CPU#0 (Core#0): 47 31 52 70 3200.00
22:02:21 05/01/08 CPU#0 (Core#1): 48 32 54 75 3200.00
22:02:22 05/01/08 CPU#0 (Core#0): 46 31 52 61 3200.00
22:02:22 05/01/08 CPU#0 (Core#1): 48 32 54 62 3200.00
22:02:23 05/01/08 CPU#0 (Core#0): 48 31 52 64 3200.00
22:02:23 05/01/08 CPU#0 (Core#1): 50 32 54 67 3200.00
22:02:24 05/01/08 CPU#0 (Core#0): 46 31 52 73 3200.00
22:02:24 05/01/08 CPU#0 (Core#1): 47 32 54 66 3200.00
22:02:25 05/01/08 CPU#0 (Core#0): 45 31 52 56 3200.00
22:02:25 05/01/08 CPU#0 (Core#1): 47 32 54 61 3200.00
22:02:26 05/01/08 CPU#0 (Core#0): 45 31 52 53 3200.00
22:02:26 05/01/08 CPU#0 (Core#1): 46 32 54 62 3200.00
22:02:27 05/01/08 CPU#0 (Core#0): 46 31 52 75 3200.00
22:02:27 05/01/08 CPU#0 (Core#1): 48 32 54 63 3200.00
22:02:28 05/01/08 CPU#0 (Core#0): 45 31 52 50 3200.00
22:02:28 05/01/08 CPU#0 (Core#1): 46 32 54 58 3200.00
22:02:29 05/01/08 CPU#0 (Core#0): 46 31 52 62 3200.00
22:02:29 05/01/08 CPU#0 (Core#1): 47 32 54 56 3200.00
22:02:30 05/01/08 CPU#0 (Core#0): 48 31 52 62 3200.00
22:02:30 05/01/08 CPU#0 (Core#1): 51 32 54 77 3200.00
22:02:31 05/01/08 CPU#0 (Core#0): 47 31 52 55 3200.00
22:02:31 05/01/08 CPU#0 (Core#1): 48 32 54 69 3200.00
22:02:32 05/01/08 CPU#0 (Core#0): 48 31 52 63 3200.00
22:02:32 05/01/08 CPU#0 (Core#1): 50 32 54 66 3200.00
22:02:33 05/01/08 CPU#0 (Core#0): 50 31 52 80 3200.00
22:02:33 05/01/08 CPU#0 (Core#1): 50 32 54 75 3200.00
22:02:34 05/01/08 CPU#0 (Core#0): 48 31 52 87 3200.00
22:02:34 05/01/08 CPU#0 (Core#1): 50 32 54 84 3200.00
22:02:35 05/01/08 CPU#0 (Core#0): 47 31 52 84 3200.00
22:02:35 05/01/08 CPU#0 (Core#1): 48 32 54 73 3200.00
22:02:36 05/01/08 CPU#0 (Core#0): 47 31 52 69 3200.00
22:02:36 05/01/08 CPU#0 (Core#1): 50 32 54 75 3200.00

I'd like a CoreTemp log capture of what game you claim will put 100/100 load on a dual core processor. Use stats from within the game and not game loading or map loading.

Mind you that I can get any game out there if I want to to put up beside yours. Let's have integrity on this.

Edit- Just for fun, a 720p x264 encoded movie (playing)...

22:09:05 05/01/08 CPU#0 (Core#0): 35 31 52 31 3200.00
22:09:05 05/01/08 CPU#0 (Core#1): 36 32 56 23 3200.00
22:09:06 05/01/08 CPU#0 (Core#0): 39 31 52 29 3200.00
22:09:06 05/01/08 CPU#0 (Core#1): 40 32 56 25 3200.00
22:09:07 05/01/08 CPU#0 (Core#0): 37 31 52 26 3200.00
22:09:07 05/01/08 CPU#0 (Core#1): 37 32 56 21 3200.00
22:09:08 05/01/08 CPU#0 (Core#0): 35 31 52 22 3200.00
22:09:08 05/01/08 CPU#0 (Core#1): 36 32 56 16 3200.00
22:09:09 05/01/08 CPU#0 (Core#0): 35 31 52 13 3200.00
22:09:09 05/01/08 CPU#0 (Core#1): 37 32 56 13 3200.00
22:09:10 05/01/08 CPU#0 (Core#0): 35 31 52 19 3200.00
22:09:10 05/01/08 CPU#0 (Core#1): 36 32 56 14 3200.00
22:09:11 05/01/08 CPU#0 (Core#0): 35 31 52 20 3200.00
22:09:11 05/01/08 CPU#0 (Core#1): 39 32 56 14 3200.00
22:09:12 05/01/08 CPU#0 (Core#0): 36 31 52 18 3200.00
22:09:12 05/01/08 CPU#0 (Core#1): 37 32 56 16 3200.00
22:09:13 05/01/08 CPU#0 (Core#0): 36 31 52 14 3200.00
22:09:13 05/01/08 CPU#0 (Core#1): 37 32 56 20 3200.00
22:09:14 05/01/08 CPU#0 (Core#0): 35 31 52 17 3200.00
22:09:14 05/01/08 CPU#0 (Core#1): 37 32 56 6 3200.00
22:09:15 05/01/08 CPU#0 (Core#0): 36 31 52 11 3200.00
22:09:15 05/01/08 CPU#0 (Core#1): 37 32 56 14 3200.00
22:09:16 05/01/08 CPU#0 (Core#0): 35 31 52 10 3200.00
22:09:16 05/01/08 CPU#0 (Core#1): 37 32 56 18 3200.00
22:09:17 05/01/08 CPU#0 (Core#0): 36 31 52 9 3200.00
22:09:17 05/01/08 CPU#0 (Core#1): 37 32 56 11 3200.00
22:09:18 05/01/08 CPU#0 (Core#0): 35 31 52 13 3200.00
22:09:18 05/01/08 CPU#0 (Core#1): 37 32 56 11 3200.00
22:09:19 05/01/08 CPU#0 (Core#0): 35 31 52 11 3200.00
22:09:19 05/01/08 CPU#0 (Core#1): 37 32 56 11 3200.00
22:09:20 05/01/08 CPU#0 (Core#0): 40 31 52 35 3200.00

[hat]

95... is this celcius?

[jonmcc33]

The big daddy test, encoding a video using Gordian Knot, XviD codec...

22:20:50 05/01/08 CPU#0 (Core#0): 47 31 52 83 3200.00
22:20:50 05/01/08 CPU#0 (Core#1): 51 32 56 92 3200.00
22:20:51 05/01/08 CPU#0 (Core#0): 47 31 52 80 3200.00
22:20:51 05/01/08 CPU#0 (Core#1): 50 32 56 98 3200.00
22:20:52 05/01/08 CPU#0 (Core#0): 47 31 52 72 3200.00
22:20:52 05/01/08 CPU#0 (Core#1): 51 32 56 100 3200.00
22:20:53 05/01/08 CPU#0 (Core#0): 46 31 52 78 3200.00
22:20:53 05/01/08 CPU#0 (Core#1): 51 32 56 98 3200.00
22:20:54 05/01/08 CPU#0 (Core#0): 47 31 52 63 3200.00
22:20:54 05/01/08 CPU#0 (Core#1): 51 32 56 100 3200.00
22:20:55 05/01/08 CPU#0 (Core#0): 47 31 52 66 3200.00
22:20:55 05/01/08 CPU#0 (Core#1): 51 32 56 100 3200.00
22:20:56 05/01/08 CPU#0 (Core#0): 47 31 52 77 3200.00
22:20:56 05/01/08 CPU#0 (Core#1): 51 32 56 95 3200.00
22:20:57 05/01/08 CPU#0 (Core#0): 47 31 52 69 3200.00
22:20:57 05/01/08 CPU#0 (Core#1): 51 32 56 100 3200.00
22:20:58 05/01/08 CPU#0 (Core#0): 47 31 52 70 3200.00
22:20:58 05/01/08 CPU#0 (Core#1): 51 32 56 97 3200.00
22:20:59 05/01/08 CPU#0 (Core#0): 48 31 52 69 3200.00
22:20:59 05/01/08 CPU#0 (Core#1): 51 32 56 100 3200.00
22:21:00 05/01/08 CPU#0 (Core#0): 47 31 52 70 3200.00
22:21:00 05/01/08 CPU#0 (Core#1): 51 32 56 100 3200.00
22:21:01 05/01/08 CPU#0 (Core#0): 47 31 52 75 3200.00
22:21:01 05/01/08 CPU#0 (Core#1): 51 32 56 100 3200.00
22:21:02 05/01/08 CPU#0 (Core#0): 48 31 52 72 3200.00
22:21:02 05/01/08 CPU#0 (Core#1): 51 32 56 97 3200.00
22:21:03 05/01/08 CPU#0 (Core#0): 48 31 52 89 3200.00
22:21:03 05/01/08 CPU#0 (Core#1): 51 32 56 95 3200.00
22:21:04 05/01/08 CPU#0 (Core#0): 48 31 52 72 3200.00
22:21:04 05/01/08 CPU#0 (Core#1): 51 32 56 98 3200.00
22:21:05 05/01/08 CPU#0 (Core#0): 47 31 52 78 3200.00
22:21:05 05/01/08 CPU#0 (Core#1): 51 32 56 98 3200.00
22:21:06 05/01/08 CPU#0 (Core#0): 48 31 52 78 3200.00
22:21:06 05/01/08 CPU#0 (Core#1): 51 32 56 100 3200.00
22:21:07 05/01/08 CPU#0 (Core#0): 48 31 52 86 3200.00
22:21:07 05/01/08 CPU#0 (Core#1): 52 32 56 98 3200.00
22:21:08 05/01/08 CPU#0 (Core#0): 50 31 52 63 3200.00
22:21:08 05/01/08 CPU#0 (Core#1): 50 32 56 100 3200.00
22:21:09 05/01/08 CPU#0 (Core#0): 47 31 52 72 3200.00
22:21:09 05/01/08 CPU#0 (Core#1): 51 32 56 100 3200.00
22:21:10 05/01/08 CPU#0 (Core#0): 48 31 52 72 3200.00
22:21:10 05/01/08 CPU#0 (Core#1): 51 32 56 94 3200.00
22:21:11 05/01/08 CPU#0 (Core#0): 48 31 52 83 3200.00
22:21:11 05/01/08 CPU#0 (Core#1): 52 32 56 94 3200.00
22:21:12 05/01/08 CPU#0 (Core#0): 48 31 52 84 3200.00
22:21:12 05/01/08 CPU#0 (Core#1): 51 32 56 94 3200.00

Again, it's the only thing I have ever seen come close to maxing out a dual core CPU that is a real world application. Temps still well under what Prime95 does to it.

[jonmcc33]

95... is this celcius?

No, again the number next to the clock speed (3200.00) is the processor load. You can see each core is logged for temperatures and load every second.

[newtekie1]

Gaming does not hit 100% CPU load on any multicore processor. Folding? Supposedly it doesn't use up any processor at all...

http://en.wikipedia.org/wiki/Folding%40home

The closest I have ever came to maxing out my processors was video encoding. One core will be maxed to 100% and the other average 50-70%.

You can post all the logs you want. Just because you don't hit 100% in the games you play doesn't mean others won't. Your first problem is that your X1900XT is holding your processor back. I on the other hand, am held back by my processor. I see 100% a lot when playing crysis because my CPU is holding my graphics card back.

And yes, Folding and all the other distributed computing programs puts the processor under 100% load constantly.

What software are you using to get the logs, I can show you my log.

actually 100% load is realistic if you game or fold or anything stressful you hit 100% so why would you not stress test @ 100%? that just seems stupid

Yes, it is very stupid. Which is why 100% stess testing has been recommended for years when overclocking. It isn't just about testing stability.

[jonmcc33]

Crysis? Okay, let me install that real quick and I'll get back to you with those logs too.

Edit- Gotta download the 1.2 patch so it will be about 25 minutes from now.

[jonmcc33]

Crysis 1.2 in the beginning of the game inside the transport plane...

20:40:20 05/02/08 CPU#0 (Core#0): 47 36 48 58 3200.00
20:40:20 05/02/08 CPU#0 (Core#1): 50 37 50 59 3200.00
20:40:21 05/02/08 CPU#0 (Core#0): 48 36 48 47 3200.00
20:40:21 05/02/08 CPU#0 (Core#1): 50 37 50 72 3200.00
20:40:22 05/02/08 CPU#0 (Core#0): 48 36 48 44 3200.00
20:40:22 05/02/08 CPU#0 (Core#1): 50 37 50 70 3200.00
20:40:23 05/02/08 CPU#0 (Core#0): 47 36 48 62 3200.00
20:40:23 05/02/08 CPU#0 (Core#1): 50 37 50 61 3200.00
20:40:24 05/02/08 CPU#0 (Core#0): 46 36 48 64 3200.00
20:40:24 05/02/08 CPU#0 (Core#1): 50 37 50 66 3200.00
20:40:25 05/02/08 CPU#0 (Core#0): 47 36 48 52 3200.00
20:40:25 05/02/08 CPU#0 (Core#1): 50 37 50 69 3200.00
20:40:26 05/02/08 CPU#0 (Core#0): 47 36 48 50 3200.00
20:40:26 05/02/08 CPU#0 (Core#1): 50 37 50 70 3200.00
20:40:27 05/02/08 CPU#0 (Core#0): 47 36 48 53 3200.00
20:40:27 05/02/08 CPU#0 (Core#1): 51 37 51 59 3200.00
20:40:28 05/02/08 CPU#0 (Core#0): 47 36 48 53 3200.00
20:40:28 05/02/08 CPU#0 (Core#1): 50 37 51 63 3200.00
20:40:29 05/02/08 CPU#0 (Core#0): 48 36 48 55 3200.00
20:40:29 05/02/08 CPU#0 (Core#1): 50 37 51 59 3200.00
20:40:30 05/02/08 CPU#0 (Core#0): 48 36 48 44 3200.00
20:40:30 05/02/08 CPU#0 (Core#1): 48 37 51 75 3200.00
20:40:31 05/02/08 CPU#0 (Core#0): 50 36 50 58 3200.00
20:40:31 05/02/08 CPU#0 (Core#1): 48 37 51 64 3200.00
20:40:32 05/02/08 CPU#0 (Core#0): 47 36 50 47 3200.00
20:40:32 05/02/08 CPU#0 (Core#1): 50 37 51 70 3200.00
20:40:33 05/02/08 CPU#0 (Core#0): 48 36 50 56 3200.00
20:40:33 05/02/08 CPU#0 (Core#1): 50 37 51 59 3200.00
20:40:34 05/02/08 CPU#0 (Core#0): 48 36 50 50 3200.00
20:40:34 05/02/08 CPU#0 (Core#1): 50 37 51 73 3200.00
20:40:35 05/02/08 CPU#0 (Core#0): 50 36 50 39 3200.00
20:40:35 05/02/08 CPU#0 (Core#1): 48 37 51 76 3200.00
20:40:36 05/02/08 CPU#0 (Core#0): 48 36 50 58 3200.00
20:40:36 05/02/08 CPU#0 (Core#1): 50 37 51 62 3200.00
20:40:37 05/02/08 CPU#0 (Core#0): 47 36 50 50 3200.00
20:40:37 05/02/08 CPU#0 (Core#1): 51 37 51 72 3200.00
20:40:38 05/02/08 CPU#0 (Core#0): 50 36 50 42 3200.00
20:40:38 05/02/08 CPU#0 (Core#1): 48 37 51 76 3200.00
20:40:39 05/02/08 CPU#0 (Core#0): 45 36 50 62 3200.00
20:40:39 05/02/08 CPU#0 (Core#1): 50 37 51 59 3200.00
20:40:40 05/02/08 CPU#0 (Core#0): 48 36 50 53 3200.00
20:40:40 05/02/08 CPU#0 (Core#1): 51 37 51 64 3200.00

Sure don't see it hitting 100% there and the settings are on medium w/o anti-aliasing. Is there a point in the game that both cores are supposed to be maxed at 100/100 or something?

Crysis 1.2 in game during combat at night...

20:48:40 05/02/08 CPU#0 (Core#0): 47 34 51 64 3200.00
20:48:40 05/02/08 CPU#0 (Core#1): 50 35 51 61 3200.00
20:48:41 05/02/08 CPU#0 (Core#0): 47 34 51 69 3200.00
20:48:41 05/02/08 CPU#0 (Core#1): 50 35 51 61 3200.00
20:48:42 05/02/08 CPU#0 (Core#0): 48 34 51 53 3200.00
20:48:42 05/02/08 CPU#0 (Core#1): 50 35 51 76 3200.00
20:48:43 05/02/08 CPU#0 (Core#0): 48 34 51 58 3200.00
20:48:43 05/02/08 CPU#0 (Core#1): 50 35 51 73 3200.00
20:48:44 05/02/08 CPU#0 (Core#0): 50 34 51 58 3200.00
20:48:44 05/02/08 CPU#0 (Core#1): 48 35 51 66 3200.00
20:48:45 05/02/08 CPU#0 (Core#0): 47 34 51 50 3200.00
20:48:45 05/02/08 CPU#0 (Core#1): 50 35 51 72 3200.00
20:48:46 05/02/08 CPU#0 (Core#0): 48 34 51 50 3200.00
20:48:46 05/02/08 CPU#0 (Core#1): 50 35 51 72 3200.00
20:48:47 05/02/08 CPU#0 (Core#0): 47 34 51 55 3200.00
20:48:47 05/02/08 CPU#0 (Core#1): 50 35 51 66 3200.00
20:48:48 05/02/08 CPU#0 (Core#0): 48 34 51 61 3200.00
20:48:48 05/02/08 CPU#0 (Core#1): 50 35 51 61 3200.00
20:48:49 05/02/08 CPU#0 (Core#0): 45 34 51 50 3200.00
20:48:49 05/02/08 CPU#0 (Core#1): 46 35 51 42 3200.00
20:48:50 05/02/08 CPU#0 (Core#0): 45 34 51 47 3200.00
20:48:50 05/02/08 CPU#0 (Core#1): 45 35 51 58 3200.00
20:48:51 05/02/08 CPU#0 (Core#0): 46 34 51 38 3200.00
20:48:51 05/02/08 CPU#0 (Core#1): 47 35 51 52 3200.00
20:48:52 05/02/08 CPU#0 (Core#0): 43 34 51 35 3200.00
20:48:52 05/02/08 CPU#0 (Core#1): 44 35 51 34 3200.00
20:48:53 05/02/08 CPU#0 (Core#0): 47 34 51 60 3200.00
20:48:53 05/02/08 CPU#0 (Core#1): 50 35 51 63 3200.00
20:48:54 05/02/08 CPU#0 (Core#0): 46 34 51 36 3200.00
20:48:54 05/02/08 CPU#0 (Core#1): 47 35 51 44 3200.00
20:48:55 05/02/08 CPU#0 (Core#0): 46 34 51 44 3200.00
20:48:55 05/02/08 CPU#0 (Core#1): 48 35 51 59 3200.00
20:48:56 05/02/08 CPU#0 (Core#0): 47 34 51 47 3200.00
20:48:56 05/02/08 CPU#0 (Core#1): 50 35 51 67 3200.00
20:48:57 05/02/08 CPU#0 (Core#0): 46 34 51 45 3200.00
20:48:57 05/02/08 CPU#0 (Core#1): 45 35 51 61 3200.00
20:48:58 05/02/08 CPU#0 (Core#0): 46 34 51 38 3200.00
20:48:58 05/02/08 CPU#0 (Core#1): 45 35 51 36 3200.00
20:48:59 05/02/08 CPU#0 (Core#0): 47 34 51 42 3200.00
20:48:59 05/02/08 CPU#0 (Core#1): 48 35 51 40 3200.00
20:49:00 05/02/08 CPU#0 (Core#0): 47 34 51 45 3200.00
20:49:00 05/02/08 CPU#0 (Core#1): 48 35 51 51 3200.00
20:49:01 05/02/08 CPU#0 (Core#0): 46 34 51 40 3200.00
20:49:01 05/02/08 CPU#0 (Core#1): 48 35 51 48 3200.00
20:49:02 05/02/08 CPU#0 (Core#0): 47 34 51 45 3200.00
20:49:02 05/02/08 CPU#0 (Core#1): 47 35 51 50 3200.00
20:49:03 05/02/08 CPU#0 (Core#0): 46 34 51 41 3200.00
20:49:03 05/02/08 CPU#0 (Core#1): 48 35 51 60 3200.00
20:49:04 05/02/08 CPU#0 (Core#0): 47 34 51 42 3200.00
20:49:04 05/02/08 CPU#0 (Core#1): 48 35 51 80 3200.00
20:49:05 05/02/08 CPU#0 (Core#0): 48 34 51 41 3200.00
20:49:05 05/02/08 CPU#0 (Core#1): 50 35 51 83 3200.00
20:49:06 05/02/08 CPU#0 (Core#0): 46 34 51 45 3200.00
20:49:06 05/02/08 CPU#0 (Core#1): 50 35 51 83 3200.00

Edit- I think I have made my point quite clear. No need to further debate this at all. Prime95 is good for really testing out a heatsink's performance but doesn't reflect real world load or heat output from a processor. Most people exist in the real world last time I checked.

[newtekie1]

No, you have just posted logs without actually reading anything anyone else has said. But if you think you have made your point clear, then by all means stop trying. The knowledgable of the group will continue to recommend the correct way, which is testing temperatures under 100% load.

You completely ignored the part about your weak graphics card holding your processor back, but whatever. If thinking you won makes you feel better...:rolleyes:

[jonmcc33]

No, you have just posted logs without actually reading anything anyone else has said. But if you think you have made your point clear, then by all means stop trying. The knowledgable of the group will continue to recommend the correct way, which is testing temperatures under 100% load.

You completely ignored the part about your weak graphics card holding your processor back, but whatever. If thinking you won makes you feel better...:rolleyes:

Um, you missed the point entirely.

The OP posted temperature and load of his Q6600 at stock clock speeds and inquired whether the retail stock cooler would work temporarily.

Someone replied that his CPU was idle (even though 3 of the 4 cores had active load at ~50%). I corrected him that those were not idle and in fact load temps.

He stated that load means 100% usage and no less and still believes that anything less than that is idle. :twitch:

Then I pointed out that any load is load, regardless of the percentage. I mentioned how no application would ever stress out a CPU the way that Prime95 does. I feel that the OP will be fine with the retail stock cooler at default clock speeds.

I wonder if you even read anything in this thread to be honest. But you were proven very wrong in claims of 100/100 CPU load in any application whether it be for gaming or video encoding. You haven't provided any proof of your claim either. I have shown plenty of proof even on a game you claim can max a CPU.

So, end of debate and I regret to inform you that you lost in more ways than one. Let's try something a little simpler next time...and be sure to provide some proof too. It doesn't look good when you don't bring any food to the table you know.

[Nitro-Max]

according to my G15 keyboard lcd display only 26 to 28% of the cpu gets used while playing crysis on my quad.

And yes i get what you mean general use very rarely brings on full load even running muliple apps and the temps never get as high as prime does mine hits 60c during prime when gaming and running apps in the background my cpu cores dont break 52c

[newtekie1]

Um, you missed the point entirely.

The OP posted temperature and load of his Q6600 at stock clock speeds and inquired whether the retail stock cooler would work temporarily.

Someone replied that his CPU was idle (even though 3 of the 4 cores had active load at ~50%). I corrected him that those were not idle and in fact load temps.

He stated that load means 100% usage and no less and still believes that anything less than that is idle. :twitch:

Then I pointed out that any load is load, regardless of the percentage. I mentioned how no application would ever stress out a CPU the way that Prime95 does. I feel that the OP will be fine with the retail stock cooler at default clock speeds.

I wonder if you even read anything in this thread to be honest. But you were proven very wrong in claims of 100/100 CPU load in any application whether it be for gaming or video encoding. You haven't provided any proof of your claim either. I have shown plenty of proof even on a game you claim can max a CPU.

So, end of debate and I regret to inform you that you lost in more ways than one. Let's try something a little simpler next time...and be sure to provide some proof too. It doesn't look good when you don't bring any food to the table you know.

No, you miss the point, probably because you have hard time reading and understand what others have said.

Can you tell me what the load on his processor were 1 second before he took the screenshot? Can you tell me what the load on his processor was 1 second after? No, because he wasn't properly putting it under load. If it was just under that 50% load for the second the screenshot was taken, then that tells us nothing about load temperatures. If the processor isn't maxed out with a stress test then I assume idle temps, because for all we know the processor is idle and the screenshot just caught a usage spike(which seems to be the case here since when he posted a screenshot "under load" the CPU actually had less load than his first shot).

I never argued that the stock cooler wouldn't be enough to cool his processor. However, if it is installed incorrctly, temperatures can get out of hand very quickly. And it is pretty easy to install the stock fan incorrectly, it is very easy to not get one of the pins in all the way and that alone would be enough to cause the CPU to overheat under load, which is why stress testing is important.

I wonder if you have read anything in this thread. Like where I said any of the Distributed computing programs out there puts the CPU under 100% load and yes it does cause them to get pretty toasty. I pointed out that several applications put the CPU under the same stress that Prime95 does. Just because you have never encounted them doesn't mean they don't exist. If you don't believe me install Folding@home and test for yourself.

Your logs aren't proof of anything, unless we are to take your word on what is actually running, which I don't because I doubt your ability to actually know what is running on your PC at this point. Posting random text logs is not proof of anything. Pictures on the other hand, well they speak 1000 words:

http://img.photobucket.com/albums/v296/newtekie1/Processexplorer1.png
http://img.photobucket.com/albums/v296/newtekie1/processexplorer2.png

So nothing in the real world stress the CPU to 100%? Do you still want to stick with that? These are programs run my millions of people, you are a fool if you assume that everyone uses the computer exactly the same way you do, which is why it is stupid to not test for the worst case.

I'm don't arguing with you, I've proven my point.

[jonmcc33]

Er, I don't see what your point is? This debate has already been settled.

Back to Atnevon, I'm sure that your temps are still fine with the stock retail heatsink. Sorry that this thread got a little off subject.

[echo75]

hey mate if its just a pin that broke on your other heatsink and you still have the stock cooler then you have no problem at all, just remove one of the clips from the stock and exchange that with the broken one.

Those clips are easy to remove, look carefully and u will see a clip-like lock on the black sleeve , use a small screw driver to push it back while appying pressure. it may be difficult for me to explain in detail, just look carefully at the plastic contraption and you will figure out the mechanic on what to press to release it from the heatsink.

[newtekie1]

Er, I don't see what your point is? This debate has already been settled.

I know it is settled, I settled it. I proved you wrong. Common people do see 100% usage, in fact that are over 2 Million people that run their CPU's at 100% just running Folding@home, there is another 1.5 Million running BIONIC. Take your ignorance elsewhere now.

Back to Atnevon, I'm sure that your temps are still fine with the stock retail heatsink. Sorry that this thread got a little off subject.

Right, back to Atnevon. I'm sure the stock heatsink will be fine for a week. However, run a stress test to make sure your temperatures stay acceptable, run Prime95 v25 to put the CPU under max load to make sure it will be totally safe.

[Atnevon]

Sorry too this thread went to hell.

Anyway, I have the heatsink back to newegg for RMA. Went fine getting back I assume. Hopefully it will get here by Thursday so I can get back to the 40s in load agian.

[newtekie1]

Sorry too this thread went to hell.

Anyway, I have the heatsink back to newegg for RMA. Went fine getting back I assume. Hopefully it will get here by Thursday so I can get back to the 40s in load agian.

Hopefully, you should be fine on the stock cooler for a week or two anyway.

[jonmcc33]

Sorry too this thread went to hell.

Anyway, I have the heatsink back to newegg for RMA. Went fine getting back I assume. Hopefully it will get here by Thursday so I can get back to the 40s in load agian.

You aren't overclocking and many actually do overclock with the retail heatsink. As long as you keep it under 70C you will be fine. Glad to help you out and avoid the confusion! :D

[DrPepper]

@jonmcc33 try supreme commander forged alliance 81km map 8 players ALX on rush and that will easily eat any cpu and whats wrong with testing it at 100% even it isn't realistic it means that in case the cpu does max out you know it won't overheat.

[jonmcc33]

@jonmcc33 try supreme commander that can easily eat any cpu and whats wrong with testing it at 100% even it isn't realistic it means that in case the cpu does max out you know it won't overheat.

RTS game? Ugh! I'll see if I can get it and post back with my results.

[DrPepper]

it won't be held back by a gpu just the cpu.