New build, doesn't post, no beeps

[LABachlr]

I just want to confirm my diagnosis. The system that I just built isn't posting.

Biostar M7VIG 400
AMD Sempron 2400+
Crucial 512MB DDR333
WD 80GB 7200RPM 8MB

I tried changing the frequency jumper (even though I know that it was the correct setting (just built a system with the same mobo with an AMD Semptron 2200+ with no problems). The funny thing is, when I changed the frequency jumper settings so that all frequencies would be open (100/133/166), it started up for 2 seconds and then shut down (started up meaning the fans started to spin; nothing else). When that same setting (which is the default out-of-the-box setting) was used with the first build, it just read it as 900MHz instead of its real speed of 1.5GHz.

Another thing that was weird was that when I booted it up with no RAM, there were no beeps. Actually there have not been any beeps yet with this system.

Do all mobos beep nowadays? Even this one? If no beeps, is it 100% a dead mobo?

Now I have the mobo outside of the case with just the CPU (+HSF) and RAM. Video is onboard. And it won't post now either. Took out the RAM again, still no beeps.

When do you know you have a bad CPU? Is it really rare to get a CPU DOA? What would be the symptoms?

In any case, I'm going to say a DOA mobo. Confirm?

 

[otispunkmeyer]

no beeps could also mean u plugged the speaker cable in wrong....if u even have one! i know my p160 doesn have a case speaker (mobos dont actually have the speaker onthem) good thing i have the ASUS post voice thing

 

[otispunkmeyer]

erm trying to boot with ZERO RAM is a no no.....it simply will not work at all, when u first turn on the one of the first things the mobo checks is the ram installed.....put ram in it u nugget.

 

[otispunkmeyer]

put the jumpers back where u found them, clear cmos an then tell us what its doin

 

[LABachlr]

The point of booting it with no RAM is to see if the mobo would give the error beeps that it usually gives when there is no RAM. It didn't, which adds to my suspicion that this puppy is DOA. Just wanted a confirmation.

 

[otispunkmeyer]

does it have error LEDS or something?......my other computer doesnt beep, but its got a bracket that goes in the pci spaces at the back with 4 leds on, the combinations of green an red leds help u sort things out

 

[LABachlr]

No LED"s.

http://www.biostar-usa.com/mbd...ls.asp?model=m7vig+400

 

[otispunkmeyer]

ok....well (assuming uve not done this) put the jumpers back where they were to start with, clear the CMOS with a jumper on thr mobo (in the manual) and take the mobo battery out for abit, put it all back in, put the cmos jumper back then try it.......if u get nothing then u got more reason to believe the board is toast

oh oh what PSU u got in there? brand?.....try starting up with minimal components

 

[LABachlr]

I just got it to post by clearing the CMOS and putting the jumper settings back to default like you said! Amazing! Thanks!

I have no idea why it was not posting before. Did I mess up the CMOS by changing the jumper setting? That should not have affected it. I did the same with the other build. However, I changed the jumper after I had booted it up, installed Windows, etc. But I've changed the jumper before I start the build on Biostar mobo's, and it didn't affect it at all. Weird.

Will now put board back into case and see what happens. Maybe I will just set it to the correct setting via the BIOS instead of the jumper. Right now it is reading the Sempron 2400+ (1.667GHz) as 1000MHz.

 

[otispunkmeyer]

glad i could help.......no probs

id get everything sorted first, then see if u can get it running the stock setting by doin it in the bios...if not then do the jumper thing.

in the bios i would make sure the FSB (an the ram speed ) is set to 166mhz (ddr333) and then make sure the CPU multiplier is set to 10 this will give u the 1.667Ghz u should have

im off to bed soon so any probs jus repost or PM me

 

[LABachlr]

Cool. Thanks. Should I attempt to OC this a little to make it at least 1.8GHz, if not 2.0GHz, or is it not worth it with this board? It came with software to OC it called warpspeed or warp something.

 

[otispunkmeyer]

welll once u get things goin stock......and i suggest running PRIME95 Blend test overnight to check everything.........if its all stable (ie still blending when u get up) then try for the overclock

i would of bought DDR400 personally as its near enough the same price and gives u head room to O/C, but u should be able to push upto 200mhz from 166.

adjustin mulitpliers is the best bet as u dont have to run the ram out of spec. but i have no idea what AMD have done with multipliers on them chips. i know on A64 that they are locked, yet they are unlocked on the FX xhips and on mobile athlons.

i mean if the mulitpliers can be cahnged then all u need do is go up to x11 from x10 to get 1.8ghz, or u could try must 180mhz out of the ram. tho if u oc the FSB, then u are aware that u are overclocking the chipset, HDD, PCi and AGP?

hopefully u got some decent cooling....if u wanna oc

 

[LABachlr]

OK. Thanks for the info. Will try that test. Just have the HS&F that came with the retail version of the AMD chip. Would that be enough for just bringing up the speed to 1.8 via the multiplier? If not, no biggy. I just won't OC.

 

[otispunkmeyer]

may be last time i used an amd cooler it was a shabby peice of crab made totally of aluminium.....tho now i think they have copper cores and some actually very good thermal material.....i think a moddest bump to 1.8ghz wouldnt be a problem at all. jus keep one eye on ur temperaturs when u do

if u have to overclock by fsb, (well if u over clock at all) run prime95 again, theres no point in a overclock if its not stable.

anyway glad i could help and save u some time. its past midnight here now so im off to bed, Private message me if u want any more help.

-Otis

 

[LABachlr]

For some reason, in the BIOS, it is saying that the CPU clock can only go up to 132, even though it is jumpered so that all three frequencies are open: 100, 133, & 166. What's the deal?

 

[otispunkmeyer]

? that is strange.........id try updating to the latest bios, semprons are new and u may need the latest bios in order to support them

 

[otispunkmeyer]

hopefullly biostar provide an nice easy way of flashing the bios, in windows or something...again the manual is ur friend

 

[LABachlr]

Set it back to 100, and it's working. Will try changing the frequency once I have WinXP installed. Have never had to wait until the OS was installed before, but whatever. We'll see.

 

[otispunkmeyer]

ok i have checked out ur mobo on the website....now semprons are new cpus from AMD, but basically the socket A semprons are based off the K7 core, i think they are codenamed "thorton". now if u look at the latest bios here u will see the latest bios fixes this problem with the Thorton CPU's

the bios fixes...... Fixed the problem where CPU speed is not properly identified with Thorton processors. Without Biostar splash screen.

so maybe u should try this

 

[LABachlr]

OK. Thanks. Didn't have to update the bios of the other mobo that is the same exact make and model, and that I got at the same store. But, it's definitely worth a try. Thanks.

 

[otispunkmeyer]

doesnt mean to say they shipped from the manufacturer at the same time

this bios update sound like ur ticket....anyway let me know how u get on

nite

-Otis

 

[LABachlr]

Very cool. Thanks. Will do.

 

[LABachlr]

Originally posted by: otispunkmeyer
doesnt mean to say they shipped from the manufacturer at the same time

this bios update sound like ur ticket....anyway let me know how u get on

nite

-Otis

LOL. Yeah, that's what I figured. Most likely that is the cure, and that is the root of all of the problems I have been having. Thanks again! Will post results, which I'm sure will be successful.

 

[LABachlr]

Looks like it is now hanging at 2% while formatting the C partition into NTFS.

Everything on this system is brand new.

 

[LABachlr]

I know that Otis is out for the night, but just posting in case anyone else is up. Just in case it was an error on part of the HD, I did a low level format with killdisk. Then, threw in the WinXP CD to partition the HD and install WinXP. Well, it is doing the same thing, except now it is hanging at 0% during the formatting of the C partition (NTFS).

Anyone have any ideas?