Inheritance Posted September 14, 2018 Share Posted September 14, 2018 Hey guys the 3.7.99 patch should have fixed the issue. Hopefully. If it hasn't please do make a new thread and please upload your logs from 3.7.99 so the Corsair team can gather more info. Link to comment Share on other sites More sharing options...
Rudzik Posted September 14, 2018 Share Posted September 14, 2018 (edited) In 3.7.99 and 3.7.103 beta it got worse. The black screen became even more common - it's impossible to work on a PC. Has removed. A whole month I was waiting for an update, but it seems that the developers were not what corrected they needed to be. I regret buying Corsair products. The lesson of the future ... (google translate) Edited September 14, 2018 by Rudzik Link to comment Share on other sites More sharing options...
Nimce Posted September 14, 2018 Share Posted September 14, 2018 You tested 3.7.99? or 3.7? Link to comment Share on other sites More sharing options...
Rudzik Posted September 14, 2018 Share Posted September 14, 2018 (edited) ...put up for sale his Commander Pro. No strength to wait for the developers to correct the problem or not. 9 pages of posts in which they described their problems in detail. As if this developers did not notice. (google translate) Edited September 14, 2018 by Rudzik Link to comment Share on other sites More sharing options...
Rudzik Posted September 14, 2018 Share Posted September 14, 2018 You tested 3.7.99? or 3.7? 3.7.99 of course Link to comment Share on other sites More sharing options...
thobber Posted September 14, 2018 Share Posted September 14, 2018 I'm using 3.7.103 atm, and computer has been running for about 24 hours without any problems. Ran some stress-tests to see if I could trigger it, but no problems so far. Seems like it's fixed for me at least. Link to comment Share on other sites More sharing options...
Rudzik Posted September 14, 2018 Share Posted September 14, 2018 I'm using 3.7.103 atm, and computer has been running for about 24 hours without any problems. Ran some stress-tests to see if I could trigger it, but no problems so far. Seems like it's fixed for me at least. strange but I had a day worked too, no problem, only then it began. and it looks like a problem for the x99 and x79 chipsets Link to comment Share on other sites More sharing options...
Rudzik Posted September 14, 2018 Share Posted September 14, 2018 Tested the 3.7 build. The problem is still there. Took less than 8 hours since iCUE installation to happen again. same problem Link to comment Share on other sites More sharing options...
WhiskeyOmega Posted September 14, 2018 Author Share Posted September 14, 2018 3.7.103 so far isnt causing me any issues. Link to comment Share on other sites More sharing options...
eXcelsum Posted September 15, 2018 Share Posted September 15, 2018 FYI (corsair and everyone else) @Corsair James, CAM by NZXT software uses the same exact CPUIDSDK DLLs which creates exact same issues, I did not try the beta drivers yet but it may fail on you if you got CAM installed. And who knows what other monitoring software is using it, I would do a system wide search before posting here.:!: Link to comment Share on other sites More sharing options...
Tommins Posted September 15, 2018 Share Posted September 15, 2018 Worked fine for a day or so... then boom back to black screen. Come on now get it fixed please. Could have bought some cheap random mouse but thought I would buy quality, how wrong I was. Link to comment Share on other sites More sharing options...
Inheritance Posted September 16, 2018 Share Posted September 16, 2018 (edited) If you're still seeing this problem please post your logs. Edited September 16, 2018 by Inheritance Link to comment Share on other sites More sharing options...
WhiskeyOmega Posted September 16, 2018 Author Share Posted September 16, 2018 If you're still seeing this problem please post your logs. There is nothing in the logs to show it. Ive just had the issue again after 4 days of nothing until now. Pretty usual if its a brand new install of the CPUID SDK. Using 3.7.103 Link to comment Share on other sites More sharing options...
Rudzik Posted September 17, 2018 Share Posted September 17, 2018 I'm still investigating the problems with iCue. I have my suspicions that my mouse logitech mx master 2s. Friezes when working with a mouse and a black screen can be called by both the iCue and Logitech options. iCue in every possible way wants to take my Logitech mouse for "Corsair mous" and interferes with the driver? Maybe it's just my guesswork. Link to comment Share on other sites More sharing options...
Rudzik Posted September 19, 2018 Share Posted September 19, 2018 (edited) I'm still investigating the problems with iCue. I have my suspicions that my mouse logitech mx master 2s. Friezes when working with a mouse and a black screen can be called by both the iCue and Logitech options. iCue in every possible way wants to take my Logitech mouse for "Corsair mous" and interferes with the driver? Maybe it's just my guesswork. Uninstall Logitech Options, Install ICUE 3.7.103 = Black screen -> Crash ICUE. Logitech Options does not interfere at all work ICUE Edited September 19, 2018 by Rudzik Link to comment Share on other sites More sharing options...
Corsair Employee Corsair James Posted September 19, 2018 Corsair Employee Share Posted September 19, 2018 I sent everyone who PM'd me a new software update. We're making progress but this time, the test will be a little more intrusive as we narrow it down by options 1x1. Link to comment Share on other sites More sharing options...
Rudzik Posted September 19, 2018 Share Posted September 19, 2018 I started the test. One by one "False" for two days... Link to comment Share on other sites More sharing options...
Rudzik Posted September 20, 2018 Share Posted September 20, 2018 I started the test. One by one "False" for two days... First tests: 1.DISPLAY_API: Black Screen -> Crash ICUE 2.ACPI_TIMER: Black Screen (The PC did not come out with a black screen ->RESET Button) 3.PROCESSOR: Black Screen -> Crash ICUE 4.HWMONITORING: Black Screen -> Crash ICUE 5.GRAPHICS: Black Screen -> Crash ICUE 6.STORAGE: Black Screen -> Crash ICUE 7.SPD: Black Screen -> Crash ICUE 8.SMBUS: Black Screen -> Crash ICUE 9.CHIPSET: Testing... Link to comment Share on other sites More sharing options...
Monster511 Posted September 20, 2018 Share Posted September 20, 2018 I was fine for about two days. Now I get a black screen every time I use my computer. I will have to uninstall iCUE and revert back to CUE and use SIV. I PM'd James in hope of getting the beta to test. Link to comment Share on other sites More sharing options...
eXcelsum Posted September 22, 2018 Share Posted September 22, 2018 No luck for me either, black screen after 10min. I left it on with this beta version but renamed all DLL files that start with the word "CPU" and so far 3 days i am ok. That includes DLL files for CAM from NZXT, and by the way from my support ticket with NZXT they said they know about the iCue and CAM having conflicts. Here is a screenshot of renamed files: Link to comment Share on other sites More sharing options...
thobber Posted September 26, 2018 Share Posted September 26, 2018 I've started getting the same problems again. Worked well for a week or so. Using 3.7.103 I also renamed all the CPUID/CPU .dll's, and now only my mouse shows up in iCue, but no black screens at least. Link to comment Share on other sites More sharing options...
Psycycb Posted September 26, 2018 Share Posted September 26, 2018 had the same problem. three days ago removed windows 10 x64 put windows 7 x64, installed all the programs and games that were on the old system. three days the computer runs 24 hours a day, stress tests and games work fine. Black screen is not yet arrived. (google translator) Link to comment Share on other sites More sharing options...
djvanyel Posted September 26, 2018 Share Posted September 26, 2018 I can confirm that crashing still occurs under 3.7.99 at this time. My system has had no major changes since my last troubleshooting and reply. I was previously running fine, although I've encountered a couple crashes in the meantime but not with the same symptoms as the "Black Screen" crashing from before. When the Black Screen/hard power off required crashing returned after performing the update, I made some notes during troubleshooting as follows: Updated to latest version 3.7.99 via iCUE. No issues encountered during install. Install completed, no reboot needed. Opened iCUE and saw multiple new sensor inputs available (ASUSTEK and others) instead of my previous state when only the video card sensor was only shown in the dropdown list (all other previous settings were intact; see my original reply). Crashing began soon after completing update during light use with exact same symptoms as before. I followed the steps in the previous testing guide above to disable cpuidsdk.dll (stop Corsair Service, rename file), rebooted. Crash occurred. Used same steps to disable cupidsdk64.dll, rebooted. Crash occurred. Attempted to stop Corsair service on next startup, but experienced a spontaneous reboot after opening the Services control panel (no blue screen, just a full reset). After the reboot, I was able to load the Services CP, stopped the Corsair service, and renamed cpuidwin7sdk.dll. Rebooted. System seems stable. I checked over the latest service logs visually via Notepad. No error entries were shown, just many "INFO: DevicesMonitor" entries. Quick scan of the logs did show a few entries where a large number of non-displayed characters are inserted before the entry (directly before the time stamp). There wasn't any other direct correlation between the entries. Not sure if this indicates anything but it appears to correspond to periods after the recent crashes occurred (can't be sure). Checked iCUE settings, now appear as before (only GPU temperature sensor monitoring available). I currently seem stable and running as I was as of my last reply. If anything else of note occurs in the near future, I'll edit this reply as appropriate. Hope this helps. Link to comment Share on other sites More sharing options...
Psycycb Posted September 27, 2018 Share Posted September 27, 2018 Oops. I apologize today flew a black screen, followed by a blue screen https://ibb.co/czr2HU Link to comment Share on other sites More sharing options...
Rudzik Posted September 27, 2018 Share Posted September 27, 2018 (edited) Oops. I apologize today flew a black screen, followed by a blue screen https://ibb.co/czr2HU This happens in everyone but 2 months there are no solutions! :( All Tests "I sent everyone who PM'd me a new software update. We're making progress but this time, the test will be a little more intrusive as we narrow it down by options 1x1" failed Edited September 27, 2018 by Rudzik Link to comment Share on other sites More sharing options...
Recommended Posts