- Joined
- Jul 30, 2019
- Messages
- 3,440 (1.69/day)
System Name | Still not a thread ripper but pretty good. |
---|---|
Processor | Ryzen 9 7950x, Thermal Grizzly AM5 Offset Mounting Kit, Thermal Grizzly Extreme Paste |
Motherboard | ASRock B650 LiveMixer (BIOS/UEFI version P3.08, AGESA 1.2.0.2) |
Cooling | EK-Quantum Velocity, EK-Quantum Reflection PC-O11, D5 PWM, EK-CoolStream PE 360, XSPC TX360 |
Memory | Micron DDR5-5600 ECC Unbuffered Memory (2 sticks, 64GB, MTC20C2085S1EC56BD1) + JONSBO NF-1 |
Video Card(s) | XFX Radeon RX 5700 & EK-Quantum Vector Radeon RX 5700 +XT & Backplate |
Storage | Samsung 4TB 980 PRO, 2 x Optane 905p 1.5TB (striped), AMD Radeon RAMDisk |
Display(s) | 2 x 4K LG 27UL600-W (and HUANUO Dual Monitor Mount) |
Case | Lian Li PC-O11 Dynamic Black (original model) |
Audio Device(s) | Corsair Commander Pro for Fans, RGB, & Temp Sensors (x4) |
Power Supply | Corsair RM750x |
Mouse | Logitech M575 |
Keyboard | Corsair Strafe RGB MK.2 |
Software | Windows 10 Professional (64bit) |
Benchmark Scores | RIP Ryzen 9 5950x, ASRock X570 Taichi (v1.06), 128GB Micron DDR4-3200 ECC UDIMM (18ASF4G72AZ-3G2F1) |
I did my research and built that system back in 2009 so that gave me about 2yrs worth of history to research to look at for that CPU when building my system at the time including online forums and such. I wasn't pioneering anything new and was following in others footsteps in building an ECC ram capable system. I don't know what else to say to convince you other than maybe screen shots of BIOS and POST screens showing the motherboard recognized and overclocked the ECC ram. Q6600 is a Kentsfield core rebranded Xeon chip to the best of what I remember. Intel has a history of select non-Xeon chips that could support ECC. Otherwise we will have to agree to disagree.Here is Intels list. You can utilize this to see exactly what cpus support ECC.
![]()
Intel product specifications
Intel® product specifications, features and compatibility quick reference guide and code name decoder. Compare products including processors, desktop boards, server products and networking products.www.intel.com
Unfortunately, it doesn't look to go as far back and cover socket 775.
Keep clicking show more.
It ends at 2007. All xeons only. No i5s. No i7s. No extreme chips. (For that time period)
CPU must have ECC support code embedded. Back then, it wasn't on desktop. Doesn't matter where the memory controller is loacted.
You have previously asserted incorrect statements about registered vs. unregistered memory. AM4/AM5 to my knowledge only supports unregistered ECC. If you want to use registered ECC you need an EPYC chip or Threadripper PRO. Having said that there are quite a variety of chips out there so ultimately you have to look at specific chip support as the memory controller is on the chip for modern CPU's, per the list I made item #1 don't rely on anyone's blanket statements research the parts you intend to use.Today, they do offer registered ECC support on just about everything.
What you said doesn't make sense. A memory overclock is when your run your ram out of spec (typically increasing frequency or lowing timings) JEDEC or not doesn't matter. JEDEC specs change over time as new capability emerge. I had/have overclocks on my ram as described that's fact.The claims where, to point out...
You didn't really overclock past ECC JEDEC.
Again I did my research back in 2009. Q6600 is a Kentsfield core rebranded Xeon chip to the best of what I remember. When paired with X38 it seemed to be recognized by BIOS and when the a ram module did start to fail the system failed as expected with a reboot (instead of silently corrupting my system or presenting BSOD's) until I removed the bad module after nearly 10 years of 24/7 operation. As far as I'm concerned it worked and it worked as expected.Q6600 doesn't support ECC.
My understanding has been in the event of an uncorrectable error with ECC memory the system is supposed to halt or reboot.Maybe OCCT burn in shows memory errors, but the system doesn't halt or crash, but doesn't mean it's showing single bit errors either. Cause I am not sure that part.
ThanksBut you do make good points that I don't have the data to disprove.![]()
Last edited: