The Corsair User Forums  

Go Back   The Corsair User Forums > Corsair Product Discussion > Memory

Reply
 
Thread Tools Search this Thread Rate Thread Display Modes
  #1  
Old 08-10-2018, 08:03 PM
Leemarvin Leemarvin is offline
Registered User
Leemarvin's PC Specs
 
Join Date: Dec 2014
Posts: 35
POST ID # = 968029
Leemarvin Reputation: 10
Default Vengeance PRO RGB 32gb (4x8) iCUE problem

Hi, I've just received my RAM and I have the following problem:

Bios (latest version 3902), Windows, LINK, AIDA, and every software detects the four modules and are working. Yet iCUE only detects two and I can't change the lightning effect either.

I have uninstalled iCUE and LINK, and installed them again to their latest versions and still the same.

iCUE tells me to update the firmware (see the attached IMG), I do it, it says that it was installed, nothing changes and the icon telling me that I have to update it is still there...I did this "installation" three times, with no result.

Any idea of what to do? is there a link to download the firmware n order to install it manually instead than throght icue?


Thanks in advance!
Attached Images
File Type: jpg firmware.JPG (702.1 KB, 117 views)

Last edited by Leemarvin; 08-10-2018 at 08:14 PM.
Reply With Quote


  #2  
Old 08-11-2018, 01:34 PM
Leemarvin Leemarvin is offline
Registered User
Leemarvin's PC Specs
 
Join Date: Dec 2014
Posts: 35
POST ID # = 968113
Leemarvin Reputation: 10
Default

Well I've managed to find some partial solution:

1. I've found a G.Skillll guide where it showed me where to find the location of SPD Write in my mobo in order to enable it.
2. That allowed me to finally update the firmware and take control of my RAM in iCUE, yet..
3. I could only do it when using the slots from the left side of my CPU...I had to put the RAM on the grey slots from my left side in turns, in order to first update the firmware and later adjust the lighting.
4. So in conclusion I have now managed to have all the RAM in one static color, but still iCUE only recognizes the RAM in the left side slots.
5. Like I've stated before, BIOS, Windows and the rest of the software installed in my PC recognizes the full 32gb (bar Photoshop that because of a weird bug only sees 25gb)

Any idea of how to solve this and get iCue recognize the modules that I have in my right side of the CPU? Is there some test I can run to see if there is some hardware problem anywhere? thanks in advance

PD I'm uploading some pics as example
Attached Images
File Type: jpg iCUE.JPG (882.5 KB, 173 views)
File Type: jpg IMG_9405.JPG (2.48 MB, 111 views)
Reply With Quote


  #3  
Old 08-12-2018, 01:40 AM
Leemarvin Leemarvin is offline
Registered User
Leemarvin's PC Specs
 
Join Date: Dec 2014
Posts: 35
POST ID # = 968169
Leemarvin Reputation: 10
Default

Nobody had a similar issue with this RAM? is there an old version from LINK that I can try to use and see if it works?

Last edited by Leemarvin; 08-12-2018 at 06:29 PM.
Reply With Quote


  #4  
Old 08-12-2018, 06:23 PM
Leemarvin Leemarvin is offline
Registered User
Leemarvin's PC Specs
 
Join Date: Dec 2014
Posts: 35
POST ID # = 968262
Leemarvin Reputation: 10
Default

Is there some user working in Corsair to give a hand? I've already sent a ticket two days ago with no answer BTW...
Reply With Quote


  #5  
Old 08-13-2018, 05:08 AM
Cpt.Planet Cpt.Planet is offline
Registered User
 
Join Date: Apr 2010
Posts: 28
POST ID # = 968295
Cpt.Planet Reputation: 18
Default

What settings do you have setup under DIMM setup? Also don't run CLink and iCue at the same time.
Reply With Quote


  #6  
Old 08-13-2018, 05:37 AM
Leemarvin Leemarvin is offline
Registered User
Leemarvin's PC Specs
 
Join Date: Dec 2014
Posts: 35
POST ID # = 968296
Leemarvin Reputation: 10
Default

Quote:
Originally Posted by Cpt.Planet View Post
What settings do you have setup under DIMM setup? Also don't run CLink and iCue at the same time.
I have uninstalled CORSAIR LINK, but I was asking for an older version from the ones that managed LEDs, because like every software bar iCUE, LINK detects the four modules.

I'm using the RAM at stock speed, 2133 mhz
Reply With Quote


  #7  
Old 08-13-2018, 11:01 AM
Corsair Art's Avatar
Corsair Art Corsair Art is offline
Corsair Employee
 
Join Date: Feb 2016
Posts: 543
POST ID # = 968323
Corsair Art Reputation: 14
Default

What's your ticket ID? Are you using a single kit?

-Art
Reply With Quote


  #8  
Old 08-13-2018, 02:14 PM
Leemarvin Leemarvin is offline
Registered User
Leemarvin's PC Specs
 
Join Date: Dec 2014
Posts: 35
POST ID # = 968345
Leemarvin Reputation: 10
Default

Quote:
Originally Posted by Corsair Art View Post
What's your ticket ID? Are you using a single kit?

-Art
Yes I'm using a single KIT and my ticket ID is 765307.

It's really weird that the four modules are detected correctly by everything bar iCUE

Last edited by Leemarvin; 08-13-2018 at 03:14 PM.
Reply With Quote


  #9  
Old 08-14-2018, 04:43 PM
Leemarvin Leemarvin is offline
Registered User
Leemarvin's PC Specs
 
Join Date: Dec 2014
Posts: 35
POST ID # = 968522
Leemarvin Reputation: 10
Default

I've updated to the newest version of iCUE and nothing changed, same old problem.

PD: Corsair Art, I've answered your email and I've made another query about an issue with my Coprsair Keyboard. Thanks in Advance

Last edited by Leemarvin; 08-14-2018 at 04:50 PM.
Reply With Quote


  #10  
Old 08-18-2018, 10:20 PM
Leemarvin Leemarvin is offline
Registered User
Leemarvin's PC Specs
 
Join Date: Dec 2014
Posts: 35
POST ID # = 969277
Leemarvin Reputation: 10
Default

So I still couldn't solve it and I have now also a ticket with my Keyboard since also was affected with flickering after updating iCUE.

These are the LOGS, if anyone can explain me what are the errors mentioned here and what can i do, I'll trully aporeciatted:

2018-08-18T23:06:52 I cue.init: iCUE version: 3.6.109
2018-08-18T23:06:52 I cue.init: Updates server: https://www3.corsair.com/software/CUE_V3/
2018-08-18T23:06:52 I cue.init: Build type: Public Release
2018-08-18T23:06:52 I cue.init: Applicaiton ID: 10744
2018-08-18T23:06:52 W cue.locale: Cannot find dir for qt *.qm files
2018-08-18T23:06:52 I cue.init.font: Using Regular text font family: "Open Sans"
2018-08-18T23:06:52 I cue.init.font: Using Title text font family: "Gotham Bold"
2018-08-18T23:06:52 I cue.session: Locked changed to false
2018-08-18T23:06:52 I cue.session.win: Will notify 'connected changed to' with delay
2018-08-18T23:06:52 I cue.session: Local changed to true
2018-08-18T23:06:52 I cue.profiles.folders.tree: Profile order deserialization started: "C:\\Users\\X99\\AppData\\Roaming\\Corsair\\CUE/profiles/tree.cueprofileorder"
2018-08-18T23:06:52 I cue.profiles.folders.tree: Profile order deserialization finished: "C:\\Users\\X99\\AppData\\Roaming\\Corsair\\CUE/profiles/tree.cueprofileorder"
2018-08-18T23:06:53 I cue.action.macro.win: Init time: 0.40289 (init: 4.26e-07 reset: 0.00199078 )
2018-08-18T23:06:54 C qml: CueColorPalette is deprecated since v3.0. Use QmlColorPalette instead.
2018-08-18T23:06:54 C qml: CueColorPalette is deprecated since v3.0. Use QmlColorPalette instead.
2018-08-18T23:06:54 C qml: CueColorPalette is deprecated since v3.0. Use QmlColorPalette instead.
2018-08-18T23:06:54 C qml: CueColorPalette is deprecated since v3.0. Use QmlColorPalette instead.
2018-08-18T23:06:54 C qml: CueColorPalette is deprecated since v3.0. Use QmlColorPalette instead.
2018-08-18T23:06:54 C qml: CueColorPalette is deprecated since v3.0. Use QmlColorPalette instead.
2018-08-18T23:06:54 C qml: CueColorPalette is deprecated since v3.0. Use QmlColorPalette instead.
2018-08-18T23:06:54 C qml: CueColorPalette is deprecated since v3.0. Use QmlColorPalette instead.
2018-08-18T23:06:54 C qml: CueColorPalette is deprecated since v3.0. Use QmlColorPalette instead.
2018-08-18T23:06:54 C qml: CueColorPalette is deprecated since v3.0. Use QmlColorPalette instead.
2018-08-18T23:06:54 C cue.osd.dpi: Cannot update OsdDpiModel. Invalid DpiProperty.
2018-08-18T23:06:55 I cue.session: Connected changed to true
2018-08-18T23:06:55 I cue.clink.device.hw_lightings: Working state about to change, lock hw lights preview.
2018-08-18T23:06:55 I cue.dev.enum.hid: Entering working state.
2018-08-18T23:06:55 I cue.dev.enum.clink: Entering working state.
2018-08-18T23:06:55 I cue.dev.enum.phost: Entering working state.
2018-08-18T23:06:55 I cue.sdk: Entering working state, session connected.
2018-08-18T23:06:55 I cue.sdk: Starting router.
2018-08-18T23:06:55 I cue.clink.device.hw_lightings: Entering working state, unlock and disable hw lights preview.
2018-08-18T23:06:55 I cue.dev: Failed to open device: (vid=1b1c, pid=1b37) "\\\\?\\hid#vid_1b1c&pid_1b37&mi_00#8&807969&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"
2018-08-18T23:06:55 C dev.manifest: Cannot find path for manifest key (vid=1b1c, pid=1b06)
2018-08-18T23:06:55 I cue.dev: Manifest for device (vid=1b1c, pid=1b06) not found.
2018-08-18T23:06:55 C dev.manifest: Cannot find path for manifest key (vid=1b1c, pid=1b06)
2018-08-18T23:06:55 I cue.dev: Manifest for device (vid=1b1c, pid=1b06) not found.
2018-08-18T23:06:55 I cue.dev: Failed to open device: (vid=1b1c, pid=1b37) "\\\\?\\hid#vid_1b1c&pid_1b37&mi_01&col01#8&184405ae&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"
2018-08-18T23:06:55 I cue.dev: Opened device: "K65 LUX RGB" (vid=1b1c, pid=1b37) "\\\\?\\hid#vid_1b1c&pid_1b37&mi_01&col02#8&184405ae&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}"
2018-08-18T23:06:55 I cue.dev: Begin attaching to "K65 LUX RGB" (vid=1b1c, pid=1b37) "\\\\?\\hid#vid_1b1c&pid_1b37&mi_01&col02#8&184405ae&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}" status b= 0
2018-08-18T23:06:55 I cue.dev: End attaching to "K65 LUX RGB" (vid=1b1c, pid=1b37) "\\\\?\\hid#vid_1b1c&pid_1b37&mi_01&col02#8&184405ae&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}" status a= 0
2018-08-18T23:06:55 I cue.dev: Created new device "K65 LUX RGB" (vid=1b1c, pid=1b37); ready: false
2018-08-18T23:06:55 I cue.dev: Opened device: "K65 LUX RGB" (vid=1b1c, pid=1b37) "\\\\?\\hid#vid_1b1c&pid_1b37&mi_01&col03#8&184405ae&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}"
2018-08-18T23:06:55 I cue.dev: Begin attaching to "K65 LUX RGB" (vid=1b1c, pid=1b37) "\\\\?\\hid#vid_1b1c&pid_1b37&mi_01&col03#8&184405ae&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}" status b= 0
2018-08-18T23:06:55 I cue.dev: End attaching to "K65 LUX RGB" (vid=1b1c, pid=1b37) "\\\\?\\hid#vid_1b1c&pid_1b37&mi_01&col03#8&184405ae&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}" status a= 0
2018-08-18T23:06:55 I cue.dev: Opened device: "K65 LUX RGB" (vid=1b1c, pid=1b37) "\\\\?\\hid#vid_1b1c&pid_1b37&mi_01&col04#8&184405ae&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}"
2018-08-18T23:06:55 I cue.dev: Begin attaching to "K65 LUX RGB" (vid=1b1c, pid=1b37) "\\\\?\\hid#vid_1b1c&pid_1b37&mi_01&col04#8&184405ae&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}" status b= 0
2018-08-18T23:06:55 I cue.dev: End attaching to "K65 LUX RGB" (vid=1b1c, pid=1b37) "\\\\?\\hid#vid_1b1c&pid_1b37&mi_01&col04#8&184405ae&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}" status a= 0
2018-08-18T23:06:55 I cue.dev: Opened device: "K65 LUX RGB" (vid=1b1c, pid=1b37) "\\\\?\\hid#vid_1b1c&pid_1b37&mi_02#8&b933814&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"
2018-08-18T23:06:55 I cue.dev: Begin attaching to "K65 LUX RGB" (vid=1b1c, pid=1b37) "\\\\?\\hid#vid_1b1c&pid_1b37&mi_02#8&b933814&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" status b= 0
2018-08-18T23:06:55 I cue.dev: End attaching to "K65 LUX RGB" (vid=1b1c, pid=1b37) "\\\\?\\hid#vid_1b1c&pid_1b37&mi_02#8&b933814&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" status a= 1
2018-08-18T23:06:55 I cue.dev: Initializing "K65 LUX RGB" (vid=1b1c, pid=1b37)
2018-08-18T23:06:55 C dev.manifest: Cannot find path for manifest key (vid=51d, pid=2)
2018-08-18T23:06:55 I cue.dev: Manifest for device (vid=51d, pid=2) not found.
2018-08-18T23:06:55 C dev.manifest: Cannot find path for manifest key (vid=1b1c, pid=1b06)
2018-08-18T23:06:55 I cue.dev: Manifest for device (vid=1b1c, pid=1b06) not found.
2018-08-18T23:06:55 C dev.manifest: Cannot find path for manifest key (vid=1b1c, pid=c04)
2018-08-18T23:06:55 I cue.dev: Manifest for device (vid=1b1c, pid=c04) not found.
2018-08-18T23:06:55 I cue.dev: Initialized true "K65 LUX RGB" (vid=1b1c, pid=1b37)
2018-08-18T23:06:55 I cue.lightings.direct_player: Started lighting worker in 0x20d8
2018-08-18T23:06:55 I cue.dev: Device insertion processing complete for K65 LUX RGB.
2018-08-18T23:06:56 C dev.manifest: Cannot find path for manifest key (vid=1b1c, pid=3)
2018-08-18T23:06:56 C dev.manifest: Cannot find path for manifest key (vid=1b1c, pid=7)
2018-08-18T23:06:56 C dev.manifest: Cannot find path for manifest key (vid=1b1c, pid=2)
2018-08-18T23:06:56 I cue.lightings.direct_player: Started lighting worker in 0x2a30
2018-08-18T23:06:56 I cue.dev: Device insertion processing complete for H110iGT.
2018-08-18T23:06:56 W cue.dev.enum.clink: "No such device to remove (id = vid<1b1c>pid<000004>serial<VENGEANCERGBPRO>index<1>)"
2018-08-18T23:06:56 I cue.lightings.direct_player: Started lighting worker in 0x2bd4
2018-08-18T23:06:56 I cue.dev: Device insertion processing complete for VENGEANCE RGB PRO.
2018-08-18T23:06:56 C dev.manifest: Cannot find path for manifest key (vid=1b1c, pid=400)
2018-08-18T23:06:56 C dev.manifest: Cannot find path for manifest key (vid=1b1c, pid=400)
2018-08-18T23:06:56 C dev.manifest: Cannot find path for manifest key (vid=1b1c, pid=3)
2018-08-18T23:06:56 C dev.manifest: Cannot find path for manifest key (vid=1b1c, pid=3)
2018-08-18T23:06:56 C dev.manifest: Cannot find path for manifest key (vid=1b1c, pid=8)
2018-08-18T23:06:56 C dev.manifest: Cannot find path for manifest key (vid=1b1c, pid=3)
2018-08-18T23:06:56 C dev.manifest: Cannot find path for manifest key (vid=1b1c, pid=1)
2018-08-18T23:06:56 W cue.dev.enum.demo: Registration of device with unsupported DemoUsbId: (vid=0, pid=0)
2018-08-18T23:06:56 C cue.download.fw: Incorrect index contents: fw obj is empty "combined-image"
2018-08-18T23:06:56 I cue.download.fw: Incorrect index contents: condition for "image-priority" is empty
2018-08-18T23:06:57 C cue.download.fw: Incorrect index contents: fw obj is empty "combined-image"
2018-08-18T23:06:57 I cue.download.fw: Incorrect index contents: condition for "image-priority" is empty
2018-08-18T23:11:13 I cue.init.ui: Starting UI.
2018-08-18T23:11:13 W QObject::connect: invalid null parameter
2018-08-18T23:11:17 W MainWindow_QMLTYPE_475(0x22dee0b0) must be a top level window.
2018-08-18T23:11:17 W MainWindow_QMLTYPE_475(0x22dee0b0) must be a top level window.
2018-08-18T23:11:17 W file:///C:/Program Files (x86)/Corsair/CORSAIR iCUE Software/QtQuick/Dialogs/DefaultFileDialog.qml:210:25: QML ListView: Binding loop detected for property "model"
2018-08-18T23:11:17 W libpng warning: iCCP: known incorrect sRGB profile
2018-08-18T23:11:17 W libpng warning: iCCP: known incorrect sRGB profile
2018-08-18T23:11:18 C qml: CueColorPalette is deprecated since v3.0. Use QmlColorPalette instead.
2018-08-18T23:11:18 C qml: CueColorPalette is deprecated since v3.0. Use QmlColorPalette instead.
2018-08-18T23:11:18 W libpng warning: iCCP: known incorrect sRGB profile
2018-08-18T23:11:18 W qrc:/qml/delegate/CurrentProfileDelegate.qml:110:4: QML CueImage: No fue posible abrir: qrc:/share/embed/assets2/icons/profile_grouping/folder_closed.png
2018-08-18T23:11:18 C qml: CueColorPalette is deprecated since v3.0. Use QmlColorPalette instead.
2018-08-18T23:11:18 C qml: CueColorPalette is deprecated since v3.0. Use QmlColorPalette instead.
2018-08-18T23:11:18 W qrc:/qml/collection/AccordionItem.qml:147:4: QML PropertyChanges: No se puede asignar a una propiedad inexistente ?textColor?
2018-08-18T23:11:18 W qrc:/qml/collection/AccordionItem.qml:147:4: QML PropertyChanges: No se puede asignar a una propiedad inexistente ?iconColor?
2018-08-18T23:11:18 W qrc:/qml/collection/AccordionItem.qml:147:4: QML PropertyChanges: No se puede asignar a una propiedad inexistente ?textColor?
2018-08-18T23:11:18 W qrc:/qml/collection/AccordionItem.qml:147:4: QML PropertyChanges: No se puede asignar a una propiedad inexistente ?iconColor?
2018-08-18T23:11:18 C qml: CueColorPalette is deprecated since v3.0. Use QmlColorPalette instead.
2018-08-18T23:11:18 C qml: CueColorPalette is deprecated since v3.0. Use QmlColorPalette instead.
2018-08-18T23:11:18 C qml: CueColorPalette is deprecated since v3.0. Use QmlColorPalette instead.
2018-08-18T23:11:18 C qml: CueColorPalette is deprecated since v3.0. Use QmlColorPalette instead.
2018-08-18T23:11:18 C qml: CueColorPalette is deprecated since v3.0. Use QmlColorPalette instead.
2018-08-18T23:11:18 C qml: CueColorPalette is deprecated since v3.0. Use QmlColorPalette instead.
2018-08-18T23:11:18 C qml: CueColorPalette is deprecated since v3.0. Use QmlColorPalette instead.
2018-08-18T23:11:18 C qml: CueColorPalette is deprecated since v3.0. Use QmlColorPalette instead.
2018-08-18T23:11:18 C qml: CueColorPalette is deprecated since v3.0. Use QmlColorPalette instead.
2018-08-18T23:11:18 C qml: CueColorPalette is deprecated since v3.0. Use QmlColorPalette instead.
2018-08-18T23:11:18 C qml: CueColorPalette is deprecated since v3.0. Use QmlColorPalette instead.
2018-08-18T23:11:18 C qml: CueColorPalette is deprecated since v3.0. Use QmlColorPalette instead.
2018-08-18T23:11:18 C qml: CueColorPalette is deprecated since v3.0. Use QmlColorPalette instead.
2018-08-18T23:11:18 C qml: CueColorPalette is deprecated since v3.0. Use QmlColorPalette instead.
2018-08-18T23:11:18 C qml: CueColorPalette is deprecated since v3.0. Use QmlColorPalette instead.
2018-08-18T23:11:18 W libpng warning: iCCP: known incorrect sRGB profile
2018-08-18T23:11:18 W libpng warning: iCCP: known incorrect sRGB profile
2018-08-18T23:11:18 W libpng warning: iCCP: known incorrect sRGB profile
2018-08-18T23:11:18 W libpng warning: iCCP: known incorrect sRGB profile
2018-08-18T23:11:18 W libpng warning: iCCP: known incorrect sRGB profile
2018-08-18T23:11:18 W libpng warning: iCCP: known incorrect sRGB profile
2018-08-18T23:11:18 W qrc:/qml/ui/DevicesPanel.qml:96:4: QML Binding: Binding loop detected for property "value"
2018-08-18T23:11:19 W qrc:/qml/ui/ProfilesToolbar.qml:18:38: Unable to assign [undefined] to QString
2018-08-18T23:11:20 W qrc:/qml/ui/DevicesPanel.qml:74:12: QML Loader: Binding loop detected for property "sourceComponent"
2018-08-18T23:11:20 W qrc:/qml/ui/ProfilesToolbar.qml:18:38: Unable to assign [undefined] to QString
2018-08-18T23:11:20 W qrc:/qml/ui/ProfilesToolbar.qml:18:38: Unable to assign [undefined] to QString
2018-08-18T23:11:20 W libpng warning: iCCP: known incorrect sRGB profile
2018-08-18T23:11:20 W libpng warning: iCCP: known incorrect sRGB profile
2018-08-18T23:11:20 W libpng warning: iCCP: known incorrect sRGB profile
2018-08-18T23:11:20 W libpng warning: iCCP: known incorrect sRGB profile
2018-08-18T23:11:20 W libpng warning: iCCP: known incorrect sRGB profile
2018-08-18T23:11:20 W libpng warning: iCCP: known incorrect sRGB profile
2018-08-18T23:11:20 W libpng warning: iCCP: known incorrect sRGB profile
2018-08-18T23:11:20 W qrc:/qml/ui/ProfilesToolbar.qml:18:38: Unable to assign [undefined] to QString
2018-08-18T23:11:21 W libpng warning: iCCP: known incorrect sRGB profile
2018-08-18T23:11:21 W libpng warning: iCCP: known incorrect sRGB profile
2018-08-18T23:11:21 W libpng warning: iCCP: known incorrect sRGB profile
2018-08-18T23:11:21 W libpng warning: iCCP: known incorrect sRGB profile
2018-08-18T23:11:21 W libpng warning: iCCP: known incorrect sRGB profile
2018-08-18T23:11:21 W libpng warning: iCCP: known incorrect sRGB profile
2018-08-18T23:11:21 W libpng warning: iCCP: known incorrect sRGB profile
2018-08-18T23:11:21 W libpng warning: iCCP: known incorrect sRGB profile
2018-08-18T23:11:21 W libpng warning: iCCP: known incorrect sRGB profile
2018-08-18T23:11:21 W libpng warning: iCCP: known incorrect sRGB profile
2018-08-18T23:11:21 W libpng warning: iCCP: known incorrect sRGB profile
2018-08-18T23:11:21 W libpng warning: iCCP: known incorrect sRGB profile
2018-08-18T23:11:21 W libpng warning: iCCP: known incorrect sRGB profile
2018-08-18T23:11:21 W libpng warning: iCCP: known incorrect sRGB profile
2018-08-18T23:11:21 W libpng warning: iCCP: known incorrect sRGB profile
2018-08-18T23:11:21 W libpng warning: iCCP: known incorrect sRGB profile
2018-08-18T23:11:21 W libpng warning: iCCP: known incorrect sRGB profile
2018-08-18T23:11:21 W libpng warning: iCCP: known incorrect sRGB profile
2018-08-18T23:11:21 W libpng warning: iCCP: known incorrect sRGB profile
2018-08-18T23:11:21 W libpng warning: iCCP: known incorrect sRGB profile
2018-08-18T23:11:24 W file:///C:/Program Files (x86)/Corsair/CORSAIR iCUE Software/QtQuick/Dialogs/DefaultFileDialog.qml:210:25: QML ListView: Binding loop detected for property "model"
2018-08-18T23:11:24 W file:///C:/Program Files (x86)/Corsair/CORSAIR iCUE Software/QtQuick/Dialogs/DefaultFileDialog.qml:210:25: QML ListView: Binding loop detected for property "model"
2018-08-18T23:11:24 W file:///C:/Program Files (x86)/Corsair/CORSAIR iCUE Software/QtQuick/Dialogs/DefaultFileDialog.qml:210:25: QML ListView: Binding loop detected for property "model"
2018-08-18T23:11:24 W file:///C:/Program Files (x86)/Corsair/CORSAIR iCUE Software/QtQuick/Dialogs/DefaultFileDialog.qml:210:25: QML ListView: Binding loop detected for property "model"
2018-08-18T23:11:24 W file:///C:/Program Files (x86)/Corsair/CORSAIR iCUE Software/QtQuick/Dialogs/DefaultFileDialog.qml:210:25: QML ListView: Binding loop detected for property "model"
2018-08-18T23:11:24 C qml: CueColorPalette is deprecated since v3.0. Use QmlColorPalette instead.
2018-08-18T23:11:24 W file:///C:/Program Files (x86)/Corsair/CORSAIR iCUE Software/QtQuick/Dialogs/DefaultFileDialog.qml:210:25: QML ListView: Binding loop detected for property "model"
2018-08-18T23:11:24 W libpng warning: iCCP: known incorrect sRGB profile
2018-08-18T23:11:24 W libpng warning: iCCP: known incorrect sRGB profile
2018-08-18T23:11:24 W libpng warning: iCCP: known incorrect sRGB profile
2018-08-18T23:11:24 C qml: CueColorPalette is deprecated since v3.0. Use QmlColorPalette instead.
2018-08-18T23:11:24 C qml: CueColorPalette is deprecated since v3.0. Use QmlColorPalette instead.
2018-08-18T23:11:24 W file:///C:/Program Files (x86)/Corsair/CORSAIR iCUE Software/QtQuick/Dialogs/DefaultFileDialog.qml:210:25: QML ListView: Binding loop detected for property "model"
2018-08-18T23:11:24 W qrc:/qml/ui/settings/DeviceSettings.qml:37:11: QML ColumnLayout: Binding loop detected for property "contentHeight"
2018-08-18T23:11:24 W qrc:/qml/collection/AccordionTitle.qml:37: ReferenceError: backgroundOpacity is not defined
2018-08-18T23:11:24 C qml: CueColorPalette is deprecated since v3.0. Use QmlColorPalette instead.
2018-08-18T23:11:24 C qml: CueColorPalette is deprecated since v3.0. Use QmlColorPalette instead.
2018-08-18T23:11:24 C qml: CueColorPalette is deprecated since v3.0. Use QmlColorPalette instead.
2018-08-18T23:11:24 C qml: CueColorPalette is deprecated since v3.0. Use QmlColorPalette instead.
2018-08-18T23:11:24 C qml: CueColorPalette is deprecated since v3.0. Use QmlColorPalette instead.
2018-08-18T23:11:24 C qml: CueColorPalette is deprecated since v3.0. Use QmlColorPalette instead.
2018-08-18T23:11:24 C qml: CueColorPalette is deprecated since v3.0. Use QmlColorPalette instead.
2018-08-18T23:11:24 C qml: CueColorPalette is deprecated since v3.0. Use QmlColorPalette instead.
2018-08-18T23:11:24 C qml: CueColorPalette is deprecated since v3.0. Use QmlColorPalette instead.
2018-08-18T23:11:24 C qml: CueColorPalette is deprecated since v3.0. Use QmlColorPalette instead.
2018-08-18T23:11:24 C qml: CueColorPalette is deprecated since v3.0. Use QmlColorPalette instead.
2018-08-18T23:11:24 C qml: CueColorPalette is deprecated since v3.0. Use QmlColorPalette instead.
2018-08-18T23:11:24 C qml: CueColorPalette is deprecated since v3.0. Use QmlColorPalette instead.
2018-08-18T23:11:24 C qml: CueColorPalette is deprecated since v3.0. Use QmlColorPalette instead.
2018-08-18T23:11:24 C qml: CueColorPalette is deprecated since v3.0. Use QmlColorPalette instead.
Reply With Quote


  #11  
Old 08-18-2018, 11:34 PM
Leemarvin Leemarvin is offline
Registered User
Leemarvin's PC Specs
 
Join Date: Dec 2014
Posts: 35
POST ID # = 969288
Leemarvin Reputation: 10
Default

So I did something I didn't do before, I put the four sticks all of them in the left side slots, and they were all detected by iCUE and I could apply the effects. Really I don't have a clue of why iCUE doesn't detect my right side slots.

The easy thing to point is the motherboard, but I guess that if the right side slots weren't functioning correctly the RAM wouldn't work at all and is not the case.

Is strange because every other software detects the four sticks wherever I put them...eally a shame that I cannot control them all if I put them in their correct slots.

I guess that might be some compatibility issue regarding iCUE and X99 mobos, or at elast ASUS's ones, or maybe just my model the Deluxe.

I'm going to put an older BIOS just as a last attemp, I really don't know what else to do.
Reply With Quote


  #12  
Old 08-19-2018, 01:05 PM
Corsair Art's Avatar
Corsair Art Corsair Art is offline
Corsair Employee
 
Join Date: Feb 2016
Posts: 543
POST ID # = 969337
Corsair Art Reputation: 14
Default

Quote:
Originally Posted by Leemarvin View Post
So I did something I didn't do before, I put the four sticks all of them in the left side slots, and they were all detected by iCUE and I could apply the effects. Really I don't have a clue of why iCUE doesn't detect my right side slots.

The easy thing to point is the motherboard, but I guess that if the right side slots weren't functioning correctly the RAM wouldn't work at all and is not the case.

Is strange because every other software detects the four sticks wherever I put them...eally a shame that I cannot control them all if I put them in their correct slots.

I guess that might be some compatibility issue regarding iCUE and X99 mobos, or at elast ASUS's ones, or maybe just my model the Deluxe.

I'm going to put an older BIOS just as a last attemp, I really don't know what else to do.
Sorry if I've missed this, but did you enable SPD WRITE within bios?

-Art
Reply With Quote


  #13  
Old 08-19-2018, 03:54 PM
Leemarvin Leemarvin is offline
Registered User
Leemarvin's PC Specs
 
Join Date: Dec 2014
Posts: 35
POST ID # = 969349
Leemarvin Reputation: 10
Default

Quote:
Originally Posted by Corsair Art View Post
Sorry if I've missed this, but did you enable SPD WRITE within bios?

-Art
From my second post here days ago, first sentence:

Quote:
Well I've managed to find some partial solution:

1. I've found a G.Skillll guide where it showed me where to find the location of SPD Write in my mobo in order to enable it.
2. That allowed me to finally update the firmware and take control of my RAM in iCUE, yet..
3. I could only do it when using the slots from the left side of my CPU...I had to put the RAM on the grey slots from my left side in turns, in order to first update the firmware and later adjust the lighting.
4. So in conclusion I have now managed to have all the RAM in one static color, but still iCUE only recognizes the RAM in the left side slots.
5. Like I've stated before, BIOS, Windows and the rest of the software installed in my PC recognizes the full 32gb (bar Photoshop that because of a weird bug only sees 25gb)

Any idea of how to solve this and get iCue recognize the modules that I have in my right side of the CPU? Is there some test I can run to see if there is some hardware problem anywhere? thanks in advance

PD I'm uploading some pics as example
Attached Images

Please Art, make someone look at the LOGs I've posted above in a prior post, there are errors there that I do not undesrtand but someone in the support departmente might. Thank you.
Reply With Quote


  #14  
Old 08-20-2018, 10:00 AM
Corsair Art's Avatar
Corsair Art Corsair Art is offline
Corsair Employee
 
Join Date: Feb 2016
Posts: 543
POST ID # = 969426
Corsair Art Reputation: 14
Default

Quote:
Originally Posted by Leemarvin View Post
From my second post here days ago, first sentence:




Please Art, make someone look at the LOGs I've posted above in a prior post, there are errors there that I do not undesrtand but someone in the support departmente might. Thank you.
Hi Leemarvin,

I've seen them on the ticket as well, not something we can provide you immediate assistance with through either medium I'm afraid.
Reply With Quote


Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -4. The time now is 04:11 AM.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2018, vBulletin Solutions, Inc.