Windows 10: ntoskrnl.exe causing crashes BSOD

Hi, MS Community there.


This is Henry.

I have had this BSOD issue since 3 weeks ago.

Today I managed to use Verifier to get 2 MEMORY.DUMP, with 954MB, and 1.64GB.


and a few mini dmp.


I am using HP laptop AMD 2700 CPU.


It is still difficult to upload the huge file into Onedrive.


Is there any online tools I can diagnostic where is the driver issue, with these 2 huge DMP ?


If not, I may need help help from community to diagnostic the files.


Another issue, I noticed, when I scroll fast in Linkedin, and Netflix. There are frequently black screen for a short while, and back to normal after a few seconds. Chrome , current 84, this happen for many versions


This never happen to any other website. Only Netflix and Linkedin. Really make me wonder what was going on behind it.



Thank you so much.

Cheers

Henry

:)

 

Suddenly - BSOD! x124, ntoskrnl.exe

I'm suddenly getting BSODs. I never see them happen, I always go to my computer and Windows oh so prolifically informs me of a crash. I don't know what triggers it, I'm not there... all I know is it likes to randomly crash. I do run BOINC full-time on the system so there's plenty of load on the CPU and whatnot, but I have before and never had issues until just lately.

(( One major pet peeve about Windows 8... previous versions would give you some info, now I get these *Frown ... ))

Bluescreenview tells me that it's the classic x124 code, and its caused by ntoskrnl.exe. At first I thought that it might be caused by my sound card, a Creative X-Fi Titanium Fatal1ty Pro. The reason I thought this is because I never really had any BSOD before I put this card in, where before I used an Asus Xonar DG. I initially blamed Creative's drivers or something along those lines, but since it says the kernel is crashing, I'm thinking maybe Creative isn't at fault here with shoddy drivers. Is my OC suddenly unstable? One line of thought that suggests some form of hardware instability here is that the Asus Xonar DG was a PCI card, and the X-Fi I am using now is PCI-E x1. Maybe having my sound card on the PCI-E bus is stressing out the system more than it was before causing BSOD?

 

BSOD Caused By Address : ntoskrnl.exe+14e7c0

My PC is constantly crashing with a BSOD message. The message seems to very regularly but the caused by driver is always the same listed as "ntoskrnl.exe".

I've replaced the RAM and the video card as well as reinstalled the NVIDIA video drivers. Problem started around Nov. 2016 and has progressively become more frequent. Disk is regularly at 100% usage also.

I would happily upload the dump file but I do not have access to box. Any advice would be appreciated.

Thanks!

==================================================

Dump File : 050617-41406-01.dmp

Crash Time : 5/6/2017 10:07:58 AM

Bug Check String : BAD_POOL_HEADER

Bug Check Code : 0x00000019

Parameter 1 : 00000000`00000023

Parameter 2 : 00000000`00000000

Parameter 3 : 00000000`00000002

Parameter 4 : ffffa189`659cadc0

Caused By Driver : ntoskrnl.exe

Caused By Address : ntoskrnl.exe+14e7c0

File Description : NT Kernel & System

Product Name : Microsoft® Windows® Operating System

Company : Microsoft Corporation

File Version : 10.0.14393.1066 (rs1_release_sec.170327-1835)

Processor : x64

Crash Address : ntoskrnl.exe+14e7c0

Stack Address 1 :

Stack Address 2 :

Stack Address 3 :

Computer Name :

Full Path : C:\WINDOWS\Minidump\050617-41406-01.dmp

Processors Count : 8

Major Version : 15

Minor Version : 14393

Dump File Size : 543,340

Dump File Time : 5/6/2017 10:11:17 AM

==================================================

 

How to fix BSOD caused by ntoskrnl.exe

I've done the steps you have given and surprisingly the issue got resolved. Now no issues with the battery too..!!

I don't know how to thank you, Gerry.!

• May I ask which tool do you use to analyse the dmp files?

• Why in BlueScreenView it showed the problematic driver as ntoskrnl.exe?