Windows 8 Random 0x0000001A errors with ntkrnlmp.exe

Nubkakes

Member
Joined
Jul 25, 2016
Messages
21
Hello!

One of my friends recently built a computer with the same hardware as myself (same part numbers and everything) with the exceptions of; the sound card, the storage device, and the operating system. Well, ever since we assembled it, he has been randomly getting 0x0000001A errors.

Initially he was using windows 10 and was getting these BSOD errors very frequently. I noticed these lines in the crash DMP files while using windbg;
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
IMAGE_NAME: ntkrnlmp.exe

I figured he had the wrong drivers installed, so I had him update all the drivers from the hardware manufacturers' website. The crashes still occurred at the same frequency with the same error codes.

So, since he had a license of windows 8 as well, he decided to try using windows 8. Well, the crashing initially disappeared for about a week. He got another 0x0000001A last night which is suspiciously close to the ones he was receiving on windows 10. On top of that he has started to get occasional black screen restarts with no DMP files. I am leaning a bit toward the hardware at this point. Hopefully someone here can help point us in the right direct.

His PC specifications:

OS: Windows 8.1
CPU: Intel Core i7 6700K
Motherboard: MSI Z170A M3
Memory: CORSAIR LPX 32GB Model CMK32GX4M4A2133C13
GPU: MSI Geforce GTX 980 TI Lightning LE
Harddrive: Samsung Pro 512GB


 

Attachments

Last edited by a moderator:
Solution
Code: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41201, fffff68000187cb8, 286040021a84c867, ffffe000e4fb39a0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+16f8c )

Followup: MachineOwner
Hi,
bugcheck 1A means an severe memory management issue occured. This is often indicative of faulty RAM. Even...
Sort by date Sort by votes
My friend hasn't been in town yet so I haven't been able to give me one of my RAM sticks but here is a mini update.

I had him run sfc /scannow last night for the hell of it since it was strange that the crashing was mostly gone for a couple days and then returned largely in the same fashion. He just texted me the results and long behold:

Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.Log
Click to expand...

Kind of sketchy if I do say so myself. We fixed that shit last week!

I told him to run "dism /online /cleanup-image /restorehealth" when he gets the chance.
 
Upvote 0 Downvote
I'd be getting him to check the system drive, can you get him to do a chkdsk c: /R from an admin command prompt. Best to warn him it may take many hours.
 
Upvote 0 Downvote
Nubkakes said:
Kind of sketchy if I do say so myself. We fixed that shit last week!
Click to expand...
Yup i remember.. It might not be too drastic and often these corrupt files relate to something insignificant. The DISM scan should hopefully repair it but if not post in the CBS logs.
 
Upvote 0 Downvote
You must log in or register to reply here.

Similar threads

V
  • Solved
Windows 10 Need a help with BSOD
Replies
12
Views
5K
kemical
I
  • Solved
Windows 8 Windows 8.1 Pro BSOD Randomly
Replies
4
Views
3K
kemical
K
  • Solved
Windows 7 BSOD caused by 'ntkrnlmp.exe'
Replies
5
Views
7K
usasma
W
  • Solved
Windows 7 IMAGE_NAME: ntkrnlmp.exe causing BSOD on Win 7 x64
Replies
1
Views
2K
ChatGPT
U
  • Solved
Windows 7 BSOD: ntkrnlmp.exe Please help
Replies
4
Views
4K
kaos