• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Lamest 3200+ Winchester in existence?

Page 2 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
Originally posted by: Zebo
Ack have you tried my A64 quick and dirty OC guide? need to isolate I think.,.
Click to expand...

Yeah, I looked at it before I started my o/cing trek. Great guide! I also looked at your memory matrix thread, impressive info! Not to derail the thread, but other than sciencemark, have you looked at other types of ways to measure CPU/memory intensive scientific computational effect on bandwidth/latency?

I tried isolating by reducing everything to a level that I thought would be sufficient for a modest o/c. For example, the I put my memory to 166 with 3-5-5-8 2T and HT to 3X and would start overclocking from there.

BTW- is there any way to tell what's causing the error from your BSOD? I thought i was starting to notice a pattern of what seemed to be too far o/ced and what the BSOD message was, but I'm not sure...
 
Originally posted by: Ackbar
Bump for additional thoughts...
Click to expand...
An interesting experiment would be to try a different MB. Get a DFI NF4 Ultra-D and see what happens to your overclock. Assuming you may have done something wrong, that the rest of us can't figure out, the act of setting up your system with a new MB may help you avoid the subtle error you're making (assuming there is an error). If you have the same issue on a different MB, the evidence becomes even stronger that it's your CPU.
 
Originally posted by: shira
Originally posted by: Ackbar
Bump for additional thoughts...
Click to expand...
An interesting experiment would be to try a different MB. Get a DFI NF4 Ultra-D and see what happens to your overclock. Assuming you may have done something wrong, that the rest of us can't figure out, the act of setting up your system with a new MB may help you avoid the subtle error you're making (assuming there is an error). If you have the same issue on a different MB, the evidence becomes even stronger that it's your CPU.
Click to expand...

I'm thinking about buying a DFI NF4 Ultra-D, if I did it would be in a couple of months (so the prices can go down) and would only be for the sake of enhancing our knowledge... 😉
 
try downloading the new beta bios. It helps overclocking a lot. I have mine at 251MHz FSB right now. The bios is marked feb 3 or something. The 1T/2T setting now finally works, but i can't get it to prime95 at 1T at all, so i don't know if it's my memory or if it's a problem with the board. Still, the bios fixes a lot of crap, and overclocking is much better.
 
Originally posted by: gobucks
try downloading the new beta bios. It helps overclocking a lot. I have mine at 251MHz FSB right now. The bios is marked feb 3 or something. The 1T/2T setting now finally works, but i can't get it to prime95 at 1T at all, so i don't know if it's my memory or if it's a problem with the board. Still, the bios fixes a lot of crap, and overclocking is much better.
Click to expand...

I've tried all of the bioses. I'm currently using the beta bios that you're referring to. I haven't noticed any change in stability... =(
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top