Event ID 17, WHEA-Logger and system freezing?
Event ID 17, WHEA-Logger and system freezing?
Hello,
I swapped out my GPU and soon experienced the first freeze on my Windows 11 system. After examining the Event Viewer, I found thousands of yellow warnings labeled "Event ID 17, WHEA-Logger." I ran several diagnostic tools: sfc /scannow, Dism /Online /Cleanup-Image /ScanHealth, Dism /Online /Cleanup-Image /CheckHealth, and Dism /Online /Cleanup-Image /RestoreHealth. Despite uninstalling the GPU driver using Display Driver Uninstaller in safe mode and installing the newest drivers, the issue continued. I also tried running SysnativeBSODCollectionApp and uploaded my ZIP file for further assistance.
Welcome to the forums, newcomer!
my windows 11 computer
Please list the specs to your build like so:
CPU:
CPU cooler:
Motherboard:
Ram:
SSD/HDD:
GPU:
PSU:
Chassis:
OS:
Monitor:
include the age of the PSU apart from it's make and model. BIOS version for your motherboard at this moment of time.
You stated;
I replace my GPU
What GPU were you on and what GPU did you upgrade to?
gtx 1660 super was my previous and RTX5060 ti 16gb is the new
CPU: I5 13500
CPU cooler:ARCTIC FREEZER I35 RGB
Motherboard: Gigabyte B760M DS3H DD4 (BIOS: AMI F21)
Ram: 2x G.Skill DDR4-3602 16GB
SSD/HDD: KINGSTON SKC3000D2048G and Samsung SSD 980 1TB
GPU: (Palit Microsystems) NVIDIA GeForce RTX 5060 Ti
PSU: Corsair RM850e (got it around may 2023)
Chassis: Corsair 7000D Airflow
OS: windows 11
Monitor: DellG2724D and SE2416H
Did you apply DDU to completely remove the driver for the GTX1660 graphics card prior to installing the RTX5060? If not, proceed with DDU now to delete all graphics drivers (it will restart) and then install the newest RTX5060 driver.
The WHEA warnings pertain to the PCIe root port, suggesting the previous driver might be conflicting or the new card could be defective.
The dump indicates a DPC_WATCHDOG_VIOLATION, but for a high IRQL run we’d need the kernel dump to investigate further. The file is large—C:\Windows\Memory.dmp—and should be uploaded for analysis.
I’m also noticing numerous live kernel events with codes 0x1A8 and 0x1B8, which are typically black screen errors. These may stem from holding the power button during a reboot, so uploading these dumps now isn’t necessary.
Additionally, there are more memory-related Application Error messages in your log than expected. They point to possible RAM issues, possibly caused by disturbing a RAM card when swapping graphics cards. I recommend first removing and reinserting the RAM modules fully. If that doesn’t resolve the problem, run Memtest86 on your RAM.
Download
Memtest86 (free), use the extracted imageUSB.exe tool to create a bootable USB drive with Memtest86 (1GB is sufficient).
Perform this on another PC if possible, as you can’t fully rely on your current system at this stage.
After booting the USB, Memtest86 will begin scanning immediately.
If no errors appear after completing four iterations of the 13 tests in the free version, restart Memtest86 and repeat with another set of four tests.
Even a single bit error indicates a failure.