[SOLVED] Constant BSOD's all linked to ntoskrnl.exe. What should I do?

[Deodorant Operator]

For quite a while now, I've been getting Blue Screen's Of Death, out of nowhere. Recently, I've found out that they've all been linked to ntoskrnl.exe. I'm attempting to prevent these annoying instances, because they have turned from something scary, to something just plain irritating from the amount of times it's happened. Some names of bugs I've gotten more than once, is: DRIVER_IRQL_NOT_LESS_OR_EQUAL, SYSTEM_SERVICE_EXCEPTION, UNEXPECTED_KERNEL_MODE_TRAP, and KMODE_EXCEPTION_NOT_HANDLED. I've attempted fixes for these, but, I haven't had any luck. If anyone can come up with a solution, It'd be greatly appreciated. Here's an example of one of the reports I've gotten from today, but I'm not sure of the amount of information it may give:

072121-8781-01.dmp
7/21/2021 6:14:33 PM
DRIVER_IRQL_NOT_LESS_OR_EQUAL
0x000000d1
0000000000000000 0000000000000002
0000000000000008 0000000000000000
ntoskrnl.exe
ntoskrnl.exe+3f6f20
x64
ntoskrnl.exe+3f6f20
C:\WINDOWS\Minidump\072121-8781-01.dmp
12
15
19041
1,220,580
7/21/2021 6:15:19 PM

 

[Colif]

1. Open Windows File Explore
   
2. Navigate to C:\Windows\Minidump
   
3. Copy the mini-dump files out onto your Desktop
   
4. Do not use Winzip, use the built in facility in Windows
   
5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
   
6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
   
7. Then post a link here to the zip file, so we can take a look for you . . .
   

NTOSKRNL = windows kernel. It handles all driver requests, power management, and memory management. It sits between Hardware and Applications. It got blamed but its not the cause

 

[Deodorant Operator]

1. Open Windows File Explore
2. Navigate to C:\Windows\Minidump
3. Copy the mini-dump files out onto your Desktop
4. Do not use Winzip, use the built in facility in Windows
5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
7. Then post a link here to the zip file, so we can take a look for you . . .

NTOSKRNL = windows kernel. It handles all driver requests, power management, and memory management. It sits between Hardware and Applications. It got blamed but its not the cause

Hopefully I've done this correctly.

https://www.dropbox.com/s/bgkylkmkkd9ur0p/Deodorant Operator's DMPS.zip?dl=0

 

[Colif]

i will ask a friend to convert them for me

 

[gardenman]

Hi, I ran the dump files through the debugger and got the following information: https://jsfiddle.net/1brpd09y/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.

Spoiler: Dump File Results

File information:	072121-8781-01.dmp (Jul 21 2021 - 18:14:33)
Bugcheck:	DRIVER_IRQL_NOT_LESS_OR_EQUAL (D1)
Probably caused by:	memory_corruption (Process: svchost.exe)
Uptime:	0 Day(s), 0 Hour(s), 00 Min(s), and 22 Sec(s)

File information:	071721-9593-01.dmp (Jul 17 2021 - 16:18:36)
Bugcheck:	DRIVER_IRQL_NOT_LESS_OR_EQUAL (D1)
Probably caused by:	memory_corruption (Process: OVRServer_x64.exe)
Uptime:	0 Day(s), 0 Hour(s), 01 Min(s), and 39 Sec(s)

File information:	071621-13171-01.dmp (Jul 16 2021 - 12:24:04)
Bugcheck:	SYSTEM_SERVICE_EXCEPTION (3B)
Probably caused by:	memory_corruption (Process: WmiPrvSE.exe)
Uptime:	1 Day(s), 22 Hour(s), 42 Min(s), and 24 Sec(s)

File information:	070621-20312-01.dmp (Jul 6 2021 - 18:05:39)
Bugcheck:	UNEXPECTED_KERNEL_MODE_TRAP (7F)
Probably caused by:	memory_corruption (Process: payday2_win32_release.exe)
Uptime:	1 Day(s), 0 Hour(s), 01 Min(s), and 58 Sec(s)

File information:	070521-29515-01.dmp (Jul 5 2021 - 18:03:12)
Bugcheck:	KMODE_EXCEPTION_NOT_HANDLED (1E)
Probably caused by:	memory_corruption (Process: msedge.exe)
Uptime:	5 Day(s), 2 Hour(s), 15 Min(s), and 56 Sec(s)

Comment: The overclocking driver "RTCore64.sys" was found on your system. (MSI Afterburner)

Possible Motherboard page: https://www.asus.com/Motherboards-Components/Motherboards/TUF-Gaming/TUF-B450M-PRO-GAMING/
There is a BIOS update available for your system. You are using version 2409 and the latest is version 3202. Wait for additional information before deciding to update or not. Important: Verify that I have linked to the correct motherboard. Updating your BIOS can be risky. Never try it when you might lose power (lightning storms, recent power outages, etc).

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

 

[Deodorant Operator]

Thank you for the information. I was pretty certain it wasn't to do with memory, since I ran multiple checks, but there's always a chance of me being wrong. Either way, thank you for the help. I will continue to fix this problem.

 

[gardenman]

Colif will go over the results that I posted and reply later.

Also, just because it says "memory_corruption ", that doesn't necessarily mean that you have a RAM issue.

 

[Deodorant Operator]

Colif will go over the results that I posted and reply later.

Also, just because it says "memory_corruption ", that doesn't necessarily mean that you have a RAM issue.

Alright, thank you. I also have downloaded the drivers available for my motherboard, as I was not aware of them until now.

 

[Colif]

We had terrible weather this weekend, sorry for being slow to answer

crash 4 was GPU drivers - try running DDU in safe mode and reinstall AMD drivers - https://forums.tomshardware.com/faq...n-install-of-your-video-card-drivers.2402269/
its the only obvious one. Although another the victim was Oculus so it could have been caused by GPU as well.

What ram are you using?
never heard of J&A Information Inc?

16384MB

2666MHz

J&A Information Inc

Unknown

what is this for?

Jul 10 2014

VKbms.sys

HID mini driver for USB Fx2 Device driver

Anything prior to July 2015 might not be a win 10 driver.

 

[Deodorant Operator]

We had terrible weather this weekend, sorry for being slow to answer

crash 4 was GPU drivers - try running DDU in safe mode and reinstall AMD drivers - https://forums.tomshardware.com/faq...n-install-of-your-video-card-drivers.2402269/
its the only obvious one. Although another the victim was Oculus so it could have been caused by GPU as well.

What ram are you using?
never heard of J&A Information Inc?

16384MB

2666MHz

J&A Information Inc

Unknown

what is this for?

Jul 10 2014

VKbms.sys

HID mini driver for USB Fx2 Device driver

Anything prior to July 2015 might not be a win 10 driver.

Sorry, I saw this message a few days ago, but wasn't logged in. Not sure about the RAM, because I had someone else build it for me. But, after diving into my files looking for the VKbms.sys driver, I found it, and deleted it. Ever since, I haven't bluescreened once. So, for now, I'm gonna say it worked, and thank you for the help! It is much appreciated, and will help me out BIG time in the long run. Have a good day!