![]() |
|
Register | Forum Rules | Support Ticket System | Members List | Social Groups | Edit System Specs | Search | Today's Posts | Mark Forums Read |
![]() |
|
Thread Tools | Search this Thread | Rate Thread | Display Modes |
#301
|
|||
|
|||
![]() Quote:
I noticed the use of £'s in your post so i can only assume you're British the same as me. I got told that if it becomes a serious issue here, consumer helpline can pass on information to trading standards. I doubt 1 complaint would get very far but 2 might start to get legs. I'll see what the outcome to this small claims court claim is as I havent heard anything yet but most companies only seem to care once they get something in the post. The email from SCC seems to hit spam filters. |
#302
|
|||
|
|||
![]() Quote:
|
#303
|
|||
|
|||
![]() Quote:
|
#304
|
|||
|
|||
![]() Quote:
Thinking this hasn't been ignored and not handled in a timely manner at this point is insane. Renaming a file isn't a fix, it's a work around at best and only minimizes the blackscreens so they happen every week or so instead of several times a day. Quote:
People aren't reporting because they don't have any faith you're going to do anything about it. I gave up a long time ago because it was simply being ignored. In saying that, there's been 19 replies since your April post that have been ignored for moths until you posted again in July. There's been another 16 posts since then that your have also ignored as I type this. Problem don't just go away; they need to be fixed. Whilst it's good to see corsair back in the thread, it's been piss poor service for the last, well, I think years now? I'm just checking back now after still getting the blackscreens but just being happy that they're every week or so instead of several times a day. >Does it only happen when you're gaming? Still trying to pin it on something else, huh? It's pretty simple, mate; if iCue is there, there's blackscreens; if iCue isn't there, there's no blackscreen. It's been pointed out by most users the blackscreens occur randomly. IT'S YOUR SOFTWARE. STOP LOOKING FOR OTHER THINGS AND START WITH YOUR SOFTWARE. I'm sorry to be so blunt, but how do you not get this yet? Fair dinkum! |
#305
|
|||
|
|||
![]()
I Settled with them out of court in the end. But just so everyone knows the opportunity was offered to fix this at the latest of hours just after I went ahead with the court claim.
They were going to get me to talk to Franck CEO of CPUID. Now Im no longer willing to help given their really crappy attitude in this whole thing but someone less bitter than me may enjoy better luck if they mention Franck in emails to their head of CS or PR. |
#306
|
|||
|
|||
![]() Quote:
|
#307
|
|||
|
|||
![]() Quote:
I went to my local pc shop to pick up my cheque. Not only did corsair have me wait for an hour they said that they'd be wanting all my corsair stuff back. While I did originally agree to it. I have heard nothing from corsair in relation to returning the items nor will I return them now given how rude every single person in the company I have dealt with has been. From the the head of CS that kept getting my name wrong on emails. To the guy that kept me waiting. Corsair do not learn from their mistakes and I am of the inclination that if they are going to keep ignoring everyone else with the issues I will keep going after them. |
#308
|
|||
|
|||
![]()
Anyone tried with the latest iCue version and if yes,had any luck?
|
#309
|
|||
|
|||
![]()
I can confirm this is still an issue with the latest version of iCUE. I contacted with the customer support and this is the only response I got:
Quote:
Now, I assume that you don't want to waste any more resource on this issue since it's not affecting a lot of customers. But at least put some compatibility information or announcement in your website about it. Announce that you accept the issue and you are not able to solve it. You can be sure I'm not buying any more Corsair products after experiencing this kind of customer support. My setup: CPU: Intel Core i7-4820K @ 3.70GHz GPU: NVIDIA GeForce GTX 770, Asus DirectCU II GDDR5 2GB Motherboard: ASUS Sabertooth X79 PSU: Seasonic Prime Ultra 750 Platinum Bios: v4801 (25 July 2014) Chipset: MEI v11.0.5.1189 (28 March 2016) USB 3.0: ASMedia v10.0.18362.207 (19 June 2019), (Also tried it with USB 2.0 ports but issue persists) Windows 10 Pro, v1903, Build: 18362.356 (Clean install) iCue: v3.20.80 |
#310
|
|||
|
|||
![]()
Hi All,
After reading through the last couple of posts, I thought to mention that I have the same symptoms on an AMD Asus Crosshair 7. Someone refers to the CPUIDSDK.DLL and CPUIDSDK64.DLL as being the culprits. I've got nothing to add to suggest otherwise. None the less, it is a royal pain. ![]() ![]() ![]() |
#311
|
|||
|
|||
![]()
Evening all,
Just had my most recent black screen crash tonight so thought I would try searching online one more time and have stumbled across this thread. I have been experiencing these crashes since I put my rig together in late 2018. My specs are as follows:- -Asus X370-f -Ryzen 2700x -Aorus 1080ti -Corsair H150i AIO -2x8GB 8pack Team Group 3200mhz RAM -RM850x PSU -Corsair Obsidian 750d case -1xM.2, 2xSsd 2xmech -Corsair M65 pro mouse -Corsair K70 mk2 keyboard -Corsair Void headset The things i have done whilst trying to get to the bottom of this issue:- -X370f RMA and replaced. -2700x RMA and replaced. -RM750x sold and replaced. -Bought h150i to replace wraith prizm cooler. -Aorus 1080ti sent back for testing and returned when found to be stable. -Memtest run on RAM as well as trying single sticks and different slots. -Removed all front panel connectors from mono bar power and reset. -Multiple BIOS and chipset updates. -Multiple attempts at changing bios settings (ram speeds, auto clock features etc). -Fresh install of windows 10 64bit twice. -Tried every single power plan except low power. -Rebuilt rig from scratch including replacing RMA'd parts 5 times. -Uninstalled monitoring software and opting to only run HWinfo64 -Uninstalled Ai suite early on -Removed speakers. -Saved many logs from HWinfo64 but the ones that were running when I got the crash never showed any anomalies There are probably some more things I've tried, each time naively believing I may have finally solved it only for it to come back at random. Long and short of it I have sunk hours (maybe even days by this point) of time and many more £££ than I originally budgeted for into trying to get to the bottom of this and not once did I consider it being down to iCue. Now my crashes are not as frequent as some and seem to go away for months only for them to return and usually happen quite frequently (1-5) for a short period and then I won't get any for a while. Also for transparency it's worth mentioning that I have had issues (unsure if related) with Ryzen Master consistently showing cpu temp anomalies where for a split second the temps would spike anywhere between -57 to +198. These anomalies have only shown once in HWinfo64 and were not fixed by replacing mobo or cpu. Can try uninstalling iCue but really (to my shame) don't want to loose my cooler/mouse/keyboard lighting after investing so heavily in Corsair products. If I rename the CPUID files as mentioned will my h150 pump stop or will it just effect the fans? As you can imagine it's bittersweet finding this thread as on one hand I'm happy to have possibly found the root cause but also really gutted to find it's down to Corsairs software after all this. I always aspired to have a mostly Corsair setup after growing up never being able to afford to and always looking on with envy at a good friends Corsair setup. Anyway I joined this forum in the hopes that adding my voice to the rest may make Corsair take note but more so I can try some of what has been suggested with a bit of feedback on how I can rename the CPUID files but keep my h150i running safely. I guess that I should also, not that I want to, consider possibly changing out all the Corsair parts that utilise iCue for other brands that don't have this issue but I'm still paying off most of the rest of the rig so this is a less than ideal solution. Needless to say this whole experience has put into doubt the esteem I've always held for Corsair and Asus. Last edited by Jontain; 10-27-2019 at 05:37 PM. |
#312
|
|||
|
|||
![]()
Evening all,
So I have just renamed cupidsdk.dll and cpuidsdk64.dll after closing icue and stopping the service followed by a to see if this fixes the issue for me, already had my fan curves set to run off of h150i sensor so hopefully this is safe? Also will I need to make this same change after every iCue update? |
#313
|
|||
|
|||
![]() Quote:
|
#314
|
|||
|
|||
![]()
I am having the same issue as Whiskey, GPU crash or flatout restarts. ICUE is the only culprit.
After uninstalling CPUID HWmonitor I was able to boot long enough and open ICUE to disable the LED's on the RGB ram then unintsall without a crash. Now my room isnt lit up like a nightclub all night. Asus x470 AMD 2700x Vega 64 Vengence RGB RPO 3200mhz (everything stock clocks) P.s Could someone clarify the process to bypass the crashes by renaming cpuid and the drawbacks. Someone mentioned not being able to read certain temps after doing so. Tia. |
#315
|
||||
|
||||
![]()
Iv had this issue for ages i am even on a nvidia thread thats huge were some have changed complete systems and still got same issue, i give up on it yet i fall on this thread and see its a cue issue, ive doen the dll (bak) and this explains why dashboard shows less no so ive disabled that, hope this is sorted as i am in too deep with cost of corasir rgb gear now, also i dont get black screen not since latest icue update just a freeze and i cant reset now i have todo a hard shutdown
|
![]() |
Thread Tools | Search this Thread |
Display Modes | Rate This Thread |
|
|