Windows 8 and 8.1 Forums


BSOD Crossfire 290 0x100000ea

  1. #1


    Posts : 24
    Windows 8 Pro 64bit

    BSOD Crossfire 290 0x100000ea


    Hello having big issue with my PC at the moment.. Any time I run crossfire and play a game abut 10-30mins it will either BSOD or driver stopped responding.. In my testing running each GPU alone they seem to work fine..

    My system is
    Windows 8.1
    i7 2600k stock
    Asus p8z77 WS ------------ I think the issue might be here, this board isn't fully Windows 8.1 the drivers I have got are from the part Manufactures. It also runs a PLX CHIPSet to get faster PCI-e Lanes
    Samsung Evo 250GB
    Crossfire 290x + 290 ---------------------- The 290x was a replacement from another 290 that I had the same issue with I sent it back and got a 290x.. Now could I have two GPUs doing the same issue? The was both bought same time so same Batch. Surely though both doing same thing??? This why I believe my issue is something else..
    SuperFlower 1000w PSU
    16GB DDR3 Kingston Ram ----- Tried running a stock and also XMP profile..

    The crashing has been a mix of system freeze alt-tab close game - Driver stopped responding.
    A complete system lockup resulting in either me force restart or waiting for BSOD THREAD_STUCK_IN_DEVICE_DRIVER
    Or with BF4 case I have had a solid RED SCREEN OF DEATH..

    Any help will be great..


      My System SpecsSystem Spec

  2. #2


    Posts : 24
    Windows 8 Pro 64bit


    Here is the zip logs

    Attachment 59372
      My System SpecsSystem Spec

  3. #3


    Posts : 24
    Windows 8 Pro 64bit


    Anyone??
      My System SpecsSystem Spec

  4. #4


    Posts : 2,480
    Windows 10 Pro x64


    There are traces of two AVs on your system. Please uninstall them both using their removal tools.
    Uninstall software highlighted in red (except Logitech)

    Code:
    LGVirHid.sys Tue Nov 24 02:36:48 2009  (4B0B38B0) 
    Logitech Gamepanel Virtual HID Device Driver 
    http://www.carrona.org/drivers/driver.php?id=LGVirHid.sys 
    
    LGBusEnum.sys  Tue Nov 24 02:36:48 2009 (4B0B38B0) 
    Logitech Keyboard 
    http://www.carrona.org/drivers/driver.php?id=LGBusEnum.sys 
    
    npf.sys Fri  Jun 25 18:50:58 2010 (4C24DE72) 
    
    npf.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. 
    
    AsUpIO.sys Tue Aug 3 04:47:59 2010  (4C57835F) 
    ASUS hardware monitoring software related 
    http://www.carrona.org/drivers/driver.php?id=AsUpIO.sys 
    
    GPU-Z.sys Wed  Oct 6 18:14:37 2010 (4CACA06D) 
    GPU-Z driver (thanks to reventon)  
    http://www.carrona.org/drivers/driver.php?id=GPU-Z.sys 
    
    NTIOLib_X64.sys  Wed Oct 20 08:45:49 2010 (4CBE901D) 
    MSI Afterburner driver (known  BSOD issues with Windows) Also found to be a part of MSI  Live Update 5 & MSI Super Charger[br] [br] Recently (Nov 2014) there have  been numerous instances of this driver in memory dumps. Analysis reveals that  they are scattered throughout the filesystem by the installed MSI command  utilities. For now I suggest uninstalling them all. 
    http://www.carrona.org/drivers/driver.php?id=NTIOLib_X64.sys 
    
    asahci64.sys Thu Jan 5  06:08:19 2012 (4F053043) 
    Asmedia 106x SATA Host Controller Driver 
    http://www.carrona.org/drivers/driver.php?id=asahci64.sys 
    
    mv91cons.sys Wed Jun 6 12:26:38  2012 (4FCF305E) 
    Marvell 91xx Confige Device Driver for 6G SATA Controller  
    http://www.carrona.org/drivers/driver.php?id=mv91cons.sys 
    
    AsIO.sys Wed Aug 22 11:54:47 2012  (5034AC67) 
    Asus PCProbe Utility 
    http://www.carrona.org/drivers/driver.php?id=AsIO.sys 
    
    trufos.sys Wed Mar 6 12:47:58 2013  (51372CEE) 
    
    trufos.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.  
    
    RTCore64.sys Mon Mar 11 06:32:06 2013  (513D6C56) 
    RivaTuner/EVGA Precision/MSI Afterburner (known BSOD issues w/Win7) 
    http://www.carrona.org/drivers/driver.php?id=RTCore64.sys 
    
    e1i63x64.sys Wed Mar 20 08:37:29  2013 (51496739) 
    Intel(R) Gigabit Adapter 
    http://www.carrona.org/drivers/driver.php?id=e1i63x64.sys 
    
    avc3.sys Thu Apr 11 10:31:58 2013  (516674FE) 
    BitDefender Active Virus Control filter driver 
    http://www.carrona.org/drivers/driver.php?id=avc3.sys 
    
    avckf.sys Thu Apr 11 10:35:04 2013  (516675B8) 
    BitDefender Active Virus Control Kernel Filtering driver 
    http://www.carrona.org/drivers/driver.php?id=avckf.sys 
    
    gzflt.sys Mon Apr 22 12:21:00 2013  (51750F0C) 
    BitDefender Gonzales FileSystem Driver 
    http://www.carrona.org/drivers/driver.php?id=gzflt.sys 
    
    ScpVBus.sys Sun May 5 23:31:26 2013  (5186CFAE) 
    Scarlet.Crush Productions Scp Dual Shock 3 Virtual Bus Driver  
    http://www.carrona.org/drivers/driver.php?id=ScpVBus.sys 
    
    bdfwfpf.sys Tue Jul 2 13:03:14  2013 (51D2B372) 
    Bit Defender 
    http://www.carrona.org/drivers/driver.php?id=bdfwfpf.sys 
    
    asmtxhci.sys Fri Aug 16 21:28:42  2013 (520E7D6A) 
    Asmedia USB 3.0 driver 
    http://www.carrona.org/drivers/driver.php?id=asmtxhci.sys 
    
    asmthub3.sys Fri Aug 16 21:28:54  2013 (520E7D76) 
    ASMedia USB 3.0 Hub driver 
    http://www.carrona.org/drivers/driver.php?id=asmthub3.sys 
    
    intelppm.sys Thu Aug 22 10:46:35  2013 (5215CFEB) 
    Intel Processor driver 
    http://www.carrona.org/drivers/driver.php?id=intelppm.sys 
    
    mvxxmm.sys Fri Oct 11 08:50:20  2013 (52579FAC) 
    Marvell Aux NV Bridge DLL - related to mv91xx SCSI HD  Controller 
    http://www.carrona.org/drivers/driver.php?id=mvxxmm.sys 
    
    mvs91xx.sys Fri Oct 11 08:51:23  2013 (52579FEB) 
    Marvell 91xx SATA Controller Driver 
    http://www.carrona.org/drivers/driver.php?id=mvs91xx.sys 
    
    rspLLL64.sys Thu Oct 17 12:56:22  2013 (525FC256) 
    
    rspLLL64.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. 
    
    iqvw64e.sys Thu Nov 14 16:22:43 2013 (5284EAC3)  
    
    iqvw64e.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. 
    
    xusb22.sys Tue Mar 18  09:18:41 2014 (53280161) 
    Xbox 360 Wireless Receiver driver 
    http://www.carrona.org/drivers/driver.php?id=xusb22.sys 
    
    asstor64.sys Wed Mar 26 02:49:44  2014 (53323238) 
    Asmedia ASM-106x Sata 6G controller 
    http://www.carrona.org/drivers/driver.php?id=asstor64.sys 
    
    iaStorA.sys Sat May 3 01:06:56  2014 (53642510) 
    Intel RST (Rapid Storage Technology) driver 
    http://www.carrona.org/drivers/driver.php?id=iaStorA.sys 
    
    AMDACPKSL.SYS Sun Jun 22 04:31:43  2014 (53A6400F) 
    included in the AMD/ATI Catalyst WDM drivers package 
    http://www.carrona.org/drivers/driver.php?id=AMDACPKSL.SYS 
    
    AtihdWB6.sys Sun Jun 22 04:32:00  2014 (53A64020) 
    AMD High Definition Audio Function Driver 
    http://www.carrona.org/drivers/driver.php?id=AtihdWB6.sys 
    
    CMUSBDAC.sys Thu Aug 21 08:58:25  2014 (53F59891) 
    C-Media USB Audio Class 1.0 and 2.0 DAC Device Driver 
    http://www.carrona.org/drivers/driver.php?id=CMUSBDAC.sys 
    
    TeeDriverx64.sys Tue Sep 23  22:01:14 2014 (5421D18A) 
    Intel Management Engine Interface driver 
    http://www.carrona.org/drivers/driver.php?id=TeeDriverx64.sys 
    
    asstahci64.sys Thu Oct 23  04:42:16 2014 (54486B08) 
    
    asstahci64.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. 
    
    cthda.sys Mon Nov 17 06:06:55 2014  (5469826F) 
    Sound Blaster HDAudio driver 
    http://www.carrona.org/drivers/driver.php?id=cthda.sys 
    
    cthdb.sys Mon Nov 17 06:07:14 2014  (54698282) 
    Sound Blaster Recon3D PCIe Audio driver 
    http://www.carrona.org/drivers/driver.php?id=cthdb.sys 
    
    atikmpag.sys Fri Nov 21 03:08:54  2014 (546E9EB6) 
    ATI Video driver (remove the Catalyst Control Center and  only install the Display Driver) 
    http://www.carrona.org/drivers/driver.php?id=atikmpag.sys 
    
    amdacpksd.sys Fri Nov 21 03:18:16  2014 (546EA0E8) 
    AMD ACP Kernel Service Driver (KSD) - I suspect it's a part  of the AMD chipset drivers as my system doesn't have it (and I have an Intel  chipset with an ATI video card). Just in case 
    http://www.carrona.org/drivers/driver.php?id=amdacpksd.sys 
    
    atikmdag.sys Fri Nov 21 03:30:27  2014 (546EA3C3) 
    ATI Video driver (remove the Catalyst Control Center and  only install the Display Driver) 
    http://www.carrona.org/drivers/driver.php?id=atikmdag.sys 
    
    VBoxNetFlt.sys Fri Nov 21  14:55:54 2014 (546F446A) 
    VirtualBox network driver 
    http://www.carrona.org/drivers/driver.php?id=VBoxNetFlt.sys 
    
    VBoxUSBMon.sys Fri Nov 21  14:55:55 2014 (546F446B) 
    VirtualBox USB driver 
    http://www.carrona.org/drivers/driver.php?id=VBoxUSBMon.sys 
    
    VBoxDrv.sys Fri Nov 21 14:57:03  2014 (546F44AF) 
    VirtualBox 
    http://www.carrona.org/drivers/driver.php?id=VBoxDrv.sys 
    
    HWiNFO64A.SYS Sun Nov 23 17:24:07  2014 (54720A27) 
    HWiNFO32 Kernel Driver 
    http://www.carrona.org/drivers/driver.php?id=HWiNFO64A.SYS 
    
    aswMonFlt.sys Mon Mar 2 13:14:33  2015 (54F45429) 
    avast! File System Minifilter Driver 
    http://www.carrona.org/drivers/driver.php?id=aswMonFlt.sys 
    
    aswRvrt.sys Mon Mar 2 13:14:43  2015 (54F45433) 
    Avast! Revert driver[br](Likely a boot driver) 
    http://www.carrona.org/drivers/driver.php?id=aswRvrt.sys 
    
    aswHwid.sys Mon Mar 2 13:15:09  2015 (54F4544D) 
    avast! HWID driver 
    http://www.carrona.org/drivers/driver.php?id=aswHwid.sys 
    
    aswRdr2.sys Mon Mar 2 13:15:17  2015 (54F45455) 
    avast! TDI Redirect Driver 
    http://www.carrona.org/drivers/driver.php?id=aswRdr2.sys 
    
    aswSnx.sys Mon Mar 2 13:15:28 2015  (54F45460) 
    avast! Virtualization Driver 
    http://www.carrona.org/drivers/driver.php?id=aswSnx.sys 
    
    aswVmm.sys Mon Mar 2 13:28:19 2015  (54F45763) 
    avast! VM Monitor driver 
    http://www.carrona.org/drivers/driver.php?id=aswVmm.sys 
    
    aswSP.sys Mon Mar 2 13:28:40 2015  (54F45778) 
    avast! Self Protection Driver 
    http://www.carrona.org/drivers/driver.php?id=aswSP.sys 
    
    aswStm.sys Mon Mar 2 13:31:36 2015  (54F45828) 
    avast! Antivirus Stream Filter driver 
    http://www.carrona.org/drivers/driver.php?id=aswStm.sys 
    
    
    
    Debug session time: Thu Mar  19 23:32:31.694 2015 (UTC + 1:00) 
    Loading Dump File  [C:\Users\Mihael\SysnativeBSODApps\031915-8859-01.dmp] 
    Built by:  9600.17668.amd64fre.winblue_r8.150127-1500 
    System Uptime: 0 days 0:02:39.406  
    *** WARNING: Unable to verify timestamp for atikmdag.sys 
    *** ERROR:  Module load completed but symbols could not be loaded for atikmdag.sys  
    Probably caused by : dxgkrnl.sys (  dxgkrnl!TdrTimedOperationBugcheckOnTimeout+4d ) 
    BugCheck 100000EA,  {ffffe0003b181500, 0, 0, 0} 
    BugCheck Info: THREAD_STUCK_IN_DEVICE_DRIVER_M  (100000ea) 
    Bugcheck code 100000eA 
    Arguments: 
    Arg1:  ffffe0003b181500, Pointer to a stuck thread object. Do .thread then kb on it to  find 
    the hung location. 
    Arg2: 0000000000000000, Pointer to a  DEFERRED_WATCHDOG object. 
    Arg3: 0000000000000000, Pointer to offending  driver name. 
    Arg4: 0000000000000000, Number of times "intercepted" bugcheck  0xEA was hit (see notes). 
    BUGCHECK_STR: 0xEA 
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_FAULT 
    PROCESS_NAME: System 
    FAILURE_BUCKET_ID:  0xEA_IMAGE_dxgkrnl.sys 
    MaxSpeed: 3400 
    CurrentSpeed: 3400 
    BiosVersion  = 3505 
    BiosReleaseDate = 03/13/2013 
    SystemManufacturer = System  manufacturer 
    SystemProductName = System Product Name  
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``  
    Debug session time: Thu Mar 19 12:58:08.604 2015 (UTC + 1:00) 
    Loading  Dump File [C:\Users\Mihael\SysnativeBSODApps\031915-9734-01.dmp] 
    Built by:  9600.17668.amd64fre.winblue_r8.150127-1500 
    System Uptime: 0 days 0:06:41.313  
    *** WARNING: Unable to verify timestamp for atikmdag.sys 
    *** ERROR:  Module load completed but symbols could not be loaded for atikmdag.sys  
    Probably caused by : dxgkrnl.sys (  dxgkrnl!TdrTimedOperationBugcheckOnTimeout+4d ) 
    BugCheck 100000EA,  {ffffe0016aab8880, 0, 0, 0} 
    BugCheck Info: THREAD_STUCK_IN_DEVICE_DRIVER_M  (100000ea) 
    Bugcheck code 100000eA 
    Arguments: 
    Arg1:  ffffe0016aab8880, Pointer to a stuck thread object. Do .thread then kb on it to  find 
    the hung location. 
    Arg2: 0000000000000000, Pointer to a  DEFERRED_WATCHDOG object. 
    Arg3: 0000000000000000, Pointer to offending  driver name. 
    Arg4: 0000000000000000, Number of times "intercepted" bugcheck  0xEA was hit (see notes). 
    BUGCHECK_STR: 0xEA 
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_FAULT 
    PROCESS_NAME: System 
    FAILURE_BUCKET_ID:  0xEA_IMAGE_dxgkrnl.sys 
    MaxSpeed: 3400 
    CurrentSpeed: 3400 
    BiosVersion  = 3505 
    BiosReleaseDate = 03/13/2013 
    SystemManufacturer = System  manufacturer 
    SystemProductName = System Product Name  
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``  
    Debug session time: Thu Mar 19 12:42:53.430 2015 (UTC + 1:00) 
    Loading  Dump File [C:\Users\Mihael\SysnativeBSODApps\031915-10671-01.dmp] 
    Built by:  9600.17668.amd64fre.winblue_r8.150127-1500 
    System Uptime: 0 days 0:05:51.140  
    *** WARNING: Unable to verify timestamp for atikmdag.sys 
    *** ERROR:  Module load completed but symbols could not be loaded for atikmdag.sys  
    Probably caused by : dxgkrnl.sys (  dxgkrnl!TdrTimedOperationBugcheckOnTimeout+4d ) 
    BugCheck 100000EA,  {ffffe0008b414880, 0, 0, 0} 
    BugCheck Info: THREAD_STUCK_IN_DEVICE_DRIVER_M  (100000ea) 
    Bugcheck code 100000eA 
    Arguments: 
    Arg1:  ffffe0008b414880, Pointer to a stuck thread object. Do .thread then kb on it to  find 
    the hung location. 
    Arg2: 0000000000000000, Pointer to a  DEFERRED_WATCHDOG object. 
    Arg3: 0000000000000000, Pointer to offending  driver name. 
    Arg4: 0000000000000000, Number of times "intercepted" bugcheck  0xEA was hit (see notes). 
    BUGCHECK_STR: 0xEA 
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_FAULT 
    PROCESS_NAME: System 
    FAILURE_BUCKET_ID:  0xEA_IMAGE_dxgkrnl.sys 
    MaxSpeed: 3400 
    CurrentSpeed: 3418 
    BiosVersion  = 3505 
    BiosReleaseDate = 03/13/2013 
    SystemManufacturer = System  manufacturer 
    SystemProductName = System Product Name  
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``  
    Debug session time: Thu Mar 19 08:15:24.741 2015 (UTC + 1:00) 
    Loading  Dump File [C:\Users\Mihael\SysnativeBSODApps\031915-9843-01.dmp] 
    Built by:  9600.17668.amd64fre.winblue_r8.150127-1500 
    System Uptime: 0 days 0:07:24.454  
    *** WARNING: Unable to verify timestamp for atikmdag.sys 
    *** ERROR:  Module load completed but symbols could not be loaded for atikmdag.sys  
    Probably caused by : dxgkrnl.sys (  dxgkrnl!TdrTimedOperationBugcheckOnTimeout+4d ) 
    BugCheck 100000EA,  {ffffe001e9972880, 0, 0, 0} 
    BugCheck Info: THREAD_STUCK_IN_DEVICE_DRIVER_M  (100000ea) 
    Bugcheck code 100000eA 
    Arguments: 
    Arg1:  ffffe001e9972880, Pointer to a stuck thread object. Do .thread then kb on it to  find 
    the hung location. 
    Arg2: 0000000000000000, Pointer to a  DEFERRED_WATCHDOG object. 
    Arg3: 0000000000000000, Pointer to offending  driver name. 
    Arg4: 0000000000000000, Number of times "intercepted" bugcheck  0xEA was hit (see notes). 
    BUGCHECK_STR: 0xEA 
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_FAULT 
    PROCESS_NAME: System 
    FAILURE_BUCKET_ID:  0xEA_IMAGE_dxgkrnl.sys 
    MaxSpeed: 3400 
    CurrentSpeed: 3400 
    BiosVersion  = 3505 
    BiosReleaseDate = 03/13/2013 
    SystemManufacturer = System  manufacturer 
    SystemProductName = System Product Name  
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``  
    Debug session time: Tue Mar 17 00:32:16.954 2015 (UTC + 1:00) 
    Loading  Dump File [C:\Users\Mihael\SysnativeBSODApps\031615-7546-01.dmp] 
    Built by:  9600.17668.amd64fre.winblue_r8.150127-1500 
    System Uptime: 0 days 0:10:13.656  
    *** WARNING: Unable to verify timestamp for atikmdag.sys 
    *** ERROR:  Module load completed but symbols could not be loaded for atikmdag.sys  
    Probably caused by : dxgkrnl.sys (  dxgkrnl!TdrTimedOperationBugcheckOnTimeout+4d ) 
    BugCheck 100000EA,  {ffffe00139f6f500, 0, 0, 0} 
    BugCheck Info: THREAD_STUCK_IN_DEVICE_DRIVER_M  (100000ea) 
    Bugcheck code 100000eA 
    Arguments: 
    Arg1:  ffffe00139f6f500, Pointer to a stuck thread object. Do .thread then kb on it to  find 
    the hung location. 
    Arg2: 0000000000000000, Pointer to a  DEFERRED_WATCHDOG object. 
    Arg3: 0000000000000000, Pointer to offending  driver name. 
    Arg4: 0000000000000000, Number of times "intercepted" bugcheck  0xEA was hit (see notes). 
    BUGCHECK_STR: 0xEA 
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_FAULT 
    PROCESS_NAME: System 
    FAILURE_BUCKET_ID:  0xEA_IMAGE_dxgkrnl.sys 
    MaxSpeed: 3400 
    CurrentSpeed: 3400 
    BiosVersion  = 3505 
    BiosReleaseDate = 03/13/2013 
    SystemManufacturer = System  manufacturer 
    SystemProductName = System Product Name  
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``  
    Debug session time: Sat Mar 14 06:32:32.600 2015 (UTC + 1:00) 
    Loading  Dump File [C:\Users\Mihael\SysnativeBSODApps\031415-8343-01.dmp] 
    Built by:  9600.17668.amd64fre.winblue_r8.150127-1500 
    System Uptime: 0 days 0:04:03.313  
    *** WARNING: Unable to verify timestamp for atikmdag.sys 
    *** ERROR:  Module load completed but symbols could not be loaded for atikmdag.sys  
    Probably caused by : dxgkrnl.sys (  dxgkrnl!TdrTimedOperationBugcheckOnTimeout+4d ) 
    BugCheck 100000EA,  {ffffe0000f271500, 0, 0, 0} 
    BugCheck Info: THREAD_STUCK_IN_DEVICE_DRIVER_M  (100000ea) 
    Bugcheck code 100000eA 
    Arguments: 
    Arg1:  ffffe0000f271500, Pointer to a stuck thread object. Do .thread then kb on it to  find 
    the hung location. 
    Arg2: 0000000000000000, Pointer to a  DEFERRED_WATCHDOG object. 
    Arg3: 0000000000000000, Pointer to offending  driver name. 
    Arg4: 0000000000000000, Number of times "intercepted" bugcheck  0xEA was hit (see notes). 
    BUGCHECK_STR: 0xEA 
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_FAULT 
    PROCESS_NAME: System 
    FAILURE_BUCKET_ID:  0xEA_IMAGE_dxgkrnl.sys 
    MaxSpeed: 3400 
    CurrentSpeed: 3400 
    BiosVersion  = 3505 
    BiosReleaseDate = 03/13/2013 
    SystemManufacturer = System  manufacturer 
    SystemProductName = System Product Name  
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``  
    Debug session time: Sat Mar 14 06:08:07.911 2015 (UTC + 1:00) 
    Loading  Dump File [C:\Users\Mihael\SysnativeBSODApps\031415-7375-01.dmp] 
    Built by:  9600.17668.amd64fre.winblue_r8.150127-1500 
    System Uptime: 0 days 0:07:34.623  
    *** WARNING: Unable to verify timestamp for atikmdag.sys 
    *** ERROR:  Module load completed but symbols could not be loaded for atikmdag.sys  
    Probably caused by : dxgkrnl.sys (  dxgkrnl!TdrTimedOperationBugcheckOnTimeout+4d ) 
    BugCheck 100000EA,  {ffffe001a3254080, 0, 0, 0} 
    BugCheck Info: THREAD_STUCK_IN_DEVICE_DRIVER_M  (100000ea) 
    Bugcheck code 100000eA 
    Arguments: 
    Arg1:  ffffe001a3254080, Pointer to a stuck thread object. Do .thread then kb on it to  find 
    the hung location. 
    Arg2: 0000000000000000, Pointer to a  DEFERRED_WATCHDOG object. 
    Arg3: 0000000000000000, Pointer to offending  driver name. 
    Arg4: 0000000000000000, Number of times "intercepted" bugcheck  0xEA was hit (see notes). 
    BUGCHECK_STR: 0xEA 
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_FAULT 
    PROCESS_NAME: System 
    FAILURE_BUCKET_ID:  0xEA_IMAGE_dxgkrnl.sys 
    MaxSpeed: 3400 
    CurrentSpeed: 3400 
    BiosVersion  = 3505 
    BiosReleaseDate = 03/13/2013 
    SystemManufacturer = System  manufacturer 
    SystemProductName = System Product Name  
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``  
    Debug session time: Sat Mar 14 06:00:00.086 2015 (UTC + 1:00) 
    Loading  Dump File [C:\Users\Mihael\SysnativeBSODApps\031415-8093-01.dmp] 
    Built by:  9600.17668.amd64fre.winblue_r8.150127-1500 
    System Uptime: 0 days 0:16:53.797  
    *** WARNING: Unable to verify timestamp for atikmdag.sys 
    *** ERROR:  Module load completed but symbols could not be loaded for atikmdag.sys  
    Probably caused by : dxgkrnl.sys (  dxgkrnl!TdrTimedOperationBugcheckOnTimeout+4d ) 
    BugCheck 100000EA,  {ffffe000385c6500, 0, 0, 0} 
    BugCheck Info: THREAD_STUCK_IN_DEVICE_DRIVER_M  (100000ea) 
    Bugcheck code 100000eA 
    Arguments: 
    Arg1:  ffffe000385c6500, Pointer to a stuck thread object. Do .thread then kb on it to  find 
    the hung location. 
    Arg2: 0000000000000000, Pointer to a  DEFERRED_WATCHDOG object. 
    Arg3: 0000000000000000, Pointer to offending  driver name. 
    Arg4: 0000000000000000, Number of times "intercepted" bugcheck  0xEA was hit (see notes). 
    BUGCHECK_STR: 0xEA 
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_FAULT 
    PROCESS_NAME: System 
    FAILURE_BUCKET_ID:  0xEA_IMAGE_dxgkrnl.sys 
    MaxSpeed: 3400 
    CurrentSpeed: 3400 
    BiosVersion  = 3505 
    BiosReleaseDate = 03/13/2013 
    SystemManufacturer = System  manufacturer 
    SystemProductName = System Product Name  
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``  
    Debug session time: Thu Mar 12 23:50:50.039 2015 (UTC + 1:00) 
    Loading  Dump File [C:\Users\Mihael\SysnativeBSODApps\031215-7468-01.dmp] 
    Built by:  9600.17668.amd64fre.winblue_r8.150127-1500 
    System Uptime: 0 days 0:05:12.750  
    *** WARNING: Unable to verify timestamp for atikmdag.sys 
    *** ERROR:  Module load completed but symbols could not be loaded for atikmdag.sys  
    Probably caused by : dxgkrnl.sys (  dxgkrnl!TdrTimedOperationBugcheckOnTimeout+4d ) 
    BugCheck 100000EA,  {ffffe0002f0e9880, 0, 0, 0} 
    BugCheck Info: THREAD_STUCK_IN_DEVICE_DRIVER_M  (100000ea) 
    Bugcheck code 100000eA 
    Arguments: 
    Arg1:  ffffe0002f0e9880, Pointer to a stuck thread object. Do .thread then kb on it to  find 
    the hung location. 
    Arg2: 0000000000000000, Pointer to a  DEFERRED_WATCHDOG object. 
    Arg3: 0000000000000000, Pointer to offending  driver name. 
    Arg4: 0000000000000000, Number of times "intercepted" bugcheck  0xEA was hit (see notes). 
    BUGCHECK_STR: 0xEA 
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_FAULT 
    PROCESS_NAME: System 
    FAILURE_BUCKET_ID:  0xEA_IMAGE_dxgkrnl.sys 
    MaxSpeed: 3400 
    CurrentSpeed: 3400 
    BiosVersion  = 3505 
    BiosReleaseDate = 03/13/2013 
    SystemManufacturer = System  manufacturer 
    SystemProductName = System Product Name  
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``  
    Debug session time: Wed Mar 11 23:55:37.443 2015 (UTC + 1:00) 
    Loading  Dump File [C:\Users\Mihael\SysnativeBSODApps\031115-14906-01.dmp] 
    Built by:  9600.17668.amd64fre.winblue_r8.150127-1500 
    System Uptime: 0 days 0:05:27.156  
    *** WARNING: Unable to verify timestamp for atikmdag.sys 
    *** ERROR:  Module load completed but symbols could not be loaded for atikmdag.sys  
    Probably caused by : dxgkrnl.sys (  dxgkrnl!TdrTimedOperationBugcheckOnTimeout+4d ) 
    BugCheck 100000EA,  {ffffe0006fcf1080, 0, 0, 0} 
    BugCheck Info: THREAD_STUCK_IN_DEVICE_DRIVER_M  (100000ea) 
    Bugcheck code 100000eA 
    Arguments: 
    Arg1:  ffffe0006fcf1080, Pointer to a stuck thread object. Do .thread then kb on it to  find 
    the hung location. 
    Arg2: 0000000000000000, Pointer to a  DEFERRED_WATCHDOG object. 
    Arg3: 0000000000000000, Pointer to offending  driver name. 
    Arg4: 0000000000000000, Number of times "intercepted" bugcheck  0xEA was hit (see notes). 
    BUGCHECK_STR: 0xEA 
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_FAULT 
    PROCESS_NAME: System 
    FAILURE_BUCKET_ID:  0xEA_IMAGE_dxgkrnl.sys 
    MaxSpeed: 3400 
    CurrentSpeed: 3410 
    BiosVersion  = 3505 
    BiosReleaseDate = 03/13/2013 
    SystemManufacturer = System  manufacturer 
    SystemProductName = System Product Name  
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``  
    Debug session time: Wed Mar 11 23:32:43.758 2015 (UTC + 1:00) 
    Loading  Dump File [C:\Users\Mihael\SysnativeBSODApps\031115-14703-01.dmp] 
    Built by:  9600.17668.amd64fre.winblue_r8.150127-1500 
    System Uptime: 0 days 0:08:40.469  
    *** WARNING: Unable to verify timestamp for atikmdag.sys 
    *** ERROR:  Module load completed but symbols could not be loaded for atikmdag.sys  
    Probably caused by : dxgkrnl.sys (  dxgkrnl!TdrTimedOperationBugcheckOnTimeout+4d ) 
    BugCheck 100000EA,  {ffffe001b7b61880, 0, 0, 0} 
    BugCheck Info: THREAD_STUCK_IN_DEVICE_DRIVER_M  (100000ea) 
    Bugcheck code 100000eA 
    Arguments: 
    Arg1:  ffffe001b7b61880, Pointer to a stuck thread object. Do .thread then kb on it to  find 
    the hung location. 
    Arg2: 0000000000000000, Pointer to a  DEFERRED_WATCHDOG object. 
    Arg3: 0000000000000000, Pointer to offending  driver name. 
    Arg4: 0000000000000000, Number of times "intercepted" bugcheck  0xEA was hit (see notes). 
    BUGCHECK_STR: 0xEA 
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_FAULT 
    PROCESS_NAME: System 
    FAILURE_BUCKET_ID:  0xEA_IMAGE_dxgkrnl.sys 
    MaxSpeed: 3400 
    CurrentSpeed: 3400 
    BiosVersion  = 3505 
    BiosReleaseDate = 03/13/2013 
    SystemManufacturer = System  manufacturer 
    SystemProductName = System Product Name  
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``  
    Debug session time: Wed Mar 11 04:57:30.398 2015 (UTC + 1:00) 
    Loading  Dump File [C:\Users\Mihael\SysnativeBSODApps\031115-17296-01.dmp] 
    Built by:  9600.17630.amd64fre.winblue_r7.150109-2022 
    System Uptime: 0 days 5:35:45.109  
    *** WARNING: Unable to verify timestamp for atikmdag.sys 
    *** ERROR:  Module load completed but symbols could not be loaded for atikmdag.sys  
    Probably caused by : dxgkrnl.sys (  dxgkrnl!TdrTimedOperationBugcheckOnTimeout+4d ) 
    BugCheck 100000EA,  {ffffe0013bad6880, 0, 0, 0} 
    BugCheck Info: THREAD_STUCK_IN_DEVICE_DRIVER_M  (100000ea) 
    Bugcheck code 100000eA 
    Arguments: 
    Arg1:  ffffe0013bad6880, Pointer to a stuck thread object. Do .thread then kb on it to  find 
    the hung location. 
    Arg2: 0000000000000000, Pointer to a  DEFERRED_WATCHDOG object. 
    Arg3: 0000000000000000, Pointer to offending  driver name. 
    Arg4: 0000000000000000, Number of times "intercepted" bugcheck  0xEA was hit (see notes). 
    BUGCHECK_STR: 0xEA 
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_FAULT 
    PROCESS_NAME: System 
    FAILURE_BUCKET_ID:  0xEA_IMAGE_dxgkrnl.sys 
    MaxSpeed: 3400 
    CurrentSpeed: 3400 
    BiosVersion  = 3505 
    BiosReleaseDate = 03/13/2013 
    SystemManufacturer = System  manufacturer 
    SystemProductName = System Product Name  
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``  
    Debug session time: Tue Mar 10 12:35:05.055 2015 (UTC + 1:00) 
    Loading  Dump File [C:\Users\Mihael\SysnativeBSODApps\031015-14203-01.dmp] 
    Built by:  9600.17630.amd64fre.winblue_r7.150109-2022 
    System Uptime: 0 days 0:08:56.766  
    *** WARNING: Unable to verify timestamp for atikmdag.sys 
    *** ERROR:  Module load completed but symbols could not be loaded for atikmdag.sys  
    Probably caused by : dxgkrnl.sys (  dxgkrnl!TdrTimedOperationBugcheckOnTimeout+4d ) 
    BugCheck 100000EA,  {ffffe0005a2ed080, 0, 0, 0} 
    BugCheck Info: THREAD_STUCK_IN_DEVICE_DRIVER_M  (100000ea) 
    Bugcheck code 100000eA 
    Arguments: 
    Arg1:  ffffe0005a2ed080, Pointer to a stuck thread object. Do .thread then kb on it to  find 
    the hung location. 
    Arg2: 0000000000000000, Pointer to a  DEFERRED_WATCHDOG object. 
    Arg3: 0000000000000000, Pointer to offending  driver name. 
    Arg4: 0000000000000000, Number of times "intercepted" bugcheck  0xEA was hit (see notes). 
    BUGCHECK_STR: 0xEA 
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_FAULT 
    PROCESS_NAME: System 
    FAILURE_BUCKET_ID:  0xEA_IMAGE_dxgkrnl.sys 
    MaxSpeed: 3400 
    CurrentSpeed: 3400 
    BiosVersion  = 3505 
    BiosReleaseDate = 03/13/2013 
    SystemManufacturer = System  manufacturer 
    SystemProductName = System Product Name  
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``  
    Debug session time: Mon Mar 9 23:57:21.380 2015 (UTC + 1:00) 
    Loading  Dump File [C:\Users\Mihael\SysnativeBSODApps\030915-16140-01.dmp] 
    Built by:  9600.17630.amd64fre.winblue_r7.150109-2022 
    System Uptime: 0 days 0:23:26.092  
    *** WARNING: Unable to verify timestamp for atikmdag.sys 
    *** ERROR:  Module load completed but symbols could not be loaded for atikmdag.sys  
    Probably caused by : dxgkrnl.sys (  dxgkrnl!TdrTimedOperationBugcheckOnTimeout+4d ) 
    BugCheck 100000EA,  {ffffe001035c0080, 0, 0, 0} 
    BugCheck Info: THREAD_STUCK_IN_DEVICE_DRIVER_M  (100000ea) 
    Bugcheck code 100000eA 
    Arguments: 
    Arg1:  ffffe001035c0080, Pointer to a stuck thread object. Do .thread then kb on it to  find 
    the hung location. 
    Arg2: 0000000000000000, Pointer to a  DEFERRED_WATCHDOG object. 
    Arg3: 0000000000000000, Pointer to offending  driver name. 
    Arg4: 0000000000000000, Number of times "intercepted" bugcheck  0xEA was hit (see notes). 
    BUGCHECK_STR: 0xEA 
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_FAULT 
    PROCESS_NAME: System 
    FAILURE_BUCKET_ID:  0xEA_IMAGE_dxgkrnl.sys 
    MaxSpeed: 3400 
    CurrentSpeed: 3400 
    BiosVersion  = 3505 
    BiosReleaseDate = 03/13/2013 
    SystemManufacturer = System  manufacturer 
    SystemProductName = System Product Name  
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``  
    Debug session time: Sun Mar 8 16:04:16.070 2015 (UTC + 1:00) 
    Loading  Dump File [C:\Users\Mihael\SysnativeBSODApps\030815-16187-01.dmp] 
    Built by:  9600.17630.amd64fre.winblue_r7.150109-2022 
    System Uptime: 0 days 0:27:11.781  
    *** WARNING: Unable to verify timestamp for atikmdag.sys 
    *** ERROR:  Module load completed but symbols could not be loaded for atikmdag.sys  
    Probably caused by : dxgkrnl.sys (  dxgkrnl!TdrTimedOperationBugcheckOnTimeout+4d ) 
    BugCheck 100000EA,  {ffffe000f8a64640, 0, 0, 0} 
    BugCheck Info: THREAD_STUCK_IN_DEVICE_DRIVER_M  (100000ea) 
    Bugcheck code 100000eA 
    Arguments: 
    Arg1:  ffffe000f8a64640, Pointer to a stuck thread object. Do .thread then kb on it to  find 
    the hung location. 
    Arg2: 0000000000000000, Pointer to a  DEFERRED_WATCHDOG object. 
    Arg3: 0000000000000000, Pointer to offending  driver name. 
    Arg4: 0000000000000000, Number of times "intercepted" bugcheck  0xEA was hit (see notes). 
    BUGCHECK_STR: 0xEA 
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_FAULT 
    PROCESS_NAME: System 
    FAILURE_BUCKET_ID:  0xEA_IMAGE_dxgkrnl.sys 
    MaxSpeed: 3400 
    CurrentSpeed: 3400 
    BiosVersion  = 3505 
    BiosReleaseDate = 03/13/2013 
    SystemManufacturer = System  manufacturer 
    SystemProductName = System Product Name  
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``  
    Debug session time: Sat Mar 7 21:20:56.743 2015 (UTC + 1:00) 
    Loading  Dump File [C:\Users\Mihael\SysnativeBSODApps\030715-17296-01.dmp] 
    Built by:  9600.17630.amd64fre.winblue_r7.150109-2022 
    System Uptime: 0 days 0:38:16.453  
    *** WARNING: Unable to verify timestamp for atikmdag.sys 
    *** ERROR:  Module load completed but symbols could not be loaded for atikmdag.sys  
    Probably caused by : dxgkrnl.sys (  dxgkrnl!TdrTimedOperationBugcheckOnTimeout+4d ) 
    BugCheck 100000EA,  {ffffe00129b1d880, 0, 0, 0} 
    BugCheck Info: THREAD_STUCK_IN_DEVICE_DRIVER_M  (100000ea) 
    Bugcheck code 100000eA 
    Arguments: 
    Arg1:  ffffe00129b1d880, Pointer to a stuck thread object. Do .thread then kb on it to  find 
    the hung location. 
    Arg2: 0000000000000000, Pointer to a  DEFERRED_WATCHDOG object. 
    Arg3: 0000000000000000, Pointer to offending  driver name. 
    Arg4: 0000000000000000, Number of times "intercepted" bugcheck  0xEA was hit (see notes). 
    BUGCHECK_STR: 0xEA 
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_FAULT 
    PROCESS_NAME: System 
    FAILURE_BUCKET_ID:  0xEA_IMAGE_dxgkrnl.sys 
    MaxSpeed: 3400 
    CurrentSpeed: 3400 
    BiosVersion  = 3505 
    BiosReleaseDate = 03/13/2013 
    SystemManufacturer = System  manufacturer 
    SystemProductName = System Product Name  
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``  
    Debug session time: Sat Mar 7 20:10:04.945 2015 (UTC + 1:00) 
    Loading  Dump File [C:\Users\Mihael\SysnativeBSODApps\030715-17328-01.dmp] 
    Built by:  9600.17630.amd64fre.winblue_r7.150109-2022 
    System Uptime: 0 days 0:04:06.656  
    *** WARNING: Unable to verify timestamp for atikmdag.sys 
    *** ERROR:  Module load completed but symbols could not be loaded for atikmdag.sys  
    Probably caused by : dxgkrnl.sys (  dxgkrnl!TdrTimedOperationBugcheckOnTimeout+4d ) 
    BugCheck 100000EA,  {ffffe00017ade080, 0, 0, 0} 
    BugCheck Info: THREAD_STUCK_IN_DEVICE_DRIVER_M  (100000ea) 
    Bugcheck code 100000eA 
    Arguments: 
    Arg1:  ffffe00017ade080, Pointer to a stuck thread object. Do .thread then kb on it to  find 
    the hung location. 
    Arg2: 0000000000000000, Pointer to a  DEFERRED_WATCHDOG object. 
    Arg3: 0000000000000000, Pointer to offending  driver name. 
    Arg4: 0000000000000000, Number of times "intercepted" bugcheck  0xEA was hit (see notes). 
    BUGCHECK_STR: 0xEA 
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_FAULT 
    PROCESS_NAME: System 
    FAILURE_BUCKET_ID:  0xEA_IMAGE_dxgkrnl.sys 
    MaxSpeed: 3400 
    CurrentSpeed: 3400 
    BiosVersion  = 3505 
    BiosReleaseDate = 03/13/2013 
    SystemManufacturer = System  manufacturer 
    SystemProductName = System Product Name  
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``  
    Debug session time: Sat Mar 7 05:54:02.024 2015 (UTC + 1:00) 
    Loading  Dump File [C:\Users\Mihael\SysnativeBSODApps\030715-14843-01.dmp] 
    Built by:  9600.17630.amd64fre.winblue_r7.150109-2022 
    System Uptime: 0 days 0:10:29.735  
    *** WARNING: Unable to verify timestamp for atikmdag.sys 
    *** ERROR:  Module load completed but symbols could not be loaded for atikmdag.sys  
    Probably caused by : dxgkrnl.sys (  dxgkrnl!TdrTimedOperationBugcheckOnTimeout+4d ) 
    BugCheck 100000EA,  {ffffe000fdb4a880, 0, 0, 0} 
    BugCheck Info: THREAD_STUCK_IN_DEVICE_DRIVER_M  (100000ea) 
    Bugcheck code 100000eA 
    Arguments: 
    Arg1:  ffffe000fdb4a880, Pointer to a stuck thread object. Do .thread then kb on it to  find 
    the hung location. 
    Arg2: 0000000000000000, Pointer to a  DEFERRED_WATCHDOG object. 
    Arg3: 0000000000000000, Pointer to offending  driver name. 
    Arg4: 0000000000000000, Number of times "intercepted" bugcheck  0xEA was hit (see notes). 
    BUGCHECK_STR: 0xEA 
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_FAULT 
    PROCESS_NAME: System 
    FAILURE_BUCKET_ID:  0xEA_IMAGE_dxgkrnl.sys 
    MaxSpeed: 3400 
    CurrentSpeed: 3400 
    BiosVersion  = 3505 
    BiosReleaseDate = 03/13/2013 
    SystemManufacturer = System  manufacturer 
    SystemProductName = System Product Name  
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``  
    Debug session time: Fri Mar 6 13:27:37.883 2015 (UTC + 1:00) 
    Loading  Dump File [C:\Users\Mihael\SysnativeBSODApps\030615-7515-01.dmp] 
    Built by:  9600.17630.amd64fre.winblue_r7.150109-2022 
    System Uptime: 0 days 0:03:41.593  
    *** WARNING: Unable to verify timestamp for atikmdag.sys 
    *** ERROR:  Module load completed but symbols could not be loaded for atikmdag.sys  
    Probably caused by : dxgkrnl.sys (  dxgkrnl!TdrTimedOperationBugcheckOnTimeout+4d ) 
    BugCheck 100000EA,  {ffffe001f869e880, 0, 0, 0} 
    BugCheck Info: THREAD_STUCK_IN_DEVICE_DRIVER_M  (100000ea) 
    Bugcheck code 100000eA 
    Arguments: 
    Arg1:  ffffe001f869e880, Pointer to a stuck thread object. Do .thread then kb on it to  find 
    the hung location. 
    Arg2: 0000000000000000, Pointer to a  DEFERRED_WATCHDOG object. 
    Arg3: 0000000000000000, Pointer to offending  driver name. 
    Arg4: 0000000000000000, Number of times "intercepted" bugcheck  0xEA was hit (see notes). 
    BUGCHECK_STR: 0xEA 
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_FAULT 
    PROCESS_NAME: System 
    FAILURE_BUCKET_ID:  0xEA_IMAGE_dxgkrnl.sys 
    MaxSpeed: 3400 
    CurrentSpeed: 3400 
    BiosVersion  = 3505 
    BiosReleaseDate = 03/13/2013 
    SystemManufacturer = System  manufacturer 
    SystemProductName = System Product Name  
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``  
    Debug session time: Fri Mar 6 13:10:35.433 2015 (UTC + 1:00) 
    Loading  Dump File [C:\Users\Mihael\SysnativeBSODApps\030615-5687-01.dmp] 
    Built by:  9600.17630.amd64fre.winblue_r7.150109-2022 
    System Uptime: 0 days 0:13:01.141  
    *** WARNING: Unable to verify timestamp for atikmdag.sys 
    *** ERROR:  Module load completed but symbols could not be loaded for atikmdag.sys  
    Probably caused by : dxgkrnl.sys (  dxgkrnl!TdrTimedOperationBugcheckOnTimeout+4d ) 
    BugCheck 100000EA,  {ffffe000d2ece080, 0, 0, 0} 
    BugCheck Info: THREAD_STUCK_IN_DEVICE_DRIVER_M  (100000ea) 
    Bugcheck code 100000eA 
    Arguments: 
    Arg1:  ffffe000d2ece080, Pointer to a stuck thread object. Do .thread then kb on it to  find 
    the hung location. 
    Arg2: 0000000000000000, Pointer to a  DEFERRED_WATCHDOG object. 
    Arg3: 0000000000000000, Pointer to offending  driver name. 
    Arg4: 0000000000000000, Number of times "intercepted" bugcheck  0xEA was hit (see notes). 
    BUGCHECK_STR: 0xEA 
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_FAULT 
    PROCESS_NAME: System 
    FAILURE_BUCKET_ID:  0xEA_IMAGE_dxgkrnl.sys 
    MaxSpeed: 3400 
    CurrentSpeed: 3400 
    BiosVersion  = 3505 
    BiosReleaseDate = 03/13/2013 
    SystemManufacturer = System  manufacturer 
    SystemProductName = System Product Name  
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``  
    Debug session time: Fri Mar 6 00:10:19.751 2015 (UTC + 1:00) 
    Loading  Dump File [C:\Users\Mihael\SysnativeBSODApps\030515-8375-01.dmp] 
    Built by:  9600.17630.amd64fre.winblue_r7.150109-2022 
    System Uptime: 0 days 0:35:52.459  
    Probably caused by : GenuineIntel 
    BugCheck 124, {0, ffffe0017a5dd028,  be000000, 800400} 
    BugCheck Info: WHEA_UNCORRECTABLE_ERROR  (124) 
    Bugcheck code 00000124 
    Arguments: 
    Arg1: 0000000000000000,  Machine Check Exception 
    Arg2: ffffe0017a5dd028, Address of the  WHEA_ERROR_RECORD structure. 
    Arg3: 00000000be000000, High order 32-bits of  the MCi_STATUS value. 
    Arg4: 0000000000800400, Low order 32-bits of the  MCi_STATUS value. 
    BUGCHECK_STR: 0x124_GenuineIntel 
    PROCESS_NAME: System  
    FAILURE_BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_MAE 
    MaxSpeed: 3400  
    CurrentSpeed: 3400 
    BiosVersion = 3505 
    BiosReleaseDate = 03/13/2013  
    SystemManufacturer = System manufacturer 
    SystemProductName = System  Product Name  
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``  
    Debug session time: Thu Mar 5 12:57:38.340 2015 (UTC + 1:00) 
    Loading  Dump File [C:\Users\Mihael\SysnativeBSODApps\030515-10062-01.dmp] 
    Built by:  9600.17630.amd64fre.winblue_r7.150109-2022 
    System Uptime: 0 days 1:00:12.051  
    *** WARNING: Unable to verify timestamp for atikmpag.sys 
    *** ERROR:  Module load completed but symbols could not be loaded for atikmpag.sys  
    Probably caused by : atikmpag.sys ( atikmpag+b848 ) 
    BugCheck 116,  {ffffe0011824a010, fffff8013fcaa848, 0, d} 
    BugCheck Info: VIDEO_TDR_FAILURE (116)  
    Bugcheck code 00000116 
    Arguments: 
    Arg1: ffffe0011824a010, Optional  pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT). 
    Arg2:  fffff8013fcaa848, The pointer into responsible device driver module (e.g. owner  tag). 
    Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last  failed operation. 
    Arg4: 000000000000000d, Optional internal context  dependent data. 
    BUGCHECK_STR: 0x116 
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT 
    PROCESS_NAME: System 
    FAILURE_BUCKET_ID:  0x116_IMAGE_atikmpag.sys  
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``  
    Debug session time: Thu Mar 5 00:43:38.664 2015 (UTC + 1:00) 
    Loading  Dump File [C:\Users\Mihael\SysnativeBSODApps\030415-7390-01.dmp] 
    Built by:  9600.17630.amd64fre.winblue_r7.150109-2022 
    System Uptime: 0 days 1:17:53.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 : dxgkrnl.sys (  dxgkrnl!TdrTimedOperationBugcheckOnTimeout+4d ) 
    BugCheck 100000EA,  {ffffe001389bc080, 0, 0, 0} 
    BugCheck Info: THREAD_STUCK_IN_DEVICE_DRIVER_M  (100000ea) 
    Bugcheck code 100000eA 
    Arguments: 
    Arg1:  ffffe001389bc080, Pointer to a stuck thread object. Do .thread then kb on it to  find 
    the hung location. 
    Arg2: 0000000000000000, Pointer to a  DEFERRED_WATCHDOG object. 
    Arg3: 0000000000000000, Pointer to offending  driver name. 
    Arg4: 0000000000000000, Number of times "intercepted" bugcheck  0xEA was hit (see notes). 
    BUGCHECK_STR: 0xEA 
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_FAULT 
    PROCESS_NAME: System 
    FAILURE_BUCKET_ID:  0xEA_IMAGE_dxgkrnl.sys 
    MaxSpeed: 3400 
    CurrentSpeed: 3400 
    BiosVersion  = 3505 
    BiosReleaseDate = 03/13/2013 
    SystemManufacturer = System  manufacturer 
    SystemProductName = System Product Name  
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``  
    
    
    
    
    --- E O J --- 2015 Mar 20 16:35:50 PM _88-dbug Copyright  2012 Sysnative Forums 
    --- E O J --- 2015 Mar 20 16:35:50 PM _88-dbug  Copyright 2012 Sysnative Forums 
    --- E O J --- 2015 Mar 20 16:35:50 PM  _88-dbug Copyright 2012 Sysnative Forums
    I would recommend stress testing your GPU because the symptoms do indicate that it might be failing.

    urMark download site: FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
    FurMark Setup:
    - If you have more than one GPU, select Multi-GPU during setup
    - In the Run mode box, select "Stability Test" and "Log GPU Temperature"
    Click "Go" to start the test (Looks like it's "BURN-IN test" now)
    - Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
    NOTE: Set the alarm to go off at 90║C. Then watch the system from that point on. If the system doesn't display a temperature, watch it constantly and turn it off at the first sign of video problems. DO NOT leave it it unmonitored, it can DAMAGE your video card!!!
    If the temperature gets above 100║C, quit the test - the video card is overheating.
    - Click "Quit" to exit

    What you are looking for:
    - excessive heat from the GPU (report back with anything over 90║C)
    - problems with the video display (picture is distorted or jumbled, picture turns black, etc)
    - problems reported by the program (I haven't seen this, but "just in case")
      My System SpecsSystem Spec

  5. #5


    Posts : 24
    Windows 8 Pro 64bit


    Thank you for very detailed reply. Do you know what two antivirus software it is? I only have bitdefender atm.

    Tomorrow am going to refresh my windows 8.1 and not install anything, just basic drivers to get my system running and go from there..

    I played new battlefield hardline last night on one GPU and as always performance was fine. Only once I run two GPUs does my pc crash.
      My System SpecsSystem Spec

  6. #6


    Posts : 2,480
    Windows 10 Pro x64


    You have Bitdefender and Avast both. OK. Keep me appraised.
      My System SpecsSystem Spec

  7. #7


    Posts : 24
    Windows 8 Pro 64bit


    That's strange because I did completely remove avast has testing because heard it can crash games.. So installed bitdefender..
      My System SpecsSystem Spec

  8. #8


    Posts : 2,480
    Windows 10 Pro x64


    Use their uninstall tools available on their websites.
      My System SpecsSystem Spec

  9. #9


    Posts : 24
    Windows 8 Pro 64bit


    Update!
    Am sending the 290 GPU back, am 100% sure its this.. Last night my PC crashed but this time it was different.. I got black screen and the 290 fan was on 100% when I restarted the PC wouldn't pick up the 290! I had to switch PC off and back on again for it to work.
      My System SpecsSystem Spec

  10. #10


    Posts : 2,480
    Windows 10 Pro x64


    I hope you'll get a good one now. If not, try an nVidia card.
      My System SpecsSystem Spec

Page 1 of 3 123 LastLast
BSOD Crossfire 290 0x100000ea
Related Threads
BSOD when playing crossfire in BSOD Crashes and Debugging
when i play crossfire my pc shuts down randomly what can i do?
Hi, i am going to build my first PC soon. I want to Crossfire 2 R9 270X's but not sure which motherboard to go for. The motherboard has to support AMD Athlon X4 760K and have USB 3.0 Can someone pont me in the right direction plz. Thanks
I cannot play crossfire anymore with my new WINDOWS 8?
Hello, I am running two 7950s in crossfire on my computer. Anytime I launch a game, my computer just locks up and this hardcore buzzing sound playing right when it crashes, the sound continues while the computer is frozen. This problem has happened in both Battlefield 3 and Splinter Cell...
Crossfire Q? in Graphic Cards
I currently have an Msi r6970 lightning. I want to get another for crossfire. I can get the reference amd brand card for alot cheaper than another msi though. Can these be used together in xfire? I've only ever messed with dual gpu setup once with two pny gtx 550 ti's. Never tried mixing...
This is driving me batty. I have sporadic flickering on both of my monitors. I have tried reseating the video cards, checked the plugs to both monitors, etc... I found a possible solution here My problem is that I cannot make/get my computer to boot from the USB. I tried making a bootable USB...
APU Crossfire problems in Graphic Cards
So I've done my fair share of searching for this and I can't seem to figure it out. I built a llano based machine earlier this year and it was running great on windows 8 without a hitch. I decided to upgrade my graphics by installing a 6770 so that my APU could run in crossfire with it. ...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook