Specialty Forums
Security and Virus
General Hardware
CPUs/Overclocking
Networking
Digital Photo/Video
Office Software
PC Gaming
Console Gaming
Programming
Database
Web Development
Digital Home

General Forums
Windows XP
Windows Vista
Windows 95/98
Windows Me
Windows NT
Windows 2000
Win Server 2008
Win Server 2003
Windows 3.1
Linux
PDAs
BeOS
Novell Netware
OpenVMS
Solaris
Disk Op. System
Unix
Mac
OS/2

Drivers
Driver Scan
Driver Forum

Software
Automatic Updates

BIOS Updates

My Computing.Net

Solution Center

Free IT eBook

Howtos

Site Search

Message Find

RSS Feeds

Install Guides

Data Recovery

About

Home
Reply to Message Icon Go to Main Page Icon

Monitor (?) problems after OCing

Original Message
Name: dean_brfc
Date: February 18, 2007 at 18:47:22 Pacific
Subject: Monitor (?) problems after OCing
OS: Windows XP Home
CPU/Ram: 512
Comment:
Hi,

I recently tried to overclock my Intel Celeron 2.4ghz via the BIOS settings. I initially did it to 2.6, which showed up fine in the System Information in Windows. I then proceeded to try 3ghz. When I saved and exited from the BIOS, the power cable was knocked out before the computer started to boot up.

Since then my monitor (and another spare) has failed to recognise anything is connected when the computer is turned on. I get the bleeping sound from the computer although the hard-disk activity light stays constantly on after a few seconds. The CD drive light flashes for a while too.

Does anyone have any ideas what may have happened or how I can get something back on my monitor screen? I'm quite desperate so help would be greatly appreciated.

Dean.


Report Offensive Message For Removal


Response Number 1
Name: dean_brfc
Date: February 18, 2007 at 18:49:19 Pacific
Subject: Monitor (?) problems after OCing
Reply: (edit)
Sorry I forgot to add: I 'THINK' the computer had shut down fully before the cable came out, I'm sure it was almost exactly in the gap between shutting down and restarting.

Report Offensive Follow Up For Removal

Response Number 2
Name: jam
Date: February 18, 2007 at 19:24:34 Pacific
Subject: Monitor (?) problems after OCing
Reply: (edit)
If you didn't lock the PCI/AGP at their defaults (33/66MHz) or don't have a BIOS option that allows you to lock them, you've raised the FSB too high & the PCI/AGP have gone too far out of spec. 112MHz is the safe max...

Report Offensive Follow Up For Removal

Response Number 3
Name: dean_brfc
Date: February 19, 2007 at 02:14:58 Pacific
Subject: Monitor (?) problems after OCing
Reply: (edit)
I didn't lock anything...although the default frequency was 133 (I changed to 150 then 166).

Is there any solution to this then? It doesn't sound promising. :(


Report Offensive Follow Up For Removal

Response Number 4
Name: jam
Date: February 19, 2007 at 06:22:25 Pacific
Subject: Monitor (?) problems after OCing
Reply: (edit)
I figured the default was 100MHz. Regardless, there are several BIOS settings that need to be addressed when overclocking, not just the CPU freq. There's the PCI/AGP bus, RAM freq, RAM timings, Spread Spectrum (which should always be disabled), CPU & RAM voltages, etc.

You haven't listed the make/model of your board or what speed RAM you're running, so it's difficult to give any suggestions.


Report Offensive Follow Up For Removal

Response Number 5
Name: dean_brfc
Date: February 19, 2007 at 08:00:47 Pacific
Subject: Monitor (?) problems after OCing
Reply: (edit)
Ah sorry, I should have mentioned that. It's an MSI motherboard, model number MS-6787 VER:2. I have two sticks of 256 RAM, one DDR400 and one DDR333, both are CL2.5. I don't know if this makes any difference, but both the graphics and sound are on-board.

Report Offensive Follow Up For Removal


Response Number 6
Name: dean_brfc
Date: February 20, 2007 at 09:46:48 Pacific
Subject: Monitor (?) problems after OCing
Reply: (edit)
Does anyone know if it's possible to get my computer working again? I can't really afford to take it to a repair shop.

This is my last hope to be honest.


Report Offensive Follow Up For Removal

Response Number 7
Name: jboy
Date: February 20, 2007 at 15:57:02 Pacific
Subject: Monitor (?) problems after OCing
Reply: (edit)
You can try clearing the CMOS and reset everything to default values - usually there's a motherboard jumper, but briefly removing the CMOS battery (while unplugged) should accomplish the same thing

I'm not one of those who think Bill Gates is the devil. I simply suspect that if Microsoft ever met up with the devil, it wouldn't need an interpreter.


Report Offensive Follow Up For Removal

Response Number 8
Name: dean_brfc
Date: February 21, 2007 at 05:21:38 Pacific
Subject: Monitor (?) problems after OCing
Reply: (edit)
Fantastic, I did it!

Thank you everyone for helping, I didn't actually think there was any chance of fixing it after reading horror stories about failed overclocking on the internet. There were indeed some reset jumpers in there, I wouldn't have had a clue had I not asked here though.

Thanks again people.


Report Offensive Follow Up For Removal

Response Number 9
Name: jboy
Date: February 21, 2007 at 21:21:44 Pacific
Subject: Monitor (?) problems after OCing
Reply: (edit)
That's good - sure, all you'd need to do in most cases would be to reset the CMOS values - those 'horror stories' are no doubt cases where the CPU was damaged.

Now you can start over...

I'm not one of those who think Bill Gates is the devil. I simply suspect that if Microsoft ever met up with the devil, it wouldn't need an interpreter.


Report Offensive Follow Up For Removal



Use following form to reply to current message:

   Name: From My Computing.Net Settings
 E-Mail: From My Computing.Net Settings

Subject: Monitor (?) problems after OCing

Comments:

 
  Homepage URL (*): 
Homepage Title (*): 
         Image URL: 
 


Data Recovery Software




DSHUB24 Connection Problems

need help with dsl and dial up

novel 3.12

help mandriva install last straw!

Icon Scaling in Explorer Bar


The information on Computing.Net is the opinions of its users. Such opinions may not be accurate and they are to be used at your own risk. Computing.Net cannot verify the validity of the statements made on this site. Computing.Net and Computing.Net, LLC hereby disclaim all responsibility and liability for the content of Computing.Net and its accuracy.
PLEASE READ THE FULL DISCLAIMER AND LEGAL TERMS BY CLICKING HERE

All content ©1996-2007 Computing.Net, LLC