Jump to content

alphalvr

Members
  • Posts

    16
  • Joined

Reputation

10 Good
  1. i us3ed this as a solution for ages and wish I had just returned the damn thing. Choosing package temp to control temps no longer seems to work. Oh and mine does not give small coolant temp changes, no it is often at 60c. I tried a digital thermometer with the led and pointed it at differnt areas such as piping and that is when I decided usiong package temp would be fine as temps were not 60c but now package temp and setting a curve doesnt react, even with only icue running
  2. ffs I read that the serial number is 17 digits and something called a 'lot' number is 12 digits hence my frustration. Last question can I get a replacement before I need to return this one? Otherwise I need to buy another cooler as well which would really be a kick in the teeth. I can't seem to find this info. Thank you for your help I am feeling less stressed.
  3. No its the leds if i turn them off it goes away.....just discovered it. Turn on....flies up, turn off silence again. Serial number??
  4. I have a H115i Liquid Platinum. For about a year I have noticed the fans suddenly going to max speed. I could not figure out why for ages but then I noticed the liquid temp was 60c ! I panicked and turned off the PC and took the side off and touched the Radiator and it was not even warm. I restarted the PC and now liquid temp 30c. I monitored the situation and everything was fine for half an hour when suddenly the fans spun up to 100%. I looked and liquid temp had gone from 30c to 45c in the blink of a eye and this just isn't possible. Using a infra red thermometer reader I checked temps and they are fine, everything pipes , radiator and pump all reading under 30c. Searching the internet and these forums I read somewhere that it is a known issue caused by the RGB lighting of the cooler causing erroneous readings on the AIO's software. I tried to live with it but it is driving me nutty so I would just like it replaced. I am trying to fill out the RMA request and it asks for a serial number. I have the original packaging and there is no serial number that I can see. The only number I see on the packaging is CW-9060038-WW and some bar codes and numbers that do not look like serial numbers. The 'C' number looks like the part number. I added two pictures one showing my CPU at 29c and liquid temp at 41c ???? and the other from my packaging. Can I get this replaced? Can I get a replacement sent before I return this as I have no alternative cooler and I need my PC for work? I am Incredibly frustrated, I bought this so I could have trouble free computing and it has been nothing but trouble from day one. How do I proceed?
  5. I also have this issue Ryzen 2700x x370-f motherboard latest icue software and firmware nvidia 980ti with driver 442.5 It just randomly occurs at least once a day, doesnt matter if i am at the computer or away from it i just suddenly hear a sound like removing a usb stick and when I look at reliability monitor the corsair service display is always listed. Description Faulting Application Path: C:\Program Files (x86)\Corsair\CORSAIR iCUE Software\Corsair.Service.DisplayAdapter.exe Problem signature Problem Event Name: CLR20r3 Problem Signature 01: Corsair.Service.DisplayAdapter Problem Signature 02: 3.29.0.3 Problem Signature 03: 5ea00306 Problem Signature 04: System.Management Problem Signature 05: 4.8.3752.0 Problem Signature 06: 5c7a241f Problem Signature 07: 8a Problem Signature 08: 51 Problem Signature 09: PSZQOADHX1U5ZAHBHOHGHLDGIY4QIXHX OS Version: 10.0.18363.2.0.0.256.48 Locale ID: 2057 Additional Information 1: 2beb Additional Information 2: 2beba6fb4680d73a8c78ca7c24ccdb46 Additional Information 3: ff77 Additional Information 4: ff7714ec4afcc5465994d79f4a396c0a Extra information about the problem Bucket ID: 4a03fa981507bf79788735d7e7714dd3 (1767440580183412179)
  6. My ryzen 2700x and Asus X370-f motherboard combo will not go into an idle state with icue installed. If I uninstall icue my CPU downclocks and downvolts to 2ghz @ .7v With icue installed my CPU never downclocks and voltage is stuck at 1.27 - 1.4. This is tested with windows balanced and ryzen balanced power modes.
  7. I am using... Asus X370-F Motherboard and Ryzen 2700X My GPU is ASUS 980Ti Nvidia Driver 442.50 Corsair H115i water cooler and Corsair Strafe Silent Keyboard. It happens When I Boot for sure, other times I am not so sure. I just kept hearing the sound like I plugged in a usb stick and then removed it and it led me to finding this error each time it happened. I am not using ai suite as computer is unusable with icue and ai suite, just crashes all the time. I had to doo a fresh install without ai suite and now this. Description Faulting Application Path: C:\Program Files (x86)\Corsair\CORSAIR iCUE Software\Corsair.Service.DisplayAdapter.exe Problem signature Problem Event Name: CLR20r3 Problem Signature 01: Corsair.Service.DisplayAdapter Problem Signature 02: 3.27.0.7 Problem Signature 03: 5e58dc27 Problem Signature 04: System.Management Problem Signature 05: 4.8.3752.0 Problem Signature 06: 5c7a241f Problem Signature 07: 8a Problem Signature 08: 51 Problem Signature 09: PSZQOADHX1U5ZAHBHOHGHLDGIY4QIXHX OS Version: 10.0.18363.2.0.0.256.48 Locale ID: 2057 Additional Information 1: 2beb Additional Information 2: 2beba6fb4680d73a8c78ca7c24ccdb46 Additional Information 3: 6b5d Additional Information 4: 6b5df3a630ebb24f1d602a720fab7a96 Extra information about the problem Bucket ID: f08c0266560f36df9a6993b0fe329fd8 (1903214705929002968)
  8. Oh my god, I waited nearly 3 weeks before checking back at this forum, and there has been zero input from Corsair. I stupidly ordered a Corsair 280mm AIO because I didn't want to add more software. I forgot it was not even installed so I reinstalled ICUE last night and have already had 5 lock-ups, requires power button reset every time. I guess it is going back, I think I will try my luck with Amazon on the keyboard as well, it has been a while but this is useless. I had forgotten just how big a pain this is. I forgot to mention the reason I saw ICUE in event viewer even though the crashes do not get logged is because when I install ICUE I get one critical event and two warnings. Description Faulting Application Path: C:\Program Files (x86)\Corsair\CORSAIR iCUE Software\Corsair.Service.exe Problem signature Problem Event Name: CLR20r3 Problem Signature 01: Corsair.Service.exe Problem Signature 02: 3.13.0.11 Problem Signature 03: 5c52e5e1 Problem Signature 04: System.Management Problem Signature 05: 4.7.3190.0 Problem Signature 06: 5b6947cb Problem Signature 07: 8a Problem Signature 08: 51 Problem Signature 09: PSZQOADHX1U5ZAHBHOHGHLDGIY4QIXHX OS Version: 10.0.17763.2.0.0.256.48 Locale ID: 2057 Additional Information 1: 2beb Additional Information 2: 2beba6fb4680d73a8c78ca7c24ccdb46 Additional Information 3: 900a Additional Information 4: 900ace4b71a5dd638cea219188cb9500 Extra information about the problem Bucket ID: e9766d44275eea45f07c79dfa4df20ca (1187958403169722570) Description Windows Installer installed the product. Product Name: CORSAIR iCUE Software. Product Version: 3.13.94. Product Language: 1033. Manufacturer: Corsair. Installation success or error status: 1624. Description Windows Installer installed the product. Product Name: CORSAIR iCUE Software. Product Version: 3.13.94. Product Language: 1033. Manufacturer: Corsair. Installation success or error status: 1602. Maybe that helps. I also started a ticket, lets see what they say. TICKET #871609 One question, has anybody with this issue tested it with and without the Asus ai-suite software as it seems mostly to be with Asus boards?? I already had the software installed as I like the fan expert software, (one of the main reasons I choose Asus boards) has anyone experienced the same issues with no ai-suite?? I only ask as my previous Asus board with a Z77 chipset and Intel 3770K CPU used to have issues (reboots) when using any other software that also polled the sensors. Board was rock solid otherwise.
  9. That is funny as I was in the process of RMA'ing my 970 EVO NVME m.2 drive being almost certain that was the culprit. Then I noticed icue had been mentioned in reliability history (only once because usually nothing is logged anywhere due to the sudden hard lockup nature) I was not really expecting it to be the cause of issue but as soon as it was uninstalled the problem went away. After leaving my PC on for a week with no more crashes I reinstalled icue yesterday and have had 4 hard lockups in 24 hours. I have just uninstalled the software again as it makes the PC virtually unusable. I will try what you suggest, not really what I wanted to hear. What would be nice is if they included a check box which would allow me to disable polling of the sensors. (my theory as to the cause) If they need a board for testing they just need a X370-f because it happens so often it should be at least helpful in pinning this down. My new PC has ruined my STRAFE RGB keyboard :(: regards
  10. Hey can I add that I have the exact same problem, Install ICUE,(I have STRAFE Keyboard) update Firmware and software and from that moment I get daily crashes, sometimes several. I only figured it out because corsair ICUE was the only thing ever mentioned in reliability history, usually the lockups show as nothing. So I tried removing it....left PC on for a week solid , no crashes. Reinstalled ICUE today and have already had two lockups. This is a clean install, in fact I was doing my install when this all started, shortly after installing ICUE for my keyboard. The lockup shows itself as sudden PC failure, screen goes black, keyboard lights go black but PC stays lit up and fans are still running. I have to use the rear power switch to restart the PC as power and reset no longer work. Could I just say it saddens me to read about being unable to source an older system, is that a joke?? Like the other poster I could have a system with that spec inside a week with about 10-mins effort. (I work in Macdonalds so you have no excuse) Leaves me little hope that this issue will be resolved. Ryzen 2700X and Asus X370-f (latest bios 4024) It crashed the same on previous bios's debug logging.zip
×
×
  • Create New...