PDA

View Full Version : Re: Windows XP overheats CPU and crashes


lugnut
December 5th 03, 01:46 AM
On Mon, 10 Feb 2003 21:39:21 -0800, "Shaun"
> wrote:

>It may be the motherboard. I have an ASUS A7S333
>Motherboard and have had somewhat the same problem. I
>have a 500 Watt power supply, 3 case fans, and for some
>reason the computer will just shut off every so often.
>Have had this problem sinse i got the computer. I even
>had the MB exchanged for a different one and still have
>the same problem, but just not as bad. I have monitored
>the temp of the case and the processor, monitored the
>power supply, and even put a new, better processor heat
>sink and fan. Never even came close to finding anything
>that would slightly cause it in the power supply, or in
>the tempature of anything.

The problem I have has only been found when I am running the
Timeslips billing software in conjunction with Windows XP.
No hardware combination seems to affect it as I have tried
the combination in several different machines over the past
several months. The later versions of Timeslips does not do
this. Unfortunately, the update utility that is provided
will not update the version I am haveing a problem with as
it should and Timeslips insist they have never heard of the
problem with either overheating or a failure to update with
their utility even though I can reproduce the problem every
time I put it together with XP. Unless, I can come up with
a solution to get the data updated to the new version or the
old software version patched somehow to correct the problem,
I am about to be in an expensive fix. At this point, I am
considering either going back to 98se which has it's own
problems or to Win2K. The application runs as it should
under either which tells me that something may be different
in WinXP to cause this. I fail to see how Timeslips cannot
be aware of the problem.

Thanks

>
>I did find that on mine it would not do it when i lowered
>the processor speed a few hundred MHz and it does not do
>it as bad sinse i got a new motherboard (but does still
>do it) so it comes down to it has to be the motherboard.
>
>Hope i was of some help
>
>>-----Original Message-----
>>On Mon, 10 Feb 2003 21:55:27 -0600, "Jim Macklin"
> wrote:
>>
>>>Some questions...
>>>1. Are all your fans working and clean?
>>
>>Yes. Have additional fans installed.
>>
>>>2. How many case fans?
>>
>>CPU fan, 3 case fans plus 2 in 500watt AMD certified PS
>>
>>>3. What mobo and CPU? What heat sink (s)?
>>
>>Asus A7V8
>>
>>>4. How hot is the ambient air temperature?
>>
>>about 68 F in room, case sensor indicates 82 F
>>
>>I don't think the cooling is the problem but, the 100%
>load
>>100% of the time that is indicated. I am hoping there
>is a
>>software setting or tweak that can be applied to force
>the
>>application to release the CPU or let it idle when it is
>not
>>active. Using multiple applications does not seem to be
>a
>>problem which I think indicates the other applications
>are
>>able to use CPU resources but, those resources are again
>>grabbed by this application when any process is
>completed.
>>
>>Thanks
>>
>>>
>>>
>>>"lugnut" > wrote in message
...
>>>| I have problem with windows XP Pro and the CPU running
>>>very
>>>| hot at all times and shutting down when ambient temps
>are
>>>| warm. It only does this when I am using y Timeslips
>V8
>>>| billing software. According to the taskmanager, the
>CPU
>>>is
>>>| at 100% load when this software is running and the CPU
>>>temp
>>>| is within 5 deg F of the CPU shutdown temp. As soon
>as
>>>the
>>>| application is closed, the temp drops back down
>>>dramatically
>>>| and the task manager shows only 4-5% useage wjen idle
>as
>>>it
>>>| should. I have tried re-installing the application
>on a
>>>| similar Win98SE machine without finding this problem.
>>>Aslo,
>>>| I believe this application uses a Borland database
>engine.
>>>| Has anyone else crossed this problem and if so, was
>there
>>>a
>>>| cure? There is an upgrade on the application but, I
>do
>>>not
>>>| want to upgrade because all of the data for several
>>>hundred
>>>| clients would have to be re-entered manually.
>>>|
>>>| A post back to the NG would be greatly appreciated.
>>>|
>>>| Thanks
>>>|
>>>
>>
>>
>>.
>>

lugnut
December 5th 03, 01:46 AM
On Tue, 11 Feb 2003 08:02:52 -0800, "Rick" >
wrote:

>You never answered what CPU.(?)
>
>What are you using to get the temps, and what
>temperature are you set to shut off at?

Sorry, It is an AMD XP1800+ on Asus A7V8R main board with
512mb Crucial DDR 333 RAM. Shutdown is set at BIOS default
60 C and all voltages and clock speeds at default for this
CPU. I tried reducing the core voltage as far down as 1.7v
at which point it became generally unstable. Temps with
this app running is 58-59C which is very close. If the
ambient room temp rises into the mid 70's, I can expect
shutdown. W/O this app running, temps are 37-38C. I am not
familiar with AMD specs as I just set the board to secs for
the CPU when I buyilt it. Again, this problem has not
followed hardware as it has been used successfully with
other hardware combinanations. It has followed the Windows
XP/Timeslips combination in several machines while trying to
isolate the problem. When I move the Timeslips application
to any other OS, the problem disappears.

Thanks again and any help that can be offered will be
greatly appreciated. I am just at witts end.

>
>Example: I have an AMD AthlonXP 1700+ running at
>CPU 99*F, Case 71*F, Room temp 67.8*F
>(CPU 37*C, Case 22*C, )
>I can run CPU at MAX 90*C (according to the AMD docs),
>but I have never seen it go over 55*C even when the
>room temp was over 100*F.
>Sorry for all the different "C" and "F" mixing...
>
>>-----Original Message-----
>>>Some questions...
>>>1. Are all your fans working and clean?
>>
>>Yes. Have additional fans installed.
>>
>>>2. How many case fans?
>>
>>CPU fan, 3 case fans plus 2 in 500watt AMD certified PS
>>
>>>3. What mobo and CPU? What heat sink (s)?
>>
>>Asus A7V8
>>
>>>4. How hot is the ambient air temperature?
>>
>>about 68 F in room, case sensor indicates 82 F
>>
>>I don't think the cooling is the problem but, the 100%
>load
>>100% of the time that is indicated.

Google