Question PAGE ERROR OCCURRED IN UNPAID SECTION?
Question PAGE ERROR OCCURRED IN UNPAID SECTION?
Hello everyone,
I recently encountered a PAGE_FAULT_IN_NONPAGED_AREA error, specifically a BSOD from win32kbase.sys. After researching, it seems the issue might be related to faulty RAM. Around the second week of August, I purchased two second-hand RAM sticks to upgrade from 16GB to 32GB. I double-checked the specifications and models to make sure they matched my existing units. Everything was fine until now I faced this error, wondering if the RAM I bought was defective. Here are some details:
Task Manager Info: [link]
MemTest Errors: [link]
WhoCrashed: [link]
Minidump: [link]
Any suggestions or advice?
Thanks!
If your RAM is faulty, you may notice errors such as DATA_BUS_ERROR and MEMORY_MANAGEMENT. PAGE_FAULT_IN_NONPAGED_AREA usually points to a driver issue. Consider updating and reinstalling the drivers. Also, avoid using hardware that is being overclocked aggressively. A video card, CPU, or RAM that is overclocked or receiving incorrect voltage can lead to a blue screen.
Since Memtest86 detected issues on your system, it suggests a faulty memory module was installed. You might also want to run CHKDSK, SFC, and DISM commands. If CHKDSK reports no problems, back up any critical data to an external storage device or USB drive. Use a disk utility to verify the drive's integrity, which you can usually download from the manufacturer’s website.
From the error details, it seems a file in System32 is causing problems. System32 holds essential OS components like DLLs, error checking, encryption services, and the Windows kernel. When booting, Windows loads many of these files into memory, which can trigger a blue screen if data isn’t copied correctly. You can try reinstalling the old memory modules to see if it resolves the issue.
If all else fails, you could perform a complete Windows reinstall as a final option, but ensure you have important files, photos, and documents safely backed up elsewhere. Hope this assists, stay safe.
Bad RAM often leads to various BSOD error checks and frequently results in crashes to the desktop. It's not advisable to rely on a single dump for diagnosis. Nevertheless, the dump you provided seems to be linked to Avast! The presence of an Avast driver in the call stack (aswVmm.sys) right before the page fault that caused the BSOD is notable...
I agree with Avast! being the worst offender. I've been using it for a long time, but now I'm realizing it's quite intrusive. I just uninstalled it right away. I also noticed I had used A.I. Tweaker in my BIOS to adjust speeds, timing, and voltage based on D.O.C.P. settings because they were being read slowly by default. I restored everything to the default except for the speeds and voltage. I ran MemTest in the same way as the screenshots, and I haven't encountered any errors. I think I overdid it with A.I. Tweaker in my BIOS.
Almost certainly. When BSODs begin, the initial step is to reset everything back to standard frequencies and voltages.