Computer just turns off

[Fab Foodie]

3 year old Mesh desktop Computer running Windows XP Pro, dual core processor, plenty memory space.
Been great to date. Recently just taken to switching off suddenly. Like somebodies pulled the plug, no warning. Also cannot get system restore to function.
Done all the usual clean-up stuff, checked power settings, Norton Antivirus all up to date, nothing obvious wrong. Any clues where to start?

 

[PK99]

3 year old Mesh desktop Computer running Windows XP Pro, dual core processor, plenty memory space.
Been great to date. Recently just taken to switching off suddenly. Like somebodies pulled the plug, no warning. Also cannot get system restore to function.
Done all the usual clean-up stuff, checked power settings, Norton Antivirus all up to date, nothing obvious wrong. Any clues where to start?

Check the main cooling fan - I recently had the same shut off problem on one of my pc's. the processor sipmly switches off to protect it self if it get too hot.

Tuned out that my fan was ok but the bit of plastic that holds the fan and cooling block down had fractured and left the block no longer in contact with the processor. Google and £6 got me a new bit!

 

[rogersavery]

most likely either overheating or faulty power supply

avoid system restore - it will cause more problems than it fixes and should only by used in certain circumstances ie mission critical and be prepared to wipe and reinstall everything

to check for overheating - remove the cover and check for dust blocking any of the fans
if clogged hold the fans and carefully blow out the dust (don't let the fans spin they will act as a generator and don't use a hoover, it statically charges the air)

faulty power supply is a case of getting a new one and see if it fixes the problem

 

[jeltz]

Over heating? Try vacuuming any vents, grills and fans. As well as the CPU heatsink/fan.

 

[Fab Foodie]

OK, seeing a trend here, will try this tomorrow... If I get the hoover and duster out now there'll be hell to pay!
Cheers, FF.

 

[mr_cellophane]

Check the System Event Log
and if you can change the BIOS setting to "Not restart after ASR" you should capture any BSOD

 

[Fab Foodie]

This is some of the mumbo-jumbo I've found in the Error Log going back to the start of the problem... Anything make sense?

The machine wide Default Launch and Activation security descriptor is invalid. It contains Access Control Entries with permissions that are invalid. The requested action was therefore not performed. This security permission can be corrected using the Component Services administrative tool.

The COM+ Event System detected a bad return code during its internal processing. HRESULT was 800706BA from line 44 of d:comxp_sp3comcom1xsrceve ntstier1eventsystemobj.cpp. Please contact Microsoft Product Support Services to report this error.

A condition has occurred that indicates this COM+ application is in an unstable state or is not functioning correctly. Assertion Failure: SUCCEEDED(hr) Server Application ID: {02D4B3F1-FD88-11D1-960D-00805 FC79235} Server Application Instance ID: {F919B434-C7E0-4B29-8158- A06AC57A53B9} Server Application Name: System Application The serious nature of this error has caused the process to terminate. Error Code = 0x8000ffff : Catastrophic failure COM+ Services Internals Information: File: f:xpsp3comcom1xsrccomsvcs trackertrksvrtrksvrimpl.cpp , Line: 3000 Comsvcs.dll file version: ENU 2001.12.4414.702 shp

The COM+ Event System detected a bad return code during its internal processing. HRESULT was 800706BA from line 44 of d:comxp_sp3comcom1xsrceve ntstier1eventsystemobj.cpp. Please contact Microsoft Product Support Services to report this error

Faulting application svchost.exe, version 0.0.0.0, faulting module unknown, version 0.0.0.0, fault address 0x00000000.

Hanging application iexplore.exe, version 8.0.6001.18702, hang module hungapp, version 0.0.0.0, hang address 0x00000000.

Failed extract of third-party root list from auto update cab at: with error: A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file.

Faulting application lws.exe, version 12.0.1280.0, faulting module lws.exe, version 12.0.1280.0, fault address 0x000d1847

 

[Fab Foodie]

Check the System Event Log
and if you can change the BIOS setting to "Not restart after ASR" you should capture any BSOD

How the heck do I do the BIOS bit????

 

[rh100]

You say the shutdown is immediate? If so then it suggests hardware, most likely power or heat problems as above. The usual culprit IME is the CPU cooler, either the fan stops OR the base of the heatsink has shifted away from the CPU. There will be some thermal paste between the heatsink and CPU, sometimes just removing the heatsink and respreading the paste around a bit (don't let it get anyware else - spreading is best done on the heatsink - not cpu), if you have to repaste with new make sure both parts are clean of the old stuff. Can be a fiddly job though, may be a job for the local geek.

As Roger suggests - don't use either a vacuum or air can - as apparently this can cause static - which is no good for electronics. Just take it outside and blow.

If you get warning of the shutdown - then check the logs and see if the times match the shutdown. Do you get a bluescreen (BSOD)?

Also - with the power off - just make sure all cards and connectors are seated properly.

 

[rh100]

This is some of the mumbo-jumbo I've found in the Error Log going back to the start of the problem... Anything make sense?

The machine wide Default Launch and Activation security descriptor is invalid. It contains Access Control Entries with permissions that are invalid. The requested action was therefore not performed. This security permission can be corrected using the Component Services administrative tool.

The COM+ Event System detected a bad return code during its internal processing. HRESULT was 800706BA from line 44 of d:comxp_sp3comcom1xsrceve ntstier1eventsystemobj.cpp. Please contact Microsoft Product Support Services to report this error.

A condition has occurred that indicates this COM+ application is in an unstable state or is not functioning correctly. Assertion Failure: SUCCEEDED(hr) Server Application ID: {02D4B3F1-FD88-11D1-960D-00805 FC79235} Server Application Instance ID: {F919B434-C7E0-4B29-8158- A06AC57A53B9} Server Application Name: System Application The serious nature of this error has caused the process to terminate. Error Code = 0x8000ffff : Catastrophic failure COM+ Services Internals Information: File: f:xpsp3comcom1xsrccomsvcs trackertrksvrtrksvrimpl.cpp , Line: 3000 Comsvcs.dll file version: ENU 2001.12.4414.702 shp

The COM+ Event System detected a bad return code during its internal processing. HRESULT was 800706BA from line 44 of d:comxp_sp3comcom1xsrceve ntstier1eventsystemobj.cpp. Please contact Microsoft Product Support Services to report this error

Faulting application svchost.exe, version 0.0.0.0, faulting module unknown, version 0.0.0.0, fault address 0x00000000.

Hanging application iexplore.exe, version 8.0.6001.18702, hang module hungapp, version 0.0.0.0, hang address 0x00000000.

Failed extract of third-party root list from auto update cab at: with error: A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file.

Faulting application lws.exe, version 12.0.1280.0, faulting module lws.exe, version 12.0.1280.0, fault address 0x000d1847

lws.exe seems to be something to do with Logitech web cam - do you have one of these loaded - if so maybe check/update/reinstall software and drivers.

 

[mr_cellophane]

I had a PC that just shut down at random times. I reseated the CPU and it has been OK since. I suspect it just lost a connection when it got warmed up.

 

[accountantpete]

You can download something like Speedfan which will give a temperature readout.

 

[just jim]

Mine did that, not a Mesh though. The power supply had failed. Not hard to replace.

 

[Fab Foodie]

Thanks everyone. Sound like it really could be temp related. I'll try and give it a good clean out and check fans, heatsinks etc. Cheers! FF.

 

[Fab Foodie]

lws.exe seems to be something to do with Logitech web cam - do you have one of these loaded - if so maybe check/update/reinstall software and drivers.

Thanks, I think there's a software update, I'll get it sorted.