TechSpot

BSOD - Recovered from serious error

By sugargurlie
Nov 20, 2005
  1. Hi,

    I've been getting random system restarts a lot for about a year now and I always get the Your system has recovered from a serious error when I restart. It happens most often when I'm playing games, so for ages i thought it was my graphics card, but I've recently upgraded to a new model and its not solved the problem, could you look at my minidump files and see if you can find the cause? It would be much appreciated!

    Sarah
     
  2. gary_hendricks

    gary_hendricks TS Rookie Posts: 107

    Have you upgraded to the latest DirectX drivers? It could also be a motherboard problem - is your motherboard very old?
     
  3. sugargurlie

    sugargurlie TS Rookie Topic Starter

    I have definitely got the latest Direct X, I had to install it to run Civ IV. My motherboard is only about a year old, I gave my system a rehaul last year about this time and the only things I kept from my old system were the graphics card (which has now been replaced) and my DVD-ROM.

    Just to be on the safe side I've made sure I have the latest drivers for my motherboard too!
     
  4. cpc2004

    cpc2004 TS Evangelist Posts: 1,994

    Hi,

    One of the minidump is crashed with 1 byte memory corruption and the rest of the minidumps are crashed at ATI display card driver.

    UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
    This means a trap occurred in kernel mode, and it's a trap of a kind
    that the kernel isn't allowed to have/catch (bound trap) or that
    is always instant death (double fault). The first number in the
    bugcheck params is the number of the trap (8 = double fault, etc)
    Consult an Intel x86 family manual to learn more about what these
    traps are. Here is a *portion* of those codes:
    If kv shows a taskGate
    use .tss on the part before the colon, then kv.
    Else if kv shows a trapframe
    use .trap on that value
    Else
    .trap on the appropriate frame will show where the trap was taken
    (on x86, this will be the ebp that goes with the procedure KiTrap)
    Endif
    kb will then show the corrected stack.
    Arguments:
    Arg1: 0000000d, EXCEPTION_GP_FAULT
    Arg2: 00000000
    Arg3: 00000000
    Arg4: 00000000

    Debugging Details:
    ------------------
    BUGCHECK_STR: 0x7f_d
    CUSTOMER_CRASH_COUNT: 1
    DEFAULT_BUCKET_ID: CODE_CORRUPTION
    LAST_CONTROL_TRANSFER: from 00000000 to a8269b4a
    SYMBOL_ON_RAW_STACK: 1

    STACK_TEXT:
    82204b20 00000000 00180001 00000000 00000000 0xa8269b4a

    STACK_COMMAND: dds @$csp ; kb

    CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    !chkimg -lo 50 -d !nt
    80506079 - nt!FsRtlRequestExclusiveOplock+112

    [ c2:a4 ]
    1 error : !nt (80506079)

    MODULE_NAME: memory_corruption
    IMAGE_NAME: memory_corruption
    FOLLOWUP_NAME: memory_corruption
    DEBUG_FLR_IMAGE_TIMESTAMP: 0
    MEMORY_CORRUPTOR: ONE_BYTE
    FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BYTE
    BUCKET_ID: MEMORY_CORRUPTION_ONE_BYTE
    Followup: memory_corruption

    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. Reseat video card as well.
    3. Downclock the ram. Check to default setting if you video card is overclocked.
    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
    For example : DIMM1 and DIMM2 do not have the same timing.
    DIMM1: Corsair CMX512-3200C2 512 MB PC3200 DDR SDRAM (2.5-3-3-8 @ 200 MHz) (2.0-3-3-7 @ 166 MHz)
    DIMM2: Corsair CMX512-3200C2 512 MB PC3200 DDR SDRAM (3.0-3-3-8 @ 200 MHz)
    DIMM3: Corsair CMX512-3200C2 512 MB PC3200 DDR SDRAM (3.0-3-3-8 @ 200 MHz)
    7. Make sure that your PSU have adequate power to drive all the hardware including USB devices
    8. If you have on-board video card. De-install ATI display card driver and remove ATI display card. Use on-board video card. If it does not crash, your ATI display card is faulty.

    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
     
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...