"Page fault in a non-paged area" BSOD. NOTE there are no 'viri' on this machine as it has NEVER been on the net for email for any other reason. Here's the deal... P4 2.0gig 512kb CPU 478sckt ALL are NTFS partitions... 1st physical drive = 20 gig IBM drive w/2 10gig partitions; 2nd physical disk = 20 gigs and 2 10gig parts and both installed on primary controller as a master/slave drive relationship. We GHOSTED the C <system> partition ( of disk 1 ) to part 1 of disk 2 and rebooted to the desktop from the C of drive 1 part 1 with no trouble and left the 2nd drive totally connected internally as slave on the primary controller. [Drive assignments are c,d (1st drive)E=cdrom f=2nd drive 1st part,g2nd drive 2nd part.] Now the infamous intermittent 'BSOD' shows up now and again claiming "page fault in a non-paged area" when the server gets busy. My question is: is this error message related to this second drive being left installed with a system ghosted partition on it and XP PRO is trying to read and/or write to it as if it were just free space? I can see where this convience of setting up a system like this would create problems merely because it would be so easy to restore a corrupted primary disk... ( you'd boot machine, ghost back disk 2 to disk 1 and off you go assuming the primary disk isn't toasted) More details - the machine also has just been upgraded to 1 gig of RAM from 750MEGs and I am somewhat suspect of the new memory stick too: PC2700 Kingston 500Meg So, it's a nuisance but I have decided to seperate the 2nd drive form the system and run that way ... any suggestions would be appreciated and would provide some more insight to the OS of XPPRO. <<<We havent run the server yet under load with the second disk seperated yet>>>> Additionally - is the service pack worth it or just a nightmare in disguise? Thanks in advance !

Your suspicion about the memory is probably correct.

To continue... We left the memory stick installed for now and we seperated the internal connections from the second installed 'back up ' disk, and since then haven't had a BSOD error or 'page fault in a non-paged area'. I find this whole deal very interesting: why would the XPPro OS attempt to use the second disk for a swap file (assuming that is happening)when there is at least 4 gigs on the primary disk? Totally craps me out to think the OS is written to scatter working files all across the machine just to indiscriminatly grab free resources ...but then again..it's Windows. Any comments welcome...