Jump to content
HWBOT Community Forums


  • Content Count

  • Joined

  • Last visited

Everything posted by dimi33

  1. It all looks more and more that this is actually a C-die as you guys said (or value B-die if they can be named like that). Haven't removed the HS to check the dimms but based on the tests i did yesterday, and the day before, it looks like they are prolly C-die since using voltages between 1.325 and 1.365 actually worked to hit 3733 and 3800 with loose timings but had to make adjustments to procodt/SoC and Cadbus. Raising the voltage past 1.38-1.39 at these frequencies immediately made things unstable. Also,It seems higher proCodt has to be set with higher SoC and vice-versa(lower proCodt
  2. Well that was my thought as well since from what i have gathered around it seems these results are comparable to c-die and not to b-die, yet, the sotware reports it as b-die(even the module part number corresponds to b-die[K4A8G085WB BCPB].Bear in mind though that this is a B1 PCB (dual rank) and i think these overclock way worse than A1/A0. And you are right about higher voltages. 3533mhz was giving errors at 1.42v, yet it was stable at 1.385/1.395.Could this really be a C-die being reported as B-die in software?
  3. Hello all, I'm trying to see how much i can overclock this ram kit i have which to be honest it probably didnt have much potential from the start since it is a 3200C16 - 32GB. Dram calculator(only used it to check bin quality - not using its output for setting the timings) shows a 81% bin quality so im not sure if i am to take this with a grain of salt.I just think this is one of the low end b-dies. However, in order to see if i can hit 3600, i set docp to manual, set all timings to auto and put 1.45v on dram and soc at 1.15v. That would result in no boot. However,
  • Create New...