Question BSOD - PAGE FAULT IN NONPAGED AREA (nvlddmkm.sys) HELP

[MarkedOne66]

Hello comunity.

I've been getting this error for days now. I didnt install anything for the past month almost. I searched the net and it said its the Nvidia driver so i did a complete removal of the driver and updated with the new one, and by clean i really mean CLEAN install, i used the 3D gurus Display Drivere Uninstall program to remove all Nvidia files from my PC, restarted and installed a new driver from the site (latest) ... few hours later, same sh*t again ... idk what to do... PLS help.

Ive browsed for a while now and its always osmething else, i cant just go around blindly like an idiot and uninstall everything ,might aswell just reinstall whole windows then for gods sake... just PLS NOT THAT ........ Someone tell me what i need to pull for you, post it here and help me locate the cause.

(picture bellow)
https://media.discordapp.net/attach...IMG_20190907_215038.jpg?width=1202&height=677

 

[Colif]

Where did you get the last Nvidia drivers from? COuld try running DDU again and run windows update afterwards and use the Nvidia drivers Microsoft have, they are normally more stable than the latest fdrom Nvidia

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

copy that file to documents
upload the copy from documents to a file sharing web site, and share the link in your thread so we can help fix the problem

 

[MarkedOne66]

Hi, thanks for the quick response,

1. I downloaded the driver directly from nvidia sites, more precisely i downloaded the latest Nvidia experience, let it find newest driver and installed that with the clean install option after using DDU.

2. Since i have Win pro, i think i dont have to set anything up, it creates the dumb files by default. Here are the files:
https://drive.google.com/file/d/19aUUMptAF6XzBXF4SeJw8kqipDobZiQ0/view?usp=sharing

090919-5703-01.dmp

drive.google.com

one is the minidump the other is some output from BSOD viewer. If it would be needed i can prolly upload the completre one too but thats 1,5 GB 😆

3. Yes i can do DDU again, just please look at this first if its really that. If you confirm i should do DDU again and let only windows download some basic driver, then yeah. I will.

Thanks

 

[Colif]

minidumps only 1mb max, my friend couldn't dl 1.5gb fast enough to make it useful to you.

I will forward them now, he is probably asleep still.

 

[gardenman]

Hi, I ran the dump file through the debugger and got the following information: https://pste.eu/p/2eX5.html

File information:	090919-5703-01.dmp (Sep 8 2019 - 20:58:44)
Bugcheck:	PAGE_FAULT_IN_NONPAGED_AREA (50)
Driver warnings:	WARNING: Unable to verify timestamp for nvlddmkm.sys
Probably caused by:	memory_corruption (Process: chrome.exe)
Uptime:	1 Day(s), 4 Hour(s), 07 Min(s), and 33 Sec(s)

Comment: The overclocking driver "XtuAcpiDriver.sys" was found on your system. (Intel Extreme Tuning Utility)

The nvlddmkm.sys file is a NVIDIA graphics card driver. There are a few things you can do to fix this problem. First off, try a full uninstall using DDU in Safe Mode then re-install the driver (more information). Or try getting the latest version of the driver. Or try one of the 3 most recent drivers released by NVIDIA. Drivers can be found here: http://www.nvidia.com/ or you can allow Windows Update to download the driver for you, which might be a older/better version.

BIOS info was not included in the dump file. This can sometimes mean an outdated BIOS is being used. It's not recommended to update BIOS just yet. Lets see if we can fix the GPU driver first.

This information can be used by others to help you. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.

 

[PC Tailor]

May 05 2013

ScpVBus.sys

Scarlet.Crush Productions Scp Dual Shock 3 Virtual Bus driver http://forums.pcsx2.net/

This driver is known to cause various issues, so you'll probably want to disable this with Autoruns.
Antivirus can commonly cause this error, however we can leave that till afterwards I think.

Also @gardenman pointed out Intel XTU, are you running any overclock/XMP at all? You may want to disable these and see if the issue persists.

Also pointed out your NVIDIA drivers, which have been updated I'm assuming based on the timestamp?

Your SATA and internet drivers may also need to be updated.

What is your full system spec including PSU make and model?
I'm guessing CPU is Haswell based on CPU family?

 

[Colif]

i don't know, the two people with the same sig seem to have answered this for you.

He knew it was GPU driver, just have to find a driver that works. He is on newest so maybe (as Gardenman says), you can use aan older version or just run windows update and use the drivers Microsoft have from Nvidia which always seem more stable than latest

I would only use latest if you have a new RTX card.

he also on an older version of windows but thats unlikely to be a cause, its not that old. it it was 1507 I would say otherwise.

Scarlet crush is unlikely to cause gpu drivers to BSOD. Yes, it can cause bsod and there is a version from 2015, but the newer version still doesn't help.

 

[PC Tailor]

Scarlet crush is unlikely to cause gpu drivers to BSOD. Yes, it can cause bsod and there is a version from 2015, but the newer version still doesn't help.

Yes, however the dump I saw above didn't mention NVIDIA drivers as a module that crashed. It crashed on Chrome, just the NV driver timestamp and symbols couldn't be read. Was just going off the NV drivers based on OP first post and then Scarlet etc. on the dump file

 

[Colif]

i assumed you both doing same dump file?
most of the time it can't read the timestamp is a sign its the driver at fault.

True, it can't read win32kfull.sys sometimes but I find, if it mentions a driver, its a good place to start.
I am just going from experience. I am not always right

 

[MarkedOne66]

OK let me add some additional input first:

Im using:

HyperX Savage 16GB (Kit 2x8GB) 1600MHz DDR3 CL9
Intel Core i7- 4790K, Quad Core, 4.00GHz
MSI GeForce GTX 1070 Z
MSI Z97 GAMING 5, Z97
Super Flower Leadex 80Plus Gold - 750W
Samsung SSD SSD850 EVO 250GB SATAIII
Seagate Barracuda 7200 2TB 3.5'' HDD
ZXT H440 Midi- Tower - matt black/red
BenQ LCD RL2455HM 24", 1ms
Acer PREDATOR 27" 165Hz 2K

1. Next, to ask about some stuff people mentioned here. Im not sure what the " The overclocking driver "XtuAcpiDriver.sys" " is and what it does at all... i mean i have a K series CPU so that does OC itself if thats what it is, otherwise i did not OC anything. So if this can be turned off without loosing any computing power, tell me how please.

2, neither of the 2 files i shared here are 1,5gb i just mentioned the full dump is 1,5GB and i didnt upload that. Only the minidump and BSODviewer uotput.

3, i see there someone posted: " memory_corruption (Process: chrome.exe) " is that not relevant ?

4, im using Windows 10 Pro, 1803 build right now and all updates installed.

5, I see some different opinions so im unsure what to do first. Where should i start please?

Thankyou for your involvement in this <3

 

[Colif]

1. Its part of INtel Extreme Tuning Utility. Its listed on your motherboards website (under utilities tab) - https://www.msi.com/Motherboard/support/Z97-GAMING-5#down-driver&Win10 64

3. Memory corruption is seen in many BSOD, it doesn't necessarily signify a ram problem.

I would follow gardenman's advice for now and see if a different driver fixes it.

 

[PC Tailor]

5, I see some different opinions so im unsure what to do first. Where should i start please?

Apologies, it may have been me confusing things slightly.

In effect your initial post talks around your NVIDIA drivers, I just identified some other potential causes from the dump file that gardenman run. That's all, but completely agree to follow on with gardenmans and Colif's advice, just the elements I mentioned may be next ports of call should the first steps not work.

As Colif said, the memory corruption can happen for a variety of reasons, we just want to eradicate software first. It's also common for memory corruption to be present on blue screens when internet/chrome is in use. If the software/drivers route fails, then you may want to run some memory tests, but typically many BSOD are driver based.

 

[MarkedOne66]

I looked into that Intel XTU but i cannot find a service, program or anything related to it on my PC. Where did u come across the reference that i have it? I wanted to try to disable it but i cannot even locate it.

 

[gardenman]

If the BSODs have stopped, leave the XTU driver alone. If not, you can download [AutoRuns] and disable the driver. Be careful what you disable in that program. It's easy to disable too much and find your Windows no longer booting.

XTU is a common Intel overclocking driver/software. Overclocks (and even just overclocking drivers) can cause BSODs. I would leave it alone until you've tried the suggestions with the other drivers mentioned above.

 

[MarkedOne66]

Hello,
Sorry for not responding for some time now. I was very busy IRL. Also, few days ago i uppdated to new nvidia driver that came out 436.30 Released on 10.sept 2019, and for now, no BSOD yet, problem is i have no idea what was causing it since we couldnt really pinpoint a process or application that was doing it, i cannot try to recreate the situation :/ ...

If its possible i would like to leave this thread open for as long as possible and ill update it if BSOD doesnt occur in next 1-3 months. Otherwise it can be closed i guess. Dont rly wanna do anything right now since it seems to be ok for now.

Thanks for the help until then.

 

[Colif]

its your thread, it stays open for as long as you need it. It may get auto closed in 6 months. Hopefully we know by then

 

[MarkedOne66]

Hey, so unforttunately, i couldnt really test nor try your suggestions. My motherboard died like 2 days after my last response. I guess you can clsoe the thread. The solutions proposed here might help someone tho. I had to buy a new motherboard and install a new windows. So im not expecting anything to be broken anytime soon 😀 hopefully. Thanks for all the great advice tho.