• 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.

Windows vomits after OCing.

L

latresillustre

Member
I was overclocking a AMD64 3000+ Venice and everything was going great.

I've got value ram so I was trying to get close to 200mhz on it at a 133 divider. The processor easily booted up after going to 300HTTx9 and ran Memtest w/o errors. When Windows XP Home loaded however, things got crazy.

The screen flashed in an array of colors up and down so I turned off the computer because it freaked me out. I've heard of Windows being corrupted from OCing, but I don't really know anything about it. I just booted up the computer at 277HTTx9 and Windows loaded perfectly fine.

Can anyone explain to me what just happened to me?
 
Your 300x9 OC was probably a bit too much, so the system was unstable. Just because memtest passed doesnt' mean the rest of the components were stable at that speed..
 
memtest tests the memory, though if the cpu is very unstable you might see errors in memtest, use the overclocking guide that is stickied, go gradually and find the point where you can no longer boot into windows successfully, either then raise the vcore (keeping it below 1.55) or start testing with prime95 to see if the cpu is stable

my bad, it no longer seems to be stickied

but the gist of this was, after dropping ldt to 3x and having the memory on a multiplier that keeps it below 200, just keep raising the htt in 5mhz increments until you can no longer boot into windows
 
Try increasing voltage to 1.6 and bumping LDT to 3. This should help. If it doesn't, then your processor can't handle it.
 
Suspect you will achieve maximum stability around 270 to 280MHz FSB with 5:6 memory divider. Limit the RAM voltage to 2.7V with stock timing. Vcore should not exceed 1.575V MAX. Use LDT 3x.
 
Originally posted by: coomar
memtest tests the memory, though if the cpu is very unstable you might see errors in memtest, use the overclocking guide that is stickied, go gradually and find the point where you can no longer boot into windows successfully, either then raise the vcore (keeping it below 1.55) or start testing with prime95 to see if the cpu is stable
Click to expand...

1.55+ is not safe for Venice? Mine needs 1.6v for 2.7ghz stable in Prime. I run Cool N' Quiet though, so must of the time it's at 1.3v.
 
winchesters were fine with 1.6, venices seem to be more sensitive to voltage, people will argue between 1.55 and 1.6 for the stock cooler, as long as your temps aren't outrageous its fine
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top