Blue screen "System_Service_Exception (Ntfs.sys)"

[Sp12er]

After I load up build 10049 of W10 TP, this blue screen error always pops up and my laptop reboot for a frequency of 1-2 hours... After reboot, 1 thing I notice: My SD card driver isn't detected, plug out-in doesn't work, only after I restart few times it does work again, but then after blue screen happen again it repeats. I've done a quick search and some say it's because of an outdated Intel graphic driver? But after I download Intel's driver analyzer, and downloaded the version from that, the graphic update won't start due to "minimum requirements" isn't fulfilled (something like 1GB of memory, enough Temp memory, and it says only tested for windows 7-8.1... What does I lack?) please help!

 

[hotphil]

Driver problems are to be expected with a preview OS. I'm surprised ntfs.sys is having issues.
​Personally, I'd either rollback that machine or do a clean install (not an update).

 

[Sp12er]

Somehow... I'm finding out behavior that the error doesn't happen when its on battery... And, it only restart when I'm using it, (for example, I charge it then turn it on, blue screen in a few minutes) this is quite weird... Maybe some programs that only active when charging is conflicting? Not really wanting to rollback to 99xx ver as it wasn't as responsive as 10049 is

 

[Sp12er]

I've used msconfig to set the device to boot up only for diagnostic and... It still happens... Why is this happening? Do I really have to go back to 99XX build? Help anyone?

 

[ShinraCorp]

Actually I got the same thing. And it's not as pretty as it seems. NTFS.sys is the file Windows uses for it's file system and three things could cause this.
1. A hard drive or RAM that's going bad.
2. A program that's corrupted (if it happens at random something like an anti-virus could be the cause)
3. Windows 10 is just being weird.

I've ordered some new parts this week and going back to Windows 8 with it, if the problem persists then I know the issue is hard drive related.

 

[Jacob Chamberlain]

Glad it's not just me. I was having no issues until 10049 so I'm hoping 10051 or 10053 fixes it. And I'm 100 percent sure that the issue is in this current build because it started within a couple of hours after updating.

 

[Thabet-Abbas Burias]

This is also happening with my rig. Started within a couple of hours after updating to 10049. I'm going to try disabling my antivirus and revert to Defender, and see what happens.

 

[ShinraCorp]

Ok so after downgrading to Windows 8.1 and changing my hardware (CPU, MOBO AND RAM) the issue seemed to be fixed. I think it's a Windows 10 bug to be honest.

 

[hotphil]

Ok so after downgrading to Windows 8.1 and changing my hardware (CPU, MOBO AND RAM) the issue seemed to be fixed. I think it's a Windows 10 bug to be honest.

Seems a bit drastic to workaround a driver issue. But if it worked for you, cool!

 

[ShinraCorp]

Seems a bit drastic to workaround a driver issue. But if it worked for you, cool!

Nah it was just an excuse to buy new hardware for my 6 year old PC

 

[BasilAddington]

My Win 10 build 10049 also started BSOD'ing almost every hour after updating to this build. SO... I took the suggestion here and removed Bitdefender and reactivated Windows Defender.... No BSOD in over 5 hours!!!!! However, I have kept my fingers crossed...:smile:

 

[grapemon1611]

Same exact situation. Right after the latest update to 10049 the BSoD started. In addition to the System_Service_Exception (Ntfs.sys) error every time, when it came up my Belkin WiFi adapter would show "no available networks" and my Cisco VPN client would attempt to "complete installation" even though I installed it months ago.

After reading through this thread, I too uninstalled BitDefender. That was over an hour ago and so far, so good. I'll update later. I also uninstalled the Cisco VPN client (don't use it anymore, use LogMeIn or TeamViewer now). After the clean reboot, my WiFi was working properly.

Assuming this ends the BSoD at least until the next build, I'm wondering if the issue is actually the antivirus program or if it is a bug in the OS and it's just triggered by the antivirus when it does some sort of scan.

UPDATE: been 12 hours without a single reboot. I'm going to install a different antivirus product to see if that changes anything.