Originally Posted by gsk3rd
Well the 4.0/2.0/1600 was stable for 3 hours so I moved on to 4.0/2.6/1600 and only core 1 was stable for 6 hours. 2, 3 and 4 all stopped. So I gave the nb and cpu volts a small bump. currently testing at email@example.comfirstname.lastname@example.org/1600.
Roughly 30 minutes in as I type this and all is well.
I typically match the cpu-nb volts with the nb volts. I think it was 1.3 or 1.28.
That's good. 1.5v sounds a little for 4.0Ghz. 1.2v Sounds a little on the weak side for 2600. 1.25v Might be a mroe stable a approach if you run into Issues. I try to match my NB and HT link Voltages. For some reason, when I'm having stability issues and those two are different (HT Link v usually is lower in that sitn.) whenI raise the Ht Link V to match the NB Chipset v, it stablizes... IDK. To each their own I guess.
Originally Posted by Chopxsticks
Hello again gentlemen, thought I would drop in and share some stuff,
So remember my Hyper transport flood sync error.... Well stopped using Win7 and went back to 64bit XP and have not seen a crash for about 2 weeks.
I think it was my 4850 drivers not working with Win7...
Glad that you found a resolution. I found that it was always caused from not enough voltage on mostly my CPU... Sometimes the CPU-NB though.
Nice work! What are you running at now?