Recently released Windows 10 insider build 18309 is reportedly showing Green screen errors to some users informing bindflt.sys failed with System_service_exception as the stop code.
The blue screen of death replaced by green screen nowadays was shown to insiders in the fast ring when they shutdown or restart the system or while they’re using Windows 10. The affected users reported the issue in this forum thread and there are already feedback hup report with several upvotes on this issue to confirm the issue has happened to several users, go and upvote if you’ve experienced this with the build.
According to the forum post, the GSOD with bindflt.sys failed issue can be resolved with instructions given below.
1. Open command prompt as administrator and run following commands
2. SFC/Scannow
3. DISM /Online /Cleanup-Image /RestoreHealth
4. SC Config bindflt start= demand.
When a user posted in a Reddit thread about this and asked ” feedback items about GSODs in bindflt.syt are piling up for this build after a reboot today (I had been using 18309 for days without incident) it’s happening here too”, Microsoft’s Gentleman replied they’re tracking collected error info and looking into the issue.
What is bindflt.sys?
According to this website, bindflt is Windows Bind Filter driver service that binds file system namespaces to different locations and hides remapping from the users. If it fails to start then the error will be logged in Event Viewer, in that case, Windows 10 will tell the user the bindflt failed to start due to an error.
Are you affected?
Related articles:
Fix Resetting Windows 10 gives a Blue Screen Error: INACCESSIBLE BOOT_DEVICE