system will shut down and no error will appear

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

My system it is shutting down after a couple of minutes in idle or if try to run any program.
 
Hi

Shutdown or reboot?

--

Will Denny
MS-MVP Windows - Shell/User


| My system it is shutting down after a couple of minutes in idle or if try
to run any program.
 
no error at all, system just turn off. used full batery and good ac power. I wil like to know if there is a virus that will keep the fan from running and making the system over heat. i do see the fan running and stoping but i am not sure if is enough air flow. this problem started after a wireless card for dsl was broken inside the slot. this is a presario notebook 1200
 
it will just shut down. If I power up again , it will do a scan of the disk and it will power up until you try to run any program.win media player will run for a couple minutes and it will power down.
 
roberto said:
it will just shut down. If I power up again , it will do a scan of the
disk and it will power up until you try to run any program.win media
player will run for a couple minutes and it will power down.
Click to expand...

Have you got a CPU/HW monitor? If so what temperature are you getting for
the CPU - could be a temperature problem. Also wasn't this what the Sasser
virus was meant to cause (or was that just a re-boot?)?

BillL
 
I'm having a similar problem on a desktop and I am NOT overheating. I've got more cooling than Greenland.
 
Hi

I seem to have the simular problem, but running on a regular desktop/tower PC

System all of a sudden powers off, and I have a power supply with 2 fans, video card with built-in cooling fan..

I run a motherboard diagnostic utility, and it indicates NO overheating at all

But all of a sudden, the computer powers down/shuts off

Since this has started recently (after installing a virus detection program and latest windows updates) I'll start rolling backwards uninstalling patches/virus protection program to see if that solves it..

I have a feeling there is a interupt sent from the OS, that cuses this.. In other words, something really wrong in the code somewhere...

I've updated every HW piece in my comp. with BIOS/SW updates...
 
Back
Top