Hi
seu03006234,
From the logs, the important part is
not Kernel-Power 41. That event only says Windows restarted unexpectedly. The real clue is:
BugcheckCode 340 = 0x154 = UNEXPECTED_STORE_EXCEPTION
That bugcheck usually points to the
storage stack: SSD/HDD/NVMe controller, Intel RST driver, disk firmware, file-system corruption, storage filter drivers, or sometimes RAM.
The other big clue is the repeated:
WHEA-Logger Event 17 — corrected hardware error
That suggests a
PCIe/device hardware or firmware issue is happening. Combined with
0x154, I would first suspect
storage / NVMe / controller / PCIe link, not Windows Defender or Explorer.
No dump file was included, so we cannot yet name the exact driver.
What I would do first
- Back up important data immediately.
Prioritize files on C: and D: because both are on the Intel NVMe SSD.
- Check SMART health for all drives using CrystalDiskInfo or the vendor tool.
Check especially:
INTEL SSDPEKNW512G8WDC WD10SPZX-22Z10T1TSD302 SCSI Disk Device
- Run these commands in Command Prompt as Administrator:
Code:
chkdsk C: /scan
chkdsk D: /scan
chkdsk F: /scan
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow
- For the
E: exFAT drive, back it up first, then run only if needed:
chkdsk E: /f
Warning: chkdsk /f can modify the file system. Undo is only possible from backup.
Update these drivers/firmware
Create a restore point first.
- Update BIOS from MACHENIKE/Clevo if a newer stable BIOS exists.
- Update Intel chipset driver.
- Update Intel Management Engine driver.
- Update Intel RST / storage driver.
- Update Intel UHD Graphics driver. Yours is very old:
27.20.100.9365 from 2021.
- Update Intel Wi-Fi/Bluetooth driver. Yours also appears old:
22.90.x.
Your NVIDIA driver is very new, but the Intel iGPU driver is old. On hybrid graphics laptops, mismatched graphics drivers can cause instability, though the
0x154 still makes me look at storage first.
Temporarily remove suspect kernel/virtual drivers
You have several virtual/filter drivers installed. For testing, uninstall or disable anything you do not currently need:
- Oray/Sunlogin remote-control components:
OrayIddDriver- Oray virtual USB/HID/display drivers
- VPN/TAP adapters:
- Old USB/debug/programmer drivers if not needed:
- Jungo
- IAR
- STLink
- TI XDS
- FTDI
- Nuvoton
- WCH CH341
Use
Apps & Features first, then reboot.
Undo: reinstall the needed vendor package later.
Test with minimal hardware
For one day, disconnect everything unnecessary:
- Remove external drives.
- Remove SD cards.
- Remove USB debug/programmer devices.
- Use only power, keyboard, mouse, and network.
If the BSOD stops, reconnect devices one at a time.
Enable proper crash dumps
Please enable small dumps so the next crash can be analyzed:
- Press
Win + R.
- Run
sysdm.cpl.
- Open Advanced.
- Under Startup and Recovery, click Settings.
- Set Write debugging information to
Small memory dump (256 KB).
- Set dump folder to
%SystemRoot%\Minidump.
- Reboot.
After the next BSOD, upload:
C:\Windows\Minidump\*.dmp
Zip the files first.
My current best guess
Most likely cause:
storage/PCIe hardware path problem, involving the Intel NVMe SSD, Intel RST driver, storage controller, BIOS/firmware, or one of the virtual/filter drivers interfering with storage/device I/O.
The repeated
WHEA Event 17 entries make this look more hardware/firmware-related than a normal software crash.
