New NVMe drives and RAM are triggering the kmode_exception_not_handled crash during BSOD cycles.
New NVMe drives and RAM are triggering the kmode_exception_not_handled crash during BSOD cycles.
Four days back I added a new NVMe SSD and two sticks of Vengeance LPX RAM to my computer. Right after installing the RAM, the machine powered on and then shut down several times before displaying an "unable to POST" error. I managed to resolve the timing and voltage issues for the RAM, but when I tried to boot into Windows, the 16GB of new memory was flagged as reserved, so I checked the msconfig settings to uncheck the maximum memory box. After restarting, the computer still showed a BSOD with the code kmode_exception_not_handled and no driver listed. It would keep rebooting until the same error appeared again. Using a fresh Windows installation on the new NVMe drive worked perfectly—my old SSD functioned normally and I was able to retrieve the dump files. I updated the BIOS to the latest version from the motherboard’s site, but the BSOD persisted. My hardware specs: AMD Ryzen 7 1700X (8-core, 3400MHz), ASUS TUF B450M-PRO (Gaming GPU, NVIDIA 3060 Ti), old SSD (Samsung 870 EVO 500GB), new SSD (Samsung 970 Evo Plus 1TB), old RAM (G Skill Ripjaws 2, 8GB, 3200MHz), new RAM (Corsair Vengeance LPX 2, 8GB, 3200MHz), 850W Bronze PSU. I would really appreciate any advice or support.
did you replace the ram or just change what you had? if you did, why? the previous setup was fine. when setting up windows, did you also install drivers for the amd chipset? i think am4 and am5 are quite selective about ram. it’s possible these two bundles don’t fit well together. run a memory test on all four sticks one at a time, using xmp off. xmp is meant for overclocking but can cause issues with different kits since each will use its own xmp profile from the first bank. from the cpu, usually slot 2 and 4, these turn on and off a few times during memory configuration changes. that’s called memory training and happens every time the memory settings are adjusted.
I kept the RAM in place without swapping them out. During the broken windows setup on the 870, I don’t recall any AMD drivers, but with the new temporary install I haven’t installed any and everything is functioning properly. I removed the Corsair RAM yet the kmode exception BSOD still appears. On the temporary Windows version of the 970, I ran a memory test and the GSKill RAM seems to be working well, though I haven’t checked the Corsair RAM yet.
If the Corsair's keeps failing, I'd return them and request a replacement part. It's important to install chipset drivers since many other device drivers won't work smoothly without them. Just make sure to use the official drivers available on the mainboard support page.
I installed the AMD chipset drivers on the new Windows, but it didn’t resolve the problem. I also moved the SSD from the faulty setup to another PC, yet the issue persisted.
What velocity are you aiming for with those four sticks? The memory controller isn’t designed for four sticks, so pushing high speeds will likely cause problems. Don’t worry about the RAM speed—this isn’t a match. Set it to the default 2133mhz and check if the issue continues.
I replaced the new sticks and have been using just the two old ones. The problem persists when trying to boot the old Windows setup. I’m sure there’s a file or configuration issue with the Windows system, but I’m not sure where to start fixing it.
A faulty RAM might lead to file corruption, which likely explains what you’re observing. You can attempt pressing F8 during startup (continue pressing until the postcode appears) and perform a system restore. This often resolves the issue, though it doesn’t always. Another option is booting into safe mode with networking (use the same F8 key), then open an elevated command prompt and run DISM.exe /Online /Cleanup-Image /Restorehealth. Execute that, followed by sfc /scannow to fix system files. For a more reliable solution, if you have another machine, use the Windows Media Creation Tool to generate a fresh installation USB. Boot from that USB, install your data while keeping personal information intact, and reinstall any programs you need.