Experiencing BSODs repeatedly after two months is unusual. Check system health and update drivers regularly.
Experiencing BSODs repeatedly after two months is unusual. Check system health and update drivers regularly.
Hello everyone, in January I shared my experience with frequent PC crashes and blue screens on this forum. Thanks to all of you, I managed to resolve the issues, but after two months without any problems, a Windows update triggered another set of BSODs. System service exceptions and error codes like "Irql not less or equal" keep appearing. Earlier, fixing these crashes was simple—just disabling XMP and adjusting the Performance Core Ratio in Intel's XTU app to 55x helped with the 14900K. Now, following the update, I’m experiencing them again. The timing of each crash seems random; sometimes it happens during browsing or watching videos, other times without warning. Previously, launching any game caused an immediate crash, but now games run smoothly. I also tried the steps from the BSOD Posting guide, but the link didn’t work properly. After some research, I think I found the right solution. However, I couldn’t complete the 'perfmon /report' action—it stuck at collecting data for over 20 minutes. The attached zip file from Sysnative seems to have helped, but my PC’s lights are now out of sync and can’t be resynchronized automatically. Also, occasionally I see a warning about CPU fan speed during boot, yet everything runs fine when checked. I disabled that alert in the BIOS. Any advice would be greatly appreciated!
PC details:
- OS: Windows 11 Home
- Build: 22631.323 (64-bit)
- CPU: Intel Core I9-14900K
- GPU: Asus RTX 4070 Ti (overclocked)
- Motherboard: Asus ROG Strix Z790-H Gaming
- SSD: Samsung 990 Pro 2TB
- RAM: G.Skill 64 DDR5-6000 Trident Z5 RGB
- Power supply: be quiet pure power 12M 1000W
- Case fans: DeepCool FC120 (3 units)
- Case: Lian Li O11 Dynamic EVO midi tower
- Software: SysnativeFileCollectionApp.zip
It's rare that these crashes are identical, yet they consistently occur during memory allocation or deallocation. Memory refers to RAM, but it can also involve storage like the page file or the CPU since the memory controller is part of the processor. I observed Aura RGB was active in two instances and several RGB utilities are known to damage memory. I don’t recall seeing Aura before, but with so many tools doing this, they might rely on a shared open-source DLL file with a problem. iCUE and RGB Fusion appear frequently, though it’s unclear if they’re common or problematic. The other three involved storage (Gameflt.sys, Xbox app storage driver, and DWM) and the system’s window manager. Overall, the RGB isn’t the most likely culprit. I’d suggest removing Aura and any other installed RGB software, then run an SFC scan to check for OS corruption that could affect upcoming updates.
Uninstalling Aura means removing the entire Armoury Crate, since that's where I manage my lights. Are you sure you have to accept this limitation? Is there another tool that can handle light control? I suspect you're right—when those BSODs appear, I get notifications about setting up my ASUS components in the Armoury Crate app. I plan to try removing it and see how it affects things. Also, I should note from the original post that I ran an SFC once, which fixed a corrupt file, but after that it didn't work again, and I'm still experiencing those BSODs.
Yes, proceed cautiously. Run a test after uninstalling. If the issue stops, consider reinstalling or switching to alternative RGB applications. Avoid the programs I suggested; I’ve turned off all RGB settings to prevent further questions about alternatives.
No clear patterns appear in the dump files beyond the Windows kernel. Possible corruption might be involved. When memory is affected—storage, RAM, or controller—it's uncommon for the same crash to repeat consistently since data corruption is random. This often points to various drivers being impacted, which is typical with memory issues. It’s worth noting that assigning blame to specific drivers isn’t always accurate; it usually involves listing processes or drivers that handled bad data. TL;DR: Uncertain, but OS corruption seems likely.
You should consider replacing the RAM if the diagnostic indicates hardware issues. It’s better to address the problem early rather than risking further damage.
Warranty covers RAM for life; reach out to G.Skill or the retailer. They may not accept the lifetime guarantee, but standard coverage is usually quicker. Should they decline, get in touch with G.Skill.