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

Dec 4, 2020
52
0
30
0
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 : 00000000
00000002
Parameter 3 : fffff8036d0dd83b
Parameter 4 : 00000000
00000000
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 : 00000000
00000002
Parameter 3 : fffff8073f7ad83b
Parameter 4 : 00000000
00000002
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 : 00000000
00000002
Parameter 3 : fffff80179aad83b
Parameter 4 : 00000000
00000002
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 : 00000000
00000002
Parameter 3 : fffff8028ae1d83b
Parameter 4 : 00000000
00000000
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 : 00000000
00000002
Parameter 3 : fffff8066123c13b
Parameter 4 : 00000000
00000002
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 : 00000000
00000002
Parameter 3 : fffff8024d9cc13b
Parameter 4 : 00000000
00000002
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 : 00000000
00000002
Parameter 3 : fffff8018fe7c13b
Parameter 4 : 00000000
00000002
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 : 00000000
00000002
Parameter 3 : fffff8047d3ec13b
Parameter 4 : 00000000
00000002
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
==================================================
 

Colif

Win 10 Master
Moderator
But, Asus only supports version 4.24 with Samsung B-die and there's also a version v5.39 with SK Hynix. Since you cannot choose the memory type by the version number but only the part number I'll probably get v5.39 with Hynix B-die.
I have checked with Asus regarding the version number and they have told me that they ONLY support v4.24 that is on the QVL, but not v5.39 even though this memory has the same part number. So, it will be very hard to buy the memory that actually is on Asus QVL.
You can't blame Asus if its Corsair that uses same part number and has 2 different types of ram. I didn't know I had SK Hynex myself until I saw CPU Z recently. I didn't go looking for B Dies as well, I got PC in 2020, its not ideal time to be picky. That and low latency ram was also stupidly expensive, at same time I got 32gb of cl16, I could get 16gb of CL14 for twice the price.

CMK16GX4M2B3600C18 - on ASUS QVL
CMK16GX4M2D3600C18 - not on ASUS QVL
There is new ram made all the time, the makers of motherboards don't test all of it and add them to new motherboards, but as the only difference between those 2 sticks is a B becomes a D, its possible that the later is just an updated version of the former. As time passes it becomes harder to find ram that is on list as most is replaced by ram maker.

Ram doesn't run in XMP without causing crashes. Is the speed of the ram that much slower to warrant replacing it as if PC actually works without BSOD otherwise, I would take it as is.
 

Colif

Win 10 Master
Moderator
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.
always fun when one says it should and they other just says, choose off our list.

Intel cpu are normally better at running off ram not tested by motherboard makers. It sort of depends on if latency and speed of your current ram is similar to ram previously tested.

  1. Can you go to C:\WINDOWS\Minidump
  2. copy the minidump files from here to another folder
  3. upload copies from new folder to a file sharing website
  4. show link here
its possible it a driver error. regardless of what whea logger says. We see what dumps show.
 
Dec 4, 2020
52
0
30
0
Hi Colif, thanks for your reply!

Here's the link to dump files:
https://easyupload.io/qd3n66

BTW, before I have upgraded to the latest Windows 10 version 20H2 I also had these restarts and I have noticed that Windows Update offered me older Intel and AMD drivers. Once I had installed these Intel drivers that were released back in 2016 I didn't have issues in a while. Then after more than 20 days since the upgrade to 20H2 I've started World of Tanks and it crashed twice that day. Once during the game synchronization and the next time once I have alt-tabbed to switch to Windows from the game.

I have checked Windows updates again and there now was another Intel driver ( Intel - System - 2040.100.0.1029) that I have installed so we'll see how it will perform now. I hope this is related to chipset drivers as even though I have reinstalled the system 3 times, updated graphic drivers several times, used Windows 10 2004 and 20H2 versions I have always used the latest chipset drivers from Asus web site and always get the same error. Hopefully, chipset drivers are the culprit here instead of hardware.

Anyhow, is it possible that I have a faulty RAM stick/s even though I have managed to run 4 passes 2 times with Memtest?
 
Dec 4, 2020
52
0
30
0
Hi again,
I was just playing world of tanks and during the map loading the system froze and it restarted with the same bug check code:

==================================================
Dump File : 120620-5906-01.dmp
Crash Time : 06-Dec-20 19:45:51
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : ffffd601d5b02122
Parameter 2 : 00000000
00000002
Parameter 3 : fffff80743edba43
Parameter 4 : 00000000
00000002
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+3f5780
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+3f5780
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\120620-5906-01.dmp
Processors Count : 12
Major Version : 15
Minor Version : 19041
Dump File Size : 2,529,892
Dump File Time : 06-Dec-20 19:46:18
==================================================
 

gardenman

Admirable
Moderator
Hi, I ran the dump files through the debugger and got the following information: https://jsfiddle.net/yms1Ldh8/show This link is for anyone wanting to help. You do not have to view it. It is safe to "run the fiddle" as the page asks.
File information:120420-5531-01.dmp (Dec 4 2020 - 06:29:50)
Bugcheck:PAGE_FAULT_IN_NONPAGED_AREA (50)
Driver warnings:*** WARNING: Unable to verify timestamp for amdkmdag.sys
Probably caused by:memory_corruption (Process: System)
Uptime:1 Day(s), 17 Hour(s), 03 Min(s), and 19 Sec(s)

File information:112920-5531-01.dmp (Nov 29 2020 - 13:31:14)
Bugcheck:PAGE_FAULT_IN_NONPAGED_AREA (50)
Driver warnings:*** WARNING: Unable to verify timestamp for amdkmdag.sys
Probably caused by:memory_corruption (Process: System)
Uptime:6 Day(s), 11 Hour(s), 34 Min(s), and 19 Sec(s)

File information:110320-5843-01.dmp (Nov 3 2020 - 15:08:11)
Bugcheck:PAGE_FAULT_IN_NONPAGED_AREA (50)
Driver warnings:*** WARNING: Unable to verify timestamp for amdkmdag.sys
Probably caused by:memory_corruption (Process: System)
Uptime:1 Day(s), 22 Hour(s), 40 Min(s), and 51 Sec(s)

File information:110120-6640-01.dmp (Nov 1 2020 - 15:59:54)
Bugcheck:PAGE_FAULT_IN_NONPAGED_AREA (50)
Driver warnings:*** WARNING: Unable to verify timestamp for amdkmdag.sys
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 13 Hour(s), 20 Min(s), and 03 Sec(s)
Comment: The GPU tweaking driver "iomap64.sys" was found on your system. (AI Suite or GPU Tweak 2)

Possible Motherboard page: https://www.asus.com/Motherboards-Components/Motherboards/PRIME/PRIME-Z490-P/
Congrats, you are using BIOS version 1410 which is the latest stable version available. It looks like a recent update.

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

Colif

Win 10 Master
Moderator
all 4 are blaming the AMD display drivers.

I would run DDU and reinstall either newer drivers from AMD or after the restart, run windows update and allow windows to download drivers for card, they will still be from AMD, just a little older.

if blame jumps to another driver after this, then we consider if its ram.
 
Dec 4, 2020
52
0
30
0
Hi,
yesterday I was playing World of Tanks for a few battles and I got 2 restarts. Then I have downloaded OCCT and the PC crashed in the first minute since it started the test.

After that, I have removed AMD display drivers that I had installed (the latest stable version) and have installed the driver that was offered through Windows Update as an optional driver update as you can see from the link below.

https://ibb.co/HdH33xV

I have installed this Intel driver a week ago, but this was not the culprit.

After I have removed and installed the offered driver for AMD I have tried to play the game again for about 20-30 minutes and also have run the OCCT for a couple of issues and there were no issues.

Since you're mentioning AI Suite, should I uninstall it and use the latest AMD driver, would this work fine?
 
Dec 4, 2020
52
0
30
0
all 4 are blaming the AMD display drivers.

I would run DDU and reinstall either newer drivers from AMD or after the restart, run windows update and allow windows to download drivers for card, they will still be from AMD, just a little older.

if blame jumps to another driver after this, then we consider if it's ram.
I had at least 15 bug checks with the same code since I've assembled this new machine. I have also tried with the fresh install and the same thing happens. The problem obviously lies in the AMD driver or AI Suite driver.

Thanks to both of you for your kind help. We'll see if the system remains stable now.
 

Colif

Win 10 Master
Moderator
You don't need AI suite unless you were using it to manage fans. i just let bios run fans now days.

without dumps its hard to say what caused others.

If you get any more dumps, just add them here.
 
Dec 4, 2020
52
0
30
0
You don't need AI suite unless you were using it to manage fans. i just let bios run fans now days.

without dumps its hard to say what caused others.

If you get any more dumps, just add them here.
So far the system appears to be working fine. Although I don't have an AMD control panel in the tray as I did with the newer drivers, I was only checking it for the GPU temperatures, nothing else.
I tend to have the ultra-silent system and yes, you're correct I only use it to flash BIOS and manage fans, nothing else.

I'm just sorry I didn't save previous dumps before I did reinstall, but all were the same bug check codes and page_fault_in_nonpaged_area errors.

I just can't understand, it appears to be an AI Suite driver, but it is working now when I have uninstalled the latest AMD drivers and have installed the ones offered from the Windows Update.

I would definitely say that this is a memory-related issue judging by this error, but you guys helped a lot:
https://ibb.co/S5jcKhJ
 

Colif

Win 10 Master
Moderator
Could it be the RAM considering my system completed 2 tests with full 4 passes using XMP profile (3600MHz) without any errors?
My last comment was just because you had mentioned it in opening post, and fact we can't see the previous BSOD on old install.

I can't read the dump files until Gardenman converts them

if you just monitoring GPU temps, you could do this

i set my pc up so the CPU & GPU temps always show in taskbar
 

gardenman

Admirable
Moderator
I ran the new dump files through the debugger and got the following information: https://jsfiddle.net/Lvhbr9on/show This link is for anyone wanting to help. You do not have to view it. It is safe to "run the fiddle" as the page asks.
File information:120620-5906-01.dmp (Dec 6 2020 - 13:45:51)
Bugcheck:PAGE_FAULT_IN_NONPAGED_AREA (50)
Driver warnings:*** WARNING: Unable to verify timestamp for amdkmdag.sys
Probably caused by:memory_corruption (Process: System)
Uptime:2 Day(s), 6 Hour(s), 40 Min(s), and 12 Sec(s)

File information:120620-5812-01.dmp (Dec 6 2020 - 14:31:16)
Bugcheck:PAGE_FAULT_IN_NONPAGED_AREA (50)
Driver warnings:*** WARNING: Unable to verify timestamp for amdkmdag.sys
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 0 Hour(s), 10 Min(s), and 15 Sec(s)

File information:120620-5625-01.dmp (Dec 6 2020 - 14:20:41)
Bugcheck:PAGE_FAULT_IN_NONPAGED_AREA (50)
Driver warnings:*** WARNING: Unable to verify timestamp for amdkmdag.sys
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 0 Hour(s), 34 Min(s), and 29 Sec(s)

File information:120620-5812-02.dmp (Dec 6 2020 - 14:47:47)
Bugcheck:PAGE_FAULT_IN_NONPAGED_AREA (50)
Driver warnings:*** WARNING: Unable to verify timestamp for amdkmdag.sys
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 0 Hour(s), 16 Min(s), and 10 Sec(s)
What are the dates listed on the General tab of Properties for that file?

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.
 
Last edited:
Dec 4, 2020
52
0
30
0
Again, it appears that all four dumps point to the same driver.

The general tab shows the newer date.
https://ibb.co/fHhJ9Bm

For now, I do not have any more restarts, but please let me know who owns this driver, AMD's, or Asus?
Should I just remove AI Suite and use the latest AMD drivers or leave this state as it is now with AI suite installed and AMD drivers installed via Windows Update?
Apparently, AI suite and AMD drivers can't coexist in my PC configuration...
 

Colif

Win 10 Master
Moderator
amdkmdag.sys is the AMD display driver. it is a newer one since the last 4 errors, but they happened on Sunday and haven't you changed the drivers since then?? We installed the Windows drivers this week so this might already be fixed now.

if its not crashing, leave AI suite as is.
 
Dec 4, 2020
52
0
30
0
amdkmdag.sys is the AMD display driver. it is a newer one since the last 4 errors, but they happened on Sunday, and haven't you changed the drivers since then?? We installed the Windows drivers this week so this might already be fixed now.

if its not crashing, leave AI suite as is.
Isn't the culprit of this blue screen error iomap64.sys driver by Asus AI suite?
amdkmdag.sys is newer than the first 4 errors because I have updated AMD drivers to the latest available version in between these crashes. For now, the system is stable, but it was stable before for more than 20 days and then crashed. Although, I feel more optimistic now because you have pointed me in the right direction.

Can I accept both of your answers as "the best answer" since both of you helped a lot ?!
 

gardenman

Admirable
Moderator
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.
 
Dec 4, 2020
52
0
30
0
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 have uninstalled the latest AMD driver using its uninstalled. I haven't used DDU :( But it appears as it is fine now. Well, 20 days without the blue screen and without playing any games. Then after a long time one crash, after which I have updated AMD drivers to the latest version and then several crashes in a couple of days.
I'm just glad that this issue is not related to a hardware error. At least it appears so.
 
Dec 4, 2020
52
0
30
0
Hopefully, you can play games now.
Even before I could have played for many days without a restart, even though I play games occasionally. But, what's interesting that restart always happened during game/WOT garage synchronization or when switching from the game to desktop (alt-tab).
Since I have assembled this machine all restarts had the same fault and bug-check code. I'll probably try to do a fresh install over the weekend with AI Suite installed, but will automatically install drivers for the GPU using Windows Update. Or I might leave it like this until the end of the month to see if the problem will occur again.
 

gardenman

Admirable
Moderator
I ran the dump file through the debugger and got the following information: https://jsfiddle.net/wuzqestx/show This link is for anyone wanting to help. You do not have to view it. It is safe to "run the fiddle" as the page asks.

File information:121920-7437-01.dmp (Dec 19 2020 - 13:42:51)
Bugcheck:PAGE_FAULT_IN_NONPAGED_AREA (50)
Driver warnings:*** WARNING: Unable to verify timestamp for atikmdag.sys
Probably caused by:memory_corruption (Process: System)
Uptime:9 Day(s), 23 Hour(s), 50 Min(s), and 11 Sec(s)

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

Results from dump file below: https://jsfiddle.net/Lfo1xr4t/show

File information:122020-5375-01.dmp (Dec 20 2020 - 12:33:22)
Bugcheck:PAGE_FAULT_IN_NONPAGED_AREA (50)
Driver warnings:*** WARNING: Unable to verify timestamp for atikmdag.sys
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 22 Hour(s), 30 Min(s), and 57 Sec(s)
 
Last edited:
Dec 4, 2020
52
0
30
0
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!
 
Last edited:

ASK THE COMMUNITY

TRENDING THREADS