Modell
asked on
Windows Protection Errors ... on StartUp
When cold-booting my computer I am always greeted with:
Windows Protection Error: you will need to restart your computer.
Sometimes this statement is preceded by a reference ... like:
While Initializing device * * * :
Where the asterisks may at times be V86mmgr ... at times, other things.
Because of this, my computer is always intent on starting in Safe Mode. Does anyone have any idea of what is going on?
I also have a funny thing happen when I go to Restart. At times the computer gets almost to the point of restarting the windows splash screen ... but hangs with the black screen until I force a reboot.
Any help will be greatly appreciated. Thanks
Windows Protection Error: you will need to restart your computer.
Sometimes this statement is preceded by a reference ... like:
While Initializing device * * * :
Where the asterisks may at times be V86mmgr ... at times, other things.
Because of this, my computer is always intent on starting in Safe Mode. Does anyone have any idea of what is going on?
I also have a funny thing happen when I go to Restart. At times the computer gets almost to the point of restarting the windows splash screen ... but hangs with the black screen until I force a reboot.
Any help will be greatly appreciated. Thanks
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Hi Modell!
A Windows Protection Error means that an error occurred loading or unloading a virtual device driver (VxD). In many cases you can tell from the error message which VxD did not load, but in other cases you may not be able to determine which VxD caused the problem.
Windows Protection Errors can occur when any of the following conditions occur:
- A real-mode driver and a protected-mode driver are in conflict.
- The registry is damaged.
- The Win.com or Command.com file is infected with a virus or is damaged.
- A driver is being loaded from the System.ini file for which a protected-mode driver has already been initialized.
- There is a physical I/O or RAM address conflict.
- There are incorrect CMOS settings for a built-in peripheral device (such as cache settings, CPU timing, hard disks, and so on).
- The Plug and Play feature of the computer's BIOS is not working correctly.
- The computer contains a malfunctioning system cache or memory.
- The computer's motherboard is not working properly.
- You installed Microsoft Office 97 and you are using the Novell Client 32 software.
In order to try and resolve a Windows Protection Error, try the following steps:
1. Start your computer in Safe mode. If the error does not occur when you start in Safe mode or when you shut down from Safe mode, see the appropriate article in the Microsoft Knowledge Base:
Windows 98: ARTICLE-ID: Q188867
TITLE: Troubleshooting Windows 98 Startup Problems
ARTICLE-ID: Q238096
TITLE: How to Troubleshoot Windows 98 Second Edition Shutdown Problems
2. If your computer is a Plug and Play computer, reinstall Windows using the following command:
setup /p I
3. Make sure that the computer's CMOS settings are correct. For information about changing CMOS settings on your computer, please refer to the computer's documentation or manufacturer.
4. Install a clean copy of Windows in an empty folder. Choose the Custom installation option and do not let Setup detect the hardware in your computer. Install only a mouse, a VGA video adapter, and a keyboard.
If the error still occurs, it is most likely caused by faulty hardware.
The VxD that is generating the error message can be any VxD--either a default
installed VxD or a third-party .386 driver being loaded from the System.ini
file. If you do not know which driver is causing the error message, create a
Bootlog.txt file and check to see which driver was the last driver initialized.
This is typically the driver causing the problem.
NOTE: You may also receive a Windows Protection error message when you restart Windows 98 after installing a program or making a configuration change to your computer.
You can also click Start, Run and type in MSCONFIG and click OK.
Now go to the Startup tab, note everything that is checked, then uncheck all and reboot.
If the problem does not appear, then the problem is in the startup program group. In this case, check one item at a time and reboot to identify which program is the offender.
Note also, that overheating the CPU or a hard drive with cluster\sector problems, or a hard drive that has a heat problem, will also cause this problem.
Dennis
A Windows Protection Error means that an error occurred loading or unloading a virtual device driver (VxD). In many cases you can tell from the error message which VxD did not load, but in other cases you may not be able to determine which VxD caused the problem.
Windows Protection Errors can occur when any of the following conditions occur:
- A real-mode driver and a protected-mode driver are in conflict.
- The registry is damaged.
- The Win.com or Command.com file is infected with a virus or is damaged.
- A driver is being loaded from the System.ini file for which a protected-mode driver has already been initialized.
- There is a physical I/O or RAM address conflict.
- There are incorrect CMOS settings for a built-in peripheral device (such as cache settings, CPU timing, hard disks, and so on).
- The Plug and Play feature of the computer's BIOS is not working correctly.
- The computer contains a malfunctioning system cache or memory.
- The computer's motherboard is not working properly.
- You installed Microsoft Office 97 and you are using the Novell Client 32 software.
In order to try and resolve a Windows Protection Error, try the following steps:
1. Start your computer in Safe mode. If the error does not occur when you start in Safe mode or when you shut down from Safe mode, see the appropriate article in the Microsoft Knowledge Base:
Windows 98: ARTICLE-ID: Q188867
TITLE: Troubleshooting Windows 98 Startup Problems
ARTICLE-ID: Q238096
TITLE: How to Troubleshoot Windows 98 Second Edition Shutdown Problems
2. If your computer is a Plug and Play computer, reinstall Windows using the following command:
setup /p I
3. Make sure that the computer's CMOS settings are correct. For information about changing CMOS settings on your computer, please refer to the computer's documentation or manufacturer.
4. Install a clean copy of Windows in an empty folder. Choose the Custom installation option and do not let Setup detect the hardware in your computer. Install only a mouse, a VGA video adapter, and a keyboard.
If the error still occurs, it is most likely caused by faulty hardware.
The VxD that is generating the error message can be any VxD--either a default
installed VxD or a third-party .386 driver being loaded from the System.ini
file. If you do not know which driver is causing the error message, create a
Bootlog.txt file and check to see which driver was the last driver initialized.
This is typically the driver causing the problem.
NOTE: You may also receive a Windows Protection error message when you restart Windows 98 after installing a program or making a configuration change to your computer.
You can also click Start, Run and type in MSCONFIG and click OK.
Now go to the Startup tab, note everything that is checked, then uncheck all and reboot.
If the problem does not appear, then the problem is in the startup program group. In this case, check one item at a time and reboot to identify which program is the offender.
Note also, that overheating the CPU or a hard drive with cluster\sector problems, or a hard drive that has a heat problem, will also cause this problem.
Dennis
ASKER
HiYa Dennis !
This time I know exactly what you think I should do ... and I have sent away for an application to M.I.T. for the Spring enrollment :-)
Until then, I will try each of your suggestions this week and get back to you with a yea or nay on our success.
Thanks so much ... both of you ... for your efforts on my behalf.
Modell
This time I know exactly what you think I should do ... and I have sent away for an application to M.I.T. for the Spring enrollment :-)
Until then, I will try each of your suggestions this week and get back to you with a yea or nay on our success.
Thanks so much ... both of you ... for your efforts on my behalf.
Modell
Hi Modell and Dew,
I apologize for breaking protocol in this forum and "answering" your message instead of "commenting" on it.
I do however stand by what I said. The steps I gave you were actually the solution to the problem. The steps that Dew has given you are provided in a language that I think should be called "microsoft-ease". This is a language capable of defining a solution to a problem as a more complicated set of problems.
Dew, considering the number of points you have acumulated and the nature of your answer (which is valuable to a technician like me:) you obviously have a large number of boilerplate responses at your fingertips. But when people ask for help they generally want an answer not a series of potential problems.
I was wrong (though innocently) of marking the question as answered. But guess what, you are more wrong for posting such a convoluted bunch a gobbledegook as a comment. Please answer questions in simple english! We can all go the microshafts knowledge base and find an abundance of aswers just like yours that don't actually help to resolve the problem.
I found this forum by accident and frnakly dobt that I will visit it again after your "boierplate" lecture on ethics. Which I have seen attached to quite a number of messages. Goodbye to you Dew and good luck to you in getting your system working again Modell.
I apologize for breaking protocol in this forum and "answering" your message instead of "commenting" on it.
I do however stand by what I said. The steps I gave you were actually the solution to the problem. The steps that Dew has given you are provided in a language that I think should be called "microsoft-ease". This is a language capable of defining a solution to a problem as a more complicated set of problems.
Dew, considering the number of points you have acumulated and the nature of your answer (which is valuable to a technician like me:) you obviously have a large number of boilerplate responses at your fingertips. But when people ask for help they generally want an answer not a series of potential problems.
I was wrong (though innocently) of marking the question as answered. But guess what, you are more wrong for posting such a convoluted bunch a gobbledegook as a comment. Please answer questions in simple english! We can all go the microshafts knowledge base and find an abundance of aswers just like yours that don't actually help to resolve the problem.
I found this forum by accident and frnakly dobt that I will visit it again after your "boierplate" lecture on ethics. Which I have seen attached to quite a number of messages. Goodbye to you Dew and good luck to you in getting your system working again Modell.
ASKER
MindBlade ... puhleeeeeze, before you go ...
When I get to the screen that lets me choose to Log the Boot, the next boot is always fine. (Sometimes I think the computer knows what I am planning and goes out of its way to defeat me!)
The problem boot is ONLY when I first cold-boot ... in the morning. After that, any reboot either works perfectly or hangs on the black screen.
But you want me to get the information from the log of the second boot which doesn't usually have a problem.
Do I understand you correctly?
Thanks so much.
Modell
When I get to the screen that lets me choose to Log the Boot, the next boot is always fine. (Sometimes I think the computer knows what I am planning and goes out of its way to defeat me!)
The problem boot is ONLY when I first cold-boot ... in the morning. After that, any reboot either works perfectly or hangs on the black screen.
But you want me to get the information from the log of the second boot which doesn't usually have a problem.
Do I understand you correctly?
Thanks so much.
Modell
Modell, that's okay. We do get quite a few of the "ego inflated" that pass through this site. No one here will leave you hang.
When you next cold boot the machine, boot to the Win98 boot menu by touching the F8 key right after the memory post or hold the Ctrl key down. Once at the boot menu, choose to create a Bootlog file during the boot.
Once you are up and running, use word pad and open bootlog.txt, it will be in the root of your "C" drive. Now check it very carefully and look for any failures during the boot process.
When you next cold boot the machine, boot to the Win98 boot menu by touching the F8 key right after the memory post or hold the Ctrl key down. Once at the boot menu, choose to create a Bootlog file during the boot.
Once you are up and running, use word pad and open bootlog.txt, it will be in the root of your "C" drive. Now check it very carefully and look for any failures during the boot process.
ASKER
I will follow your instructions the next time I do a cold-boot. But, until then I thought you might like to see what the Bootlog.txt currently has listed as failures. Does any of this help?
[000AF20C] Loading Vxd = ndis2sup.vxd
[000AF20D] LoadFailed = ndis2sup.vxd
[000AF24A] DEVICEINIT = MTRR
[000AF24A] DEVICEINITFAILED = MTRR
[000AF341] INITCOMPLETE = SIS530V
[000AF341] INITCOMPLETEFAILED = SIS530V
[000AF346] INITCOMPLETE = SDVXD
[000AF346] INITCOMPLETEFAILED = SDVXD
LoadStart = Bern Cond.ttf
LoadFail = Bern Cond.ttf Failure code is 0002
LoadStart = C:\WINDOWS\fonts\dummy.lyt
LoadFail = C:\WINDOWS\fonts\dummy.lyt
[000AF20C] Loading Vxd = ndis2sup.vxd
[000AF20D] LoadFailed = ndis2sup.vxd
[000AF24A] DEVICEINIT = MTRR
[000AF24A] DEVICEINITFAILED = MTRR
[000AF341] INITCOMPLETE = SIS530V
[000AF341] INITCOMPLETEFAILED = SIS530V
[000AF346] INITCOMPLETE = SDVXD
[000AF346] INITCOMPLETEFAILED = SDVXD
LoadStart = Bern Cond.ttf
LoadFail = Bern Cond.ttf Failure code is 0002
LoadStart = C:\WINDOWS\fonts\dummy.lyt
LoadFail = C:\WINDOWS\fonts\dummy.lyt
Okay, let's walk you through some of the items you just posted.
[000AF20C] Loading Vxd = ndis2sup.vxd
[000AF20D] LoadFailed = ndis2sup.vxd
**This is a normal failure. This is a virtual device driver for novell networking. It looks for any Novell related devices, and upon not finding any, goes to a fail.
[000AF24A] DEVICEINIT = MTRR
[000AF24A] DEVICEINITFAILED = MTRR
**This failure is also normal. MTRR stands for Memory Type Range Registers and is used for memory handling. Only directX 6.0 uses it and only on a limited basis.
[000AF341] INITCOMPLETE = SIS530V
[000AF341] INITCOMPLETEFAILED = SIS530V
**This is a sound device driver that is failing. What type of sound card do you use?
[000AF346] INITCOMPLETE = SDVXD
[000AF346] INITCOMPLETEFAILED = SDVXD
**This belongs to your sound card as well.
LoadStart = Bern Cond.ttf
LoadFail = Bern Cond.ttf Failure code is 0002
LoadStart = C:\WINDOWS\fonts\dummy.lyt
LoadFail = C:\WINDOWS\fonts\dummy.lyt
**These last two are bad fonts. Use find, files and folders and delete these two fonts from you system.
[000AF20C] Loading Vxd = ndis2sup.vxd
[000AF20D] LoadFailed = ndis2sup.vxd
**This is a normal failure. This is a virtual device driver for novell networking. It looks for any Novell related devices, and upon not finding any, goes to a fail.
[000AF24A] DEVICEINIT = MTRR
[000AF24A] DEVICEINITFAILED = MTRR
**This failure is also normal. MTRR stands for Memory Type Range Registers and is used for memory handling. Only directX 6.0 uses it and only on a limited basis.
[000AF341] INITCOMPLETE = SIS530V
[000AF341] INITCOMPLETEFAILED = SIS530V
**This is a sound device driver that is failing. What type of sound card do you use?
[000AF346] INITCOMPLETE = SDVXD
[000AF346] INITCOMPLETEFAILED = SDVXD
**This belongs to your sound card as well.
LoadStart = Bern Cond.ttf
LoadFail = Bern Cond.ttf Failure code is 0002
LoadStart = C:\WINDOWS\fonts\dummy.lyt
LoadFail = C:\WINDOWS\fonts\dummy.lyt
**These last two are bad fonts. Use find, files and folders and delete these two fonts from you system.
It appears that you are new to this site, and with that welcome! There are some issues though that I would like to make you aware of. The protocol (albeit unwritten) that is observed here by the techs is that suggestions, best guesses and the like be posted as comments, thereby leaving the question open for review by other techs. Answers are only posted when there is certainty that it will resolve the problem or the questioner requests it. Your cooperation would be appreciated.
Dennis