Hmm...I decided to play with my FSB overclock to see where my limits were.
I had been running my 1.4 Tbird at 1.5 (10x150) just fine. I decided to lower the multiplier a bit and raise the FSB. When I got to 9.5x160 I got a BSOD before Win2K completed booting. No big deal...I'll just back off a bit and re-boot, right?
No. I rebooted and got into the bios but it kept locking up before I could back off to stable settings. I decide to power down and step away for a while.
I come back...power up and the monitor is no longer getting a signal. The system fans all spin and the drives spin but nothing on-screen.
Could I have killed my Geforce 3 with this FSB OC?? That would explain why the system previously froze on the bios screen.
I've got a GeForce 2 and an old TNT2 Ultra around here somewhere but my wife is gonna kill me if I fried my $350 GF3 (especially after killing my $170 Gigabyte GA-7VTX).
Is it possible for a FSB OC to kill my video card?
-Sili
I had been running my 1.4 Tbird at 1.5 (10x150) just fine. I decided to lower the multiplier a bit and raise the FSB. When I got to 9.5x160 I got a BSOD before Win2K completed booting. No big deal...I'll just back off a bit and re-boot, right?
No. I rebooted and got into the bios but it kept locking up before I could back off to stable settings. I decide to power down and step away for a while.
I come back...power up and the monitor is no longer getting a signal. The system fans all spin and the drives spin but nothing on-screen.
Could I have killed my Geforce 3 with this FSB OC?? That would explain why the system previously froze on the bios screen.
I've got a GeForce 2 and an old TNT2 Ultra around here somewhere but my wife is gonna kill me if I fried my $350 GF3 (especially after killing my $170 Gigabyte GA-7VTX).
Is it possible for a FSB OC to kill my video card?
-Sili
Comment