TechSpot

Help interpretting minidump analysis

By scarecrow420
Oct 4, 2006
  1. Hi guys,

    System Specs:

    Conroe E6600
    ASRock Conroe865PE motherboard
    4 x 512Mb Crucial Ballistix DDR500
    Leadtek 6600GT (AGP)
    Seagate 120Gb SATA drive
    600W power supply


    This system was running fine for a couple of weeks, but this week it has started randomly rebooting.

    I have run the windows debugging tools over the minidump files, but im not exactly sure what i can do with the analyses. They all seem to point to a particular memory address, but when running memtest86+ it runs fine for several hours without a single error.

    however the most recent time it crashed, i ran memtest86+ straight away after the crash, and it actually did show up HEAPS of errors straight away. But after only like 10 seconds, i restarted the memory tests again and then they didnt show any errors, once again for hours on end.

    So is there a problem with the RAM or its something like the motherboard or system is just unstable so soon after the crash occurs, which causes the RAM to have errors.

    Ive attached the 5 most recent minidumps

    Any help would be much appreciated

    here's a basic rundown of what id already extracted from the various minidumps. Note how the same address 7e4e819b seems to be coming up alot. What can this tell me?

    Mini100206-01.dmp Bug Check: BugCheck 100000D1, {7e4e819b, 2, 0, 7e4e819b}
    Mini100206-01.dmp Probable Cause: Probably caused by : hardware

    Mini100206-02.dmp Bug Check: BugCheck 100000D1, {7e4e819b, 2, 0, 7e4e819b}
    Mini100206-02.dmp Probable Cause: Probably caused by : hardware

    Mini100306-01.dmp Bug Check: BugCheck 100000D1, {7e4e819b, 2, 0, 7e4e819b}
    Mini100306-01.dmp Probable Cause: Probably caused by : hardware

    Mini100306-02.dmp Bug Check: BugCheck 1000008E, {c0000005, 7e4e819b, b754c7d8, 0}
    Mini100306-02.dmp Probable Cause: Probably caused by : hardware

    Mini100306-03.dmp Bug Check: BugCheck 1000008E, {c0000005, 7e4e819b, baa0877c, 0}
    Mini100306-03.dmp Probable Cause: Probably caused by : hardware

    Mini100306-04.dmp Bug Check: BugCheck 1000007E, {c0000005, 7e4e819b, f78f2b50, f78f284c}
    Mini100306-04.dmp Probable Cause: Probably caused by : hardware

    Mini100306-05.dmp Bug Check: BugCheck 100000D1, {7e4e819b, 2, 0, 7e4e819b}
    Mini100306-05.dmp Probable Cause: Probably caused by : hardware

    Mini100306-06.dmp Bug Check: BugCheck 1000008E, {c0000005, 8058469f, b764dc00, 0}
    Mini100306-06.dmp Probable Cause: Probably caused by : memory_corruption ( nt!MmDeleteTeb+2e )

    Mini100306-07.dmp Bug Check: BugCheck 1000008E, {c0000005, 7e4e819b, b4f0995c, 0}
    Mini100306-07.dmp Probable Cause: Probably caused by : hardware

    Mini100306-08.dmp Bug Check: BugCheck 1000000A, {0, 2, 1, 804ecb04}
    Mini100306-08.dmp Probable Cause: Probably caused by : ntkrnlmp.exe ( nt!CcAllocateInitializeBcb+93 )

    Mini100306-09.dmp Bug Check: BugCheck 100000D1, {7e4e819b, 2, 0, 7e4e819b}
    Mini100306-09.dmp Probable Cause: Probably caused by : hardware
     
  2. scarecrow420

    scarecrow420 TS Rookie Topic Starter

    Here's another 5 minidumps
     
  3. scarecrow420

    scarecrow420 TS Rookie Topic Starter

    bump... anyone able to shed more light on the minidump analyses?
     
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...