Any news on this? I have the exact same problem as you did, have tried everything, but the damn driver keeps coming back.
BSOD Loop - CorsairVBusDriver.sys failure
After running optional system update for Corsair devices, my ASUS RoG G771 laptop is completely unusable. It's stuck in a BSOD reboot loop and not one recovery method is working. I wasn't provided a recovery disk with the laptop and apparently it's unable to boot from USB. I can't even reset the OS because it prompts for an outlook.com password and says the one I provide is incorrect (I've confirmed I am entering the latest password for the account and it's working on other devices). Safe mode doesn't work, either.
Others have posted this on the Corsair forum and the company doesn't answer. My laptop is now a boat anchor and I'm desperate for a solution...
Windows for home | Windows 10 | Performance and system failures
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
63 answers
Sort by: Oldest
-
Anonymous
2020-12-09T13:37:52+00:00 -
Anonymous
2020-12-09T15:05:04+00:00 Yea this is a **** disaster. My PC went ape this morning, failed to boot like 3 times, then I was able to do a restore and got back in. Immediately disabled Automatic Windows Updates (and likely will never re-enable them), uninstalled Corsair Utility Engine (I had an older unused version). Eventually, Windows prompted me to restore after multiple failed boots. I didn't boot with USB or into Safe.
I'm now hunting around for the CorsairVBusDriver.sys.
The driver is still in my C:\Windows\System32\drivers folder. Date on driver is 7/6/2020 -- however when I look at the File Repository and the SoftwareDistribution download folders, it seems that the files got pulled this morning at 9:18, which coincides exactly with when my machine went insane.
In my case I think Windows had been updated the version that did not play nice with the drivers and then the drivers updated and everything went to poo. When I restored I was able to revert back to an earlier version of Windows, the drivers seem to have stayed in place and work fine with this version of windows.
I rolled myself back to W10 Pro 2004 (build: 19041.630) -- I wish I could tell you which build I had been on. Probably 685?
I'd use this to get rid of the drivers.
https://github.com/lostindark/DriverStoreExplorer/releases/tag/v0.11.64
Make sure they are gone from all these:
C:\Windows\System32\DriverStore\FileRepository
C:\Windows\System32\drivers
C:\Windows\SoftwareDistribution\Download\Install (you will need to do this one manually)
Further, if you cannot get access to anything, or only cmd line, this may help: https://www.bleepingcomputer.com/forums/t/690502/bsod-cannot-boot-safemode-or-system-restore/
-
Anonymous
2020-12-09T17:07:10+00:00 Likewise, I had same issue when I woke up, today, to my Surface Pro 3 on a blue screen with the CorsairVBusDriver.sys error message. Unable to start up in Safe Mode and I am certainly not as savvy as those above in this thread^^
If anyone is able to help here, would be greatly appreciated.
-
Anonymous
2020-12-09T17:29:10+00:00 Youre going to want to use this article and follow the steps under "
How to do a System Restore without reaching the desktop in Windows 10 (from Advanced Boot Options)"
Its not an exact science but if you monkey around enough Windows will eventually let you do a restore to a point before the drivers and the windows update messed things up.
Then you need to stop it from happening again, disable windows and driver updates, remove Corsair Utility, remove the drivers like I have in my post above.
Then ideally backup a system image and slowly renable auto updates and update windows and hope it doesnt happen again.
-
Anonymous
2020-12-10T01:23:20+00:00 Any news on this? I have the exact same problem as you did, have tried everything, but the damn driver keeps coming back.
I came home today to my computer at the bios screen. Every reboot failed citing CorsairVbusDriver.sys. Did a system restore to 3 days ago. Got to desktop, everything seemed fine. BSOD 5 mins later, system crashed again citing CorsairVbusDriver.sys.