NO_PAGES_AVAILABLE    |    Repair Windows Error 0x0000004D    |    Fix Error Code 0x0000004D


STOP 0x0000004D : NO_PAGES_AVAILABLE

STOP Errors are usually the result of a hardware malfunction or device driver issue. It is also possible to receive a Blue Screen Error due to bad system memory, malfunctioning power supply, components overheating, or hardware overclocked beyond its specification. In older versions of the Windows OS you may also receive Blue Screen Errors due to incompatible DLL files.

Since the only option when receiving a Blue Screen Error is to reboot, any unsaved data is lost. With that in mind, it is very important to eliminate these errors to protect your data.

Basic Troubleshooting

Troubleshooting STOP Errors can be a difficult and time consuming process. Try these basic steps to fix your own Blue Scree Error. We hope it will help you avoid an expensive service call and provide a rewarding experience of solving the problem on your own.

Advanced Troubleshooting

The following details are for advanced users. These are provided for your convenience and may help those with advanced knowledge discover the root cause of their STOP Error.


Stop 0x4D: NO_PAGES_AVAILABLE

The NO_PAGES_AVAILABLE stop error code has a value of 0x0000004D. This indicates that no free pages are available to continue operations.

Parameters

The following parameters are displayed on the blue screen.

ParameterDescription
1The total number of dirty pages
2The number of dirty pages destined for the page file
3Windows XP and Windows 2000: The size of the nonpaged pool available at the time the stop error code occurred

Windows Server 2003 and later: Reserved

4Windows 2000: The number of transition pages that are currently stranded

Windows XP and later: The most recent modified write error status.

Cause

To see general memory statistics, use the !vm 3 debugger extension.

This stop error code can occur for any of the following reasons:

  • A driver has blocked, deadlocking the modified or mapped page writers. Examples of this include mutex deadlocks or accesses to paged out memory in file system drivers or filter drivers. This indicates a driver bug.

    If Parameter 1 or Parameter 2 is large, then this is a possibility. Use the !vm 3 debugger extension.

  • A storage driver is not processing requests. Examples of this are stranded queues and non-responding drives. This indicates a driver bug.

    If Parameter 1 or Parameter 2 is large, then this is a possibility. Use the !vm 8 debugger extension, followed by the !process 0 7 debugger extension.

  • A high-priority realtime thread has starved the balance set manager from trimming pages from the working set, or starved the modified page writer from writing them out. This indicates a bug in the component that created this thread.

    This situation is difficult to analyze. Try using the !ready debugger extension. Try also the !process 0 7 debugger extension to list all threads and see if any have accumulated excessive kernel time as well as what their current priorities are. Such processes may have blocked out the memory management threads from making pages available.

  • Windows XP and Windows 2000: Not enough pool is available for the storage stack to write out modified pages. This indicates a driver bug.

    If Parameter 3 is small, then this is a possibility. Use the !vm and !poolused 2 debugger extensions.

  • Windows 2000: All the processes have been trimmed to their minimums and all modified pages written, but still no memory is available. The freed memory must be stuck in transition pages with non-zero reference counts — thus they cannot be put on the freelist.

    A driver is neglecting to unlock the pages preventing the reference counts from going to zero which would free the pages. This may be due to transfers that never finish, causing the driver routines to run endlessly, or to other driver bugs.

    If Parameter 4 is large, then this is a possibility. But it is very hard to find the driver. Try the !process 0 1 debugger extension and look for any drivers that have a lot of locked pages.

If the problem cannot be found, then try booting with a kernel debugger attached from the beginning, and monitor the situation.

Helpful Tools

The following products are free to try. We have found them to be of the highest quality and value. They have been extremely useful in our own pc troubleshooting and maintainance and we highly recommend trying them out for yourself.


Anti-Malware Pro

With a lightning fast free scan and the largest authentic spyware detection database we have seen, Anti-Malware Pro finds and removes threats to your PC stability and security. Download Anti-Malware Pro


DriverFinder

DriverFinder will scan your system for driver and software updates. Its easy to use interface makes keeping your drivers updated quick and simple. They will even send you an email notification when new driver updates are available for your system! It doesn't get any more convenient than this. Download DriverFinder





Browse STOP Error Codes:





Is a STOP error code missing?

Help us to make errorDecoder.com the best resource we possibly can by submitting you very own STOP error code details. If you have detailed information on any STOP error code please let us know by visiting the following link.

Submit Error Details Form

Repair Windows Error 0x0000004D    |    NO_PAGES_AVAILABLE    |    Fix Error Code 0x0000004D