Windows memory diagnostics tool

If you suspect memory issues, then you may also want to consider using and running Memtest86+ at boot. Memtest86+ is a comprehensive stand-alone memory diagnostic program that you boot from at startup to test your RAM. You can download a ISO file to burn to DVD to boot with, or a floppy disk package installable from Windows to a USB flash drive or floppy disk to boot with.
Microsoft Online Crash Analysis: Windows Memory Diagnostic Users Guide
http://www.sevenforums.com/tutorials/715-memory-diagnostics-tool.html
NOTE: Start with either step 1, 2, or 3 for how you want to start the Memory Diagnostics Tool.

1. To Start from within Windows 7

A) Open the Control Panel (icons view).
B) Click on the Administrative Tools icon, and click on Memory Diagnostics Tool.
C) Go to step 1F below.
OR
D) Open the Start menu.
E) In the Start Menu search box, type mdsched and press Enter. (See screenshot below)

F) Select the Restart now and check for problems option. (See screenshot below)

G) Go to step 4.

2. To Start from Windows Boot Manager

A) Boot into the Advanced Boot Options screen.
B) While in the Advanced Boot Options screen, press the Escape (Esc) key. (See screenshot below)

C) While in the Windows Boot Manager screen, press the Tab key. (See screenshot below)

D) With Windows Memory Diagnostics selected, press Enter. (See screenshot below)

E) Go to step 4.

3. To Start from System Recovery Options

A) Boot into the System Recovery Options screen.
B) Select the Windows Memory Diagnostic Tool option. (See screenshot below)

C) Select the Restart now and check for problems option. (See screenshot below)

4. The computer will now restart, and you will see this screen next. (See screenshot below.
NOTE: Windows Memory Diagnostic Tool will run the Standard test by default.

A) Go to step 6.

5. To Change the Memory Diagnostic Tool Options

A) Press F1. (See screenshot above)
NOTE: If you have a multimedia keyboard, then you may need to press the Function (F-Lock) key for F1 to work.
B) Press the TAB key to switch between the option categories, and use the arrow keys to select the option. (See screenshot below)

C) When finished, press F10 to apply any changes you made to the options. (See screenshot above)
NOTE: Press the Escape (Esc) key if you do not wish to make any changes to the options and return to the screen below step 4.

6. When the test is finished running, it will automatically restart the computer. (See screenshot below step 4)
NOTE: If errors are found, the Windows Memory Diagnostics Tool will attempt to determine which particular memory module in your computer is causing these errors. If that information is available, it will be stated in the results after you log on from the restart. If bad memory is found then you will need to remove and replace the bad RAM module.
7. You can also read the Memory Diagnostic Tool system log in Event Viewer.

Error in memory module(s)

STOP 0x0000008e

STOP 0x00000050 PAGE_FAULT_IN_NON_PAGED_AREA 

Source

Additionally, if you troubleshoot by removing all unnecessary hardware devices that are installed on the computer, and then you run the Setup program, you may receive an error message that is similar to the following:

Setup cannot copy the file Setupdd.sys. 

This behavior may occur if one of the following conditions is true:

• One or more of the random access memory (RAM) modules that are installed on your computer are faulty.
• The RAM configuration is incompatible with Windows XP.

STOP: 0x0000004E

Source

PFN_LIST_CORRUPT means that the system went to swap memory between the RAM and the VRAM on the hard drive, and couldn't.
Either:

• Pagefile.sys is not properly addressed.. did you change it's location in the registry?
• HDD Corruption -- The bad sector is located inside the pagefile.sys (although usually this would just cause a hang)
• BAD RAM -- (usually would give you a Page Fault Error instead

Vapor wrote:
one last thing - what destroyed your ram in the first place is random, but in my case it was the powersupply. So i switched from 300 watt to 600 watt. Most people dont know this, but many graphics card and system errors/failures is from mal-power!
Good luck

Posted by Mosel Lathersn
Does that mean if I change my memory, i should also upgrade my power supply to prevent from happening again?

Posted by Geoff Wheeler
check your CPU heatsink for proper thermal contact.
Replacing this fixes ALL blue screen crashes

Posted by doug h.
Heatsink compound WON'T fix all "blue screen" crashes...
Most PFN_LIST_CORRUPT problems are related to memory modules issues - bad, not-seated properly, etc. The first thing to try is to re-seat each of your memory sticks and see if that fixes the problem.
So, if re-seating doesn't work, like someone mentioned earlier, get a memchecker and put it on a bootable floppy or CD and use it. Better yet, if you've upgraded your memory and still have your old sticks (or have access to to some that you know are correct for your PC), replace them and see if that corrects the problem.
If this doesn't pan out then you can move to the less probable scenarios like CPU overheating, power supply issues, BIOS-upgrades, etc.

tartar wrote:
I have solved my problem by updating BIOS. Now it works flawlessly.

Posted by Michael
90% of the time this message does not mean your ram itself is bad. A program using improper mdls could also cause this same issue. as well as hitting the reset button can cause this issue because the pfn (Page Frame Database) also called Page Frame Number list hence the PFN part is not flushed out. Drivers can also cause this problem by writing to memory areas they sholdn't write to. Don't be so quick to chalk it up as bad ram. run a memory test if its bad fine otherwise try disabling drivers one by one (sound drivers do this a LOT) till you find your culprit

The Nvdia display driver is the problem, if I try to change my screen resolution (after a new installation with nvidia driver), my system crashed.

What is "MDLs"? I have this blue screen of death in Windows Vista Ultimate 32-bit
Posted by Michael
MDLs are a programming api for programs to lock certain areas of memory so another program cannot use it. its used in multi-threaded programs so that they have exclusive access to an area of memory and sometimes things lock an area used by another program instead of its own area and that causes windows to just shutsdown to stop the intruder from doing something it shouldn't do.
Yes, bad memory CAN cause it, but 90% of the time its a bad driver (or badly written one) Just replaced a sound card on my vista machine 2 months ago that was causing the PFN_LIST_CORRUPT message and no longer get it. If i put the old sound card in, I get the message again. (turns out the sound card does not have 100% vista compatible drivers)

STOP 0x0000008e

Source Source2

STOP 0x00000050 PAGE_FAULT_IN_NON_PAGED_AREA
When you install Microsoft Windows XP, you may receive a Stop Error message while the Setup program is running.
This behavior may occur if one of the following conditions is true:

• One or more of the random access memory (RAM) modules that are installed on your computer are faulty.
• The RAM configuration is incompatible with Windows XP.