View Full Version : [SOLVED] overclocked 1333 crashes windows
Hey can anyone tell me how to fix this!!!???
I am using a abit kt7a raid motherboard 2 40gb ibm drives and my os is windows 2000. I have 640 mb ram. If I try to overclock at all windows locks solid. I've tried changing the voltage from1.75 all the way to 1.85 with the same results. I am new to this (as you've probably figured out) but I would like to overclock to at least 1466. thanks, Derek
TranceBear
06-29-01, 06:13 AM
Well it is harder to get those high voltages with a T-Birdie, anything over default WILL result in ultra high temps, BE PREPERED!! Lot's of awesome cooling will be nothing but good. I agree with him on the choice of heatsinks, I have tried the swifttech and the glaciator(just installed 20 minutes ago, we'll see), no opinions on the Glaciator, Swifttech not good for my system. I love the Vantech for cost (but noisy). What kind of cooling you have? This will help in giving advice.
Would71 (Jun 28, 2001 10:27 p.m.):
"..all the way to 1.85.."
I've tried to up the voltage beyond 1.85 and the system will not boot, No monitor no nothing. Any ideas? I am using a globalwin fop38 is that sufficient? Running in bios it will heat up to 125 F After awhile but never any hotter. Thanks for your response
Derek
Well, to be brutally honest, that's not a very long way to have gone. I'm running stable at 2.0v right now.. but when you start getting that high in voltage, better have some decent to serious cooling going on. If you have a good heat sink like a Glaciator or a Swiftech 462 or even a middle-of-the-road model like the better Global Win stuff, try upping your voltage to 1.9-2.0 and see if it's stable then at the target MHz range. Then if you can inch it down slowly, start taking it down from 2.0v until it becomes unstable again, then bump it back up to the last stable setting. Just remember, they put out a LOT of heat no matter what voltage. If you're not careful, you'll be the proud owner of one very (burn-) colored keychain. :D
I have 4 case fans in a full tower the system temp is about 84F.
If Iset the core voltage to 1.84 and the clock to 1466 it will boot but it will crash windows . When I reboot to bios thecpu temp will start at 114F and eventually get up to 125F but no higher. Is it usually necessary to run the core voltage higher than 1.85 for such a small gain in clock speed? Do I need to increase the i\o voltage or anything else? Finally, is heat usually the reason that a system wont boot when the voltage is increased? I'd just like to know before I blow a hole in my case and add another fan as it's already very loud with the 5 fans im using now. Thanks alot for your patience.
Derek
Would71 (Jun 29, 2001 05:29 p.m.):
But the "case temperature" at the motherboard's therm. can be quite different from the air around the HSF/CPU. You have to keep in mind airflow patterns inside the case and what not. If the layout of your case and fans creates a pocket of relatively "dead air" around the CPU, then your case temp. can be fine and the CPU will still run needlessly hot. Hence I recommend a "blowhole" intake fan near the CPU in most cases, to directly blow cooler outside air onto the HSF. My CPU actually seems to run cooler with the case covers on, since one of them has the blowhole fan, than with the covers off the sides. (I say "seems" because I'm not very trusting of my mobo sensors.. I'm pumping 2.0v into this chip and under full load it's showing 111 deg. F right now.. my Glaciator is good, but I don't think it's THAT good! *snicker*)
Are you doing the overclocking using Multiplier or FSB?
Try removing sound, SCSI Modem cards to see if that is causing the problem.
penguinfreak (Jun 30, 2001 09:42 a.m.):
Are you doing the overclocking using Multiplier or FSB?
Try removing sound, SCSI Modem cards to see if that is causing the problem.
I am overclocking by setting the multiplier to 11*133 which is 1466 . I am leaving the fsb at default. I've tried 10.5*133 and it still will hang in windows eventually. At 1333 though it runs fine. I'd just like to overclock successfully mainly to find out why it's hanging now, (although if I am successful I will run at the faster clock) thanks
Derek
vBulletin® v3.8.7, Copyright ©2000-2012, vBulletin Solutions, Inc.