Windows 10: Constant crashes on fresh W10 - ntoskrnl.exe

I had a very stable rig that I built a couple of months ago. Then the KB4038788 update would just not install - it always failed. I kept putting up with it for a month. I tried a lot of things that were advised on various support sites. The rig was still stable as anything, no problems whatsoever, but I just wanted to get that failing Windows update done!

Now today I formatted and reinstalled my Windows 10 from ground up. After that, it's crashed already 5 times or so. I downloaded the WhoCrashed tool, and got these:

http://i63.tinypic.com/8wwhl3.png
http://i63.tinypic.com/2ccpg0k.png
http://i63.tinypic.com/34g37i.png
What might be causing the crashes? The last crash happened immediately when I opened Firefox, after maybe 1-2 minutes of uptime.

I would argue that the failure to install the update and these sudden crashes are unrelated, but if they are, figured I'd tell the background, too.

Thanks a lot! I promise to buy a beer to anyone who helps, if we ever meet!
And oh, here are my specs:
Asus TUF Z270 Mark 1 Intel Z270
Intel Core i7 7700K 4x 4.20GHz
Noctua NH-U12S
16GB Corsair Vengeance LPX DDR4-3000 DIMM CL15-17-17-35
750 Watt Corsair RMx Series RM750x Modular 80+ Gold
6000GB WD WD6002FZWX 7.200U/min 128MB 3.5"
1000GB Samsung 850 Evo 2.5" (6.4cm) SATA 6Gb/s TLC Toggle

EDIT:
Here are them on txt versions as well:
On Mon 09/10/2017 0.43.25 your computer crashed
crash dump file: C:\Windows\Minidump\100917-5828-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C580)
Bugcheck code: 0x1A (0x41792, 0xFFFFE43FFE422008, 0x1000000000000000, 0x0)
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. This problem might also be caused because of overheating (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 Mon 09/10/2017 0.43.25 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: 0x1A (0x41792, 0xFFFFE43FFE422008, 0x1000000000000000, 0x0)
Error: MEMORY_MANAGEMENT
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. This problem might also be caused because of overheating (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 Mon 09/10/2017 0.32.24 your computer crashed
crash dump file: C:\Windows\Minidump\100917-6484-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C580)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80203230913, 0xFFFFCC000F5C88A0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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.



On Mon 09/10/2017 0.01.54 your computer crashed
crash dump file: C:\Windows\Minidump\100917-5781-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C580)
Bugcheck code: 0x1A (0x41793, 0xFFFF8480000E9E00, 0x1C1, 0x1C0)
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. This problem might also be caused because of overheating (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 Sun 08/10/2017 23.53.15 your computer crashed
crash dump file: C:\Windows\Minidump\100817-6578-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C580)
Bugcheck code: 0x1A (0x41793, 0xFFFFEF800011DD10, 0x1A3, 0x1A2)
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. This problem might also be caused because of overheating (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.


:)

 

Frequent BSODs on new laptop

Just did a fresh reinstall of W10 Pro and it crashed shortly after (PFN_LIST_CORRUPT)

071916-5578-01.dmp

 

Windows 10 Blue screens

Hi All,

ever since upgrading to win 10 my PC will randomly blue screen on me. on first upgrade it was constant, I then wiped windows off and did a fresh install which was a bit better. I then formatted the drive and started fresh. this was good for about
2 weeks then they started again.

bluescreen view says the last three were KMODE_EXCEPTION_NOT_HANDLED caused by NTFS.sys or ntoskrnl.exe. other stirngs are system_service_exception, page_fault_in_nonpaged_area and driver+power_state_failure. all from NTFS.sys or ntoskrnl.exe.

if I turn on verifier my pc just reboots load and rebotts to recovery mode continuously. had to go into safe mode and turn it off again to be able to load into windows.

is there any other way to determine what bit of hardware is causing this?

Page_fault suggests a mem module but NTFS suggest HDD right?

cheers Mark :^)

 

Hi Velokki,

In order for us to best help you, we will need some additional information about your machine. This can be easily gathered by running the log collector. You can find it here: BSOD - Posting Instructions - Windows 10 Forums.

Given that this is happening on a fresh install of Windows 10, this could very well be a hardware issue. I'd suggest you start by testing your RAM for 8+ passes using MemTest86+. Also, if you are overclocking, reset everything to default as this is another variable we'll want to eliminate.

 

Hi guys!

Here is the file, attached.

It's really irritating that this should happen now, since I'm was attempting to record my band's demo these days, and then I end up in a system failure hell *Biggrin Well, inspiration for the lyrics, I guess!

P.S. I've done this piece of registry editing to enable the old Photo Viewer:
Is Windows Photo Viewer gone? Solved - Page 2 - Windows 10 Forums

 

I've never overclocked. So that's ruled out.
I thought that it might have something to do with display drivers, or the lack of them, so I downloaded the newest NVIDIA drivers. 2 hours, no crashes! Until I had 3 crashes in a row just now. It doesn't seem to be correlated to what I'm doing in any way - watching a video, just browsing the Internet or just idle. I also ran Prime95 for 2 hours - no problems.

I seriously don't have any idea what is causing this. To recap, my timeline is as follows:
-I get a new PC build in the beginning of June.
-The system runs great, no probelms, nada.
-Somewhere near the beginning of September, the update KB4038788 would not install. It would always fail. Yesterday I started troubleshooting it like a mofo. Tried to fix with some command prompts that Microsoft Support suggested. At some point, I got a BSOD with the big emoji *Sad and the text "Your PC ran into a problem and needs to restart. We're just collecting some error info, and then we'll restart for you. Stop code: CRITICAL_STRUCTURE_CORRUPTION.
-After reboot, Spotify was corrupted, and couldn't start because of a corrupt file.
-I decided to install Windows 10 fresh altogether.
-Now it's been crashing all the time. Actually, this is the third time I write this post. This time on the Notepad and pressing Ctrl+S every 10 seconds, since I don't want to write it a fourth time. It worked in the morning for 2 straight hours, but now keeps crashing all the time.

Thanks a lot for checking into this, it means the world to me right now.

 

Right, I decided to run the Windows Memory Diagnostics Tool. This is what it came up with:




This showed up on the boot after that:





I take it the RAM is faulty then?

 

Yep, that indicates an issue with your RAM. If your RAM kit is still under warranty, just contact the seller and get a replacement set.

If it's not under warranty, remove all but one stick of RAM, test it, and repeat the process until you determine which stick is faulty and then replace that single stick. Make sure to get the same brand/speed/size of ram when replacing it, to eliminated strange compatibility issues that may come up.

 

It is under warranty.

But oh boy, Memtest86 was not pretty to look at. Just tens of thousands of errors everywhere.

I tested the RAM kits one at a time. Turns out that the first RAM kit of the two works perfectly fine. With the second one in, the PC wouldn't even boot. Now I have only one RAM kit inside, and it seems to be working just fine, hasn't crashed yet at least.

I think this is the solution for now, hopefully I won't meet the horrid BSOD ever again.