Page 1 of 2 12 LastLast
  1.    08 Sep 2017 #1
    Join Date : Sep 2017
    Posts : 12
    Windows 10 Home 64-bit

    BSOD Every Time I Game (atikmdag.sys)


    Hello,

    So I've been having this issue since about the 24th of June (according to the logs).

    It happens every time I play ANY game (CS:GO, Shadow of Mordor, WoW, Arkham Knight, etc). Otherwise the computer is completely fine whenever I do any work or watch anything.

    I've tried to troubleshoot this over time trying a ton of different things, and I just feel like I'm missing a small piece of the puzzle to get this to finally get fixed.

    Have been using "WhoCrashed" to analyze the crashes, and it's basically saying that it's the ATI Radeon Kernel Mode Driver that's causing the issue, but I've DDU'd and reinstalled that to no avail.

    Attached is the log (24 dumps) according to the posting instructions.

    This is my first Windows PC at home, so I'm new to this. It was built by a 3rd party company after I picked all the parts earlier this year, so it's brand new.

    Specs:
    Gigabyte Z270XP-SLI
    intel i5 7600k
    16 GB Corsair Vengeance Black
    MSI RX480 Gaming X (I think)
    TS 650W by XFX

    Let me know if you have any questions.

    Any help is truly appreciated!

    Thank you!

    DESKTOP-FA82IO4-08_09_2017_232823,29.zip
      My ComputerSystem Spec
  2.    08 Sep 2017 #2
    Join Date : Jan 2014
    Central West NSW Australia
    Posts : 803
    7 and 10 on various machines

    Hello and welcome hungrymaven mate your specs are a little thin on the ground please update them a little but in the meantime this dump obviously shows you have a graphics issue so the suggested fix for this is to uninstall the Catalyst Control Centre and use only the driver s for the card Support For Radeon RX 480 GAMING X 8G | Graphics card - The world leader in display performance | MSI Global


    [CODE][VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.
    Arguments:
    Arg1: ffffc70bdc363010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff8079bdef818, 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.

    Debugging Details:
    ------------------


    DUMP_CLASS: 1

    DUMP_QUALIFIER: 400

    BUILD_VERSION_STRING: 15063.0.amd64fre.rs2_release.170317-1834

    SYSTEM_MANUFACTURER: Gigabyte Technology Co., Ltd.

    SYSTEM_PRODUCT_NAME: Z170XP-SLI

    SYSTEM_SKU: Default string

    SYSTEM_VERSION: Default string

    BIOS_VENDOR: American Megatrends Inc.

    BIOS_VERSION: F5

    BIOS_DATE: 04/07/2017

    BASEBOARD_MANUFACTURER: Gigabyte Technology Co., Ltd.

    BASEBOARD_PRODUCT: Z270XP-SLI-CF

    BASEBOARD_VERSION: x.x

    DUMP_TYPE: 2

    BUGCHECK_P1: ffffc70bdc363010

    BUGCHECK_P2: fffff8079bdef818

    BUGCHECK_P3: 0

    BUGCHECK_P4: d

    FAULTING_IP:
    atikmpag+f818
    fffff807`9bdef818 4883ec28 sub rsp,28h

    DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT

    CPU_COUNT: 4

    CPU_MHZ: ed0

    CPU_VENDOR: GenuineIntel

    CPU_FAMILY: 6

    CPU_MODEL: 9e

    CPU_STEPPING: 9

    CPU_MICROCODE: 6,9e,9,0 (F,M,S,R) SIG: 42'00000000 (cache) 42'00000000 (init)

    CUSTOMER_CRASH_COUNT: 1

    BUGCHECK_STR: 0x116

    PROCESS_NAME: System

    CURRENT_IRQL: 0

    ANALYSIS_SESSION_HOST: DESKTOP-9I73FSG

    ANALYSIS_SESSION_TIME: 09-09-2017 10:11:27.0668

    ANALYSIS_VERSION: 10.0.10586.567 amd64fre

    STACK_TEXT:
    ffffb581`bf047778 fffff807`97997d28 : 00000000`00000116 ffffc70b`dc363010 fffff807`9bdef818 00000000`00000000 : nt!KeBugCheckEx
    ffffb581`bf047780 fffff807`97997403 : fffff807`9bdef818 ffffc70b`dc363010 ffffb581`bf047889 00000000`00000000 : dxgkrnl!TdrBugcheckOnTimeout+0xec
    ffffb581`bf0477c0 fffff807`9609b461 : ffffc70b`dc363010 00000000`00388157 00000000`00000009 ffffb581`bf0478d0 : dxgkrnl!TdrIsRecoveryRequired+0x193
    ffffb581`bf0477f0 fffff807`960ee022 : 00000000`00000000 ffffc70b`d80f4000 00000000`00000000 00000000`00000000 : dxgmms2!VidSchiReportHwHang+0x4c1
    ffffb581`bf0478f0 fffff807`960dd2df : ffffc70b`d80f4000 ffffc70b`d75a51f8 ffffc70b`da000100 ffffffff`feced300 : dxgmms2!VidSchWaitForCompletionEvent+0x2e5f6
    ffffb581`bf047970 fffff807`960818b5 : ffffc70b`d3170000 ffffc70b`d3170000 00000000`00000006 ffffc70b`d80f4000 : dxgmms2!VidSchiWaitForCompletePreemption+0x7b
    ffffb581`bf047a60 fffff807`960dc469 : ffffc70b`d86e8010 ffffc70b`d3170000 ffffc70b`d9c3e010 00000000`0000000f : dxgmms2!VidSchiSwitchFromSuspendedDevices+0x1e5
    ffffb581`bf047ad0 fffff807`960e60e0 : ffffc70b`d7590000 ffffc70b`d3170000 ffffc70b`00000000 ffffc70b`d3170000 : dxgmms2!VidSchiSubmitDeviceCommand+0x35
    ffffb581`bf047b00 fffff807`960e5dbe : ffffc70b`d3170500 ffffc70b`d3170000 00000000`00000080 fffff807`960e5d30 : dxgmms2!VidSchiRun_PriorityTable+0x310
    ffffb581`bf047b50 fffff800`77efbac7 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms2!VidSchiWorkerThread+0x8e
    ffffb581`bf047b90 fffff800`77f909e6 : ffffb581`b9460180 ffffc70b`d3135040 fffff800`77efba80 00000000`00000246 : nt!PspSystemThreadStartup+0x47
    ffffb581`bf047be0 00000000`00000000 : ffffb581`bf048000 ffffb581`bf041000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


    STACK_COMMAND: kb

    THREAD_SHA1_HASH_MOD_FUNC: a4338dcef8824cd5748aa9bc6bec7ee99ecd1f75

    THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 9f7ec04f2dd3a858de81f9b52668da462cbb2555

    THREAD_SHA1_HASH_MOD: 96f675609ab6c42221e2413d413146835acfd94d

    FOLLOWUP_IP:
    atikmpag+f818
    fffff807`9bdef818 4883ec28 sub rsp,28h

    FAULT_INSTR_CODE: 28ec8348

    SYMBOL_NAME: atikmpag+f818

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: atikmpag

    IMAGE_NAME: atikmpag.sys
    /CODE]
      My ComputerSystem Spec
  3.    09 Sep 2017 #3
    Join Date : Sep 2017
    Posts : 12
    Windows 10 Home 64-bit
    Thread Starter

    Thank you SO MUCH ICIT2LOL

    I didn't realize it was a different Driver to the Default AMD Crimson <- Noob.

    I'll uninstall it (first I'll have to find it), and let you know if this fixed the issue, though I believe it will.

    Here are the updated specs, this should theoretically include everything. Not sure what you meant by 'they're thin' - did you mean in my profile?

    Case: Cooler Master CM 690 III Window
    Motherboard: Gigabyte GA-Z170X-SLI
    CPU: Intel Core i5 7600K (@ up to 4x 4,50GHz)
    Thermal Paste: NOCTUA NT-H1
    CPU Cooler: Be Quiet! Pure Rock
    Graphic Card: MSI AMD Radeon RX 480 8GB
    RAM: DDR4-2400 RAM CL16 CORSAIR KIT Vengeance Black
    SSD 1 (System): SSD 120GB adata M.2 (I believe... it's definitely not a 2.5 inch)
    HD 2 (Storage): 1TB SATA-III Harddrive Seagate
    CD/DVD: ASUS DRW-24D5MT (24x DVD/CD Burner)
    PSU: XFX 650W TS650G (80+Gold)
    Fans: Default 240 cm front fan, and simple 120 back fan

    These are the specs that I gathered from the order I made with a few updates to the upgrades they send me. I thought it was a Z270 even though I did order a Z170, but the box says Z270... weird.

    Thanks again for taking the time to go through my file(s)!
    Last edited by hungrymaven; 09 Sep 2017 at 08:00.
      My ComputerSystem Spec
  4.    09 Sep 2017 #4
    Join Date : Sep 2017
    Posts : 12
    Windows 10 Home 64-bit
    Thread Starter

    It seems like I never had the Catalyst Control center installed.

    The atikmpag.sys has been found in the new installation of the drivers in the following folders:

    C:\Windows\System32\DriverStore\FileRepository\c0317359.inf_amd64_71db94a48cef0172
    C:\Windows\System32\DriverStore\FileRepository\c0317359.inf_amd64_71db94a48cef0172\B317239
    C:\AMD\Non-WHQL-Radeon-Software-Crimson-ReLive-17.8.2-Win10-64Bit-Aug24\Packages\Drivers\Display\WT6A_INF\B317239

    I'll test some games now to see if the issue is solved, but I have a feeling it won't be. I'll keep you updated

    EDIT: I did do the "express installation" - maybe I needed to untick something with the custom installation version?

    I also use MSI afterburner, but I don't overclock anything (as far as I'm aware).
      My ComputerSystem Spec
  5.    09 Sep 2017 #5
    Join Date : Sep 2017
    Posts : 12
    Windows 10 Home 64-bit
    Thread Starter

    Not trying to bump this thread...

    Just had another BSOD. This time due to the ntoskrnl.exe apparently.

    I've uploaded a new file with the latest minidump.

    Thanks!

    DESKTOP-FA82IO4-09_09_2017_155616,29.zip
      My ComputerSystem Spec
  6.    10 Sep 2017 #6
    Join Date : Apr 2017
    Posts : 8,907
    windows 10 professional version 1607 build 14393.969 64 bit

    Drive easy was a cause of crashes in July.
    Is the software still in use or has it been uninstalled?
    Which drivers were installed by the software?


    Please update the computer specs in the "My Computer" section:

    How To Fill Out Your System Specs
    How To Fill Out Your System Specs
    System Specs - Fill in at Ten Forums:
    System Specs - Fill in at Ten Forums Windows 10 General Tips Tutorials
    In the left corner below in your post you find 'My System Specs'.
    After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.
    System Info - See Your System Specs - Windows 7 Help Forums

    Please include PSU, cooler, case, peripherals (mouse, keyboard, joystick) and anything attached by wireless or wired (printer, headset, xbox, etc.)

    Please post a kernal memory dump:

    file explorer > this PC > local C: drive > right upper corner search > type: C:\Windows\MEMORY.DMP

    Post the memory.dmp file into the thread using a one drive or drop box share link.
    Last edited by zbook; 10 Sep 2017 at 03:56.
      My ComputerSystem Spec
  7.    10 Sep 2017 #7
    Join Date : Sep 2017
    Posts : 12
    Windows 10 Home 64-bit
    Thread Starter

    Hello Zbook,
    Thank you for taking a look at my "case".
    Drive easy was a cause of crashes in July.Is the software still in use or has it been uninstalled?Which drivers were installed by the software?
    The software has been uninstalled.I'm not sure, there definitely were some drivers being installed by it, how do I find this out?
    Please include PSU, cooler, case, peripherals (mouse, keyboard, joystick) and anything attached by wireless or wired (printer, headset, xbox, etc.)
    I believe I have added the info to everything that I can think of. For the internal information I used "Speccy" by Piriform.
    Please post a kernal memory dump:file explorer > this PC > local C: drive > right upper corner search > type: C:\Windows\MEMORY.DMPPost the memory.dmp file into the thread using a one drive or drop box share link.
    Sounds good, here it is:
    Dropbox - MEMORY.DMP

    I had to copy the original memory.dmp to my desktop to be able to upload it for some reason - I hope that doesn't corrupt the file?

    It was halfway uploading (with me playing CS:GO) when another crash happened, so this also includes the latest crash.

    Thanks for taking the time!
      My ComputerSystem Spec
  8.    10 Sep 2017 #8
    Join Date : Apr 2017
    Posts : 8,907
    windows 10 professional version 1607 build 14393.969 64 bit

    The memory dump when debugged displayed 3 misbehaving hardware drivers.
    They were all graphic card misbehaving drivers.
    2 were AMD: atikmdag.sys and atikmpag.sys
    1 was Intel: igdkmd64.sys

    The information that was entered into the "My Computer" section does not yet display all of the hardware.
    The computer has hybrid graphics and only one of the adapters was entered.
    Please update with the Intel graphics.
    Both graphic adapters had misbehaving drivers.

    The AMD was fixed above per ICIT2LOL.
    Please indicate the method that you used to uninstall and reinstall the graphics driver.

    For the Intel graphics driver please use this method:
    Downloads for Graphics Drivers
    Updating a driver: https://answers.microsoft.com/en-us/...=1436753520149


    After replacing the drivers if there are any new BSOD please post a new zip:
    BSOD - Posting Instructions - Windows 10 Forums

    Code:
    Name    Radeon (TM) RX 480 GraphicsPNP Device ID    PCI\VEN_1002&DEV_67DF&SUBSYS_34131462&REV_C7\4&38939596&0&0008Adapter Type    AMD Radeon Graphics Processor (0x67DF), Advanced Micro Devices, Inc. compatibleAdapter Description    Radeon (TM) RX 480 GraphicsAdapter RAM    (1.048.576) bytesInstalled Drivers    aticfx64.dll,aticfx64.dll,aticfx64.dll,amdxc64.dll,aticfx32,aticfx32,aticfx32,amdxc32,atiumd64,atidxx64.dll,atidxx64.dll,atiumdag,atidxx32,atidxx32,atiumdva,atiumd6a.cap,atitmm64Driver Version    22.19.673.0INF File    oem16.inf (ati2mtag_Polaris10DS section)Colour Planes    Not AvailableColour Table Entries    4294967296Resolution    1920 x 1080 x 59 hertzBits/Pixel    32Memory Address    0xD0000000-0xE01FFFFFMemory Address    0xE0000000-0xE01FFFFFI/O Port    0x0000E000-0x0000EFFFMemory Address    0xEF100000-0xEF1FFFFFIRQ Channel    IRQ 4294967292I/O Port    0x000003B0-0x000003BBI/O Port    0x000003C0-0x000003DFMemory Address    0xA0000-0xBFFFFDriver    c:\windows\system32\driverstore\filerepository\c0317359.inf_amd64_71db94a48cef0172\atikmpag.sys (22.19.673.0, 529,02 KB (541.720 bytes), 24.08.2017 19:41)

    Code:
    Adapter Type    Intel(R) HD Graphics Family, Intel Corporation compatibleAdapter Description    Intel(R) HD Graphics 630Adapter RAM    1,00 GB (1.073.741.824 bytes)Installed Drivers    igdumdim64,igd10iumd64,igd10iumd64,igd12umd64,igdumdim32,igd10iumd32,igd10iumd32,igd12umd32Driver Version    21.20.16.4534INF File    oem24.inf (iKBLD_w10_DS section)Colour Planes    Not AvailableColour Table Entries    4294967296Resolution    1920 x 1080 x 60 hertzBits/Pixel    32Memory Address    0xEE000000-0xEEFFFFFFMemory Address    0xC0000000-0xCFFFFFFFI/O Port    0x0000FEC0-0x0000FEFFIRQ Channel    IRQ 4294967284Driver    c:\windows\system32\driverstore\filerepository\igdlh64.inf_amd64_0745f11ce6fc197c\igdkmd64.sys (21.20.16.4534, 10,52 MB (11.033.056 bytes), 01.11.2016 22:05)




    atikmdag.sys ATI Video driver (remove the Catalyst Control Center and only install the Display Driver) http://support.amd.com/us/Pages/AMDSupportHub.aspx
    Get from OEM for laptops



    atikmpag.sys ATI Video driver (remove the Catalyst Control Center and only install the Display Driver) http://support.amd.com/us/Pages/AMDSupportHub.aspx
    Get from OEM for laptops

    Code:
    igfx    igfx    c:\windows\system32\driverstore\filerepository\igdlh64.inf_amd64_0745f11ce6fc197c\igdkmd64.sys    Kernel Driver    Yes    Manual    Running    OK    Ignore    No    Yes
    Code:
    amdkmdag    amdkmdag    c:\windows\system32\driverstore\filerepository\c0317359.inf_amd64_71db94a48cef0172\atikmdag.sys    Kernel Driver    Yes    Manual    Running    OK    Ignore    No    Yesamdkmdap    amdkmdap    c:\windows\system32\driverstore\filerepository\c0317359.inf_amd64_71db94a48cef0172\atikmpag.sys    Kernel Driver    Yes    Manual    Running    OK    Ignore    No    Yes

    Code:
    08.09.2017 21:23    Windows Error Reporting    Fault bucket 0x116_TdrBCR:D_Tdr:9_IMAGE_atikmpag.sys, type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 15b1b960-767a-4280-a780-7556371421ab
    
    Problem signature:
    P1: 116
    P2: ffffc70bdc363010
    P3: fffff8079bdef818
    P4: 0
    P5: d
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\090817-10140-01.dmp
    \\?\C:\Windows\Temp\WER-12046-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER44AB.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER44AC.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER44BC.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_116_855645c20d680708f78b6a98cdfa115bcaacb70_00000000_cab_1ff10b74
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: 031372db-0046-4d8f-90a7-764d30b06acd
    Report Status: 268435456
    Hashed bucket:08.09.2017 21:23    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: a2072f78-1e65-4768-bdfa-648306eaa6f8
    
    Problem signature:
    P1: 141
    P2: ffffc70bd9cb5010
    P3: fffff8079bdef818
    P4: 0
    P5: 2a8
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170908-2321.dmp
    \\?\C:\Windows\Temp\WER-12046-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER446B.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER448A.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER448B.tmp.txt
    \\?\C:\Windows\Temp\WERE8C1.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_22dbfaedca72b9a3570fe749274d2c326a463e_00000000_cab_1ff0ebe6
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: a18b98e5-a2c4-4e83-8ed8-fe9e13e96e64
    Report Status: 268435456
    Hashed bucket:08.09.2017 21:22    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 70815a35-c2a2-495e-9d3f-9fa2474fc70a
    
    Problem signature:
    P1: 141
    P2: ffffc70bd9cb5010
    P3: fffff8079bdef818
    P4: 0
    P5: 2a8
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170908-2321.dmp
    \\?\C:\Windows\Temp\WER-350375-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5C31.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5C39.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5C49.tmp.txt
    \\?\C:\Windows\Temp\WERC22B.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_22dbfaedca72b9a3570fe749274d2c326a463e_00000000_cab_1ff0c5a1
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: 42256689-fc89-4702-8cf5-1bdd82b57693
    Report Status: 268435456
    Hashed bucket:08.09.2017 21:22    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 97b2ad43-e875-438a-9332-629a646e381b
    
    Problem signature:
    P1: 141
    P2: ffffc70bd9cb5010
    P3: fffff8079bdef818
    P4: 0
    P5: 2a8
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170908-2321.dmp
    \\?\C:\Windows\Temp\WER-340359-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3540.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3546.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3557.tmp.txt
    \\?\C:\Windows\Temp\WER7EA6.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_22dbfaedca72b9a3570fe749274d2c326a463e_00000000_cab_1ff08462
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: 2ce79eff-49e7-46ad-8fca-2eea5d989a46
    Report Status: 268435456
    Hashed bucket:
    Code:
    08.09.2017 21:21    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 9002faba-a8f8-4590-8a46-d4ca782b6905
    
    Problem signature:
    P1: 141
    P2: ffffc70bd9cb5010
    P3: fffff8079bdef818
    P4: 0
    P5: 2a8
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170908-2321.dmp
    \\?\C:\Windows\Temp\WER-318421-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDF7F.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE202.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE212.tmp.txt
    \\?\C:\Windows\Temp\WER33E9.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_22dbfaedca72b9a3570fe749274d2c326a463e_00000000_cab_18093715
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: c092bd63-715f-4a96-bd18-09ef4efe646c
    Report Status: 268435456
    Hashed bucket:
    
    08.09.2017 21:21    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 706bab2e-cb16-4d18-9012-052321dac1ab
    
    Problem signature:
    P1: 141
    P2: ffffc70bd7a2e010
    P3: fffff8079bdef818
    P4: 0
    P5: 4
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170908-2320.dmp
    \\?\C:\Windows\Temp\WER-313250-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCB6A.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCB6A.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCB7B.tmp.txt
    \\?\C:\Windows\Temp\WERE5E9.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_39d06f6d31aabbe2f2e97fdb624fa708683a8cd_00000000_cab_04f8e924
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: 10ca3d5e-cc15-47e4-84e2-bd622d4f3032
    Report Status: 268435456
    Hashed bucket:




    Code:
    27.07.2017 17:47    Windows Error Reporting    Fault bucket 0x3D_atikmdag!unknown_function, type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 9fae82bd-c406-46a7-a8c1-eb8ff2bc12cb
    
    Problem signature:
    P1: 3d
    P2: ffff8f815866b948
    P3: ffff8f815866b190
    P4: 0
    P5: 0
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\072717-11062-01.dmp
    \\?\C:\Windows\Temp\WER-11953-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3E70.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3E74.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3E85.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_3d_51226f4a89c4f1817d69b83ae1608ee010fa6133_00000000_cab_1684701f
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: 02ad83c6-2b72-421c-a56f-b406c6e67fd0
    Report Status: 268435456
    Hashed bucket:
    Code:
    24.07.2017 19:57    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: ba93198f-a9d6-4151-afc7-c5568d56869f
    
    Problem signature:
    P1: 141
    P2: ffffd78244b154a0
    P3: fffff8095b0bf640
    P4: 0
    P5: 195c
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170724-2156.dmp
    \\?\C:\Windows\Temp\WER-1775593-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1F2D.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1F2D.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1F3D.tmp.txt
    \\?\C:\Windows\Temp\WER4311.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_a679e3e0a4fdfe879612a4f5ca724f2c8ad2448_00000000_cab_10c346ba
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: 946f723c-b1ea-4259-a7eb-5e5a1970a0a0
    Report Status: 268435456
    Hashed bucket:
    Code:
    24.07.2017 19:20    Windows Error Reporting    Fault bucket AV_atikmdag!CpCmdFrameMgr_vi::PatchIb, type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 1bc0a1eb-d209-4f04-8cf3-ca98c53c9282
    
    Problem signature:
    P1: 1000007e
    P2: ffffffff80000003
    P3: fffff806414c6669
    P4: ffff80009c332288
    P5: ffff80009c331ad0
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\072417-7406-01.dmp
    \\?\C:\Windows\Temp\WER-9640-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER346D.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3596.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER35A7.tmp.txt
    \\?\C:\Windows\Temp\WER8D2D.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1000007e_52e8f2c4c914e293a2ba6977d6d2161e35072e9_00000000_cab_1c5c948f
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: 204d5189-6221-4565-9a8a-048bee7e274b
    Report Status: 268435456
    Hashed bucket:
    Code:
    23.07.2017 20:52    Windows Error Reporting    Fault bucket AV_atikmdag!ProcessCallbacks, type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 03e164ff-91d5-4e92-88d1-028a7eeb180e
    
    Problem signature:
    P1: d1
    P2: a8840fc0b1
    P3: 8
    P4: 0
    P5: fffff808cdad7e62
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\072317-10062-01.dmp
    \\?\C:\Windows\Temp\WER-10734-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER39CC.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER39CE.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER39DF.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_d1_c1ae7e8e71bf976cdfc51b81a80274178e72ff8_00000000_cab_17e47f32
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: 7b9465a7-f3a8-452b-b4bb-39021bde78f1
    Report Status: 268435456
    Hashed bucket:
    Code:
    23.07.2017 18:29    Windows Error Reporting    Fault bucket 0x193_DxgkrnlLiveDump:804_Status_0xC0000001_Driver_atikmpag_failed_DdiStartDevice_dxgkrnl!DxgCreateLiveDumpWithWdLogs, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: a76b45d3-d67b-49db-aa37-d79e179c463a
    
    Problem signature:
    P1: 193
    P2: 804
    P3: ffffffffc0000001
    P4: 108
    P5: fffff80074490eb4
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170723-2028.dmp
    \\?\C:\Windows\Temp\WER-7645593-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB5FD.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB60F.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB62F.tmp.txt
    \\?\C:\Windows\Temp\WERCF62.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_193_24ccc64c4f88123c70bd6775db317fac565876_00000000_cab_05a8d29d
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: 831a8ca6-c239-4265-9d5c-bbea1448eaf7
    Report Status: 268435456
    Hashed bucket:
    Code:
    21.07.2017 19:19    Windows Error Reporting    Fault bucket AV_atikmdag!unknown_function, type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 91bfa253-82b4-496e-8b3c-613dc726292d
    
    Problem signature:
    P1: d1
    P2: ffffa41d150b78e8
    P3: 2
    P4: 1
    P5: fffff805f35da663
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\072117-10703-01.dmp
    \\?\C:\Windows\Temp\WER-11328-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3BEF.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3BF3.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3C04.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_d1_199a464a5f78cf15cb157df3265ee7e7bb94197a_00000000_cab_14e459d8
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: b0ee6ed8-4953-445a-9a98-10d1519b3d4c
    Report Status: 268435456
    Hashed bucket:
    Code:
    04.07.2017 20:28    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 66cde7c8-ca33-4e6a-8ef9-1a6a814d2f0d
    
    Problem signature:
    P1: 141
    P2: ffffd68e4754f010
    P3: fffff80fce5cf654
    P4: 0
    P5: 2d8
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170704-2228.dmp
    \\?\C:\Windows\Temp\WER-172434375-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2C52.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2C52.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2C63.tmp.txt
    \\?\C:\Windows\Temp\WER4634.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_d09d2f24575968b4e5ab5beca5d7b55b44a55ff6_00000000_cab_1343497f
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: fb85840c-cc27-4f01-bc6c-ee81ae6b5ad9
    Report Status: 268435456
    Hashed bucket:
    Code:
    27.06.2017 16:23    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 7bc45e05-4589-4c7a-a8fc-ecd157bf43dc
    
    Problem signature:
    P1: 141
    P2: ffffbc8d08526150
    P3: fffff80613b5f654
    P4: 0
    P5: 4
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170627-1823.dmp
    \\?\C:\Windows\Temp\WER-189574390-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCD4F.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCD4F.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCD60.tmp.txt
    \\?\C:\Windows\Temp\WER48D.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_f8f7121e267b3eb52ecfa136b58dfa89bebcbdf6_00000000_cab_2a0d098d
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: cdc08f48-0809-46f3-bd5d-0e0fe83205b5
    Report Status: 268435456
    Hashed bucket:
    Code:
    26.06.2017 16:16    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: db82fa84-06d1-4d82-a838-a15dc90e97e0
    
    Problem signature:
    P1: 141
    P2: ffffbc8cf3a58310
    P3: fffff80613b5f654
    P4: 0
    P5: 4
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170626-1815.dmp
    \\?\C:\Windows\Temp\WER-102723765-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7DB5.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7DD5.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7DE5.tmp.txt
    \\?\C:\Windows\Temp\WER9862.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_1d3463d7469905892cd21c75165619f810c195_00000000_cab_22779c3a
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: 549b6a23-df80-4a34-ab43-bc6f52a68f6e
    Report Status: 268435456
    Hashed bucket:
    Code:
    25.06.2017 11:40    Windows Error Reporting    Fault bucket 0x193_DxgkrnlLiveDump:804_Status_0xC0000001_Driver_atikmpag_failed_DdiStartDevice_dxgkrnl!DxgCreateLiveDumpWithWdLogs, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 9651870e-50bf-473e-a4b1-cba2fc0dfb84
    
    Problem signature:
    P1: 193
    P2: 804
    P3: ffffffffc0000001
    P4: 108
    P5: fffff8024d730eb4
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170625-1340.dmp
    \\?\C:\Windows\Temp\WER-79195578-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7367.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7367.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7377.tmp.txt
    \\?\C:\Windows\Temp\WER8D87.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_193_e246c3ae2ec997fecd279cd7035b9a4bb813bad_00000000_cab_107490c2
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: e5d7bad7-b81e-4a84-841d-2351c7d13d3d
    Report Status: 268435456
    Hashed bucket:
    Code:
    24.06.2017 16:15    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_atikmpag.sys, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 77cd0adb-df0f-4653-b4c1-95f8f82e0261
    
    Problem signature:
    P1: 141
    P2: ffffb004032be110
    P3: fffff80248b4f654
    P4: 0
    P5: 22fc
    P6: 10_0_15063
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170624-1815.dmp
    \\?\C:\Windows\Temp\WER-9287453-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBAD6.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBAD6.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBAE6.tmp.txt
    \\?\C:\Windows\Temp\WERF6A7.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_1e2633c3f62d5fd3982e6c398fbdebeb44b9af_00000000_cab_1051fa50
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report ID: 6f9965ab-aed1-43ad-84db-11b9adc01387
    Report Status: 268435456
    Hashed bucket:
      My ComputerSystem Spec
  9.    10 Sep 2017 #9
    Join Date : Jan 2014
    Central West NSW Australia
    Posts : 803
    7 and 10 on various machines

    Hello hungrymaven I will leave you with zbook as I am sure he can carry on from here

    Just as by the by though I had no idea that you were using a driver finder software and just as a personal thing I never use add on software that will check for drivers except for one and then only in desperation, Windows 7 and it is removed immediately after use. I also include any software that promises an increase in performance of a machine puts the registry right etc etc because they often well more than often instil more problems than when you didn't have them on board. Plus I think that the OS is so much more involved in the drivers than 7 ever was and I am not that familiar with 10 yet to make comment I can only pick the glaringly obvious right now.
    Anyway I shall let you get on with where you are up to good luck I'm sure the others can get it fixed for you.
      My ComputerSystem Spec
  10.    10 Sep 2017 #10
    Join Date : Sep 2017
    Posts : 12
    Windows 10 Home 64-bit
    Thread Starter

    The memory dump when debugged displayed 3 misbehaving hardware drivers.
    They were all graphic card misbehaving drivers.
    2 were AMD: atikmdag.sys and atikmpag.sys
    1 was Intel: igdkmd64.sys

    The information that was entered into the "My Computer" section does not yet display all of the hardware.
    The computer has hybrid graphics and only one of the adapters was entered.
    Please update with the Intel graphics.
    Both graphic adapters had misbehaving drivers.

    The AMD was fixed above per ICIT2LOL.
    Please indicate the method that you used to uninstall and reinstall the graphics driver.

    For the Intel graphics driver please use this method:
    Downloads for Graphics Drivers
    Updating a driver: https://answers.microsoft.com/en-us/...=1436753520149
    OK, I didn't know about the Intel one to be honest, so that's new to me - thanks for finding that.

    I've DDU'd it and reinstalled from the link you posted.

    I've updated the "My Computer" section to include the missing adapter I believe.

    Regarding the AMD issue - the CCC that is being installed comes from the link that ICIT2LOL shared (and directly from AMD's website too), so it seems to be reinstalled no matter what I do.

    This time I chose "custom installation" and unchecked "AMD Settings", to just install the drivers perhaps that fixes it, screenshot with settings attached.
    Click image for larger version. 

Name:	amd_driver_install_settings.png 
Views:	1 
Size:	32.2 KB 
ID:	152700

    Previously I had used the AMD uninstaller to uninstall the AMD drivers, this time I DDU'd it in Safe Mode, so perhaps that got rid of everything this time? The driver reinstallation process was mentioned above.

    I won't have time to "stress test" this tonight, but if there are any issues tomorrow I'll update the thread

    Thanks again!
      My ComputerSystem Spec

 
Page 1 of 2 12 LastLast


Similar Threads
Thread Forum
BSOD when starting computer first time in day. sometimes in game
Hello, I have had many BSODs regarding ntoskrnl.exe, FLTMGR.SYS, WdFilter.sys since I have updated to Windows 10 from Windows 7. I have checked drivers, memtest, and bios drivers. All is fine. Memtest for a whole night. Specs: i7 4970k gtx 1080...
BSOD Crashes and Debugging
BSOD playing any game for any period of time, error 0x00000124
So i just got a vanilla installation going for about a week and this started happening. Also ran sfc nothing returned, cleaned the register did not help. ran cpu stress test no result. Will run memtest overnight, after having ran 9 runtroughs...
BSOD Crashes and Debugging
BSOD every time I start a game (not overheating)
61603 I hope this is the right file, I cannot find anything else. Please help. I have tried everything.
BSOD Crashes and Debugging
BSOD SYSTEM_SERVICE_EXCEPTION atikmdag.sys
Hello Guys, i have been getting an error whenever i install my graphics drivers. Any version i use results in a BSOD on startup. the BSOD says: SYSTEM_SERVICE_EXCEPTION (atikmdag.sys) Also, whenever my computer restarts it shuts straight off...
BSOD Crashes and Debugging
BSOD's from atikmdag.sys
Hi Guys, I'm new to ten forums so I hope I'm posting this in the correct place. :huh: Ive had a few BSOD's from atikmdag.sys This happens when it seems that windows update installs a new video driver Name AMD Radeon R7 200 Series...
BSOD Crashes and Debugging
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 23:01.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums