Memory dumps in Windows XP

By Matt_2006 ยท 5 replies
Jan 19, 2006
  1. Hi, I'm only new here, but my Windows XP Professional (SP2) laptop has been having numerous blue STOP screens recently. I managed to attach the dump files in a ZIP file below, so if anyone can provide me with further information as to what is causing them, I would very much appreciate it.

    The ZIP file attached contains the 4 most recent dumps.

    Another problem I have been having with the same computer is that when it starts up (at the Welcome screen) it says "One of the files containing the system's registry data had to be recovered by use of a log or alternate copy. The Recovery was successful." This is just a basic Windows message popup and the MSDN site says not to worry about it - but I want to! Mainly because it is corrupting parts of Windows such as Network Connections in Control Panel - there are no connections listed at all. In the properties for Windows Firewall, on the Advanced tab, it says network settings are corrupt.

    Thanks in advanced for anyone who can help :)

    Attached Files:

  2. DamianTV

    DamianTV TS Rookie Posts: 20

    That almost sounds like bad sectors on your hard drive. I'll leave the reading of the dump files for someone else, I can read but dont know enough specifically about what Im looking at to understand. First question, have you tried doing a surface scan on your hard drive (scan disk)?
  3. Matt_2006

    Matt_2006 TS Rookie Topic Starter

    It did it automatically one time at start up. It found a bad area in file "$I30", repaired it successfully. The next time CHKDISK ran, it said there were no errors.
  4. peterdiva

    peterdiva TechSpot Ambassador Posts: 1,088

    Crashing at system files,download Memtest86+ to test your memory.
  5. cpc2004

    cpc2004 TS Evangelist Posts: 1,994


    1. Your windows install a faulty version ZoneAlarm. De-install or upgrade ZoneAlarm
    2. The software Hive may be corrupted. Use regedit to repair the registry
    3. The paging space may be corrupted. Run chksk /r to repair any bad I/O block. Re-allocate paging space
    4. Run memtest to stress test the ram.

    Your Debug Report
    Mini011306-01.dmp BugCheck 10000050, {e11c2000, 0, bf81ea2e, 1}
    Probably caused by : win32k.sys ( win32k!RGNOBJ::bMerge+117 ) <- faulty ram

    Mini011306-02.dmp BugCheck 1000008E, {c0000005, 8056eba4, ec832b18, 0}
    Probably caused by : ntoskrnl.exe ( nt!HvpGetCellMapped+5f ) <- corruption in software Hive

    Mini011806-01.dmp BugCheck 10000050, {90ff0875, 1, bf9ca787, 0}
    Probably caused by : memory_corruption <-- Faulty paging space

    Mini111605-01.dmp BugCheck 1000008E, {c0000005, 804dc5e2, ec086c80, 0}
    Probably caused by : ntoskrnl.exe ( nt!KeDelayExecutionThread+27f ) <- Faulty RAM
  6. Matt_2006

    Matt_2006 TS Rookie Topic Starter

    Hi, thanks cpc2004.

    When you say faulty ram, do mean the actual ram sticks in the computer?

    And also when you say repair the registry using regedit, can you please explain how to do that? I know you can export the registry (for backup) but if the registry (or part of it) is corrupt then I'll just be backing up a faulty registry won't I?

    Thanks again,

Topic Status:
Not open for further replies.

Similar Topics

Add your comment to this article

You need to be a member to leave a comment. Join thousands of tech enthusiasts and participate.
TechSpot Account You may also...