First-time BSOD event caused by unintentionally damaging drivers.
First-time BSOD event caused by unintentionally damaging drivers.
Here’s a rephrased version of your message:
In short, I experience a sudden BSOD right after logging in following driver updates. I’ve been using my PC for about ten hours straight, and so far no fix has helped. I’m eager to learn about fresh ideas and have attached some dump files for reference.
My system specs include Windows 11 Pro 21H2, a Ryzen 5 3600 with MSI B450M DDR4 3000MHz RAM, an RTX 3070 Ti, a 1TB PCIe M2 NVMe SSD, and a 250GB SSD.
Over the past weeks, my PC has been running sluggishly. Windows showed frequent micro-stutters, games became unresponsive, and applications slowed down. I attempted to clean up the system and updated both Nvidia and AMD drivers (including Chipset and Ryzen Master). I believe this was the first issue I encountered, but I’ll explain it in more detail later.
After a restart, I logged in and immediately encountered a BSOD. I received three distinct error codes: IRQL_NOT_LESS_OR_EQUAL, KERNEL_MODE_HEAP_CORRUPTION, and BAD_POOL_CALLER. These codes didn’t appear normally, which is why no dump files were generated. However, during secure mode, two similar BSODs occurred, producing dump files (which I’ve attached).
I tried various troubleshooting steps in the Windows Recovery Environment: Startup Repair failed, Uninstall Updates didn’t help, System Restore was ineffective, and System Image Restore also didn’t work. The RAM diagnostic showed everything was normal, and the SSD was still functioning properly. Accessing files via a live Linux USB worked, but it didn’t resolve the problem.
I could back up important data using a live Linux installation, but that wasn’t an option. Switching off non-essential Windows services and programs in msconfig helped restore partial functionality, though only in a limited way.
Browsing through guides online, I’ve tried numerous solutions without success. I’m running out of options and desperately need any guidance or alternative approaches.
Thank you for your attention. I hope this detailed account helps clarify the situation. Please let me know if anything is missing. Your support means a lot!
Great news! The final answer came easy. The main issue was StoreMI. You could install an alternative driver for Windows instead of AMD's. Just look for drivers on your PC and pick one from the options. I used the regular controller and everything worked smoothly. It wasn't that hard at all!