Experience BSODs with different error codes. Decide whether to start fresh or try to resolve them.
Experience BSODs with different error codes. Decide whether to start fresh or try to resolve them.
Here’s a revised version of your text:
I’d like to start with a warm welcome to everyone. I purchased my setup in 2021 and it includes these components: CPU – i5 10400F, RAM – 2x8GB DDR4 at 3200 MHz, GPU – 3060 Ti, Power supply – Seasonic 550W, SSD – 500GB MX500 (released 5 years ago), SATA OS – Windows 10 64-bit.
First problem: Windows indicated a disk error on C drive and suggested fixing it. I’ve mostly ignored it since several apps showed the SSD health at 96% and all green lights.
Second issue: During boot, I encountered a prompt asking me to stop disk checking for about 8...6...7 seconds. After that, I was presented with the default Windows 10 installation image. Once I entered my password, it would take roughly 2:30 or 3:00 minutes to launch the OS.
Third concern: Over the past two to three months, the PC would become slow after a few hours of use. After rebooting, it would either restart normally (though this was rare) or trigger BSODs after entering my password. The error codes I’ve seen most often are PAGE_FAULT_IN_NON_PAGED_AREA.
What failed: Ntfs.sys (most frequently), MEMORY_MANAGEMENT (around 10%), KERNEL_SECURITY_CHECK_FAILURE (about 5%), UNEXPECTED_KERNEL_MODE_TRAP (rarely), IRQL_NOT_LESS_OR_EQUAL (occasionally).
I tried several fixes: updating graphics drivers, updating BIOS, scanning for malware, reseating RAM. Temperatures were normal, and Memtest86 found no issues. The last minidump file was empty, but the Blue Screen Viewer consistently logged the same BSODs.
Other problems include: inability to install certain games from specific sites (often due to missing .dll files), corruption in legitimately purchased games requiring repeated integrity checks, and issues with large .rar archives.
Software like Ubisoft Launcher, Steam, or EA Play sometimes reported corrupted files (usually .dll) and needed repair. I also faced difficulties with the Windows search function. After gaming or heavy tasks, Chrome would show errors such as “STATUS_ACCESS_VIOLATION” or “OUT OF MEMORY,” which are common with a 14th-gen Intel CPU.
Things I’ve tested: updating drivers, checking BIOS, scanning malware, cleaning RAM, and using Memtest86. My minidump folder was clean, yet the Blue Screen Viewer consistently captured the same error patterns. The latest BSODs (like 090524-12640-01.dmp) show memory management issues.
I’m unsure if a new M.2 SSD and two fresh RAM sticks would solve everything, but given the price difference, it might be worth considering. Alternatively, I’m contemplating upgrading to a Ryzen 7800X3D with DDR5, though that seems costly unless the 5000-series NVIDIA chips arrive soon. Any advice or suggestions would be greatly appreciated.
This indicates it's accessing the minidump directory: "C:\Windows\Minidumps\090524-12640-01.dmp". You need dump files stored there, not the regular Minidump folder. I'm focusing on the file attributes at the bottom. If you didn't collect the dumps manually, verify the folder in C:\Windows and copy it to your Downloads area. Compress the files and attach them as instructed.
All dump files indicate memory problems. Four occurred during data transfer from RAM to the page file, suggesting storage issues are likely. The page file acts like RAM, storing low-priority data and causing crashes that mimic storage failures. It temporarily holds data on disk until needed or when RAM demand exceeds space. On your D:\ drive, the warning points to a specific location. Typically it resides on C:, but it can span multiple drives. If unsure, run this PowerShell command: Get-CimInstance -ClassName Win32_PageFileUsage -Property * To find the exact path. A result showing "C:\pagefile.sys" means the file is on C:. If it's on D:, consider removing the drive physically since it also triggers a similar warning in CDI.
Quick clarification – I don’t assume any special knowledge, so here’s what I mean: Since the system was built in 21, have you ever reinstalled the operating system before? Windows can behave oddly at times, and as it ages, it may become sensitive or start acting strangely. A straightforward reinstall often resolves problems temporarily, but eventually the installation itself can degrade. Over time, registry issues and changes from removed programs can cause fragmentation. You might try defragmenting the registry, though success depends on how much it’s degraded. After a fresh install, consider creating a backup image of the new setup so you can restore it quickly if needed. It’s best to keep your backup on a separate, non-essential drive—ideally something you don’t use regularly—to avoid risks from malware or hidden partitions. Always store copies in a safe place like a drawer, and feel free to ask more questions if you need further guidance.
While testing powershell I noticed the file "MScoree.dll" is missing, preventing me from proceeding with your suggestions. A quick online search indicates the issue might be related to the SSD or Windows setup. Since the software was released in 2021, I haven’t performed any OS updates or reinstalls (I’m using a Jolly Roger version). Your advice about checking backup files is helpful—I’ll review the dumps and consider whether the problem lies with the storage device or the operating system installation. Your plan to upgrade with a new M.2 SSD and RAM sounds reasonable, especially at around 110€ for a quality product. I appreciate your guidance and will look into setting up a fresh Windows installation once I can afford it.
You suspect the operating system has become outdated and may require a reinstall. If the issue persists after reinstallation, it could indicate hardware concerns. Unless minor glitches resolve themselves, consider testing with a fresh drive first to confirm stability. If successful, move necessary files from the old drive to the new one, complete the setup as desired, and then create a backup of the OS as recommended.
I haven't encountered this before—it could indicate a Windows issue. This document offers instructions for adjusting the page file location I already have for other problems, though you might adapt those steps to check the drive it uses. You don't need to actually modify it; just try switching drives to test, but if it's an SSD, avoid connecting it to an HDD unless you're certain it's fine. When memory errors appear, they're usually hardware-related rather than installation problems.
The indicated issues clearly suggest RAM as the main concern, though a corrupted OS remains a potential factor. The "IRQL_NOT_LESS_OR_EQUAL" error is strongly linked to RAM problems, typically resolved by adjusting the voltage slightly. However, the user also mentioned the CPU might be failing, which can lead to similar RAM-related issues. Given the other errors present, it might be worth attempting a simple fix that requires minimal cost and effort.
Very few BSOD errors give a clear clue about the cause. This specific issue isn’t among the strong signs that point to a particular problem. If your RAM is faulty, you might see almost any BSOD type since data loss can happen randomly. There isn’t really a direct link between BSOD and RAM damage. The nearest possibility would be Memory_Management, though even that can stem from other factors. You’ll need to use a debugger to see what’s happening. In some cases, crashes occurred because copied data from RAM to the page file didn’t match its original state—this isn’t typical with OS corruption, but BSOD crashes often cause similar issues. Therefore, BSODs are less likely to result from corruption and more likely from other underlying problems.