Error code BSOD indicates a page fault in unallocated memory.
Error code BSOD indicates a page fault in unallocated memory.
Hi acoustics, a frequent cause of the PAGE_FAULT_IN_NONPAGED_AREABluescreen issue is a virus scanner that misinterprets memory regions, resulting in a BSOD. To address this, consider pausing your antivirus temporarily. This error often appears with third-party antivirus programs. You might try enabling only Windows Defender Antivirus and see if it resolves the problem. Another method involves activating Windows resource protection. Launch a command prompt with admin privileges and execute the command sfc /scannow. This tool scans all system and resource files for errors, replacing corrupted files with intact ones. After completing the repair, restart your computer thoroughly and verify whether the BlueScreen error persists. I hope this resolves your issue and prevents future occurrences.
1) I will! Can you tell me where to find them? Is it memorydmp.dmp? 2) I ran the test, here's the log file: Spoiler ========= TestMem5 Log File ========= Customize: Default @1usmus_v3 Start testing at 15:39, 880Mb x20 ========= TestMem5 Log File ========= Customize: Default @1usmus_v3 Start testing at 15:39, 880Mb x20 Error in test #6 through 6 sec. Error in test #6 through 7 sec. Error in test #2 through 17 sec. Error in test #0 through 2m 50s. Error in test #0 through 4m 53s. Error in test #12 through 4m 55s. Error in test #2 through 5m 14s. Error in test #2 through 5m 29s. Error in test #10 through 5m 42s. Error in test #0 through 5m 50s. Error in test #0 through 5m 57s. Error in test #10 through 5m 57s. Error in test #1 through 6m 20s. Error in test #0 through 6m 21s. Error in test #4 through 6m 28s. Error in test #13 through 6m 45s. Error in test #0 through 6m 53s. Error in test #0 through 6m 59s. Error in test #0 through 6m 59s. Error in test #1 through 7m 44s. Error in test #1 through 7m 44s. Error in test #11 through 7m 46s. Error in test #11 through 7m 46s. Error in test #11 through 7m 48s. Error in test #11 through 7m 49s. Error in test #0 through 7m 49s. Error in test #6 through 7m 55s. Error in test #6 through 7m 57s. Error in test #12 through 8m 25s. Error in test #0 through 8m 25s. Error in test #2 through 8m 34s. Error in test #0 through 8m 42s. Error in test #2 through 8m 42s. Error in test #0 through 8m 42s. Error in test #2 through 8m 48s. Error in test #2 through 8m 49s. Error in test #0 through 8m 55s. Error in test #10 through 8m 56s. Error in test #10 through 9m 13s. Error in test #0 through 9m 16s. Error in test #10 through 9m 20s. Error in test #0 through 9m 40s. Error in test #0 through 9m 40s. Error in test #1 through 9m 46s. Error in test #1 through 9m 48s. Error in test #0 through 9m 48s. Error in test #13 through 10m 17s. Error in test #13 through 10m 21s. Error in test #0 through 10m 23s. Error in test #7 through 10m 28s. Error in test #7 through 10m 29s. Error in test #11 through 10m 41s. Error in test #0 through 10m 42s. Error in test #0 through 10m 43s. Error in test #11 through 10m 43s. Error in test #11 through 10m 43s. Testing is completed through 10m 46s, detected 1048 error(s). I don't have any antivirus active except for Windows defender. I also tested sfc/scannow already, forgot to mention it sorry.
Hi acoustics The only ideas that come to mind are checking for hardware problems: memory testing errors might stem from faulty RAM. To investigate, test each RAM module individually. Look into software issues too—wrong settings or conflicting programs can trigger these errors. Try running the test again with new configurations or close background apps. Consider other influences like temperature, power stability, or surroundings. If the problem persists, a tech specialist could diagnose further and offer tailored solutions. Your report from testmem5 suggests possible timeouts, insufficient voltage, or crashes during data transfer—those are likely contributing factors. I’m here to help resolve this as soon as possible.
Hi! Great to hear you're working with new Patriot DDR5 modules. Changing the XMP profile could definitely impact performance. I'll reseat them tomorrow as planned. Regarding your questions: Memtest's high error rate is likely due to its testing method, not random luck—it’s a way to verify stability under stress.
It might work to adjust the XMP profile on your Patriot DDR5 RAM to address the BSOD issues while playing Far Cry 6 and Call of Duty MW2. Modifying the XMP settings could enhance performance and stability, though you should handle it with care. Overclocking RAM can lead to problems if not done correctly, so proceed cautiously. The errors detected by Memtest may be resolved by built-in error-correction features, which is why other programs run smoothly. Be mindful when reinstalling the RAM—this requires removing modules from the motherboard, cleaning contacts, and reinserting them properly. If the problem persists, testing each module individually with Memtest can help identify a faulty unit for replacement.
I have three XMP profiles built into my RAM. Currently I'm using the top profile at 6000MHz and CL36, which is the rated speed. The others are slower. I might consider testing the other settings by lowering the clock speeds, but if they can't reach their rated performance, I'd prefer to replace them. I also question whether that's realistic since I'm not familiar with Patriot chips, though I suspect they're SK Hynix DRAM.
It's likely the issue stems from your RAM not operating at its intended speed. Running it below that level might fix instability and game-related problems. Testing alternative XMP profiles at a reduced speed could resolve the matter. If the problem continues even at lower speeds, there could be a fault with your RAM modules or a mismatch between your RAM and motherboard. In such cases, reaching out to the RAM manufacturer or motherboard maker for guidance is advisable. They can provide further troubleshooting advice or confirm if your hardware needs replacement.