Overclock.net › Forums › AMD › AMD Motherboards › ROG Crosshair VI overclocking thread
New Posts  All Forums:Forum Nav:

ROG Crosshair VI overclocking thread - Page 1137

post #11361 of 17778
biggrin.gif
Quote:
Originally Posted by Mumak View Post

Several Intel systems block SPD write access as a security mechanism.

And G.Skill say .... doh.gif ....

As always many thanks Martin for your help smile.gif .
XPS - R7 1700
(14 items)
 
XPS - i5 4690K
(12 items)
 
XPS - Q6600
(8 items)
 
CPUMotherboardGraphicsRAM
Ryzen 7 1700 Asus Crosshair VI Hero Sapphire Fury X@1145/545 G.Skill Trident Z 2x 8GB 3200MHz C14 
Hard DriveCoolingCoolingCooling
Samsung Evo 840 ThermalRight Archon IB-E X2 + 2x TY143 ThermalRight TY-143 2x front case intake Arctic Cooling F12 + 2x F9 as rear case exhaust 
OSMonitorKeyboardPower
Win 7 Pro x64 / Win 10 Pro x64 Asus MG279Q Cherry MX-Board 3.0 Cooler Master V850 
CaseMouse
SilverStone TJ06 Logitech G700S 
CPUMotherboardGraphicsRAM
i5 4690K@4.9GHz 1.255V Asus Maximus VII Ranger Sapphire Fury X@1145/545 HyperX Savage 2x8GB 2400MHz C11 
Hard DriveCoolingOSMonitor
Samsung Evo 840 TR Archon SB-E X2 Win 7 Pro x64 / Win 10 x64 Asus MG279Q 
KeyboardPowerCaseMouse
Cherry MX-Board 3.0 Cooler Master V850 SilverStone TJ06 Logitech G700S 
CPUMotherboardGraphicsRAM
Intel Q6600 G0 Asus P5K Premium Black Pearl Sapphire Toxic HD5850 Corsair Dominator 4GB 
Hard DriveCoolingOSPower
Crucial MX 100 256GB TR TRUE Rev.A Win 7 Pro x64 Cooler Master V650 
  hide details  
Reply
XPS - R7 1700
(14 items)
 
XPS - i5 4690K
(12 items)
 
XPS - Q6600
(8 items)
 
CPUMotherboardGraphicsRAM
Ryzen 7 1700 Asus Crosshair VI Hero Sapphire Fury X@1145/545 G.Skill Trident Z 2x 8GB 3200MHz C14 
Hard DriveCoolingCoolingCooling
Samsung Evo 840 ThermalRight Archon IB-E X2 + 2x TY143 ThermalRight TY-143 2x front case intake Arctic Cooling F12 + 2x F9 as rear case exhaust 
OSMonitorKeyboardPower
Win 7 Pro x64 / Win 10 Pro x64 Asus MG279Q Cherry MX-Board 3.0 Cooler Master V850 
CaseMouse
SilverStone TJ06 Logitech G700S 
CPUMotherboardGraphicsRAM
i5 4690K@4.9GHz 1.255V Asus Maximus VII Ranger Sapphire Fury X@1145/545 HyperX Savage 2x8GB 2400MHz C11 
Hard DriveCoolingOSMonitor
Samsung Evo 840 TR Archon SB-E X2 Win 7 Pro x64 / Win 10 x64 Asus MG279Q 
KeyboardPowerCaseMouse
Cherry MX-Board 3.0 Cooler Master V850 SilverStone TJ06 Logitech G700S 
CPUMotherboardGraphicsRAM
Intel Q6600 G0 Asus P5K Premium Black Pearl Sapphire Toxic HD5850 Corsair Dominator 4GB 
Hard DriveCoolingOSPower
Crucial MX 100 256GB TR TRUE Rev.A Win 7 Pro x64 Cooler Master V650 
  hide details  
Reply
post #11362 of 17778
Quote:
Originally Posted by Mumak View Post

You need to run HWiNFO in Debug Mode, see here for more details about that: https://www.hwinfo.com/forum/Thread-IMPORTANT-Read-this-before-submitting-a-report

I believe the problem with corrupted SPD is due to a conflict between software that writes to SPD and any other software that accesses SPD during the same time.
DDR4 has 2 banks of 256 bytes for SPD and to read the entire SPD, it's required to send a command (via SMBus) to switch the banks.
So if such a bank switch command happens during the write cycle, it can cause corruption.
Another problem might happen if multiple tools send an SMBus command at the same time, not just bank switch.
To avoid problems of concurrent SPD access, tools like HWiNFO, AIDA64, CPU-Z and some others are synchronized - we use a global mutex which we hold during the entire access operation and anyone else attempting to access SPD if using the same mechanism will wait for that mutex and only if it's released, will perform the operation.
I believe that Aura or G.Skill software don't support this mechanism and think they're the only ones accessing SPD. Not sure about Typhoon. Anyway, a correct implementation of synchronization would require that ALL tools accessing SPD support this mechanism. This should significantly reduce the probability of a conflict, though you can't avoid that for 100%. Writing to SPD should never be done, it's a fatal design. Several Intel systems block SPD write access as a security mechanism.

Thanks again for the help in reviewing my debug files, hopefully getting new memory will solve the difficulty I was having in getting to UEFI after a clear CMOS with switching bios versions. Maybe be able to tighten timings better as well. I'm just about to punch the order button on either some 3600 MHz or some 4266 MHz DRAM for the replacements - having trouble deciding.
post #11363 of 17778
Does OC.net have a g.skill rep?

Might be worth tagging them if so.
post #11364 of 17778
Quote:
Originally Posted by gupsterg View Post

biggrin.gif
And G.Skill say .... doh.gif ....

As always many thanks Martin for your help smile.gif .

I think I'll wait for G.Skill and Asus to acknowledge the issue before sending my RAM for RMA, not risking sending the sticks only to get told that I'm to blame for their software shortcomings smile.gif
Main Rig
(16 items)
 
  
CPUMotherboardGraphicsRAM
AMD Ryzen 1700 - 3.810GHz - 1.286v Asus Crosshair VI Hero MSI 1080 Ti Gaming X - 1.000mv 2012/6210 G.Skill Trident Z 16GB 3600Mhz CL16 RGB 
Hard DriveHard DriveOSMonitor
850 evo 120GB (for OS + programs) 850 evo 250GB (for Games) Windows 10 LG 27ea73LM-P 
KeyboardPowerCaseMouse
Razer BlackWidow Ultimate 2013 Corsair RM750x Corsair Obsidian 750D Razer DeathAdder 2013 
Mouse PadAudioAudioAudio
Razer Goliathus Razer Kraken Pro Sennheiser HD 598 Sound Blaster Z  
  hide details  
Reply
Main Rig
(16 items)
 
  
CPUMotherboardGraphicsRAM
AMD Ryzen 1700 - 3.810GHz - 1.286v Asus Crosshair VI Hero MSI 1080 Ti Gaming X - 1.000mv 2012/6210 G.Skill Trident Z 16GB 3600Mhz CL16 RGB 
Hard DriveHard DriveOSMonitor
850 evo 120GB (for OS + programs) 850 evo 250GB (for Games) Windows 10 LG 27ea73LM-P 
KeyboardPowerCaseMouse
Razer BlackWidow Ultimate 2013 Corsair RM750x Corsair Obsidian 750D Razer DeathAdder 2013 
Mouse PadAudioAudioAudio
Razer Goliathus Razer Kraken Pro Sennheiser HD 598 Sound Blaster Z  
  hide details  
Reply
post #11365 of 17778
I believe the SPD corruption problem can be only fixed if all tools writing to SPD would synchronize with others using the method I have described above.
The name of the mutex to interlock SPD/SMBus access is: "Global\Access_SMBUS.HTP.Method"
When this would be implemented, then list all tools supporting this mechanism as approved to be used concurrently.
Until then those who don't want to run into troubles - best would be to completely avoid running any RGB controlling software. If you still do, then make sure not to run with any other system monitoring/information tools that might read SPD or access SMBus. Approved applications currently are: Notepad, Solitaire, Calculator biggrin.gif
post #11366 of 17778
Quote:
Originally Posted by Mumak View Post

I believe the SPD corruption problem can be only fixed if all tools writing to SPD would synchronize with others using the method I have described above.
The name of the mutex to interlock SPD/SMBus access is: "Global\Access_SMBUS.HTP.Method"
When this would be implemented, then list all tools supporting this mechanism as approved to be used concurrently.
Until then those who don't want to run into troubles - best would be to completely avoid running any RGB controlling software. If you still do, then make sure not to run with any other system monitoring/information tools that might read SPD or access SMBus. Approved applications currently are: Notepad, Solitaire, Calculator biggrin.gif

Thanks again, I only have a question, can you tell by my debug files above if my RAM SPD on the fourth slot can keep going (assuming I don't use Aura at all) till we get an official answer from Asus/G.Skill about the issue? Like I said, I don't want to risk getting told that I'm not under RMA because of the different SPD values. Personally, other than the reading issues with XMP I haven't noticed anything weird performance wise, and it doesn't show errors with memtest64. I'm setting both speed and timings manually though.
Edited by Clukos - 4/25/17 at 1:15am
Main Rig
(16 items)
 
  
CPUMotherboardGraphicsRAM
AMD Ryzen 1700 - 3.810GHz - 1.286v Asus Crosshair VI Hero MSI 1080 Ti Gaming X - 1.000mv 2012/6210 G.Skill Trident Z 16GB 3600Mhz CL16 RGB 
Hard DriveHard DriveOSMonitor
850 evo 120GB (for OS + programs) 850 evo 250GB (for Games) Windows 10 LG 27ea73LM-P 
KeyboardPowerCaseMouse
Razer BlackWidow Ultimate 2013 Corsair RM750x Corsair Obsidian 750D Razer DeathAdder 2013 
Mouse PadAudioAudioAudio
Razer Goliathus Razer Kraken Pro Sennheiser HD 598 Sound Blaster Z  
  hide details  
Reply
Main Rig
(16 items)
 
  
CPUMotherboardGraphicsRAM
AMD Ryzen 1700 - 3.810GHz - 1.286v Asus Crosshair VI Hero MSI 1080 Ti Gaming X - 1.000mv 2012/6210 G.Skill Trident Z 16GB 3600Mhz CL16 RGB 
Hard DriveHard DriveOSMonitor
850 evo 120GB (for OS + programs) 850 evo 250GB (for Games) Windows 10 LG 27ea73LM-P 
KeyboardPowerCaseMouse
Razer BlackWidow Ultimate 2013 Corsair RM750x Corsair Obsidian 750D Razer DeathAdder 2013 
Mouse PadAudioAudioAudio
Razer Goliathus Razer Kraken Pro Sennheiser HD 598 Sound Blaster Z  
  hide details  
Reply
post #11367 of 17778
Quote:
Originally Posted by SpecChum View Post

Does OC.net have a g.skill rep?

Might be worth tagging them if so.

Already done/posted in a thread which is about Ryzen, have other members where RGB dimms died on Gigabyte, Asrock ...

Link.
XPS - R7 1700
(14 items)
 
XPS - i5 4690K
(12 items)
 
XPS - Q6600
(8 items)
 
CPUMotherboardGraphicsRAM
Ryzen 7 1700 Asus Crosshair VI Hero Sapphire Fury X@1145/545 G.Skill Trident Z 2x 8GB 3200MHz C14 
Hard DriveCoolingCoolingCooling
Samsung Evo 840 ThermalRight Archon IB-E X2 + 2x TY143 ThermalRight TY-143 2x front case intake Arctic Cooling F12 + 2x F9 as rear case exhaust 
OSMonitorKeyboardPower
Win 7 Pro x64 / Win 10 Pro x64 Asus MG279Q Cherry MX-Board 3.0 Cooler Master V850 
CaseMouse
SilverStone TJ06 Logitech G700S 
CPUMotherboardGraphicsRAM
i5 4690K@4.9GHz 1.255V Asus Maximus VII Ranger Sapphire Fury X@1145/545 HyperX Savage 2x8GB 2400MHz C11 
Hard DriveCoolingOSMonitor
Samsung Evo 840 TR Archon SB-E X2 Win 7 Pro x64 / Win 10 x64 Asus MG279Q 
KeyboardPowerCaseMouse
Cherry MX-Board 3.0 Cooler Master V850 SilverStone TJ06 Logitech G700S 
CPUMotherboardGraphicsRAM
Intel Q6600 G0 Asus P5K Premium Black Pearl Sapphire Toxic HD5850 Corsair Dominator 4GB 
Hard DriveCoolingOSPower
Crucial MX 100 256GB TR TRUE Rev.A Win 7 Pro x64 Cooler Master V650 
  hide details  
Reply
XPS - R7 1700
(14 items)
 
XPS - i5 4690K
(12 items)
 
XPS - Q6600
(8 items)
 
CPUMotherboardGraphicsRAM
Ryzen 7 1700 Asus Crosshair VI Hero Sapphire Fury X@1145/545 G.Skill Trident Z 2x 8GB 3200MHz C14 
Hard DriveCoolingCoolingCooling
Samsung Evo 840 ThermalRight Archon IB-E X2 + 2x TY143 ThermalRight TY-143 2x front case intake Arctic Cooling F12 + 2x F9 as rear case exhaust 
OSMonitorKeyboardPower
Win 7 Pro x64 / Win 10 Pro x64 Asus MG279Q Cherry MX-Board 3.0 Cooler Master V850 
CaseMouse
SilverStone TJ06 Logitech G700S 
CPUMotherboardGraphicsRAM
i5 4690K@4.9GHz 1.255V Asus Maximus VII Ranger Sapphire Fury X@1145/545 HyperX Savage 2x8GB 2400MHz C11 
Hard DriveCoolingOSMonitor
Samsung Evo 840 TR Archon SB-E X2 Win 7 Pro x64 / Win 10 x64 Asus MG279Q 
KeyboardPowerCaseMouse
Cherry MX-Board 3.0 Cooler Master V850 SilverStone TJ06 Logitech G700S 
CPUMotherboardGraphicsRAM
Intel Q6600 G0 Asus P5K Premium Black Pearl Sapphire Toxic HD5850 Corsair Dominator 4GB 
Hard DriveCoolingOSPower
Crucial MX 100 256GB TR TRUE Rev.A Win 7 Pro x64 Cooler Master V650 
  hide details  
Reply
post #11368 of 17778
Quote:
Originally Posted by Clukos View Post

Thanks again, I only have a question, can you tell by my debug files above if my RAM SPD on the fourth slot can keep going (assuming I don't use Aura at all) till we get an official answer from Asus/G.Skill about the issue? Like I said, I don't want to risk getting told that I'm not under RMA because of the different SPD values. Personally, other than the reading issues with XMP I haven't noticed anything weird performance wise, and it doesn't show errors with memtest64. I'm setting both speed and timings manually though.

Sorry, but that's corrupted too. Several fields including timing data are corrupt.
post #11369 of 17778
Quote:
Originally Posted by Mumak View Post

Sorry, but that's corrupted too. Several fields including timing data are corrupt.

Is it on both sticks or just the one that is not reading XMP correctly? What I'm thinking is that even if I get a replacement I could be facing the same issue. Do we know for certain that Aura is to blame?
Main Rig
(16 items)
 
  
CPUMotherboardGraphicsRAM
AMD Ryzen 1700 - 3.810GHz - 1.286v Asus Crosshair VI Hero MSI 1080 Ti Gaming X - 1.000mv 2012/6210 G.Skill Trident Z 16GB 3600Mhz CL16 RGB 
Hard DriveHard DriveOSMonitor
850 evo 120GB (for OS + programs) 850 evo 250GB (for Games) Windows 10 LG 27ea73LM-P 
KeyboardPowerCaseMouse
Razer BlackWidow Ultimate 2013 Corsair RM750x Corsair Obsidian 750D Razer DeathAdder 2013 
Mouse PadAudioAudioAudio
Razer Goliathus Razer Kraken Pro Sennheiser HD 598 Sound Blaster Z  
  hide details  
Reply
Main Rig
(16 items)
 
  
CPUMotherboardGraphicsRAM
AMD Ryzen 1700 - 3.810GHz - 1.286v Asus Crosshair VI Hero MSI 1080 Ti Gaming X - 1.000mv 2012/6210 G.Skill Trident Z 16GB 3600Mhz CL16 RGB 
Hard DriveHard DriveOSMonitor
850 evo 120GB (for OS + programs) 850 evo 250GB (for Games) Windows 10 LG 27ea73LM-P 
KeyboardPowerCaseMouse
Razer BlackWidow Ultimate 2013 Corsair RM750x Corsair Obsidian 750D Razer DeathAdder 2013 
Mouse PadAudioAudioAudio
Razer Goliathus Razer Kraken Pro Sennheiser HD 598 Sound Blaster Z  
  hide details  
Reply
post #11370 of 17778
Quote:
Originally Posted by Clukos View Post

Is it on both sticks or just the one that is not reading XMP correctly? What I'm thinking is that even if I get a replacement I could be facing the same issue. Do we know for certain that Aura is to blame?

I don't have a 'reference' dump of a module that would be 100% OK, but I suppose both your modules are affected.
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: AMD Motherboards
Overclock.net › Forums › AMD › AMD Motherboards › ROG Crosshair VI overclocking thread