Windows XP acting up
#1
Posted 02 October 2005 - 04:08 PM
#3
Posted 02 October 2005 - 04:58 PM
If you feel safe opening your PC cover, you could try to remove some of the dust inside.
How many case fans do you have?
Also, what is the error message?
#4
Posted 02 October 2005 - 05:25 PM
After you do what wannabe1 said:
If you feel safe opening your PC cover, you could try to remove some of the dust inside.
How many case fans do you have?
Also, what is the error message?
Its a laptop so I can't think very many fans. The error message is not up long enough to see entirely, but the main error i see is "invalid queue item" i believe.
#5
Posted 02 October 2005 - 05:43 PM
#6
Posted 02 October 2005 - 05:47 PM
#7
Posted 02 October 2005 - 05:49 PM
The ACPI reference in your last post piqued my interest.
Click Start then Run and type eventvwr.msc and click "Ok". In the left pane, click "System"...in the right pane, are there any red circles next to errors referencing acpi?
wannabe1
Edited by wannabe1, 02 October 2005 - 05:53 PM.
#8
Posted 02 October 2005 - 06:58 PM
ist643...
The ACPI reference in your last post piqued my interest.
Click Start then Run and type eventvwr.msc and click "Ok". In the left pane, click "System"...in the right pane, are there any red circles next to errors referencing acpi?
wannabe1
No acpis listed at all in the event log, but there are loads of errors, the majority of them showing up next to the "DCOM" and "cdrom" sources. For the record, 60C now the temp showing up....I've been told anytihng more than 50 is bad
#9
Posted 02 October 2005 - 07:44 PM
It started out too hot and got worse. Can you hear the fan running in there? You might try a can of compressed air and see if you can get the CPU cooler as clean as possible. For now, prop the back of the machine on a book or something to get some airspace under it and see if it cools down a little. Maybe a notebook cooler would be a good investment for you. Definitely try to get the dust out of it, though.
Might also be time for a new CPU fan.
Kinda thought this was a heat problem from the git go....just wanted a little verification.
wannabe1
Similar Topics
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users