|
|
|
re: Windows Protection Error
Sunday, January 11, 2004 at 11:55 pm Windows 98 Annoyances Discussion Forum
Posted by Tom
(3 messages posted)
I had the same problem with a computer that I was doing a service call on. I was
scratching my head for hours. It turned out that my client bought a new stick of
256Mb PC-133 AZENRAM. This was causing the windows protection fault. I didn't even
think to check the RAM because I was convinced that it was one of the 6 virii that
was on his system.......or it could be that it's 3AM and I have to work 2 jobs tomorrow...meh
hope this will help a bit :)
On Thursday, October 18, 2001 at 10:54 am, Scott wrote:
>I've been currently dealing with this problem specifically with my uncle's computer
>and what it has turned out to be is a hardware conflict with some aftermarket RAM
>he purchased. In your case however, with a demo for an antivirus program it sounds
>like a driver conflict.
> I generally search windows error's in Yahoo....the following fix is from a
>link to Microsofts website with some solutions because it is a known bug....I'll
>cut and paste what I found and give you a link as well.
>_________________________________________
>Link http://support.microsoft.com/support/kb/articles/Q149/9/62.aspthe
>following is one fix of many for this problem...
>How to Troubleshoot Windows Protection Error Messages
>
>--------------------------------------------------------------------------------
>The information in this article applies to:
>
>Microsoft Windows 95
>Microsoft Windows 98
>Microsoft Windows 98 Second Edition
>Microsoft Windows Millennium Edition
>
>--------------------------------------------------------------------------------
>If this article does not describe the error message that you are receiving, view
>the following Microsoft Web site to view more articles that describe error messages:
>http://support.microsoft.com/support/windows/topics/errormsg/emresctr.asp
>
>
>SYMPTOMS
>When you start Windows, you may receive one of the following error messages, where
>device name is a device name:
>
>While initializing device device name Windows Protection Error
>-or-
>Windows Protection Error
>When you shut down your computer, you may receive the following error message:
>Windows Protection Error
>NOTE: To more effectively search the Microsoft Knowledge Base, use keywords that
>relate to your issue when you search. If you are searching for troubleshooting information
>that is not referred to in this article, please try searching the Microsoft Knowledge
>Base again by using keywords that are listed in the following Microsoft Knowledge
>Base article:
>Q242450 How to Query the Microsoft Knowledge Base Using Keywords
>
>
>
>CAUSE
>This behavior can occur when a when your computer loads or unloads a virtual device
>driver (VxD). In many cases, the VxD that did not load or unload is mentioned in
>the error message. In other cases, you may not be able to determine which VxD caused
>the behavior.
>
>Windows Protection error messages can occur under any of the following conditions:
>
>If a real-mode driver and a protected-mode driver are in conflict.
>
>
>If the registry is damaged.
>
>
>If either the Win.com file or the Command.com file are infected with a virus, or
>if either of the files are damaged.
>
>
>If a protected-mode driver is loaded from the System.ini file and the driver is
already
>initialized.
>
>
>If there is a physical input/output (I/O) address conflict or a random access memory
>(RAM) address conflict.
>
>
>If there are incorrect complementary metal oxide semiconductor (CMOS) settings for
>a built-in peripheral device (such as cache settings, CPU timing, hard disks, and
>so on).
>
>
>If the Plug and Play feature of the computer's basic input/output system (BIOS)
is
>not working correctly.
>
>
>If the computer contains a malfunctioning cache or malfunctioning memory.
>
>
>If the computer's motherboard is not working properly.
>
>
>If you installed Microsoft Office 97 and you are using the Novell Client 32 software.
>
>
>
>
>
>RESOLUTION
>To resolve a Windows Protection error message:
>
>Start your computer in Safe mode. For information about how to start your computer
>in Safe mode, view one of the following sections, depending on your operating system.
>
>Windows 95
>To start Windows 95 in Safe mode, press the F8 key when you see the "Starting Windows
>95" message, and then choose Safe Mode from the Startup menu.
>Windows 98 and Windows 98 Second Edition
>To start Windows 98 in Safe mode, restart your computer, press and hold down the
>CTRL key until the Windows 98 Startup menu appears, and then choose Safe Mode.
>Windows Millennium Edition (Me)
>
>
>To start Windows Me in Safe mode, press and hold down the CTRL key while you restart
>your computer, and then choose Safe Mode on the Windows Me Startup menu.
>If you do not receive the error message when you start your computer in Safe mode
>or when you shut down your computer from Safe mode, view one of the following articles
>in the Microsoft Knowledge Base: Windows 95:
>Q136337 Troubleshooting Windows 95 Startup Problems
>Q145926 How to Troubleshoot Windows 95 Shutdown Problems
>Windows 98:
>Q188867 Troubleshooting Windows 98 Startup Problems
>Q202633 How to Troubleshoot Windows 98 Shutdown Problems
>Windows Millennium Edition (Me):
>
>
>Q273738 TITLE: Troubleshooting Windows Me Startup Problems
>Q273746 TITLE: How to Troubleshoot Windows Me Shutdown Problems
>If your computer is a Plug and Play computer, reinstall Windows by using the setup
>/p I command.
>
>For additional information about how to install Windows 95, click the article number
>below to view the article in the Microsoft Knowledge Base:
>Q129260 Windows 95 Setup: Description and Troubleshooting Steps
>If you are using the Novell Client 32 software, remove it, and then install Microsoft
>Client for Novell Networks.
>
>
>Verify that the computer's CMOS settings are correct. For information about how
to
>change CMOS settings on your computer, view the computer's documentation or contact
>the computer manufacturer.
>
>
>Install a "clean" copy of Windows in an empty folder. For further information, please
>see one of the following articles below:
>
>
>Q277648 How to Install Windows Millennium Edition in a New Folder [winmil]
>Q193902 How to Install Windows 98 Into a New Folder
>Q142096 How to Reinstall Windows 95 to a New Folder
>IMPORTANT: If the error message still occurs, it is most likely caused by faulty
>hardware.
>
>
>
>MORE INFORMATION
>The VxD that is generating the error message can be any VxD, either a default VxD
>that is installed, or a third-party .386 driver that is loaded from the System.ini
>file. If you do not know which driver is causing the error message, create a Bootlog.txt
>file, and then check to see which driver is the last driver that is initialized.
>This is typically the driver that is causing the problem.
>
>NOTE: You may also receive a Windows Protection error message when you restart Windows
>95 after you install a program or make a configuration change to your computer.
For
>additional information about this issue, click the article number below to view
the
>article in the Microsoft Knowledge Base:
>
>Q157924 Err Msg: "IOS Failed to Initialize" on Boot
>For additional information about how to resolve Windows protection issues, click
>the article number below to view the article in the Microsoft Knowledge Base:
>Q131431 How to Troubleshoot Registry Errors
>
>Additional query words: wpe corrupt win command com
>
>Keywords : kberrmsg kbtshoot diskmem win95 win98 win98se kbWinME kbProd2Web kbDiskMemory
>Issue type : kbprb
>Technology : kbWinMEsearch kbWin95search kbWin98search kbWin98SEsearch kbZNotKeyword3
>kbWin98 kbWinME kbWin98SE
>_________________________________________
>
>
- Written in response to:
- re: Windows Protection Error (Scott: Thursday, October 18, 2001 at 10:54 am)
There are presently no replies to this message.
|
|
All messages in this thread [show all]
 |  |  |  | re: Windows Protection Error (Tom: Sun, Jan 11, 2004, 11:55 pm) |
| |
| |
Return to the Windows 98 Discussion Forum
|
|
|
|