How to troubleshoot and diagnose this problem:
Start by doing a simple web search on "PAGE_FAULT_IN_NONPAGED_AREA" to
locate the following:
http://www.microsoft.com/resources/d...d_stp_ccgm.aspStop 0x00000050 or PAGE_FAULT_IN_NON_PAGED_AREA
The Stop 0x50 message indicates that requested data was not in memory. The
system generates an exception error when using a reference to an invalid
system memory address. Defective memory (including main memory, L2 RAM
cache, video RAM) or incompatible software (including remote control and
antivirus software) might cause Stop 0x50 messages.
Since this is coming from inside the Virtual Machine, a "hardware failure"
is either a bug in emulation or a real problem with your HW (that then
adversely affects the emulation).
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Scott Willeke" <scott...datadynamics.com> wrote in message
news:%23BXMPuftEHA.3972...TK2MSFTNGP15.phx.gbl...
Okay, I've spent many hours trying to get the final release of Virtual
Server to work on a brand new machine. Most recently I installed a brand
new full version (not msdn) of Windows Server 2003, applied all critical
updates from Windows Update and then installed the purchased final
release of the Virtual Server (boxed product) and we're installing on a
brand new machine. Everything appears to go smoothly up to this point.
Next, I tried to create a new virtual machine image for Windows Server
2003. I create one from scratch (using pretty much all default
settings), it boots up runs setup, goes all the way through setup until
it tires to reboot. Upon rebooting to continue setup, I get the blue
screen with the message "PAGE_FAULT_IN_NON_PAGED_AREA" in ntfs.sys
(0xCDCDCDA4, 0x00000000, 0xFC26158E, 0X00000000) before I can even login.
How can I troubleshoot and diagnose this problem?
-scott