Windows 10: BSOD ntfs.sys and ntoskrnl.exe crashing (System Service Exception)

Could you upload a kernel dump (C:\Windows\Memory.dmp) to a 3rd party uploader (dropbox, onedrive, google drive) and post a share link in your next reply.

This registry error is a rare error, this is the first time I've seen it. With a little bit of luck and no corruption in the file I might be able to get some information out of it.

Chance exists it might *Smile

 

Omg, I got a rare error? The rarest of them all? :O

Truth be told, I'm making fun of it while I might be royally f*cked for all I know hahah :x

I'll edit this post with the share link when I get back home in about 3 hours.

Edit: Here it is! (took a while to upload)

Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

Also, computer still hasn't crashed while verifier was running since last night.

 

Just got a crash while using the computer, ntoskrnl.exe crashed.

I don't know if it's cause of verifier though...

On Tue 06/06/2017 17:55:05 your computer crashed
crash dump file: C:\Windows\Minidump\060617-4781-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C310)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF802FDC72BB9, 0xFFFF8581D2BD4580, 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.

 

Please don't use WhoCrashed, BlueScreenView or similar tools, they don't provide useful data.
Use the DM Log Collector instead.

I assume the kernel dump has been updated to the latest crash before you could upload it, so the request to upload the kernel dump may be ignored.

 

Did you check it? I copied it away from the folder. (the link is in previous comment)

Edit: Used the collector for the latest crash.

 

I'm currently checking it, and as I kinda expected the error code is different.
The error code is one I can troubleshoot with a minidump, because it is better documented than the rare onces. Unfortunately I seem to be getting errors with the kernel dump, I may get back to you on it later.

I just checked your MemTest86+ test result, unfortunately I need to ask to run the test again. The issue is with the version, the newer version 5.01 has some changes that include bugfixes and other problem fixes.

 

8 passes, no errors. https://i.imgur.com/NOL4XQ7.jpg

Any suggestions on what to do next? :/

 

Did the system crash with driver verifier, I can't remember and cannot check atm

 

While not being on a computer and having verifier running, no. It would crash when I'd do stuff, like it usually would.

 

Here are the crash dump reports from today and yesterday while the verifier was running.

 

I notice that the system runs for a few seconds and then crashes, too early for driver verifier to get in action.

Could you shutdown, remove all peripheral and start the system just to see if the system can run for longer than a few minutes with driver verifier. If this doesn't work the system needs to be stripped down by removing everything that is not required to boot. Thus removing all RAM sticks except for 1, removing hdd/ssd until the boot device is solely connected, disconnecting the internet cable, etc.

 

Sorry for responding so late, I spent the whole day yesterday taking my pc apart and replacing components. I rebuilt it from the ground up, again.

To respond to your request... driver verifier ran fine before, the whole day, without touching anything. I only got one crash and that was when I was using it. Sent you the crash dump file and you said it was the usual one, as far as I understood.

Anyway... onto the point. Long story short, I replaced every component except the motherboard, processor, and the fans, and the computer still crashed. I did load the windows from SSD, but the SSD worked fine on my friends computer, and on mine it would crash whether it was on SSD, or HDD. Also, I checked them both and had the latest drivers so... what would be the conclusion?

I updated the BIOS, but I didn't touch the SATA drivers for my MB. I'll probably do that now, but excluding that, due to the nature of errors, who's to blame? Could the processor even be capable of doing that?

 

When you'd think about it, knowing how every part basically works, you could say that every part could cause a lot of issues.
Yes, the CPU is capable of causing a large amount of issues. It is 1 of the parts that is most difficult to identify as a cause, and relatively the rarest to cause problems.

If you decide to replace, I recommend to first replace the motherboard.