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

Error While Booting

Gumby16

Member
Here's an interesting problem I've never seen before. (Also, this is not my computer, so the hardware specs are fuzzy...I know it is a Windows 2k OS and there are 512MB of RAM. Sorry for the lame specs...that doesn't help diagnosing problems).

The computer was turned on normally, booted into Windows, began bringing up its programs in the task bar, and then rebooted itself. That's when the problems started.

When you turn the power on, it begins the POST process. After the RAM count, a message appears saying "WARNING! FSB/SDRAM FREQUENCY MAY HAVE BEEN CHANGED". It then does one of two things. Sometimes, it will attempt to find the primary/secondary drives, fail, and then just sit there. Other times, it will just sit after the warning.

The interesing part is, hitting DEL will not bring up the BIOS, and I have not found a successful way to get into the BIOS to see how the settings have been changed.

No new software has been installed in the past several months and no drivers have been updated. It is running McAfee Anti-Virus which has not reported any viruses before now.

If anyone can provide any information on where to go from here, or where to look for more information, I would appreciate it.
 
Well, we'll need a lot more info to really have an idea; if you can get the mobo type/model we can try to get the manual in PDF to see if there is a CMOS reset jumper on the board.
Setting that jumper should reset the BIOS and allow you to get in and load the default settings. If it's a pre-built (Dell, etc.,) get the model of the machine, the company's web-site might have the resources we need.

alzan
 
Yeah...it's a little sparse being that I'm trying to do this without really seeing the computer. The CMOS reset is a good answer and I'm sure that will fix the problem. I'm just irked I didnt' think of it sooner. It's always the first thing I do when weird stuff happens. Thanks!
 
As an option if you can't get the mobo manual or model #, removing power from the computer and then unplugging the CMOS battery for about five minutes should also reset the BIOS.

alzan
 
Back
Top