F5F Stay Refreshed Software Operating Systems Device powers off unexpectedly on Windows 8.

Device powers off unexpectedly on Windows 8.

Device powers off unexpectedly on Windows 8.

K
kcristan
Senior Member
514
04-15-2016, 10:34 PM
#1
My sister's computer is experiencing problems. It frequently powers off, at least twice daily. Previously it would occur occasionally, but lately it happens every day. After inspecting all her devices, I cleaned her system using CCleaner and cleared registry entries. I also did the same on another Windows 8 machine she owns. So far, only her laptop shuts down during activities like browsing the web. I’ve excluded overheating concerns—her machine stays cool and temperatures remain below 45°C. I noticed recurring errors in the system event logs each day:

- **Log Name:** System Source
- **Date:** 4/14/2014 12:47:16 PM
- **Event ID:** 41
- **Task Category:** (63) Level: Critical
- **Keywords:** ??
- **User:** SYSTEM
- **Computer:** Traci-ASUS
- **Description:** The system restarted without a clean shutdown. This might result from unresponsiveness, crashes, or power loss.

- **Log Name:** System Source
- **Date:** 4/14/2014 12:47:16 PM
- **Event ID:** 6
- **Task Category:** None
- **Level:** Error
- **Keywords:** User: SYSTEM
- **Computer:** Traci-ASUS
- **Description:** A registry operation related to I/O failed permanently. The registry couldn’t clear the hive file.

- **Log Name:** System Source
- **Date:** 4/14/2014 12:47:28 PM
- **Event ID:** 6008
- **Level:** Error
- **Keywords:** Classic User: N/A
- **Computer:** Traci-ASUS
- **Description:** The prior shutdown at 12:44:57 PM was unexpected.

I intend to upgrade her machine to Windows 8.1 to test if it resolves the issue, but I’d appreciate guidance from someone experienced with Windows 8 on this matter, especially if I need help identifying the cause and a solution later. What seems unusual is that her other laptop runs fine—used for gaming and other demanding tasks—and it’s less powerful than hers.
K
kcristan
04-15-2016, 10:34 PM #1

My sister's computer is experiencing problems. It frequently powers off, at least twice daily. Previously it would occur occasionally, but lately it happens every day. After inspecting all her devices, I cleaned her system using CCleaner and cleared registry entries. I also did the same on another Windows 8 machine she owns. So far, only her laptop shuts down during activities like browsing the web. I’ve excluded overheating concerns—her machine stays cool and temperatures remain below 45°C. I noticed recurring errors in the system event logs each day:

- **Log Name:** System Source
- **Date:** 4/14/2014 12:47:16 PM
- **Event ID:** 41
- **Task Category:** (63) Level: Critical
- **Keywords:** ??
- **User:** SYSTEM
- **Computer:** Traci-ASUS
- **Description:** The system restarted without a clean shutdown. This might result from unresponsiveness, crashes, or power loss.

- **Log Name:** System Source
- **Date:** 4/14/2014 12:47:16 PM
- **Event ID:** 6
- **Task Category:** None
- **Level:** Error
- **Keywords:** User: SYSTEM
- **Computer:** Traci-ASUS
- **Description:** A registry operation related to I/O failed permanently. The registry couldn’t clear the hive file.

- **Log Name:** System Source
- **Date:** 4/14/2014 12:47:28 PM
- **Event ID:** 6008
- **Level:** Error
- **Keywords:** Classic User: N/A
- **Computer:** Traci-ASUS
- **Description:** The prior shutdown at 12:44:57 PM was unexpected.

I intend to upgrade her machine to Windows 8.1 to test if it resolves the issue, but I’d appreciate guidance from someone experienced with Windows 8 on this matter, especially if I need help identifying the cause and a solution later. What seems unusual is that her other laptop runs fine—used for gaming and other demanding tasks—and it’s less powerful than hers.

G
galaxy13011
Junior Member
34
04-16-2016, 12:10 PM
#2
Avoid altering the registry; doing so often causes more issues than it solves. Consider reverting the system to its original state before attempting cleanup. Users who rely on registry cleaners usually face difficulties with Windows updates, upgrades, and service installations. Cleaning the registry offers no real advantage. It functions as a data storage system, enabling quick access to information regardless of size—whether it contains a single entry or millions. Check this forum for reference; it remains efficient despite increased activity. As noted in the event logs, the system abruptly stopped unexpectedly. This isn’t due to software malfunctioning or malware, but rather hardware failure. The second event indicates changes were made to the registry, possibly through RAM updates that didn’t fully transfer to storage. This likely coincided with an unexpected shutdown. If the problem occurred immediately after startup, it points to a hardware issue—such as failing capacitors that can’t hold charge or release it properly. This often leads to system crashes. Inspect the motherboard; a bad capacitor is usually visible. In most laptops, capacitors are solid and don’t show obvious damage. But if they’re faulty, other parts may be affected. Another cause could be overheating from a malfunctioning fan or sensor, triggering an emergency shutdown to protect the device. Verify the temperature readings. If they’re high, it’s probably the reason. The power cord or adapter might also be defective, especially since laptops rely on batteries. However, if the laptop struggles to maintain power and only fails when plugged in, the battery itself could be the culprit. The shutdown would then occur before the battery depletes completely.
G
galaxy13011
04-16-2016, 12:10 PM #2

Avoid altering the registry; doing so often causes more issues than it solves. Consider reverting the system to its original state before attempting cleanup. Users who rely on registry cleaners usually face difficulties with Windows updates, upgrades, and service installations. Cleaning the registry offers no real advantage. It functions as a data storage system, enabling quick access to information regardless of size—whether it contains a single entry or millions. Check this forum for reference; it remains efficient despite increased activity. As noted in the event logs, the system abruptly stopped unexpectedly. This isn’t due to software malfunctioning or malware, but rather hardware failure. The second event indicates changes were made to the registry, possibly through RAM updates that didn’t fully transfer to storage. This likely coincided with an unexpected shutdown. If the problem occurred immediately after startup, it points to a hardware issue—such as failing capacitors that can’t hold charge or release it properly. This often leads to system crashes. Inspect the motherboard; a bad capacitor is usually visible. In most laptops, capacitors are solid and don’t show obvious damage. But if they’re faulty, other parts may be affected. Another cause could be overheating from a malfunctioning fan or sensor, triggering an emergency shutdown to protect the device. Verify the temperature readings. If they’re high, it’s probably the reason. The power cord or adapter might also be defective, especially since laptops rely on batteries. However, if the laptop struggles to maintain power and only fails when plugged in, the battery itself could be the culprit. The shutdown would then occur before the battery depletes completely.

D
dniznemac
Senior Member
555
04-16-2016, 01:10 PM
#3
I’ll need to check with her about whether this has been ongoing since she purchased the laptop. Probably opening it up now would be pointless because it’s still covered under warranty. I’ll keep an eye on the temperature as well. While using a monitoring program and doing her regular tasks, the CPU stayed between 40 and 48°C, which I noticed earlier today. She confirmed that the problem didn’t appear until several months after buying the laptop. I’ve already suggested she review her warranty details, save her files, and contact the manufacturer since the device remains under protection. Thanks for sharing all this information! I’ll keep it in mind for future reference.
D
dniznemac
04-16-2016, 01:10 PM #3

I’ll need to check with her about whether this has been ongoing since she purchased the laptop. Probably opening it up now would be pointless because it’s still covered under warranty. I’ll keep an eye on the temperature as well. While using a monitoring program and doing her regular tasks, the CPU stayed between 40 and 48°C, which I noticed earlier today. She confirmed that the problem didn’t appear until several months after buying the laptop. I’ve already suggested she review her warranty details, save her files, and contact the manufacturer since the device remains under protection. Thanks for sharing all this information! I’ll keep it in mind for future reference.

S
Spalgra
Junior Member
4
04-17-2016, 08:05 AM
#4
Contact the manufacturer for a replacement. Avoid skipping the warranty—don’t just close things up and leave extra screws behind. If you’re shipping it, make sure to save all related data first. Based on the issue and model, they may replace the whole unit instead of just the faulty part, meaning the hardware could be new.
S
Spalgra
04-17-2016, 08:05 AM #4

Contact the manufacturer for a replacement. Avoid skipping the warranty—don’t just close things up and leave extra screws behind. If you’re shipping it, make sure to save all related data first. Based on the issue and model, they may replace the whole unit instead of just the faulty part, meaning the hardware could be new.

T
Tom01098
Junior Member
34
05-05-2016, 04:54 PM
#5
it turns off based on the ac battery status, not when it's connected to a power source.
T
Tom01098
05-05-2016, 04:54 PM #5

it turns off based on the ac battery status, not when it's connected to a power source.

D
David_8643
Junior Member
4
05-05-2016, 06:08 PM
#6
Indeed so.
D
David_8643
05-05-2016, 06:08 PM #6

Indeed so.

S
SgtSplash
Junior Member
9
05-07-2016, 11:31 AM
#7
I encountered a comparable problem with an Acer Aspire, but only when using the AC battery. I resolved it by turning off the "Power" service in msconfig.
S
SgtSplash
05-07-2016, 11:31 AM #7

I encountered a comparable problem with an Acer Aspire, but only when using the AC battery. I resolved it by turning off the "Power" service in msconfig.