A computer components & hardware forum. HardwareBanter

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.

Go Back   Home » HardwareBanter forum » General Hardware & Peripherals » General Hardware
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

Help: Windows XP Spontanous shutdown



 
 
Thread Tools Display Modes
  #22  
Old June 5th 04, 09:14 PM
catchmerevisited
external usenet poster
 
Posts: n/a
Default

in article Dqowc.9677$B%4.1358@clgrps12,
at
wrote on 6/5/04 11:38 AM:

In calgary.general catchmerevisited wrote:

Video card . The same happened to me with an ATI all-in-one-wonder until I
updated the driver .
Good luck .


if that's the case, download from
http://www.ati.com

Is that where I get ati drivers from?

yep.

  #23  
Old June 8th 04, 03:42 AM
external usenet poster
 
Posts: n/a
Default

Well, I believe I've finall found the problem: Hot processor.

I determined this by noticing that the powerdowns happened primarily during
processor-intensive activities, such as unpacking a rarball. I was able
to reproduce spontaneous shutdown four times by unpacking a rarball.

It also appears that my proc temp is being mis-reported by "AsusProbe",
which is reporting the SOCKET temperature, not the DIODE temperature.
Diode temperature for the CPU is a steady 77.

I was able to determine this by installing Mother Board Monitor 5, which
gave far higher temperature readings for my CPU. At first, I thought it
may have been a bad-seating of the heatsink on the CPU, but touching the
heatsink, it is BLAZING hot... Thus, suggesting that it is conducting
properly. My processor (Barton 2500) is not overclocked

I've worked around the situation by underclocking my CPU. I'm now running
at a FSB of 100, instead of 166, which seems to be allowing my system to run
stable.

I still don't understand why my proc is suddenly generating so much heat.
My ambient temp is no hotter than usual (25C), nor have I made any changes
to the comp.

Anyhow, it's working, and I really don't notice the difference in speed...
Although there are still unsolved Q's, it's good enough for me.



--
.................................................. ............................

"Forced counseling and "sensitivity training" are nothing more than
buzzwords for political re-education"
-Letter in NY Times, Feb 2, 2000

.................................................. ............................
http://www.memeticcandiru.com
  #24  
Old June 8th 04, 05:19 AM
Whitelightning
external usenet poster
 
Posts: n/a
Default

W32MyDoom can cause random shut downs.
Whitelightning


  #25  
Old June 8th 04, 06:06 AM
Kelly
external usenet poster
 
Posts: n/a
Default

Ok....

--
All the Best,
Kelly

Microsoft-MVP Windows® XP
2004 Windows MVP "Winny" Award

Troubleshooting Windows XP
http://www.kellys-korner-xp.com

Taskbar Repair Tool Plus!
http://www.kellys-korner-xp.com/taskbarplus!.htm


"Whitelightning" wrote in message
...
W32MyDoom can cause random shut downs.
Whitelightning




  #26  
Old June 8th 04, 09:41 PM
di0nysus
external usenet poster
 
Posts: n/a
Default

wrote in message news:MI9xc.35270$DV4.3536@clgrps13...
Well, I believe I've finall found the problem: Hot processor.

I determined this by noticing that the powerdowns happened primarily during
processor-intensive activities, such as unpacking a rarball. I was able
to reproduce spontaneous shutdown four times by unpacking a rarball.

It also appears that my proc temp is being mis-reported by "AsusProbe",
which is reporting the SOCKET temperature, not the DIODE temperature.
Diode temperature for the CPU is a steady 77.

I was able to determine this by installing Mother Board Monitor 5, which
gave far higher temperature readings for my CPU. At first, I thought it
may have been a bad-seating of the heatsink on the CPU, but touching the
heatsink, it is BLAZING hot... Thus, suggesting that it is conducting
properly. My processor (Barton 2500) is not overclocked

I've worked around the situation by underclocking my CPU. I'm now running
at a FSB of 100, instead of 166, which seems to be allowing my system to run
stable.

I still don't understand why my proc is suddenly generating so much heat.
My ambient temp is no hotter than usual (25C), nor have I made any changes
to the comp.

Anyhow, it's working, and I really don't notice the difference in speed...
Although there are still unsolved Q's, it's good enough for me.



--
.................................................. ...........................

"Forced counseling and "sensitivity training" are nothing more than
buzzwords for political re-education"
-Letter in NY Times, Feb 2, 2000

.................................................. ...........................
http://www.memeticcandiru.com


I had a similar problem in the past, here's what I did:

Remove the power supply and cut a hole in the bottom (the side that
faces toward the floor). Install a fan to suck air from the case and
blow it into the power supply and eventually through the other fan and
out the back of the case. Then I covered the existing vent holes with
duct tape (yes... tape). In my case the new fan is right above the CPU
so it moves a ****load of air over the heatsink. just a thought...

You might also consider a better heatsink?
Reseat the processor and re-install the heatsink with new CPU grease?
  #27  
Old June 8th 04, 09:42 PM
di0nysus
external usenet poster
 
Posts: n/a
Default

wrote in message news:MI9xc.35270$DV4.3536@clgrps13...
Well, I believe I've finall found the problem: Hot processor.

I determined this by noticing that the powerdowns happened primarily during
processor-intensive activities, such as unpacking a rarball. I was able
to reproduce spontaneous shutdown four times by unpacking a rarball.

It also appears that my proc temp is being mis-reported by "AsusProbe",
which is reporting the SOCKET temperature, not the DIODE temperature.
Diode temperature for the CPU is a steady 77.

I was able to determine this by installing Mother Board Monitor 5, which
gave far higher temperature readings for my CPU. At first, I thought it
may have been a bad-seating of the heatsink on the CPU, but touching the
heatsink, it is BLAZING hot... Thus, suggesting that it is conducting
properly. My processor (Barton 2500) is not overclocked

I've worked around the situation by underclocking my CPU. I'm now running
at a FSB of 100, instead of 166, which seems to be allowing my system to run
stable.

I still don't understand why my proc is suddenly generating so much heat.
My ambient temp is no hotter than usual (25C), nor have I made any changes
to the comp.

Anyhow, it's working, and I really don't notice the difference in speed...
Although there are still unsolved Q's, it's good enough for me.



--
.................................................. ...........................

"Forced counseling and "sensitivity training" are nothing more than
buzzwords for political re-education"
-Letter in NY Times, Feb 2, 2000

.................................................. ...........................
http://www.memeticcandiru.com


Sorry... I should clarify that I covered the vent holes in the power
supply only, not the whole case
  #28  
Old June 8th 04, 10:02 PM
An Unexploded Scotsman
external usenet poster
 
Posts: n/a
Default

On Tue, 08 Jun 2004 02:42:52 GMT,
wrote:

Well, I believe I've finall found the problem: Hot processor.

I determined this by noticing that the powerdowns happened primarily during
processor-intensive activities, such as unpacking a rarball. I was able
to reproduce spontaneous shutdown four times by unpacking a rarball.

It also appears that my proc temp is being mis-reported by "AsusProbe",
which is reporting the SOCKET temperature, not the DIODE temperature.
Diode temperature for the CPU is a steady 77.

I was able to determine this by installing Mother Board Monitor 5, which
gave far higher temperature readings for my CPU. At first, I thought it
may have been a bad-seating of the heatsink on the CPU, but touching the
heatsink, it is BLAZING hot... Thus, suggesting that it is conducting
properly. My processor (Barton 2500) is not overclocked

I've worked around the situation by underclocking my CPU. I'm now running
at a FSB of 100, instead of 166, which seems to be allowing my system to run
stable.

I still don't understand why my proc is suddenly generating so much heat.
My ambient temp is no hotter than usual (25C), nor have I made any changes
to the comp.

Anyhow, it's working, and I really don't notice the difference in speed...
Although there are still unsolved Q's, it's good enough for me.


You're 100% sure your voltage is set to whatever a Barton 2500 wants?
If you decide to go for a replacement heatsink, I'm a big fan of
Zalman's stuff. I'm running a 2.4gHz P4 @ 3.5gHz and it's not much
warmer than it was before the overclock with a stock Intel heatsink.

http://www.zalmanusa.com/

Granted it's the size of a small toaster, but it does a nice job.
Very quiet too.
 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
64 bit - Windows Liberty 64bit, Windows Limited Edition 64 Bit, Microsoft SQL Server 2000 Developer Edition 64 Bit, IBM DB2 64 bit - new ! vvcd AMD x86-64 Processors 0 September 17th 04 09:07 PM
nVidia Windows Drivers "no sync" problem. Chris Nvidia Videocards 4 August 31st 04 01:49 AM
Will Windows Power the Living Room? Ablang Homebuilt PC's 32 July 8th 04 05:34 AM
Please help with new system - hangs when booting Windows 2000. Kevin Lawton Homebuilt PC's 7 April 14th 04 02:40 AM
Microsoft to force Windows updates? Steve Dell Computers 114 September 9th 03 02:11 AM


All times are GMT +1. The time now is 03:53 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 HardwareBanter.
The comments are property of their posters.