Hi Bob,
Thanks for sharing such a detailed account of your upgrade and the troubleshooting steps you’ve already taken. That kind of clarity makes a huge difference when trying to pinpoint what’s going on—and I can tell you’ve put a lot of time and effort into this already.
What We Know So Far
You upgraded from AMD to Intel i9 with an ASUS motherboard, 32GB RAM, and an RTX GPU.
You had initial boot issues due to leftover AMD drivers, which you resolved manually.
The system ran well for a while, but intermittent Blue Screens (Bugcheck 0x1E) started appearing.
You’ve tried SFC, DISM, and even swapped GPUs back to Radeon, which helped temporarily.
The issue resurfaced in July, and you’ve uploaded dump files for analysis.
That’s a solid timeline—and it gives us a few good leads.
What Might Be Happening
The 0x1E error (KMODE_EXCEPTION_NOT_HANDLED) typically points to a driver or kernel-level issue. Given the hardware swap and the persistence of the issue, here are a few possibilities:
Residual AMD Drivers or Registry Entries Even after removing AMD processors from Device Manager, some deep registry hooks or services might still linger. A clean install of Windows is often the safest route after a major platform change like this.
Driver Conflicts or Incomplete GPU Cleanup Switching between NVIDIA and AMD drivers can leave behind conflicting files. Using a tool like Display Driver Uninstaller (DDU) in Safe Mode can help fully remove both sets before reinstalling the preferred GPU driver.
BIOS or Chipset Drivers Make sure your ASUS motherboard has the latest BIOS version installed. Also, install the latest Intel chipset drivers directly from ASUS or Intel’s site—these can resolve subtle compatibility issues.
Memory or Storage Issues Run MemTest86 overnight to rule out RAM instability. Also, check your SSD/HDD health using tools like CrystalDiskInfo or the manufacturer’s diagnostic utility.
Windows Kernel or Third-Party Software Conflicts Some third-party utilities (especially system-level ones like antivirus, monitoring tools, or backup software) can cause kernel exceptions. Try a clean boot with only essential services running and see if the issue persists.
About the Dump Files
Thanks for uploading those. I’ll take a look at the dump sequences and see if any specific driver or module is consistently flagged. If you haven’t already, enabling Driver Verifier (with caution) can help catch problematic drivers—but it may also cause intentional crashes, so be sure to back up your data first.
Let’s take this one step at a time. If you’re open to it, I’d recommend starting with a full cleanup of GPU drivers using DDU, followed by a BIOS and chipset update. If the issue persists, we can dig deeper into the dump analysis and possibly consider a clean Windows install as a last resort.
I hope my answer is useful for you.
Warm regards,
Quinnie Quoc.