PLEASE HELP Can't install any OS?

[Liddle]

I recently formatted my hard drive. I tried to reinstall windows and was given this error message.

Standard mode: Fault outside of MS-DOS Extender.
EC=0000 CS=0397 IP=74D0 AX=0000 BX=0397 CX=FFB1 DX=0397
SI=2ABA DI=7041 BD=OFBO ES=038F SS=027F SP=OF94

I have tried to reinstall on two different hard drives and with both win95 and win98 and winME and get the same error. I have an idea that it might be a problem with the BIOS. what should I do, am currently using a P166 with 16ram so PLEASE HELP ME!!.

 

[reghakr]

hope this helps:

Windows Err Msg: Fault in MS-DOS Extender

------------------------------------------------------------
The information in this article applies to:

Microsoft Windows operating system versions 3.1, 3.11
Microsoft Windows for Workgroups versions 3.1, 3.11
Microsoft Windows 95
Microsoft Windows 98

------------------------------------------------------------
SUMMARY
This article discusses the following two error messages with stack dump:


Bad Fault in MS-DOS Extender
-and-
Standard Mode: Fault outside of MS-DOS Extender


Raw fault frame:
EC=0344 CS=031F IP=85E2 AX=001D BX=0005 CX=1800 DX=155F
SI=0178 DI=0178 BP=016E DS=027F ES=027F SS=027F SP=0166


MORE INFORMATION

Bad Fault in MS-DOS Extender
This error message occurs when the fault handler dispatcher in DOSX.EXE generates another cascaded fault while trying to handle a protected-mode exception. This error is usually caused by one of the following factors:

HIMEM.SYS is unable to control the A20 line.

DOS=HIGH is not functioning properly (related to HIMEM.SYS control).

The RAM, static RAM (SRAM), single in-line memory module (SIMM), or dynamic RAM (DRAM) chips are not functioning properly.

You are running DR DOS.

The third-party memory manager is not configured correctly.

The EMM386.EXE NOEMS x=A000-EFFF line is missing from the Config.sys file.

You have an old, out-of-date ROM BIOS.

Your CMOS settings are incorrect.

Your Windows files are old or corrupted. To test this, create a new directory on the hard drive, and install Windows in that directory.

Your disks are corrupted.

Your system is infected with the Form, Forms, Noint, or Yankee Doodle virus.

Standard Mode Fault Outside MS-DOS Extender
This error message occurs when the Kernel generates a processor exception during initialization (before it has installed its own exception handlers) or when the Kernel determines that it cannot handle an exception. The causes are the same as those for the "Fault in MS-DOS Extender" error.

Meaning of Stack Dump and Raw Fault Frame
The portion of the display labeled "Stack Dump:" should always be the same and does not carry much valuable information.

The portion of the display labeled "Raw Fault Frame"

EC=0344 CS=031F IP=85E2 AX=001D BX=0005 CX=1800 DX=155F
SI=0178 DI=0178 BP=016E DS=027F ES=027F SS=027F SP=0166

contains information generated by the 80286 or 80386 processor in response to the original fault. The meaning of these settings is as follows:

Setting Meaning
------- -------
EC=xxxx An exception code produced by the processor in response
to the original fault.

IP=xxxx The program counter of the faulting instruction (8086
register "IP&quot.

CS=xxxx The code segment of the faulting instruction. If this is
"0053" or "005B", the (original) fault was in DOSX.EXE,
the "MS-DOS Extender."

FL=xxxx The flag's image at the time of the original fault.

SP=xxxx The stack pointer at the time of the original fault.

SS=xxxx The stack segment at the time of the original fault. If
this is "004B", the fault occurred on a stack belonging
to DOSX.EXE.


The CS and IP sections tell at what point in the faulting program that the original problem was detected.

For more information about A20 handlers, see the following article in the Microsoft Knowledge Base:

ARTICLE-ID: Q72302
TITLE : Specifying A20 Handlers with HIMEM.SYS /M in MS-DOS

reghakr

 

[Liddle]

But what should I do?? I never had a problem before this format and I have formatted many time before. Do you think I should go and buy a new Motherboard??

 

[reghakr]

Then why did you re-format?

reghakr

 

[Liddle]

You miss understand I meant that I never had a problem re-installing windows before this format. I formatted due to I virus on my system which I have just learnt could have infectde my BIOS also.

 

[Guest_imported]

Maybe his computer totally locked up on him or sommat, use ya brain. The guy needs 2 know the way fix the prob, not 2 look into a past tense.

 

[reghakr]

RickyNoHelp...Forget it, it's not even worth it LOL

I usually ask what the problem was that caused the re-format. Many times it's because of hardware, and there's no way to get it to install untill the hardware problem is fixed.

I think these two would be the most likely:
You have an old, out-of-date ROM BIOS.
Your CMOS settings are incorrect.

Or the virus still resides in the boot-sector.

What I would try at this point is to boot with your boot disk, and from the a: prompt type sys c:

Hard to say just what happened there, but if you can accomplish that and can run scandisk you might be ok. Another last resort kind of command you could try is:
fdisk /MBR

Or visit the site of your virus scanner program and look for ways to manually rid the virus from your computer.

reghakr

 

[Guest_imported]

Might be a good idea to get your boot disk(s) checked for viruses as well, otherwise you're in a vicious circle.

ROGER - GØAOZ.

 

[Liddle]

The virus I had/have was called W95/CIH or chenobyl.

I can run scandisk and it finds no errors, the BIOS is the same one I've had since I got the computer and the BIOS settings are set to defualt which they were last time I formatted and installed windows. So none of them are the problem.

Please tell me what fdisk /MDR does. I have already tried using fdisk to add a new FAT32 partition before formatting but that doesn't help my problem.

i have a virus protection device built into my BIOS which stops anything from the boot sector entering ram. The only thing I can think of is that the BIOS has been overwritten by the virus.

Please continue to help me out of the people I have spoken to you are the only one who has a clue that has a clue what they are talking about.

Thnx

 

[edfair]

/mbr writes a new boot program onto the boot sector. It leaves the partition information alone. It overwrites the existing boot program and is one way to be rid of a boot sector virus. Ed Fair
efair@atlnet.com

Any advice I give is my best judgement based on my interpretation of the facts you supply.

Help increase my knowledge by providing some feedback, good or bad, on any advice I have given.

 

[Liddle]

Thansk, please check the board again tommorow as I won't be able to try any of your suggestions until then. Tommorow I will tell you if I still have a problem or if hopefully you help has given me a solution.

 

[reghakr]

Liddle,

From Microsoft:
NOTE: Some systems have antivirus capabilities built into the system. If this option is left enabled in BIOS/CMOS settings, you may receive a warning about "virus-like activity" or "Master Boot Record" changes. You must allow these changes to take place for Setup to complete successfully. See your antivirus software documentation for more information.

If this applies, disable the virus protection in the BIOS and give it a try.

reghakr

 

[reghakr]

More:

After using Fdisk to create my primary DOS partition and format my HDD, I try to run setup to install Win98. However I keep getting the following massage: Standard Mode: Fault outside MS-DOS extender. This is a new one for me and I can't seem to get around it!

These are the answers so far
Have you set your Primary partition as the active partition when using fdisk then formatted the C drive using the format c:/s command? If so Setup should then run OK from CDROM but don't forget that your CDROM will be moved forward one letter, ie: if your CDROM is normally D it will have become E temporarily.

reghakr

 

[reghakr]

More yet:

Standard Mode Messages
If you get any of the following error messages, remove any memory managers (such as EMM386.exe, QEMM, or 386Max) from your Config.sys file, and then run Setup again.

Standard Mode: Invalid DPMI return.
Standard Mode: Fault in MS-DOS Extender.
Standard Mode: Bad Fault in MS-DOS Extender.
Standard Mode: Unknown stack in fault dispatcher.
Standard Mode: Stack Overflow.

NOTE: If you still have problems, add EMM386.EXE back into your Config.sys file and exclude all ranges. For example,

device=c:\windows\emm386.exe x=A000-FFFF

If you encounter these messages or if your computer stops responding during Setup, turn on double-buffering in SmartDrive. Several SCSI hard drives and some ESDI drives require double-buffering.

To turn on double buffering, add the following line to the beginning of your Config.sys file:

device=c:\windows\smartdrv.exe /double_buffer+

where "c:\windows" is the path to your Windows directory.

reghakr

 

[biday77]

In light of your system specs,I'd seriously consider a new system. Prices are very cheap now.

 

[BOKA]

I had the same problem recently and consider it a hardware incompatibility problem. I installed Maxtor 3.2G harddrive into a clone system with ASUS motherboard (Intel 430FX chipset, P166, Award BIOS) and tried to install Win98 on it and I would get either the same error or PC would lock up completely just when it would finish running scandisk and would be starting the setup wizard. I also tried to install Win95 with the same result. That happened on two Maxtors drives. Then I took Fujitsu drive instead and everything went without a glitch.
Maxtors worked fine in Compaq or DELL, BTW.
This is not the first time I had a problem with Maxtors and clone PCs, so I am trying to stay away from Maxtor.

Hope this helps.

 

[Liddle]

To Start with I'd like to clear this up I do not have a P166 as my main computer that is the computer I was using to post on the forum. The computer that would not install any OS is a P3 700mhz 192Mb ram TNT2 32Mb etc...

I had to clear that up cos anyone using a P166 as their main computer in this day an age is a serious loser.

anyway...Problem Solved.

After consulting with people at SOPHOS they told me that if the virus had infected mt BIOS it will literally have been wiped clean and my PC unusable. He then went on to tell me that the problem must lie within a hardware area of my computer.

For many months I had been overclocking my computer so long in fact that I totally forgotten that I had done it and just took my clockspeed for granted. Anyway I decided to try resetting my clock speed back to it's original to see if this would work.

I booted up and the win 98 installation began first time. Somehow DOS must have detected the overclock and wasn't as stable withit as windows.

Thanks for the help. I can now go back to playing counter-strike, and throw this slow P166 back in the atic where it belongs.

 

[pintail]

Man! This posting is a great example of asking the right question with all of the relevant information in order to get the right answer. A lot of back and forth with good intentions took place, which could have been largely avoided if the overclocking issue had been raised. Based upon the facts presented, the responders tried to be helpful but were hindered by the lack of full knowledge! This should be a lesson for everyone.