14936 upgrade complete, but BSOD after login

Same here, managed to start in safe mode and disable start up programs and that seems to have fixed it (praises demo gods). cldflt.sys description is "Cloud Files Mini Filter Driver" so OneDrive maybe? Shame we can not uninstall it from Windows 10 to see. But the only thing in my startup list in Task Manager that is Microsoft related is Skype and Windows Defender Notification. Not sure if those use cldflt.sys.

Wasn't able to rollback the insider update from safe mode but machine doesn't seem to be in a BSOD loop any more so I'll stick with it for now. Can't see an attach button (need more coffee) but if dump files are requested I can upload them somethere and provide links / find the attach button. The caused by address is cldflt.sys+362cc if that is help to anyone. If any info is requested give a shout and I'll get on it.

Filter drivers are kernel drivers so the only process that attach them is System (pid 4).

All running processes, that call into the kernel can fail when transitioning into this filter. But as the name hints, it could be some kind of cloud client, hard to tell without a kernel dump.

Here's a set of minidumps: cldflt BSOD dumps

Following Jack's advice, I started disabling startup items that would use the cloud. I disabled OneDrive first, but the BSOD still happened. I then disabled KeyBase and the BSODs stopped happening.

However, when I then tried to manually start OneDrive it gave me the sign-in window which threw 4 or 5 js errors. It just showed a blank white window.

Yesterday, before I disabled the startup items, I would see the same OneDrive sign-in window appear and the same set of js errors just before the BSOD happened.

> I then disabled KeyBase...

Just so happens that I also disabled keybase which was only installed very recently. May of found the cause (Keybase does have a cloud storage system - https://keybase.io/docs/kbfs ), I'll re-enable it and try again.

Enabled Keybase run on startup and the BSOD did return so I believe that is the cause. Guess its time to pester KeyBase on their GitHub.

Opened an issue on their client GitHub as i'm not 100% sure if its a client or kbfs issue.

https://github.com/keybase/client/issues/4470

https://github.com/keybase/keybase-issues/issues/2595

EDIT: added a link to the right repo and a prev report of this issue.

It's definitely KeyBase. I re-enabled OneDrive and I'm not getting the BSODs.

OneDrive still isn't working, though.

Edit: do you think I should make a new topic specifically for the OneDrive error?

Update: the OneDrive .js errors can be fixed by doing the following:

1: hold Win + R keys until the Run window pops up

2: type inetcpl.cpl and then hit OK

3: Under Browsing history, click on Delete...

4: In the Delete Browsing History window, click the Delete button.

5: Once it has finished, start OneDrive.