Solved

AMD CCC 13.10 Beta driver causing BSOD

Hello,

I am facing this issue whereas my PC using a Sapphire HD7970 OC with boost (BIOS 2 with 1000 core and 1450 mem @ 1.050v, 15% power control settings) blue screens when using the AMD 13.10 Beta driver. But i have since reverted to the latest 13.9 "WHQL" driver.

This following is the dmp. log reported by WhoCrashed

System Information (local)
--------------------------------------------------------------------------------

computer name: FBKMW2B7YDMG696
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8533716992 total
VM: 2147352576, free: 1933283328


--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Mon 23/9/2013 9:08:29 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092313-9937-01.dmp
This was probably caused by the following module: atikmpag.sys (atikmpag+0x7864)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8800498E75C, 0xFFFFF88009D3E408, 0xFFFFF88009D3DC60)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\atikmpag.sys
product: AMD driver
company: Advanced Micro Devices, Inc.
description: AMD multi-vendor Miniport Driver
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.
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: atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.).
Google query: Advanced Micro Devices, Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M


On Mon 23/9/2013 9:08:29 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1!VidMmInterface+0x20E9C)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF8800498E75C, 0xFFFFF88009D3E408, 0xFFFFF88009D3DC60)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
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 that cannot be identified at this time.


On Sat 21/9/2013 12:54:24 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092113-10623-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x37707)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF880047EA707, 0xFFFFF88005FF52A8, 0xFFFFF88005FF4B00)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.


--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

3 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

---

Is there any way that i can diagnose this problem?
11 answers Last reply Best Answer
More about amd ccc beta driver causing bsod
  1. fruitcakefps said:
    Hello,

    I am facing this issue whereas my PC using a Sapphire HD7970 OC with boost (BIOS 2 with 1000 core and 1450 mem @ 1.050v, 15% power control settings) blue screens when using the AMD 13.10 Beta2 driver. But i have since reverted to the latest 13.9 "WHQL" driver.

    This following is the dmp. log reported by WhoCrashed

    System Information (local)
    --------------------------------------------------------------------------------

    computer name: FBKMW2B7YDMG696
    windows version: Windows 7 Service Pack 1, 6.1, build: 7601
    windows dir: C:\Windows
    CPU: GenuineIntel Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz Intel586, level: 6
    4 logical processors, active mask: 15
    RAM: 8533716992 total
    VM: 2147352576, free: 1933283328


    --------------------------------------------------------------------------------
    Crash Dump Analysis
    --------------------------------------------------------------------------------

    Crash dump directory: C:\Windows\Minidump

    Crash dumps are enabled on your computer.

    On Mon 23/9/2013 9:08:29 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\092313-9937-01.dmp
    This was probably caused by the following module: atikmpag.sys (atikmpag+0x7864)
    Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8800498E75C, 0xFFFFF88009D3E408, 0xFFFFF88009D3DC60)
    Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
    file path: C:\Windows\system32\drivers\atikmpag.sys
    product: AMD driver
    company: Advanced Micro Devices, Inc.
    description: AMD multi-vendor Miniport Driver
    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.
    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: atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.).
    Google query: Advanced Micro Devices, Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M


    On Mon 23/9/2013 9:08:29 AM GMT your computer crashed
    crash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: dxgmms1.sys (dxgmms1!VidMmInterface+0x20E9C)
    Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF8800498E75C, 0xFFFFF88009D3E408, 0xFFFFF88009D3DC60)
    Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
    file path: C:\Windows\system32\drivers\dxgmms1.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: DirectX Graphics MMS
    Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
    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 that cannot be identified at this time.


    On Sat 21/9/2013 12:54:24 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\092113-10623-01.dmp
    This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x37707)
    Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF880047EA707, 0xFFFFF88005FF52A8, 0xFFFFF88005FF4B00)
    Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
    file path: C:\Windows\system32\drivers\dxgmms1.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: DirectX Graphics MMS
    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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.


    --------------------------------------------------------------------------------
    Conclusion
    --------------------------------------------------------------------------------

    3 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

    atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.)

    If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


    Read the topic general suggestions for troubleshooting system crashes for more information.

    Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

    ---

    Is there any way that i can diagnose this problem?


    It's a beta driver, there's only so much that one can expect
  2. Not really, you've reached the extent of the end user analysis by finding out that the AMD drivers were causing it. You have to bear in mind that they are beta drivers, so they may be flawed. I suggest you report it to AMD and just stick with 13.9.
  3. Best answer
    atikmpag.sys is the error I always see on BSOD's and it's a driver error and it's also the same error that I used to always see with ATi cards 15 years ago so I don't think its going to be fixed any time soon.
  4. I am really, really glad that it is identified as a driver issue but not with my hardware (since they are still pretty new, using them for about 9months now).

    I will be reporting them to AMD asap.

    Sticking with the 13.9 drivers. Won't close this thread just in case someone who is encountering the same problem right now comes by this.
  5. Fruitcakefps. I had the same issue (I have the same exact GPU) I just reverted back to the 13.8 beta and it stopped doing that.
  6. Drew010 said:
    Fruitcakefps. I had the same issue (I have the same exact GPU) I just reverted back to the 13.8 beta and it stopped doing that.


    Great! Have you tried using the 13.9 WHQL drivers ?
  7. fruitcakefps said:
    Drew010 said:
    Fruitcakefps. I had the same issue (I have the same exact GPU) I just reverted back to the 13.8 beta and it stopped doing that.


    Great! Have you tried using the 13.9 WHQL drivers ?


    I have not
  8. Drew010 said:
    fruitcakefps said:
    Drew010 said:
    Fruitcakefps. I had the same issue (I have the same exact GPU) I just reverted back to the 13.8 beta and it stopped doing that.


    Great! Have you tried using the 13.9 WHQL drivers ?


    I have not


    You should try it! It's the latest stable drivers :)
  9. fruitcakefps said:
    Drew010 said:
    fruitcakefps said:
    Drew010 said:
    Fruitcakefps. I had the same issue (I have the same exact GPU) I just reverted back to the 13.8 beta and it stopped doing that.


    Great! Have you tried using the 13.9 WHQL drivers ?


    I have not



    You should try it! It's the latest stable drivers :)



    Yeah but they don't have the frame pacing that is in the 13.8 beta
  10. Drew010 said:
    fruitcakefps said:
    Drew010 said:
    fruitcakefps said:
    Drew010 said:
    Fruitcakefps. I had the same issue (I have the same exact GPU) I just reverted back to the 13.8 beta and it stopped doing that.


    Great! Have you tried using the 13.9 WHQL drivers ?


    I have not



    You should try it! It's the latest stable drivers :)



    Yeah but they don't have the frame pacing that is in the 13.8 beta


    If you aren't using crossfire, frame pacing wouldn't make any change though.
  11. fruitcakefps said:
    Drew010 said:
    fruitcakefps said:
    Drew010 said:
    fruitcakefps said:
    Drew010 said:
    Fruitcakefps. I had the same issue (I have the same exact GPU) I just reverted back to the 13.8 beta and it stopped doing that.


    Great! Have you tried using the 13.9 WHQL drivers ?


    I have not



    You should try it! It's the latest stable drivers :)



    Yeah but they don't have the frame pacing that is in the 13.8 beta


    If you aren't using crossfire, frame pacing wouldn't make any change though.


    Occasionally I stick a 7870 XT in crossfire just for fun =P
Ask a new question

Read More

Windows Blue Screen AMD Graphics