Question PAGE_FAULT_IN_NONPAGED_AREA ?

[TDUBS]

Hello all,

I recently experienced a PAGE_FAULT_IN_NONPAGED_AREA What failed: win32kbase.sys BSOD. Upon reading up on the error, it has indicated it could be due to faulty RAM. Around the 2nd week of August, I bought 2 sticks of RAM secondhand to go from 16GB to 32GB. I matched the specs/model to ensure they matched my current sticks. All has been well but now I got that BSOD and wonder if the guy sold me faulty RAM. Here's some information below:

Task Manager Info:
https://scrncp.com/i/nt1t0ea.png

MemTest Errors:

https://scrncp.com/i/qu81ztv.png

WhoCrashed:

https://scrncp.com/i/pqobr7e.png

Minidump:
https://uploadir.com/76262/2iZISfqfW3

Any ideas?

Thanks!

 

[turtletarget111]

If you have faulty RAM you will typically see messages like DATA_BUS_ERROR and MEMORY_MANAGEMENT. PAGE_FAULT_IN_NONPAGED_AREA typically indicates a driver error. Try updating and reinstalling drivers. Also ensure you do not have any hardware that is aggressively overclocked. A video card, CPU, or RAM that is overclocked or receiving the wrong amount of voltage can result in a blue screen.

Because Memtest86 came back positive on your end, you were likely sold a faulty stick of memory. You can also run CHKDSK, SFC, and DISM. If CHKDSK is positive, back up any important data to an external drive or USB stick, and run a disk utility to ensure the drive is still safe to use. You can typically find a downloadable disk tool on the manufacture's website of your drive.

From the What failed, it looks like a file within System32 is giving you trouble. System32 contains data for the OS, like DLL's, error checking, encryption services, and the Windows kernel itself. Windows will load many of these files into memory when it is booting into the OS. This means if and when your PC tried to access a piece of data within memory, it likely caused the blue screen because your memory is not copying data properly. You can always install the old sticks to see if this resolves your issue.

You could also completely reinstall Windows as a last resort, but again, make sure you have important files, photos, and documents backed up to another drive. Hope this helped, take care.

 

[ubuysa]

Bad RAM can cause all sorts of BSOD bugchecks and often just crashes to the desktop. In addition, it's never wise to make a diagnosis based on only one dump. However, the one dump you uploaded was likely caused by Avast!. There is an Avast driver in the call stack (aswVmm.sys), just before the page fault that triggered the BSOD...

ffffc486`2c105848  fffff804`4fa2de41 nt!KiPageFault+0x341
ffffc486`2c105850  00000000`00989680
ffffc486`2c105858  fffff804`4f81d7f0 nt!EtwpReserveTraceBuffer+0x1a0
ffffc486`2c105860  000000af`8c9fdfbc
ffffc486`2c105868  00000000`00000018

.....

ffffc486`2c105938  00000000`00000000
ffffc486`2c105940  aaaaaaaa`aaaaaaaa
ffffc486`2c105948  fffff804`544ce176 aswVmm+0xe176
ffffc486`2c105950  ffffa40f`5866a210
ffffc486`2c105958  00000000`00000000
ffffc486`2c105960  00000000`00000000
ffffc486`2c105968  00004ad8`00027540
ffffc486`2c105970  ffffa40f`5866a210
ffffc486`2c105978  fffff804`4f820986 nt!ExReleaseResourceLite+0x146

All third-party anti-malware tools cause BSODs on some systems now and again, but in my experience Avast! is the worst offender. The version of aswVmm.sys that you have installed is fairly recent (18th July 2023) but you might want to look for an updated to Avast!. Personally I would uninstall it, you really don't need it. Windows Firewall and Windows Defender are all you need , they are all I use.

 

[TDUBS]

Bad RAM can cause all sorts of BSOD bugchecks and often just crashes to the desktop. In addition, it's never wise to make a diagnosis based on only one dump. However, the one dump you uploaded was likely caused by Avast!. There is an Avast driver in the call stack (aswVmm.sys), just before the page fault that triggered the BSOD...

ffffc486`2c105848  fffff804`4fa2de41 nt!KiPageFault+0x341
ffffc486`2c105850  00000000`00989680
ffffc486`2c105858  fffff804`4f81d7f0 nt!EtwpReserveTraceBuffer+0x1a0
ffffc486`2c105860  000000af`8c9fdfbc
ffffc486`2c105868  00000000`00000018

.....

ffffc486`2c105938  00000000`00000000
ffffc486`2c105940  aaaaaaaa`aaaaaaaa
ffffc486`2c105948  fffff804`544ce176 aswVmm+0xe176
ffffc486`2c105950  ffffa40f`5866a210
ffffc486`2c105958  00000000`00000000
ffffc486`2c105960  00000000`00000000
ffffc486`2c105968  00004ad8`00027540
ffffc486`2c105970  ffffa40f`5866a210
ffffc486`2c105978  fffff804`4f820986 nt!ExReleaseResourceLite+0x146

All third-party anti-malware tools cause BSODs on some systems now and again, but in my experience Avast! is the worst offender. The version of aswVmm.sys that you have installed is fairly recent (18th July 2023) but you might want to look for an updated to Avast!. Personally I would uninstall it, you really don't need it. Windows Firewall and Windows Defender are all you need , they are all I use.

I agree with Avast! being the worst offender. I've just used it for so long but thinking about it right now, it's very intrusive. I uninstalled it just now. I also realized I used A.I. Tweaker in my BIOS to modify the speeds using D.O.C.P. settings, timing, and voltage because they were being read at slower speeds out of the box so I just put everything back to default except the speeds and voltage. I ran MemTest the same way as these screenshots and haven't gotten any errors. I think I overdid whatever using A.I. Tweaker in my BIOS.

 

[ubuysa]

Very likely. Whenever you start getting BSODs the very first thing you should check is to return everything to stock frequencies and voltages.