How did this happen...? I have a W3520 too..... please... do telll.... :)
Printable View
This didn't happen. That's a CPUZ error, nothing else. Still, looks good. :)
Man good luck with RMA, you really are struck with a run of bad luck aren't you?! Maybe this says something about the boards quality. Only good thing is that it was stable for a while..
ouch sorry to hear mate.. take photos and all of the damage - good to document everything before sending back for RMA :)
Corsair will take care of you if you need to RMA, 3 options for RMA listed at http://i4memory.com/f74/corsair-domi...ncement-18738/
Quote:
ORIGINAL: Corsair_Mike
For Dominator GT/Elpida Hyper IC customers with failed parts we offer the following 3 options.
1. A refund, original invoice required
2. A set of hand screened Dom GTs (Elpida Hyper ICs), with full warranty of course
3. Replacement with a 12GB 1600 kit: http://www.corsair.com/_datasheets/HX3X12G1600C9.pdf
PWM temp I'm really not sure about exactly, never measured it, but the cooler over that area wasn't all that hot - not cool, there was heat transfer, but not burning up either. Overclock was never more than 3.7 - see above, I could never get more than 185 BCLK to boot.
Just making sure here, for VTT/IMC/Mem stability checks I need to run Prime with FFTs ranging from 128 to 4096 with in-place unchecked and max memory right? Or whats the best setting for this purpose?
Blend with mem maxed right?
Thanks guys. Btw, Razer I think I'm on to something. Running 12GB was as easy as slapping the additional 6GB in and just run them. I think most of my problems came from the fact that asking for LinX stability at 89°C was just a tad too much. Even in a warm room (sry have no thermometre around) I'm not going over 70°C now at 1.32 vcore. You just have to love water cooling, 50 LinX passes max mem easy even at 7-7-7-24-1N. I'm posting some screenies when I confirmed prime stability. :)
TRUE has met it's end for people that have no air conditioning around in the summer for benching or stability testing me thinks.
Try around with that setting, for me it also had an impact on stability as I discussed that with Eva.. somewhere in this thread I think. Also PWM frequency setting and IOH volts. When you set a boot-up baseclock there's no jumping RTL anymore I think. But are your issues now gone with your new ram or not?
Edit: Found it. But maybe you've read that already.
the best bios? :confused:
What?! 0619 BIOS works flawlessly with my w3520...1.175v BIOS to pass 200x20 no problem. However with high uncore (4000Mhz) will need slightly higher vcore to compensate. 227 bclk with QPI enabled cold boot to windows without any problem, but 228 failed no matter what PCI-E I used I guess that's the bclk wall for my w3520 then, can't handle high QPI Frequency. With QPI Disabled 232 bclk cold boot is ok.
Well, here it is. Not really amazing voltages, but stable.
vcore load 1.32
IOH/ICH 1.19
RAM 1.65
VTT load 1.43
Boot-up bclk 185
DRAM PWM reduce 15%
(only listing changes, also 7-7-7-24-1N needed to be put in manually)
http://img18.imageshack.us/img18/3730/50linx200x21.png
http://img23.imageshack.us/img23/823...53200x2112.png
Wow! Really nice temps!
PS: My problem seems to be still here
Thanks! :)
My loop is like DDC3.2 xspc res top -> 2 PA120.3 with medium yates -> HK3.0 Cu -> mcw30, all with 3/4" Norprene. Apart from the temps this build was just so fun, but I already have things I'd do differently with the next build. :p:
If I have the time I would want to post some pics in the watercooling build thread.
What do you mean by "no go"? Does 16 & 19 require more voltage than for example 05/08? Just got a new board from RMA so I'm still testing. So far I've established that my previous stable vcore setting is not enough for 06/19. I've flashed back to 05/08 now to check if it improves.