Diablo 3 Blue screen of death

  • Hey, I have recently encountered an issue, while playing Diablo 3 I can get BSOD time to time. Note that this is the only game where I have encountered this issue.

    I mostly get this issue when I'm talking with someone over xfire / ventrilo (I know that the xfire overlay may cause BSOD, it has been disabled), however it can happen even if I do not speak over these particular programs and/or if they are switched off.

    As i have been trying to fix myself the error contained in the BSOD itself inclined it has to do something with my HDD, I reinstalled it to my 2nd HDD, yet still the problem persisted, I have changed my SATA cables as it could be a solution, but it didn't work as well. Have error checking option (windows inbuilt), have tested my HDD's on various testing utilities (HDtune, no bad blocks, nor any other particular errors). The same goes for my RAM's I've used MEMTEST and it didn't show any errors.

    Eventviewer info - The computer has rebooted from a bugcheck. The bugcheck was: 0x000000f4 (0x0000000000000003, 0xfffffa8007893b30, 0xfffffa8007893e10, 0xfffff80003384510). A dump was saved in: C:\Windows\Minidump\060412-7191-01.dmp. Report Id: 060412-7191-01. (Dump files linked below)

    This is my DXDIAG (note I have older NVidia driver as I thought that the video drivers could have caused that, but as it appears it wasn't their fault and just haven't updated them afterwards) http://failiem.lv/down.php?i=vewwhcp&n=DxDiag.txt
    Minidump - http://failiem.lv/down.php?i=sflvqvc&n=060312-7300-01.dmp
    Minidump - http://failiem.lv/down.php?i=pypydfb&n=060412-7191-01.dmp

    Computer info
    GPU - Asus GTX570 CU II
    MOVO - Asus P8P67-M
    CPU - I5-2500K (Sandybridge)
    PSU - 800W Xilence
    RAM - 8GB Kingston (4x2GB)
    HDD - SSD OCZ Vertex 30GB (only windows)
    HDD - 1TB Samsung
    HDD - 1TB WD Black Caviar

    Well you're currently the only people who can save me, don't let me down blizz tech -_-

    And if you need any additional info, please, ask!
  • Pesado,

    Please look at the date of the thread before posting. For example, this one was last updated back in December 2014. Also, try not to come into a thread and just say "same here". We won't be able to do anything for you with just that information.

    If you have a problem, start a new thread of your own and post a complete description of what's happening along with a list of the steps you've tried so far to resolve it. It also helps to post your DxDiag info so we can see what hardware you're using. You can find this information in the Direct X Diagnostic Tool:

    Press Windows Key + R.
    Type DxDiag and press Enter.
    In the DxDiag window, at the bottom, click Save All Information.
    Name the file "dxdiag" and click Save. (note where it's been saved so you can find it)

    Locate the Dxdiag.txt file just created and open it to copy and paste ALL of it's contents into your new thread.