This is what's so really odd with Windows at times. It seemingly borked itself on FTDIBUS.SYS, but then was fine, even though there was still another FTDIBUS.SYS there, and was perfectly happy even when the other was reinstalled.
That suggests to me Windows is somehow 'getting its knickers in a twist' rather than it being an actual problem with the drivers. But when it does go wrong it seems impossible to figure out why.
It seems most .SYS files are reported to have been the cause of some BSOD at one time or another, even Microsoft's own, so one can only imagine it's something 'odd' which happens with Windows and things go downhill from there. Yet everything is fine once set back to how it was before Windows decided that wasn't okay.
The thing about Device Drivers, is that when loaded, they become a
part of the Operating System. They are not merely programs, that Windows "keeps an eye on" ... they
are Windows.
So in the case of the OP's problem,
something has driven FTDIBUS.SYS through a code path containing a bug, which has resulted in the default Exception Handler being invoked. Said Exception Handler instantly brings the system to a halt (because its integrity has been brought into doubt, the system is halted to avoid any further damage).
Since the analysis of the bugcheck reveals FTDIBUS.SYS to be the culprit, it's done something instantly detectable (divide-by-zero, or writing to readonly or non-existent virtual memory, for example). What sent FTDIBUS.SYS through that code is anyone's guess (without access to its source code) - but the aforementioned change-log documents a few known instances ... which seem to be related to 'surprise device removal'. (Perhaps Windows Update was attempting to load a new 'USB Controller' driver, that was signalling to its attached devices, that a config. change was occurring - but just guesswork on my part).
At least it wasn't one of the more dangerous types of bug, where a driver
succeeds in doing something untoward ... resulting in a system crash, some time later, in some seemingly random location.
... (not that I have had any non-recoverable BSOD events for some years, knock on wood).
That's a direct result of Microsoft's WHQL process.
The first version of the FT232R drivers that are certified for use on Windows 10, is
2.12.06, from July 2015