Unsolved
This post is more than 5 years old
22 Posts
0
8093
March 2nd, 2004 19:00
Exception OE message
The more I know the more I realize how little I know.
Several times now I've had an Exception OE message as follows:
0028:C003/A54 in Vxd - this was called from 0028:C00030IF9 in vxd.
When I "Press any Key" as suggested, the Windows screen comes up with "Windows Shutting Down" - but it does not shut down. I have to literally pull the plug.
When the systems is brought back up I have Scan Disk because "windows was not properly shut down, one or more etc.. .I'm told that I should have shut down from the START MENU. At no time do I have access to my START MENU when all this is going on. Is that normal?
Anyway, why the error message and what is my solution. I already know it's not a good idea to pull the plug. I appreciate any comments.
Denny Denham
2 Intern
•
18.8K Posts
0
March 2nd, 2004 19:00
Fatal Exception 0E errors are difficult to correct. See the information here and in the links provided for some possible assistance.
teacup
22 Posts
0
March 2nd, 2004 21:00
Denny, thanks for your direction and links. Not interesting, but useful information. Right now I will limit myself to starting in Safe Mode and see what I find out. The correction aspect seems a little beyond me.
Otherwise, is there a link where I can key in my exact Exception OE to get a full description? I checked the most common "Fatal Errors" listed but did not find my particular one.
Teacup
pskelley
933 Posts
0
March 3rd, 2004 00:00
Here is another resource that might help.
http://support.microsoft.com/default.aspx?scid=%2Fsupport%2Fwindows%2Ftopics%2Ferrormsg%2Femresctr.asp
Windows Xp Professional
5.1.2600 Service Pack Build 2600
Dimension 4550 X-86 based PC
Bios A03, 11/12/2002
Pentium 4 2.0Ghz
256MB RAM
IE 6.0
Garfield Rules
51 Posts
0
March 3rd, 2004 02:00
Reading your post reinds me of my early days with windows. Usually when you get a VXD error it specifies which VXD threw to error. VXD files are what windows calls Virtual Device Drivers, meaning some programs (especially DOS) require direct access to the computers hardware (ie. hard drive, modem, etc.) and windows doesn't like to allow that. So their answer is VXD's, drivers which trick software into thinking it has direct access to the hardware. Since your error isn't specific as to which VXD file caused the OE trying to track down the specific cause and therefore cure may be difficult.
Dimension XPS Gen2
Win XP Home SP1
Intel P4 3.2Ghz HT 800mhz FSB
2Gb DDR3200 (400mhz) RAM
2 - 120Gb S-ATA HD 7200RPM 8Mb (non RAID currently) Intel ICH5R on-board RAID
2 - 60Gb ATA133 HD 7200RPM 2Mb (RAID 1) on a
Promise FastTrak TX2000 PCI UltraATA/133 RAID Card
128Mb Radeon 9800 Pro Video
SB Audigy2 Sound
CD-RW: 48X/48X/24X; DVD-ROM: 16X
DVD-RW DVD-4X/2.4X/2X CD-40X/24X/10X
Ext USB 100Mb ZipDrive
17" 1703FP LCD Monitor
Intel Pro 1000 Ethernet
56K PCI Data Fax Modem
teacup
22 Posts
0
March 8th, 2004 19:00