An exception 06 has occured

[mike12]

When booting up my wife's computer (Windows 98 SE), I get the following message. "An exception 06 has occured at 0028:c148f201 VxD CDR4VSD (01) + 000142C1. This was called from 0028:C1471195 in VxD CDVSD(01) + 00000e65. It may be possible to continue" If I hit any key, I can continue. I ran Spybot S&D and it found 11 items which I removed. I tried to run Ad-Aware also, but it stopped and I got a similiar message as above but the numbers were different. I scanned the computer with AVG and no problems. I also noticed that when I click on MY COMPUTER on the desktop, I get the same message as above, exactly. Any suggestions ?

[GaryRouth]

Hi Mike12

I've seen a couple of approaches to fixing this:

1) If you can start the computer in Safe Mode: try uninstalling roxio's Easy CD Creator, if you have it on your system. [You can uninstall it from the Add/Remove applet in the Control Panel]. Reboot, and see if the error has vanished. You can then try installing roxio again & testing for the error (if it recurs, you'll uninstall it again & search for an update/patch on their website) - this approach is for computers who experience the error immediately after installing CD-recording software (so your program might be different - but roxio's was the most common).

2) Rename the offending file. You boot the computer with a bootable floppy that matches your version of Windows (or from a Win98se CD, and choose "start computer with CD-rom support"). From the A:> prompt, type:

cd C:\WINDOWS\SYSTEM\IOSUBSYS
rename cdr4vsd.vxd cdr4vsd.old

Then reboot, and see if the error is gone.

There are some other angles for fixing these errors, but these two are fairly quick and usually painless.
. . . Gary

[mike12]

Hi GaryRouth--- Easy CD creator was not on the computer, so I renamed the bad file per your directions. FIXED !!! I can now boot up the computer without that error message. I also can click on MY COMPUTER on the desktop and open it without any messages. I also can run Ad-Aware without any error messages, so it looks like the problem is fixed ! Many many thanks, Mike