Windows 10: Windows 10’s new Corsair driver update is causing boot failures

Some Windows 10 drivers are necessary for your devices, which is why we’ve both automatic and optional driver updates. However, driver updates can also prevent your devices from working under rare circumstances.

A new driver update “CorsairVBusDriver” is currently rolling out to some users via Windows Update and it’s reportedly breaking down PCs. The latest driver is incompatible with the old CorsairVBusDriver (driver version is 2.x or older) and BSOD is triggered when the older driver is detected.

In some instances, users have found that the compatibility issues between the new and old drivers result in a loop of Blue Screen of Death errors.



While Microsoft has yet to respond to the reports, Corsair has confirmed that it’s aware of the problem.

“This is caused by a very old CorsairVBusDriver (driver version is 2.x or older) installed with old CUE SW (CUE 2.x or older) conflicting with the new driver (driver version is 3.x) released with the recent Windows update,” wrote James, ICUE product manager at Corsair.

If you have a Corsair update pending in the Windows Update page, you need to uninstall the old Corsair’s CUE software and download the iCUE software, and then apply the Windows Updates.

For those stuck in a Blue Screen of Death with “CorsairVBusDriver.sys” stop code error, follow these steps:

• In the Windows Recovery Environment, select Troubleshoot.
• Select Advanced Options > System Restore. When you click on System Restore, Windows will retry to recover your operating system using the recovery partition and it won’t affect your personal files, but it will remove recently installed apps, drivers, etc.
• Create a bootable media drive and recover your PC manually.

Advanced users can also follow our workaround to fix issues with CorsairVBusDriver.sys in Windows 10 version 2004 or newer.

This incident is another reminder for users to avoid the necessary driver updates offered via Windows Update. As we have reported before, optional updates for Intel, Nvidia, AMD or other products can relegate your drivers to an old or default version. In other words, you should avoid optional updates if the hardware is fully functional.

The post Windows 10’s new Corsair driver update is causing boot failures appeared first on Windows Latest

Weiterlesen...

 

New Secondary Drive Causes Boot Failure Windows 10

For the second time now, Windows 10 failed to boot after initializing and formatting a spare drive (using Windows Disk Management). After the boot fail, UEFI boot settings were still set to boot from Windows Boot Manager, but it still wouldn't boot, just goes into diagnostic mode, fails to repair boot problem, and goes to the repair menu. In advanced options I can then load a recent image (made with Windows 7 Backup and Recovery in control panel), and everything goes back to normal. My question is what causes this problem, and how do I repair it without re-imaging Windows? I don't recall ever having this problem in other Windows versions, only in Windows 10. Anyone else notice this problem?

 

Confusing Disk Boot Failure

Well, Brand new Harddrive the western digital se16 caviar 640. Had a clean install, and while installing drivers and programs after a couple restarts I am receiving disk boot failure. Not the first restart or the second. Each time that it has given me the failure was after installing updates. I've system restored to before installing the updates and it works fine. It's a large list of around 38 or so updates. Granted may be a fluke but anyone heard of this?



P5N-E SLi
E6420
OCZ Platinum 2 x 1 kit
WD 640gb

 

New Secondary Drive Causes Boot Failure Windows 10

No, I didn't install Windows on anything - I'm saying that on my high-end Windows 10 Pro x64 PC, which by the way has Windows installed on a 400GB Intel 750 Series AIC, when I simply initialize and partition a new storage drive (HDD or SSD), just that, not put anything at all on the drive, just a new, empty, bare drive. When you first plug it in, a Windows dialog pops up, saying that the new disc needs to be initialized, so it can be seen by Windows Disk Management, asking if you want it use MBR or GPT partition table. Then I used Windows Disk Management to format the drive as NTFS in the full available size and assign it a drive letter (or leave it unassigned - doesn't matter). Everything normal, except the new drive doesn't show up in Windows Explorer (My computer). So I reboot, and the aforementioned failure to boot occurs. After I get back into Windows, by loading a recent system image onto my Intel 750 Series AIC boot drive, everything is working fine, and the new drive shows up in Windows Explorer as an empty but fully functional drive, with just the one partition, as normal (and I checked it with MiniTool Partition Wizard, no extra system or hidden partitions). This happened the first time with a 1 TB HDD installed to a SATA port on my motherboard. This latest time it was an SSD connected to my PC through an external USB 3 drive dock - with the same result and fix. Maybe I shouldn't use the built in Windows utilities, I should just use MiniTool to initialize and partition the drive, but I still want to know why Windows behaves this way.