[SOLVED] Windows 10 BugCheck error - Page fault in nonpaged area

[nikicam]

Dear community. Before I buy a new memory kit I would like to hear your opinion on issues that I have with my new PC build.

The new PC build specs:
Asus Prime Z490-P MBO
Intel Core i5-10600 CPU - On Asus QVL list
Corsair VENGEANCE LPX 16 GB kit(2x8GB) DDR4 DRAM 3600MHz PC4-28800 CL18, 1.2V / 1.35V, CMK16GX4M2D3600C18 - NOT on Asus QVL list
Samsung 970EVO NVMe M.2 SSD 500GB - System Drive
SSD Crucial P1 500GB 3D NAND NVMe PCIe M.2 SSD
Corsair 650W PSU - RM650 Fully modular
MSI Armor RX570 graphic card

Since I have bought this new PC configuration back in July I had at least 10-15 BUGCHECK errors where Windows froze and have restarted after a couple of seconds. As you can see this is happening randomly and can't find the cause of it, although I suspect at BIOS, Chipset drivers, or memory. Please check the attached picture from BlueScreenview.

I have flashed BIOS 3 times since I've bought the board and still receive the same bug checks. The problem can happen two times in a couple of days, or even after 26 days as you can see from the attached pictures. Please have in mind that my system is online at least 12 hours per day and I'm using the sleep feature instead of shutting down the machine.

A couple of days ago I was working on my external Toshiba USB drive and after about 30 minutes of work, the computer froze and have restarted after 30-40 seconds.
After this crash, a dump was not saved and I could only check for the system log that said:WHEA-Logger: A fatal hardware error has occurred. (Please check the attached picture). I'm not sure if that's the cause of the crash since this log was created after the PC booted up again and the external disk was still plugged in. Also, I couldn't find any detailed information about this event.

I am also using the XMP profile set in BIOS for the memory specified above.

I am using the latest available chipset drivers and BIOS from the Asus website.

I have also contacted ASUS and Corsair support where Asus pointed me to use the memory kit from the QVL list in order to get help while Corsair support said I should test both memory sticks individually with Memtest.

After the first bug check, I have tested both sticks with 4 passes (default-test) with the XMP profile set in BIOS. Everything went without a single error. After a couple of days, I have run the same test with four passes and again without any errors.

Just to mention I am working in the IT industry I am always using Asus MBO, Corsair memory, Corsair PSU, and Intel CPU's for my PC configurations and I firmly stick to this combo.

I have reinstalled Windows 10 twice v2004 and now have upgraded to v20H2, still the same error.

Is it possible to run 2x 4 Memtest passes without errors and still have the faulty RAM?

I would kindly ask you for help and advice and if you need any more information please let me know and I will update this post.

Thanks in advance!


Minidump logs on Windows 10 20H2:

==================================================
Dump File : 120420-5531-01.dmp
Crash Time : 04-Dec-20 12:29:50
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : ffff9e00969f1ad6 Parameter 2 : 0000000000000002
Parameter 3 : fffff8036d0dd83b Parameter 4 : 0000000000000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+3f5210
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.19041.662 (WinBuild.160101.0800)
Processor : x64
Crash Address : ntoskrnl.exe+3f5210
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\120420-5531-01.dmp
Processors Count : 12
Major Version : 15
Minor Version : 19041
Dump File Size : 2,200,508
Dump File Time : 04-Dec-20 12:30:17
==================================================

==================================================
Dump File : 112920-5531-01.dmp
Crash Time : 29-Nov-20 19:31:14
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : ffff99819b25c00a Parameter 2 : 0000000000000002
Parameter 3 : fffff8073f7ad83b Parameter 4 : 0000000000000002
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+3f5210
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.19041.662 (WinBuild.160101.0800)
Processor : x64
Crash Address : ntoskrnl.exe+3f5210
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\112920-5531-01.dmp
Processors Count : 12
Major Version : 15
Minor Version : 19041
Dump File Size : 2,704,276
Dump File Time : 29-Nov-20 19:31:42
==================================================

==================================================
Dump File : 110320-5843-01.dmp
Crash Time : 03-Nov-20 21:08:11
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : ffffd9812705500a Parameter 2 : 0000000000000002
Parameter 3 : fffff80179aad83b Parameter 4 : 0000000000000002
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+3f45a0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.19041.662 (WinBuild.160101.0800)
Processor : x64
Crash Address : ntoskrnl.exe+3f45a0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\110320-5843-01.dmp
Processors Count : 12
Major Version : 15
Minor Version : 19041
Dump File Size : 2,443,556
Dump File Time : 03-Nov-20 21:08:39
==================================================

==================================================
Dump File : 110120-6640-01.dmp
Crash Time : 01-Nov-20 21:59:54
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : ffffb20125fb7ad6 Parameter 2 : 0000000000000002
Parameter 3 : fffff8028ae1d83b Parameter 4 : 0000000000000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+3f45a0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.19041.662 (WinBuild.160101.0800)
Processor : x64
Crash Address : ntoskrnl.exe+3f45a0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\110120-6640-01.dmp
Processors Count : 12
Major Version : 15
Minor Version : 19041
Dump File Size : 2,276,236
Dump File Time : 01-Nov-20 22:00:22
==================================================

Minidump logs on Windows 10 2004:

==================================================
Dump File : 082720-6343-01.dmp
Crash Time : 27-Aug-20 13:54:27
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : ffffb880fe7b400a Parameter 2 : 0000000000000002
Parameter 3 : fffff8066123c13b Parameter 4 : 0000000000000002
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+3ddf40
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.19041.450 (WinBuild.160101.0800)
Processor : x64
Crash Address : ntoskrnl.exe+3ddf40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\082720-6343-01.dmp
Processors Count : 12
Major Version : 15
Minor Version : 19041
Dump File Size : 3,086,628
Dump File Time : 27-Aug-20 13:54:55
==================================================

==================================================
Dump File : 081420-6578-01.dmp
Crash Time : 14-Aug-20 20:41:24
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : ffffe20047aeb336 Parameter 2 : 0000000000000002
Parameter 3 : fffff8024d9cc13b Parameter 4 : 0000000000000002
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+3ddf40
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.19041.450 (WinBuild.160101.0800)
Processor : x64
Crash Address : ntoskrnl.exe+3ddf40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\081420-6578-01.dmp
Processors Count : 12
Major Version : 15
Minor Version : 19041
Dump File Size : 2,200,708
Dump File Time : 14-Aug-20 20:41:51
==================================================

==================================================
Dump File : 081320-7796-01.dmp
Crash Time : 13-Aug-20 17:45:07
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : ffffa18066540f8a Parameter 2 : 0000000000000002
Parameter 3 : fffff8018fe7c13b Parameter 4 : 0000000000000002
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+3ddb60
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.19041.450 (WinBuild.160101.0800)
Processor : x64
Crash Address : ntoskrnl.exe+3ddb60
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\081320-7796-01.dmp
Processors Count : 12
Major Version : 15
Minor Version : 19041
Dump File Size : 3,401,308
Dump File Time : 13-Aug-20 17:45:40
==================================================

==================================================
Dump File : 080320-6453-01.dmp
Crash Time : 03-Aug-20 18:57:05
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : ffffd201e19ba05e Parameter 2 : 0000000000000002
Parameter 3 : fffff8047d3ec13b Parameter 4 : 0000000000000002
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+3ddb60
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.19041.450 (WinBuild.160101.0800)
Processor : x64
Crash Address : ntoskrnl.exe+3ddb60
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\080320-6453-01.dmp
Processors Count : 12
Major Version : 15
Minor Version : 19041
Dump File Size : 2,679,844
Dump File Time : 03-Aug-20 18:57:34
==================================================

 

[nikicam]

Another one today, also in-game 🙁 Is it possible that this card is faulty? Can someone confirm that all dumps are caused by the ATI drivers?
https://easyupload.io/wviuya

Considering that lately, the freeze is happening only during gaming can we say for sure that the culprit is not related to system memory, especially that I've successfully run 4 passes 2 times with XMP profile ON.

Thanks!

 

[Colif]

Another one today, also in-game 🙁 Is it possible that this card is faulty? Can someone confirm that all dumps are caused by the ATI drivers?
https://easyupload.io/wviuya

I was also checking the GPU temperature and the maximum was at 75 degrees Celsius.
With all this info, can we safely say that the culprit of this issue is not related to system memory, but most probably with an ATI driver or a faulty graphic card?

Thanks!

@gardenman will need to convert it for us.

What gpu is it?
is it made by Asus? if so, you still have

Apr 28 2017

IOMap64.sys

!!! ASUS 64-bit Input Output Map driver (GPU Tweaking driver)

running and it may be causing driver errors.
uninstall Asus GPU Tweak or AI suite if you have them installed.

 

[nikicam]

Thanks for the reply Colif,
The graphic card is made by MSI. This is the one:
Overview Radeon RX 570 ARMOR 8G | MSI Global

would it mean something if I would for a start remove this driver using driver verifier?
https://ibb.co/LgBSLD7
I have also noticed slow desktop performance while connected via NetScaler work environment using the Citrix Workspace app. Once I close Citrix Workspace the system starts flying.

 

[Colif]

driver verifer doesn't remove drivers, it just tests them.

You better off running https://docs.microsoft.com/en-us/sysinternals/downloads/autoruns and stopping it from auto loading with windows. That doesn't stop an application loading it if its needed though

 

[nikicam]

driver verifer doesn't remove drivers, it just tests them.

You better off running https://docs.microsoft.com/en-us/sysinternals/downloads/autoruns and stopping it from auto-loading with windows. That doesn't stop an application loading it if its needed though

I'm using AI Suite only to autotune fans as the system is then ultra silent. Can't do that from the BIOS.

 

[Colif]

if its only used for case fans it shouldn't have anything to do with the AMD drivers.

its possible gpu is to blame. I assume you have tried a few different driver versions by now?

 

[nikicam]

if its only used for case fans it shouldn't have anything to do with the AMD drivers.

its possible gpu is to blame. I assume you have tried a few different driver versions by now?

Correct, I have tried installing several versions of drivers available from the AMD website. I am also currently using drivers offered by the Windows Update.
AI Suite includes several tools for tweaking performance, bios update, fans control and tuning, pc cleaner, etc, but I am only using it for controlling the fans. I am not overclocking my system and I am only using the XMP profile in BIOS to run the memory at the supported speed of 3600MHz.
https://ibb.co/jkYvTHh

 

[Colif]

have you tried the drivers that might be on the GPU makers website for card, most of them have something. If the driver supplied by maker of card doesn't work you have to wonder.

What card is it? can you test card in another PC and see if it has same errors? (I may have asked this already)

AI Suite looks about same as it was a few years ago.

 

[nikicam]

Something strange started happening today. It appears that it was not related to citrix workspace this time. I have really slow PC performance.
For instance, opening windows explorer takes few seconds, even though I have restarted my machine now.
Browsing through folders is also slow. Either now I have a memory issue or something went wrong with my Windows installation..
For instance, when I open task manager I have to wait for 4-5 seconds until it's starts working/refreshing cpu/memory times.
CPU usage 8%, memory 26% and the system is working pretty slow.

 

[Colif]

try safe mode? tell us if its hardware or drivers

Try a clean boot and see if it changes anything - make sure to read instructions and make sure NOT to disable any microsoft services or windows won't load right - https://support.microsoft.com/en-au/help/929135/how-to-perform-a-clean-boot-in-windows

if clean boot fixes it, it shows its likely a startup program. You should, over a number of startups. restart the programs you stopped to isolate the one that is to blame.

 

[nikicam]

I'll try that, but the whole system restarts very slowly. My monitor went in standby for 5-7 seconds before PC started booting the OS. This was never happening during the restart before.
Maybe another memtest would find something now.?

 

[Colif]

i don't think its ram. Ram errors aren't consistent. You don't get it blaming the same driver all the time. I mean, it will but it jumps to another cause if you remove the driver it thinks is bad. Yes, we don't have all 15 errors but recently they all blamed GPU

you could remove gpu and run off the intel hd graphics in CPU, but you won't be able to play many games. Its only to check if errors stop, as if it isn't the GPU then it should just blame something else.

Notices he should have read your op - MSI Armor RX570 graphic card - okay so MSI just say to use AMD. So much for that idea.

slow start could mean some hardware slow to respond at startup. You only have nvme drives so that removes the most common slow down (hdd)

try running samsung Magician on the ssd and run the Diagnostic scans.. SMART doesn't reveal a lot on that page.

 

[nikicam]

I've tried to again install the latest AMD drivers for the graphic card. During this process of removal of current graphic drivers, the system restarted.
BTW, in safe mode, the PC works normally.
The event log says it couldn't write the dump for that issue. Please check the attached files.
Also, once I was trying to uninstall something using the system app in windows 10, this app crashed:

Faulting module name: ntdll.dll, version: 10.0.19041.662, time stamp: 0x27bfa5f0
Exception code: 0xc0000005
Fault offset: 0x0000000000045f86
Faulting process id: 0xc5c
Faulting application start time: 0x01d6d7a5edf615cb
Faulting application path: C:\Windows\ImmersiveControlPanel\SystemSettings.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: ec10d016-d304-441e-8c5f-acd8cbbfd843
Faulting package full name: windows.immersivecontrolpanel_10.0.2.1000_neutral_neutral_cw5n1h2txyewy
Faulting package-relative application ID: microsoft.windows.immersivecontrolpanel

Something strange is going on.
I think it would be best to do a clean install of win10 20H2 and use GPU drivers from Windows update and the latest version of AI suite and then see how it goes then..
Easyupload.io - Upload files for free and transfer big files easily.

 

[Colif]

Its going south pretty quick.
immersive control panel is the new settings menu

I could do without application errors, they seem to be more common of late.
clean install might help.

did you mean to include link to website?

 

[nikicam]

OK, I have reinstalled the machine now, everything is working flawlessly.
I have installed the latest GPU drivers from the AMD website and also have installed AI Suite.
Yesterday I have installed the Microsoft Debugging tool, can't remember which one and I presume that I have turned something on since it asked for a restart.
Anyway, before I have reinstalled my machine I have run into threads linked below, and apparently, this IOMap64.sys is known as a troublesome driver.
error: PAGE_FAULT_IN_NONPAGED_AREA (IOMap64.sys) - Troubleshooting - Linus Tech Tips
IOMap64.sys crashing my computer - Page 2 (asus.com)

I'm thinking about deleting all instances of IOMap64.sys driver as recommended in one of these threads. What do you think?

 

[Colif]

OK, I have reinstalled the machine now, everything is working flawlessly.
I have installed the latest GPU drivers from the AMD website and also have installed AI Suite.
Yesterday I have installed the Microsoft Debugging tool, can't remember which one and I presume that I have turned something on since it asked for a restart.
Anyway, before I have reinstalled my machine I have run into threads linked below, and apparently, this IOMap64.sys is known as a troublesome driver.
error: PAGE_FAULT_IN_NONPAGED_AREA (IOMap64.sys) - Troubleshooting - Linus Tech Tips
IOMap64.sys crashing my computer - Page 2 (asus.com)

I'm thinking about deleting all instances of IOMap64.sys driver as recommended in one of these threads. What do you think?

if you clean installed it shouldn't be on your machine now. Its not part of windows, and unless Windows update randomly installs it (as it might put ASio.sys on PC since its an Asus board) , it shouldn't be there yet.

 

[nikicam]

As mentioned I have installed the Asus AI suite along with the latest graphic drivers from AMD.

Here's what I've discovered about this file:

What is IOMap64?
The genuine IOMap64.sys file is a software component of Asus PC Probe by ASUS.
ASUS PC Probe is a utility software used for hardware device management. AsIOMap64.sys is a system driver required for the proper functioning of ASUS PC Probe. This file is not a critical Windows file and can be removed if known to create problems. ASUS PC Probe is a freeware application designed for the Windows platform that allows users to manage processor and graphics processing unit speeds, monitor and manage system fan RPM, AGP power levels, GPU and RAM temperature. After installation, the program resides in the taskbar and alerts the user on possible hardware issues such as the processor overheating. This program requires an ASUS motherboard as a prerequisite to work.

One guy also said this:
The other possibility is that you may have a bad stick of memory so you should use memtest to find the offending module. This issue has come up many times in the past with bad memory being the most likely cause.

I have tested my memory sticks 2 with memtest passing all 4 passes without error and with XMP profile enabled in BIOS. Is it possible to have a faulty memory stick and should I test these sticks individually with memtest?

 

[Colif]

it always helps to test the sticks by themselves as if you had an error, you wouldn't know which was cause.
Now its up to you, since you ran it already with both and didn't get an error.
I would test 1 stick at a time, 4 runs (since thats max free version offers)

its 4.39am, I should stop answering since i missed the part about you installing AI suite

 

[nikicam]

it always helps to test the sticks by themselves as if you had an error, you wouldn't know which was cause.
Now its up to you, since you ran it already with both and didn't get an error.
I would test 1 stick at a time, 4 runs (since thats max free version offers)

its 4.39am, I should stop answering since i missed the part about you installing AI suite

Go to sleep man and thanks for your kind help.
So you advise testing sticks 1 at a time with 4 runs. I'll probably do that for the weekend.

 

[nikicam]

I found this bogus file in many locations. I wonder should I rename only the one located in the drivers' folder as shown in the dump?
https://ibb.co/Y2XhKLD

 

[nikicam]

The iomap64.sys is a overclocking driver, or can be used for overclocking. That doesn't necessarily mean that it's at fault. But we usually recommend removing overclocks (and sometimes those drivers) when trying to figure out why your system is crashing. I just commented that the file exists on your system, so it may or may not be in an issue (it usually isn't).

It looks like the video driver is mentioned in all dumps. So the issue could be the driver itself (try slightly older ones after using DDU to clean out first), or it could be the card itself (try in another PC), or it still could be a completely different issue that we haven't hit on yet. Usually BSODs take alot of time and testing to figure out, rarely is it figured out with just a few posts.

It makes it very difficult when it crashes only once every 20 days. Maybe johnbl will see this post and have other ideas.

I'm a bit confused now. So according to dump files what is the culprit of this bluescreen?
This is the most important info, right?

BugCheck 50, {ffffae008b223122, 2, fffff8075a726327, 2}
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Could not read faulting driver name
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
Followup: memory_corruption

 

[gardenman]

Yes, the most important line is this one:
*** WARNING: Unable to verify timestamp for atikmdag.sys

Download AutoRuns and disable the IOMap64 with it by simply unchecking the files in the program. Note: If the IOMap64 isn't being used for overclocking, then it might have nothing to do with your crashing. I always warn about the file when I see it because it can be used for overclocking. Also just because others have had issues with the driver that doesn't mean that your issue is the same.

@gardenman will need to convert it for us.

I already converted them, see the previous page.

 

[nikicam]

Hi gardenman,
actually, you haven't run the latest dump through the analyzer:
https://easyupload.io/wviuya

There were 2 crashes and you missed the post with the latest one but I could put my money on it that it will be the same as all other dumps.

I can confirm that in the last 5 months, ever since I've bought this machine, all dumps were exactly the same even though I was reinstalling windows, using several versions of GPU drivers but without luck. Hmm, if I remember correctly I have installed v2004 from the scratch and then I did not experience any bugchecks for some time. After that, I have upgraded to 20H2 and then bugchecks with system restarts were back.

Yesterday I have installed 20H2 from the scratch and unless I start a game I won't see any restarts.

 

[gardenman]

I ran that dump file. It's 122020-5375-01.dmp and the results can be found here: https://forums.tomshardware.com/thr...-fault-in-nonpaged-area.3668253/post-22119251
It's the one at the bottom of that post. I edited my post after you linked to it. It still blames the GPU driver.

 

[nikicam]

I ran that dump file. It's 122020-5375-01.dmp and the results can be found here: https://forums.tomshardware.com/thr...-fault-in-nonpaged-area.3668253/post-22119251
It's the one at the bottom of that post. I edited my post after you linked to it. It still blames the GPU driver.

I'm sorry since I must have overlooked it. Yes, you've run both dumps through the analyzer. Considering I am not tweaking my system we can safely say that it's not the IOMap64.sys driver fault. So the only thing it can be now is the driver or malfunctioning graphic card?