Solved BSOD page_fault_in_nonpaged_area ntoskrnl.exe windows 11

Picis · Nov 30, 2023

Hello everyone, good morning!
I'm a new user, and I'm here because I need urgent help.
I have an ASUS Rog Zephyrus M16 with the following specifications:

Processor: 13th Gen Intel(R) Core(TM) i9-13900H 2.60 GHz
Installed RAM: 16.0 GB (15.6 GB usable)
System type: 64-bit operating system, x64-based processor

Video Card: Nvidia Geforce RTX 4070 GPU
I'm experiencing daily BSODs, at least twice a day. I've already reset the computer to factory settings, ran diagnostics, and couldn't figure out the cause. I couldn't identify a pattern of error causes, so I find it very strange. The computer is new, it hasn't even been used for 3 months, and I also don't think it's a hardware problem.
I downloaded BlueScreenView and found that the error comes from the file: ntoskrnl.exe, caused by the address: ntoskrnl.exe+416980
Details:

113023-13718-01.dmp
30/11/2023 10:42:55 PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 fffff2f8`7df810f0 00000000`00000002 fffff802`4806187a 00000000`00000002 ntoskrnl.exe ntoskrnl.exe+416980 x64 ntoskrnl.exe+416980 C:\WINDOWS\Minidump\113023-13718-01.dmp 20 15 22621 6.107.804 30/11/2023 10:43:23

I'm attaching a .zip file with the minidump file from today, and the V2Log file aswell (The PICISPC file)

Please help, I don't know what else to do!

zbook · Dec 1, 2023

New laptops should not have BSOD.

Please contact Asus for Return Merchandise Authorization (RMA).

How come the opening post did not report the use of Windows Driver Verifier?

While waiting for a RMA:

Run: Tuneup plus:

https://www.tenforums.com/attachments/bsod-crashes-debugging/360139d1645183596-batch-files-use-bsod-debugging-tuneup_plus_log.zip

Post a share link.

Both video drivers can be clean installed using DDU.

Display Driver Uninstaller: How to use

How to Use Display Driver Uninstaller to Uninstall any Installed Display Driver

www.sevenforums.com

Display Driver Uninstaller (DDU) download latest version 18.0.7.6

Official Display Driver Uninstaller (DDU) download website. DDU is a driver removal utility that can help you completely uninstall AMD/NVIDIA/INTEL graphics card drivers and packages from your system, trying to remove all leftovers (including registry keys, folders and files, driver store).

www.wagnardsoft.com

PCI Express Root Port PCI\VEN_8086&DEV_A76E&SUBSYS_14731043&REV_00\3&11583659&0&38 51

Code:

Full Error Message

This device is currently waiting on another device or set of devices to start. (Code 51).

Microsoft Recommended Resolution:

There is currently no resolution to this problem.
To help diagnose the problem, examine other failed devices in the device tree that this device might depend on.
If you can determine why another related device did not start, you might be able to resolve this issue.

Name Intel(R) UHD Graphics
PNP Device ID PCI\VEN_8086&DEV_A720&SUBSYS_14731043&REV_04\3&11583659&0&10
Adapter Type Intel(R) UHD Graphics Family, Intel Corporation compatible
Adapter Description Intel(R) UHD Graphics
Adapter RAM 1,00 GB (1.073.741.824 bytes)
Installed Drivers <>,C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_ffe7d9986336312b\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_ffe7d9986336312b\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_ffe7d9986336312b\igd12umd64.dll
Driver Version 31.0.101.4502
INF File oem68.inf (iRPLPD_w10_DS section)
Driver C:\WINDOWS\SYSTEM32\DRIVERSTORE\FILEREPOSITORY\IIGD_DCH.INF_AMD64_FFE7D9986336312B\IGDKMDN64.SYS (31.0.101.4502, 48,26 MB (50.603.488 bytes), 10/08/2023 10:26)

Name NVIDIA GeForce RTX 4070 Laptop GPU
PNP Device ID PCI\VEN_10DE&DEV_2860&SUBSYS_14731043&REV_A1\4&17526E30&0&0008
Adapter Type NVIDIA GeForce RTX 4070 Laptop GPU, NVIDIA compatible
Adapter Description NVIDIA GeForce RTX 4070 Laptop GPU
Adapter RAM (1.048.576) bytes
Installed Drivers C:\WINDOWS\System32\DriverStore\FileRepository\nvamsi.inf_amd64_87b54c271c2f9160\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nvamsi.inf_amd64_87b54c271c2f9160\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nvamsi.inf_amd64_87b54c271c2f9160\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nvamsi.inf_amd64_87b54c271c2f9160\nvldumdx.dll
Driver Version 31.0.15.4601
INF File oem241.inf (Section230 section)
Driver C:\WINDOWS\SYSTEM32\DRIVERSTORE\FILEREPOSITORY\NVAMSI.INF_AMD64_87B54C271C2F9160\NVLDDMKM.SYS (31.0.15.4601, 56,00 MB (58.720.904 bytes), 10/11/2023 13:39)

Picis · Dec 1, 2023

Hi there, Zbook!

First and foremost, I appreciate your response.

zbook said:
Please contact Asus for Return Merchandise Authorization (RMA).

I comprehend the situation. The challenge is that I'm currently not in the USA, and I suspect my warranty only applies there. However, I will investigate further to confirm and initiate the RMA process as soon as possible. The silver lining is that I'll be in the USA in December, so I could potentially exchange the equipment during that time aswell...

zbook said:
zbook said:

How come the opening post did not report the use of Windows Driver Verifier?

Click to expand...

Secondly, I apologize for not sharing the Windows Driver Verifier logs initially, and I forgot to mention that I used it and identified the issue with the driver csaudio.sys , but I didn't find any solutions...

The challenge now is that I can't recall the exact steps I took. Could you please guide me through the correct steps to run the Driver Verifier again? Thank you!

zbook said:
Post a share link.

Tune Up ZIP

zbook said:
Both video drivers can be clean installed using DDU.

Are you suggesting that I uninstall the graphics drivers for both the integrated and dedicated GPU, and then reinstall them using the software you mentioned? I apologize if it wasn't clear to me.

Thank you one more time for your help!

zbook · Dec 1, 2023

Please uninstall and reinstall both GPU drivers: Nvidia and Intel

These are links for Windows Driver Verifier (WDV):

Enable and Disable Driver Verifier in Windows 10

How to Enable and Disable Driver Verifier in Windows 10

www.tenforums.com

Create System Restore Point in Windows 11 Tutorial

This tutorial will show you how to manually create a restore point in Windows 11. Turning on system protection for a drive allows System Restore to include the drive when restore points are created so you can undo undesired system changes by reverting to a previous point in time. System...

www.elevenforum.com

ubuysa · Dec 2, 2023

Picis said:
Secondly, I apologize for not sharing the Windows Driver Verifier logs initially, and I forgot to mention that I used it and identified the issue with the driver csaudio.sys , but I didn't find any solutions...

That is a MASSIVE clue, it's what Driver Verifier is for. The csaudio.sys driver is a third-party driver belonging to the CSAudio Converter product (I think). If Driver Verifier caused a BSOD and flagged csaudio.sys then that driver is misbehaving. If we had the dump we could tell you much more.

I would suggest you now fully uninstall the CSAudio product and reboot. Then see whether the problem persists - with Driver Verifier enabled.

Picis · Dec 2, 2023

Hello again guys!

zbook said:
Please uninstall and reinstall both GPU drivers: Nvidia and Intel

Thank you! I did this almost 24 hours ago, and the error has not recurred. I uninstalled both drivers using DDU and reinstalled them in safe mode. I will monitor to see if the error repeats.

ubuysa said:
I would suggest you now fully uninstall the CSAudio product and reboot. Then see whether the problem persists - with Driver Verifier enabled.

I will do that either.

Apparently, I had a BSOD with two drivers, csaudio.sys and also the graphics drivers. I followed the steps you suggested, and now I am monitoring to see if it will happen again.

Thank you very much for your time and attention so far.

zbook · Dec 2, 2023

Please run WDV to see if there are any other misbehaving drivers.

The tool has various testing options.

Plan to run WDV for 48 hrs.

Start with these settings:
a) test all non-Microsoft drivers
b) test no Microsoft drivers
c) start the testing with the 3 tests in the TF tutorial

If there is no immediate BSOD then open administrative command prompt and copy and paste:

verifier /querysettings

Post a share link into the newest post using one drive, drop box, or google drive.

For any BSOD post a new V2 share link.

x BlueRobot · Dec 5, 2023

If you're going to run Driver Verifier again, then use the tutorial written specifically for Windows 11: BSOD - Driver Verifier Instructions

The tutorial on TenForums isn't adequate: one of the options specified isn't even a test, it just saves additional logging information to the dump file which usually requires a MEMORY.DMP file in order to read from WinDbg.

zbook said:
Start with these settings:
a) test all non-Microsoft drivers
b) test no Microsoft drivers

You might want to update your canned speech because a) and b) both refer to the same thing.

Picis · Dec 6, 2023

Guys i did everything you asked me too. The BSOD stopped!

Thank you very much for your help! I believe it was the graphic drivers

If something happens again i will come here again

x BlueRobot said:
If you're going to run Driver Verifier again, then use the tutorial written specifically for Windows 11: BSOD - Driver Verifier Instructions

I will do this just to ensure that I don't have anything else bugging

I will post here after that!

Thanks again

zbook · Dec 6, 2023

That's great news.

You're welcome.

There are multiple methods for using the WDV tool.

There are multiple tutorials.

There are pro and con for each including Microsoft tutorials.

The Ten Forums tutorial in post #4 is one of the safest methods for using WDV.

Once you've seen how the tool performs in the computer environment with the 3 customized tests you can modify the customized tests.

It is not necessary to use the tool as you've reported computer stability.

The tool can be used proactively.

Using the 3 customized simultaneous tests will stress the system substantially less than running 9 or more simultaneous tests.

If 3 run smoothly (no major performance problems or very slow boot) you can either switch to other customized tests or add additional customized tests.

If you use the tool please follow the Ten Forums tutorial and the steps in post #7.

ubuysa · Dec 7, 2023

@Picis, I imagine you're confused having two contributors tell you to run Driver Verifier in different ways. I know @x BlueRobot, he is one of the senior BSOD dump analysis instructors on the Sysnative BSOD Academy, which is where I met him. He is a renowned expert (and I do mean expert) in Windows Internals and especially BSOD analysis. He has been invaluable in helping me improve my dump reading and BSOD analysis skills and I have the utmost respect for his knowledge and skills.

The difference between the two sets of instcrutions is that @x BlueRobot asks that the following Microsoft drivers be selected, in addition to all third-party drivers. These additional drivers are high-level Microsoft drivers that manage lower-level third party drivers that we wouldn't otherwise be able to test...

Wdf01000.sys is the manager driver for the Windows Driver Foundation (WDF), many third-party drivers are written using WDF libraries and this is the only way of getting them included in the DV checks.
ndis.sys is the high-level networking driver and including this ensures that all third-party networking drivers are inbcluded in the DV checks.
fltMgr.sys is the filter manager driver. Many drivers act as filter drivers, modifying the action of an existing driver, so by including this high-level driver we ensure that DV checks all these third-party drivers.
Storport.sys is the high level external drive storage drive, by selecting this we ensure that any third-party styroage drivers (NVMe drivers for example) are included in DV checks.

I too would encourage you to use the Driver Verifier instructions in this forum, which you can clearly see have been written by someone who clearly knows what they're talking about.

zbook · Dec 7, 2023

The methods for running the WDV tool are varied.

The Ten Forums tutorial in post #4 is one of the safest methods for using WDV.

Enable and Disable Driver Verifier in Windows 10

How to Enable and Disable Driver Verifier in Windows 10

www.tenforums.com

x BlueRobot · Dec 8, 2023

zbook said:
The methods for running the WDV tool are varied.

That may be true but those instructions you've provided aren't suitable for "general" use. The Windows 10 tutorial essentially enables one option which is I/O Verification, this option should not even be enabled for multiple drivers as stated in the documentation:

When Level 1 I/O Verification is enabled, all IRPs obtained through IoAllocateIrp are allocated from a special pool and their use is tracked.

[...]

Because the special IRP pool is of limited size, I/O Verification is most effective when it is only used on one driver at a time.

Source: I/O Verification - Windows drivers

The other two options rely on I/O Verification being enabled, however, IRP Logging simply creates an additional log within the dump file which is only really useful for Stop 0x44 bugchecks. The other option which is "Force Pending I/O Requests" shouldn't even be enabled unless you have the source code associated to the driver you're testing:

Caution Do not use this option on a driver unless you have detailed knowledge of the operation of the driver and have verified that the driver is designed to handle STATUS_PENDING return values from all of its calls to IoCallDriver. Running this option on a driver that is not designed to handle STATUS_PENDING from all calls can result in crashes, memory corruptions, and unusual system behavior that can be difficult to debug or correct.

Source: Force Pending I/O Requests - Windows drivers

So no, the Windows 10 tutorial is just plain wrong and isn't at all the "safest" method for using Driver Verifier. I think you need to start reading the MSDN documentation before making out a tutorial is wrong or unsafe to use. You've done this multiple times across many threads on this forum, yet you can never justify or even attempt to justify why a set of instructions are incorrect.

zbook · Dec 8, 2023

WDV is a tool.

It has many settings.

Most users of the tool have their preferred testing method.

Again the TF tutorial has some of the safest methods for using the tool.

ubuysa · Dec 8, 2023

I think the two responses above tell you all you need to know. One has a detailed explanation of why specific settings should or should not be used, and the reasons why. The other reply simply insists that their method is better without offering any evidence. I know which reply I would trust.

x BlueRobot · Dec 8, 2023

zbook said:
Again the TF tutorial has some of the safest methods for using the tool.

Please read my post again; I've just explained why that tutorial is incorrect and shouldn't be used. I don't understand why you consistently argue against using the Windows 11 version, when two people have just explained the benefits of it?

zbook · Dec 8, 2023

Safer is different from better or worse.

This is incorrect:
I/O Verification, this option should not even be enabled for multiple drivers as stated in the documentation

x BlueRobot · Dec 8, 2023

zbook said:
This is incorrect:
I/O Verification, this option should not even be enabled for multiple drivers as stated in the documentation

So, Microsoft - the developer of Driver Verifier - is incorrect? Have you read the documentation I quoted?

zbook · Dec 8, 2023

Read the link that was posted.

The comments that you made are incorrect.

x BlueRobot · Dec 8, 2023

zbook said:
Read the link that was posted.

Which link? The one you posted or the one I posted?

zbook said:
The comments that you made are incorrect.

How are they incorrect? Please explain, in detail, how they are wrong? I want you to go through every point in the Windows 11 Driver Verifier tutorial and explain how each option should not be used. How is the Windows 10 version "safer"?

One of the options you suggested leads to unexpected crashes which can be difficult to debug! It was only a few weeks ago, you were telling everyone to use low resources simulation, despite me telling you not to enable it so many times, so have you now understood why that was the case? I'm sorry but you should not be recommending a tool which you do not understand at all. Your dump file analysis doesn't even go beyond !analyze -v and !thread + dps.