Results 1 to 4 of 4

Thread: How to Fix a Physical memory dump

  1. #1
    Join Date
    Dec 2008
    Posts
    33

    How to Fix a Physical memory dump

    hello , I have a problem with my computer almost every Hour suddenly a blue screen appears with marked physical memory dump to disk driver IRQL_NOT_LESS_OR_EQUAL. Does someone can help me solve this problem urgently please , Can you tell me how to Fix the Physical Memory Dump Errir thank you in advance

  2. #2
    Join Date
    Nov 2005
    Posts
    3,026

    Re: How to Fix a Physical memory dump

    The Windows Memory Diagnostic tests the Random Access Memory (RAM) on your computer for errors. The diagnostic includes a comprehensive set of memory tests. If you are experiencing problems while running Windows, you can use the diagnostic to determine whether the problems are caused by failing hardware, such as RAM or the memory system of your motherboard. Windows Memory Diagnostic is designed to be easy and fast. On most configurations, you can download the diagnostic, read the documentation, run the test and complete the first test pass in less than 30 minutes.

    To run Windows Memory Diagnostic, you must reboot your computer with the disk or CD-ROM on which you installed Windows Memory Diagnostic in the drive. After the reboot, Windows Memory Diagnostic will load and its interface will appear. After loading, the first test pass will begin, using the default standard test suite, and continue until complete, unless Windows Memory Diagnostic is either paused or exited. Once the first test pass is complete, Windows Memory Diagnostic will begin a second test pass using the same settings as before. Windows Memory Diagnostic will continue to run test passes until you exit.

    Download Windows Memory Diagnostic

  3. #3
    Join Date
    Apr 2008
    Posts
    3,295

    Re: How to Fix a Physical memory dump

    When using Windows 2000 or Windows XP, it may happen that the error occurred, causing a blue screen:

    *** STOP: 0x0000000A (0x00000011, 0x0000002, 0x00000001, 0x80443205)
    IRQL_NOT_LESS_OR_EQUAL


    This problem is due to access by a driver or process to a protected memory area. The error may be due to faulty memory or a new device installed incorrectly.

    In such cases it is advisable, if possible, to temporarily uninstall or remove the the latest hardware/software added, and gradually try automatic re installing the latest driver for each device.

  4. #4
    Join Date
    Apr 2008
    Posts
    3,522

    Re: How to Fix a Physical memory dump

    To Solve your problem

    1. Click on Start, Control Panel, then double-click Display.
    2. On the Settings tab, click Advanced, then click the Troubleshooting tab.
    3. Move the Hardware Acceleration slider to None, then uncheck the Enable Write Combining.
    4. Click OK twice.


    Note: This procedure prevents the display driver from programming the hardware incorrectly, but it causes the loss of some functionality and video performance. Even if you can still set the hardware acceleration on a level higher than None to regain functionality and performance, these settings increase the risk of seeing the problem happen again. To ensure optimal stability, leave hardware acceleration off

Similar Threads

  1. Physical Memory Dump Of Windows Xp
    By imvgsthe1 in forum Operating Systems
    Replies: 3
    Last Post: 12-10-2009, 09:05 AM
  2. Physical Memory Dump
    By Ranchero in forum Windows XP Support
    Replies: 1
    Last Post: 24-07-2008, 01:28 PM
  3. dump of physical memory
    By manuscripts in forum Windows XP Support
    Replies: 1
    Last Post: 29-07-2007, 08:22 PM
  4. Physical memory dump
    By Nabhendu in forum Vista Help
    Replies: 4
    Last Post: 19-06-2006, 01:03 PM
  5. Physical memory dump
    By Russyan in forum Windows XP Support
    Replies: 2
    Last Post: 26-09-2005, 09:36 AM

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Page generated in 1,710,814,030.29103 seconds with 17 queries