#Memory Protection Fault
5 messages in this thread
Brian,
3ds Ver 4 is crashing during the rendering process. It leaves a
message at the Dos prompt, "Memory Protection Fault,
CS:EIP=000FH:0010B5B5H" (the last nine alpha-numerics are always
different). I've had this happen on both stand alone systems and now
on my Lantastic net, as well as WFW. Microsoft Dos tech support is
unfamiliar with this memory address, which leads me to believe it is
Pharlap related. The crash usually occurs when rendering between
frame 1 to 50, file size doesn't matter. The problem occassionally
occurs when just running the program also. It happens on any machine
on the net.
Can you help me isolate this as a Pharlap memory addressing problem,
or direct me a new direction? Thanks
<<"Memory Protection Fault, CS:EIP=000FH:0010B5B5H">>
Memory protection faults are almost always the result of a memory conflict.
below are some instructions to help you isolate and identify that conflict.
-brian
Title: Clean system boot; diagnostics for memory conflict…
Description:
To confirm that the problem is caused by a memory conflict, re-start the
computer with simplified settings (a 'stripped system') and see if the problem
goes away.
For DOS-only computers, a stripped system means that the computer is
rebooted without terminate and stay resident (TSR) programs nor
device drivers that are not absolutely necessary for the operation of
the operating system and computer. The Autodesk program should also
be configured for VGA display if possible, to rule out display driver
conflicts.
To reboot into a stripped system for 3D Studio and Animator Pro, change the
system files as follows:
CONFIG.SYS should contain only:
FILES=40
BUFFERS=20
AUTOEXEC.BAT should contain only:
PATH=<your path>
PROMPT=<your prompt>
You may want to use the DOS SYS command to create a bootable floppy
for this trouble-shooting exercise and place these simplified system
files on the diskette. Or, you may edit the existing CONFIG.SYS and
AUTOEXEC.BAT files currently on the hard disk (make back-up copies
first). Make sure you have a bootable DOS floppy on hand, just in
case the computer has trouble rebooting.
Note: Quarterdeck QEMM users may find it helpful to review the QEMM
trouble-shooting documentation and use the Analyze utility to track
down memory conflicts.
Trouble-shooting:
If the program now operates correctly, the next step is to determine which
program or driver in your system files is causing the conflict. Edit the
CONFIG.SYS and AUTOEXEC.BAT files, adding one device driver or TSR command at
a time, rebooting, and starting 3D Studio/AAPRO until the error reappears.
When the error happens, the last item you added to the configuration is
probably the trouble maker. Once we know which drivers are conflicting, we can
determine the proper course of action.
If you are using special display adapters (for example, a Targa frame buffer),
you should check the documentation that came with the display driver to see if
special memory settings or EMS exclusions are needed.
Brian,
A guru told me to put a /s after the cd-rom driver. Something to do with the
ms-version being written for networks.
Rick
<<A guru told me to put a /s after the cd-rom driver. Something to do with the
ms-version being written for networks.>>
The /s paramater stands for SHARE and allows other users on the network (if
peer to peer) to access your CD-ROM.
-Brian
Brian,
My machine exactly. I think it may be the type of simm. I replaced a single
sided simm with a double-sided simm – it's been blazing all da day. I'm running
an ASUS 100MHZ/P5 with 16meg. The single sided simm has two
chip outboard on either end with a encoder chip(s) in the middle.
Pop the top and take a look. I hope that's it. Let me know. I also
posted mess# 165669 to Richard Turnock(same problem).
Good Luck, Chris Martin