Jump to content
Corsair Community

Read this warning corsair~!


ifixit
 Share

Recommended Posts

Your about to get hundreds of people spam here because Ver 3.12 of iCUE Reboots to a blue screen message "inaccessible boot device."

 

Consider yourselves warned. I had a restore point. Will happen upgrading in ICUE and fully installing from installer.

 

Not sure if hardware specific..but lucky i had a restore point.

Link to comment
Share on other sites

  • Corsair Employees

This happens because of a preinstalled USB driver being installed and conflicting with the iCUE driver. The two drivers can't work together, they don't launch, causes a boot loop.

 

Weirdly enough, it tends to be associated with an older CD/DVD drives that are using a fairly obnoxious driver. If you have one connected, try removing it.

 

Otherwise, we would suggest making sure that your computer's Antivirus/Firewall software is turned off while iCUE is installing to prevent the software from quarantining necessary installation files.

 

You can also use this MSI installer tool to help correct a lot of issues caused by .msi files: https://support.microsoft.com/en-ca/help/17588/windows-fix-problems-that-block-programs-being-installed-or-removed

Link to comment
Share on other sites

This happens because of a preinstalled USB driver being installed and conflicting with the iCUE driver. The two drivers can't work together, they don't launch, causes a boot loop.

 

Weirdly enough, it tends to be associated with an older CD/DVD drives that are using a fairly obnoxious driver. If you have one connected, try removing it.

 

Otherwise, we would suggest making sure that your computer's Antivirus/Firewall software is turned off while iCUE is installing to prevent the software from quarantining necessary installation files.

 

You can also use this MSI installer tool to help correct a lot of issues caused by .msi files: https://support.microsoft.com/en-ca/help/17588/windows-fix-problems-that-block-programs-being-installed-or-removed

 

 

Yeah ok, DVD/CD less system

Not running AV

 

PS been using icue fine till this particular version.

 

Heed my warning troubles coming,

Link to comment
Share on other sites

Just because it happens to you doesn't mean that it's widespread. I'm running on several machines and haven't seen that and no one on the community beta team has seen it either. That's a larger sample with no issues than your single system.

 

So perhaps you should take Corsair Calico Jack's suggestion to heart and look and see if there's something conflicting on your system rather than coming in here like Chicken Little.

Link to comment
Share on other sites

Yeah, I just updated to the latest version as well, and had zero problems. I'm running a tower with at least a 4 year old if not more disc drive, and always running AV software - why would you ever connect a computer to the internet and NOT have AV?! Either way, I have had troubles with iCUE in the past but this update was probably the smoothest so far.
Link to comment
Share on other sites

Your about to get hundreds of people spam here because Ver 3.12 of iCUE Reboots to a blue screen message "inaccessible boot device."

 

Consider yourselves warned. I had a restore point. Will happen upgrading in ICUE and fully installing from installer.

 

Not sure if hardware specific..but lucky i had a restore point.

 

Yeah, haven't had this occur either (not saying it didn't happen to you). To give such an apocalyptic warning made this sound like it was a widespread issue...

Link to comment
Share on other sites

I have some of the same hardware and have not had any boot problem, only the recurring problem of Vengeance RGP Pro RAM not showing in iCUE. Below is the hardware and drivers I'm using and some UEFI settings I tested a moment ago to try and create your situation; thankfully no dice.

 

I too have a 2700X and 970 EVO 500GB NVMe boot drive (Samsung NVMe Controller driver, 3.0.0.1802), 2TB of SSDs and 4TB of HDDs, (AMD Virtualized AHCI driver for StoreMi, 11.5.35.252, Microsoft Storage Spaces controller driver), AHCI mode, no RAID setup, Vengeance RGB Pro (3000, 2X8), H115i Pro AIO, 3X LL120 fans but ASUS ROG STRIX X470-F motherboard and have not had any boot problems. Internal USB 2.0 ports used by H115i Pro and Lighting Node Pro, External USB ports connected to two pairs of peripherals, DAC/headset, mouse mat, DS4 (AMD, ASMedia, Corsair and Windows USB drivers). I'm running all the latest versions of BIOS, drivers and Windows 10 Pro. I even tested the following UEFI/BIOS settings and all worked: Normal boot, fast boot, CSM enabled, CSM disabled (UEFI, Windows secure boot enabled), USB legacy and AHCI handoff enabled or disabled.

 

All in an Obsidian 500D too, so it's definitely not the case :cool:

Edited by RiverM
Link to comment
Share on other sites

I have some of the same hardware and have not had any boot problem, only the recurring problem of Vengeance RGP Pro RAM not showing in iCUE. Below is the hardware and drivers I'm using and some UEFI settings I tested a moment ago to try and create your situation; thankfully no dice.

 

I too have a 2700X and 970 EVO 500GB NVMe boot drive (Samsung NVMe Controller driver, 3.0.0.1802), 2TB of SSDs and 4TB of HDDs, (AMD Virtualized AHCI driver for StoreMi, 11.5.35.252, Microsoft Storage Spaces controller driver), AHCI mode, no RAID setup, Vengeance RGB Pro (3000, 2X8), H115i Pro AIO, 3X LL120 fans but ASUS ROG STRIX X470-F motherboard and have not had any boot problems. Internal USB 2.0 ports used by H115i Pro and Lighting Node Pro, External USB ports connected to two pairs of peripherals, DAC/headset, mouse mat, DS4 (AMD, ASMedia, Corsair and Windows USB drivers). I'm running all the latest versions of BIOS, drivers and Windows 10 Pro. I even tested the following UEFI/BIOS settings and all worked: Normal boot, fast boot, CSM enabled, CSM disabled (UEFI, Windows secure boot enabled), USB legacy and AHCI handoff enabled or disabled.

 

All in an Obsidian 500D too, so it's definitely not the case :cool:

 

You're likely better off creating a new thread for your issue rather than jumping on this one.

 

That said, there have been reports of issues specifically with Asus Ryzen motherboards and a particular BIOS release. Going back to an earlier BIOS has solved issues for many folks.

Link to comment
Share on other sites

You're likely better off creating a new thread for your issue rather than jumping on this one.

 

That said, there have been reports of issues specifically with Asus Ryzen motherboards and a particular BIOS release. Going back to an earlier BIOS has solved issues for many folks.

 

I've already posted about the RAM issue in another thread and about a temporary fix with reverting first to an older BIOS for that particular board. I was replying to the OP here since I have the same boot drive and chipset and have heard of numerous boot problems with X470 after the OS install when not installing Samsung's driver.

Link to comment
Share on other sites

I've already posted about the RAM issue in another thread and about a temporary fix with reverting first to an older BIOS for that particular board. I was replying to the OP here since I have the same boot drive and chipset and have heard of numerous boot problems with X470 after the OS install when not installing Samsung's driver.

 

Ah ... OK, I missed that. There seem to be numerous issues with X470 ... period. :[pouts:

Link to comment
Share on other sites

Ah ... OK, I missed that. There seem to be numerous issues with X470 ... period. :[pouts:

 

NO. Your software is garbage. Its well documented here.

Stop blaming your customers for your crap software. Telling people to roll back their bios ? REALLY? Its not them ,its YOU.

Unbelievable. Id fire you and your staff if it were up to me. This has been going on for years.

Link to comment
Share on other sites

Just because it happens to you doesn't mean that it's widespread. I'm running on several machines and haven't seen that and no one on the community beta team has seen it either. That's a larger sample with no issues than your single system.

 

So perhaps you should take Corsair Calico Jack's suggestion to heart and look and see if there's something conflicting on your system rather than coming in here like Chicken Little.

 

Fair enough, i over egged it. Happened to me and assumed, ..but it was just a warning, with good intent in mind.

 

Pardon me for getting it wrong.

 

However personally my vengence RGB is stuck on red. I can't update icue without the boot device blue screen. Not sure where to head with this,

Link to comment
Share on other sites

Yeah, I just updated to the latest version as well, and had zero problems. I'm running a tower with at least a 4 year old if not more disc drive, and always running AV software - why would you ever connect a computer to the internet and NOT have AV?! Either way, I have had troubles with iCUE in the past but this update was probably the smoothest so far.

 

Never used an AV, never had a virus. don't open attachments in email from unknown sources, or that look suspicious. Don't go to porn sites. avoid dodgy wed sites. Use common sense.

Link to comment
Share on other sites

I'll try updating one more time.

 

Well this time i had gone back to 3.10 turned off enable SDK,

 

updated without a hitch. :)

 

Still my rams stuck on red . I was updating in the hope it would come back to life. It's also not detecting in Icue

Link to comment
Share on other sites

NO. Your software is garbage. Its well documented here.

Stop blaming your customers for your crap software. Telling people to roll back their bios ? REALLY? Its not them ,its YOU.

Unbelievable. Id fire you and your staff if it were up to me. This has been going on for years.

 

Hey genius ... did you read my signature? I DON'T WORK FOR CORSAIR. I'm here on my own time help folks out.

 

Now - the issue with the BIOS is well known. Is it iCUE? Is it the BIOS? Is it Asus (since it seems to mostly be Asus boards)? I've no clue. I do know that many users have had issues when they update the BIOS. Since it's pretty specific to that chipset and BIOS ... I suspect that's where the issue is. Heck ... even another user pointed out issues with Samsung drives and that chipset. So it ain't just the Corsair stuff.

 

And there are plenty of folks that use iCUE without issue (myself included). Most don't post here because ... well ... there's no reason to. So all you see are the issues.

Link to comment
Share on other sites

Well this time i had gone back to 3.10 turned off enable SDK,

 

updated without a hitch. :)

 

Still my rams stuck on red . I was updating in the hope it would come back to life. It's also not detecting in Icue

 

Try reverting back to the previous BIOS. There have been many reports of issues with the RAM after updating the X470 BIOS that are magically fixed when it's reverted. I have to wonder if SPD Write is disabled in that BIOS - that would explain it. But SPD Write is a memory setting that I've never heard of being visible on a Ryzen system (it is visible on Intel). Or ... maybe ... it's now visible and just disabled by default. So perhaps look for it.

Link to comment
Share on other sites

  • 2 months later...

Came here to tell that i have had the same experience when upgrading iCUE to the latest version. First the system became sluggish with repeated stalls.

The System event log has lots of Event ID 7045 from the Service Control Manager about GPIO and I2C driver being installed.

Next thing that happens is Event ID 225 (Kernel-PnP) where a harddisk volume stops working, a sample message looks like this:

The application \Device\HarddiskVolume7\Windows\System32\wininit.exe with process id 1112 stopped the removal or ejection for the device PCI\VEN_1179&DEV_0116&SUBSYS_00011179&REV_00\4&d3fd913&0&00D8.

 

For what its worth i am on Windows 1903 (18362.86), so perhaps this is a case of more testing of Windows Insider builds is required.

 

In any case i am thankful for reading about this potential problem and that it is software related.

Link to comment
Share on other sites

  • Corsair Employees
Came here to tell that i have had the same experience when upgrading iCUE to the latest version. First the system became sluggish with repeated stalls.

The System event log has lots of Event ID 7045 from the Service Control Manager about GPIO and I2C driver being installed.

Next thing that happens is Event ID 225 (Kernel-PnP) where a harddisk volume stops working, a sample message looks like this:

The application \Device\HarddiskVolume7\Windows\System32\wininit.exe with process id 1112 stopped the removal or ejection for the device PCI\VEN_1179&DEV_0116&SUBSYS_00011179&REV_00\4&d3fd913&0&00D8.

 

For what its worth i am on Windows 1903 (18362.86), so perhaps this is a case of more testing of Windows Insider builds is required.

 

In any case i am thankful for reading about this potential problem and that it is software related.

 

Can you provide us with your system information and the blue screen dump?

Link to comment
Share on other sites

  • 9 months later...
Your about to get hundreds of people spam here because Ver 3.12 of iCUE Reboots to a blue screen message "inaccessible boot device."

 

Consider yourselves warned. I had a restore point. Will happen upgrading in ICUE and fully installing from installer.

 

Not sure if hardware specific..but lucky i had a restore point.

 

YES you were right.... i hate to see all the comments of people being like im fine , the other guy fine and everyone fine ...

this is a real issue .

My laptop is CD / DVD less and i still got this blue screen after updating corsair

.

I had no restore point so i had to revert the laptop to defaults while saving my files in hopes i dont loose my university work.

Clean Install with keeping files , from the image on the laptop itself did not work.

Next i will try a USB with the latest Windows 10 and that did not work.

so im going to boot into ubuntu to get the files out.

After taking the important stuff out i was forced to install windows 10 from cero and then restore the files.

 

 

CORSAIR FIX THIS!!!!!

Link to comment
Share on other sites

 Share

×
×
  • Create New...