Ticket ID: 5390 Creation Date: 4/24/2007 10:57 PM Product: SiteKiosk Classic Windows Attachment: -
TicketType: Support Request Version: 6.2.51 Language: English
Views: 41485 Last Modification Date: 4/26/2007 9:37 AM Platform: Windows XP Home
Level: Closed IE: 6.0
Bug Status: Fixed User account: SiteKiosk Restricted User Bug Frequency: On every start

Support Request: Apple Intel based iMac crashes when restarted using replace system shell

Reproduction

Intel based iMac running Windows XP Home using BootCamp 1.2. Either use AutoStart or Customized replacing the System Shell and upon reboot the PC Bluescreens with a generic PAGE_FAULT_IN_NONPAGED_AREA . If the system shell is not replaced, reboots and starts in the limited user account with no problems.

Description

Intel based iMac running Windows XP Home using BootCamp 1.2. Either use AutoStart or Customized replacing the System Shell and upon reboot the PC Bluescreens with a generic PAGE_FAULT_IN_NONPAGED_AREA . If the system shell is not replaced, reboots and starts in the limited user account with no problems.

Answer: (1)
Re: Apple Intel based iMac crashes when restarted using replace system shell 4/25/2007 11:58 AM
Hello,

it seems that there is something wrong with your Windows configuration or maybe the SiteKiosk driver for the keyboard lock during system start-up is not compatible with your iMac hardware.
Running SiteKiosk with Windows on an iMac is not a tested or supported system environment.

-->Apple: http://www.apple.com/macosx/bootcamp/
Using Windows on a Mac
Mac hardware operates differently from PCs, and this public beta does not support all features of the Mac in Windows. http://docs.info.apple.com/article.html?artnum=303572

Microsoft about PAGE_FAULT_IN_NONPAGED_AREA:
This Stop message occurs when requested data is not found in memory. The system generates a fault, which normally indicates that the system looks for data in the paging file. In this circumstance, however, the missing data is identified as being located within an area of memory that cannot be paged out to disk. The system faults, but cannot find, the data and is unable to recover.
Faulty hardware, a buggy system service, antivirus software, and a corrupted NTFS volume can all generate this type of error.
http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/w2000Msgs/6093.mspx?mfr=true
http://support.microsoft.com/kb/817197/en-us

Regards,
Michael Olbrich
My Account
Login
Language (Tickets):