Windows 10: BSOD - ntkrnlmp.exe

Don't think my BIOS has XMP (I haven't seen it). I'm able to change RAM frequency and voltage manually though, so same difference?

 

I hope you are right about this *Smile
Because that would mean a driver is causing issues, to catch this driver, driver verifier is needed.





Diagnostic Test

DRIVER VERIFIER


Warning Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.
Please follow this tutorial to run driver verifier.

Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.



Note Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

 

None are caused by driver verifier.
Keep verifier running for about 35h more.

 

Well things have gone from bad to FUBAR. The system is now completely unusable. I can't even get the dump files off it to post here - it crashes too quickly. I eventually managed to turn driver verifier off, but it's still crashing like crazy. Most of time not even bluescreening - just freezing or restarting itself without warning.

 

How is it in safe mode?

 

Lasted longer in safe mode, but still crashed (black screened this time). Managed to run the dump file collector tool and transfer to a flash drive (see attachment).

 

That means hardware problems.
I realize your system can't stay on long enough to run online tests, below are 2 bootable tests.
Hardware Diagnostics does have other tests you could run.





Diagnostics Test

HDD TEST


Run SeaTools DOS to check the integrity of your HDD. http://www.sevenforums.com/tutorials...s-how-use.html



Note Do not run SeaTools on an SSD as the results will be invalid.



Run chkdsk http://www.sevenforums.com/tutorials...isk-check.html






Diagnostic Test

RAM TEST


Run MemTest86+ - Test RAM - Windows 10 Forums



Note



MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

 

I tried, but the system isn't stable enough. I managed chkdsk by booting into safe mode w/ command prompt. It reported no errors, but gave a "failed to transfer logged messages to the event log with status 50" message. Significant? I also noticed it completed the test suspiciously quick. Tried to run it normally, but crashed before completion three times, so gave up. Memtest86 wouldn’t boot – I don’t understand why. Becoming dangerously frustrated, I walked away from it for a while.

In any case, I ran both of these tests before (see original post) and got no errors, so don't consider them good candidates. With the system in its current state, I'm guessing I have little choice but to start swapping parts. A visual inspection didn’t reveal anything either. The slots are free of dust and debris. No visible cracks. No bulging caps. Everything has been disconnected and reseated.

 

There are indeed 2 tests, but I missed chkdsk with removing from the test, for the HDD tests I have 3 different tests.

I suggest you try running SeaTools in DOS.

You said you ran MemTest86, which is different from MemTest86+

 

Another escalation occurred yesterday - it failed POST (infinitely repeating long beeps), which it has done many times before, but this time wouldn't pass even after several resets. After removing and reinstalling the processor, the system booted fine. I managed to run chkdsk, Sea Tools and Memtest86+ (9 passes), none of which returned any errors. Surprisingly, the system didn't crash during any of this which is making me very suspicious of the CPU. Whilst it was out, I observed a defect on the casing. I couldn't tell whether it was just a surface scratch or hairline fracture and no amount of looking at it from different angles and running my finger over it could help me decide.

Your thoughts on how to proceed from here?

Oh, and I did another dump file collection since the computer was being unusually co-operative. Though, if they haven't given you anything useful so far, I doubt any more are going to help.

 

Please check GIGABYTE - Motherboard - Socket AM3+ - GA-970A-DS3 (rev. 1.0)
for BIOS updates.
Install the most recent NOT in beta.
Attachment 50271

 

It blue-screened whilst updating BIOS! *Eek

Luckily it still boots okay. Do you think I should risk a second attempt?

 

I hope you have made a backup of your data. If not do it a.s.a.p.

At what moment came the bluescreen?

 

If I may interject something here, I would first do what @axe0 suggested. Then go into BIOS and tell us what version of BIOS it says is installed now.

 

Yes, my data is backed-up (the important stuff, anyway).

A notification informed me that the screen might freeze for a few seconds during the BIOS update and asked me if I was sure about proceeding. I clicked yes, the window closed, and about a second later it blue-screened, collected a dump file and restarted.

BIOS version F1 (the original) is showing as current.