Numerous Blue Screens while playing Diablo 3


  1. Posts : 14
    windows 7 professional 64 bit
       #1

    Numerous Blue Screens while playing Diablo 3


    Hello, i have been having this problem for about a year now, and im kind of fed up with it
    I get constant blue screens when playing diablo 3, and i have no idea what might be causing this issue.

    I have run Memtest for 10 hours the other day, and it didnt come back with any issues, i also tried furmark as well as heaven benchmarks to see if its my graphics card.

    The last time i played, my audio completely cut out but i did not crash; It did however make the same sound it makes when it does crash and go into a blue screen.

    I have attached my latest dump files, and here is what WhoCrashed tells me as well:

    On Sun 3/30/2014 9:04:46 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\033014-22230-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
    Bugcheck code: 0x50 (0xFFFFF8A0520A7140, 0x0, 0xFFFFF880111AD60E, 0x5)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that invalid system memory has been referenced.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


    On Sun 3/30/2014 7:20:52 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\033014-35334-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
    Bugcheck code: 0x1A (0x41287, 0x3DBE5, 0x0, 0x0)
    Error: MEMORY_MANAGEMENT
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that a severe memory management error occurred.
    This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


    On Sat 3/29/2014 5:48:21 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\032914-19983-01.dmp
    This was probably caused by the following module: atikmdag.sys (atikmdag+0xED80)
    Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88011086D80, 0xFFFFF88004692740, 0x0)
    Error: SYSTEM_SERVICE_EXCEPTION
    file path: C:\Windows\system32\drivers\atikmdag.sys
    product: ATI Radeon Family
    company: Advanced Micro Devices, Inc.
    description: ATI Radeon Kernel Mode Driver
    Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).
    Google query: atikmdag.sys Advanced Micro Devices, Inc. SYSTEM_SERVICE_EXCEPTION




    On Fri 3/28/2014 4:33:14 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\032814-26754-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
    Bugcheck code: 0xA (0xFFFFF880FF9ED500, 0x2, 0x0, 0xFFFFF80002ED70DB)
    Error: IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


    On Fri 3/28/2014 2:48:46 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\032714-19749-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
    Bugcheck code: 0xC5 (0x8, 0x2, 0x0, 0xFFFFF80003000A9B)
    Error: DRIVER_CORRUPTED_EXPOOL
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that the system attempted to access invalid memory at a process IRQL that was too high.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


    On Wed 3/26/2014 1:58:04 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\032514-19968-01.dmp
    This was probably caused by the following module: rt64win7.sys (Rt64win7+0x288A)
    Bugcheck code: 0xD1 (0x80, 0x2, 0x1, 0xFFFFF88011D7788A)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\drivers\rt64win7.sys
    product: Realtek 8136/8168/8169 PCI/PCIe Adapters
    company: Realtek
    description: Realtek 8136/8168/8169 NDIS 6.20 64-bit Driver
    Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: rt64win7.sys (Realtek 8136/8168/8169 NDIS 6.20 64-bit Driver , Realtek ).
    Google query: rt64win7.sys Realtek DRIVER_IRQL_NOT_LESS_OR_EQUAL




    On Wed 3/26/2014 1:09:20 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\032514-24694-01.dmp
    This was probably caused by the following module: atikmdag.sys (atikmdag+0x277CE)
    Bugcheck code: 0xA0000001 (0x5, 0x0, 0x0, 0x0)
    Error: CUSTOM_ERROR
    file path: C:\Windows\system32\drivers\atikmdag.sys
    product: ATI Radeon Family
    company: Advanced Micro Devices, Inc.
    description: ATI Radeon Kernel Mode Driver
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).
    Google query: atikmdag.sys Advanced Micro Devices, Inc. CUSTOM_ERROR




    On Wed 3/26/2014 12:24:16 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\032514-18798-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0xABB80)
    Bugcheck code: 0x1000007E (0xFFFFFFFFC0000002, 0xFFFFF80002EBCB80, 0xFFFFF88009753DB0, 0xFFFFF88009753E50)
    Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


    On Fri 3/21/2014 1:58:19 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\032014-21964-01.dmp
    This was probably caused by the following module: ntfs.sys (Ntfs+0x48D8)
    Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88006BE2D38, 0xFFFFF88006BE2590, 0xFFFFF80002EECD6C)
    Error: NTFS_FILE_SYSTEM
    file path: C:\Windows\system32\drivers\ntfs.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT File System Driver
    Bug check description: This indicates a problem occurred in the NTFS file system.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


    On Sun 3/9/2014 11:08:14 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\030914-21403-01.dmp
    This was probably caused by the following module: atikmdag.sys (atikmdag+0xEBB5)
    Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF880110FDBB5)
    Error: UNEXPECTED_KERNEL_MODE_TRAP
    file path: C:\Windows\system32\drivers\atikmdag.sys
    product: ATI Radeon Family
    company: Advanced Micro Devices, Inc.
    description: ATI Radeon Kernel Mode Driver
    Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).
    Google query: atikmdag.sys Advanced Micro Devices, Inc. UNEXPECTED_KERNEL_MODE_TRAP


    On Sun 3/2/2014 5:17:33 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\030214-24897-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
    Bugcheck code: 0x19 (0x3, 0xFFFFFA801161CC20, 0xFFFFFA801161CC20, 0xFFFFFA800F61CC20)
    Error: BAD_POOL_HEADER
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that a pool header is corrupt.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

    Here is my system info:

    Videocard: Radeon 5770 HD
    SSD- Corsair 64gb

    Motherboard
    Manufacturer

    ASUSTeK COMPUTER INC.
    Product Name
    M5A99X EVO
    Version
    Rev 1.xx
    S/N
    MT7022001700656



    CPU
    Socket Designation

    AM3r2
    Manufacturer
    AMD
    Version
    AMD Phenom(tm) II X4 955 Processor
    Supported Voltage
    1.4 v
    External Clock
    200 MHz
    Max Speed
    3200 MHz
    Current Speed
    3200 MHz


    Memory
    Socket Designation

    DIMM0
    Current Speed
    1333 MHz
    Memory Type
    DDR3
    Installed Size
    4096 MBytes


    Socket Designation
    DIMM1
    Current Speed
    1333 MHz
    Memory Type
    DDR3
    Installed Size
    4096 MBytes


    Socket Designation
    DIMM2
    Current Speed
    1333 MHz
    Memory Type
    DDR3
    Installed Size
    2048 MBytes


    Socket Designation
    DIMM3
    Current Speed
    1333 MHz
    Memory Type
    DDR3
    Installed Size
    2048 MBytes
      My Computer


  2. Posts : 19,383
    Windows 10 Pro x64 ; Xubuntu x64
       #2

    Additional information is required.

    1. Download the DM Log Collector application to your desktop by clicking the link below

    DM Log Collector.exe

    2. Run it by double-clicking the icon on your desktop, and follow the prompts.
    3. Locate the .ZIP file created on your desktop, and upload it here in your next reply.

      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 10:43.
Find Us