No Post, No Video, D-Bracket Early Chipset Init. error, Worked before CPU Upgrd.

Zalman ZM400B-APS
MSI K8t Neo FSr2
AMD 3000+ 64 S.754
Corsair Twinx 2x512 PC3200 With Activity LED's.
ATI Radeon X800 XT Platium
6 Sata and 3 IDE Drives
Hello
Basically what I was trying to do was install a Clawhammer 3700+ with a Tuniq Tower 120 Heatsink. The system worked fine with the previous 3000+. After the installation the system powered on but there was no video (There is a slight blip when powered on though, indicating a connection.) and the ram LED's indicated that the system didn't enter post, or didn't post properly. The D-Bracket also hangs at the "Early Chipset Initialization" phase. I then removed the new processor/heatsink and put the 3000 back in but the boot failure still remained unchanged(No change in LED.). I made no other changes to the system other than the processor.
I should probably mention that I didn't clear CMOS before doing this because I didn't think it to be an issue. Also, several of the bios settings were changed from their defaults. Dynamic Overclocking was enabled at 5%, no other overclock settings were adjusted other than that.
I've looked on the internet for solutions and tried most of them but they haven't worked.
-Ram- Did the whole ram test thing, switched positions, tried just 1, etc. Ram worked before anyway. Also substited it with confirmed working lower quality ram so latency doesn't seem to be the issue. The LED's show activity for about 10 seconds, then it goes silent. This activity is completely different from the usual boot sequence. (LED's are great for diagnosing.)
-Video Card- Tried pulling it out and booting. No change.
-Power supply- Shouldn't be an issue, even though I have a lot of drives it still worked before. Did powering up with the new processor push it over the edge and did something permanent? I doubt it.
-Motherboard- My case is made entirely out of acrylic plastic. Screws are screwed into all spacers. Some of the spacers on one side didn't quite line up but I don't think they are off position enough to be touching anthing major. There appears to be what looks like a tiny ring of sodder joints around each spacer hole. The spacer may be touching this in a couple spots, would that be a problem?
-Processor- The 3700+ was bought off Ebay and I have no way of testing it here, however the 3000+ did work before, and that's what's installed now. Since the LED's show activity, Doesn't that indicate that both ram and processor are working?
One thing about the heatsink that I might should mention is that I screwed the bolts on pretty tight, mabye too tight. Perhaps the motherboard was damaged in some way. But still, LED's indicate that somethings working.
I'm not sure what to do at this point, any idea's would be appreciated. Keep in mind though that I have NO video, no keyboard control, no BIOS access, no control of any kind.
Thanks

Quote from: Hans on 10-November-06, 05:21:53
you say you cannot test the cpu, but that you did set the old cpu in another board -> that makes testing possible, or am I missing something?
I only have just that motherboard with no extra components to assemble a complete computer. Although I suppose I could take parts from the main one to do so. The more important issue is why the previous 3000 isn't working.
Quote from: Hans on 10-November-06, 05:21:53
Then: did you apply thermal greace in the right way?
Are you sure you install the cpu's like you should? (You probably are, just asking...)
Match the gold and black arrow, hold down cpu with light pressure while closing ZIF socket. I think so.
It was my first time using thermal grease but I think I got it right. Thin film evenly distributed, move heatsink slightly to eliminate air pockets.
Quote from: Tiresmoke on 10-November-06, 09:04:56
Try some other RAM.
I did. Some kind of generic 512 DDR confirmed working on a non-754 computer.
I didn't notice any apparant signs of damage on or near the ZIF socket. Would it be worth attempting to remove the backplate and check behind it? It'll be pretty inconvient to get to it, and probably even more so to get it off.
Quote from: XanaduServers on 10-November-06, 09:31:27
Test both processors in both boards.
Will do...

Similar Messages

Early Chipset Initialitation error after rebooting

I just bought a K8N SLI Platinum mobo and everything works fine but after rebooting the PC I got an "Early Chipset Initialization Error" .
The only way to shut down the computer is using the power supply switch .
If I turn on the power supply inmediatly, instead of going to standby mode the PC reboots and go back to the same error.
But if I leave it off for half an hour, then it boots fine an everything works OK !!!
Do you think that I am having a power supply issue ???
The main problem is that when the computer hangs or when I need to change the bios configuration I must wait a time before rebooting the system .
The power supply is rated at 500W but it is a generic brand . . . perhaps its real rating is 350W ??
January 3rd, 2006
Last news,
Yesterday I've tryed everythig I found in different forums :
1.- I disconnect all unnecesary devices (CDR - DVDRW - HDs - Fans , etc)
. . . nothing happens
2.- I remove one stick of memory (I was using 2x512 MB Kingston)
. . . nothing happens
3.- I check the BIOS for Sahdow RAM and disable that option
. . . nothing happens
4.- I replace the power supply by another that a friend of mine is using with the same mobo.
. . . nothing happens
But finally,
5.- I see that the small card that MSI use to select Single Video Card or Dual Video Card (SLI) is lose.
I tighten it in place using the plastic clamp and since then the system seems to work OK.
Should this be the cause of my headache ???
Someone suffer the same problem ???
John Bish

Perhaps we should get back on track and help out jrgbish .
Signature or not .
He already said he has a new "K8N SLI Platinum" running a noname 500w , that perhaps ony is real 350w and gets d-bracket error.
So it looks like a nwe build in process .
My first advice would be to get all power connections from PSU to mobo and gfx all wired up , disconnect
all but one HD and one optical , use plain ps2 mouse and keyboard without any kvm's ,
use one memory stick in dimm slot1 and se if it posts .
If it doesn't get hold of and try with a known good PSU with higher ratings on +12v line .

K8T Neo-FIS2R early chipset init. hang-up; won`t POST

I`m new to forums (participating anyway) and also new to self-builds; this is my first so please be gentle with me! but am very impressed with the help you people give each other, and that is what I seem to need. I have studied this forum extensively and so am aware of the PSU/RAM pattern of problems associated with this board - am I in the same boat?
Having connected everything up I switched on and the D-bracket is giving me 3 red lights and 1 green(top left; position 1) indicating `early chipset initialization`. The monitor remains totally blank (tested on my ancient wind-up PC and works great), and there are no beeps to be heard, but all fans work and LEDs too, and the drives can be heard and seen to power up. The manual for the board lists the diagnostics for the D-bracket in what appears to be a sequential order, so it seems that I have passed the 4 red lights problem that so many of you are having/have faced. Can I assume(dangerous word that) that my CPU is properly loaded and functional as the manual suggests (if indeed the D-bracket diagnostics are carried out in this sequential manner)?
I have tried to run the board with just CPU 4-pin(JPW1)supply, heat sink fan(CFAN1)supply, 20-pin board supply, graphics card slotted in and powered up, D-bracket connected and power switch(case) connected, with all combinations of just 1 or both sticks of RAM, in all computations of DR DIMMS 1-3, and get the same hang up at the D-bracket. I cleared CMOS before trying the above as well.
Do I need to do anything to the Maxtor drives at this early stage - they came with no instructions or anything? The board is clear of the metal chassis, held aloft by the 9 clips supplied (no plastic washers supplied though? but the metal eyelets are clear of any routing on the board so I assume(that word again) that washers are no longer necessary/supplied). While working on the board I was earthed to the radiator behind me, and I did not touch the surface at all. The PSU specs seem to be within the parameters that you indicate are necessary, and the brand seems to be respectable. The OCZ RAM seems to also be of the necessary standard and type, although I don`t see the exact same RAM anywhere on this forum, unless it is just described as OCZ PC3200 256MB EL, which I have seen several times.
So over to you folks - sorry for the length of this thread, but how else can I tell you what I`ve done!!. Any advice would be greatly appreciated. I want to get this board running;it sounds like once these initial problems are (hopefully) addressed, it is a super bit of kit, so I ain`t giving up without a fight - I think I`ve tried everything mentioned in earlier threads that may resolve this, other than start on the `buy a different PSU/RAM ` road!

Officially - as I've just researched the AMD website, here's what AMD has to say about RAM:
MEMORY SUPPORTED
PC1600, PC2100, PC2700 & PC3200 unbuffered memory modules
184-pin 2.5 volt
I've heard of others running PC3500 and higher, but question the effectiveness of running these modules. As earlier posts by Jocko indicate, running some inexpensive PC3200 sticks seem to have no problems with early chipset initialization. HOWEVER - just yesterday I went to a local retailer to check on 1gig modules, and the prices have jumped $20 or more per memory stick. I then went to NewEgg and checked on their prices and found that memory I paid $88 for is now $108 per stick

Early Chipset Initialization error: One solution

I too was plauged with a non-booting K8T_Neo board that stuck on "Early Chipset Initialization" according to the lights. I knew my Thermaltake 480w PS wasn't it - and sure enough it was the RAM like others have said. I was trying Corsair XMS Extreme Memory Speed Series, (Twin Pack) 184 Pin 1GB(512MBx2) DDR PC-4000 - Retail. So today I picked up some Crucial PC3200 256mb sticks and bingo I'm in.
Later today I'll fiddle with the timings to see if I can get the Corsair to fire and let you know what happens. Buyer beware!

Quote
Originally posted by JLP
I just set up some AMD Athlon 64 3000+ system on MSI K8T Neo-FIS2R and also have this system. I have 512 MB of TwinMOS Twister PC3200 CL2 ram. Does anyone else have a problem with this configuration? Or maybe doesn't have problems with it? Please help...
I had the same problem, and the reason was the ram. Twinmos twister does just not work, im sorry.
I have been very sucsessful with the Corsair XMS pro cl2 by the way.

MSI 990fxa-6d65v2 No Post, No Video, No Beeps, and verified everything DOES work

Well basically i will start with this i bought this for my brother as a Christmas gift and it still isn't working 2 god damn months later. I was reading this post (http://) forum-en.msi.com/index.php?topic=165453.0
and it sounded very similar to my problem except about 1000000000000000000 times less complicated due to everything i have tried since this has been an ongoing problem, and i basically just gave my brother a crushed dream for Christmas i would like to get it fixed. Plus his B-day just passed yesterday and all i had to give him for that was disappointment, words cant begin to describe the anger, frustration, depression, and sadness this has caused me. And to eliminate well pretty much EVERY question you could have, because i am 99.9999999% sure i have tried every single possibility, i will refer you to the other forum i have it posted in ( i just think you guys can help me more). Since the bios did jack , i think it might be what someone was saying like the vbios or something anyways here it is, in all its glory (make sure your sitting for all this)
PLEASE READ THROUGH IT THOROUGHLY...
(www.)tomshardware.com/forum/383169-31-post-video-beeps-verified-work

OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO
MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FFFFFFFFFFFFFFFFFFFFFFFFF
GGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGG GGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGG GG
IT WORKED!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
i don't care how gay this makes me sound i could seriously make love to you right now dude. I haven't been this elated in a very very very very very very very very very long time. I JUST CANT BELIEVE SOMETHING FINALLY WORKED !!!!!!!
Please understand my excitement:
i spent almost $1500 on this build
i'm in college so i dont really have a lot of spare money
i got it for my brother for christmas
i bought parts i KNEW were compatible yet all i gave him was disappointment
i tried LITERALLY every single suggestion i could find ANYWHERE online
despite what i tried (even though it worked for others) nothing could fix it
i tested each and EVERY hardware component individually and verified they worked
even though the CPU, GPU, MOBO, RAM, HDD all tested fine when put together... nothing
Two months roll by and my brothers god damn Birthday arrives and the only gift i have for him is broken hopes
I (only for a slight second) thought that the psu might actually be the problem
So i even (mainly to satisfy the idiotically overwhelming amount of ppl who claimed it was this) bought another brand new PSU, since almost everyone was SOOOOO sure that the problem was the PSU....
after spending another $120 on a really nice PSU it turned out that, gosh it wasn't the PSU
After calling MSI and explaining this all to them, they said "Wow, that a lot of stuff, it sounds like the only thing left to try would be to update the bios, because from what you have told me, it sounds like you have eliminated everything else."
So i download the newest bios AVAILABLE ON THEIR SITE, and update it, and then in a turn of
events not shocking in anyway at all and totally expected, it did jack .
Even though MSI claimed that they actually "tested" the 7950 on that board and it worked, they even said that
it should work right out of the box..... oh really is that so.........
Throughout the entire time (and i do mean EVERYDAY) since pretty much christmas i have been on the internet trying to find answers or ppl who have had similar problems. I took what gigabyte said into deep consideration
"How could they have added support for that card, if the GPU was manufactured at a latter date than that of the
motherboard."
Well i figured that the latest bios, being that it was the only one they offered on their website would fix that....
After the suggestion of the beta bios by "flobelix" i had about a 99.9% assurance that it wouldnt work, i mean after everything this what reason was there to have any hope. I was going to (if it didn't work) call MSI and tell them i am sending back the gd65 and i want to exchange it for the gd80, because regardless of what they say about the card and its compatibility, OBVIOUSLY there is some sort of problem.
HOWEVER, IT DID WORK AND I AM FREAKING OUT WITH JUST OVERWHELMING JOY!!
it feels really good more than anything to do this for my brother
With all that, i think it is bullshit that i had to use a beta bios, to put it more bluntly an experimental bios to get the card to work. Clearly the 7950 worked on MSI mobo when they tested it because it prolly had the latest beta bios....
How the hell are all the people that buy the board suppose to get the beta bios, i mean you dont have it on your website, is everyone that buys a new GPU suppose to just go through two agonizing months of frustration and depression before they get an answer?
MSI needs to address this issue asap, at the very least they need to offer the beta bios on their website. I have been buying from MSI for almost 10 years and i have always been happy but this situation really pissed me off. I am not going to stop buying from them because i think they are a really good company but, they need to stay on top of like this A LOT better.
Therefore to conclude this all, i am extremely happy to have this finally resolved, i cannot thank you guys enough i really cant.

Was watching a video I downloaded earlier today, and it worked fine. Tried watching it now and it stops about half way through. Solutions to this issue?

This happened just today with the only two videos I downloaded from iTunes. They seemed to stop working after I synced my itouch, but I don't know how that would have caused the problem... Both videos will play about 2 minutes on the itouch, then stop.

In case you do not know, to redownload videos you have to contact iTunes.
How to report an issue with Your iTunes Store purchase

Video encoding failed, audio encoding successful, both worked before

I have an .AVI that was provided by a studio. I used this .AVI in the past (February-ish) to create a .FLV using Media Encoder with no issues. I have to add a section to the original .AVI now. When i import the video to the new project, the preview monitor does not show video, but the audio can be heard. When trying to export as an .FLV it errors out and just says "Encoding Failed: Unknown Error".
I can export the audio fine, but the video causes the error (when separated). Thinking it was a corrupt file, I obtained original copies from the studio and tried again with no success.
Premiere Pro CS4 V4.1
Windows Vista x32 w/ SP2
Centrino T9300, 3GB RAM, 160GB HD
Any and all help is greatly appreciated.

Video:
     Codec: dvsd
     Name: DVC/DV Video - MPG2
     Stats: Installed
Audio:
     Codec: PCM Audio
     Info: 48000Hz 768 kb/s (1 chnl)
If i've recorded the wrong information let me know and i'll change it.

Having issues playing videos texted to me. They always worked before.

I was always able to play videos texted to be, but for some reason all I get now is "This movie could not be played". It will not play even when sent from another Iphone. Anyone have any ideas?

Right-click on your main iTunes folder and click Properties, then go to the Security tab and click Advanced. If necessary grant your account and system full control to this folder, subfolders and files, then tick the option to replace permissions on child objects which will repair permissions throughout the library. This is the XP dialog but Windows 7 shouldn't be too different.
tt2

Another "Early Chipset Initialization"

Problem: doesnt post
MSI Kt8 Neo
Athlon64 3000+
512 Kingston valueram
600watt hercules ps
Radeon 9500 np
Audigy 1 sound
120gb WD (8mb cache 7200rpm)
LG combo drive
I have read through most of the forum concerning computers that will not post and read "early chipset initialization". So before people start asking me the basics
The 12v rail (4 pin) was plugged in
Its not the PSU (probably) because i tried 2:
- One brand new 600 watt hercules (pos i know) 12v: 20A 3.3: 40A 5: 40A
- One older but working powmax (also not too great) 400w 12v: 25A 3.3v: 30A 5v:28A
also, i used a multimeter to check voltage and the 600 watt ran .25-.3 low on the 12 v readout. the 400 watt didnt
I have tried 3 separate sticks of ram
-1 pc2100 (specom)
-1 pc2700 (i dunno, pc toys? heatspreader in way)
-1 pc3200 (kingston value)
all 512mb
I made sure nothing is grounded as in nothing is touching the case
I have tried 3 different video cards
Processor is brand spankin new. No pins bent. Installed perfectly
I have left the battery out for 6 hours+ and used the jbat1 jumpers to reset cmos
I have tried it barebones and with everything
Here is the catch
It works sometimes! If i let it cool for like an hour, and then mess with it, SOMETIMES it boots, and i got into bios once. Then it made a sound and turned off and went back to hang at early chipset initialization. It seems like the chipset gets too hot too fast, like warm to touch after a few minutes of being on. I dont have experience with msi boards nor with athlon 64s sooo.... i dunno. When it actually runs it says "bios settings error" or "faulty".
Heres where i may have screwed it up bad:
When i was putting the board together for the first time i powered it up. I noticed the cd rom wasnt plugged in. So i plugged it in, backwards, and teh pins happened to touch and it shut off. That was the first time i had it plugged in so it may have been messed up to start.
My question is, is the board screwed?
If so, what board would you recommend? (i dont need sata, or raid, or onboard video. I like gigabit ethernet and OCing)

Just went out and bought a new psu, because the 600 watt wont cut it. I got a quality one Antec 400 watt. I also bought some generic hynix ram because its listed as working, HY5DU56822BT-D43 (it has a B instead of an A though...crap) I unplugged the jumper from the hard drive and removed the audigy 1 card. I had left the battery out all day and so i put it back in. I also disconnected the d-bracket entirely. Booted it up
Same problem...nothing comes up on the screen. No beeps. No monitor signal at all because the LED is yellow. Everything sounds right, but nothing is. (all fans spinning, all drives spinning, exactly like when i have GRRR on d-bracket (early chipset...)
To answer your question, if i remember clearly, i got into bios once, this is after i did the backwards plug thing.. and i was just about to press a button when i heard a kind of zap sound...or buzz. And it froze there. Seems to me like problem with agp but i dont know. The screen went black and then came on again to the main bios menu but my computer was frozen.
Also, when i boot it up, and hit escape twice to get past the logo, and then reset, goes beep beep pause beep. When i boot it up with no ram of course..beep pause beep pause etc.... and with no videocard, nothing.
The few times it did work were after i left it, whether or not resetting the cmos made any difference i dunno. And then i would remove both ram and vid card. Then turn on. beeps. Then put ram in. Then turn on. beeps. THen put videocard in. Then it would boot and tell me i have bad bios.
Thanks for the help. Any creative suggestions would be welcome.

K7n420 pro early chipset intialization

I am getting early chipset intialization error message and computer fails to boot up, it was working fine before. It happened once before when it was installed but I can't remember what msi told me to correct it. any idea's?

gaspasser,
That is the classic example of RAM that is not compatible with nForce. (Just because it worked once does not mean it will work all the time. If the advice given above does not work, try changing your RAM.)
I always use Mushkin High Performance RAM with nForce without any problems.
256MB Hi Perf Level II PC2100 222 Black
256MB Hi Perf Level II PC2700 222 Black
Take Care,
Richard

No boot -- Early chipset initialization

Just built my new computer and it booted first time without issue. Was able to installed Windows XP on it. Shut it down to leave and then came back to fire it up again and it's dead. No video, no beeps, no nothing. The D-Bracket is sitting with LED1 green and the others red. I read that as early chipset initialization. Searching here let me to believe that quite a few other people have had this problem but the resolution(s) are not simple.
I've reset the BIOS but that hasn't resolved the issue. I've disconnected all unnecessary fans, etc but no help. I've also tried pulling one of the DIMMs and disconnecting the cdrom drives from power and IDE.
Any ideas about what's next before I RMA? I don't want to miss something simple but it's been 6 years since I built a system and I could easily miss something.
MSI 865G NEO2-PLS
Intel P4/2.8E GHz 800MHz FSB 1mb L2 cache Prescott core
Cooler Master Aero 4 socket 478 CPU cooler
Corsair 512MBx2 DDR400 CAS2.5
Vantec Iceberg DDR Copper headspreader
Antec case with Antec 300 watt power supply
cooling fans added front and back of case
200gb Maxtor HD Ultra ATA/133
Mad Dog 56x CDROM
Hi-Val CD-ReWritable drive
Using the integrated video on the motherboard -- for now
Thanks,
Mike

Sorry about my rant on the previous post. Third computer I've built and the first one that's had serious problems. Maybe I should be happy that I've not had any problems with the first two and just take this one in stride.
Per specs, the 400watt PSU that I tried yesterday is:
+3.3v - 28A
+5v - 38A
+12v - 18A
The 300 that came in the case is:
+3.3v - 20A
+5v - 30A
+12v - 15A
I don't know how to test the actual output from the PSU's and lack a multitester to find out.
I have an online support request into MSI. I also have an RMA from Newegg.com, where I got the MB and CPU from. I'm not sure where the problem is so the RMA is for both. I've checked with friends and am unable to come up with a setup to test the MB and CPU independently.
Not sure what to do next other than to RMA the stuff back. Was unaware of the higher power requirement for Prescott. But should 300watts be sufficient for the MB, CPU, RAM, and single Maxtor 200gb harddrive after stripping out everything else? If not the 300watt then certainly the 400watt PSU...
Anything I'm missing?

Early Chipset Initialization Problem

Hello all,
After reading around this board I havn't found a very good answer for the Early Chipset Initialization problem. (which is the code that D-bracket gives me) Everything is entirely new, Including the new PSU that I bought to try to fix the problem. Any ideas? I know it's not the PSU so don't try telling me that.
The funny thing about this problem...the computer locks up and gives me the Neo Platinum screen, gives one beep to say the POST finished, and then locks up and I can't use the keyboard or get into the BIOS. Oddly enough, if I hit the reset button it boots up just fine. I'm thinking perhaps a faultly reset switch but has anybody else had this problem?

Quote
Originally posted by naedaneth
Hello all,
The funny thing about this problem...the computer locks up and gives me the Neo Platinum screen, gives one beep to say the POST finished, and then locks up and I can't use the keyboard or get into the BIOS. Oddly enough, if I hit the reset button it boots up just fine. I'm thinking perhaps a faultly reset switch but has anybody else had this problem?
Yeah try using a USB keyboard instead if you are using a PS2 keyboard..

Early chipset initialization

What does it mean when the D-bracket hangs there?
G R
R R
Early chipset initialization, so what does it mean if it hangs there and won't boot? X(

Thanks guy's it was ram.
One stick went bad. Now I'm the dumbo, I really should have known to check it.
Beaverpants, Wonkanoby, you guy's are getting pretty good. Also the video card reseating was good to but that, I already did. You know the board went out so fast I was looking for the D-bracket to show a code relating to the memory and when it showed the early chipset initialization i just jumped to the wrong conclusion. :O
Thanks again.
Jim

Early Chipset Initialization (failure) Help!

Specs finally in the Siggy.
Just installed a new HD, just got WinXP (and no other drivers loaded) installed and running. In the Bios I thought I'd take earlier advice and turned on Manual OC, only upped the Memory to its designed 200Mhz, and CAS 2.0
Saved, Reboot. Now I only get "Early Chipset Initialization " as reported by the D Bracket. I've tried clearing the CMOS, have pulled the battery, same thing.
Any ideas or is the board dead? The floppy is currently not funtional, I could get one tomorrow I suppose if you think the Bios Recovery may work per www.msicomputer.com/support/sup_tshoot.asp#1_2
Quote
Try BIOS recovery for AMI or Award BIOS
AMI BIOS recovery procedure
• Rename the desired AMI BIOS file to AMIBOOT.ROM and save it on a floppy disk. e.g. Rename A6712VMS.190 to AMIBOOT.ROM
• Insert this floppy disk in the floppy drive. Turn On the system and press and hold Ctrl-Home to force update. It will read the AMIBOOT.ROM file and recover the BIOS from the A drive.
• When 4 beeps are heard you may remove the floppy disk and restart the computer.
Award BIOS recovery procedure
• Make a bootable floppy disk
• Copy the Award flash utility files & bios file to the bootable floppy diskette
• Open Notepad and put the following command line e.g. awdfl826B w6777NMS.140 than save to the floppy drive and name as Autoexec.bat
• Restart system with the floppy diskette that contains the Award utility & bios file (it will take less than 2 minutes before screen comes out)
I know, I probably should have messed around before system drivers (besides what XP loads) are installed, but it never got pass the Bios load? Wierd!

Quote from: JETninja on 25-August-06, 02:08:49
Yes, so far so good! I'm hoping the Bios upgrade did it! I try to run filters to keep the dust down (pretty dusty here in SoCal) and clean them every few months. (I use "used" clothes dryer antistatic sheets)
What was concering was 2 HD's failed so close to each other. First a 40Gb WD (maybe 5 years old) and then a week later the IBM. Odd, considering I've never had one before in 7 years of PC's. This PC does get turned off every evening, where mine is always on. (so HD's always spinning)
With this Bios I'm hoping to ramp up the speed a tad, but I'll leave it alone for a bit longer.....
Thanks!
Sorry, I just ran across this last post. For what it is worth, I would definately not use dryer sheets, used ones or new ones. There are a lot of chemicals embedded in them. Some of those could be corrosive to some of the parts inside the computer. I would rather use some of the filter material that is used in several small appliances, such as air conditioners. They should be available in hardware stores, among other places. If not, try women's hose or pantyhose, folded over a couple of times perhaps.
Two elderly hard drives in a short time is not a significant red flag, but it is certainly something to watch. You could check the voltages with a good quality meter, but that process isn't necessarily as reliable as it should be. The voltages can vary quite quickly and cause problems. That would not necessarily show up on a meter, depending on how long the over voltage condition lasts. Then again, if the meter shows excessive voltage, I wouldn't wait to see another drive go out.
The readings on the BIOS look a little high, but not excessive. I'd like to see meter readings to confirm that, but it isn't a big deal.
The BIOS has NOTHING to do with hard drives going out.

Early Chipset Initialization Failure

Well hooked up my new computer and it was working good running XP pro and i started playing some unreal tournament and my computer just shut down, i try and restart it and it gets stuck on the 2nd combo of leds on d-bracket which is Early Chipset Initialization and the system will just hang there?? I tried all the basic troubleshooting nothing got it to work... anyone have an idea what the problem is? should I just RMA the board?

Just throwing my 2 cents in the mix... I had the same "Early chipset initialization" boot failure and it turned out the CPU was dead. Dead to the point that it would not POST far enough for the DBracket to indicate a dead CPU. Anyway, not sure if you have anyone with another AMD64 you can try...?

No Post, No Video, D-Bracket Early Chipset Init. error, Worked before CPU Upgrd.

Similar Messages

Maybe you are looking for