|
|||||||
![]() |
|
|
LinkBack | Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
|
#1 |
|
Wrench Bender
Join Date: Dec 2002
Location: Plymouth,MN
Posts: 5,961
|
Another "fatal exception" error person
Got a "fatal exception 0D has occured at 0028.C14B9781 in VXD DISKVSD(01) +000004E1"
Has happened a couple of times and tried looking it up at M$ and Googling. No luck/any clues?
__________________
"When sliding down the banister of life; look out for splinters pointing up."
|
|
|
|
|
|
#2 |
|
Member (12 bit)
Join Date: Nov 2001
Location: Woodland Hills, CA (suburb of Los Angeles)
Posts: 4,014
|
Here's a blurb from the Knowledge Base:
"A Fatal Exception 0D is an error message that is most commonly found, but not limited to, out dated or damaged video display adapter drivers and out dated multimedia software; however, this error message has also been know to occur when the Hsflop.pdr file is missing or damaged" This quote is taken from the webpage: http://support.microsoft.com/default...g%2fkbfe0d.asp On that same webpage are more pages referencing specific areas for either Win98 or WinMe OD errors. On the hardware side of life, you can test your system memory (RAM) just to make sure it's OK, since this sort of error can also be caused by faulty modules http://www.simmtester.com A few system files can be at fault when corrupted, so you can also try a run of the System File Checker to look for corrupt files. Have your WinME CD ready, or if you've copied the .cabs to the hard drive, you can point sfc there. You may have had something place an older version of Diskvsd.vxd in your system, overwriting a newer version - and this is causing the errors. You could try using System Restore if you have WinME to go to a restore point from before the errors started. In Win98se, you could use sfc to "extract one file from disk", and try pulling a fresh copy from the Win98se CD. If the version on the CD is still too old for whatever is requesting the recent version and giving the error - see if you can track it down to a particular program or driver, and update-or-uninstall/reinstall those. Hopefully it's one of the shorter fixes! . . . Gary [p.s. the location of the diskvsd.vxd file is usually in C:\Windows\System\IOSUBSYS\ ... and the hsflop file mentioned in the MSKB note is usually associated with errors concerning the floppy drive controller - your error message doesn't really indicate any trouble there] Last edited by GaryRouth; 02-14-2004 at 08:46 PM. |
|
|
|
![]() |
| Bookmarks |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|