G
Guest
I realize that Microsoft OCA diagnose every BSOD as a driver problem, but
sometimes the BSOD really does result from a driver problem.
KB article 817197 says that version 4.6 of the SAUSB.SYS Lexar driver (the
latest one available from the LEXAR site) fixes the known BSOD problem with
this product.
NOT TRUE!
Even uninstalling the card reader device and the software is not enough, you
have to go into C:\WINDOWS\system32\drivers and manually remove the SAUSB.SYS
and SESAUSB.SYS files in order to cure the problem.
I got hold of a driver that appears to work fine with Windows XP and my
GS-UFD-20SA-TP from http://www.usb-drivers.com/drivers/54/54144.htm: CAUSB.SYS
Both the SAUSB.SYS and CAUSB.SYS drivers fail the Microsoft "verifier"
test, but CAUSB.SYS does not appear to cause any problems - at least on my
XP pro 5.1 sp2 system.
sometimes the BSOD really does result from a driver problem.
KB article 817197 says that version 4.6 of the SAUSB.SYS Lexar driver (the
latest one available from the LEXAR site) fixes the known BSOD problem with
this product.
NOT TRUE!
Even uninstalling the card reader device and the software is not enough, you
have to go into C:\WINDOWS\system32\drivers and manually remove the SAUSB.SYS
and SESAUSB.SYS files in order to cure the problem.
I got hold of a driver that appears to work fine with Windows XP and my
GS-UFD-20SA-TP from http://www.usb-drivers.com/drivers/54/54144.htm: CAUSB.SYS
Both the SAUSB.SYS and CAUSB.SYS drivers fail the Microsoft "verifier"
test, but CAUSB.SYS does not appear to cause any problems - at least on my
XP pro 5.1 sp2 system.