Unsolved

This post is more than 5 years old

2 Posts

3655

August 25th, 2000 19:00

Fatal Exception error 0D on shutdown

I work for a Hospital and we have had a problem with a fatal exception error on the shutdown of Windows 95 B version computers. It only seems to occur on Dell Dimension Mxxxa models. The error occurred after a policy was placed globally on our network for windows 95 boxes to save settings for each user. When this option is changed, the errors go away for a short time, and occur again.

I have tried reinstalling the drivers for the network card with new and old drivers, I have updated video drivers as well. The exact error message is " A Fatal exception 0D has occurred at 0337:00001F37. " I have searched both Dell's site and Microsoft Tech-Net information CD's for this error with no luck.

I currently have 4 computers in our facilities that are doing this exact error. Any information on this error is appreciated. Thanks.

On a more technical note, is there a program I can use to shadow the memory to see where this error is comeing from, or a way to trace back the memroy rewrite to a specific program?

Reverse Corrupoiton.
revcorrupt@hotmail.com
http://madodin.gh0st.net

2 Intern

 • 

2.2K Posts

August 26th, 2000 22:00

Unfortunately, I am also unable to find any additional specific information related to this error. You mentioned that you updated the video drivers; do all machines affected contain the same video card? Also, do all these machines have a specific printer driver loaded (even if it is a driver for a networked printer)? There have been cases where the video driver and printer driver cause conflicts.

If the systems have the same video card and/or have the same printer drivers loaded, you should try reducing the video acceleration. To do this go to START | SETTINGS | CONTROL PANEL | SYSTEM | Performance and click on Graphics and reduce the Hardware Acceleration. Click OK, and Close, and allow the computer to restart. If moving the slider one notch does not help, continue moving it to the left and restarting and see if it helps the issue.

While I do not know of a program that will allow you to view memory addresses directly before a crash, you may be able to isolate one running program that could be causing the problem. Before shutting down, press CTRL+ALT+DELETE quickly, and you should get a Close Program dialog box. For every item in this box EXCEPT for Explorer and Systray, click it and click End Task. The box will disappear each time you click End Task, so you will need to press CTRL+ALT+DELETE again to bring it back up until all other programs are gone. You may also want to wait approximately 10 seconds between clicking End Task and pressing CTRL+ALT+DELETE again to make sure another box does not appear, and if it does, click End Task again. Once everything is gone except for Explorer and Systray, you can proceed.

If the exception does not occur, you can (after restarting) eliminate one program in this box, then attempt to shut down. If that does not work, next time end task on two programs, and so forth.









2 Posts

August 28th, 2000 19:00

Unfortunately these systems are somewhat critical. Since this error only occurs at shutdown, it has not been a large enough priority to remove the system from service and diagnose. I will talk to the users and see if there is one that will be willing to give up a system. There are Network Printers attached to these systems, however none are connected to the same printer, therefore I don’t see that as a specific issue. I have also looked into many other programs as the cause, with no luck. I will work on removing one of the systems to run diagnostic tests. Thanks anyway.

0 events found

No Events found!

Top