[SOLVED] kernel security check failure bsod

[Lenard D.]

HI guys, I'am having this problem in my ryzen unit for some time now
processor: ryzen 5 2400g
mobo.: msi a320m vh-pro
ram: avixer 1x8gb budget series 2133 MHz
gpu: rx 570
psu: corsair 650 watts
I have recently installed my os because of bsod problem in the past, the unit was working fine for a month then kernel security check failure bsod comes up again.
hoping someone knows how to fix this issue

https://drive.google.com/file/d/11_XCUl-TvdJYR5Y2RNKxeneX7NPG9NTF/view?usp=sharing
sorry I tried to open the mini dump with notepad, appreciate any help tnx

 

[Lenard D.]

I just want to update the thread, I tried almost everything suggested for this type of problem but had no luck for the past week of fixing it. BOSD got even worse and I cant even use the pc properly anymore, with in a day this are some of the list i got form WhoCrushed other crush dump were unreadable.

B]Crash dump directories:[/B]
C:\Windows
C:\Windows\Minidump

On Tue 4/28/2020 10:22:52 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\042820-16531-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390)
Bugcheck code: 0x1A (0x3453, 0xFFFF9B86D09544C0, 0x2C8F2, 0x3)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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. This problem might also be caused because of overheating (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.



On Tue 4/28/2020 10:22:52 PM 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+0x9BDFC)
Bugcheck code: 0x1A (0x3453, 0xFFFF9B86D09544C0, 0x2C8F2, 0x3)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
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. This problem might also be caused because of overheating (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.



On Tue 4/28/2020 7:20:31 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\042820-13000-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390)
Bugcheck code: 0xA (0x10, 0x2, 0x1, 0xFFFFF80782E96C8C)
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 4/28/2020 6:22:03 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\042820-12171-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390)
Bugcheck code: 0xFC (0xFFFFF8031BD79A81, 0x800000015ED08929, 0xFFFF91881534F350, 0x2)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
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 an attempt was made to execute non-executable memory.
This may be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. Memory corruption can also occur because of overheating (thermal issue). There is a possibility this problem was caused by a virus or other malware.
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 4/28/2020 5:34:01 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\042820-13515-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390)
Bugcheck code: 0xA (0x38, 0x2, 0x0, 0xFFFFF8050C2D18CF)
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 4/28/2020 3:43:00 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\042820-12109-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390)
Bugcheck code: 0x133 (0x1, 0x1E00, 0xFFFFF8016DF73358, 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.



On Tue 4/28/2020 12:24:00 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\042820-14281-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390)
Bugcheck code: 0x139 (0x4, 0xFFFFC8018777EFF0, 0xFFFFC8018777EF48, 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.



On Tue 4/28/2020 9:51:33 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\042820-15671-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390)
Bugcheck code: 0x133 (0x1, 0x1E00, 0xFFFFF80413173358, 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.



On Tue 4/28/2020 9:35:54 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\042820-17531-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390)
Bugcheck code: 0xBE (0xFFFFAF9001F422F0, 0x8A00000005300121, 0xFFFFF30E54813D20, 0xA)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 4/28/2020 9:30:18 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\042820-22109-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2390)
Bugcheck code: 0xBE (0xFFFF9E8008FBA710, 0x8A00000005100121, 0xFFFFF28AD01DFD20, 0xA)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

[Lenard D.]

Here are some of the fixes that I've tried hopefully it may help other

sofware fixes:

1. I run memory diagnostic (1x8gb 2133 mhz @ stock) in extended settings run it three times, went to the event viewer and there were no error found.

2. I have also use memtest86, run it for under an hour and no red lines pop up while the memory is being tested http://memtest.org/ this shows the memory was clear of any faults

3. so I check the ssd if it had any errors run chkdsk /r in both cmd and windows power shell in admin. even use a third party app to cheack for bad sector in the ssd https://www.seagate.com/as/en/support/downloads/seatools/seatools-win-master/ the storage came up clean and had no errors

4. Microsoft suggested the sfc /verifyonly for checking any corrupted files or registry and sfc /scannow to try to repair if any errors shows up. This does not help in my case

under cmd admin. I also tried dism /online /cleanup-image /scanhealth

dism /online /cleanup-image /cheackhealth

dism /online /cleanup-image /restorehealth

5. bios updated (msi a320m pro-vh plus) all setting are left in default

6. tried clean install of graphics driver done it multiple times , i tried both amd and ddu in safe mode

https://www.amd.com/en/support/kb/faq/gpu-601

https://www.guru3d.com/files-details/display-driver-uninstaller-download.html

i suggest if anyone is having problems in their amd gpu drivers try uninstalling gpu drivers first in safe mode the links above will direct you to the dl site. then boot up in windows (not in safe mode) try downloading the latest drivers for your gpu https://www.amd.com/en/support and install . unfortunately this does not work for me

7. micrsoft also suggested to rollback to previous windows version ( I'am currently running 1909 vr) this dont work if you've just updated and use the computer for more than 10 days windows wont allow you to roll back in old version, you can also try uninstalling the installed drivers. go to settings, update and security then veiw update history from their you can choose what updates to uninstall

8. for amd mobo and cpu if your having problem in voltage, temp, core clock speed, etc that is you think maybe connected to bios but already updated you bios try updating your chipset driver https://www.amd.com/en/support , choose chipset in the selection and the socket of the motherboard if you don't now what socket your mobo is try finding that box you throw when building the pc.

9. most especially what others are commonly suggesting is drivers update, windows wont be able to update all drivers in your pc try using third party application or if your patient enough go to the driver management and try updating the drivers manually

10. if none of that helps like in my case, try for other changing the components like ram modules, power supply or re placing the cpu in the socket and cleaning both ram and cpu socket

i borrowed some components from a friend to test if some of the hardware is causing the issues, but after re installing windows the BOSD, freezing and crushes both in idle and doing work with the units came back just within a day of using it.

conclusion: don't give up on trying to finding solution to pc issues or problems because some of the fixes might really help on solving your problem, but in my case it seems like that I've exhausted all the options I know, my best guess is that I was not lucky to get a good cpu or its my motherboard and if I'am going to buy a replacement for both I guess I would just go back to much stable and reliable build.

Hopefully some of the fixes that I've tried might work on your pc problems.