Windows 10: Fresh Windows 10 upgrade - ntoskrnl.exe & ntkrnlmp.exe

I just installed windows 10 and I have had constant BSOD's when doing multiple things at once (gaming, surfing web, listening to music, etc). This is what WhoCrashed is saying:

On Tue 9/29/2015 7:29:06 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\092915-19531-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E240)
Bugcheck code: 0x139 (0x3, 0xFFFFD001FD8C65D0, 0xFFFFD001FD8C6528, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 9/29/2015 7:29:06 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: 0x139 (0x3, 0xFFFFD001FD8C65D0, 0xFFFFD001FD8C6528, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 9/29/2015 1:41:27 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\092815-19781-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E240)
Bugcheck code: 0x1A (0x411, 0xFFFFF6BFFE9022C0, 0xE51000011E43A884, 0xFFFFF68042942470)
Error: MEMORY_MANAGEMENT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

And below is the requested .zip

Thank you for the help!

:)

 

Multiple BSOD, I don't know where to start

Thank you for your quick answer!

I already had a one-year old Windows 10 clean install and already did almost all the steps described in the first link you provided. I ended by a fresh reset from the Settings. So far it worked without issues for 3 days, and I was happily uninstalling some
bloatware (Candycrush! please no haha) and reinstalling all my software...

But yesterday I got BSODs again "due to Microsot drivers" (ntoskrnl.exe, ntkrnlmp.exe, hal.dll).

I have now exactly the same behaviour as before. I did a full backup of my system before doing a fresh reset, just in case. For the time being, I would like to investigate and understand what software or driver is causing the issue. I couldn't make a connection
between the software I installed and the first time the BSOD happened.

If you have some time to help me finding the cause of this issue I would be more than happy to provide you all the needed information!

 

Windows 10: BSOD - ntoskrnl.exe & ntkrnlmp.exe

1. it was preinstalled when i got the computer

2. i didnt

3. Version 1703 Build 15063.540

 

Hi haoleflip,

Welcome to the 10forums.

The memory_management error means that there are problems with your memory.
Because in both crashes I found no drivers, if the memory test comes out clean please enable driver verifier.





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.






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.

Some windows drivers are blamed in a few crashes, but that usually means that a 3rd party driver is actually the cause.
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.