Teamgroup 2600 c10 2 x 4gb issues
- Thread starter MrPils
- Start date
ok thanks,
as you can see, your read speed is way lower than the write. this was the case with mine, until i set trdrd back to 4.
but, you dont seem to have that timing, must be a platform thing. but you are losing a good 7-8GB/s on that if you can find it.
ill upload a picture later but its at
~39,000
~41,000
~38,000
~41
as you can see, your read speed is way lower than the write. this was the case with mine, until i set trdrd back to 4.
but, you dont seem to have that timing, must be a platform thing. but you are losing a good 7-8GB/s on that if you can find it.
ill upload a picture later but its at
~39,000
~41,000
~38,000
~41
Last edited:
Quick update:
Default vccsa and vccio failed in 7 minutes...considerably faster.
Default vccsa and 1.2 vccio failed in just under 2 hours.
As a reminder 1.1vccsa and 1.15 vccio failed in 3 1/2 hours.
It looks like im finally seeing some reaction to voltage change now ive swapped the dimms round in the slots, hopefully I can tune in to stability.
Next step will be a run at 1.15vccio to see if it fails faster than 1.2vccio, and therefore if its worth trying further increases. Following that ill be doing some independant vccsa testing, then hopefully putting them both together. The point in that being once I have found where increasing voltage no longer increases stability I can set both voltages to their respective values.
Still finding it somewhat annoying that XMP is not stable. XMP should always be 100% stable and offer you a base to tweak from. I am still getting the feeling I need a slight nudge of vdimm (1.67v - 1.68v), but we shall see.
Default vccsa and vccio failed in 7 minutes...considerably faster.
Default vccsa and 1.2 vccio failed in just under 2 hours.
As a reminder 1.1vccsa and 1.15 vccio failed in 3 1/2 hours.
It looks like im finally seeing some reaction to voltage change now ive swapped the dimms round in the slots, hopefully I can tune in to stability.
Next step will be a run at 1.15vccio to see if it fails faster than 1.2vccio, and therefore if its worth trying further increases. Following that ill be doing some independant vccsa testing, then hopefully putting them both together. The point in that being once I have found where increasing voltage no longer increases stability I can set both voltages to their respective values.
Still finding it somewhat annoying that XMP is not stable. XMP should always be 100% stable and offer you a base to tweak from. I am still getting the feeling I need a slight nudge of vdimm (1.67v - 1.68v), but we shall see.
This thread is kinda split as theres a portion of it over at ask 8pack...I didnt want anyone thinking it had gone unanswered or abandoned so theres a couple of replies there. This is notable enough to duplicate here :
And my reply :
Damn you TRAS! Its quite feasible its benchable and mostly stable set low (under 30), but needs raising for full prime stability (or perhaps it just needs big volts). That would explain the reputation for low tras in samsung based kits anyway.
Still, XMP should set 35 if it needs 35 for stability, it shouldnt take this much effort to get them stable. This has been quite a poor experience with Teamgroup for me so far!
And my reply :
Damn you TRAS! Its quite feasible its benchable and mostly stable set low (under 30), but needs raising for full prime stability (or perhaps it just needs big volts). That would explain the reputation for low tras in samsung based kits anyway.
Still, XMP should set 35 if it needs 35 for stability, it shouldnt take this much effort to get them stable. This has been quite a poor experience with Teamgroup for me so far!
WHy should XMP be stable when your running an IMC at 2600mhz which is 1000mhz above spec!!! XMP also only sets primary timings in the main. Its the Bios and board manufacturer that sets the rest for comp and perf.
Here are stable Haswell and Ivy settings. VDRAM is 1.65v
Ivy 2600
The Transmitter slews are 3,3,4,4 down the Bios.
Haswell 2600 and 2666
Bios shots for Haswell 2600 as Memtweakit was not working for me on this old OS.
[URL=http://imageshack.com/i/f31uf0j/]
and 2666
[/URL]
[/URL]
Here are stable Haswell and Ivy settings. VDRAM is 1.65v
Ivy 2600
The Transmitter slews are 3,3,4,4 down the Bios.
Haswell 2600 and 2666
Bios shots for Haswell 2600 as Memtweakit was not working for me on this old OS.
[URL=http://imageshack.com/i/f31uf0j/]
and 2666
Not wishing to sound ungrateful or anything, but XMP timings that are not stable is a bit of an issue when you're trying to get everything set up isn't it? It's at the very least somewhat misleading. TRAS is part of the xmp spec and it sets it to 31 so I expected 31 to be stable. I wasn't aware that the IMC had any impact at all on primary timings (hence why only primaries are set by XMP).
Anyway, muchas gracias for spending the time and posting the screens up...I'll have a play around with your posted timings over the weekend and see what happens. I'm still not totally convinced my kit isn't faulty, but at this point I'm really glad I didn't just send it back when the rma was authorised. Now I have some settings I know should work (and the sticks are finally responding to IMC and VTT voltage changes after swapping slots) I've a busy weekend ahead with this memory it seems!
Anyway, muchas gracias for spending the time and posting the screens up...I'll have a play around with your posted timings over the weekend and see what happens. I'm still not totally convinced my kit isn't faulty, but at this point I'm really glad I didn't just send it back when the rma was authorised. Now I have some settings I know should work (and the sticks are finally responding to IMC and VTT voltage changes after swapping slots) I've a busy weekend ahead with this memory it seems!
IMC impacts on everything mate. My BBSE can do CAS5 2600 on two cpu I have. On another ten I tried they cant. Once you overclock the IMC everything plays a part, including all timings.
Your IMC may well be good for mhz but not timings.
You need to use your rig also instead of running prime for 24 hours. Prime only shows the rig can do prime.
Your IMC may well be good for mhz but not timings.
You need to use your rig also instead of running prime for 24 hours. Prime only shows the rig can do prime.
Noted about MHz and not timings. I've actually got some decent BBSE and PSC sticks knocking about that I could test 2600 with, however i'm not convinced it would have any relevance given they have different IC density to the HCH9's.
And yeah using the rig is the main priority....I pulled out prime as it was the only stress test that was picking up errors consistent with my game crashes/freezes. Linx and 32m both run fine annoyingly, even at 4.6ghz cpu. That and my 24" DGM L-2442WD blew its power board on Monday night, and gaming at 1280x1024 just makes me angry lol
And yeah using the rig is the main priority....I pulled out prime as it was the only stress test that was picking up errors consistent with my game crashes/freezes. Linx and 32m both run fine annoyingly, even at 4.6ghz cpu. That and my 24" DGM L-2442WD blew its power board on Monday night, and gaming at 1280x1024 just makes me angry lol
I last tried mine on P67...the max I had on air was 7-10-7 (PSC) or 8-9-8 (BBSE) @ 2300ish 1.85v-1.95v for benching. Never thought to try them 2400+ on Ivy...shame about 2600 though it would've been nice to see if it would post/boot at c8 or c9.
I'll give that a quick shot...saved my best 6 sticks when I shifted all my old benching gear so they should be plenty capable of at least a post. I still have a really good pair of hypers too, they were worth worthless on P67 and Sandy due to random BSODs benching, but if I'm digging out my 2gb sticks I may as well give them a quick tickle and they could always post really easily.
If I'm forced to use c10 or even c11 at 2600 then it would start to point things towards the IMC not reaching the timings rather than the new kit being faulty.
If I'm forced to use c10 or even c11 at 2600 then it would start to point things towards the IMC not reaching the timings rather than the new kit being faulty.
.You can't tweak the main sub which is making a huge huge read difference, is my point. Same as your results, read speed way too low.
It was.. I was messing around with it to try and tweak it. But now when I reset 8 packs timings, the auto timings are being set way lower than his for some reason. Now it's crashing. Reset to what I think is right.. And testing again
Edit,
Took sticks out, put back and now the above timings are working again (I think) so weird..
Also 8pack I've noticed that your bios is different to mine, you don't have latency boundary a and b after the primary timings? Is that a shamino bios thing?
It was.. I was messing around with it to try and tweak it. But now when I reset 8 packs timings, the auto timings are being set way lower than his for some reason. Now it's crashing. Reset to what I think is right.. And testing again
Edit,
Took sticks out, put back and now the above timings are working again (I think) so weird..
Also 8pack I've noticed that your bios is different to mine, you don't have latency boundary a and b after the primary timings? Is that a shamino bios thing?
Last edited:
Spoke too soon, crashing again
edit:
given up, samsung is back in, stable and getting better bench results than this kit has managed while stable.
thanks for your help guys, its been really nice of you 8 pack trying to get this working for me i appreciate it a lot.
edit:
given up, samsung is back in, stable and getting better bench results than this kit has managed while stable.
thanks for your help guys, its been really nice of you 8 pack trying to get this working for me i appreciate it a lot.
Last edited: