NTKERN Windows Protection Error

April 8, 2012 at 11:12:37
Specs: Windows 95 4.10.999 (VPC), 1.6 GHz AMD Athlon (host), 64MB (given to guest VPC) / 512 MB
When I boot my Windows 95 Virtual PC, it usually after running autoexec.bat and in middle of the boot screen, displays this message:

"While initializing driver NTKERN
Windows protection error, you have to restart your computer"

And then hangs.

I can boot to safe mode. Also, I can boot into normal mode if I boot to safe mode first then change to normal mode. It only works once then, though.

Tried following things:
1. Other Virtual PC's work. It's not a RAM problem.
2. Replace the vmm32.vxd with a clean version from Win95 CABs.
3. Reinstall Windows 95. TWICE.
4. Running RegClean, absolutely no help.
5. Set memory down to 16 MB.

Still no help.

About the version: I'm not sure whether it has packs, OSRs or something, but the System dialog says 4.10.999. Strange enough, command.com says "Microsoft Nashville", so it's possible this is a some kind of beta version?

This problem is very annoying, and I have looked it from the Google for around three hours now. What could be the solution?

See More: NTKERN Windows Protection Error

Report •

April 8, 2012 at 13:17:01
Sounds like you do have an odd Beta version of Windows 95.

I have seen that particular error when running 95 on newer hardware whenever the last version of NTKERN.VXD is not installed.

While not written EXACTLY for this particular problem, my FIX95CPU update should correct this. Try installing it.

See here for detailed information:

See especially the "KNOWN ISSUES" section of the ReadMe for an error similar to what you are experiencing.

The ZIP contains bootable Floppy and CD images, use whichever is more convenient.

I would advise you to reinstall from scratch, you cannot simply replace VMM32.VXD with the one from the CABs. It is only a "starter" file that is compressed with several other VXD's during the first reboot of SETUP. They can be unique to each machine depending on certain factors during SETUP.

Report •

April 8, 2012 at 16:59:41
Note that vmm32.vxd from the CD is just a place holder and should not be used to replace vmm32 which was formed during install. The latter is unique to your system and depends on the installed drivers.

If you are still using the CD copy of vmm32.vxd then you ought to re-install W95 again before you take the issue further. It is a good idea to then keep a copy of the vmm32.vxd produced because if this ever gets into trouble it will save you having to re-install.

Always pop back and let us know the outcome - thanks

Report •

April 8, 2012 at 18:57:11
Keep in mind that FIX95CPU has its limits.

I've recently tested it on a Athlon XP 2200+ and FIX95CPU failed to prevent the Windows protection error.

Report •

Related Solutions

April 8, 2012 at 21:44:51

Please elaborate on this. This is the first report I've ever had wherein the problem was not solved or not found to be unrelated to FIX95CPU.

For example - in the 4th post of my thread at MSFN it is confirmed to work with an AMD Atlhon 64 4000+ @ 2.40 GHz.

Also, remember that you helped another member here install it on a system using the same processor that you listed - and it worked for him...

Report •

April 9, 2012 at 00:21:09
So it's third time for setup. It's a shame since I have already customized this system already.

After installing, @LoneCrusader I will try your patch.

Report •

April 9, 2012 at 01:45:15
After installing the patch, when I started my W95, a BSOD appeared:

"Invalid VxD dynamic link call from NTKERN(01) + 000086FE to device "VMM ", service 1A7.
Your WIndows configuration is invalid. Run the Windows Setup program again to correct this problem.

To continue running WIndows press Y or ENTER. To quit the current program press N. If you continue running Windows, your system may become unstable. Do you want to continue?

Press Y for Yes and N for No: Y"

What does this mean?

EDIT: When pressing Y, the protection error comes up again.

Report •

April 9, 2012 at 19:17:42
Eck... Not good.

Probably this means that the latest version of NTKERN for Windows 95 will not work with the Beta version that you are using.

Something is "mismatched" between NTKERN.VXD and VMM.VXD (which is already packed inside the "starter" VMM32.VXD).

If you're feeling brave, you could try extracting the last VMM.VXD for Windows 95 into your C:\WINDOWS\SYSTEM\VMM32\ folder and see if Windows will boot using this file along with the other new files from FIX95CPU.
(Last VMM.VXD for 95 is in this package)

Other than that, I don't know what else to tell you to try without actually having that Beta version to run tests on...

Report •

April 13, 2012 at 11:12:20

I just realized my error: FIX95CPU does not work on the original version of Windows 95.

It does work on later versions, however.

It's clear I was using the "A" version of 95 when I ran into my issue with FIX95CPU.

Sorry for the confusion!!!

Report •

April 16, 2012 at 05:23:12
I think I gave up, since I copied another Win95 VHD on top of this one, so I now have those two Win95's running fine.

Thanks for your help, anyway.

Report •

April 16, 2012 at 11:58:41
Thx for feedback anyhow.

Always pop back and let us know the outcome - thanks

Report •

April 22, 2012 at 00:49:12
@sdfox 7
Thanks for the clarification. At the time FIX95CPU was developed I did not have any copies of 95 RTM or 95A to test with. I had (and still get) reports that it did/does work on those versions, but I could not test it myself. I have now done so and encountered an error with 95 RTM. I don't know the cause or if there is a solution yet, but I plan to experiment further.

As Derek said thanks for reporting back. It might be possible to develop a solution for your Nashville Beta, but given that the official 95 HotFix files don't work, it would probably be a matter of trying to debug the error and backport code from the FIX95CPU files to Nashville files. A matter far over my head! :)

Report •

Ask Question