spacer spacer spacer
 
 
  arrow Description
  arrow Sample Screen
  arrow Key Facts
  arrow Solutions
  arrow Forum Help
  arrow Technical Details
  arrow Vendor Summary
  arrow Research this Issue
  help Solutions Help
 
 
box_image
RadarSync
Ensures you have the latest drivers and software updates to make your PC run better and safer.
 
  Partition Commander
Now it's easy for anyone to safely partition their hard drive! You can reclaim waste disk space, organize files, even add new OSes.
box_image  
 
 
box_image
PC Mover
Move applications, files and settings from one PC to another. Handles Windows upgrades too, even XP 32-bit to Windows 7 64-bit!
     
 
 
Fatal Error Solutions
     
 

MEMORY_MANAGEMENT

STOP: 0x0000001A

 
  Description  
     
 

A severe memory management error occurred.

This is a fatal Windows error, typically called a Stop message, Bug Check, or more commonly the Blue Screen of Death (BSoD). The system is in a forced reboot state. Any unsaved work is likely lost.

 
   
  Sample Screen  
     
 

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

MEMORY_MANAGEMENT

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 your computer, press F8 to select Advanced Startup Options, and then select Safe Mode.

Technical Information:

*** STOP: 0x0000001A

Beginning dump of physical memory
Physical memory dump complete.

Contact your system administrator or technical support group for further
assistance.

 
 
Text may appear differently depending on where the error occurs.
Additional technical information (hex values) specific to a machine are not shown.
 
   
  Key Facts  
     
 
Full Title
  MEMORY_MANAGEMENT 

Stop Code
  0x0000001A 

Type
  Fatal 

occurance meter
Windows
  2000, XP, Vista, 2008, 7, 8

Vendor
  Microsoft Corporation
 
   
  Solutions and Fixes  
     
 
  Date Votes ratings
Use Last Known Good Configuration
8
    Add    Flag
solution icon

If you are unable successfully boot into Windows because of the fatal error, Windows has an option to reload registry information from the last successful boot. To revert to the last successful boot:

  1. Reboot the computer.
  2. Near the end of the BIOS messages or graphic, but well before anything appears from Windows, press the F8 key. You may only have a few seconds to get the right spot to press F8 before it attempts to go into Windows. If the BIOS complains about a pressed key or asks you to go into BIOS setup, you've pressed F8 too soon (Don't go into BIOS setup).
  3. When successful, you should see a black screen with white text "Windows Advanced Options". Use the up or down arrow keys to highlight Last Known Good Configuration and press Enter.
 
   
 
transparent
transparent
solves it indicator
risk indicator
effort indicator
 
  FaultWire Staff
Posted: 5-Oct-2008
 
Avatar
 
Check Memory
7
    Add    Flag
solution icon

You may have a defective memory. This is even more likely if it only occurs when the system is cold or hot, but not all the time. Use a memory tester to confirm if it is defective or if you have spare memory, try replacement.

Windows 7 and Vista include a Memory Test program when booting from the Windows Installation DVD. Step-by-step instructions with screen shots are available at Using System Restore on 7/Vista/2008 as part of System Recovery.

Several software products that also provide memory and video diagnostics includes Fix-It Utilities Professional and SystemSuite Professional. Other diagnostic products include Eurosoft's PC Check and Iolo's System Mechanic.

Additional Memory Solutions:

  • Confirm all the memory is of the same type and speed. Many motherboards only work correctly when the memory is installed with matched sets and matched speeds.
  • If you added or changed your memory just before this problem occurred, try reverting to the prior memory configuration to confirm it's the source of the problem.
  • Check that the memory is fully seated in the sockets. Memory sockets often have side latches that need to be upright to indicate the memory is correctly locked in place.
  • Confirm the memory resides in the correct slots on the motherboard. You'll need to refer to the motherboard manual to confirm this. There is little consistency, even within a single vendor. Some systems require that memory is installed as matched pairs, but not always adjacent to each other!
  • It's also possible the memory problem is on the video card, as they often contain additional memory. The video card should be tested and/or try a different video card to see if the problem goes away.
 
   
 
transparent
transparent
solves it indicator
risk indicator
effort indicator
 
  FaultWire Staff
Posted: 5-Oct-2008
 
Avatar
 
Add More Memory
7
    Add    Flag
solution icon

The operating system or application may have run out of usable memory.

Adding additional memory may solve this problem. This is especially true if your system is configured for a minimal amount of memory for Windows.

 
   
 
transparent
transparent
solves it indicator
risk indicator
effort indicator
 
  FaultWire Staff
Posted: 5-Oct-2008
 
Avatar
 
Uninstall the Last Install
6
    Add    Flag
solution icon

If you can get the system up for more than a few minutes or can use safe mode, try removing the last installed software application or driver.

For removal of an application (Windows 8+)

  1. Press the Windows Key and X together, then  Control Panel, then Programs and Features.
  2. Select the software to uninstall and select Uninstall.

 For removal of an application (Windows 7 & Vista):

  1. Click on Start, Control Panel, then Programs and Features.
  2. Select the software to uninstall and select Uninstall.

For removal of an application (Windows XP):

  1. Click on Start, Control Panel, then Add or Remove Programs.
  2. Select the software to uninstall and select Remove.

To disable a driver:

  1. Bring up the system information dialog:

    On the keyboard, press the Windows key + Pause/Break.

       or

    Select Start, right click Computer and on the drop-down, select Properties.

  2. Click on the left side option Advanced system settings (7/Vista only).
  3. In System Properties, select the Hardware tab, then click on Device Manager button.
  4. Find the hardware/driver of interest (you may need to expand a choice at the "plus" graphic) and double click the choice.
  5. Select the Driver tab. Here you can perform a number of actions such as update the driver, roll Back the driver to an older version, disable or uninstall the driver.
  6. Click OK to exit, then close the Device Manager and other previously opened dialogs.
 
   
 
transparent
transparent
solves it indicator
risk indicator
effort indicator
 
  FaultWire Staff
Posted: 5-Oct-2008
 
Avatar
 
Get the Latest Drivers
6
    Add    Flag
solution icon

Check if you are using the latest hardware drivers, especially the chipset and video drivers. Older drivers are a common contributor to BSoD issues.

You can use a product like Driver Genius or Radar Sync to verify you have the latest drivers and help keep all your drivers up-to-date. If you're comfortable with driver installations, you can individually find and install current drivers.

A some of the most popular driver download sites:

 
   
 
transparent
transparent
solves it indicator
risk indicator
effort indicator
 
  FaultWire Staff
Posted: 5-Oct-2008
 
Avatar
 
Update the BIOS and BIOS Parameters
6
    Add    Flag
solution icon

Check with the PC manufacturer if you're using the latest BIOS or not. If not, update to the current version.

A few of the manufacture's download or support links for a motherboard/BIOS update:

    If the BIOS is current, it's possible bad BIOS parameters are causing the problem, especially if the memory or CPU settings are overclocked. The BIOS parameters are stored in CMOS memory. The best way to reset the BIOS parameters is to remove the CMOS battery. To do this:

    1. Unplug the PC, and open the case.
    2. Locate the battery on the motherboard - typically a silver coin cell.
    3. Remove the battery and note if the plus side is up or down, so you can reinstall it later the same way.
    4. Wait at least 1 minute and reinstall the battery.
    5. Attach power and power up. Typically a BIOS warning message will indicate CMOS was corrupted or changed and it may require you to go into the BIOS setup to set the time and date.
    6. Proceed to boot Windows and see if this fixes the issue.

    Some BIOSes have options to enable/disable caching and/or shadowing. If the options are available, disable caching and shadowing. Most newer (2005+) systems do not have these options. There are many BIOS makers and customized versions of the BIOS, so you may have to enter BIOS setup and look a bit to find these options. Typically you press a key like Esc, Del, F1, or F2 before Windows starts (almost right after you reboot) to enter BIOS setup. Consult your computer manual for details. The setup key can also be found in our BIOS access list.

     
       
     
    transparent
    transparent
    solves it indicator
    risk indicator
    effort indicator
     
      FaultWire Staff
    Posted: 5-Oct-2008
     
    Avatar
     

    Also see our list of common Fatal Error Solutions.

     
     
     
      Forum Help  
         
     
    Forums on topic

    Check out what others say about this issue and review or add your own comments and solutions!

    Go to Forums on topic.
     
       
      Technical Details  
         
     
      technical details

    After the Stop code will be up to 4 hex values: {Parameter 1, Parameter 2, Parameter 3, Parameter 4} of which only Parameter 1 is of interest.

    The specific memory issue is identified from the Parameter 1 value (in hex):

    Value The cause of the error
    0x1 The fork clone block reference count is corrupt. (This only occurs on checked builds of Windows used by developers.)
    0x777 The caller is unlocking a system cache address that is not currently locked. (This address was either never mapped or is being unlocked twice.)
    0x778 The system is using the very last system cache view address, instead of preserving it.
    0x780 The PTEs mapping the argument system cache view have been corrupted.
    0x781 The PTEs (Page Table Entries) mapping the argument system cache view have been corrupted.
    0x1000 A caller of MmGetSystemAddressForMdl* tried to map a fully-cached physical page as non-cached. This action would cause a conflicting hardware translation buffer entry, and so it was refused by the operating system. Since the caller specified "bug check on failure" in the requesting MDL, the system had no choice but to issue a bug check in this instance.
    0x1010 The caller is unlocking a pageable section that is not currently locked. (This section was either never locked or is being unlocked twice.)
    0x1234 The caller is trying lock a nonexistent pageable section.
    0x1235 The caller is trying to protect an MDL (Memory Descriptor List) with an invalid mapping.
    0x3451 The PTEs of a kernel thread stack that has been swapped out are corrupted.
    0x8888 Internal memory management structures are corrupted.
    0x8889 Internal memory management structures are corrupted.
    0x41283 The working set index encoded in the PTE (Page Table Entry) is corrupted.
    0x41284 A PTE or the working set list is corrupted.
    0x41286 The caller is trying to free an invalid pool address.
    0x41785 The working set list is corrupted.
    0x41287 Internal memory management structures are corrupted. To further investigate the cause, a kernel memory dump file is needed.
    0x61940 A PDE has been unexpectedly invalidated.
    0x3030303 The boot loader is broken. (This value applies only to systems using the Intel Itanium CPU.)
    Other An unknown memory management error occurred.

    (For software developers: MSDN reference)

     
       
      Vendor Summary  
         
     
    Vendor
      Microsoft Corporation (more info...)

    Microsoft Corporation Logo
    Phone
    1-425-882-8080
    1-800-642-7676

    Web
    Main
    USA

    Assistance
    Support
    Downloads

     
         
        While BSoD fatal stop errors are identified by Microsoft Windows, they are often caused by non-Microsoft applications, drivers and hardware issues.  
       
      Research this Issue  
         
     
    Getting search results...
     
         
      Notes  
         
      While we believe this information up to date and accurate, FAQware is not responsible for any inaccuracies. If you find something that is out of date or inaccurate, please let us know at so we can correct it.