Black Screening / Video Card output switching off from iCUE

jergarmy · January 22, 2019

I am also at a loss on this one and am out of options... I changed the names of the cpuids and i'm still getting constant black screens. Asus Sabertooth X79 with an 4930k CPU (from what I understand it seems to be Asus mobo issues)?

Kriegpig · January 22, 2019

@Jergarmy

the only way to keep your computer from (for now) blackscreening is disable the startup of anything Corsair. that'll change if they add support for the X79 chipset and it looks like ASUS boards.

I'm also getting the blackscreens on my EVGA X79 Dark board.

omcilvain · January 24, 2019

Having the same exact issue and from the look of this thread is has been going on for way to long to have any hope of this being fixed anytime soon. Since having ICue installed on my system is what is causing all of the problems I have been having (removing it fixes them) I can't keep this software installed, thus all Corsairs product that I have (mouse, keyboard, cooling, headset) are dependent on this software they are of no use to me and are a liability. So guess its good buy Corsair and on to a different brand who hopefully don't implement a software programs such as ICancer. here are my logs for just the last hour or two...good luck Corsair

Log Name: Application

Source: Application Error

Date: 1/24/2019 12:01:27 AM

Event ID: 1000

Task Category: (100)

Level: Error

Keywords: Classic

User: N/A

Computer: DESKTOP-AFT7JKD

Description:

Faulting application name: iCUE.exe, version: 3.11.114.0, time stamp: 0x5c18fe4b

Faulting module name: VCRUNTIME140.dll, version: 14.0.24215.1, time stamp: 0x57bfd587

Exception code: 0xc0000005

Fault offset: 0x0000d160

Faulting process id: 0x15d0

Faulting application start time: 0x01d4b3b1c1ac85f5

Faulting application path: C:\Program Files (x86)\Corsair\CORSAIR iCUE Software\iCUE.exe

Faulting module path: C:\Windows\SYSTEM32\VCRUNTIME140.dll

Report Id: e52e1a23-6519-4d47-84c9-ed7d80df6122

Faulting package full name:

Faulting package-relative application ID:

Event Xml:

<Channel>Application</Channel>

<Computer>DESKTOP-AFT7JKD</Computer>

</System>

<Data>VCRUNTIME140.dll</Data>

<Data>C:\Program Files (x86)\Corsair\CORSAIR iCUE Software\iCUE.exe</Data>

<Data>C:\Windows\SYSTEM32\VCRUNTIME140.dll</Data>

<Data>

</Data>

<Data>

</Data>

</EventData>

</Event>

Log Name: Application

Source: Application Error

Date: 1/24/2019 12:03:52 AM

Event ID: 1000

Task Category: (100)

Level: Error

Keywords: Classic

User: N/A

Computer: DESKTOP-AFT7JKD

Description:

Faulting application name: iCUE.exe, version: 3.11.114.0, time stamp: 0x5c18fe4b

Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000

Exception code: 0xc0000005

Fault offset: 0x6e6f633a

Faulting process id: 0x403c

Faulting application start time: 0x01d4b3b2c926d975

Faulting application path: C:\Program Files (x86)\Corsair\CORSAIR iCUE Software\iCUE.exe

Faulting module path: unknown

Report Id: 12b26270-1e77-4c47-bfe4-8780be527b83

Faulting package full name:

Faulting package-relative application ID:

Event Xml:

<Channel>Application</Channel>

<Computer>DESKTOP-AFT7JKD</Computer>

</System>

<Data>unknown</Data>

<Data>C:\Program Files (x86)\Corsair\CORSAIR iCUE Software\iCUE.exe</Data>

<Data>unknown</Data>

<Data>

</Data>

<Data>

</Data>

</EventData>

</Event>

Log Name: Application

Source: Application Error

Date: 1/24/2019 12:23:07 AM

Event ID: 1000

Task Category: (100)

Level: Error

Keywords: Classic

User: N/A

Computer: DESKTOP-AFT7JKD

Description:

Faulting application name: iCUE.exe, version: 3.11.114.0, time stamp: 0x5c18fe4b

Faulting module name: VCRUNTIME140.dll, version: 14.0.24215.1, time stamp: 0x57bfd587

Exception code: 0xc0000005

Fault offset: 0x0000d3f0

Faulting process id: 0x3e58

Faulting application start time: 0x01d4b3b5a1ed77bb

Faulting application path: C:\Program Files (x86)\Corsair\CORSAIR iCUE Software\iCUE.exe

Faulting module path: C:\Windows\SYSTEM32\VCRUNTIME140.dll

Report Id: 098b48c1-43e8-4a57-973e-86f31dd6e395

Faulting package full name:

Faulting package-relative application ID:

Event Xml:

<Channel>Application</Channel>

<Computer>DESKTOP-AFT7JKD</Computer>

</System>

<Data>VCRUNTIME140.dll</Data>

<Data>C:\Program Files (x86)\Corsair\CORSAIR iCUE Software\iCUE.exe</Data>

<Data>C:\Windows\SYSTEM32\VCRUNTIME140.dll</Data>

<Data>

</Data>

<Data>

</Data>

</EventData>

</Event>

Log Name: Application

Source: Application Error

Date: 1/24/2019 12:30:45 AM

Event ID: 1000

Task Category: (100)

Level: Error

Keywords: Classic

User: N/A

Computer: DESKTOP-AFT7JKD

Description:

Faulting application name: iCUE.exe, version: 3.11.114.0, time stamp: 0x5c18fe4b

Faulting module name: VCRUNTIME140.dll, version: 14.0.24215.1, time stamp: 0x57bfd587

Exception code: 0xc0000005

Fault offset: 0x0000d3f0

Faulting process id: 0x4394

Faulting application start time: 0x01d4b3b5b001ed79

Faulting application path: C:\Program Files (x86)\Corsair\CORSAIR iCUE Software\iCUE.exe

Faulting module path: C:\Windows\SYSTEM32\VCRUNTIME140.dll

Report Id: cc08db1f-43d7-4ee0-8386-7b1b9d397ece

Faulting package full name:

Faulting package-relative application ID:

Event Xml:

<Channel>Application</Channel>

<Computer>DESKTOP-AFT7JKD</Computer>

</System>

<Data>VCRUNTIME140.dll</Data>

<Data>C:\Program Files (x86)\Corsair\CORSAIR iCUE Software\iCUE.exe</Data>

<Data>C:\Windows\SYSTEM32\VCRUNTIME140.dll</Data>

<Data>

</Data>

<Data>

</Data>

</EventData>

</Event>

Log Name: Application

Source: Application Error

Date: 1/24/2019 12:51:27 AM

Event ID: 1000

Task Category: (100)

Level: Error

Keywords: Classic

User: N/A

Computer: DESKTOP-AFT7JKD

Description:

Faulting application name: iCUE.exe, version: 3.11.114.0, time stamp: 0x5c18fe4b

Faulting module name: Qt5Gui.dll, version: 5.9.4.0, time stamp: 0x5a5da519

Exception code: 0xc0000005

Fault offset: 0x00270e40

Faulting process id: 0x215c

Faulting application start time: 0x01d4b3b9731d2edd

Faulting application path: C:\Program Files (x86)\Corsair\CORSAIR iCUE Software\iCUE.exe

Faulting module path: C:\Program Files (x86)\Corsair\CORSAIR iCUE Software\Qt5Gui.dll

Report Id: d449ee23-4487-4b31-8151-c28e6b85f41a

Faulting package full name:

Faulting package-relative application ID:

Event Xml:

<Channel>Application</Channel>

<Computer>DESKTOP-AFT7JKD</Computer>

</System>

<Data>C:\Program Files (x86)\Corsair\CORSAIR iCUE Software\iCUE.exe</Data>

<Data>C:\Program Files (x86)\Corsair\CORSAIR iCUE Software\Qt5Gui.dll</Data>

<Data>

</Data>

<Data>

</Data>

</EventData>

</Event>

Log Name: Application

Source: Application Error

Date: 1/24/2019 12:51:29 AM

Event ID: 1000

Task Category: (100)

Level: Error

Keywords: Classic

User: N/A

Computer: DESKTOP-AFT7JKD

Description:

Faulting application name: iCUE.exe, version: 3.11.114.0, time stamp: 0x5c18fe4b

Faulting module name: Qt5Gui.dll, version: 5.9.4.0, time stamp: 0x5a5da519

Exception code: 0xc000041d

Fault offset: 0x00270e40

Faulting process id: 0x215c

Faulting application start time: 0x01d4b3b9731d2edd

Faulting application path: C:\Program Files (x86)\Corsair\CORSAIR iCUE Software\iCUE.exe

Faulting module path: C:\Program Files (x86)\Corsair\CORSAIR iCUE Software\Qt5Gui.dll

Report Id: 9c8656a4-f24c-41ca-b564-a36f1fe0e940

Faulting package full name:

Faulting package-relative application ID:

Event Xml:

<Channel>Application</Channel>

<Computer>DESKTOP-AFT7JKD</Computer>

</System>

<Data>C:\Program Files (x86)\Corsair\CORSAIR iCUE Software\iCUE.exe</Data>

<Data>C:\Program Files (x86)\Corsair\CORSAIR iCUE Software\Qt5Gui.dll</Data>

<Data>

</Data>

<Data>

</Data>

</EventData>

</Event>

thunderdolt · January 24, 2019

Looks like I solved the problems with my grownup work software crashing. Turns out that the solution was simple: disable Corsair's children's toy software.

Instantly went from crashes on 10/10 attempts to crashes on 0/10 attempts.

WhiskeyOmega · January 25, 2019

They cannot fix this issue because its not their software its the SDK its built on and apparently they can no longer find a X79 board and cpu to test it with. The only way to go around it is to rename cpuidksdk.dll and cpuidksdk64.dll and thus remove the sensor reading from the cpu and prey your cooling is enough that the temps dont get too high. Im stuck and disappointed in Corsair but what else can be done?

meleemike · January 26, 2019

@ WhiskyOmega - except the fact that this is not limited to X79 boards - I have a ASUS PRIME Z370-A LGA1151 and i7 8700k (both of which are easy to get a hold of) and have the same issue. You can use the old version of the software just known as "CUE" to get around it -still hosted on corsairs site - http://downloads.corsair.com/download?item=Files/CUE/CorsairUtilityEngineSetup_2.24.50_release.msi

Pyretech · January 28, 2019

This is also happening with my i5-6600k and ASUS Z170-AR. I would definitely love an update!

thobber · January 28, 2019

And it is happening with my Ryzen 5 2600X on an ASUS X470-f board. So it seems like its mainly on Asus boards, and not specifically chipsets.

Pyretech · January 29, 2019

I have ordered an MSI PRO Z270 board that should arrive at my house on Thursday, and I will post an update as to whether or not the crash happens on that. This didn't happen on my old MSI board but I didn't have my H100i or Vengeance Pro RGB at the time, so I'm curious whether or not it will happen there.

Pyretech · February 1, 2019

Update on MSI board - still having the same problem. Does not seem to be localized to ASUS boards.

Edit: My issue may be separate as it does not appear to be happening with my GTX 970 graphics card, just my Vega 64. Will be doing further testing to make 100% certain.

Edited February 2, 2019 by Pyretech
clarification on issue

8link · February 3, 2019

Same problem here!

Asus Rampage IV Black Edition x79 chipset, 4960X CPU, ASUS Strix GTX980 GPU

I was struggling with black screen problem since I've installed Windows 10 few weeks ago. I was going to revert back to Win 7, which didn't had that problem.

But i found that the Corsair software is causing the issue. I've disabled Corsair Link and it seams that problem is gone.

Hope that someone can find some workaround.

thobber · February 3, 2019

After the latest update (3.11.114), I havent gotten any black screens (yet) and I can see all the temps from ASUS, GPU, CPU and coolant in iCUE.

3 days without a black screen atm

raptor734 · February 4, 2019

It's an absolute godsend to have found this thread. I've had this same issue for almost a year now and I recently decided that I can't take it anymore. Did some Google-fu which took me everywhere from bad drivers to bad hardware. To finally have found a solid answer is quite the relief.

When I started reading the thread, I perhaps got too eager that I may have finally found a solution that I immediately uninstalled both CLINK4 and iCUE. The problem is that I'm still crashing despite uninstalling them.

Are there any residual files that I might have missed?

Should I reinstall them and then uninstall them in a certain order?

Thanks for the help. I hope we can all get back to a crash-free lifestyle.

meleemike · February 6, 2019

@raptor734 - When you say:

"The problem is that I'm still crashing despite uninstalling them."

Could you describe exactly what you mean by that? Specifically, does your PC blue screen? Black screen? Does it ever recover? Any sound abnormalities if you are playing music or watching youtube etc when it happens?

If it was just iCUE causing your crashes it should have stopped when iCUE was uninstalled.

You may want to DL and run bluescreenview and see what your latest crash logs show is making you crash now that you uninstalled iCUE.

https://www.nirsoft.net/utils/blue_screen_view.html

meleemike · February 6, 2019

After the latest update (3.11.114), I havent gotten any black screens (yet) and I can see all the temps from ASUS, GPU, CPU and coolant in iCUE.
3 days without a black screen atm

How about now? Still crash free? Anyone else try the newest and willing to report?

Kriegpig · February 6, 2019

Hi meleemike,

I installed it last night, so far so good. I'll update when I get home tonight.

Cheers

thobber · February 6, 2019

How about now? Still crash free? Anyone else try the newest and willing to report?

Still good! Haven't had any problems what so ever.

Can't think of anything else I did, other than update to the newest version. Tried stresstesting, running games (BO4, Overwatch, and some random other games) and still no black screen.

So as far as I can see, they might've fixed it in the newest update.

(When I check the iCue folder, it still has the same cpuidsk dll files, so they haven't removed them)

kangelbaer · February 6, 2019

Just a week old windows and computer. Bought the harpoon wireless, k63 wireless and k63 lapboard today. Plugged the usb dongles and was so pleased that both the mouse and keyboard worked immediately. And the lapboard is actually nice and comfy!

Downloaded and installed iCue. Had about 2min of time with the software aaand -black screen- ... Had to cut power from psu to boot.

Ok, windows up and running. about half a minute and black screen again...

Psu power switch off and on. Windows startup aaand the same blackscreen after just under a minute...

After uninstalling iCue everyting back to normal. Some google and here I am.

So what should I do. I only want to manage the keyboard macros and mouse settings. Do corsair have any separate software for that? Or should i try the "Rename or delete cpuidsdk.dll"? Or maby just return all the stuff..

thobber · February 6, 2019

Just a week old windows and computer. Bought the harpoon wireless, k63 wireless and k63 lapboard today. Plugged the usb dongles and was so pleased that both the mouse and keyboard worked immediately. And the lapboard is actually nice and comfy!
Downloaded and installed iCue. Had about 2min of time with the software aaand -black screen- ... Had to cut power from psu to boot.

Ok, windows up and running. about half a minute and black screen again...

Psu power switch off and on. Windows startup aaand the same blackscreen after just under a minute...

After uninstalling iCue everyting back to normal. Some google and here I am.

So what should I do. I only want to manage the keyboard macros and mouse settings. Do corsair have any separate software for that? Or should i try the "Rename or delete cpuidsdk.dll"? Or maby just return all the stuff..

Renaming the different cpuidskd files should work.

But did you try to download the latest update? It worked for me, no black screens since.

kangelbaer · February 6, 2019

Renaming the different cpuidskd files should work.
But did you try to download the latest update? It worked for me, no black screens since.

Well i downloaded it from corsairs site today, v3.11.114. It should be the latest version? And then there is the problem that with the iCue installed i only have like 30-60sec after boot til the black screen. Maby if i do it in safe mode... Ill give it I try when i have time to.

RiverM · February 6, 2019

If I just bought the stuff and had a constant black screen when using the required software, I'd return it all and post reviews anywhere I could. I'm not having the problem but would be extremely vocal if I was.

SaltyCrumbs · February 6, 2019

Built my pc 1 month ago and just installed the iCUE software today and it started crashing my pc right away. How is there no fix for this yet?

kangelbaer · February 7, 2019

If I just bought the stuff and had a constant black screen when using the required software, I'd return it all and post reviews anywhere I could. I'm not having the problem but would be extremely vocal if I was.

I cant find any other wireless keyboard suited for gaming. And i need the icue to set the color to static.. now when i put on the backlights it has som damn carnival setting.. I still hav a month time to try out the stuff so maby ill give the icue tweaks a shot.

kangelbaer · February 7, 2019

Before I edit or delete the cpuidsdk.dll. Will it mess up anyting else in my system. I can remember someone mentioning that the fans will start to fail? Sounds like a too big of a risk..

thobber · February 7, 2019

Before I edit or delete the cpuidsdk.dll. Will it mess up anyting else in my system. I can remember someone mentioning that the fans will start to fail? Sounds like a too big of a risk..

Shouldn't be any issues.

I could still control and see my H115i Pro cooler even after editing the .dll files.

What do you control through iCue? I dont know what it will do if you have a commander pro or something to control your fans, but assume it will be fine.

You shouldn't delete the dll files though, just rename them to something like cpuidsdk.dll.bak.

Black Screening / Video Card output switching off from iCUE

Recommended Posts

Link to comment

Share on other sites

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

cabralkev

Posted Images

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites