TechSpot

Help me please, BSOD

By billymcgregs
May 19, 2009
  1. Hello, I have been getting this BSOD a lot lately.

    Error:
    The computer has rebooted from a bugcheck. The bugcheck was: 0x10000050 (0xbad0b158, 0x00000000, 0x805babc5, 0x00000002). A dump was saved in: C:\WINDOWS\Minidump\Mini051309-01.dmp.


    Comp details:
    Operating System: Windows XP Professional
    Manufacturer: Dell DXP051
    BIOS: Phoenix ROM BIOS PLUS Version 1.10 A03
    Processor: Intel(R) Pentium(R) D CPU 2.80 GHz (2 CPUs)
    Memory: 1022MB RAM
    Page File: 324 MB used. 2134 MB available
    DirextX 9.0c (4.09.0000.0904)
     
  2. Route44

    Route44 TechSpot Ambassador Posts: 11,966   +70

    As you can tell from your error code a number of things can cause your issue.

    0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
    Requested data was not in memory. An invalid system memory address was referenced. Defective memory (including main memory, L2 RAM cache, video RAM) or incompatible software (including remote control and antivirus software) might cause this Stop message, as may other hardware problems (e.g., incorrect SCSI termination or a flawed PCI card).

    You can attach your 5 most recent minidumps to your next posting.

    How to find your Minidump Files:

    My Computer > C Drive > Windows Folder > Minidump Folder > Minidump Files.

    It is these files that we need (not the folder). Attach to your next post. Notice the Manage Attachments button at the bottom when you go to post the next time. You can Zip up to five files per Zip. Please do us a favor and don’t Zip each one individually.
     
  3. billymcgregs

    billymcgregs TS Rookie Topic Starter

    thank you very much!
    here ya go
     
  4. Route44

    Route44 TechSpot Ambassador Posts: 11,966   +70

    Two errors are 0x50 but they only cited Windows OS drivers and they are too general to be of much help.

    One error is 0x0000007F: UNEXPECTED_KERNEL_MODE_TRAP and is defined as
    one of three types of problems occurred in kernel-mode: (1) Hardware failures. (2) Software problems. (3) A bound trap (i.e., a condition that the kernel is not allowed to have or intercept). Hardware failures are the most common cause and, of these, memory hardware failures are the most common.

    Again nothing definitive was cited.

    The remaining error is 0x8E and these are almost always caused by hardware errors and are strong indicators of bad RAM. Sure enough this minidump cited memory corruption as your cause.

    Keep in mind all three error codes have faulty memory as a strong possibility and with your constant crashes you should run Memtest on your RAM.

    See this link: http://www.techspot.com/vb/topic62524.html

    Let it run for a LONG time. The rule is a minimum of 7 Passes. There are 8 individual tests per Pass. Many people will start this test before going to bed and check it the next day.

    If you have errors you have corrupted memory and it needs to be replaced; it cannot be fixed.

    Also, with errors you need to run this test per stick of RAM. Take out one and run the test. Then take that one out and put the other in and run the test. If you start getting errors before 7 Passes you know that stick is corrupted and you don’t need to run the test any further on that stick.

    *** Get back to us with the results.
     
  5. billymcgregs

    billymcgregs TS Rookie Topic Starter

    So all the tests passed. So now I'm stuck.
     
  6. Route44

    Route44 TechSpot Ambassador Posts: 11,966   +70

    How many Passes did you allow it to run? Try this: Remove one stick of RAM and run your system for awhile. Any BSODs?

    Then switch out and do the same thing. What have been the results?
     
Topic Status:
Not open for further replies.

Similar Topics

Add New Comment

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