[SOLVED] BSOD every day due to ntoskrnl.exe

[purlox]

Practically every day I get a BSOD on my PC. The time when it happens and the error messages vary a lot, so not sure what's causing it.

Seems like there might also be some memory corruption going on, because few minutes before the BSOD happens programs start to crash or the data in my terminal starts to get corrupted, etc. I tried checking my RAM before booting up Windows 10, but it never finds anything wrong with it. I also tried checking my HDDs, but that also didn't come up with any errors.

Here is the minidump from the latest crash: https://drive.google.com/open?id=15IOoyZgBop5-vOOln2UVFxRPbFrxcski

 

[Colif]

have you checked you have latest drivers for PC?

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. If it crashes, windows has no choice but to follow

i will get someone to convert dump file for me.

 

[purlox]

have you checked you have latest drivers for PC?

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. If it crashes, windows has no choice but to follow

i will get someone to convert dump file for me.

Thanks, I just updated my drivers. Hopefully, all of them should be up to date now.

 

[gardenman]

Hi, hopefully the driver updates help. If not, I ran the dump file through the debugger and got the following results: https://pste.eu/p/kPxz.html

File: 012319-122609-01.dmp (Jan 23 2019 - 02:49:12)
BugCheck: [APC_INDEX_MISMATCH (1)]
Probably caused by: ntkrnlmp.exe (Process: MsMpEng.exe)
Uptime: 0 Day(s), 0 Hour(s), 26 Min(s), and 59 Sec(s)

Motherboard: https://www.msi.com/Motherboard/B250M-BAZOOKA.html
I think you are using the first BIOS version that was available for your system. If so, there are updates. Wait for additional information before deciding to update or not. Also verify the information before attempting to update. Updating your BIOS can be risky. Never try it when you might lose power (lightning storms, recent power outages, etc).

I can't help you with this. Someone else will post with more information soon. Please wait for more answers. Good luck.

 

[Colif]

process that crashed is part of windows defender, was one of the drivers you updated the LAN drivers as that would be what I would suspect is cause?

Another option is run anti virus scan or Malwarebytes

 

[purlox]

Got another crash after updating drivers. Minidump is here: https://drive.google.com/open?id=16ms9PU-wO2NPbz2qaRmRedqs4cAB_qBM

After the crash, I scanned my PC with Malwarebytes, which found 2 instances of malware that I got rid of.

Also checked my motherboard and you were close. It's actually https://www.msi.com/Motherboard/B250M-PRO-VDH . I don't think I have updated the driver from it yet. Should I do that?

 

[gardenman]

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

File: 012419-85656-01.dmp (Jan 24 2019 - 10:52:16)
BugCheck: [MEMORY_MANAGEMENT (1A)]
Probably caused by: memory_corruption (Process: firefox.exe)
Uptime: 0 Day(s), 0 Hour(s), 06 Min(s), and 13 Sec(s)

I can't help you with this. Someone else will post with more information soon. Please wait for more answers. Good luck.

 

[Colif]

Run MSI live update 6, if its not installed it should be on the utility tab of MSI web site under support

It will check PC and make sure you have latest LAN driver.

 

[purlox]

Run MSI live update 6, if its not installed it should be on the utility tab of MSI web site under support

It will check PC and make sure you have latest LAN driver.

Thank you.

I just downloaded MSI live update 6 and downloaded all the drivers it offered me to update. Unfortunately, few minutes after I installed them and restarted my PC, it decided to crash again. So here is the new minidump: https://drive.google.com/open?id=1htRkGg1VcFLqACsfJ0G_-SstArLPVz92

 

[Colif]

i had been guessing it was the LAN drivers based on the 2 programs that crashed. Your current LAN driver was from this year so maybe I been looking in wrong place.

any idea what this is part of?

Nov 15 2010 - ioFakMap.sys - KYE System Corp. IO Tablet Fake driver
Jul 22 2015 - ioFakDrv.sys - KYE System Corp. IO Tablet Fake driver
Dec 20 2017 - gKbdfltr.sys - KYE Systems Corp. driver

perhaps your mouse drivers? See if any newer ones.

Try updating bios from the release version to latest as your version of Intel Management Engine Interface matches a newer bios than what is installed. It may not fix problem but it adds more stability to system. There have been 7 more BIOS since the one you are on

This video shows you how to do it - [video="https://www.youtube.com/watch?v=LRyFMf0D9Lc"][/video]

 

[gardenman]

The latest dump file: https://pste.eu/p/IAV2.html

File: 012519-103046-01.dmp (Jan 25 2019 - 04:55:22)
BugCheck: [KERNEL_DATA_INPAGE_ERROR (7A)]
Probably caused by: memory_corruption (Process: conhost.exe)
Uptime: 0 Day(s), 0 Hour(s), 09 Min(s), and 40 Sec(s)

I can't help you with this. Someone else will post with more information soon. Please wait for more answers. Good luck.

 

[purlox]

I think those drivers might be part of my keyboard drivers. The keyboard is from Genius, who is in turn owned by KYE system corp. After looking at the driver again, I noticed a newer version of it was available, so I updated it.

I also downloaded the latest BIOS update and got it installed successfully.

Hopefully this should fix things. Will post again if I get another crash.

 

[purlox]

Not sure if it helped. I just got another crash from ntoskrnl.exe today.

Minidump: https://drive.google.com/open?id=11W3CD6hcZYJampdv4UvI-6r_aWMxdEeU

 

[Colif]

enough guessing... again... time to make PC tell us what problem is.

Before running this,
1) search for “Create a restore point” and create a restore point
2) Create a bootable USB of Win 10 installer to use as a boot drive. download the Windows 10 media creation tool and use it to make a win 10 installer on USB

try running driver verifer, just read the instructions carefully. It is part of win 10 designed to find misbehaving drivers. It will cause BSOD, that is its job since it tests drivers.
Once it bsod, upload the minidump file and we see what it shows us.

Steps 1 & 2 are just precautions as sometimes driver verifer can put you in a boot loop. If this happen, follow these steps to get out of it
change boot order so USB is first, hdd second
boot from installer
on screen after languages, choose repair this pc, not install.
choose troubleshoot
choose advanced
choose system restore and roll system back to restore point created in step 1. PC should boot normally.

 

[purlox]

Hello, I run the driver verifier and it finally BSODed few moments ago. The minidump is here: https://drive.google.com/open?id=1JQHdxAbaxnC6utIKTANv0RYjArzchLu1

 

[gardenman]

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

File: 012719-90578-01.dmp (Jan 27 2019 - 10:03:02)
BugCheck: [FAULTY_HARDWARE_CORRUPTED_PAGE (12B)]
Probably caused by: memory_corruption (Process: MemCompression)
Uptime: 0 Day(s), 20 Hour(s), 26 Min(s), and 11 Sec(s)

File: 012619-42718-01.dmp (Jan 26 2019 - 05:56:16)
BugCheck: [FAULTY_HARDWARE_CORRUPTED_PAGE (12B)]
Probably caused by: memory_corruption (Process: MemCompression)
Uptime: 0 Day(s), 2 Hour(s), 05 Min(s), and 08 Sec(s)

I don't think Verifier caught a crash. It usually gives errors such as DRIVER_VERIFIER_DETECTED_VIOLATION.

When you checked your RAM, did you do it with Windows Memory Diagnostic or Memtest86? Memtest86 is more reliable. Since you have 2 sticks of RAM, I would open the case and remove one and run Memtest86 on each RAM stick one at a time for at least 8 passes. This will take a long time. You'll have to download Memtest86 and put it on a bootable flash drive or disc. https://www.memtest86.com/download.htm Another simple way of testing would be to remove 1 stick of RAM and run your PC with only 1 at a time for the next few days. See if either one is causing the problems.

 

[Colif]

only error count you want in memtest is 0, anything higher is too many. Remove/replace ram sticks with errors...

slaps self for looking at file names and not error codes. I would have suggested memtest earlier.

 

[purlox]

Thanks. I ran memtest on both my RAM sticks separately and found the faulty one, so I'll be replacing it.