Windows 8 and 8.1 Forums


Random BSOD related to atikmdag.sys

  1. #1


    Posts : 1
    Windows 8 64 bit

    Random BSOD related to atikmdag.sys


    My computer was fine until recently. I moved out of my college dorm and in with one of my friends, my computer would crash to a blackscreen at random points after i opened the desktop app. I fiddled with startup settings and deleted all recently installed apps and drivers, reinstalling drivers afterwards and it appeared to have solved the problem. A few days later i went to play minecraft and while it was trying to load the map data, the game bluescreened, giving me the dpc watchdog timer error. At first it was only when trying to load minecraft, but it has since progressed to almost any game, (heart of the swarm starcraft 2 randomly, dark souls randomly... etc) but now it is happening at random times when there absolutley no programs running , ill leave the room and come back to find my computer on the login screen. when i run whocrashed afterwards it creates to reports at each time of a bsod, one of them saying it doesnt know what caused it the other says the likeley cause is the atikmdag.sys. Ive uninstalled and reinstalled all the drivers i could think of and combed the forums looking for people with a similar problem and although ive found several similar nothing ive found has solved the problem, including deleting all of the amd drivers and reinstalling them without catalyst and with catalyst.
    This is about to convince me to go back to windows 7 although i love windows 8 and it worked wonderfully until i moved. Im a junior electrical engineering student so i know enough about computers to get by but please explain any possible fixes well.

      My System SpecsSystem Spec

  2. #2


    Posts : 5,139
    Win8.1Pro - Finally!!!


    We've seen a number of BSOD issues with SSD's. Here's the information that I've compiled so far:
    There's not a whole bunch available to test SSD's. The "easiest" test is to remove the SSD, install a platter-based hard drive, install Windows and test for stability that way.

    Here's some suggestions:
    - Update the SSD's firmware to the latest available version (VERY IMPORTANT!!!)
    - Update the motherboard controllers drivers to the latest available version from the controller manufacturer (NOT the mobo manufacturer unless you can't find any on the controller manufacturer's website). Be sure to update ALL controllers on the motherboard! I STRONGLY suggest not using controller drivers older than mid-2012 with SSD's.
    - Slow the memory (RAM) down to the next slower speed (I've only seen one person who claimed that this worked for them).
    - Use any manufacturer's utilities that you may have. If you don't have any, then try this free one (I haven't used it myself): Crystal Dew World
    ....NOTE: Recently (Nov 2011) we had BSOD issues with the Marvell 91xx controller and an SSD. You may have to switch controllers also.
    - Replace the SSD with a platter based hard drive and see if that stops the BSOD's. If it does, then it's likely that there's a problem with the SSD OR an incompatibility with your system.
    06 Dec 2011 - This post tends to confirm issues with certain SSD chipsets and certain controllers - [SOLVED] cant find the cause of BSOD F4 - Tech Support Forum
    05 Jan 2013 - very interesting post about difficulties with the Marvell controllers even when not connected to the SSD drives: https://www.eightforums.com/bsod-cra...tml#post169956
    27 Feb 2013 - I'm starting to see much better reliability with SSD's using current (mid-2012 and later) storage drivers. I have withdrawn my objections to using these devices in everyday systems.
    Unusual pattern of errors here. They seem to point at both your mouse and your video.
    Let's start with the mouse driver first. If you don't need any special features on your mouse, just uninstall the mouse software and use the Windows drivers (it's a Primax/Dell USB Optical Mouse driver ). If you do need the features, then:
    - download a fresh copy of the latest, Win8 compatible drivers from the manufacturer's website
    - uninstall the current drivers
    - install the freshly downloaded drivers
    - monitor for further BSOD's

    As for the video errors, start with this:
    AMD OverDrive (AODDriver2.sys) is either a stand-alone application, or a component of the AMD VISION Engine Control Center. This driver is known to cause BSOD's on some Windows systems.
    Please un-install all AMD/ATI video stuff from Control Panel...Programs...Un-install a program
    Then, download (but DO NOT install) a fresh copy of the ATI drivers from Global Provider of Innovative Graphics, Processors and Media Solutions | AMD (in the upper right corner of the page)
    Use this procedure to install the DRIVER ONLY: ATI video cards - DRIVER ONLY installation procedure - Sysnative Forums

    If the device (AODDriver or AODDriver4.01) remains a problem, open Device Manager, select the "View" item.
    Then select "Show hidden devices" and scroll down to the Non-Plug and Play Drivers section.
    Locate the AODDriver entry, right click on it and select "Un-install". Reboot for changes to take affect.
    Sometimes the driver remains and continues to cause BSOD's. If this is the case for you, post back and we'll give further instructions for safely removing it.

    If overclocking, please stop. Remove the overclock and return the system to stock/standard values while we're troubleshooting. Once the system is stable again, feel free to resume the overclocking.

    Then try the fixes listed here: Video TDR Timeout - 0x116 + 0x117 - Sysnative Forums

    Let's see how that works. If the BSOD's continue, please post back for further suggestions.

    Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

    NMgamingms.sys Fri Jul 24 04:55:08 2009 (4A6976EC)
    Primax/ Dell USB Optical Mouse driver (CHECK OEM - system manufacturer)
    http://www.carrona.org/drivers/driver.php?id=NMgamingms.sys

    LGBusEnum.sys Mon Nov 23 20:36:48 2009 (4B0B38B0)
    Logitech Keyboard
    http://www.carrona.org/drivers/driver.php?id=LGBusEnum.sys

    LGVirHid.sys Mon Nov 23 20:36:48 2009 (4B0B38B0)
    Logitech Gamepanel Virtual HID Device Driver
    http://www.carrona.org/drivers/driver.php?id=LGVirHid.sys

    DrvAgent64.SYS Mon Dec 14 05:23:26 2009 (4B26121E)
    FLEXnet Licensing Service 64 - Acresso Software Inc.
    http://www.carrona.org/drivers/driver.php?id=DrvAgent64.SYS

    windrvr6.sys Sun Jan 17 13:02:30 2010 (4B5350B6)
    WinDriver or Alohabob USB Bridge Cable Driver
    http://www.carrona.org/drivers/driver.php?id=windrvr6.sys

    vmwvusb.sys Wed Jul 13 21:32:41 2011 (4E1E4739)
    VMware USB driver
    vmwvusb.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.

    amdide64.sys Sun Dec 18 20:43:17 2011 (4EEE96B5)
    AMD SATA Controller driver
    http://www.carrona.org/drivers/driver.php?id=amdide64.sys

    VERY IMPORTANT - REMOVE THIS:
    NTIOLib_X64.sys Thu Oct 25 07:46:40 2012 (508926A0)
    MSI Afterburner driver (known BSOD issues with Windows 7) Also found to be a part of MSI Live Update 5
    http://www.carrona.org/drivers/driver.php?id=NTIOLib_X64.sys



    Analysis:
    The following is for informational purposes only.
    Code:
    **************************Tue Mar 19 16:15:19.766 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\031913-8564-01.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
    System Uptime:0 days 9:44:46.466
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    Probably caused by :atikmdag.sys ( atikmdag+10114f )
    BugCheck 133, {1, 784, 0, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
        DISPATCH_LEVEL or above. The offending component can usually be
        identified with a stack trace.
    Arg2: 0000000000000784, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x133_ISR_atikmdag+10114f
      BIOS Version                  V1.13
      BIOS Release Date             01/12/2012
      Manufacturer                  MSI
      Product Name                  MS-7642
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Mar 19 06:30:08.213 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\031913-10576-01.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
    System Uptime:0 days 4:46:34.914
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    Probably caused by :atikmdag.sys ( atikmdag+1011d1 )
    BugCheck 133, {1, 784, 0, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
        DISPATCH_LEVEL or above. The offending component can usually be
        identified with a stack trace.
    Arg2: 0000000000000784, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x133_ISR_atikmdag+1011d1
      BIOS Version                  V1.13
      BIOS Release Date             01/12/2012
      Manufacturer                  MSI
      Product Name                  MS-7642
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Mar 19 01:43:08.451 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\031913-9235-01.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
    System Uptime:0 days 2:46:57.151
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    Probably caused by :atikmdag.sys ( atikmdag+fa39f )
    BugCheck 133, {1, 784, 0, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
        DISPATCH_LEVEL or above. The offending component can usually be
        identified with a stack trace.
    Arg2: 0000000000000784, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x133_ISR_atikmdag+fa39f
      BIOS Version                  V1.13
      BIOS Release Date             01/12/2012
      Manufacturer                  MSI
      Product Name                  MS-7642
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon Mar 18 22:55:47.067 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\031813-8361-01.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
    System Uptime:0 days 0:47:27.767
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    Probably caused by :atikmdag.sys ( atikmdag+fa38f )
    BugCheck 133, {1, 784, 0, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
        DISPATCH_LEVEL or above. The offending component can usually be
        identified with a stack trace.
    Arg2: 0000000000000784, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x133_ISR_atikmdag+fa38f
      BIOS Version                  V1.13
      BIOS Release Date             01/12/2012
      Manufacturer                  MSI
      Product Name                  MS-7642
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon Mar 18 22:07:55.065 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\031813-10093-01.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
    System Uptime:0 days 1:56:58.765
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    Probably caused by :atikmdag.sys ( atikmdag+fa386 )
    BugCheck 133, {1, 784, 0, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
        DISPATCH_LEVEL or above. The offending component can usually be
        identified with a stack trace.
    Arg2: 0000000000000784, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x133_ISR_atikmdag+fa386
      BIOS Version                  V1.13
      BIOS Release Date             01/12/2012
      Manufacturer                  MSI
      Product Name                  MS-7642
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon Mar 18 17:13:43.802 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\031813-8424-01.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
    System Uptime:0 days 13:09:28.503
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    Probably caused by :atikmdag.sys ( atikmdag+1011bf )
    BugCheck 133, {1, 784, 0, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
        DISPATCH_LEVEL or above. The offending component can usually be
        identified with a stack trace.
    Arg2: 0000000000000784, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x133_ISR_atikmdag+1011bf
      BIOS Version                  V1.12
      BIOS Release Date             10/11/2011
      Manufacturer                  MSI
      Product Name                  MS-7642
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon Mar 18 04:03:49.675 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\031813-8314-01.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
    System Uptime:0 days 3:39:26.375
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    Probably caused by :atikmdag.sys ( atikmdag+1011cd )
    BugCheck 133, {1, 784, 0, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
        DISPATCH_LEVEL or above. The offending component can usually be
        identified with a stack trace.
    Arg2: 0000000000000784, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x133_ISR_atikmdag+1011cd
      BIOS Version                  V1.12
      BIOS Release Date             10/11/2011
      Manufacturer                  MSI
      Product Name                  MS-7642
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon Mar 18 00:09:26.939 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\031713-8533-01.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
    System Uptime:0 days 0:01:31.639
    *** WARNING: Unable to verify timestamp for NMgamingms.sys
    *** ERROR: Module load completed but symbols could not be loaded for NMgamingms.sys
    Probably caused by :NMgamingms.sys ( NMgamingms+1cbb )
    BugCheck 139, {3, fffff880031864e0, fffff88003186438, 0}
    BugCheck Info: KERNEL_SECURITY_CHECK_FAILURE (139)
    Arguments: 
    Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
    Arg2: fffff880031864e0, Address of the trap frame for the exception that caused the bugcheck
    Arg3: fffff88003186438, Address of the exception record for the exception that caused the bugcheck
    Arg4: 0000000000000000, Reserved
    BUGCHECK_STR:  0x139
    DEFAULT_BUCKET_ID:  LIST_ENTRY_CORRUPT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x139_3_NMgamingms+1cbb
      BIOS Version                  V1.12
      BIOS Release Date             10/11/2011
      Manufacturer                  MSI
      Product Name                  MS-7642
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon Mar 18 00:05:18.259 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\031713-10015-01.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
    System Uptime:0 days 0:30:18.960
    *** WARNING: Unable to verify timestamp for NMgamingms.sys
    *** ERROR: Module load completed but symbols could not be loaded for NMgamingms.sys
    Probably caused by :NMgamingms.sys ( NMgamingms+1cbb )
    BugCheck 139, {3, fffff88002f634e0, fffff88002f63438, 0}
    BugCheck Info: KERNEL_SECURITY_CHECK_FAILURE (139)
    Arguments: 
    Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
    Arg2: fffff88002f634e0, Address of the trap frame for the exception that caused the bugcheck
    Arg3: fffff88002f63438, Address of the exception record for the exception that caused the bugcheck
    Arg4: 0000000000000000, Reserved
    BUGCHECK_STR:  0x139
    DEFAULT_BUCKET_ID:  LIST_ENTRY_CORRUPT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x139_3_NMgamingms+1cbb
      BIOS Version                  V1.12
      BIOS Release Date             10/11/2011
      Manufacturer                  MSI
      Product Name                  MS-7642
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sun Mar 17 23:34:32.991 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\031713-8923-01.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
    System Uptime:0 days 0:20:45.692
    *** ERROR: Module load completed but symbols could not be loaded for volmgr.sys
    *** ERROR: Module load completed but symbols could not be loaded for partmgr.sys
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    Probably caused by :memory_corruption
    BugCheck 7A, {fffff6fc40007008, ffffffffc00000c0, 15819a860, fffff88000e01000}
    BugCheck Info: KERNEL_DATA_INPAGE_ERROR (7a)
    Arguments: 
    Arg1: fffff6fc40007008, lock type that was held (value 1,2,3, or PTE address)
    Arg2: ffffffffc00000c0, error status (normally i/o status code)
    Arg3: 000000015819a860, current process (virtual address for lock type 3, or PTE)
    Arg4: fffff88000e01000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)
    BUGCHECK_STR:  0x7a_c00000c0
    PROCESS_NAME:  System
        fffff88000e01000-fffff88000e010e2  227 bytes*** ERROR: Module load completed but symbols could not be loaded for volmgrx.sys
    FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE_4096
      BIOS Version                  V1.12
      BIOS Release Date             10/11/2011
      Manufacturer                  MSI
      Product Name                  MS-7642
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sun Mar 17 23:13:18.515 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\031713-10264-01.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
    System Uptime:0 days 20:43:40.215
    *** WARNING: Unable to verify timestamp for NMgamingms.sys
    *** ERROR: Module load completed but symbols could not be loaded for NMgamingms.sys
    Probably caused by :NMgamingms.sys ( NMgamingms+1cbb )
    BugCheck 139, {3, fffff8800b5b84e0, fffff8800b5b8438, 0}
    BugCheck Info: KERNEL_SECURITY_CHECK_FAILURE (139)
    Arguments: 
    Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
    Arg2: fffff8800b5b84e0, Address of the trap frame for the exception that caused the bugcheck
    Arg3: fffff8800b5b8438, Address of the exception record for the exception that caused the bugcheck
    Arg4: 0000000000000000, Reserved
    BUGCHECK_STR:  0x139
    DEFAULT_BUCKET_ID:  LIST_ENTRY_CORRUPT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x139_3_NMgamingms+1cbb
      BIOS Version                  V1.12
      BIOS Release Date             10/11/2011
      Manufacturer                  MSI
      Product Name                  MS-7642
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sun Mar 17 02:29:12.652 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\031713-8689-01.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
    System Uptime:0 days 0:09:41.353
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    Probably caused by :atikmdag.sys ( atikmdag+10115a )
    BugCheck 133, {1, 784, 0, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
        DISPATCH_LEVEL or above. The offending component can usually be
        identified with a stack trace.
    Arg2: 0000000000000784, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x133_ISR_atikmdag+10115a
      BIOS Version                  V1.12
      BIOS Release Date             10/11/2011
      Manufacturer                  MSI
      Product Name                  MS-7642
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Mar 16 04:26:04.431 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\031613-9906-01.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
    System Uptime:0 days 0:03:21.132
    *** ERROR: Module load completed but symbols could not be loaded for HDAudBus.sys
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    Probably caused by :HDAudBus.sys ( HDAudBus+13d7 )
    BugCheck 133, {1, 784, 0, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
        DISPATCH_LEVEL or above. The offending component can usually be
        identified with a stack trace.
    Arg2: 0000000000000784, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x133_ISR_HDAudBus+13d7
      BIOS Version                  V1.12
      BIOS Release Date             10/11/2011
      Manufacturer                  MSI
      Product Name                  MS-7642
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Mar 16 04:22:17.928 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\031613-10452-01.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
    System Uptime:0 days 0:02:14.629
    *** WARNING: Unable to verify timestamp for NMgamingms.sys
    *** ERROR: Module load completed but symbols could not be loaded for NMgamingms.sys
    Probably caused by :NMgamingms.sys ( NMgamingms+1cbb )
    BugCheck 139, {3, fffff8800b4534e0, fffff8800b453438, 0}
    BugCheck Info: KERNEL_SECURITY_CHECK_FAILURE (139)
    Arguments: 
    Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
    Arg2: fffff8800b4534e0, Address of the trap frame for the exception that caused the bugcheck
    Arg3: fffff8800b453438, Address of the exception record for the exception that caused the bugcheck
    Arg4: 0000000000000000, Reserved
    BUGCHECK_STR:  0x139
    DEFAULT_BUCKET_ID:  LIST_ENTRY_CORRUPT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x139_3_NMgamingms+1cbb
      BIOS Version                  V1.12
      BIOS Release Date             10/11/2011
      Manufacturer                  MSI
      Product Name                  MS-7642
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Mar 16 04:19:38.186 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\031613-10920-01.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
    System Uptime:0 days 0:01:04.886
    *** WARNING: Unable to verify timestamp for NMgamingms.sys
    *** ERROR: Module load completed but symbols could not be loaded for NMgamingms.sys
    Probably caused by :NMgamingms.sys ( NMgamingms+1cbb )
    BugCheck 139, {3, fffff88002f5c4e0, fffff88002f5c438, 0}
    BugCheck Info: KERNEL_SECURITY_CHECK_FAILURE (139)
    Arguments: 
    Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
    Arg2: fffff88002f5c4e0, Address of the trap frame for the exception that caused the bugcheck
    Arg3: fffff88002f5c438, Address of the exception record for the exception that caused the bugcheck
    Arg4: 0000000000000000, Reserved
    BUGCHECK_STR:  0x139
    DEFAULT_BUCKET_ID:  LIST_ENTRY_CORRUPT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x139_3_NMgamingms+1cbb
      BIOS Version                  V1.12
      BIOS Release Date             10/11/2011
      Manufacturer                  MSI
      Product Name                  MS-7642
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Mar 16 04:18:08.408 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\031613-10935-01.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
    System Uptime:0 days 0:24:49.108
    *** WARNING: Unable to verify timestamp for NMgamingms.sys
    *** ERROR: Module load completed but symbols could not be loaded for NMgamingms.sys
    Probably caused by :NMgamingms.sys ( NMgamingms+1cbb )
    BugCheck 139, {3, fffff8800cd644e0, fffff8800cd64438, 0}
    BugCheck Info: KERNEL_SECURITY_CHECK_FAILURE (139)
    Arguments: 
    Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
    Arg2: fffff8800cd644e0, Address of the trap frame for the exception that caused the bugcheck
    Arg3: fffff8800cd64438, Address of the exception record for the exception that caused the bugcheck
    Arg4: 0000000000000000, Reserved
    BUGCHECK_STR:  0x139
    DEFAULT_BUCKET_ID:  LIST_ENTRY_CORRUPT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x139_3_NMgamingms+1cbb
      BIOS Version                  V1.12
      BIOS Release Date             10/11/2011
      Manufacturer                  MSI
      Product Name                  MS-7642
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Mar 16 03:52:54.023 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\031613-9422-01.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
    System Uptime:0 days 0:19:11.724
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    Probably caused by :atikmdag.sys ( atikmdag+fa3c2 )
    BugCheck 133, {1, 784, 0, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
        DISPATCH_LEVEL or above. The offending component can usually be
        identified with a stack trace.
    Arg2: 0000000000000784, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x133_ISR_atikmdag+fa3c2
      BIOS Version                  V1.12
      BIOS Release Date             10/11/2011
      Manufacturer                  MSI
      Product Name                  MS-7642
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Mar 16 03:33:16.424 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\031613-8954-01.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
    System Uptime:0 days 0:18:07.124
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    Probably caused by :atikmdag.sys ( atikmdag+fa375 )
    BugCheck 133, {1, 784, 0, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
        DISPATCH_LEVEL or above. The offending component can usually be
        identified with a stack trace.
    Arg2: 0000000000000784, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x133_ISR_atikmdag+fa375
      BIOS Version                  V1.12
      BIOS Release Date             10/11/2011
      Manufacturer                  MSI
      Product Name                  MS-7642
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Mar 16 03:14:44.446 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\031613-8221-01.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
    System Uptime:0 days 0:09:30.146
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    Probably caused by :atikmdag.sys ( atikmdag+fa328 )
    BugCheck 133, {1, 784, 0, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
        DISPATCH_LEVEL or above. The offending component can usually be
        identified with a stack trace.
    Arg2: 0000000000000784, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x133_ISR_atikmdag+fa328
      BIOS Version                  V1.12
      BIOS Release Date             10/11/2011
      Manufacturer                  MSI
      Product Name                  MS-7642
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Mar 16 03:04:49.804 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\031613-8236-01.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
    System Uptime:0 days 0:17:37.504
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    Probably caused by :atikmdag.sys ( atikmdag+fa38f )
    BugCheck 133, {1, 784, 0, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
        DISPATCH_LEVEL or above. The offending component can usually be
        identified with a stack trace.
    Arg2: 0000000000000784, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x133_ISR_atikmdag+fa38f
      BIOS Version                  V1.12
      BIOS Release Date             10/11/2011
      Manufacturer                  MSI
      Product Name                  MS-7642
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Mar 16 02:46:46.902 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\031613-8299-01.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
    System Uptime:0 days 0:23:24.602
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    Probably caused by :atikmdag.sys ( atikmdag+fa32f )
    BugCheck 133, {1, 784, 0, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
        DISPATCH_LEVEL or above. The offending component can usually be
        identified with a stack trace.
    Arg2: 0000000000000784, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x133_ISR_atikmdag+fa32f
      BIOS Version                  V1.12
      BIOS Release Date             10/11/2011
      Manufacturer                  MSI
      Product Name                  MS-7642
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Mar 16 02:22:57.305 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\031613-8439-01.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
    System Uptime:0 days 0:03:03.005
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    Probably caused by :atikmdag.sys ( atikmdag+fa3c2 )
    BugCheck 133, {1, 784, 0, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
        DISPATCH_LEVEL or above. The offending component can usually be
        identified with a stack trace.
    Arg2: 0000000000000784, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x133_ISR_atikmdag+fa3c2
      BIOS Version                  V1.12
      BIOS Release Date             10/11/2011
      Manufacturer                  MSI
      Product Name                  MS-7642
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Mar 16 02:19:28.894 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\031613-8330-01.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
    System Uptime:0 days 0:11:05.594
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    Probably caused by :atikmdag.sys ( atikmdag+fa2e4 )
    BugCheck 133, {1, 784, 0, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
        DISPATCH_LEVEL or above. The offending component can usually be
        identified with a stack trace.
    Arg2: 0000000000000784, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x133_ISR_atikmdag+fa2e4
      BIOS Version                  V1.12
      BIOS Release Date             10/11/2011
      Manufacturer                  MSI
      Product Name                  MS-7642
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Mar 16 02:07:51.551 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\031613-8283-01.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
    System Uptime:0 days 0:42:15.251
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    Probably caused by :atikmdag.sys ( atikmdag+fa2d2 )
    BugCheck 133, {1, 784, 0, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
        DISPATCH_LEVEL or above. The offending component can usually be
        identified with a stack trace.
    Arg2: 0000000000000784, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x133_ISR_atikmdag+fa2d2
      BIOS Version                  V1.12
      BIOS Release Date             10/11/2011
      Manufacturer                  MSI
      Product Name                  MS-7642
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Mar 16 01:24:34.338 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\031613-9094-01.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
    System Uptime:0 days 1:21:40.039
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    Probably caused by :atikmdag.sys ( atikmdag+fa328 )
    BugCheck 133, {1, 784, 0, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
        DISPATCH_LEVEL or above. The offending component can usually be
        identified with a stack trace.
    Arg2: 0000000000000784, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x133_ISR_atikmdag+fa328
      BIOS Version                  V1.12
      BIOS Release Date             10/11/2011
      Manufacturer                  MSI
      Product Name                  MS-7642
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Mar 16 00:01:52.645 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\031513-11497-01.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
    System Uptime:2 days 3:39:45.287
    *** ERROR: Module load completed but symbols could not be loaded for atapi.sys
    Probably caused by :ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+234cc )
    BugCheck 7A, {fffff6fc40062df8, ffffffffc000000e, 138ab0be0, fffff8800c5bf000}
    BugCheck Info: KERNEL_DATA_INPAGE_ERROR (7a)
    Arguments: 
    Arg1: fffff6fc40062df8, lock type that was held (value 1,2,3, or PTE address)
    Arg2: ffffffffc000000e, error status (normally i/o status code)
    Arg3: 0000000138ab0be0, current process (virtual address for lock type 3, or PTE)
    Arg4: fffff8800c5bf000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)
    DISK_HARDWARE_ERROR: There was error with disk hardware
    BUGCHECK_STR:  0x7a_c000000e
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x7a_c000000e_nt!_??_::FNODOBFM::_string_
      BIOS Version                  V1.12
      BIOS Release Date             10/11/2011
      Manufacturer                  MSI
      Product Name                  MS-7642
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon Mar 11 03:56:02.989 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\031113-10545-01.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
    System Uptime:0 days 0:45:49.689
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    Probably caused by :atikmdag.sys ( atikmdag+fa37c )
    BugCheck 133, {1, 784, 0, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
        DISPATCH_LEVEL or above. The offending component can usually be
        identified with a stack trace.
    Arg2: 0000000000000784, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x133_ISR_atikmdag+fa37c
      BIOS Version                  V1.12
      BIOS Release Date             10/11/2011
      Manufacturer                  MSI
      Product Name                  MS-7642
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon Mar 11 02:41:02.199 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\031113-9204-01.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
    System Uptime:0 days 2:40:07.899
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    Probably caused by :atikmdag.sys ( atikmdag+fa36b )
    BugCheck 133, {1, 784, 0, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
        DISPATCH_LEVEL or above. The offending component can usually be
        identified with a stack trace.
    Arg2: 0000000000000784, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x133_ISR_atikmdag+fa36b
      BIOS Version                  V1.12
      BIOS Release Date             10/11/2011
      Manufacturer                  MSI
      Product Name                  MS-7642
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    
    3rd Party Drivers:
    The following is for information purposes only.
    Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
    Code:
    **************************Tue Mar 19 16:15:19.766 2013 (UTC - 4:00)**************************
    NMgamingms.sys         Fri Jul 24 04:55:08 2009 (4A6976EC)
    LGBusEnum.sys          Mon Nov 23 20:36:48 2009 (4B0B38B0)
    LGVirHid.sys           Mon Nov 23 20:36:48 2009 (4B0B38B0)
    windrvr6.sys           Sun Jan 17 13:02:30 2010 (4B5350B6)
    nusb3hub.sys           Thu Feb 10 00:52:32 2011 (4D537D20)
    nusb3xhc.sys           Thu Feb 10 00:52:33 2011 (4D537D21)
    vmwvusb.sys            Wed Jul 13 21:32:41 2011 (4E1E4739)
    amdide64.sys           Sun Dec 18 20:43:17 2011 (4EEE96B5)
    LPCFilter.sys          Tue Mar  6 09:58:27 2012 (4F562613)
    AODDriver2.sys         Thu Apr  5 05:23:37 2012 (4F7D6499)
    GEARAspiWDM.sys        Thu May  3 15:56:17 2012 (4FA2E2E1)
    sthid.sys              Fri Oct 19 01:28:41 2012 (5080E509)
    NTIOLib_X64.sys        Thu Oct 25 07:46:40 2012 (508926A0)
    AtihdW86.sys           Wed Dec 12 12:20:30 2012 (50C8BCDE)
    atikmpag.sys           Wed Dec 19 14:32:55 2012 (50D21667)
    atikmdag.sys           Wed Dec 19 15:38:55 2012 (50D225DF)
    Rt630x64.sys           Thu Dec 27 19:04:06 2012 (50DCE1F6)
    cmdhlp.sys             Wed Jan 16 14:26:10 2013 (50F6FED2)
    inspect.sys            Wed Jan 16 14:26:10 2013 (50F6FED2)
    cmderd.sys             Wed Jan 16 14:26:12 2013 (50F6FED4)
    cmdguard.sys           Wed Jan 16 14:27:00 2013 (50F6FF04)
    netr28x.sys            Mon Feb 18 17:48:30 2013 (5122AFBE)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Mar 19 06:30:08.213 2013 (UTC - 4:00)**************************
    NTIOLib_X64.sys        Mon Sep 19 23:09:19 2011 (4E7803DF)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Mar 19 01:43:08.451 2013 (UTC - 4:00)**************************
    DrvAgent64.SYS         Mon Dec 14 05:23:26 2009 (4B26121E)
    atikmpag.sys           Thu Sep 27 21:12:52 2012 (5064F994)
    atikmdag.sys           Thu Sep 27 22:14:57 2012 (50650821)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon Mar 18 00:09:26.939 2013 (UTC - 4:00)**************************
    BthLEEnum.sys          Wed Jul 25 22:25:02 2012 (5010AA7E)
    btwl2cap.sys           Thu Jul 26 11:14:41 2012 (50115EE1)
    bcbtums.sys            Fri Aug 24 17:21:36 2012 (5037F060)
    btwavdt.sys            Sun Sep 16 01:16:14 2012 (5055609E)
    btwrchid.sys           Sun Sep 16 01:17:08 2012 (505560D4)
    btwaudio.sys           Tue Sep 18 23:04:54 2012 (50593656)
    btwampfl.sys           Tue Sep 25 15:58:15 2012 (50620CD7)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Mar 16 03:52:54.023 2013 (UTC - 4:00)**************************
    AODDriver2.sys         Tue Mar  6 04:55:00 2012 (4F55DEF4)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon Mar 11 03:56:02.989 2013 (UTC - 4:00)**************************
    AODDriver2.sys         Mon Dec 19 02:30:03 2011 (4EEEE7FB)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon Mar 11 02:41:02.199 2013 (UTC - 4:00)**************************
    Rt630x64.sys           Wed Oct 19 08:12:55 2011 (4E9EBEC7)
    
    http://www.carrona.org/drivers/driver.php?id=NMgamingms.sys
    http://www.carrona.org/drivers/driver.php?id=LGBusEnum.sys
    http://www.carrona.org/drivers/driver.php?id=LGVirHid.sys
    http://www.carrona.org/drivers/driver.php?id=windrvr6.sys
    http://www.carrona.org/drivers/driver.php?id=nusb3hub.sys
    http://www.carrona.org/drivers/driver.php?id=nusb3xhc.sys
    vmwvusb.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    http://www.carrona.org/drivers/driver.php?id=amdide64.sys
    http://www.carrona.org/drivers/driver.php?id=LPCFilter.sys
    http://www.carrona.org/drivers/driver.php?id=AODDriver2.sys
    http://www.carrona.org/drivers/driver.php?id=GEARAspiWDM.sys
    sthid.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    http://www.carrona.org/drivers/driver.php?id=NTIOLib_X64.sys
    http://www.carrona.org/drivers/driver.php?id=AtihdW86.sys
    http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
    http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
    http://www.carrona.org/drivers/driver.php?id=Rt630x64.sys
    http://www.carrona.org/drivers/driver.php?id=cmdhlp.sys
    http://www.carrona.org/drivers/driver.php?id=inspect.sys
    http://www.carrona.org/drivers/driver.php?id=cmderd.sys
    http://www.carrona.org/drivers/driver.php?id=cmdguard.sys
    http://www.carrona.org/drivers/driver.php?id=netr28x.sys
    http://www.carrona.org/drivers/driver.php?id=NTIOLib_X64.sys
    http://www.carrona.org/drivers/driver.php?id=DrvAgent64.SYS
    http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
    http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
    BthLEEnum.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    http://www.carrona.org/drivers/driver.php?id=btwl2cap.sys
    http://www.carrona.org/drivers/driver.php?id=bcbtums.sys
    http://www.carrona.org/drivers/driver.php?id=btwavdt.sys
    http://www.carrona.org/drivers/driver.php?id=btwrchid.sys
    http://www.carrona.org/drivers/driver.php?id=btwaudio.sys
    http://www.carrona.org/drivers/driver.php?id=btwampfl.sys
    http://www.carrona.org/drivers/driver.php?id=AODDriver2.sys
    http://www.carrona.org/drivers/driver.php?id=AODDriver2.sys
    http://www.carrona.org/drivers/driver.php?id=Rt630x64.sys
      My System SpecsSystem Spec

Random BSOD related to atikmdag.sys
Related Threads
Hi, I just signed up to the forum as I have exhausted my own efforts at solving a seemingly known issue with ATI drivers BSOD'ing my system. I RDP to the effected system and use that method 99% of the times. At random occassions my system BSOD's giving a few different reasons as attached and...
Solved Yet another atikmdag.sys BSOD... in BSOD Crashes and Debugging
Dear Support Team, I am aware that there are a lot of topics around the WWW covering exactly this problem. And trust me, I already spent hours to lookup solutions. And I tried a lot. It's been a long time now that I need to create a case to get my problem fixed.So I was searching for the right...
Windows 8.1 Pro BSOD; (atikmdag.sys) in BSOD Crashes and Debugging
SF_10-09-2014 SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (atikmdag.sys) Hello! I recently upgraded my hard drive+fresh install and since I've experienced a couple BSoD errors. I believe both times the errors occurred I was watching some plugin-forced html5 youtube videos. Also every BSoD error...
hello dear please check my bsod my error on blue screen::system_thread_exception_not_handled(atikmdag.sys)
Random BSOD - possible video card related? in BSOD Crashes and Debugging
**Please ignore or remove this thread, I uploaded the wrong file and am at work, so cannot upload again** Sorry for the inconveniance..will update later. Hello all, first time, long time. I keep getting errors of the BSOD variety lately, and i have not changed anything of interest. The...
Random BSOD's Possible Sleep/Hibernate Related in BSOD Crashes and Debugging
Last few nights, maybe a week now, after a fresh install of window 8 Pro I will wake my PC up and it'll have a report it wants to send to MS becuase of a BSOD. I check events and about the only thing I can see that may be the cause is "Windows failed to resume from hibernate with error status...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook