[Fixed] BSOD - - - Crashing out of nowhere - - I have no idea what to do next?
[Fixed] BSOD - - - Crashing out of nowhere - - I have no idea what to do next?
Nice! Thanks for those BIOS hard-reset instructions. I didn't know that before. I'm going to do it after a BSOD happens. I'll run Memtest86 several times, check Windows Memory diagnostics, and also run Intel diagnostics. If there are other tools out there, I might use them too. Thank you! I will update this thread in a few days or right after the next BSOD occurs.
I've seen this happen a lot before, so I suggest resetting your BIOS hard reset, then doing a clean Windows install. Do not install Armory Crate. You don't actually need it to get the factory drivers; you can just grab those from the motherboard support page on your own computer. How many times have I had people use Armory Crate and end up with BSODs, freezing screens, errors, or slow performance? It's the same for most built-in tools no matter who made the board. Just skip all of them. Instead, do a clean install of Windows, keep checking for updates until you're done, then download and install the ASUS B660-I Gaming WiFi chipset drivers plus WiFi, LAN, Audio, and Bluetooth drivers. Make sure to get the ones that work with Windows 11 because the Windows 10 versions aren't always right and can cause issues. Also, make sure to install the latest driver for your graphics card, since you didn't mention it in this list but knowing which one is best would be helpful too. And don't forget drivers for any extra cards or accessories you might add later.
That last 0x3B BSOD was just weird for you and other stuff besides RAM could cause this too. If your RAM passes two tests in Memtest86, we think it is good right now. Turning off C States is a common trick to fix the 0x101 BSOD. Some CPUs are slow when they leave low power mode, which makes them miss an interrupt and causes that error. In all three of your 0x101 dumps, Processor #5 was the one missing the signal, so it's possible this is the problem. I've seen this happen before with AMD CPUs but less often on Intel ones. Turning off C States stops processors from entering low power states at the cost of more electricity and is a reliable fix. There isn't much else you can do if that is why these 0x101 BSODs are happening. It's also possible a rogue driver could cause this, so it might not be the CPU. If you get CLOCK_WATCHDOG_TIMEOUT BSODs please immediately copy the C:\Windows\Memory.dmp file to a safe place somewhere before they overwrite it by another error. Then upload several kernel dumps to give us a clearer picture of what's going on.
Hey guys, I found out that the CPU unit was defective. It was strange when I ran a stress test using Intel's XTU on my old CPU; nothing happened at all. The CPU usage stayed between 1% and 4%. When I tried the benchmark from the working version of XTU, the old CPU got stuck in constant thermal throttling right after it started within 2 seconds. The new CPU handles stress tests perfectly with much better thermals, mostly staying around 80 to 90 degrees. There were a few times when the old CPU had to slow down just for a short while to cool down, but that was all fine. The benchmark runs smoothly on the new one with a max temperature hitting about 88 degrees. Wish me luck and thank you all so much for your help!