Page fault condition remains unchanged
Page fault condition remains unchanged
OS: Windows 11 CPU: i7-13700K CPU cooling: iBuyPower triple rad, no temperature issues. Motherboard: ASRock Z690-C/D5 RAM: DDR5-6000MHz TEAMGROUP T-Force Delta GPU: RTX 3070 Ti Power supply: CORSAIR HX1000 Primary storage: 2TB WD Black SN770 M.2 PCIe Gen 4 NVMe SSD I purchased this machine from iBuyPower in late 2022 and it performed well until around February to March of this year (2024). At that point, it began experiencing crashes while running demanding software, first observed in Blender; it would freeze severely, requiring a self-repair. Updating the graphics driver didn’t help. I also noticed similar issues in certain games, eventually getting stuck in a blue screen loop after a crash during a session of Planet Crafter—Windows had to be reinstalled to resolve it (standard recovery tools failed). The main error codes appeared as: IRQL_NOT_LESS_OR_EQUAL KMODE_EXCEPTION_NOT_HANDLED PAGE_FAULT_IN_NONPAGED_AREA During the time I waited between crashes and reinstalling, I ran a full memory test and found no faults. After the Windows update, I handled the installation carefully but eventually got stuck in another BSOD loop after a few weeks, requiring a second reinstall. Since this issue has persisted, other programs have also acted oddly—Discord kept crashing constantly, and some games like Ship Graveyard Simulator 2 refused to launch, often accompanied by Blue Screens (usually only when Windows was functioning normally). To try solving it, I studied dump files and examined several Windows logs. They suggested a driver problem but didn’t specify which one. I also found logs for Discord and Ship Graveyard Simulator 2, indicating memory access errors likely caused by a faulty driver. This all seemed linked to a graphics driver update. Shortly after, I ran a DDU and attempted to install a Nvidia studio driver from the same period, but it failed. A full malware scan by Malwarebytes came back clean. After two OS reinstalls, I considered that recent drivers might be conflicting with my old BIOS. I downloaded and applied a newer BIOS for my motherboard, yet Windows refused to load properly—even though I could enter BIOS settings with the latest version visible. It now blocks loading entirely, instead looping into BSODs due to unhandled mode exceptions and page faults in nonpaged areas. At this stage, I’m unsure what to do next; I can’t even access Windows to share dump files. Unless someone knows a BIOS tweak that resolves this, I might have to reinstall Windows a third time.
Typically following a BIOS flash, remnants of previous BIOS settings can lead to crashes in new BIOS or the system itself. It’s often best to reset the BIOS to its original factory defaults. If you encounter issues, enter Troubleshoot mode, open a Command Prompt, and run SFC /scannow.
I recently tested both options after applying the default bios profile. It didn’t function properly, but I encountered a DRIVER_OVERRAN_STACK_BUFFER bsod error at one point. Additionally, a SYSTEM_THREAD_EXCEPTION_NOT_HANDLED bsod appeared during attempts to boot multiple times. Eventually, I reached troubleshooting mode via cmd and executed the command you provided. It indicated a corrupt file was detected, suggesting it could be fixed or resolved on restart. However, instead of a simple restart, it triggered a KERNEL_SECURITY_CHECK_FAILURE.
The uninstall updates feature didn't function properly. Although I'm not covered by the return warranty, I'm included in the standard warranty, which means I can request a replacement part if needed.
I wanted to know if it would be simpler for them to identify what’s not working, given they have many components available for testing. Page faults and kernel faults point toward a RAM or disk issue, but the problem could also stem from the CPU or mainboard because both manage RAM and disk operations.
Would have appreciated the dump files. The combination of crash errors often points to memory issues (random crashes are a warning sign). Memory isn't just about RAM, but it's typically the primary area to investigate and test first. Simply attempt to run the Windows installer using one stick at a time.