Windows 10: ntoskrnl.exe 142760 BSOD Error

Hi,

I built my pc about a week ago and I have been getting BSODS, and I used BlueScreenView to see that ntoskrnl.exe, 142760 was causing the issue. I am not sure how to troubleshoot this as this is completely new to me. I checked that my memory and storage are fine. I will be attaching the dmp file below. Please help me, thanks a lot.

:)

 

Getting Blue Screen of Death on Windows 10 with error ntoskrnl.exe

Old title: BSOD ntoskrnl.exe 142760

I seem to be getting BSODs since the beginning of April relating to ntoskrnl.exe 142760, and I don't know what's causing it.

Currently on Windows 10 64-bit.

Here's my dumps:

Link not found

 

BSOD (Blue screen error) on Windows 10 PC.

Original Title: BSOD

010216-10078-01.dmp

2.1.2016. 14:35:34

0x00000139

00000000`00000021

ffffd000`209ea5d0

ffffd000`209ea528

00000000`00000000

ntoskrnl.exe

ntoskrnl.exe+142760

NT Kernel & System

Microsoft® Windows® Operating System

Microsoft Corporation

10.0.10586.17 (th2_release.151121-2308)

x64

ntoskrnl.exe+142760

C:\Windows\Minidump\010216-10078-01.dmp

4

15

10586

134.716

2.1.2016. 14:36:01

I need help with bsod
i repeatedly get this error

 

Have you a Raid setup, is so upgrade drivers....Also check all hardware drivers.
Have you overclocked, if so restore to original clock speed.
I assume you have taken out one memory at a time to check as you state memory fine.

 

A stray crash dump is not enough to debug a KERNEL_SECURITY_CHECK_FAILURE BSOD.
Code: A kernel component has corrupted a critical data structure. The corruption could potentially allow a malicious user to gain control of this machine. Arguments:[/quote] @akashme2palli, you need to post a reply in this thread following the Blue Screen of Death (BSOD) Posting Instructions .

Apparently the display driver is flagged,
Code: fffff803`c13e0648 fffff801`2b2005b4Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for atikmdag.sys *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys atikmdag+0x905b4[/quote] Those files will help us to know more about it.

 

Hey guys,

Thanks a lot for helping, I updated all my drivers and I have not been getting any BSODS

Cheers

 

Arc... many thanks for your efforts and willingness to help others. For us scanning the web for solutions to issues, people like you are such a blessing. I've had my own issues related to this ntsokml.exe and ntkrnlmp.exe problem. I also experienced DRIVER OVERAN STACK BUFFER. For those searching for more information related to these issues, here is an abbreviated paste from a Who Crashed analysis of my system, and what I ended up doing with it.
4/22/2016 3:39:02 AM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xF7 (0xFF000D1673F4E696, 0xD1673F4E696, 0xFFFFF2E98C0B1969, 0x0)
Error: DRIVER_OVERRAN_STACK_BUFFER
Bug check description: This indicates that a driver has overrun a stack-based buffer.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
4/21/2016 11:05:55 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\042216-10546-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F4D0)
Bugcheck code: 0x7F (0x8, 0xFFFFD000ADDE4A30, 0xFFD000ADF0DFB0, 0xFFFFF8030D762F9F)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

As you can see there really is no useful or traceable information provided by Who Crashed. As my system is a custom build and has been running well for about a year, I tried doing a format and clean install in hopes it was a software or update issue (and reloaded the original base drivers). The clean install did not help and my computer would restart randomly without displaying a BSOD. Just poof and it would restart. No specific third party software was in use when these random restarts would occur. Often the PC would be sitting idle. The only indication of the crash was in the Who Crashed analysis. After the clean install, I cloned and replaced my SSD. This had no positive effect. I then swapped out my video card to insure that it was not a GPU issue. No effect. I swapped out my year old PSU with a new PSU off the shelf… no effect. I then ran two full cycles of Memtest on the RAM with no errors. The RAM I was using was one Kingston Hyper X Fury Red 4GB stick (1866mhz) mixed with one Crucial Ballistix 2GB stick (1600mhz). Same voltage but mixed frequencies. (I did not know the frequencies were different at the time of installation, Kingston is bad about not listing frequency on the stick) These DIMMs had been running together for over a year with no issues. I replaced both modules with a paired set of 4GB sticks. Matched manufacturers, matched frequencies. I’ve been running now for almost a week with no restarts or any other issues. I thought it might provide useful information for others with a similar problem to know how I resolved this. Thanks again for your and everyone’s help with PC problems!

 

Hi @ThatPCGuy. Please follow the Blue Screen of Death (BSOD) Posting Instructions ... we will see what we can do.

 

Glad to see you got it sorted.....mine was only basic advice, the real expert being Arc.

 

My problem is solved, I wanted to thank you and the other helpful folks in the forum for their tireless effort and patience in helping others... my problem was a hardware issue, but I saved the solutions that you offered for ntoskml.exe software related issues as I may need to use them in the future. Thanks a bunch and many blessings to all.

 

ntoskml.exe and/or ntkrnlmp.exe are not the originating causes of any BSOD. Those are the kernel images. Description here: ntoskrnl.exe - Wikipedia, the free encyclopedia

When the crash dump recording mechanism cannot point out and record the actual originating cause of the BSOD, it blames the kernels itself on which the crash took place. It is a mistake by the dump recording mechanism only.

A BOSD pointing to those kernels often requires further analysis etc.