Windows Protection Error Windows 2000
The new bootlog will either stop at the file causing the error or the next file that is not reported in the new bootlog but is in the old bootlog. The cause of the error may not be apparent even though you may see the VXD name in the error message, thereby believing it is the causative factor of the error. Now comes the problem, building the new second production machine. In this article, I’ll explain what Windows protection errors are, and I’ll discuss some steps that you can take to resolve them. http://pubdimensions.com/windows-protection/windows-protection-error-45.php
Everything works fine until it finishes setup, but it when it tries to start Windows for the first time, it says, "While initializing device IOS: Windows protection error. So what causes these mysterious error messages?There are actually quite a few different things that can cause Windows protection errors. There is no software out there that can find your Windows Protection Error, it is something you need to find yourself. By using the process of elimination, you can determine which device is causing the problem.If the system boots in Safe Mode but won’t boot in normal mode, regardless of which drivers
If the problem is related to a conflict between a real-mode and a protected-mode driver, an operating system upgrade will correct the problem because Windows 2000 and XP don’t use real-mode If my operating system had been giving me a problem before the BSOD I would look at the file system, the Registry and CPU (possibly), unless it was hardware related, such Therefore, it must be a corrupted VXD file! Hence, Windows reports the VXD error, the one that is broken, the one that is trying to fit in the slot or memory address; as you see it "Windows Protection Error:
They have the same problem as Windows 95.The reason is mostly because they are based on Windows 95(and are alphas of Windows 98).Yes, they are. When restarting computer this message appears:"Windows protection error You need to restart your computer." It will not boot up further. They all reported lots of errors, and fixed them. Rebooted and turned everything back on in the BIOS and yes you guessed it, the BSOD.
When you do, you’ll see the printer’s properties sheet. Another similar one exists at speeds >2.1GHz. I've personally never encountered this error when installing Windows 98 FE/SE. _________________Deus damnaret eam! http://www.computing.net/answers/windows-95/win-95-windows-protection-error-after-setup/170738.html This problem can also occur when you start your computer in Safe mode.
Because the error does not present itself unless you use a 2.2GHz processor or greater.See the KB article."Windows protection error in NDIS with a CPU that is faster than 2.1 GHz"It This solution worked perfectly. I do not want to mislead you and tell you exactly how to fix one. To determine the culprit, reenable one device at a time, rebooting between each.
The further the builds are apart, the greater the possibility for further incompatibility. _________________Author of FIX95CPU - Run Windows 95 on >2.1GHz Processors!Author of XUSBSUPP - "NUSB for Windows 95!" Top Install the Windows. Top LoneCrusader Post subject: Re: Fix "NDIS Windows Protection Error" in Win98 & Memphis B Posted: Thu Apr 26, 2012 6:39 am Joined Thu Apr 05, 2012 You need to restart your computer Windows Legacy OS forum About This ForumCNET's Forum on Windows legacy operating systems, (XP, 2000/NT, ME, & Windows 95/98) is the best source for finding
Please refer to our CNET Forums policies for details. useful reference Off-Topic Tags How-tos Drivers Ask a Question Computing.NetForumsWindows 95/98Installation Solved Win 95: Windows protection error after setup Tags:Microsoft Windows 95windows 95setup N7I2S5 May 7, 2011 at 12:08:39 Specs: Windows 95 & I installed Memphis build 1351.Good tests!I have not had the opportunity to look into the NTKERN errors with early Beta builds. Top LoneCrusader Post subject: Re: Fix "NDIS Windows Protection Error" in Win98 & Memphis B Posted: Fri Apr 13, 2012 11:20 pm Joined Thu Apr 05, 2012
This applies a patch that fixes this error most of the time. _________________It's called a hustle, sweetheart. Each OS, Windows 98, 98SE, ME, NT4, 2 versions of 2000, 3 versions of 2003, 2 versions of XP, are installed to a different partition and can be booted to. Thank you for any help/solutions. my review here For those not in the know, a BSOD is the Blue Screen Of Death.
Report • Start a discussion Ask Your QuestionEnter more details...Thousands of users waiting to help!Ask now Weekly Poll Do you think Google Fiber has a strong future? Reboot the system normally and the system should function correctly. However, like the Virtual PC suggestion above, this is a workaround, not a fix.
Still, the BSOD was there on every boot.
Please refrain from making pointless posts, please. _________________James *~*~* BA Moderator | Alternate History writer"No plan survives first contact with the enemy."- von Moltke the Elder Top LoneCrusader Post subject: This will make a great Web Server, I will remove the sound card, modem, Network card, display adapter, floppy drive, CD-ROMs, and install a older display adaptor, a new SCSI Controller This will fix the problem. get redirected here The HotFix is the right way to fix it. _________________Author of FIX95CPU - Run Windows 95 on >2.1GHz Processors!Author of XUSBSUPP - "NUSB for Windows 95!" Top cantasan99 Post subject: