Jump to content

Recommended Posts

Posted

Could someone help me please?

Today I bought a new EPOX 8RDA3G motherboard to go with a AMD ATHLON XP 3200+ Processor but I cant get it to work. After it trys to start windows it just gives me that horrible blue sreen.

I know the mobo is supposed to be set at 200MHz but all I can get is 133MHz

Any help please?


Posted
I know the mobo is supposed to be set at 200MHz but all I can get is 133MHz

That's because your processor's FSB (Front Side Bus) is 266MHz, raising it on the motherboard to 200MHz will shoot up the FSB on the processor to 400MHz, value unsupported by the CPU. So I'd leave it to 133 on the mobo. As for the BSOD, as ripken said, please give us the error code.

Posted

I havent seen the blue screen in a while now because I was told to do a fresh instalation of windows cause apparently XP does not like new motherboards. So im doing that now.

Posted
I havent seen the blue screen in a while now because I was told to do a fresh instalation of windows cause apparently XP does not like new motherboards. So im doing that now.

Haha, you never said you used an already installed windows. Now that you will freshly install it, I don't see you getting that "horrible blue screen" anymore :lol:

Posted (edited)

well u can fix that but it is not worth it

u can boot in safe mode and uninstall all drivers from previous mobo......

Edited by boooggy
Posted

I think its all fixed,,,, I hope anyway

My Cuz said it could be faulty ram so I tested and tried different modules and seems to be working now. thanks for the help.

Lets hope it still keeps going>!!!!!!!!!!!

Posted (edited)

A new PC, then it's likely a buggy BIOS or insufficient power supply. You may be required to set the Vcore and/or VDIMM manually!

But, also, if you have a socket A Epox, then it's likely because of bad caps!

Edited by RJARRRPCGP
Posted
A new PC, then it's likely a buggy BIOS or insufficient power supply. You may be required to set the Vcore and/or VDIMM manually!

But, also, if you have a socket A Epox, then it's likely because of bad caps!

Would`nt have a clue how to do that :blushing:

Anyway I upgraded the BIOS, Seems OK now thanks.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...