If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
CPU temps stable, then rising w/o load?
I recently upgraded my system and now have a new AMD Athlon 64 3200+ on
a new ASUS K8V SE Deluxe mobo, with a new Enermax 470W "Noisetaker" PSU. Ambient temps have been consistenly in the 65-75F range, and for the couple of weeks I've had the new hardware running, the mobo and CPU temps have been pretty consistently in the 75-85F range (depending on load, of course, and lately I haven't been doing much as I also reorganized my hard drives and I'm still getting things reinstalled and reconfigured). Those temps are as reported by ASUS PC Probe, which I have running all the time in the background (i.e., tooltray). Tonight I got the unpleasant surprise of my system shutting down suddenly. No warning, no error, no alarm or alert from PC Probe, no gentle close -- just suddenly a dark screen, silence, and the monitor shifting into sleep mode. I powered it up again and it ran for a short time and then it shut down again, just as abruptly. Both times, the Ethernet indicators were still lit on the mobo and the PSU was doing it's post-shutdown cool-down (this PSU continues exhausting the case for a couple minutes after shutdown). My first "suspect" was a power problem, specifically with the UPS, because another of the same type that I got in the same order from newegg.com just went back w/ an RMA today. But it didn't really seem right, so I did some looking online in various discussion groups. Most pointed to either a PSU failure (possible) or a temp problem. I didn't think it would be temp related because the system wasn't under any real load and hadn't been on very long. The first time it happened, I was in the middle of rebooting after changing my network configuration. The second time it happened I was just reading a message in Mozilla mail. Despite thinking it wasn't a temp problem, I decided it was easy to check for that, so I booted the system and went right into the BIOS Setup. Watched, and didn't like what I saw. The mobo temp stayed in the same range it's been in, but the CPU was steadily climbing as I watched. When it got to 110F (after about 3 or 4 minutes) I shut it down, since I was already seeing what looked to me like bad behavior. (I'm assuming sitting and watching the hardware monitor in the BIOS Setup does not impose much of a CPU load -- am I wrong?) After awhile, I decided to ask online, so I booted up to Windows 2000. As I write this message, PC Probe is again saying that my CPU temp is in the 75-85F range (at the moment, 28C/82F). So maybe the problem has gone away for now, or maybe PC Probe isn't reporting temps correctly. I would appreciate ideas and input on this abrupt shutdown problem and/or the CPU temp behavior that I'm seeing. TIA, -- Stuart Whitmore , sans -bounce) Science fiction, politics, pretty models, & mo http://www.just-stuart.com/ |
#2
|
|||
|
|||
"S. Whitmore" wrote:
.... The first time it happened, I was in the middle of rebooting after changing my network configuration. The second time it happened I was just reading a message in Mozilla mail. I think that's your suspect (network, and input or video stuff). As a nuke style workaround, you could try switching from Windows NT to Windows XP, if possible. After awhile, I decided to ask online, so I booted up to Windows 2000. As I write this message, PC Probe is again saying that my CPU temp is in the 75-85F range (at the moment, 28C/82F). It's like Hawaii inside your case. So maybe the problem has gone away for now, or maybe PC Probe isn't reporting temps correctly. Because it's not over 85°F? Where did you get your information about CPU temperature, so I can avoid it. I would appreciate ideas and input on this abrupt shutdown problem and/or the CPU temp behavior that I'm seeing. My CPU temperature varies significantly with room temperature. You are overconcerned about CPU temperature. Next time, when it gets to 43°C, do not shut off your computer. Too hot for my CPU, in my opinion, is over about 52°C. The maximum operating temperature of an Athlon XP CPU is about 85°C which is 185°F. Good luck. -- United States and British intelligence agencies admittedly break the law while spying on each other. United States and British governments claim to energetically share that information. |
#3
|
|||
|
|||
John Doe wrote:
I think that's your suspect (network, and input or video stuff). To cause an abrupt shutdown? I'd consider that doubtful at best, based on my experience. As a nuke style workaround, you could try switching from Windows NT to Windows XP, if possible. Nope, not going to XP. Linux maybe, but not XP. Windows 2000 has been the most stable Microsoft OS I've used (well, other than MS-DOS 3.3 maybe), so I have no incentive at the moment to switch to something that adds the annoyance of "activation" just to play around with my system. It's like Hawaii inside your case. Ah, so the hula girls caused the shutdown. Figures! You are overconcerned about CPU temperature. No, I'm concerned about having my system shut off abruptly, without warning from either software tool I expected to warn me (i.e., the UPS monitoring software for power failures and ASUS PC Probe for temp or fan issues). Next time, when it gets to 43°C, do not shut off your computer. Too hot for my CPU, in my opinion, is over about 52°C. The maximum operating temperature of an Athlon XP CPU is about 85°C which is 185°F. Well, I didn't shut it down for being too hot. I shut it down because I was already seeing behavior that I didn't expect based on what I've observed in the week or two that I've had this upgraded system operational, and didn't want to sit and watch until it did climb too high (which, of course, was based on the assumption that it would continue rising). I wouldn't get concerned about the temperature itself until it was over 55C, based on what I've read about this chip (where 60C seems to be a key level). Sorry if I gave the wrong impression. -- Stuart Whitmore , sans -bounce) Science fiction, politics, pretty models, & mo http://www.just-stuart.com/ |
#4
|
|||
|
|||
"S. Whitmore" wrote:
John Doe wrote: "S. Whitmore" wrote: .... The first time it happened, I was in the middle of rebooting after changing my network configuration. The second time it happened I was just reading a message in Mozilla mail. I think that's your suspect (network, and input or video stuff). To cause an abrupt shutdown? Yes. As I recall, shutting down happens. These days, saying "shut down Windows" can do it. I'd consider that doubtful at best, based on my experience. I'm having trouble reading between the lines. Your entire original post dwelled on the idea that it was CPU overheating. Given the facts, I can't imagine a worse lead. As a nuke style workaround, you could try switching from Windows NT to Windows XP, if possible. Nope, not going to XP. Linux maybe, but not XP. Windows 2000 has been the most stable Microsoft OS I've used (well, other than MS-DOS 3.3 maybe), so I have no incentive at the moment to switch to something that adds the annoyance of "activation" just to play around with my system. There is an easy workaround. You are overconcerned about CPU temperature. No, I'm concerned about having my system shut off abruptly, without warning from either software tool I expected to warn me (i.e., the UPS monitoring software for power failures and ASUS PC Probe for temp or fan issues). I think it's a low-level software problem, but maybe you could test for that one if your BIOS allows an after power failure state of ON. .... 60C seems to be a key level). Sorry if I gave the wrong impression. -- Stuart Whitmore , sans -bounce) Science fiction, politics, pretty models, & mo http://www.just-stuart.com/ Path: newssvr30.news.prodigy.com!newsdbm05.news.prodigy. com!newsdst02.news.prodigy.com!newsmst01a.news.pro digy.com!prodigy.com!newscon06.news.prodigy.com!pr odigy.net!border1.nntp.dca.giganews.com!border2.nn tp.dca.giganews.com!nntp.giganews.com!cyclone1.gni link.net!spamkiller.gnilink.net!gnilink.net!trnddc 08.POSTED!287bbbc2!not-for-mail From: "S. Whitmore" usenet-bounce @just-stuart.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041217 X-Accept-Language: en-us, en MIME-Version: 1.0 Newsgroups: alt.comp.hardware.pc-homebuilt Subject: CPU temps stable, then rising w/o load? References: FcEOd.16937$uc.8354@trnddc04 In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Lines: 45 Message-ID: j6FOd.16206$uc.1566 @trnddc08 Date: Thu, 10 Feb 2005 08:40:47 GMT NNTP-Posting-Host: 4.27.235.166 X-Complaints-To: X-Trace: trnddc08 1108024847 4.27.235.166 (Thu, 10 Feb 2005 03:40:47 EST) NNTP-Posting-Date: Thu, 10 Feb 2005 03:40:47 EST Xref: newsmst01a.news.prodigy.com alt.comp.hardware.pc-homebuilt:429076 |
#5
|
|||
|
|||
S. Whitmore writes:
I recently upgraded my system and now have a new AMD Athlon 64 3200+ on a new ASUS K8V SE Deluxe mobo, with a new Enermax 470W "Noisetaker" PSU. But you left out the most important part: What OPERATING SYSTEM are you running? Some older versions of Windows (those not derived from Windows NT) don't actually halt the processor when they are idle; instead, they run a continuous "idle loop" that keeps the processor pegged at 100%. Some other older operating systems work the same way. More modern and better-written operating systems actually halt the processor when there is nothing to do. This is true for anything based on UNIX (including Mac OS X) and anything based on Windows NT (Windows NT itself, Windows 200x, and Windows XP). I don't know if the old Mac OS did this. If your machine is running an operating system with an "idle loop," temperatures will climb to just about the maximum even when the system seems quiet. -- Transpose hotmail and mxsmanic in my e-mail address to reach me directly. |
#6
|
|||
|
|||
S. Whitmore writes:
Nope, not going to XP. XP, 2000, and NT all have the same kernel and code base, so switching from one to another would make no difference in this case. -- Transpose hotmail and mxsmanic in my e-mail address to reach me directly. |
#7
|
|||
|
|||
Mxsmanic wrote:
S. Whitmore writes: Nope, not going to XP. XP, 2000, and NT all have the same kernel and code base, That is false. so switching to from one to another would make no difference in this case. That is wild speculation based on faulty information or at best based on a half truth. I'm not trying to sell Microsoft products. I'm simply trying to help the user solve his problem. Please keep in mind I called the suggestion about switching to Windows XP a "nuke style workaround". In fact, Windows XP is a more modern operating system which handles things better, whether or not you can cope with that idea. It was an uneasy upgrade for me as well. -- Transpose hotmail and mxsmanic in my e-mail address to reach me directly. Path: newssvr11.news.prodigy.com!newscon03.news.prodigy. com!newsmst01a.news.prodigy.com!prodigy.com!newsco n06.news.prodigy.com!prodigy.net!border1.nntp.dca. giganews.com!nntp.giganews.com!local1.nntp.dca.gig anews.com!news.giganews.com.POSTED!not-for-mail NNTP-Posting-Date: Thu, 10 Feb 2005 03:45:02 -0600 From: Mxsmanic From: Mxsmanic mxsmanic @hotmail.com Newsgroups: alt.comp.hardware.pc-homebuilt Subject: CPU temps stable, then rising w/o load? Date: Thu, 10 Feb 2005 10:45:02 +0100 Organization: None Message-ID: Message-ID: s8bm01hfbr6m6jmh3ur3vc3ss269cscb2r @4ax.com References: FcEOd.16937$uc.8354@trnddc04 j6FOd.16206$uc.1566@trnddc08 X-Newsreader: Forte Agent 2.0/32.652 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Lines: 9 X-Trace: sv3-qVijxNYX4GdNN0+krugUcV3UB0ZtsG8jU/f8ZhcCNuBKeBzRlwbNPqVFg4G9/Z+byz3dD8eobx08Mze!wVbM08iTYGwdH4U+E9REQCcXucQkX3P x/f0+VjlUATATHfD6JFVDEWwAgiBftsojlA== X-Complaints-To: X-DMCA-Notifications: http://www.giganews.com/info/dmca.html X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly X-Postfilter: 1.3.23 Xref: newsmst01a.news.prodigy.com alt.comp.hardware.pc-homebuilt:429083 |
#8
|
|||
|
|||
S. Whitmore wrote:
I recently upgraded my system and now have a new AMD Athlon 64 3200+ on a new ASUS K8V SE Deluxe mobo, with a new Enermax 470W "Noisetaker" PSU. Ambient temps have been consistenly in the 65-75F range, and for the couple of weeks I've had the new hardware running, the mobo and CPU temps have been pretty consistently in the 75-85F range (depending on load, of course, and lately I haven't been doing much as I also reorganized my hard drives and I'm still getting things reinstalled and reconfigured). Those temps are as reported by ASUS PC Probe, which I have running all the time in the background (i.e., tooltray). Tonight I got the unpleasant surprise of my system shutting down suddenly. No warning, no error, no alarm or alert from PC Probe, no gentle close -- just suddenly a dark screen, silence, and the monitor shifting into sleep mode. I powered it up again and it ran for a short time and then it shut down again, just as abruptly. Both times, the Ethernet indicators were still lit on the mobo and the PSU was doing it's post-shutdown cool-down (this PSU continues exhausting the case for a couple minutes after shutdown). My first "suspect" was a power problem, specifically with the UPS, because another of the same type that I got in the same order from newegg.com just went back w/ an RMA today. But it didn't really seem right, so I did some looking online in various discussion groups. Most pointed to either a PSU failure (possible) or a temp problem. I didn't think it would be temp related because the system wasn't under any real load and hadn't been on very long. The first time it happened, I was in the middle of rebooting after changing my network configuration. The second time it happened I was just reading a message in Mozilla mail. Despite thinking it wasn't a temp problem, I decided it was easy to check for that, so I booted the system and went right into the BIOS Setup. Watched, and didn't like what I saw. The mobo temp stayed in the same range it's been in, but the CPU was steadily climbing as I watched. When it got to 110F (after about 3 or 4 minutes) I shut it down, since I was already seeing what looked to me like bad behavior. (I'm assuming sitting and watching the hardware monitor in the BIOS Setup does not impose much of a CPU load -- am I wrong?) Yes, because the CPU does not go into any power saving or sleep modes when in the BIOS like it does when the operating system is at idle; which is most of the time if you're not doing anything intensive. After awhile, I decided to ask online, so I booted up to Windows 2000. As I write this message, PC Probe is again saying that my CPU temp is in the 75-85F range (at the moment, 28C/82F). So maybe the problem has gone away for now, or maybe PC Probe isn't reporting temps correctly. It's because the O.S. puts it in sleep mode when idle. I would appreciate ideas and input on this abrupt shutdown problem and/or the CPU temp behavior that I'm seeing. The shutdown could be caused by a myriad of things. Check your event logs, although your symptoms suggest it dies before an event could be recorded. TIA, |
#9
|
|||
|
|||
John Doe writes:
That is false. I've read the source code. That is wild speculation based on faulty information or at best based on a half truth. See above. Current Microsoft Windows operating systems are derived from the Windows NT code base, because NT is very well written. The base has evolved and differs somewhat from product to product, and there are cosmetic and configuration differences, but under the hood they are mostly the same, as careful examination of the operating systems reveals. -- Transpose hotmail and mxsmanic in my e-mail address to reach me directly. |
#10
|
|||
|
|||
Mxsmanic wrote:
S. Whitmore writes: I recently upgraded my system and now have a new AMD Athlon 64 3200+ on a new ASUS K8V SE Deluxe mobo, with a new Enermax 470W "Noisetaker" PSU. But you left out the most important part: What OPERATING SYSTEM are you running? Some older versions of Windows (those not derived from Windows NT) don't actually halt the processor when they are idle; instead, they run a continuous "idle loop" that keeps the processor pegged at 100%. Some other older operating systems work the same way. More modern and better-written operating systems actually halt the processor when there is nothing to do. This is true for anything based on UNIX (including Mac OS X) and anything based on Windows NT (Windows NT itself, Windows 200x, and Windows XP). I don't know if the old Mac OS did this. If your machine is running an operating system with an "idle loop," temperatures will climb to just about the maximum even when the system seems quiet. What is the typical behavior of BIOSes at idle? I had a Biostar M7NCD Pro with Athlon XP 2500+ (Barton). I normally run Linux, but I don't have a way to check CPU temp under Linux. But when it was idling in Linux and I shut Linux down and went immediately (without power down) into the health-status page of the BIOS, I would see the temp rise in about twenty minutes from about 38 C to about 48 C. So it seemed to run about 10 C hotter when idling in the BIOS than when idling in Linux. |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
pc problems after g card upgrade + sp2 | ben reed | Homebuilt PC's | 9 | November 30th 04 01:04 AM |
Overheating Overclocking PSU System Temps Inifinite Loop | Nick Le Lievre | Overclocking AMD Processors | 0 | November 27th 03 06:10 PM |
Pentium 4 2.4 temperatures | Lou Pratt | Homebuilt PC's | 6 | August 29th 03 01:17 AM |
CPU Idle and under load temps? | Whitesell \(Verizon\) | Overclocking AMD Processors | 2 | August 2nd 03 08:30 PM |
Athlon 2800 temps | Sparky | Overclocking AMD Processors | 2 | July 20th 03 03:23 PM |