![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(38.4, 11%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECB%3C/text%3E%3C/svg%3E)
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(249.60000000000002, 12%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECN%3C/text%3E%3C/svg%3E)
Hi Claud Bog,
Thank you for reaching out to Microsoft Q&A forum. I understand how frustrating unexpected restarts can be. I’ve reviewed the crash details and summarized our findings and recommendations below.
Your system stopped with a KMODE_EXCEPTION_NOT_HANDLED error. In simple terms, Windows detected a low‑level hardware instruction that couldn’t be safely executed and shut the system down on purpose to protect stability and prevent potential data corruption.
The crash occurred inside a core Windows component that handles hardware timing and power management, and it happened while the system was transitioning into or out of an idle/power‑saving state. Virtualization features (such as Hyper‑V or Windows security virtualization) were active at the time, which is an important clue.
Please follow the steps below in order. Each one is safe and commonly resolves this type of crash:
Step 1: Update the system BIOS / UEFI
This is the most important step. The BIOS controls how the CPU handles power states and timing.
-Visit your device or motherboard manufacturer’s support website
-Check for and install the latest BIOS/UEFI update for your model
These updates often include fixes for CPU microcode, power management, and virtualization compatibility
Step 2: Install the latest chipset / platform drivers
Chipset drivers allow Windows to communicate correctly with the CPU and system firmware.
-Download the latest chipset or platform drivers (Intel or AMD) from the manufacturer’s site
-Avoid relying only on drivers provided automatically by Windows Update
Step 3: Temporarily disable virtualization features (for testing)
Because virtualization was active during the crash, we recommend a short test to confirm whether it’s contributing.
-If you don’t actively use Hyper‑V or virtual machines, temporarily turn off:
Hyper‑V
Windows Hypervisor Platform
Virtual Machine Platform
-Also check Windows Security → Device Security → Core Isolation, and temporarily disable Memory Integrity if enabled
This step is reversible and helps confirm the root cause.
Step 4: Check power and CPU settings
The crash happened during a power/idle transition.
Make sure there is no CPU overclocking or undervolting enabled
Use default BIOS settings if possible
Set Windows power mode to Balanced or High performance
Avoid third‑party tuning or performance utilities during testing
Step 5: Keep Windows fully up to date
Ensure all Windows updates are installed so the system is running with the latest stability fixes.
Please let me know once you’ve tried these steps, or if you’d like help with any of them. I’m happy to stay with you and continue troubleshooting if needed.
If you have additional questions about this answer, please click "Comment".
Note: If you want to receive email notifications about this thread, follow the steps in our documentation to enable email notifications.