Solved

cascade of events

Posted on 1999-01-23
2
226 Views
Last Modified: 2013-12-28
problems started when I tried to install 64mg of edo ram on my computer. after installing my computer never ran correctly and would get a host of errors including 'bad registry'. the new ram works on my friends computer. i am back to my original ram, but i am now getting stack dump errors randomly during netscape, or eudora, winfax and other  programs. oh by the way i had also recently put in a new 56k usr winmodem about the same time that these problems started happening.
0
Comment
Question by:salraf
2 Comments
 

Accepted Solution

by:
neptune26 earned 50 total points
ID: 1652710
Your stack dump errors are probably caused by problems with your new modem and/or it's drivers.  You can get the most recent updated drivers from USR/3Com.  On your RAM problem, are you certain that your motherboard will accept EDO RAM?  And is it of the proper speed?  There is also a chance that the SIMMS or DIMMS were not seated properly.  When you installed the RAM, did your Power On System Test recognize 64MB?
0
 
LVL 25

Expert Comment

by:dew_associates
ID: 1652711
Neptune, I have to disagree with you Stack Dumps have no relationship at all to modems or the programs that use them, nor even the virtual device drivers they require.

Stack dumps are normally caused by either of two reasons:

Bad Fault in MS-DOS Extender
-and/or-
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
 
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.
- You have an old, out-of-date ROM BIOS.
- Your CMOS settings are incorrect.
- Your Windows files are corrupted. To test this, you can create a new directory on the hard drive, and install Windows in that  directory, or you can run SCANREG/FIX from a dos prompt (not windows MSDos prompt!)
- 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 X86 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
responseto the original fault.

IP=xxxx   The program counter of the faulting instruction (X86       register "IP").
 
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.
==================

If I were you, here's what I would do:

HIMEM.SYS  (verify that this is being called properly)

DOS=HIGH (relating to HIMEM.SYS)  Make sure this is used correctly or eliminated entirely if being used.

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

(Verify that your RAM if functioning properly)

The third-party memory manager is not configured correctly.

If your running one, or even a disk manager, such as that for Western Digital, get rid of it unless you have no alternative.

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

(Verify your Bios and that it is current)

Your CMOS settings are incorrect.

(Boot your system into the Bios setup and verify the settings, especially for memory issues, such as SDram v. Edo.)

Your Windows files are corrupted.

(To test this, you can create a new directory on the hard drive, and install Windows in that  directory, or you can run SCANREG/FIX from a dos prompt (not windows MSDos prompt!))

Your disks are corrupted.

(Run scandisk in thorough mode either from a dos prompt or while within safemode)

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

(Verify there are no virus's on the system, even those that could infect your computers Bios)

If you need more, ask!
Dennis
0

Featured Post

Flexible connectivity for any environment

The KE6900 series can extend and deploy computers with high definition displays across multiple stations in a variety of applications that suit any environment. Expand computer use to stations across multiple rooms with dynamic access.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
robocopy 33 117
Calibrating x & y screen  pixel coordinates 1 41
Windows Restrict installation 11 40
Optiplex 755 Very Sluggish in Normal Windows 8.1 Pro 10 26
When you try to extract and to view the contents of a Microsoft Update Standalone Package (MSU) for Windows Vista, you cannot extract the files from the MSU. Here we are going to explain how to extract those hotfix details without using any third pa…
In this article, I will show you HOW TO: Perform a Physical to Virtual (P2V) Conversion the easy way from a computer backup (image).
This Micro Tutorial hows how you can integrate  Mac OSX to a Windows Active Directory Domain. Apple has made it easy to allow users to bind their macs to a windows domain with relative ease. The following video show how to bind OSX Mavericks to …
Windows 8 came with a dramatically different user interface known as Metro. Notably missing from that interface was a Start button and Start Menu. Microsoft responded to negative user feedback of the Metro interface, bringing back the Start button a…

821 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question