Question BSOD ntoskrnl.exe+1c2390 on brand new desktop

May 19, 2020
21
0
10
0
After much research on the internet I found the forum of you who seem to be experts on the subject and I have faced several BSOD's on my new PC.
I bought several new pieces and asked a friend to assemble it. Since after installing Windows he warned me about some BSOD's and that I should look for bad blocks on the old hard drive, a 1 TB that I used to store files. Even without finding errors in CrystalDiskInfo and TunePro HDD, I decided to remove the HD from the PC, but the blue screens keep happening.

Setup:
AMD Ryzen 7 2200X
Asus b450 Gaming?BR
HyperX Fury DDR4 16GB 2400mhz
Samsung SSD EVO 120GB
Geforce GTX 1660 6GB GPU
PowerThermaltake Smart 600W

Bios updated
Updated chipset
Updated video driver
Updated Windows

What I did:
I've recovered Windows several times but the problem persists.
I performed a Windows memory test
I performed chkdsk /r /f test
sfc scannow test
DISM RestoreHealth
GPU stress test with OTTC

Besides the blue screens there are also black screens, where the PC does not shut down. Sometimes there are crashes, which already happened in the BIOS or would be POST?) and also occurred that Windows does not stay clickable. (video)
I'm using a Microsoft offline account because I notice a distinct improvement. Microsoft account is slow from the first moments.
Ironically, when I play online poker I don't experience crashes. I play for hours and no blue screen happens. However, there is no specific action that triggers the BSOD.

BlueScreenView here

BTW: 442.92 is the updated driver for Nvidia, and i dont know if this is the problem.

Crash Dump Analysis

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Tue 19/05/2020 14:45:44 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\051920-7156-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x139 (0x3, 0xFFFFAC08FD053700, 0xFFFFAC08FD053658, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 19/05/2020 14:45:44 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x139 (0x3, 0xFFFFAC08FD053700, 0xFFFFAC08FD053658, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 19/05/2020 14:40:31 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\051920-7171-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x139 (0x3, 0xFFFFD50BC72B56A0, 0xFFFFD50BC72B55F8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 19/05/2020 14:34:25 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\051920-7546-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x5518)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8028C715518, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispsi.inf_amd64_85e939ca9040d47c\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 442.92
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 442.92
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 442.92 , NVIDIA Corporation).
Google query: NVIDIA Corporation KMODE_EXCEPTION_NOT_HANDLED



On Tue 19/05/2020 14:30:36 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\051920-7859-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x139 (0x3, 0xFFFFE88034EA77B0, 0xFFFFE88034EA7708, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 19/05/2020 14:26:21 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\051920-7453-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x139 (0x3, 0xFFFFEC8B9A0A7700, 0xFFFFEC8B9A0A7658, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.





Conclusion



6 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 442.92 , NVIDIA Corporation)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.
 
Last edited:
May 18, 2020
4
0
10
0
Really simple quick try: Remove the Windows 10-KB4556799 update, restart your PC, and check again. I had the almost exact same issue and after flashing BIOS, reinstalling windows etc. etc. that little thing did the trick.
It's also a known issue. Let me know how it goes.
 
May 19, 2020
21
0
10
0
Yep, I had the same thing. Just keep trying. Thats what I did.
UPDATE

I couldn't uninstall it. I tried several times, with clean boot, safe mode and even at the command prompt through the wmic qfe list brief /format:table.

I restored Windows, again, and did not update Windows. I just installed NVIDIA Game Driver and received this blue screen.


Computer name: DESKTOP-KVDRVBJ
Windows version: Windows 10 , 10.0, build: 18363
Windows dir: C:\WINDOWS
Hardware: ASUSTeK COMPUTER INC., PRIME B450M-GAMING/BR
CPU: AuthenticAMD AMD Ryzen 7 2700X Eight-Core Processor AMD8664, level: 23
16 logical processors, active mask: 65535
RAM: 17107705856 bytes (15,9GB)


--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dumps are enabled on your computer.
Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump
On Tue 19/05/2020 22:21:18 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!setjmpex+0x81D9)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF805179C971F)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Tue 19/05/2020 22:21:18 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\051920-8046-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF805179C971F)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Tue 19/05/2020 22:19:45 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\051920-7781-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF803694DD2DB)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
 
May 19, 2020
21
0
10
0
UPDATE 2:

Freeze scren and new BSOD, Kernel Securiy Check

Turned off energy options settings to NEVER and changed Economy energy plan from AMD Ryzen Balanced to Windows. NEVER suspend activity and NEVER turn off video

Crash Dump Analysis

Crash dumps are enabled on your computer.

Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump

On Tue 19/05/2020 23:16:42 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!setjmpex+0x81D9)
Bugcheck code: 0x139 (0x3, 0xFFFF9B01E3C8B6A0, 0xFFFF9B01E3C8B5F8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 19/05/2020 23:16:42 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\051920-7562-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390)
Bugcheck code: 0x139 (0x3, 0xFFFF9B01E3C8B6A0, 0xFFFF9B01E3C8B5F8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
 
May 19, 2020
21
0
10
0
UPDATE 3

I was playing online poker and everything was smooth. I sit out and a few seconds later I received a new blue screen (below).

I updated the AMD chipset driver following the recommendation from Toms's Hardware page.

https://www.tomshardware.com/news/amd-driver-problems-chipset-ryzen

Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dumps are enabled on your computer.
Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump
On Wed 20/05/2020 00:53:14 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\052020-7015-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390)
Bugcheck code: 0x1E (0xFFFFFFFFC0000096, 0xFFFFF8072ED20257, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Wed 20/05/2020 00:53:14 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: afd.sys (afd+0x58844)
Bugcheck code: 0x1E (0xFFFFFFFFC0000096, 0xFFFFF8072ED20257, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\afd.sys
product: Sistema Operacional Microsoft® Windows®
company: Microsoft Corporation
description: Ancillary Function Driver for WinSock
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
 
May 19, 2020
21
0
10
0
UPDATE 4

I restarted the PC after the driver was updated and received a black screen where I enter the Microsoft login info
 
Last edited:
May 19, 2020
21
0
10
0
UPDATE 5

The same thing that happened on UPDATE 3 happened again. Sit out playing poker and when i came back new error.

Crash dumps are enabled on your computer.

Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump

On Wed 20/05/2020 02:25:09 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\052020-7109-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390)
Bugcheck code: 0x4E (0x2, 0x144522, 0x41F37F, 0x8)
Error: PFN_LIST_CORRUPT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 20/05/2020 02:25:09 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!memset+0x714E5)
Bugcheck code: 0x4E (0x2, 0x144522, 0x41F37F, 0x8)
Error: PFN_LIST_CORRUPT
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 20/05/2020 02:21:19 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\052020-7140-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390)
Bugcheck code: 0x133 (0x1, 0x1E00, 0xFFFFF80406B73358, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


Do you guys have any idea if it is a driver or a hardware problem?
 

Colif

Win 10 Master
Moderator
May 19, 2020
21
0
10
0
Go to C:\WINDOWS\Minidump
copy the minidump files to another folder
upload the copies from new folder to a file sharing website
show link here and I get a friend to look at dumps

One BSOD did blame Nvidia drivers, sometimes having latest drivers from Nvidia isn't a good idea. Could run ddu and try other Nvidia drivers - https://forums.tomshardware.com/faq/how-to-perform-a-clean-install-of-your-video-card-drivers.2402269/
Thank you. Done.
https://drive.google.com/drive/folders/1UiRn8OGcH7uzPOz1FxaCvUjEGUdmrudB?usp=sharing
 

gardenman

Admirable
Moderator
I can't sleep, so I'm here about 3 hours early. I ran the dump files through the debugger and got the following information: https://segmentalpolarbear.htmlpasta.com/
File information:052020-7140-01.dmp (May 20 2020 - 01:21:19)
Bugcheck:DPC_WATCHDOG_VIOLATION (133)
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 1 Hour(s), 14 Min(s), and 57 Sec(s)

File information:052020-7109-01.dmp (May 20 2020 - 01:25:09)
Bugcheck:PFN_LIST_CORRUPT (4E)
Probably caused by:memory_corruption (Process: MsMpEng.exe)
Uptime:0 Day(s), 0 Hour(s), 03 Min(s), and 02 Sec(s)

File information:052020-7015-01.dmp (May 19 2020 - 23:53:14)
Bugcheck:KMODE_EXCEPTION_NOT_HANDLED (1E)
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 1 Hour(s), 35 Min(s), and 55 Sec(s)

File information:051920-8046-01.dmp (May 19 2020 - 21:21:18)
Bugcheck:IRQL_NOT_LESS_OR_EQUAL (A)
Probably caused by:memory_corruption (Process: svchost.exe)
Uptime:0 Day(s), 0 Hour(s), 00 Min(s), and 48 Sec(s)

File information:051920-7562-01.dmp (May 19 2020 - 22:16:42)
Bugcheck:KERNEL_SECURITY_CHECK_FAILURE (139)
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 0 Hour(s), 04 Min(s), and 14 Sec(s)
Possible Motherboard page: https://www.asus.com/br/Motherboards/PRIME-B450M-GAMING-BR/
While I can't speak the language, I think you have the latest BIOS already installed, version 2006.

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
I can't sleep, so I'm here about 3 hours early.
that's funny as I went to sleep early instead.

Error 2 that crashed MsMpEng is likely LAN drivers (the process is part of windows defender)
latest LAN drivers here - https://www.realtek.com/en/component/zoo/category/network-interface-controllers-10-100-1000m-gigabit-ethernet-pci-express-software
Error 3 likely LAN. Mentions afd.sys which is ancillary Function Driver for winsock.
Winsock is a programming interface and the supporting program that handles input/output requests for Internet applications in a Windows operating system

the other 3 aren't as obvious.

wonders what this is
Jul 10 2012LPCFilter.sysLPC Filter Stack driver (Compal Electronic Inc)

fun fact
Mar 19 2015amd_sata.sysAMD SATA Controller AHCI Device driver http://support.amd.com/
Mar 19 2015amd_xata.sysAMD Stor Filter driver http://support.amd.com/
AMD themselves suggest you don't use these and roll the drivers back to the MIcrosoft versions
https://www.amd.com/en/support/kb/faq/pa-250
 
May 19, 2020
21
0
10
0
ok, my friend won't be on for about 8 hours or so due to being in USA so it will be a while.
thank you for your help.

UPDATE 6

while i was Reading the fórum got a BSOD Kernel Security Check Failure

I can't sleep, so I'm here about 3 hours early. I ran the dump files through the debugger and got the following information: https://segmentalpolarbear.htmlpasta.com/
i hope you sleep better.

Updated the LAN drivers and cant roll back SATA Controller drivers, option to roll back AMD Sata and AHCI is disabled.

sould i install any of these drivers?
https://www.catalog.update.microsoft.com/Search.aspx?q=sata

if you need specific information of the motherboard i can search and translate for you.
 
Last edited:

Colif

Win 10 Master
Moderator
can you give us a new dump file each time you crash, makes it easier to find the new ones then

While I can't speak the language, I think you have the latest BIOS already installed, version 2006.
It doesn't matter, the driver pages are in English although section headers aren't

clever your chipset driver is newer than one on Asus website, its dated 20/1/20 and yet system has an AMD driver from March on it.
https://www.asus.com/br/Motherboards/PRIME-B450M-GAMING-BR/HelpDesk_Download/
 

Colif

Win 10 Master
Moderator
So i wonder where this came from then -
Mar 03 2020AMDPCIDev.sysAdvanced Micro Devices PCI Device driver

as I would have thought it was part of chipset? only thing that new on Asus site is AI Suite and I doubt it includes it. I guess it doesn't matter unless it shows as a cause.

I am not going to guess when/where Gardenman is this time :)
 

gardenman

Admirable
Moderator
I ran the dump file through the debugger and got the following information: https://dormientcount.htmlpasta.com/

File information:052020-9390-01.dmp (May 20 2020 - 18:16:47)
Bugcheck:KERNEL_SECURITY_CHECK_FAILURE (139)
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 13 Hour(s), 25 Min(s), and 47 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.
 

Colif

Win 10 Master
Moderator
I can't tell what cause of that is. I can tell its a driver but not which one :)

possible causes - Nvidia drivers. Yes, I know, they fairly new but having newest can cause errors.
realtek lan driver - I seen a lot of people with lan driver problems and I am not even sure if its not win 10 causing those.

the crashes don't look to be caused by either of those though, or not obviously anyway. Just leave them for now.
Do you have an LG printer?
Mar 05 2015wdfserial.sysSerial Device driver (LG Electronics Inc.)
 
May 19, 2020
21
0
10
0
well, i didnt experience any crashes since the lan driver update.

the LG is the monitor. didnt install any drivers for it.

by now everything is smooth, and im just waiting for the next BSOD (hope it doesnt happen).
 
May 19, 2020
21
0
10
0
Last edited:

gardenman

Admirable
Moderator
I ran the dump file through the debugger and got the following information: https://fricativeposition.htmlpasta.com/

File information:052020-7015-01.dmp (May 19 2020 - 23:53:14)
Bugcheck:KMODE_EXCEPTION_NOT_HANDLED (1E)
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 1 Hour(s), 35 Min(s), and 55 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.
 

ASK THE COMMUNITY

TRENDING THREADS

Latest posts