Minidumps of crashing system

By Xyxoz ยท 12 replies
Dec 25, 2006
  1. Hello.
    For a very detailed description of my problem check my other thread at:

    Here are my 4 latest minidumps, attached.
    I'd really appreciate a solution on this problem, as it's killing me.

    Attached Files:

  2. Xyxoz

    Xyxoz TS Rookie Topic Starter Posts: 31

    I've disabled "Restart automatically on system error" in advanced system options.
    I've just uploaded a picture of my screen, when it crashes to my other thread. Sometimes it just goes pure blue.
    You'll find the picture on reply #6
  3. howard_hopkinso

    howard_hopkinso TS Rookie Posts: 24,177   +19

    3 minidumps crash at RtkHDAud.sys. this is part of your onboard sound drivers. Download and install the latest version from your mobo manufacturers website.

    1 minidump crashes at ati3duag.dll. this is part of your graphics card drivers. Again check for any updated drivers.

    3 of your minidumps reference wow.exe as the owning process. Do you get crashes when playing any other game?

    See if that helps.

    Regards Howard :)
  4. Xyxoz

    Xyxoz TS Rookie Topic Starter Posts: 31

    Thanks a lot for the reply, it's greatly appreciated.
    But the problem here is, that I've always had this problem - even before any hardware switch. My graphics driver is the newest for my card as well.
    I've always got the problem in any game or program that loaded my graphics card heavily before switching any hardware, and I've only installed WoW on my new harddrive. And seeing it happens in WoW after replacing most of my hardware, it must happen in any game again.
    When my computer crashes, my sound stops playing as well, so that might be why my sound driver crashed.

    But can it be hardware-related then? Would it be my RAM or my graphics card? Did you see the picture of my screen, when the problem occured by the way?
  5. howard_hopkinso

    howard_hopkinso TS Rookie Posts: 24,177   +19

    Go into your device manager and temporarily disable your onboard sound. See if you still get the crashes as frequently.

    In your other thread, you say you`ve tested your ram. However, some faulty ram can pass memtest.

    I agree with Donagual that it may be your graphics card that`s the problem. Try what I`ve suggested above and let me know the outcome. Please attach any further minidumps you get.

    Regards Howard :)
  6. Xyxoz

    Xyxoz TS Rookie Topic Starter Posts: 31

    All right. I think I'll just buy a new GFX. This is another soundcard as well, so I don't think it'd do the exact same thing to my computer as before I switched it. But anyways.. Can a failing soundcard really cause restarts? :S
  7. Xyxoz

    Xyxoz TS Rookie Topic Starter Posts: 31

    Update: I disabled my sound card. Just earlier, when I was searching the internet, not playing a game or loading the graphics card at all I got a blue screen with an error message and a few troubleshooting instructions.
    This is the newest dump with the sound disabled.
    I won't order my graphics card yet then. Do you know what the problem is?
  8. Xyxoz

    Xyxoz TS Rookie Topic Starter Posts: 31

    Man.. This can't be true. I just bought my new graphics card, uninstalled my old drivers and installed the newest ones from And guess what happened a day after :(
    Now, is it faulty RAM or is it a software issue?
    Latest minidump:

  9. cpc2004

    cpc2004 TS Evangelist Posts: 1,994

    From your latest minidumps, your windows is still using the RealTek Sound card driver. You have to de-install RealTek Sound Card driver and install the sound card driver.

    Mini123006-01.dmp had code corruption and it is the symptom of faulty ram.Mini122606-01.dmp is crashed with NT Status code 1d (ie illegal instruction) and it is also the symptom of hardware error. Probably the ram is bad. Run memtest to stress test the ram.

    Mini122406-01.dmp BugCheck 100000D1, {44004, 2, 0, f6da1e33}
    Probably caused by : RtkHDAud.sys ( RtkHDAud+65e33 )
    Mini122406-01.dmp BugCheck 100000D1, {44004, 2, 0, f6da1e33}
    Owning Process 864c1660 Image: WoW.exe
    Mini122406-01.dmp Probably caused by : RtkHDAud.sys ( RtkHDAud+65e33 )
    RtkHDAud.sys Wed Jun 28 16:25:18 2006 (44A23CEE)

    Mini122406-02.dmp BugCheck 100000D1, {44004, 2, 0, f6909e33}
    Owning Process 80562f00 Image: Idle
    Mini122406-02.dmp Probably caused by : RtkHDAud.sys ( RtkHDAud+65e33 )

    Mini123006-01.dmp BugCheck 1000008E, {c0000005, 805295da, ecb83550, 0}
    Owning Process 86734da0 Image: iexplore.exe
    Mini123006-01.dmp Probably caused by : memory_corruption

    Mini122406-03.dmp BugCheck 100000D1, {4, 2, 0, f6dc1e33}
    Owning Process 8668bc68 Image: WoW.exe
    Mini122406-03.dmp Probably caused by : RtkHDAud.sys ( RtkHDAud+65e33 )

    Mini122606-01.dmp BugCheck 1000008E, {c000001d, bfabf219, b84f8a4c, 0}
    Owning Process 84ea06f8 Image: WoW.exe
    Mini122606-01.dmp Probably caused by : ati3duag.dll ( ati3duag+1b219 )

    Mini011107-01.dmp BugCheck 100000D1, {8, 2, 0, 8}
    Owning Process 852d6da0 Image: WoW.exe
    Mini011107-01.dmp Probably caused by : RtkHDAud.sys ( RtkHDAud+5b112 )
    RtkHDAud.sys Wed Jun 28 16:25:18 2006 (44A23CEE)
  10. Xyxoz

    Xyxoz TS Rookie Topic Starter Posts: 31

    All right, thanks a lot.
    Seeing I had this problem with my old motherboard, which had built-in sound card as well, I guess that leaves the RAM as the culprit. I've already run Memtest86+ for like 5 hours, and that didn't get any errors at all. But as I've been told faulty RAM can pass such tests.
  11. Xyxoz

    Xyxoz TS Rookie Topic Starter Posts: 31

    Ok, I deleted my sound driver and installed it again from my motherboard driver cd. Problem still persists. The weird thing is, that at my last crash it showed a sound-related sys file as well. But can it really be the sound? I mean, it happened before the hardware switch as well.
    Can I be sure 100% sure it's the RAM?
    More dumps:
  12. peterdiva

    peterdiva TechSpot Ambassador Posts: 1,088

    Run with only 1 stick of RAM at a time, if it still crashes then swap it for the other stick.

    BugCheck 1000007E, {c0000005, b818e029, b84ccbb4, b84cc8b0}
    Probably caused by : memory_corruption

    CHKIMG_EXTENSION: !chkimg -lo 50 -db !kmixer
    8 errors : !kmixer (b818e00a-b818e07a)
  13. Xyxoz

    Xyxoz TS Rookie Topic Starter Posts: 31

    I guess I'll just wait till I can afford new RAM :)
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...