*Official Benchmark Thread* - Post it here or it didn't happen :D

[Mr. Fox]

9 minutes ago, Mr. Fox said:

If it is SPD corruption and not a hardware failure the firmware can be copied from the good module to the corrupted one. If I can find the link to where I saw how to do it (overclock.net) I will post it. You have to have a ROG Maximum motherboard or the tool will not work. Unless something has changed it will not work with a Strix, Prime or TUF motherboard.

@Rage Set not only OpenRGB but also Corsair iCUE has been known to corrupt the SPD. If that is the problem and not a hardware failure, here is the link that I discovered and the method I used to fix the corrupted SPD more than once.

https://www.overclock.net/threads/corrupted-ddr5-spd-fix-tutorial.1795935/

 

I see numerous links about Corsair iCUE doing the same thing as OpenRGB. You can also fix it another way (which I have not tried).

https://linustechtips.com/topic/1505572-am4-x570-system-no-longer-posts-with-4-sticks-of-memory-installed/?do=findComment&comment=15930927

[Rage Set]

1 hour ago, Mr. Fox said:

It corrupted the stick in the first slot and the system would boot if I moved the good one to the first slot and let the memory train, then turn it off and put the corrupted stick in the second slot. It would not boot at all with the corrupted stick in the first slot. In Windows, the corrupted stick showed everything was erased. This actually happened like 3 times. The first time I did not know what happened and the second and third times I fixed it.

 

I got the system to boot with both sticks, but while the bad stick is powered (raindow RGB flowing), it is not being detected. I am going to assume the Asus OCTools are exclusive to the Apex boards. As I can't find them and my AI Suite - ASUS Dual Intelligent Processors app doesn't have anything related to OC'ing RAM. So I guess, RMA is the route I must take.

 

Thanks for helping bro!!!

[Rage Set]

5 minutes ago, Mr. Fox said:

@Rage Set not only OpenRGB but also Corsair iCUE has been known to corrupt the SPD. If that is the problem and not a hardware failure, here is the link that I discovered and the method I used to fix the corrupted SPD more than once.

https://www.overclock.net/threads/corrupted-ddr5-spd-fix-tutorial.1795935/

 

I see numerous links about Corsair iCUE doing the same thing as OpenRGB. You can also fix it another way (which I have not tried).

https://linustechtips.com/topic/1505572-am4-x570-system-no-longer-posts-with-4-sticks-of-memory-installed/?do=findComment&comment=15930927

 

LOL, I was literally reading the first link and saw your reply in that thread. 

[Mr. Fox]

Just now, Rage Set said:

 

I got the system to boot with both sticks, but while the bad stick is powered (raindow RGB flowing), it is not being detected. I am going to assume the Asus OCTools are exclusive to the Apex boards. As I can't find them and my AI Suite - ASUS Dual Intelligent Processors app doesn't have anything related to OC'ing RAM. So I guess, RMA is the route I must take.

 

Thanks for helping bro!!!

I downloaded the OCTool from HWBOT forum. Let me see if I can locate the link. You don't need an Apex. A Maximus board of any kind will work if memory serves me correctly.

 

When I stopped trying to control the memory RGB lighting and removed any and all software to control it (including Armory Crap) the problem stopped and never returned.

[Mr. Fox]

17 minutes ago, Rage Set said:

 

LOL, I was literally reading the first link and saw your reply in that thread. 

What kind of DDR5 motherboards do you have? I do not know if it will work on an AMD system.

 

The ASUS OCTools are not specific to ASUS, but some features only work with a limited set of boards where i2c bus access is available using software. I do not think ASUS authors the tools, but they are commonly used by people like Safedisk that work for/with ASUS.

 

The same OCTools allowed me to override the Intel ARC GPU power limits and voltage to overclock it further. (It has an ARC tool feature that worked similar to the EVGA Classified tool.) I discovered that in a Skatterbencher video.

 

Edit: @Rage Set I believe it is bundled in this OCPak archive.

I found a link to it in this thread: https://community.hwbot.org/topic/220910-asus-rog-maximus-apex-z790-apex-15/#comments

[electrosoft]

1 hour ago, electrosoft said:

 

And lastly, 265k is a potential issue....but we will see.

 

Testing so far with the Corsair 9200 sticks

 

G2 8000 pass

G2 8200 pass

G2 8400 fail (and I mean within the first minute)

G4 8400 pass 

 

8400 G4 pass is the same as with the Kingbank sticks except the KB sticks required a fan and 1.5v. These 9200 sticks only require 1.45v and no fan.

 

I'll goose the voltages on the IMC to see how much further I can push it in G2 but falling off the rails at G2 8400 isn't a great portend of things to come. 

 

But first I'm going to see how far the MB can go in G4 just to see how far it can go with the newest BIOS. If it can do at least 8800 I'll keep it. If not, back to Amazon it goes and most likely a Unify is in my future unless I can find a well priced and properly working Apex.

 

Correction. I wasn't paying attention (in a rush today since it is the wife and my official holiday shopping all day "fun"), I forgot when you switch gears it auto resets the memory frequency to auto so that G4 pass run was at 5600 (DERP!). This means most likely last time in G4 it was back to auto frequency too when testing the KB sticks and it passed.

 

So I set it to G4 to remove the CPU from the equation, set to 8400 and it failed again on both the KB and Corsair sticks. So that is a double failure at G4 on the KB 8200 sticks and Vengeance 9200 sticks when testing 8400 but 8200 passes.

 

So now it is pointing to the MB not the CPU.

 

I'll dive back in either very late tonight or tomorrow as now onward to Xmas shopping and dinner and more shopping....

 

 

[Mr. Fox]

18 minutes ago, Mr. Fox said:

Edit: @Rage Set I believe it is bundled in this OCPak archive.

I found a link to it in this thread: https://community.hwbot.org/topic/220910-asus-rog-maximus-apex-z790-apex-15/#comments

There might be a newer version in the opening post by Safedisk in this thread:

https://community.hwbot.org/topic/242375-rog-crosshair-x870e-heroapexextreme/

 

I will have to see if it works on my X870E Apex motherboard.

 

https://www.dropbox.com/scl/fi/94dljuo7lj4o0luen1hc1/OCPak_1506.zip?rlkey=sgozvyrcy88kxxhbo3fpwdcya&e=1&st=9zd14xd6&dl=0

[Rage Set]

17 minutes ago, Mr. Fox said:

There might be a newer version in the opening post by Safedisk in this thread:

https://community.hwbot.org/topic/242375-rog-crosshair-x870e-heroapexextreme/

 

I will have to see if it works on my X870E Apex motherboard.

 

https://www.dropbox.com/scl/fi/94dljuo7lj4o0luen1hc1/OCPak_1506.zip?rlkey=sgozvyrcy88kxxhbo3fpwdcya&e=1&st=9zd14xd6&dl=0

 

I am using my Asus Z690 Extreme board. The good news, the newer version works with my board and I was able to read and save a copy of the working stick's firmware. The bad news, is the software doesn't see the other stick. 

 

EDIT: Yes, I had iCue on this machine. So it is likely what caused the issue with the bad stick. 

[Mr. Fox]

6 minutes ago, Rage Set said:

 

I am using my Asus Z690 Extreme board. The good news, the newer version works with my board and I was able to read and save a copy of the working stick's firmware. The bad news, is the software doesn't see the other stick. 

 

EDIT: Yes, I had iCue on this machine. So it is likely what caused the issue with the bad stick. 

Try with the naked green sticks as well as the RGB. That's a bummer that it doesn't see the other stick. That suggests it could be a hardware failure. Did you enable SPD Write in the BIOS? If not, enable that and try again and maybe it will work.

[Rage Set]

21 minutes ago, Mr. Fox said:

Try with the naked green sticks as well as the RGB. That's a bummer that it doesn't see the other stick. That suggests it could be a hardware failure. Did you enable SPD Write in the BIOS? If not, enable that and try again and maybe it will work.

 

So this is what I found out thus far.

 

The green stick - is dead as a door nail. The PC won't boot with it, at ALL. Even with the known working stick in A2, trained and etc. As soon as I put it in any slot outside of A2, the mobo just clicks whenever I press power. 

 

The bad G.Skill stick will boot with the known working stick in A2 after it has trained. I don't think it is hardware related, but it is definitely corrupted by that damn iCue software. I tried changing around the speeds to see if it could be detected. I even lowered the trained stick to 2133, lol. Still can't be detected but obviously it is getting power by the slot. It's almost behaving like a dummy stick. 

[Mr. Fox]

23 minutes ago, Rage Set said:

 

So this is what I found out thus far.

 

The green stick - is dead as a door nail. The PC won't boot with it, at ALL. Even with the known working stick in A2, trained and etc. As soon as I put it in any slot outside of A2, the mobo just clicks whenever I press power. 

 

The bad G.Skill stick will boot with the known working stick in A2 after it has trained. I don't think it is hardware related, but it is definitely corrupted by that damn iCue software. I tried changing around the speeds to see if it could be detected. I even lowered the trained stick to 2133, lol. Still can't be detected but obviously it is getting power by the slot. It's almost behaving like a dummy stick. 

If you can determine the target slot number with the tool after saving the SPD from the good stick, select the target slot for the dead stick and see if the tool will allow you to write to it. When I had the SPD corruption happening from OpenRGB the stick seemed dead. CPU-Z could not "see" it and the tool could not read from it, and Thaiphoon Burner showed the module had no firmware on it. But, I was able to select the target slot annd write the SPD from the good stick to the corrupted one. Set the BIOS for SPD Write enabled (or SPD write disable set to "enabled" depending on how it is worded in the BIOS) has to be toggled. It may not work, but it would be worth a shot. Maybe you will get lucky.