ntoskrnl.exe :: Hardware and Operating Systems

HellishSlayer Sep 10, 2017 @ 6:04am

Occasional BSoD

Every once in a while my PC will get the BSoD at startup and then restart but after it restarts its completely fine. I just built this PC about 2 months ago and have had this problem for about a month but its very infrequent. Now the only thing I can think it MIGHT be was that I got a new wireless internet card and dropped it before putting in so maybe it's broken and conflicting with the PC. Is there a way to check if any of my hardware is faulty?

PC Specs:
CPU: i7 7700k
Mobo: Asus Prime Z270-A
GPU: EVGA GTX 1070 FTW
RAM: Corsair Vengeance LPX 16GB (2x8GB) DDR4 DRAM 3200MHz
PSU: EVGA 650W G2
Wireless Card: TP-Link AC1900

#1

rotNdude Sep 10, 2017 @ 11:12am

The first thing you need to look at is the minidumps that Windows creates. http://www.nirsoft.net/utils/blue_screen_view.html

#2

Bad 💀 Motha Sep 11, 2017 @ 3:44pm

^ This

As far as the Wireless Card; put it into a Slot that doesn't conflict.
Look in the Manual for where it shows what Slot shares with what Onboard devices/resources.

Make sure your RAM is setup correctly, meaning XMP Profile is applied.

But yea you'll have to look up the errors and go from there. Everything gets logged into Event Viewer.

#3

#packwatch bozo-killer Sep 19, 2017 @ 4:46am

Originally posted by HellishSlayer:
I keep randomly and infrequently getting the BSoD. Apparently 'ntoskrnl.exe' is the casue of it. Can anybody give some insight as to what that means?

format is the only way

#4

[wan-clan.org] Gordy Freeman Sep 19, 2017 @ 6:12am

It means the hardware or driver that is executing the NT OS Kernel is faulty.

#5

HellishSlayer Sep 19, 2017 @ 7:49am

Originally posted by Gordy Freeman (Hardware Girl):
It means the hardware or driver that is executing the NT OS Kernel is faulty.

How do I find out which hardware it is?

#6

FluffyPinkDecoyBunny Sep 19, 2017 @ 8:16am

A few things you can try:

1) If you're using Windows 7 or later, you could try running a:

sfc /scannow

from the command prompt. If you're unsure of how to do this, google is your friend. This way if it is strictly an issue with Windows system files, it may correct the problem.

2) If you have installed any new hardware or driver since the BSODs have started, then revert the change (remove the hardware and uninstall the driver or roll back to a previous driver) to see if this corrects the issue.

3) If you're using a HDD you could try running a:

chkdsk /f /r

from the command propmpt. If you're unsure of how to do this, google is your friend. It could be possible you have bad sectors on your HDD that windows can't properly read necessary files from. This may fix any bad sectors or simply exclude them from being used on the HDD.

If the above options haven't fixed it for you, then a format and re-install of the Windows OS may be in order. If you do go this route, please be sure to back up any important data to a spare hard drive or burn it to a CD/DVD or copy to a flash drive....something to make sure you have your important files on hand.

#7

Sticky Honeybuns Sep 19, 2017 @ 9:15am

That BSoD is almost always associated with GPU driver or memory. Have you updated your GPU driver lately? Only update drivers if there is something wrong. Don't update drivers just because a new one is available.

Last edited by Sticky Honeybuns; Sep 19, 2017 @ 9:16am

#8

!xS Sep 19, 2017 @ 9:14pm

hi there fellows,
dear TC, open up the event viewer and if you're not sure what the given reason means or how te fix it feel free to contact us again ;)

btw if you don't know where to find event viewer then do this:

press and hold the win button on your keyboard plus the R button, the run dialog should be shown where you type the following in and confirm with enter or by the OK button...:

LOOOIL CAN'T REMEMBER brb MUST TAKE A PEEK ON ON POST HISTORY... MMC.eXe EventVwr.MSC

cheers
- !xS -
** updated: MMC.eXe EventVwr.MSC

Last edited by !xS; Sep 19, 2017 @ 9:25pm

#9

HellishSlayer Sep 26, 2017 @ 1:14pm

Occasional BSoD since I built my PC...

I get the BSoD almost every time I start my PC after it being off for a while but after I get it, the computer works fine. It's very occasional. This is the error message I get on Blue Screen View:

092617-13359-01.dmp 9/26/2017 3:15:17 PM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 ffffb000`f9636000 00000000`00000000 fffff80d`e51d195c 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+16c580 x64 ntoskrnl.exe+16c580 C:\Windows\Minidump\092617-13359-01.dmp 8 15 15063 698,388 9/26/2017 3:16:02 PM

PC Build:
CPU: i7 7700k
MOTHERBOARD: ASUS PRIME Z270-A
RAM: Corsair Vengeance LPX 16GB (2x8GB) DDR4 DRAM 3200MHz
GPU: GTX 1070 FTW
OS: Win 10
SSD: Crucial MX300

#10

Omega Sep 26, 2017 @ 1:19pm

Did you do a clean install of Windows or did you move the drive over from your old PC?

Have you installed all your drivers?

#11

HellishSlayer Sep 26, 2017 @ 1:20pm

Originally posted by Omega:
Did you do a clean install of Windows or did you move the drive over from your old PC?

Have you installed all your drivers?

I moved the drive over from my old PC but I did a clean install. I'm almost certain I installed all drivers

Originally posted by rotNdude:
The first thing you need to look at is the minidumps that Windows creates. http://www.nirsoft.net/utils/blue_screen_view.html

092617-13359-01.dmp 9/26/2017 3:15:17 PM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 ffffb000`f9636000 00000000`00000000 fffff80d`e51d195c 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+16c580 x64 ntoskrnl.exe+16c580 C:\Windows\Minidump\092617-13359-01.dmp 8 15 15063 698,388 9/26/2017 3:16:02 PM

I don't think it's the card as this has actually been happening since I built the PC.

Originally posted by ╶ !xS ╴:
hi there fellows,
dear TC, open up the event viewer and if you're not sure what the given reason means or how te fix it feel free to contact us again ;)

btw if you don't know where to find event viewer then do this:

press and hold the win button on your keyboard plus the R button, the run dialog should be shown where you type the following in and confirm with enter or by the OK button...:
LOOOIL CAN'T REMEMBER brb MUST TAKE A PEEK ON ON POST HISTORY... MMC.eXe EventVwr.MSC

cheers
- !xS -
** updated: MMC.eXe EventVwr.MSC

092617-13359-01.dmp 9/26/2017 3:15:17 PM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 ffffb000`f9636000 00000000`00000000 fffff80d`e51d195c 00000000`00000000 ntoskrnl.exe ntoskrnl.exe+16c580 x64 ntoskrnl.exe+16c580 C:\Windows\Minidump\092617-13359-01.dmp 8 15 15063 698,388 9/26/2017 3:16:02 PM

This is what I'm getting on Blue Sreen View

Last edited by rotNdude; Sep 28, 2017 @ 10:32am

#12

Bad 💀 Motha Sep 26, 2017 @ 1:37pm

Boot into Safe Mode; press Winkey+X; click Command Prompt (Admin)
type SFC /SCANNOW press enter
let it run it's course, if that checks out ok...
type CHKDSK /F /R press enter

#13

Squirrell Sep 26, 2017 @ 1:41pm

A page fault is a memory error. You might want to try reseating the memory and/or trying different settings. Could be an overclock as well.

Read this and similar posts about ntoskrnl.exe as well -

https://www.drivereasy.com/knowledge/ntoskrnl-exe-bsod-bluse-screen-of-death-error-in-windows-7/

#14

Omega Sep 26, 2017 @ 1:52pm

^^ Might indeed be smart to make sure XMP is correctly enabled and check the RAM for errors with Memtest86.

Lots of Windows BSODs are blamed on ntoskrnl.exe. ntoskrnl is part of the Windows kernel and is responsible for quite a things of stuff like hardware virtualization, process management and memory management. So it's impossible to tell you exactly what is causing the issue with ntoskrnl as the only lead.

#15

Report this post