[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]

Any other ideas?
One of my friends suspects on GDDR memory. I have opened a ticket with MSI and AMD and hopefully, they will be able to detect if the card is faulty with the dump info provided.

 

[Colif]

it looks like the display driver called a location in the page file that was incorrect.

can't you get newer drivers? both crashes the drivers were

Aug 27 2019	atikmdag.sys	ATI Radeon Kernel Mode driver
Aug 27 2019	atikmpag.sys	ATI video card driver

latest here dated 8th Dec - https://www.amd.com/en/support/graphics/radeon-500-series/radeon-rx-500-series/radeon-rx-570

 

[nikicam]

I have reinstalled Windows 10 a couple of days ago and have installed the latest drivers 20.12.1 for the graphic card. I still haven't played the game to see if the crash will happen again.

 

[nikicam]

Hey guys,
hopefully, someone will still be able to provide suggestions.

I have reinstalled Windows, made a clean install of Windows 10 2004 on December 21, 2020, and was playing games every few days. I have also installed 20.12.1 AMD drivers that are the newest available.
The first crash happened today on 09.01.2021 with the same old bug check code.

On Sat 09-Jan-21 11:21:03 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\010921-7312-01.dmp
This was probably caused by the following module: amdkmdag.sys (0xFFFFF80170F8BA43)
Bugcheck code: 0x50 (0xFFFFCC007907505E, 0x2, 0xFFFFF80170F8BA43, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\System32\DriverStore\FileRepository\u0361901.inf_amd64_204a65b18f2a904a\B361909\amdkmdag.sys
product: ATI Radeon Family
company: Advanced Micro Devices, Inc.
description: ATI Radeon Kernel Mode Driver
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: amdkmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).
Google query: amdkmdag.sys Advanced Micro Devices, Inc. PAGE_FAULT_IN_NONPAGED_AREA

Here is the dump file so you can run it through analyzer.
https://easyupload.io/qe2tfs

Thanks in advance!

 

[Colif]

The first crash happened today on 09.01.2021 with the same old bug check code.

and the same old Drivers again.. maybe different version but its the same.

tries to think of a suggestion... guess i wait until gardenman converts it.

 

[nikicam]

Thanks, Colif.
I've found this info on the net, is this user referring to GPU processor?

Your processor is not working stably. The atikmdag.sys error does not always indicate GPU driver error. The error you get is probably due to your processor not working properly.
BSOD - atikmdag.sys - cannot resolve - AMD Community

 

[Colif]

first i heard of that.

Re: BSOD Error Code: atikmdag.sys (0xFFFFF806384AD0C4)
IRQL_NOT_LESS_OR_EQUAL BSOD reason is not GPU. It is also not the RAMs. It is the CPU. Go to the BIOS of your motherboard and find the "CPU Core Ratio" section. Give this value manually 41. You can also try to set manual CPU core voltage, but "CPU Core Ratio" change will reduce your CPU-induced errors.

You cannot probably fix atikmdag.sys errors with driver updates. A driver may fail immediately. The other is with 2 hours of gaming experience. So this error is hardware-related. Your GPU is an OC version. For this reason, changing some settings with WattMan may solve the problem. Set GPU power limit value to -10% and decrease CPU core frequency by -5% with WattMan.

With these changes, your system will work stably. If it doesn't work, use your consumer rights about the GPU. I think your motherboard is not broken. Also use two different PSU cables for GPU power. You should definitely don't give 16PIN GPU power with a single cable.

https://community.amd.com/t5/processors/bsod-error-code-atikmdag-sys-0xfffff806384ad0c4/td-p/56923

thats a 3700x, but he also has a AMD gpu, so according to this guy its a CPU setting, not GPU.
You are in same position, AMD CPU/GPU
I don't know what setting you would set for your CPU though. You might want to ask on AMD forums since that is where he is.

makes sense for it not to be GPU as 99% of the time, the errors I see for AMD cards are almost always "thread stuck in Device driver", I can almost guess its an AMD card based on that error.

 

[nikicam]

You are in same position, AMD CPU/GPU
makes sense for it not to be GPU as 99% of the time, the errors I see for AMD cards are almost always "thread stuck in Device driver", I can almost guess it's an AMD card based on that error.

Actually, I have Intel CPU and AMD GPU. If that's what you've meant?

 

[Colif]

i got mixed up since most people I fix these days have AMD cpu.

You still might want to ask on the AMD forums since its always the same driver that appears. They might be able to suggest I fix I don't know

 

[nikicam]

i got mixed up since most people I fix these days have AMD cpu.

You still might want to ask on the AMD forums since its always the same driver that appears. They might be able to suggest I fix I don't know

I have written to both MSI and AMD support where AMD support seems to be terrible.

First I have written what I have written here and got the following reply from MSI:

1. Please try to uninstall the graphics card driver, and then reinstall the latest version of the graphics card driver.

1. Please try to reinstall the operating system to see if it can be resolved.
2. Please try to plug the graphics card into another PC to see if the same phenomenon occurs.

Then I have replied that I have reinstalled Windows 10 v2004 and so far I don't have any issues. I also asked is it possible that this error could be related to Video RAM. And I got the following reply

It is recommended that you contact the local service center to check whether the graphics card needs repair. If there is no contact information, I will ask a colleague of our maintenance department to contact you.

 

[Colif]

I guess MSI think its the card then, have you contacted them? or are you waiting for a reply?

 

[nikicam]

I have written them another update and waiting for a reply.
BTW, I am currently stress testing Video GPU using OCCT, but unfortunately, it can only test up to 6GB, while my card has 8GB.
Once this test completes I might stress test the CPU, although I doubt it's the CPU.

I remember that I have run OCCT after I had one crash and it crashed during the first 10 seconds. All dumps had the same bug check code. Those 3 crashes happened in the same day and after I have updated AMD drivers.

 

[Colif]

if problem is physical no driver will fix it.

here are few other options to test vram - https://www.raymond.cc/blog/having-problems-with-video-card-stress-test-its-memory/

 

[nikicam]

I doubt it's video RAM, so far the OCCT memory stress test is going fine. I've found that this appears to be a common issue.
(2) Question - keep getting amdkmdag.sys error & crash | Tom's Hardware Forum

 

[nikicam]

if problem is physical no driver will fix it.

here are few other options to test vram - https://www.raymond.cc/blog/having-problems-with-video-card-stress-test-its-memory/

Colif, have you read my post I've written that I am currently testing my GPU RAM with OCCT which is at the top of the list from your link

 

[Colif]

BTW, I am currently stress testing Video GPU using OCCT, but unfortunately, it can only test up to 6GB, while my card has 8GB.

i offered the tests as maybe one of the others can test all 8gb? I saw it was there, I should have said...

 

[nikicam]

i offered the tests as maybe one of the others can test all 8gb? I saw it was there, I should have said...

Oh, sorry about that. Thanks!
Well, I have successfully run the memory stress test with OCCT for one hour. After that, I have run a system stress test and it crashed during the first couple of minutes with the same bug check code.:
https://ibb.co/WyxPmMg

I am now starting another system stress test to see what will happen.

 

[Colif]

Could be the fault on GPU isn't memory but something to do with the processor itself on GPU. Might explain why OCCT doesn't crash it but the other system stress test did.

I wonder if its the PSU. I know everything points at GPU but I just wonder if I am wrong. Only way to find out is contact MSI since every BSOD so far blamed GPU.
https://www.msi.com/support/technical_details/how-to-send-my-product-for-repair-service

 

[nikicam]

Could be the fault on GPU isn't memory but something to do with the processor itself on GPU. Might explain why OCCT doesn't crash it but the other system stress test did.

I wonder if its the PSU. I know everything points at GPU but I just wonder if I am wrong. Only way to find out is contact MSI since every BSOD so far blamed GPU.
https://www.msi.com/support/technical_details/how-to-send-my-product-for-repair-service

Sorry Colif, I wasn't clear enough.
After the successful OCCT stress test of GPU RAM, I have run the SYSTEM stress test with OCCT.

First attempt with the default settings as you can see in the picture below: The system crashed in a couple of minutes. Same bug check code.
https://ibb.co/WyxPmMg

The second attempt with the default settings and duration changed to 30 minutes. The system crashed in a couple of minutes. Same bug check code.

Third attempt with the default OCCT system stress test and duration set to 10 minutes. The stress test passed without errors.

Now, I will run again the OCCT system stress test with the duration set to 30 minutes.

 

[Colif]

i was just covering my bases in case you get a replacement GPU and it still crashes with same error.

are you tracking GPU temps/usage on the graphs as CPU isn't even hot in that shot .

I leave you to it, I am not really helping right now.

 

[nikicam]

Thanks for your comments Colif!

Here's what happened next:

On 4th attempt, the system froze and I had to manually reset the system using the reset button. No dump was created during this freeze.
On the 5th attempt, the system froze after 7 minutes and I have taken picture of the system temperatures during the freeze. It appears that temperatures were just fine (please check the image below). If you notice the mouse cursor was a bit scrambled pointing to a video issue. And this time Colif, for the first time I had different dump information, but it was related to the same old amdkmdag.sys driver.

Screenshot of the system during the freeze:
https://ibb.co/Csr30tJ

This time instead of PAGE_FAULT_IN_NONPAGED_AREA the error was: VIDEO_TDR_ERROR.

On Sat 09-Jan-21 15:25:42 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\010921-5484-01.dmp
This was probably caused by the following module: amdkmdag.sys (0xFFFFF8024CAD5040)
Bugcheck code: 0x116 (0xFFFFBB8C5D073060, 0xFFFFF8024CAD5040, 0xFFFFFFFFC0000001, 0x3)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\System32\DriverStore\FileRepository\u0361901.inf_amd64_204a65b18f2a904a\B361909\amdkmdag.sys
product: ATI Radeon Family
company: Advanced Micro Devices, Inc.
description: ATI Radeon Kernel Mode Driver
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: amdkmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).
Google query: amdkmdag.sys Advanced Micro Devices, Inc. VIDEO_TDR_ERROR

Hopefully, gardenman will run dump files through the analyzer soon. Here are all of the dump files collected.
https://easyupload.io/utul3t

With all of the information I have now, can we say that the problem is either with the GPU driver or with the graphic card itself? If I need to use the older driver, AMD or ATI support should point me in that direction. I presume it could be that my system isn't compatible with this AMD amdkmdag.sys module..

 

[Colif]

i think its the card, as do MSI.

Have you reinstalled windows since it started? If yes, its still blaming same driver. Its always same things. Its screaming FIX me.

Video TDR is another BSOD I often see with AMD cards. There are a few that make guessing what gpu you have easier. Nvidia cards are less obvious.
Different BSOD, same driver.

converting dump won't tell us anything the whocrashed report isn't already, it will show the driver name we can already see.

I think only fix is get a new card. There aren't any magic drivers that will fix this.

 

[nikicam]

i think its the card, as do MSI.

Have you reinstalled windows since it started? If yes, its still blaming same driver. Its always same things. Its screaming FIX me.

It started ever since I've built up this machine. Since July 2020 I have reinstalled Windows 10 three times. Thanks for your help Colif.
I have updated all of this info to the MSI ticket and will probably send this card back. It was a long and tough journey through debugging of this issue

 

[Colif]

hope new card fixes it and you can just forget about it and enjoy your new pc

 

[nikicam]

Hi again Colif,
it appears that the problem is not with my RX570 graphic card. Let me post what I have tried so far:

I have tried the following:

1. I have put my RX570 card in my old i5 3rd Gen system also with Asus MBO and run OCCT stress test twice. It went without the freeze or errors.
2. I have put my RX550 card from my old PC to the new one i5 10th-gen and run the OCCT stress test. In two tests the system froze both times. The first time the system became unresponsive so I had to reset the machine using the reset button. After PC booted again I found this in my system log:

Event 1, WHEA-Logger (A fatal hardware error has occurred. A record describing the condition is contained in the data section of this event. During this freez dump was not saved.

The second freeze came up after only 1 minute of OCCT stress test with the following dump error:

On Sat 16-Jan-21 10:36:52 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: amdkmdag.sys (amdkmdag+0x70C00)
Bugcheck code: 0xEA (0xFFFF858E0A2FA0C0, 0x0, 0x0, 0x0)
Error: THREAD_STUCK_IN_DEVICE_DRIVER
file path: C:\Windows\System32\DriverStore\FileRepository\u0361901.inf_amd64_204a65b18f2a904a\B361909\amdkmdag.sys
product: ATI Radeon Family
company: Advanced Micro Devices, Inc.
description: ATI Radeon Kernel Mode Driver
Bug check description: This indicates that a thread in a device driver is endlessly spinning.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: amdkmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).
Google query: amdkmdag.sys Advanced Micro Devices, Inc. THREAD_STUCK_IN_DEVICE_DRIVER

On Sat 16-Jan-21 10:36:27 your computer crashed or a problem was reported
crash dump file: C:\Windows\LiveKernelReports\PoW32kWatchdog-20210116-1036.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!IoUnregisterShutdownNotification+0xF84)
Bugcheck code: 0x1A1 (0xFFFF858E0A32C040, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR

The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

1. I have run the OCCT stress test twice on my new machine without AMD drivers and without any graphic card installed and it passed both times without errors of freeze!

So, this appears as an AMD driver incompatibility issue with my new system or I have some other issue. I’m clueless now.