At this point you should find the failure points of your mobo and RAM. Bump your multiple down to keep the CPU speed at 3.0 or less, and keep raising FSB till failure. Use the lowest RAM multiple you have available. You have 1066, so you should have plenty of headroom for FSB.
If your FSB is choking, you'll need to start tweaking BIOS settings and finding what makes it more stable. Then you can go back to overclocking the CPU.
The only catch here is that even though your RAM is rated for 1066, it may be failing at lower speeds because it doesn't play nice with your NB etc. If tweaking board settings isn't helping FSB max, you may want to look at more VDIMM or loosening your RAM timings.
What are you at for FSB and RAM right now?
Originally Posted by consume
Just thought i'd report back and say i got 3.4ghz stable ^_^. Turns out, my ram was partially the culprit. With both ram sticks in, i'd bsod prime in about 2 lines of the small ffts test. I pulled one out, and it ran for 2 hours before i stopped it. Also, i couldn't boot into windows @ 3.6ghz even with up to 1.5 vcore. With one ram stick in, i could boot at 1.4v. It still failed prime95 within 10 minutes but still, i'm getting somewhere now.
Although, all the BSODs i get from prime are the same, 0x124. I've searched this for quite a while and it points to either a cpu error, low vcore and low vtt. I set fsb to 1.5 (max is 1.5) vcore to 1.5 and the nb to 1.4, still bsod instantly after starting prime. Maybe the cpu just can't reach 3.5-3.6?
Or is it the board? My motherboard doesn't have options like CPU PLL and i can only do +-.10v on the northbridge and fsb.