| THE | E | LIST | N | EWS |
| by Mr. E | ||||
An Invalid Page Fault Occurs in Module SHDOCVW.DLL When You Open My Computer or Control Panel Win95, Win98, Win98 SE (New content 6/5/02)
One known cause for this is a damaged URLMON.DLL file. Solution: Extract a new copy from your Windows CD. Links to companion articles are given for other related situations.
Invalid VxD Dynamic Link Call from VSDATA95(01)... Win95, Win98, Win98 SE, Win ME (New content 6/5/02)
ZoneAlarm, my favorite freeware firewall program, is great! But there are a few known problems with it — at least with some versions of ZoneAlarm on some versions of Windows. One of these is the situation, in Windows 9x, where you get the error message Invalid VxD dynamic link call from vsdata95(01)+00012474 to device "0028", service 800a. Your Windows configuration is invalid. Run setup again to correct this problem. If this occurs while you are in the middle of upgrading to a new version of Windows, reinstalling your current Windows version over itself, or after you startup in Safe Mode and then go straight into Device Manager, then ZA is on the suspect list. The solution is to uninstall it. (You really shouldn’t be running software like this during an upgrade or reinstallation anyway!)
Invalid VxD Dynamic Link Call to Device 3 Service B Win95, Win98, Win98 SE, Win ME (New content 6/5/02)
But maybe you get a very different sort of Invalid VxD Dynamic Link Call error message — specifically, the one in this article’s title. This can occur if the SYSTEM.INI file is blank. Solution: Get a new copy of SYSTEM.INI. The article walks you through it.
SETUP caused a General Protection Fault in module SETUP.EXE Win95, Win98, Win98 SE (New content 6/5/02)
When this occurs during an installation of AOL... well, if nothing else, it’s one more good argument for not installing AOL. That aside, the immediate cause (besides the AOL software) is that your computer’s clock is set for the wrong date — specifically, because it is set for a future year.
Come to think of it, this is a rather cool feature of AOL. If they leave it in place, maybe it will slow down a few of those folks who set their clocks to 2047 and then go post on the newsgroups! OK, on second thought, AOL gets my vote on this one. ;)
Error Message Refers to the KERNEL32.EXE File if Your Computer Is Infected by the Worm_badtrans.b Virus Win XP (New content 6/5/02)
Words you do not want to see on your computer: “KERNEL32.EXE has encountered a problem and needs to close. We are sorry for the inconvenience.” You see, there is no Windows file named KERNEL32.EXE. There’s a very important file named KERNEL32.DLL — but not .EXE. The .EXE version is a Badtrans variety of virus. Run up-to-date antivirus software to get rid of it. (And don’t be fooled by similar error messages that tell you KERNEL32.EXE is missing.)
STOP 0x0000000A Error Message When You Change from AC Power to DC Power Win XP (New content 6/5/02)
Of all the categories of Stop Messages (the variety of error message characteristic of NT-based operating systems such as Windows 2000 and XP), 0x0000000A (abbreviated 0x0A) is the most common. It can be caused by a number of different things, most commonly faulty or incompatible hardware or software. You can think of it as sort of the General Protection Fault of the NT world. Several articles exist for addressing it and are linked on my Knowledge Base Links: Stop Messages page. Most of the time, the best solution is the “General Troubleshooting” checklist that I have near the top of that page.
The present article discusses something much more specific, though. It addresses the situation where you get this error message just after you have changed from AC to DC power on your laptop (for example, when you unplug or replug the power supply into the computer while it is in Standby mode). In that special situation, the error is due to a bug in Win XP. Microsoft has a patch for the bug. The article provides further information and a link to the patch.
Stop 0x000000ED Error Message When Volume on IDE Drive with Caching Enabled Is Mounted Win XP (New content 6/5/02)
If you are using the NTFS file system on some IDE drives, at startup you might get the UNMOUNTABLE_BOOT_VOLUME error message (Stop Message 0xED). Certain normal behaviors of IDE disk drives make them vulnerable to a type of corruption in NTFS, leading to this problem. The article suggests several solutions, the best of which (in most cases) is the installation of a patch that resolves this particular problem. The articles gives a link to the patch.
By the way, the Knowledge Base Links: Stop Messages page has been growing as new information becomes available. I can happily recommend it as a first stop in addressing Stop Messages. In the last couple of months, new sections were added on the 0x76 error, PROCESS_HAS_LOCKED_PAGES, caused by a driver not cleaning up completely after an I/O operation and on its companion error message, 0xCB, DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS. There is also a new section on 0x23, FAT_FILE_SYSTEM, a problem with many causes but which, primarily, means that some problem occurred within a read or write to a FAT16 or FAT32 file system drive. Additionally, many articles have been added to other sections. This has become one of the most popular pages on the Windows Support Center site.