k7s5a CONFIG_INITIALIZATION_ERROR

[dannymac]

whenever my computer has been off for an extended period of time, it gives me this stop error in windows 2k when i boot up:

STOP: 0x00000067 CONFIG_INITIALIZATION_ERROR

but after i reboot, it does fine. here's my stats:

ecs k7s5a @ 133/133 (most recent bios)
AMD Tbird 1.2GHz @ 266MHz
2x256MB Crucial PC2100 DDR ram (default memory settings)
Enhance 300W ps
MSI GeForce3
Maxtor 30GB 7200rpm udma100
Affrey 56x cdrom

i have disabled the onboard modem. thats about it. i've also noticed that programs occasionally report invalid memory references, and the computer sometimes reboots for no apparent reason.

i've searched everywhere and cant find literature on this error or how to fix it. does anyone out there have ideas?

 

[Buz2b]

Could you list the entire error message you get? That would help. Also, one thing I find works well is to take the main portion of the error message and enter in in a Google search. That usually turns up many choices. Sounds more like a Win2K issue here than the MB, but we'll find out. Start with the error messages and their entire text.

 

[dannymac]

ok... here's the entire error message:

-----------------------------------------------
*** STOP: 0x0000067 (0x0000004, 0x00000007, 0x00000000, 0x00000000)
CONFIG_INITIALIZATION_ERROR

If this is the first time you've seen this Stop error screen, restart your computer. If this screen appears again, follow these steps:

Check to make sure any new hardware or software is properly installed. If this is a new installation, ask your hardware or software manufacturer for any Windows 2000 Updates you might need.

If problems continue, disable or remove any newly installed hardware of software. Disable BIOS memory options such as caching or shadowing. If you need to use safe mode to remove or disable components, restart your computer, press F8 to select Advanced Startup Options, and then select Safe Mode.

Refer to your Getting Started Manual for more information on troubleshooting stop errors.
--------------------------------------------------


and believe me... i have tried searching ALL over the internet for that error message. if you can find anything helpful, let me know. the most helpful thing i got from anywhere was "that error should never happen."

and yes, i've tried reinstalling win2k before, and the only device i have installed (except for all storage drives) is the video card.

 

[moregolf]

Ask a guy named Rebelwolf over at amdmb.com He knows that puppy inside out. Also the people at ocforums.com

 

[Buz2b]

RAM or BIOS. Start with RAM. Pull one stick and see what happens. Then switch and test the other stick. If for some reason both are OK, put both back in again and see if the problem returns. When testing, try each stick in EACH slot.
If that doesn't isolate the trouble try turning off the "System BIOS Cacheable" in the Advanced settings of the BIOS.

If those don't work, then drop back ten and punt. Actually, seek out a Win2K Guru. It would have to be some "glitch with that. There is a small chance it is the board; very small. I have not seen this error either and (as you related) had no luck finding anything on the net about it either.

 

[dannymac]

i have already gone through 4 sticks of Crucial memory trying to make sure it isnt the RAM, and i've already tried disabling the "system bios cacheable" option.

heheh... the guys at crucial thought i was nuts for trying to replace my ram, implying that i messed with it somehow and broke it. they didnt believe me when i said something was wrong, but allowed me to return them anyway. originally, one of my first sticks of crucial wouldnt let the mother board post (that is, after my CPU died, which i got amd to replace for me), so i got 2 replacements which are in now.


and thanks Moregolf, i'll check out amdmb.com and ocforums.com

any other ideas before i drop back 10 and punt?

 

[dannymac]

ok.... i have read the sites you referenced and tested my memory with that memtester for 16 straight hours at 133/133 with no errors.

i even reinstalled win2k today at 100/100 and played with it for a while with no problems.

but as soon as i changed it to 133/133 and tried to get into windows, i got a bluescreen immediately followed by a reboot. when i got in windows finally, IE crashed in like, 45 seconds.... then my whole system wouldnt respond.

it seems to run fine right now at 100/133 (i think thats the right order, cpu = 100, ram = 133).

i JUST GOT a BRAND NEW amd Tbird 1.2GHz @ 266 processor in the mail when my other one broke.

i'm already emailing ECS tech support back and forth and i'm trying to get them to send me a new one.

so what should i try now?

 

[patsun123]

ok... i went into the bios and disabled the floppy seek. BOOM !! it bluescreens and reboots continuously.

however, my roommate just happened to have a digital camera, so i kept snapping at the blue screen flash until i managed to time it right and capture it (or at least the important part of it, i think the bottom got cut off). here's the stop error it reports:

--------------------------------------------
STOP: c0000218 {Registry File Failure}
The registry cannot load the hive (file):
\SystemRoot\System32\Config\SOFTWARE
or its log or alternate.
It is corrupt, absent, or not writeable.

Beginning dump of physical memory
Physical memory dump complete. Con.
-----------------------------------------------

then it gets cutt off.

i cannot get back into windows. i tried clearing the CMOS but this didnt help. i guess i'll leave it off for tonight and try booting again in the morning. (on a friends computer for now)

so.... what do you guys make of all this?

 

[DAPUNISHER]

patsun123
Post the system specs including powersupply and brand of memory please. I'll give you a fix to try before you post the specs though. I've seen a few threads @OCworkbench with a similar problem to the 1 you describe and it was fixed by going into the bios to power management setup and choosing "NO" for ACPI aware O.S. if that doesn't do the trick then the system specs will help enormously.

 

[dannymac]

dapunisher:

patsun123 was my friend's computer i was on while i was reinstalling win2k. my stats are above in the first message:

> ecs k7s5a @ 133/133 (most recent bios)
> AMD Tbird 1.2GHz @ 266MHz
> 2x256MB Crucial PC2100 DDR ram (default memory settings)
> Enhance 300W ps
> MSI GeForce3
> Maxtor 30GB 7200rpm udma100
> Affrey 56x cdrom

i dont seem to get the errors anymore, but its because i'm running at 100/133. what a waste of a 1.2GHz processor... i'm having to run it at 900MHz. i've been emailing ECS for about a week and they've been no help. will they replace my board? or am i not going to win this battle? is there anyone out there who can run 133/133 stable?

 

[Buz2b]

Did you try disabling ACPI as DAPUNISHER recommended? I've seen the same thing with Win2K. The problem is that many many folks have no problem at all running Win2K with the ECS board. That means it is harder to isolate your trouble. There are no real board functions that could cause this type of trouble. Even from the look of the error messages it is looking like an OS issue. Try reloading with the ACPI option disabled, but do so at 133/133 if possible. Do a fresh install only. What is the model number of the Enhance PS you are using? Probably not the problem, just curious what combined voltage rating is.

 

[dannymac]

disabling the ACPI function and reinstalling win2k will be my next task... but i'm about to start finals, so i dont want to deal with it right now.

what features will i lose by disabling ACPI?

the enhance power supply model number is: ENP-0730

thanks a ton for your help

 

[yazz]

i have seen this problem on ECS boards before.... your system will install at the 100mhz bus setting, but not at the 133mhz setting. you can flash your BIOS all you want because that will not fix it. What you need to do it is get another BIOS chip from ECS or RMA your board back to your vendor/distributor. i have had ECS and my vendor send me new BIOS chips to replace the current one in the board. Once i swapped BIOS chips the board would operate at 133mhz FSB (even though it could operate at that speed before) and let me install win2k/XP or win98se with no issues at all. In my case the problem was the actual BIOS CHIP. I had to get 10 BIOS chips for the boards i had in stock for them to operate properly with a 266FSB CPU...

have fun
yazz