Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

Annoying Motherboard Problem


  • Please log in to reply

#1
Admiral_Fuzzie

Admiral_Fuzzie

    New Member

  • Member
  • Pip
  • 9 posts
I apologize for this rather lengthy post, but I am having a problem with my new mobo, and I want to go into as much detail as possible with this.

I ordered an ABit KV7-V Mobo, along with an AMD Athlon XP 2700+ CPU and a DDR 400 (PC3200) 512 MB stick of RAM from NewEgg.com, and I just received everything yesterday.

I installed everything into my case immediately, and I hooked everything up properly, then I powered on the system. Everything started up fine with no problem at all, but then I noticed something rather odd when the BIOS/POST screen came up: The CPU was being detected as an AMD Athlon XP 1500+ and the memory clock as DDR 266.

I immediately went into CMOS setup. I went to see what the CPU FSB was set at, and this is what I saw:

FSB: 166 MHz
Ratio: 5:2:1
Multiplier: x13

I did notice though at the top of the screen that it still said that my CPU was an XP 1500+, and clearly, it wasn't. I then went and applied the Optimized Defaults, and saved to CMOS.

The system rebooted without any trouble, and when the BIOS/POST screen came up, I was glad to see that it was now detecting the CPU and memory with the proper specs. (the CPU as XP 2700+ and the memory as DDR 400).

I went back into CMOS setup to double check a few things. I checked to see if anything had changed with the CPU FSB, Ratio, etc. and it said the same thing as before:

FSB: 166 MHz
Ratio: 5:2:1
Multiplier: x13
(Out of fear that I would royally mess my system up, I did not dare change any of the above settings!)

I exited CMOS, rebooted, and I let the system boot into Win XP. Something strange happened though when I got into Win XP: This messagebox popped up with a strange error message. It said something like "The system failed unrecoverably in the registry" and if I remember, that same error message said something about an I/O error. So I clicked OK on the messagebox, and the system immediately rebooted.

I let the system boot into Win XP again, and this time, that error message did not appear, and my desktop loaded with no problems what so ever. Everything runs with great stability too. No crashes, no freezes. Nothing out of the ordinary. ;)

After about two hours of testing all of my games and apps, gawking at how much faster they run :) , I shut my system down. A little later, I came back and turned my system back on (what you might call a "cold boot"). The system failed to boot and I got an error beep code. It was a long, single beep, that repeated once every second or so. I recognized that beep code as some sort of problem with the video adapter. ;)

I did what I usually do with such a problem, and I pressed the reset switch on my case. The system then booted up absolutely fine with no problem, and Win XP booted fine as well. The system is still very stable as of right now. :)

The thing is though, whenever I do a cold boot on my system, It will fail to boot and I get that stupid beep code again :) ; all I have to do to is press the reset switch on my case and the system will then boot up and run absolutely fine. I DO want to fix this problem, so I don't have to do that every time I cold boot my system.

Does anyone have a solution to this annoying problem I'm having? I'd really appreciate it. :tazz:

System Specs
- ABit KV7-V Motherboard
- AMD Athlon XP 2700+ CPU
- 512 MB DDR 400 (PC3200) RAM
- 450 Watt PSU
- nVidia 128MB GeForce4 MX4000 Video Card
- Creative Sound Blaster Audigy Sound Card
- NETGEAR 10/100 MBps NIC
- Windows XP Home w/ SP2
  • 0

Advertisements


#2
Doby

Doby

    Member 2k

  • Member
  • PipPipPipPipPip
  • 2,075 posts
Hi,

I have a KV7 and used a couple others great board very stable and fast but troublesome to set up.

It sound like you got the setup close cause the cpu is recognized properly but the dram clock if set to "BY SPD" will run at 200mhz, try turning it down to 166mhz.

This will make the cpu and ram run in sync sometimes required with this board.

I could be wrong but the beep code you described sounds like a ram error code so make sure the ram is seated correctly.

What bios are you running? there are a couple other things but try these first and post back

Rick
  • 0

#3
Admiral_Fuzzie

Admiral_Fuzzie

    New Member

  • Topic Starter
  • Member
  • Pip
  • 9 posts
Okay, I have the DRAM clock set to BY SPD, and the FSB is set to 166 MHz.

I opened my case up, took the memory out, put it back in and made sure it was seated properly. When I turned my system back on, I still got the beeping, but pressing the reset switch once again fixed it, and the system started right up.

Here is my BIOS info:

KT600-8237-6A6LYA1HC-14
BIOS Version: 14
BIOS Date: 1/7/2005

Flash ROM Type: WINBOND 49V002 /5V
  • 0

#4
Doby

Doby

    Member 2k

  • Member
  • PipPipPipPipPip
  • 2,075 posts
No try setting the dram clock to 166mhz and leave the fsb at 166
  • 0

#5
Admiral_Fuzzie

Admiral_Fuzzie

    New Member

  • Topic Starter
  • Member
  • Pip
  • 9 posts
Okay, I set the DRAM clock to 166 MHz, shut the system down, and turned it back on 10 minutes later. The system booted right up without any error beeps. :tazz:

My memory is now being detected as DDR333 though. Is it okay to leave it like that, or is there more I need to do first?
  • 0

#6
Doby

Doby

    Member 2k

  • Member
  • PipPipPipPipPip
  • 2,075 posts
No that will be fine its just that you had to underclock the memory this is normal beause you are using a 333mhz cpu with 400mhz ram but now the ram is at 333 the same as the cpu. you won't notice any differance

goodluck Rick
  • 0

#7
Admiral_Fuzzie

Admiral_Fuzzie

    New Member

  • Topic Starter
  • Member
  • Pip
  • 9 posts
Alright then. Thanks for the help. :tazz:
  • 0

#8
Doby

Doby

    Member 2k

  • Member
  • PipPipPipPipPip
  • 2,075 posts
your welcome :tazz:
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP