Computer crashing with "ntkrnlmp.exe" at fault (logs included)

Toggle sidebar Toggle sidebar
QuestionableUsername

QuestionableUsername

Reputable
Nov 5, 2014
267
0
4,790
My computer randomly crashed (cannot find a pattern to the crashed), and when I mean crashes, I do not mean BSOD. The crashes just make the screen turn black and then my computer 'restarts' (doesn't save anything, just powers off than back on again)...

I used WhoCrashed to get these reports (for some reason only 2 got inputted in the WhoCrashed log but I've experienced MANY more crashes).

Note: I got these after updating my BIOS (I was quite behind on updates so I decided who not?), after another update a few days later I am now at the most recent BIOS and still crashes occur.

Additional Notes: I do not overclock (there is a weird setting on my motherboard related to overclocking that is set to auto (the default). I ran a temperature test, my computer does not go above ~45 Celsius, temperature is not a problem. I ran Intel diagnostic checker with a clear pass. I ran windows memory diagnostics with a pass.

PC SPECS: http://pcpartpicker.com/list/9w83Vn

------------WhoCrashed logs-----------------
On Thu 6/23/2016 9:29:08 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\062316-11328-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!WheapCreateLiveTriageDump+0x81)
Bugcheck code: 0x124 (0x0, 0xFFFFE0004980D038, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 6/22/2016 2:13:23 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\062116-11156-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!WheapCreateLiveTriageDump+0x81)
Bugcheck code: 0x124 (0x0, 0xFFFFE001698B98F8, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

UPDATE: Just had the RAM returned to Corsair and they sent me new RAM. It still crashes, I believe it's the motherboards fault now, any suggestions?
 
Sort by date Sort by votes
QuestionableUsername

QuestionableUsername

Reputable
Nov 5, 2014
267
0
4,790


It's near impossible to test, it happens randomly. I had a full day with no crash yesterday, and today just this morning it happened twice.

Thank you for you're effort. I will keep a sharp eye on this thread, however I have an appointment soon and will check up on this thread in an hour or two.
 
Upvote 0 Downvote
QuestionableUsername

QuestionableUsername

Reputable
Nov 5, 2014
267
0
4,790
BUMP - I thought it stopped after I turned off fast startup in the BIOS but unfortunately it just happened now. I worked for a solid day and a half though...

UPDATE: The newest crash didn't make a WhoCrashed log..I wonder why?
 
Upvote 0 Downvote
Flyfisherman

Flyfisherman

Distinguished
May 29, 2012
1,136
8
20,365
Test Your memory's
Download and install Memtest86+ it's a free s/w http://www.memtest.org/
Create a bootable CD/DVD or USB-stick, it is a very small program and it will easily fit on a CD.

Then boot the computer from this, memtest will automatically start, and don't worry - it will not in any way compromise nor touch anything on the hard drives.
You must run memtest until at least pass 7 and for 8GB of memory it will take the whole night, approx 5-6 hours, if 16GB memory - twice as long.
If an error occur, You can just shut it down. Then You know that it is a serious problem with your memory's.

Best regards from Sweden

 
Upvote 0 Downvote
QuestionableUsername

QuestionableUsername

Reputable
Nov 5, 2014
267
0
4,790


I have 32 GB of ram... Will that take as long as it sounds?
 
Upvote 0 Downvote
Flyfisherman

Flyfisherman

Distinguished
May 29, 2012
1,136
8
20,365
Yes.

What you can do is to remove one or two ram-sticks and see how it works.
If problem, exchange and test again.
The thing is to try to isolate if there is any problem and which of the memory ram-sticks.

If Not, then we will look into another possible resolution.
Best regards from Sweden
 
Upvote 0 Downvote
QuestionableUsername

QuestionableUsername

Reputable
Nov 5, 2014
267
0
4,790
Another thing I forgot to add is the problem started occurring not only after I updated the BIOS, but I reset my BIOS settings to 'optimum defaults' (I changed a few things in the BIOS that I didn't want to keep and I didn't know where they were, huge mistake on my part...)

I will get back to you in a few days with the results of the memtest
 
Upvote 0 Downvote
Flyfisherman

Flyfisherman

Distinguished
May 29, 2012
1,136
8
20,365
You where doing correct in "Load Bios Optimum Defaults" and this has not likely to do with Your problem, unless You have chanced Bios settings other than the Boot priority.

But, try to change in the Bios setup the UEFI Secure Boot state settings:
In the Bios Boot menu > Secure boot state > Disable => Save & Exit
https://www.asus.com/us/support/FAQ/1016356/

Best regards from Sweden
 
Upvote 0 Downvote
QuestionableUsername

QuestionableUsername

Reputable
Nov 5, 2014
267
0
4,790


Quick question, right before I run memtest. Should I run this: http://www.memtest.org/
or this: http://www.memtest86.com/

They seem the same to me and someone from a different post recommended me another one.
 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
generally, memory or fast startup should never cause bugcheck 0x124

you should put your memory dumps from c:\windows\minidump directory on a server like microsoft onedrive, share the files as public and post a link.
This bugcheck is common with overclocking, power problems, and overheating problems. generally, the only driver that would cause this problem would be a overclocking driver. (assuming your BIOS was updated to reflect the actual CPU you have installed)
 
Upvote 1 Downvote
QuestionableUsername

QuestionableUsername

Reputable
Nov 5, 2014
267
0
4,790

It's late and I will do that tomorrow, thank you to everyone contributing so much you guys have no idea how much this means to me. Is there any way to check if it is a power problem? I'm just using an old wall socket in my older house, when my fan, lights, desk light, monitor, computer and keyboard (LED) is on, the room light tends to dim. Maybe when other lights are on too?

Perhaps this is a reason?

BTW: I do not overclock, unless my mobo is automatically somehow overclocking by itself since some of the setting are set to "auto"...
 
Upvote 0 Downvote
QuestionableUsername

QuestionableUsername

Reputable
Nov 5, 2014
267
0
4,790


Also another problem is that the 'crashes' are not creating logs or minidumps... I've ONLY seen these two crashes get logs/minidumps, the rest do not.
 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
generally a you would not get a memory dump if the problem is with the storage subsystem. But it would be a different bugcheck code. in those cases it would display on the screen but could not write it to disk.

that leave you with a power problem.

a memory dump can still have some use in figuring out the problem. even a overloaded circuit can cause the power to the psu to drop too low and cause the protection circuits of the motherboard to reboot your machine.

I have talked to people that had machines reboot when a refrigerator motor turned on.
you could have a power outlet that has a bad circuit connection where it is providing a low voltage like 90 volts rather than 120. you might see if your bios will indicated the voltages applied to the motherboard.




 
Upvote 1 Downvote
QuestionableUsername

QuestionableUsername

Reputable
Nov 5, 2014
267
0
4,790


This is an awkward problem... What should I do in this situation? I mean I can check the voltage of a power outlet and things and match it with the mobo, and assuming it's not good (kind of what I expect at this point). What do I do? Try and install a new outlet?

What did the people who you talked to do to fix it?

Thanks!
 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
I would start by looking at the most likely cause of this problem>
overclocking in BIOS or software.
any of the memory dumps will show the CPU clock rate and the list of drivers installed.
often I have seen people running many copies of overclocking programs at the same time and not even know it.
it is why I look at the memory dump as the first step. it will show any software or BIOS cause this problem.
(most likely) it will also give a hint as to the hardware cause. I do this because you don't end up running out to buy hardware you really don't need.

I often see people jumping to the conclusion of a failed part, buying a part and it does not help.
I even see people buy a part and it does help (but not for the reason they think, the first part was most likely still ok)





 
Upvote 0 Downvote
Flyfisherman

Flyfisherman

Distinguished
May 29, 2012
1,136
8
20,365
Download and install free BlueScreenView http://www.nirsoft.net/utils/blue_screen_view.html
run the s/w to see if there are any memory dump file with errors, that suggest a Windows system crash.
The important info is: Error message and the stop error code.

To find out if it has some strange temperatures or voltage: download and install HWMonitor (free) http://www.cpuid.com/softwares/hwmonitor.html
To the left download the free version.
Obs! during installation make sure that you untick any third part s/w. I always recommend this procedure no matter what on any free s/w. Ok.

Then, in the HWmonitor window there are three columns:
Value= shows the actual readings from all the sensors including temperatures and voltage
Min and max speaks for itself.

Now, Start the most cpu heavy program you have and work with it, surf the internet and perhaps watch an on-line news film for at least 5-10 minutes.
Then quit all these programs/webbrowser and take a reading from HWmonitor, which of course you have been running in the background:

In the column Max: what does it says?
Post the values here or you can also click 'File > Save monitoring data > it will be a text file and attach that into your next post.

Run System File Checker (SFC /scannow) to see if there are any corrupted system files that can be repaired.
Se instructions here:
Windows 10 Forums - SFC Command - Run in Windows 10

Another thing; have You overclocked Your CPU? In any case, also make sure to load BIOS Optimized Defaults or Load BIOS Default in the BIOS Settings menu, check the boot priority for your drives afterwards and then Save & Exit.http://

Best regards from Sweden
 
Upvote 0 Downvote
QuestionableUsername

QuestionableUsername

Reputable
Nov 5, 2014
267
0
4,790


Ok I got the program and google what the most CPU intensive thing was, turns out rendering 3D animations on Cinema4D is one of them so I rendered about 150 1440p PNG's for 5 min then let it relax a for a few minutes and saved the monitoring data. The Max column said 100% when rendering.

HWmonitor txt monitoring data is found here on OneDrive

I will try out the SFC thing tomorrow morning or tonight! Thanks for the help!

UPDATE: I did the SFC/scannow thing just now, and it came out clean.

NOTE: On days that my computer goes crazy and 'crashes', it becomes very slow the longer I use it (or the computer is on). Today luckily that wasn't the case however days like yesterday it became extremely laggy to do anything, especially online.
 
Upvote 0 Downvote
Flyfisherman

Flyfisherman

Distinguished
May 29, 2012
1,136
8
20,365
Hi, I'm sorry that I could not respond until now.
No, You have not correctly saved the HW monitoring data.
I do not what You have been saving, but it does not tell me anything about the temperatures.

Do it again: Post the values here or you can also click 'File > Save monitoring data > it will be a text file and attach that into your next post.
Or just copy & paste into your nexxt post.
Remember:

Start the most cpu heavy program you have and work with it, surf the internet and perhaps watch an on-line news film for at least 5-10 minutes.
Then quit all these programs/webbrowser and take a reading from HWmonitor, which of course you have been running in the background:

In the column Max: what does it says?
Post the values here or you can also click 'File > Save monitoring data > it will be a text file and attach that into your next post.

Best regards from Sweden



 
Upvote 1 Downvote
QuestionableUsername

QuestionableUsername

Reputable
Nov 5, 2014
267
0
4,790


I'm doing exactly what you say and it's giving me the same type of file data in the text file...
 
Upvote 0 Downvote
Flyfisherman

Flyfisherman

Distinguished
May 29, 2012
1,136
8
20,365
Hi, It is hard to determining what is going on over there, but can you give us the readings from HardWare Monitor as I suggested before?

Otherwise a complete new Windows installation should be considered - unless it is something with the hardware..
you can also check the memories:

Test Your memory's
Download and install Memtest86+ it's a free s/w http://www.memtest.org/
Create a bootable CD/DVD or USB-stick, it is a very small program, it will easily fit on a CD.

Then boot the computer from this, memtest will automatically start, and don't worry - it will not in any way compromise nor touch anything on the hard drives.
You must run memtest until at least pass 7 and for 8GB of memory it will take the whole night, approx 5-6 hours, if 16GB memory - twice as long.
If an error occur, You can just shut it down. Then You know that it is a serious problem with your memory's.
Best regards from Sweden


 
Upvote 0 Downvote
QuestionableUsername

QuestionableUsername

Reputable
Nov 5, 2014
267
0
4,790


Again as for the HWMonitor I cannot get any results other than the one's I've posted.

As for the memtest86+, I ran it. 1 pass, was 50% through the next test (I was not at my computer at the time) but it restarted on it's own! I have no idea what that means? Did it just crash? Does it mean my memory is faulty?

(I should also add that I reseated my RAM and cleaned the dust from my computer.
 
Upvote 0 Downvote
Flyfisherman

Flyfisherman

Distinguished
May 29, 2012
1,136
8
20,365
Possible. run memtest again and watching it.

Remove all the ram- sticks but one.
Then exchange the ram stick to the next one and run memtest again.

With just one ram-stick the test will get to its Pass 7 much quicker.
This a way to determine if there is a problem and which one of the ram-sticks got a problem.

important: perhaps looking into Your motherboard manual to see in which memory slot to be used if only one ram-stick is used. Typical often on Intel mobos is the second memory slot from the CPU (slot #1, but otherwise it is the nearest memory slot to the CPU slot #0).
They are numbered from zero and upwards.
Best regards from Sweden
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom