Blue Screen 0x00000050: "PAGE_FAULT_IN_NONPAGED_AREA"

original title: Blue Screen: "PAGE_FAULT_IN_NONPAGED_AREA" on Vista

Hello Microsoft answers,

I have recently gotten a Blue screen message "STOP: 0x00000050 PAGE_FAULT_IN_NONPAGED_AREA" on my Windows Vista home premium SP2 .

I've all ready done a Startup Repair, and had no affect.

There is a hotfix for this from KB Article Number(s): 939720, only seems that there is a great risk if something is not right.

I was wondering, if i were to re-install SP2 and have a chance at fixing this error. Would it be worth it to re-install SP2 or it won't do a thing, and I should just go ahead and do the hotfix?

Any help would be fantastic! =]

-eplalo

Answer
Answer

Hi,

Do you have ZoneAlarm or any 3rd party firewall installed? If so that could be the cause.
Other antivirus/security programs could be at least partially responsible.

This Hotfix "Might" apply however do not use unless you are fairly sure.

Using two Windows Filtering Platform (WFP) drivers causes a computer to crash when the
computer is running Windows Vista, Windows 7, or Windows Server 2008
http://support.microsoft.com/kb/979278

------------------------------------------------------------------------------------------------------

To see how to use BlueScreenView and MyEventViewer to troubleshoot Bluescreens see the methods
indicated in this thread - top 3 replies.

http://social.answers.microsoft.com/Forums/en-US/vistarepair/thread/3deab2fa-4000-4136-8c78-a3d22b1db009

-------------------------------------------------------------

You can try Safe Mode to try to fix this - repeatedly tap F8 as you boot.

Have you added any hardware lately? Have you updated any driver just before these started? (Check
Control Panel - Windows Updates to see if any drivers were updated there about the time this started)
Main likely culprits are Video driver, other major drivers, memory, and antivirus/antispyware/security
products could be at fault as well as drive issues.

Use the troubleshooter below and refer to the next message for drivers and memory when you get to
those sections and then return back to the troubleshooter as needed.


BCCode: 50     0x00000050

Cause

The BCCode 50 usually occurs after the installation of faulty hardware or in the event of failure of installed
hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM).

Another common cause is the installation of a faulty system service.

Antivirus software can also trigger this error, as can a corrupted NTFS volume.

Resolving the Problem

Resolving a faulty hardware problem: If hardware has been added to the system recently, remove it to see
if the error recurs. If existing hardware has failed, remove or replace the faulty component. You should run
hardware diagnostics supplied by the system manufacturer. For details on these procedures, see the owner's
manual for your computer.

Resolving a faulty system service problem: Disable the service and confirm that this resolves the error. If so,
contact the manufacturer of the system service about a possible update. If the error occurs during system
startup, restart your computer, and press F8 at the character-mode menu that displays the operating system
choices. At the resulting Windows Advanced Options menu, choose theLast Known Good Configuration
option. This option is most effective when only one driver or service is added at a time.

Resolving an antivirus software problem: Disable the program and confirm that this resolves the error. If it
does, contact the manufacturer of the program about a possible update.

Resolving a corrupted NTFS volume problem: Run Chkdsk /f /r to detect and repair disk errors. You must
restart the system before the disk scan begins on a system partition. If the hard disk is SCSI, check for
problems between the SCSI controller and the disk.

Finally, check the System Log in Event Viewer for additional error messages that might help pinpoint the
device or driver that is causing the error. Disabling memory caching of the BIOS might also resolve it.

BCCode: 50      0x00000050  <-- read this

http://www.faultwire.com/solutions-fatal_error/PAGE-FAULT-IN-NONPAGED-AREA-0x00000050-*1095.html?order=votes

------------------------------------------------------------------------------------------------------------------------

Look in the Event Viewer to see if anything is reported about those.
http://www.computerperformance.co.uk/vista/vista_event_viewer.htm

MyEventViewer - Free - a simple alternative to the standard event viewer of Windows.
TIP - Options - Advanced Filter allows you to see a time frame instead of the whole file.
http://www.nirsoft.net/utils/my_event_viewer.html

-------------------------------------------------------------------------

Here are some methods to possibly fix the blue screen issue. If you could give the Blue Screen info that would
help. Such as the BCC and the other 4 entries on the lower left. And any other error information such as STOP
codes and info such as IRQL_NOT_LESS_OR_EQUAL or PAGE_FAULT_IN_NONPAGED_AREA and similar messages.

As examples :

BCCode: 116
BCP1: 87BC9510
BCP2: 8C013D80
BCP3: 00000000
BCP4: 00000002

or in this format :

Stop: 0x00000000 (oxoooooooo oxoooooooo oxooooooooo oxoooooooo)
tcpip.sys - Address 0x00000000 base at 0x000000000 DateStamp 0x000000000


This is an excellent tool for posting Blue Screen Error Information

BlueScreenView scans all your minidump files created during 'blue screen of death' crashes, and displays the
information about all crashes in one table - Free
http://www.nirsoft.net/utils/blue_screen_view.html


Many BlueScreens are caused by old or corrupted drivers, especially video drivers however there are other causes.

You can do these in Safe Mode if needed or from Command Prompt from Vista DVD or Recovery Options if your
system has that installed by the maker.

This tells you how to access the System Recovery Options and/or from a Vista DVD
http://windowshelp.microsoft.com/Windows/en-US/Help/326b756b-1601-435e-99d0-1585439470351033.mspx

You can try a System Restore back to a point before the problem started if there is one.

How to Do a System Restore in Vista
http://www.vistax64.com/tutorials/76905-system-restore-how.html

-------------------------------------------------------------------------

Start - type this in Search Box ->  COMMAND   find at top and RIGHT CLICK  -  RUN AS ADMIN

Enter this at the prompt - sfc /scannow

How to analyze the log file entries that the Microsoft Windows Resource Checker (SFC.exe) program
generates in Windows Vista cbs.log
http://support.microsoft.com/kb/928228


The log might give you the answer if there was a corrupted driver. (Does not tell all the possible driver issues).

Also run CheckDisk so we can rule out corruption as much as possible.
How to Run Check Disk at Startup in Vista
http://www.vistax64.com/tutorials/67612-check-disk-chkdsk.html


-------------------------------------------------------------------------

Often updating drivers will help, usually Video, Sound, Network Card  (NIC), WiFi, 3rd party keyboard and
mouse, as well as other major device drivers.

Manually look at manufacturer's sites for drivers - and Device Maker's sites.
http://pcsupport.about.com/od/driverssupport/ht/driverdlmfgr.htm

How to Install a Device Driver in Vista Device Manager
http://www.vistax64.com/tutorials/193584-device-manager-install-driver.html

How To Disable Automatic Driver Installation In Windows Vista - Drivers
http://www.addictivetips.com/windows-tips/how-to-disable-automatic-driver-installation-in-windows-vista/
http://technet.microsoft.com/en-us/library/cc730606(WS.10).aspx

-------------------------------------------------------------------------

How to fix BlueScreen (STOP) errors that cause Windows Vista to shut down or restart unexpectedly
http://support.microsoft.com/kb/958233

Troubleshooting Vista Blue Screen, STOP Errors
http://www.chicagotech.net/vista/vistabluescreen.htm

Understanding and Decoding BSOD (blue screen of death) Messages
http://www.taranfx.com/blog/?p=692

Windows - Troubleshooting Blue Screen Errors
http://kb.wisc.edu/page.php?id=7033

-------------------------------------------------------------------------

In some cases this might be required.

StartUp Repair from Recovery Options or Vista disk

How to do a Startup Repair
http://www.vistax64.com/tutorials/91467-startup-repair.html

This tells you how to access the System Recovery Options and/or from a Vista DVD
http://windowshelp.microsoft.com/Windows/en-US/Help/326b756b-1601-435e-99d0-1585439470351033.mspx

Hope this helps.


Rob Brown - MS MVP - Windows Desktop Experience : Bicycle - Mark Twain said it right.
Rob Brown - past Microsoft MVP - Windows Insider MVP 2016 - 2021
Microsoft MVP Windows and Devices for IT 2009 - 2020

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Answer
Answer

I check a few dumps:

you get a DRIVER_CORRUPTED_EXPOOL( pool corruption ), BUGCODE_USB_DRIVER ( USBBUGCODE_BAD_SIGNATURE An Internal data structure (object) has been corrupted), CRITICAL_OBJECT_TERMINATION -  ExceptionCode: c0000005 (Access violation) andPAGE_FAULT_IN_NONPAGED_AREA.


So it looks like your RAM is damaged. Please download memtest86+ [1], burn a new bootable CD (use a CD-RW if possible) from the ISO (download and use ImgBurn [2] to do this), reboot your PC and scan your RAM 4-5hours for errors.

André

[1] http://www.memtest.org/download/4.10/memtest86+-4.10.iso.zip
[2] http://www.imgburn.com/index.php?act=download


"A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/

11 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

 
 

Question Info


Last updated February 18, 2022 Views 88,651 Applies to: