Jump to content

Asylum

Members
  • Posts

    17
  • Joined

Reputation

10 Good
  1. My initial thinking was that a 4600 cl 18 kit should be able to perform something close to 3866 cl14 @1.45. The G.skill kit confused me because it claimed to be B-die with the same timings. If I set I/O to 1.0 -1.05V, My 5800x3d's IF is stable up to DDR4 4133. Anyway, thanks for the information. I'd love to be able to use a single app for my RGB lighting also. Is there a guide for tuning micron ICs? Despite being able to attain a greater transfer rate, the bandwidth seems to be much lower than B-die; there has to be a way to overcome that, no?
  2. I assumed it was also bdie because Gskill sells a set of 4600 that are bdie and have the same timings that Corsair listed. I ran aida after installing and discovered it was micron, but I wasn't expecting such a big difference. the Gskills i own are $85 and this Corsair RAM is $145.
  3. yes. ive been using a couple cables from an older hx850 on an hx1200i for years now and have zero issues.
  4. I recently purchased a pair of Venegnce RT 4600mhz DDR4 memory modules. and I have to say that they are the WORST product I've ever purchased for a PC, and I've been building computers for over 15 years. They are simply awful. With my G.Skill 4000MHz kit, I am able to get them to run at "14-14-14-36/1.435V @ at 3600MHz. These "4600mhz" moduals can't go lower than "16-20-20-52/1.45V" @ 3600mhz . Compared to the g.skills, I receive 4GB/s LESS bandwidth at a HIGHER frequency. And on top of that, the Trfc defaults to 1001!! (Seriously!) And I can't go below 600 without my computer crashing and locking up. In fact, I have crappy OEM RAM that can overclock better! Corsair must despise Ryzen if these are "Ryzen optimized." Corsair, what happened to you? You used to make excellent ram. How are you even in business selling this junk masquerading as high-performance RAM? Not only that, but Corsair lied and posted the timings online as 18-22-22-42 when they are actually 18-26-26-46. Why is Corsair duping people? Corsair should exit the ram business completely; they are terrible at making ram. Now I'll have to go through the hassle of RMAing these horrible things. Why are you even trying to sell this? Thanks for wasting my time.
  5. Just a quick update. I tried the newest version (3.4.95) and it also doesn't detect any of my devices. I don't know what else i can try.
  6. OK I understand. it's suppose to be in program data. but because of my luck no error log there either.. :roll: so I'm still in the same boat. lol thanks again man!
  7. I see. So without that error log file it's hard to figure out whats happening. But that file isn't in the archive I uploaded from iCUE. thanks.
  8. here is what I'm seeing when I install icue over CL. Corsair link says that my devices are now controlled by iCUE but then iCUE says no devices are detected.. i exported a new log and so i attached that new log file to this post.. It seems to have some kind read out now that says: 2018-04-29T17:46:52 W cue.sensors.system_info: Values request failed: 5 "Request timeout" icuelog.zip
  9. no, nothing works with iCUE at all unfortunately. I tried plugging my h100i v2 into the second internal usb header instead of the commander pro but that also didn't work. This is happening with both my Asus Crosshair 6 and 7 so I'm starting to think it might have something to do with how Amd's new chipsets handle usb or something like that. ill just use corsair link for now (hope it's still going to get updates) thanks for all the help!
  10. link works great for controlling and monitoring my devices. I attached a couple more screenshots verifying that the service is running. the other two are what i see when i use CL vs what i see when i use iCUE.
  11. There isn't any "service_error.log" files in that location there is only that "service_trace.log" file. There's a "debuglogging" file in the settings folder but that's about it for the ProgramData folder.
  12. ok thanks! here are the logs that you requested. infolog.zip Service_Trace.log
  13. ok, here is what USBDeview is showing for my devices with that device ID. As far as i can tell everything is showing up mostly.. the blank one at the top is probably my power supply.
  14. correct, CL works just fine but iCUE doesn't. what's even stranger is yesterday i just installed a brand new x470 C7H motherboard and reinstalled windows and just installed iCUE and still it refuses to detect any of my devices. my HD fans do use the lighting node that came with them in the box which is then chained to my commander pro.
  15. Thanks for the help. The version of CL I'm using is "4.9.7.35" there doesn't seem to be a newer version available. +here are the logs from iCUE edit:i tried version 3.2.87 and it still is refusing to detect any of my devices. log1.zip
×
×
  • Create New...