ckong

Brandonn, iCUE also BSODs for me unless I remove all the CpuId .dll files. I've documented the .dll files here https://forum.corsair.com/v3/showthread.php?t=200665&page=2 on post # 19. Basically, I have to always remove anything containing "cpuid" in it. Of course, this eliminates iCUE's ability to do system monitoring, but much better than having randomly BSOD.

I've honestly never heard of Riot Vanguard so I've never manually installed it. I also checked Control Panel > Programs and Features and there's no occurrence of that program. Btw, I've been running iCue 3.34.161 with the CpuID files removed since my last post about 2 weeks ago. No BSODs.

This update like all the other versions before it, continues to BSOD my computer after a seemly random amount of time (last time it took 4 hours). To "stabilize" it, I've used the old trick and removed the CpuId files from the "C:\Program Files (x86)\Corsair\CORSAIR iCUE Software" directory (there are 10 different files now): Corsair.Module.CpuId.dll Corsair.Module.CpuIdDevice.dll Corsair.Service.CpuIdRemote.exe Corsair.Service.CpuIdRemote.exe.config Corsair.Service.CpuIdRemote64.exe Corsair.Service.CpuIdRemote64.exe.config cpuidsdk.dll cpuidsdk64.dll CpuIdWrapper.dll CpuIdWrapper64.dll I've been running a full day with no crashes, but of course...no system monitoring. This was a real shame as I'm re-building my computer and was hoping to replace my old 3+ year old H60 with a new H115i or H150i CPU cooler. But since I won't be able to use iCUE to control the fans, I've ordered a competitor's AIO that works with the motherboard PWM headers instead. If anyone from Corsair is reading this, the CpuId BSOD bug is losing you sales. I want to buy more Corsair products, but avoid adding any more iCUE-dependant devices for fear of destabilizing my PC (I only use iCUE to support a K70 RGB MK.2 Low Profile keyboard...which is superior hardware imho). The last thread below may indicate a possible solution of using "industry standard synchronization mutexes". Not sure what that is, but it might be a clue. Corsair iCUE software causing PC crashes Black Screening / Video Card output switching off from iCUE https://forum.corsair.com/v3/showthread.php?t=177867&page=8 New Computer Crashing To Black Screen Have To Turn Off Power Supply To Restart https://forums.tomshardware.com/threads/new-computer-crashing-to-black-screen-have-to-turn-off-power-supply-to-restart.3372871/ Corsair iCUE program breaks after enabling sensors in AIDA64 https://forums.aida64.com/topic/5208-corsair-icue-program-breaks-after-enabling-sensors-in-aida64/

Possible fix in this thread: https://forum.corsair.com/v3/showthread.php?t=167998 From gboy's reply from Corsair Support: "Google Chrome has a driver that takes control of our media keys, preventing them from being used with Desktop apps while Chrome is open. To fix this issue: - Head to ‘Chrome://Flags - Locate Hardware ‘Media Key Handling’ - From the drop down set to ‘Disable’ If this didn't help please do let us know."

gboy, thanks for this. I've been running into this issue on my Corsair K70 RGB MK.2 Low Profile ever since I started to use the volume wheel. The problem has been very intermittent. I've applied this fix you shared. Crossing fingers it resolves the issue.

I just wanted to add to the thread that I tried #4 of the 5 tests (removal of cpuidsdk.dll), but with the addition of running iCUE. So far no BSOD for about a week.

Corsair K70 MK.2 Low Profile here. Purchased just last week Monday evening. BSOD on my Win10 64-bit machine about twice a day untill I did #2 of the 5 tests. PC been running fine so far, and iCUE is running in my system tray. Of course, the downside is that whatever the Service had controlled is not working.