event log faultbucket error message and BSOD 0x00000050

  • Thread starter Thread starter Fran
  • Start date Start date
F

Fran

I got the BSOD stop message 0x00000050 page fault in non-paged area - when I
clicked on link, MS said "problem with Device Driver" uninstall new hardware
and software.

Then I ran event viewer and saw these 2 error messages:
1) under Application:
Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1001
Date: 10/30/2008
Time: 7:47:59 AM

Description:
Fault bucket 945974882.
Data:
0000: 42 75 63 6b 65 74 3a 20 Bucket:
0008: 39 34 35 39 37 34 38 38 94597488
0010: 32 0d 0a 2..

2) under System:
Event ID: 1003
Date: 10/30/2008
Time: 8:51:31 AM

Description:
Error code 10000050, parameter1 e6498000, parameter2 00000000, parameter3
83a053de, parameter4 00000001.
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 65 36 eters e6
0030: 34 39 38 30 30 30 2c 20 498000,
0038: 30 30 30 30 30 30 30 30 00000000
0040: 2c 20 38 33 61 30 35 33 , 83a053
0048: 64 65 2c 20 30 30 30 30 de, 0000
0050: 30 30 30 31 0001

recent software installations were Norton security suite 2009 and FF 3.0.
No new hardware. I use Win XP, SP3

Thanks for any help
Fran
 
OK, I ran chkdsk. Then I ran devmgmt.msc - no bangs or exclamation points.

I want to test the memory but am having a problem.
I downloaded windows memory diagnostic file mtinst.exe and then burned the
ISO file onto a CD using a converter program.
Instructions say to boot from that CD but computer booted into win XP the
regular way so can't run the memory program
What do I need to do to run the mtinst.exe file - or is there another memory
tester you would recommend instead of that one.
Thanks for your help
Fran
 
Fran

Does the error occur before or after the computer boots to the Desktop?
Does the error occur if you boot into safe mode?

Background information on Stop Error message
http://msdn2.microsoft.com/en-us/library/ms793437.aspx

0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
(Click to consult the online MSDN article.)
Requested data was not in memory. An invalid system memory address was
referenced. Defective memory (including main memory, L2 RAM cache, video
RAM) or incompatible software (including remote control and antivirus
software) might cause this Stop message, as may other hardware problems
(e.g., incorrect SCSI termination or a flawed PCI card).
Source: http://aumha.org/a/stop.htm

Have you tried Last Known Good Configuration?
A description of the Safe Mode Boot options in Windows XP
http://support.microsoft.com/kb/315222/en-us

Please post the complete Stop Error ( BSOD) Report.

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,
Start-Up and Recovery, System Failure and uncheck box before
Automatically Restart.

Do not re-enable automatic restart on system failure until you have
resolved the problem. Check for variants of the Stop Error message.

An alternative is to keep pressing the F8 key during Start-Up and select
option - Disable automatic restart on system failure.

If you are using a wireless keyboard and the F8 key does not work
substitute a wired keyboard and mouse for this exercise only.

--



Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
 
Hello,

The following is from my web site -

verifier - Have you had a blue screen of death experience? Not sure
what's causing it? Well, there is a possibility that you have a problem
with a driver file. To find out, boot into Safe Mode, click Start, Run,
and type in verifier, then hit enter. You will get a dialog with some
options. Select the option for "test all drivers" and OK out of the dialog.

Now reboot and try to go into Normal Mode. If your blue screen before
was caused by a driver problem you should get another blue screen now
with the culprit driver being identified on it. Go back to safe mode and
un-install the driver causing the problem, and if it's for needed
hardware, go to the manufacturers web site and look for an updated
driver to install.

That should fix you up.

Later, Ray Parrish
 
Back
Top