Getting so many ntoskrnl.exe BSOD (PLEASE HELP)

[ahmedennab704]

Hello, I keep getting a bsod error related to ntoskrnl.exe [strike]every 2 days, if not daily[/strike] I am getting it daily, which seems very very often. running on widows 10 pro
I have tried reinstalling windows 4 times, same issue.
I have my cpu overclocked from 3.0 ghz to 3.7 ghz but it should be stable since I did a stress test for like 10 hours?
I tried using driver verifier but I just got into a infinite loop of bsods with "driver_fail_error (something near this)"
Also tried running memtest86 twice, no errors.
I have tried everything, can anyone please be kind and help me?
Thanks

P.S, I just got bsod when writing this thread....

WhoCrashed dump: https://pastebin.com/BkSk4Ngj

PC specs:

Operating System
Windows 10 Pro 64-bit
CPU
AMD Ryzen 7 1700 43 °C
Summit Ridge 14nm Technology
RAM
16.0GB Dual-Channel Unknown @ 1599MHz (16-16-16-36)
Motherboard
Micro-Star International Co. Ltd X370 GAMING PRO CARBON (MS-7A32) (AM4) 39 °C
Graphics
LG Ultra HD (3840x2160@60Hz)
4095MB NVIDIA GeForce GTX 1080 (MSI) 55 °C
Storage
931GB Seagate ST1000DM010-2EP102 (SATA) 31 °C
931GB Seagate ST31000528AS (SATA) 30 °C
232GB Samsung SSD 960 EVO 250GB (Unknown)
Optical Drives
No optical disk drives detected
Audio
Realtek High Definition Audio

UPDATE: I removed my CPU overclock and don't get as much as bsods lately, but I still get it every 3-4 days.
Same error log

 

[Colif]

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

can you go to C:\WINDOWS\Minidump and copy the minidump files to desktop. Then upload the copies from desktop to a file sharing web site and share the links here, I will get someone to look at the errors for you.

the errors appear to only be driver errors, we should be able to figure them out.

 

[ahmedennab704]

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

can you go to C:\WINDOWS\Minidump and copy the minidump files to desktop. Then upload the copies from desktop to a file sharing web site and share the links here, I will get someone to look at the errors for you.

the errors appear to only be driver errors, we should be able to figure them out.

Here is the dump file https://drive.google.com/open?id=12ytxgwssh4Vk1UltqtWZg8ipqhQj6FM9 & https://drive.google.com/open?id=1FeUaJfJn4WNFIp82T-GQQBLrMKGGdAdt
Thanks

 

[gardenman]

Hi, I ran the dump files through the debugger and got the following information: https://pste.eu/p/HkFG.html

File: 052518-7093-01.dmp (May 25 2018 - 03:29:28)
BugCheck: [PAGE_FAULT_IN_NONPAGED_AREA (50)]
Probably caused by: memory_corruption (Process: audiodg.exe)
Uptime: 0 Day(s), 1 Hour(s), 01 Min(s), and 34 Sec(s)

File: 052418-7109-01.dmp (May 24 2018 - 15:15:51)
BugCheck: [SYSTEM_SERVICE_EXCEPTION (3B)]
Probably caused by: memory_corruption (Process: svchost.exe)
Uptime: 0 Day(s), 0 Hour(s), 53 Min(s), and 54 Sec(s)

Remove all overclocks.
The overclocking driver "NTIOLib_X64.sys" was found on your system (MSI Afterburner). The NTIOLib_X64.sys file may be installed with other software such as MSI Live Update and that is OK.
The overclocking driver "RTCore64.sys" was found on your system (MSI Afterburner).

Motherboard: https://www.msi.com/Motherboard/X370-GAMING-PRO-CARBON.html

I can't help you with this. Wait for additional replies. Good luck.

 

[ahmedennab704]

Hi, I ran the dump files through the debugger and got the following information: https://pste.eu/p/HkFG.html

File: 052518-7093-01.dmp (May 25 2018 - 03:29:28)
BugCheck: [PAGE_FAULT_IN_NONPAGED_AREA (50)]
Probably caused by: memory_corruption (Process: audiodg.exe)
Uptime: 0 Day(s), 1 Hour(s), 01 Min(s), and 34 Sec(s)

File: 052418-7109-01.dmp (May 24 2018 - 15:15:51)
BugCheck: [SYSTEM_SERVICE_EXCEPTION (3B)]
Probably caused by: memory_corruption (Process: svchost.exe)
Uptime: 0 Day(s), 0 Hour(s), 53 Min(s), and 54 Sec(s)

Remove all overclocks.
The overclocking driver "NTIOLib_X64.sys" was found on your system (MSI Afterburner). The NTIOLib_X64.sys file may be installed with other software such as MSI Live Update and that is OK.
The overclocking driver "RTCore64.sys" was found on your system (MSI Afterburner).

Motherboard: https://www.msi.com/Motherboard/X370-GAMING-PRO-CARBON.html

I can't help you with this. Wait for additional replies. Good luck.

I know you told me to wait for replies, but, if I uninstall both MSI Live and Afterburner I will no longer get those annoying bsods?

 

[Colif]

try updating the corsair link software, anything older than 2015 is too old for windows 10 and both of these are part of Corsair Link

Jul 15 2010 SiLib.sys USBXpress SDK http://www.silabs.com/
Jul 15 2010 SiUSBXp.sys USBXpress SDK http://www.silabs.com/

the link in quotes doesn't lead to corsair, I have just seen these 2 linked to a USB attachment on the cooler itself

I2cHkBurn.sys - FINTEK FitGpBus Device driver (Feature Integration Technology)

think its part of MSI Gaming app? I only mention it as file is from 2014 and too old to be a Win 10 file.

Audiodg is Windows Audio Device Graph Isolation, part of the OS. You appear to have the latest Realtek sound drivers

 

[ahmedennab704]

try updating the corsair link software, anything older than 2015 is too old for windows 10 and both of these are part of Corsair Link

Jul 15 2010 SiLib.sys USBXpress SDK http://www.silabs.com/
Jul 15 2010 SiUSBXp.sys USBXpress SDK http://www.silabs.com/

the link in quotes doesn't lead to corsair, I have just seen these 2 linked to a USB attachment on the cooler itself

I2cHkBurn.sys - FINTEK FitGpBus Device driver (Feature Integration Technology)

think its part of MSI Gaming app? I only mention it as file is from 2014 and too old to be a Win 10 file.

Audiodg is Windows Audio Device Graph Isolation, part of the OS. You appear to have the latest Realtek sound drivers

I'm running the latest corsair link?
And I just updated MSI Gaming App using MSI Liveupdate.

but if I uninstall all of these MSI apps will I no longer get BSODS? It's ok by me if I uninstall them

 

[Colif]

the errors didn't show exact cause, all I did was identified really old software that is more likely to cause the errors.

Corsair may still need to update their software then, I know that the same drivers showed up last year as problems.

so remove MSI software and see if you get any BSOD. If you do, upload the dumps and we will keep looking, all the other drivers look new so I don't suspect them as much.

 

[ahmedennab704]

the errors didn't show exact cause, all I did was identified really old software that is more likely to cause the errors.

Corsair may still need to update their software then, I know that the same drivers showed up last year as problems.

so remove MSI software and see if you get any BSOD. If you do, upload the dumps and we will keep looking, all the other drivers look new so I don't suspect them as much.

Ok I just unsintalled everything, I hope this will fix the issue.
Thank you for your time, waiting on that bsod to appear (hopefully never)

 

[ahmedennab704]

the errors didn't show exact cause, all I did was identified really old software that is more likely to cause the errors.

Corsair may still need to update their software then, I know that the same drivers showed up last year as problems.

so remove MSI software and see if you get any BSOD. If you do, upload the dumps and we will keep looking, all the other drivers look new so I don't suspect them as much.

There's a new bsod in the field, should I make another thread for it or what? Anyhow, here's the dump file https://drive.google.com/open?id=1jKNjmdu3jA3wPkewo50N08BVnct2xxkP

 

[gardenman]

Keep all of the BSODs and dumps here in this thread. I ran the dump file through the debugger and got the following information: https://pste.eu/p/cvo1.html

File: 052718-12578-01.dmp (May 27 2018 - 11:43:53)
BugCheck: [KMODE_EXCEPTION_NOT_HANDLED (1E)]
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
Probably caused by: dxgmms2.sys (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 08 Min(s), and 32 Sec(s)

The overclocking driver "NTIOLib_X64.sys" was found on your system. (MSI Afterburner)

This time your Nvidia Graphics card driver crashed. If you haven't already, considering removing it with DDU (while in safe mode) then re-installing the latest version. Full instructions can be found here: http://www.tomshardware.com/faq/id-2767677/perform-clean-install-video-card-drivers.html

I can't help you with this. Wait for additional replies. Good luck.

 

[Colif]

You appear to have the latest Nvidia drivers so I would run DDU as suggested and then instead of getting drivers from Nvidia, run windows update and use the Nvidia drivers Microsoft still have. Only difference is age, MS drivers seem to be more stable than the latest from Nvidia themselves.

 

[ahmedennab704]

You appear to have the latest Nvidia drivers so I would run DDU as suggested and then instead of getting drivers from Nvidia, run windows update and use the Nvidia drivers Microsoft still have. Only difference is age, MS drivers seem to be more stable than the latest from Nvidia themselves.

Yeah it did make sense as I got logged out when updating the nividea driver the other day, anyhow, did all that
I just got two new BSODS, one is related to my ethernet network adapter, in processes of updating it (but I'm on latest version?)
Other one is same as original :/
Here are the dumps:
https://drive.google.com/open?id=1JAKaObvHWkHAdSddKnA7TZ38PNwC0n9B
https://drive.google.com/open?id=1k_68KCyQz3CulzUgqN92oO0jd73caKMm

 

[gardenman]

I ran the 2 dump files through the debugger and got the following information: https://pste.eu/p/2RpD.html

File: 053018-6375-01.dmp (May 29 2018 - 16:05:50)
BugCheck: [SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007E)]
*** WARNING: Unable to verify timestamp for e1r65x64.sys
Probably caused by: e1r65x64.sys (Process: System)
Uptime: 0 Day(s), 4 Hour(s), 17 Min(s), and 49 Sec(s)

File: 053018-6265-01.dmp (May 29 2018 - 16:11:35)
BugCheck: [KMODE_EXCEPTION_NOT_HANDLED (1E)]
Probably caused by: partmgr.sys (Process: MsMpEng.exe)
Uptime: 0 Day(s), 0 Hour(s), 04 Min(s), and 58 Sec(s)

I can't help you with this. Wait for additional replies. Good luck.

 

[Colif]

MsMpEng.exe = Windows defender

Which driver version is the update for the Intel driver? where did you get it from?? The newest version on the MSI site for your motherboard is 22.9.16.0 dated 29th Dec 2017 whereas the newest version on the Intel site is version 23.1 dated 21 Feb 2018

Check in device manager and see which version is installed there, its possible Win 10 has updated the drivers to a point past the MSI site has.

What bios version are you on? Its odd for gardenmans file to not show PC details, this can happen if the bios is old. Latest BIOS is Version 7A32v1G dated th May 2018 - only update BIOS if problems continue after you update Ethernet.

 

[ahmedennab704]

MsMpEng.exe = Windows defender

Which driver version is the update for the Intel driver? where did you get it from?? The newest version on the MSI site for your motherboard is 22.9.16.0 dated 29th Dec 2017 whereas the newest version on the Intel site is version 23.1 dated 21 Feb 2018

Check in device manager and see which version is installed there, its possible Win 10 has updated the drivers to a point past the MSI site has.

What bios version are you on? Its odd for gardenmans file to not show PC details, this can happen if the bios is old. Latest BIOS is Version 7A32v1G dated th May 2018 - only update BIOS if problems continue after you update Ethernet.

I thought I updated it from intel site, but it shows im on version 12.15.184.0? Anyhow, I just updating it from MSI site but the program is telling me I already have a newer version. Should I just uninstall it and install the version from the MSI site?

And I'm running on latest BIOS, 7A32v1G

 

[Colif]

I think the 23.1 in my post is a pack of drivers - https://downloadcenter.intel.com/download/22283/Intel-Ethernet-Adapter-Complete-Driver-Pack

12.15.184.0 appear to be from 3 Nov 2017, and included in Intel Network Connections Software Version 22.9 WHQL

I wouldn't install the drivers from MSI, try the ones from intel instead as its likely windows has newer driver version than is on the MSI site.

 

[ahmedennab704]

I think the 23.1 in my post is a pack of drivers - https://downloadcenter.intel.com/download/22283/Intel-Ethernet-Adapter-Complete-Driver-Pack

12.15.184.0 appear to be from 3 Nov 2017, and included in Intel Network Connections Software Version 22.9 WHQL

I wouldn't install the drivers from MSI, try the ones from intel instead as its likely windows has newer driver version than is on the MSI site.

Installed them from intel, still getting few bsods now, newest one is here:
https://drive.google.com/open?id=1im4nr-mzkXwc-9k2e1DghFzv02SnKpL8
Also, I'm getting now more freezes than bsods, is there a dump file for freezes?

 

[Grugbug]

What is the make/ model of your PSU?
A flaky PSU can cause all sorts of errors.

I'd also run memtest overnight.

 

[gardenman]

I ran the dump file through the debugger and got the following information: https://pste.eu/p/M2su.html

File: 060418-6328-01.dmp (Jun 4 2018 - 10:18:24)
BugCheck: [SYSTEM_SERVICE_EXCEPTION (3B)]
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Probably caused by: Unknown_Image (Process: https://www.google.com/search?q=)
Uptime: 0 Day(s), 0 Hour(s), 09 Min(s), and 38 Sec(s)

Either my debugger is having problems with dump files or the latest update is messing with things because it's unusual to see "Unknown_Module" and we've seen it a few times in the last few days.

I can't help you with this. Wait for additional replies. Good luck.

 

[ahmedennab704]

What is the make/ model of your PSU?
A flaky PSU can cause all sorts of errors.

I'd also run memtest overnight.

http://www.xfxforce.com/en-us/products/xtr-series-gold-full-modular/xtr-series-750w-psu-p1-750b-befx
Yeah I will run it. But most of the freezes I'm getting are like screen freezes, if I play a song in the background and get frozen, I can still hear the music but can't move my mouse/keyboard and screen wont refresh. And other freezes are just normal freeze, screen + audio + input

[strike]Ehh forgot to run memtest, I will run it after like 15 hours from now[/strike]
Here's the test report: https://pste.eu/p/5Vnz.html

 

[ahmedennab704]

Also not sure if this is a overclock or not, but my ram is 3200mhz, the motherboard has it stock at 2133 (or 2400, not sure) so I had to enable XMP 2 profile, as it matches my ram at 3200MHZ 16-16-16-36

 

[ahmedennab704]

I'm not getting as much as BSOD as before, but I just got another one:
https://drive.google.com/open?id=1IakfhlOT3qxsfKJ5Le8U-Julv1NhN6DR

 

[Colif]

XMP is a sort of overclock, but just on the ram. I think some boards might speed up CPU as well when you run in XMP but your CPU speed is only 3ghz so it doesn't seem to do it on your board.

I expect fact the last dump file Gardenman created was a little messed up explains why the bios info was as well. I 1st saw the unknown module thing on whocrashed and it appears to be spreading to win dbg. Only answer I found for that is update symbols file, but thats just general advice for Gardenman.

lets see what next dump you just posted reveals.

 

[gardenman]

I ran the dump file through the debugger and got the following information: https://pste.eu/p/NTPW.html

File: 060718-9328-01.dmp (Jun 7 2018 - 04:29:25)
BugCheck: [KMODE_EXCEPTION_NOT_HANDLED (1E)]
Probably caused by: memory_corruption (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 15 Min(s), and 04 Sec(s)

I can't help you with this. Wait for additional replies. Good luck.

Edit: To Colif, there is no "symbols file" to update. Symbols are just driver files (*.sys files). There can be different versions of symbols and each is hosted in their own folder. For example, if I read 3 different dumps from 3 different PCs, each can have a different version of the dxgmms1.sys driver. Here's is how the debugger's symbols cache is saved on my PC. https://s15.postimg.cc/fx4n4ascb/symbols.jpg As you can see, there are 3 different dxgmms1.sys files already cached. If the debugger finds a new one referenced in a dump file that hasn't been seen before, it will be downloaded from the server and added to the folder. This is automatically done each time I run a dump file through. Only new symbols are downloaded if they don't already exist. The C:\ProgramData\dbg\sym folder is just a cache, like temporary internet files. If I delete it, it will be re-created with "symbols" on the next dump that I read. This doesn't explain the "unknown module" thing though. I don't know what is going on with that. I will clear the symbols cache now and we'll see if that helps.

Edit 2: Updated the pste.eu page. I guess the site owner cleared all of his old pages.