Page_fault_in_non_paged_area BSOD on certain programms

Quartuccio · 24 Jun 2019

Hello guys,

so i get the BSOD when starting certain programms. (the game crawl for example). I wanted to look into it myself. Downloaded Bluescreen viewer and ntoskrnl.exe is at fault. Well i know from research that this is pretty broad so i wanted to check myself with Windbg. Well when trying to start it i got the same BSOD.
I attached the minidmp files, 1 of those was another BSOD i had while i was away, with the driver verifier, but i think i fixed that. if this doesn't seem to have the same cause as the other ones, then please just ignore it.
Here is also the link to the latest memory dump file: MEMORY.rar - Google Drive

I already ran the sysfile check, harddrive check, memory check and played with driver verifier. Also i updated every single driver, updated the BIOS. Manually checked the RAM's by only putting in one on every single slot possible. I found something about the virtual memory and tried changing that. Nothing helped.

The whole build is really new and it took me a while to set it all up again so i really want to come around a completely new install if possible.

Thanks in advance

- - - Updated - - -

Tried Rocket league to see what would happen there and had the same BSOD but way more serious as you can see in the attached picture. The percentage stayed at 0%. So I restarted and it didn't even create a dmp file. Also i had a notification on startup after the BSOD about something like "... Watts settings reset because of system failure" or something like this. I'm starting to suspect hardware, but what could it be?Attachment 238249

Ztruker · 24 Jun 2019

First, read and follow the attention box instructions at the top of the forum and top of your thread:

Attachment 238256

Second. the log files are in a non-english language and some can not be analyzed. Please change the system language to English and post a new log collector zip. Use the V2 log collector shown in the Blue Screen of Death (BSOD) Posting Instructions link as it collects more information than the standard collector.

Add, Remove, and Change Display Language in Windows 10
How To Change Language In Windows 10 Operating System - YouTube

You can put the language back to normal once done though you may have to do this multiple times if we need you to run the log collector script again in the future. Won't help with data that's already collected but newly generated data will be in English which can help.

Thanks

Quartuccio · 24 Jun 2019

I changed the language and ran the collector.
Should i make the system crash again so the dmp files get created in english or is the collector stuff enough?Attachment 238257

Ztruker · 24 Jun 2019

Collector is enough for now, thanks. If another BSOD does occur, run the collector immediately and upload the zip please.

Ztruker · 24 Jun 2019

The problem we're having right now is Microsoft has not loaded the symbols for 18362.30 or 18362.175 builds which are for the latest 1903 release, so we can't do much with dumps. Hopefully they will correct this soon but until then all we can do is look at the rest of the collected data and see if anything pops out, especially event logs.

I'll post back after I've had time to examine them.

Quartuccio · 24 Jun 2019

Thank you for your help. I tried running Windbg on the laptop of a friend but it didn't work because of errors with symbols. I thought I was just to stupid to fix that but well, seems like it wasn't my fault after all haha

cwsink · 24 Jun 2019

I'm not sure why this would be the case but if I open the minidumps from within the zip (rather than first extracting them) symbols seem to be getting correctly resolved. Weird.

062219-8843-01.dmp has Driver Verifier enabled and flagged avgntflt.sys as leaking pool memory. The more recent dumps are showing crashes happening while doing filter binding functions so I suspect it's an Avira problem. Please try completely uninstalling Avira and using only Windows Defender to see if the crashes stop in that configuration.

Quartuccio · 24 Jun 2019

So I firstly tried crashing the system again for an english dmp but BSOD stuck on 0% for like 5-6 miutes so i just restarted, so there was no dump. Then I tried deinstalling Avira and had a Driver verififier BSOD during that, also stuck on 0% so no dump. Well deactivated driver verifier, deinstalled and tried running a programm again and again the Page BSOD, but this time a minidmp and memdmp were created and they both should be in english.
Also attached the new V2 log.Attachment 238276 Attachment 238277
And the new memdmp on my gdrive: new_mem_dump_english.rar - Google Drive

Ztruker · 24 Jun 2019

cwsink said:

I'm not sure why this would be the case but if I open the minidumps from within the zip (rather than first extracting them) symbols seem to be getting correctly resolved. Weird.

062219-8843-01.dmp has Driver Verifier enabled and flagged avgntflt.sys as leaking pool memory. The more recent dumps are showing crashes happening while doing filter binding functions so I suspect it's an Avira problem. Please try completely uninstalling Avira and using only Windows Defender to see if the crashes stop in that configuration.

That is crazy. I just tried it and got the same results, symbol files resolved. Not a clue why but as long as it works I'm happy.

Many thanks.

Edit: Doesn't work from inside a RAR file, just ZIP as far as I can tell.

Ztruker · 24 Jun 2019

All the dumps show bindflt.sys as the cause. This seems to be happening quite a bit recently. A lot of these are GSODs (Green Screens) but it would be worth giving their solution a try:

Windows 10 build 18309 showing bindflt.sys failed Green Screen error
1. Open command prompt as administrator and run following commands
2. SFC/Scannow
3. DISM /Online /Cleanup-Image /RestoreHealth
4. SC Config bindflt start= demand.

Some info on it here: Windows Bind Filter Driver (bindflt) Service Defaults in Windows 10

Also, in all but one dump, GameBarFT.exe was the active process. I can't find any information on it or what it belongs to. Can you search your hard drive and find out what program it belongs to? Perhaps uninstall that for now and see if it helps.