Move your bodies such that you are sitting on the edige of your chair (sofa,
whatever). Place you hands clasped together on back of you head and/or neck.
Bend over and place your head between your knees and kiss your ass goodbye.
No wait.
I think these instructions were the EVAC debrief I remember getting on the
way to Kuwait in a C-130... sorry.
Blue screens and Safe Modes are never good. Is disk space (and/or possibly
page file definition possible a problem? Page File is the way "virtual"
memory is created, making your system think it has more RAM than it does. It
"moves" memory to the Page File when it has to, so other programs can use the
now freed RAM memory. A Page Fault is name for this "paging out memory to a
file" is called.
Page File is defined in Control Panel, System\Advanced tab. Then Peformance
Options. You'll see a "Virtual Memory" section. Take a look, but don't change
anything unless you sure of what to change.
The actual file is on the root drive (C:\) and is hidden. Open a Command
Prompt, type "cd \", then "dir /a:h". Should see "pagefile.sys" file if
defined...
"kpasse" wrote:
> I performed today's current critical update to W2000. Download and
> installation were fine, then called for restart. When restarting, came to
> blue screen with Stop Error "Page Fault In Nonpaged Area". Instructions said
> to reboot, but returned to same page. Next instruction was to go to Safe
> Mode, but after F8 and Safe Mode selection, system returns to same blue
> screen. I can't get out of the loop. Is it safe to go to Last Known Good
> Configuration? Any ideas?
|