TechSpot

bsod help and minidump

By OldTom
Nov 11, 2005
  1. hello my PC has started to reboot recently and i am getting the dreaded BSOD.
    here is the latest .txt file and I have attached some minidump..rar

    Any help would be greatly appreciated, and if I have left anythiing out please let me know, Cheers.

    MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
    Arguments:
    Arg1: 0004128b, The subtype of the bugcheck.
    Arg2: 0075c201
    Arg3: 00000000
    Arg4: c0503000

    Debugging Details:
    ------------------


    BUGCHECK_STR: 0x1a_4128b

    CUSTOMER_CRASH_COUNT: 2

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    LAST_CONTROL_TRANSFER: from 80524e66 to 8053331e

    STACK_TEXT:
    f7510b9c 80524e66 0000001a 0004128b 0075c201 nt!KeBugCheckEx+0x1b
    f7510bd0 804e71a0 000000d5 0000085f 0075c201 nt!MiSwapWslEntries+0x157
    f7510bfc 804e9064 f7510c28 c0505818 886ff9f8 nt!MiUpdateWsle+0x159
    f7510c20 804e9e1c 0000085f c01f240c 8117d490 nt!MiAddValidPageToWorkingSet+0x99
    f7510c50 804e9d24 00000000 7c90390c c01f240c nt!MiCompleteProtoPteFault+0x167
    f7510c80 804e91e7 00000000 7c90390c c01f240c nt!MiResolveProtoPteFault+0x17d
    f7510cfc 804e8f62 00000000 7c90390c c01f240c nt!MiDispatchFault+0x13b
    f7510d4c 804e1718 00000000 7c90390c 01000001 nt!MmAccessFault+0xc09
    f7510d4c 7c90390c 00000000 7c90390c 01000001 nt!KiTrap0E+0xcc
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    033afa74 00000000 00000000 00000000 00000000 0x7c90390c


    FOLLOWUP_IP:
    nt!MiSwapWslEntries+157
    80524e66 8b4d10 mov ecx,[ebp+0x10]

    SYMBOL_STACK_INDEX: 1

    FOLLOWUP_NAME: MachineOwner

    SYMBOL_NAME: nt!MiSwapWslEntries+157

    MODULE_NAME: nt

    DEBUG_FLR_IMAGE_TIMESTAMP: 42250ff9

    STACK_COMMAND: kb

    IMAGE_NAME: memory_corruption

    FAILURE_BUCKET_ID: 0x1a_4128b_nt!MiSwapWslEntries+157

    BUCKET_ID: 0x1a_4128b_nt!MiSwapWslEntries+157

    Followup: MachineOwner
     
  2. cpc2004

    cpc2004 TS Evangelist Posts: 1,994

    Hi Oldtom,

    All of your minidumps are crashed with memory access fault. The culprit is faulty memory. You can run memtest to stress the ram. If memtest reports the ram is faulty, ram is bad. However Memtest is not a perfect tool to test the memory as some faulty ram can pass memtest.

    Suggestion
    1. Check the temperature of the CPU and make sure that it is not overheat (ie temperature < 60C)
    Make sure that the CPU fan works properly
    2. Reseat the memory stick to another memory slot
    3. Downclock the ram
    4. Clean the dust inside the computer case
    5. Make sure that the ram is compatible to the motherboard
    6. Check the bios setting about memory timing and make sure that it is on
    If it still crashes, diagnostic which memory stick is faulty
    1. Take out one memory stick. If windows does not crash, the removed memory stick is faulty.
    2. If you have only one memory stick, replace the ram
     
  3. OldTom

    OldTom TS Rookie Topic Starter

    Thankyou for your reply.
    I have run memtest for a few hours and it reports no errors. hmmm

    1. Check the temperature of the CPU and make sure that it is not overheat (ie temperature < 60C);
    never goes above 50C
    Make sure that the CPU fan works properly;
    Silent and clean as a whistle
    2. Reseat the memory stick to another memory slot;
    I cannot do this as the configuration for this board (a7nx8-e deluxe) only allows for this config with my RAM. please see my post here: http://www.houseofhelp.com/forums/showthread.php?t=44728
    3. Downclock the ram;
    Im not sure what you mean by this, but the Ram isnt Overclocked.
    4. Clean the dust inside the computer case;
    I am pedantic about dust as I have asthma and a baby, so this too has been done.
    5. Make sure that the ram is compatible to the motherboard;
    please see this thread again: http://www.houseofhelp.com/forums/showthread.php?t=44728
    6. Check the bios setting about memory timing and make sure that it is on:
    It is on, as i need to set it as here: http://www.houseofhelp.com/forums/showthread.php?t=44728
    If it still crashes, diagnostic which memory stick is faulty
    1. Take out one memory stick. If windows does not crash, the removed memory stick is faulty.
    have run memtest and windows on one stick and it does the same thing ;o(
    2. If you have only one memory stick, replace the ram;
    I have 2 sticks.

    I hope this helps. Any further instructions?
     
  4. cpc2004

    cpc2004 TS Evangelist Posts: 1,994

    Hi,

    Some faulty ram can pass memtest. Take out a memory stick. Don't run the memtest. Reboot the system normally. If your windows does not crash for two days, the removed memory stick is faulty. If it still crashes, swap the memory stick and reboot windows.
     
  5. OldTom

    OldTom TS Rookie Topic Starter

    just a question, could improperly placed or faulty cables, IDE and SATA, to the drives cause this problem?
     
  6. cpc2004

    cpc2004 TS Evangelist Posts: 1,994

    Hi OldTom,

    If it is cable or hard disk error, windows will give bugcheck code 77, 7A and 7B.
     
  7. Lohq

    Lohq TS Rookie

    I don't know if this helps, but I was having memory errors recently that I couldn't track down and I finally found the PSU was insufficent for the power I was demanding from my computer which was causing all kinds of faults... it might be something to take into consideration if your using a standard psu with a whole bunch of addons...

    read on Kirock's post about the PSU Wattage Calculator
    http://www.techspot.com/vb/showthread.php?t=48731
     
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...