kernel shutdown event 63

Question

EventLog - EventID 6008

it has caused kernel shutdown event 63

kernel shutdown happening all of a suden without warning

i have checked HWmonitor for voltages and overheating.

i have done sfc scan- no corrupted files

no malware with antivirus

battery health is ok

all drivers and ram is running perfectly

windows 10 as well. attached file New Text Document (3).txt

i have attached file related to event. please get back to me

Answer 1

Please check to see if your PC is producing any minidump files, I will check those to see if they provide any insight into a potential cause of the system crashes.

Please do not upload a very large Memory.dmp file.

Open Windows File Explorer.

Navigate to C:\Windows\Minidump

Copy any minidump files onto your Desktop, then zip those up.

Upload the zip file to the Cloud (OneDrive... etc.), then choose to share those and get a share link.

Then post the link here to the zip file, so I can take a look for you.

Answer 2

Event ID 6008 together with Kernel-Power Event ID 41 indicates that Windows detected an unexpected shutdown or reboot, not a normal, user-initiated one.

From the system log perspective:

• Event ID 41 (Source: Kernel-Power) means: the system rebooted without a clean shutdown. This typically happens if the system stopped responding, crashed, or lost power unexpectedly.
• Event ID 6008 (Source: EventLog) records: “The previous system shutdown was unexpected.”

These events do not by themselves identify the root cause; they only confirm that Windows did not shut down cleanly.

To investigate further using Event Viewer:

1. Open Event Viewer → Windows Logs → System.
2. Filter by these Event IDs to build a reboot history:
   • 12, 13, 6005, 6009 → show startup/shutdown history and OS version.
   • 41, 6008, 1001 → show unexpected shutdowns and bugchecks.
3. Look for patterns around each unexpected reboot:
   • Event ID 41 (Kernel-Power) and 6008 (EventLog) mark the unexpected reboot.
   • If present, Event ID 1001 (WER-SystemErrorReporting) indicates a bugcheck (blue screen) and points to a MEMORY.DMP path and bugcheck code.
   • Check for driver or software changes just before the first occurrence by also filtering for Event ID 19 (driver/package install) and 7045 (new service/driver installed).

Typical interpretations:

• Normal reboot sequence usually shows:
  • 1074 (User32) → 13 (Kernel-General) → 6009 (EventLog).
• Unexpected reboot sequence usually shows:
  • 41 (Kernel-Power) + 6008 (EventLog), often with 1001 (bugcheck) if a crash dump was generated.

Next steps based on what appears:

• If Event ID 1001 is present with a bugcheck code and MEMORY.DMP path, analyze that dump or share the bugcheck code with support to identify driver or kernel issues.
• If there is no 1001, focus on power-related causes (PSU, power cable, power strip, battery/AC adapter, sudden power loss) or hardware resets.
• Use the filtered history (12, 13, 19, 41, 1001, 1074, 6008, 6009, 7045) to correlate the first unexpected reboot with any new driver, firmware, or software installation.

This event pattern confirms that Windows is reporting an unexpected shutdown; the detailed cause must be derived from the surrounding events (especially 1001 and recent driver/service installs) and hardware/power checks.

---

References:

• Troubleshoot unexpected reboots using system event logs
• Event ID 6008 is unexpectedly logged to the System event log after you shut down and restart your computer