USBUIRT ftdibus.sys, SYSTEM_THREAD_EXCEPTION crash in Win10 - SOLUTION

[jksmurf]

Hi all,

I have been using a USBUIRT with GBPVR/NextPVR since 2004 and a recent Windows 10 update has given my first crash with that device. Rather, lots of crashes on windows startup, with SYSTEM_THREAD_EXCEPTION_NOT_HANDLED errors all over.
Analysis using "WhoCrashed" of 7 minidumps all look like below.

The only ftdibus.sys-based device on my PC is the USBUIRT.

This thread viewtopic.php?f=1&t=5606 describes how to roll your own driver, but initially I was too scared to try it.
But I did try and it seems to have worked. I am pretty pleased with myself

Code:

[url=http://usbuirt.com/phpBB3/viewtopic.php?f=2&t=8855&p=13894#]SELECT ALL[/url]On Mon 11/16/2015 12:37:02 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\111615-13828-01.dmp
This was probably caused by the following module: ftdibus.sys (ftdibus+0x9363)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF801CB054C90, 0xFFFFD0013DD9AF08, 0xFFFFD0013DD9A720)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\ftdibus.sys
product: FTDIChip CDM Drivers
company: FTDI Ltd.
description: FTDIBUS USB Driver
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: ftdibus.sys (FTDIBUS USB Driver, FTDI Ltd.).
Google query: FTDI Ltd. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

If you use this, you may need to follow his point 17 and sign it. I actually temporarily disabled unsigned drivers while it loaded but then used that.

Code:

17) at this point, the driver files will have been copied into their correct locations, but the driver will not load because it is unsigned. To deal with the unsigned driver, you need to take some extra measures:

a) download Driver Signature Enforcement Overrider 1.3b at [URL]http://www.ngohq.com/home.php?page=dseo[/URL]
b) right-click the downloaded file dseo13b.exe, and select "Run as administrator"
c) consider reading the instructions to understand what you will be doing
d) select "Enable Test Mode"
e) select "Sign a System File"
f) enter "c:\windows\system32\drivers\ftdibus.sys"

18) now the driver is signed. Reboot, and you should be set.

I am not sure if I am allowed to post it (sub or mods please remove if not) but it is attached for now.

I got the 2.12.06 drivers dated 28 Jul 2015 from here http://www.ftdichip.com/Drivers/VCP.htm

Cheers and I hope this helps someone.

Kristian