Microsoft Nashville build 999 NTKERN failure on VPC.

[Zacchi4k]

Hi, I have Microsoft Nashville build 999 installed on Virtual PC 2007.
I have a big problem: after the last restart of the setup, i get an NTKERN protection error and I cannot startup Nashville.
What can I do?

[x010]

I think that you have too much RAM(>512 MB).
Reduce it to something like 64-200 MB.

[Zacchi4k]

I think that you have too much RAM(>512 MB).
Reduce it to something like 64-200 MB.

Hi,
that's not the problem.
I was using 32 MB of RAM, I also tried with 88MB but nothing.

[Overdoze]

See this.

[Zacchi4k]

See this.

It doesn't work
Stupid s

[DragonExagon]

Disable Hardware Acceleration

[x010]

See this.

It doesn't work
Stupid s

Can you post the specs of your host PC and guest VM?

[Zacchi4k]

Disable Hardware Acceleration

My processor doesn't support it.

Can you post the specs of your host PC and guest VM?

I have a Lenovo ThinkPad R500 with Windows 8.1 Pro Update 1 32 bit
I'm reporting the details from Speccy:
CPU:
Intel Mobile Core 2 Duo T5670
Core 2
Thread 2
Name Intel Mobile Core 2 Duo T5670
Codename Merom
Package Socket P (478)
Tecnologia 65nm
Details Intel Core2 Duo CPU T5670 @ 1.80GHz
Family 6
Ext Family 6
Model F
Ext Model F
Stepping D
Revisione M0
Instructions MMX, SSE, SSE2, SSE3, SSSE3, Intel 64, NX
Virtualizzazione Not supported
Hypertreading Not supported
Bus speed Around 198 MHz
Valued Bus speed Around 790 MHz
Stock core speed 1800 MHz
Stock bus speed 200 MHz
Medium temperature 67 °C

Cache
L1 Data chace size 2 x 32 KByte
L1 Instructions chace size 2 x 32 KByte
L2 Unified chace size 2048 KByte

1944 MByte DDR3 RAM



I'm using a modded version of Virtual PC 2007 to work on Windows 8.
I'm using 32 MB of RAM and a 2048 MB VHD

[x010]

Quite strange. This does not happen to me with VPC 2007(It's a Merom core - T7200 dual core @ 2GHz).. and your processor doesn't seem to have anything odd.
Try to change the affinity of the program. To do so , open Task Manager , go to the Defaults tab , look for the VPC process , right click and select only 1 core(instead of the default 2).

[Zacchi4k]

Quite strange. This does not happen to me with VPC 2007(It's a Merom core - T7200 dual core @ 2GHz).. and your processor doesn't seem to have anything odd.
Try to change the affinity of the program. To do so , open Task Manager , go to the Defaults tab , look for the VPC process , right click and select only 1 core(instead of the default 2).

Nothing ç.ç

[Zacchi4k]

Also, I've noticed that in the Virtualization tab it says that's not supported, but there's the tick.

[TheCollector1988]

try extracting ntkern.vxd from the installation cabinets (.cab format) and patch it by using rloew's fix. and put it back in system/vmm32.

[LoneCrusader]

As TheCollector1988 said use rloew's fix for this issue. Read this thread:Fixing The CPU Speed Limit in Windows 95, 98 and their Betas

[x010]

As TheCollector1988 said use rloew's fix for this issue. Read this thread:Fixing The CPU Speed Limit in Windows 95, 98 and their Betas

That won't have an effect as his clock speed is only 1.8 GHz.
Have you reinstalled Nashville?
Can you try using VirtualBox or VPC 2004(use the same modification)?

[Battler]

- x010: He should still try patching the files though. AFAIK, under some conditions, it's triggered for any speed above 600 MHz too.

[Overdoze]

- x010: He should still try patching the files though. AFAIK, under some conditions, it's triggered for any speed above 600 MHz too.

First barrier is at 350MHz, the second is at 2.1GHz.

[x010]

- x010: He should still try patching the files though. AFAIK, under some conditions, it's triggered for any speed above 600 MHz too.

First barrier is at 350MHz, the second is at 2.1GHz.

What is the first barrier about? How does it not happen for me?

[Overdoze]

Windows 95 has two specific errors when dealing with processors
with speeds higher than 350 MHz. With a little patience however,
both of these errors are fixable.


The first error occurs with processors greater than 350 MHz.
Microsoft released a patch for this error, AMDK6UPD.EXE. This
patch IS NOT just for AMD processors. It will work for Intel
Pentium 4 processors as well. The problem with Microsoft's patch
is that it must be run from within Windows. When your system
encounters this error, you will not be able to boot into Windows.
This error will be displayed on the first reboot during the
installation process.

[startmenus]

If it doesn't work with VirtualPC， try another VM.