Crashing to blue screen of death/Page_Fault errors

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Within the last little while, I've been getting fairly frequent crashes to a
blue screen telling me I have a PAGE_FAULT_IN_NONPAGED_AREA (almost exactly
the problem outlined here: http://support.microsoft.com/?kbid=817197). This
occured soon after I had been forced to do a force-restart which corrupted my
user profile. I had not installed any hardware or software that might have
had anything to do with it, nor does the fix outlined on the webpage above
have any use for me (since I have no Lexar items, hence no Lexar drivers).

Currently, I have deleted the user profile via User Accounts in my Control
Panel. However, it appears as though the bulk of it remains (when I go to
Explorer -> Documents And Settings) where the profile name and files remain.
I figure I shouldn't go just arbitrarily deleting it since I have no idea if
that would make things better or worse (and it contains about 300 Megs...
mostly in a Local Settings folder... I have no idea if any of it's critical
or useful stuff).

A further clue: Though the majority of these crashes occur at random times
(often when I'm not physically at the computer and have left it alone for an
extended period of time and it's gone into sleep mode), I am able to crash it
when I run Microsoft Baseline Security Analyzer 2.0 (usually when it's about
2/3 of the way through the scan). I'm not sure if that will help narrow the
search down a bit.

A friend of mine who's a little more computer-savvy than I am emailed me
back this response: "Page faults typically indicate memory errors. Either you
have corrupted files that are writting over each other in memory, or your
memory sticks are loose in their sockets or going bad."
I have a hunch it's the first, the corrupted files writing over one another.
How would I go about tracking them down and fixing them?

Thanks.
 
Juko

Please post the exact text of the Stop message.

I suggest you Disable automatic restart on system failure. This should
help by allowing time to write down the STOP code properly. Right click
on the My Computer icon on the Desktop and select Properties, Advanced,
StartUp and Recovery, System Failure and uncheck box before
Automatically Restart.

There will also be Error Reports in Event Viewer. Please post copies.

You can access Event Viewer by selecting Start, Administrative Tools,
Event Viewer.
When researching the meaning of the error, information regarding Event
ID, Source
and Description are important.

HOW TO: View and Manage Event Logs in Event Viewer in Windows XP
http://support.microsoft.com/default.aspx?scid=kb;en-us;308427&Product=winxp

A tip for posting copies of Error Reports! Run Event Viewer and double
click on the
error you want to copy. In the window, which appears is a button
resembling two
pages. Double click the button and close Event Viewer. Now start your
message
(email) and do a paste into the body of the message. This will paste the
info from the
Event Viewer Error Report complete with links into the message. Make
sure this is
the first paste after exiting from Event Viewer.

--


Hope this helps.

Gerry
~~~~~~~~~~~~~~~~~~~~~~~~
FCA

Using invalid email address

Stourport, Worcs, England
Enquire, plan and execute.
~~~~~~~~~~~~~~~~~~~~~~~~
Please tell the newsgroup how any
suggested solution worked for you.



~~~~~~~~~~~~~~~~~~~~~~~~
 
Hello

Okay, the exact text of the blue screen is as follows:

The text is as follows:

"A problem has been detected and Windows has been shut down to prevent
damage to your computer.

PAGE_FAULT_IN_NONPAGED_AREA

If this is the first time you've seen this Stop error screen, restart your
computer. If this screen appears again, follow these steps:
Check to make sure any new hardware or software is properly installed. If
this is a new installation, ask your hardware or software manufacturer for
any Windows updates you might need.
If problems continue, disable or remove any newly installed hardware or
software. Disable BIOS memory options such as caching or shadowing. If you
need to use Safe Mode to remove or disable components, restart yourcomputer,
press F8 to select Advanced Startup Options, and then select Safe Mode.

Technical Information
*** STOP: 0x00000050 (0xBDE6ECE4,0x00000001,0x8065E5D8,0x00000002)
Beginning dump of physical memory
Physical memory dump complete.
Contact your system administrator or technical support group for further
assistance."

The numbers and letters in the STOP code seem to change each time it
crashes. When I crashed my computer this time and I opened up Event Viewer
there are a couple events that occur within a couple seconds of the crash.
I'm guessing the last one is the important one. They follow chronologically
in order:

1)
Event Type: Information
Event Source: EventLog
Event Category: None
Event ID: 6005
Date: 09/11/2005
Time: 12:29:46 PM
User: N/A
Computer: COREY
Description:
The Event log service was started.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

2)
Event Type: Information
Event Source: EventLog
Event Category: None
Event ID: 6009
Date: 09/11/2005
Time: 12:29:46 PM
User: N/A
Computer: COREY
Description:
Microsoft (R) Windows (R) 5.01. 2600 Service Pack 2 Multiprocessor Free.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


3)
Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 09/11/2005
Time: 12:29:49 PM
User: N/A
Computer: COREY
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x10000050
(0xcea6ece4, 0x00000001, 0x8065e5d8, 0x00000000). A dump was saved in:
C:\WINDOWS\Minidump\Mini110905-01.dmp.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.



When I try the weblinks provided, the first gives me a simple description of
what the even log does. The next two links read as unavailable. This
particular crash was forced by me by running the Microsoft Baseline Analyzer
2.0 (since I didn't want to wait around for the computer to crash on its own)

The latest actual error type I can find contains this text:

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 31/10/2005
Time: 4:42:09 PM
User: N/A
Computer: COREY
Description:
Error code 10000050, parameter1 d8fb8cc5, parameter2 00000001, parameter3
8065e5d8, parameter4 00000000.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 31 30 30 30 30 30 35 1000005
0020: 30 20 20 50 61 72 61 6d 0 Param
0028: 65 74 65 72 73 20 64 38 eters d8
0030: 66 62 38 63 63 35 2c 20 fb8cc5,
0038: 30 30 30 30 30 30 30 31 00000001
0040: 2c 20 38 30 36 35 65 35 , 8065e5
0048: 64 38 2c 20 30 30 30 30 d8, 0000
0050: 30 30 30 30 0000

Hopefully all this will help a bit.

Thanks.
 
Juko

What was the last change you made to your system hardware and when was
it made?


--


Hope this helps.

Gerry
~~~~~~~~~~~~~~~~~~~~~~~~
FCA

Using invalid email address

Stourport, Worcs, England
Enquire, plan and execute.
~~~~~~~~~~~~~~~~~~~~~~~~
Please tell the newsgroup how any
suggested solution worked for you.



~~~~~~~~~~~~~~~~~~~~~~~~
 
Back
Top