Windows 10: Is it my graphics card?

Page 2 of 2 FirstFirst 12
  1.    18 Mar 2018 #11

    No I have not.
      My ComputerSystem Spec


  2. Posts : 20,986
    windows 10 professional version 1607 build 14393.969 64 bit
       19 Mar 2018 #12

    Hi RoachBoi,

    There were no BSOD dump files.
    The logs displayed many problems related to Nvidia GPU.
    Windows failed fast startup.
    The logs displayed many kernel dumps.
    The bugchecks were 117 and 141.

    For all tests /steps please post images into the thread.
    If there are any problems posting images please use one drive or drop box share links.

    1) Please update the specs in the "My Computer" section:
    System Specs - Fill in at Ten Forums:
    System Specs - Fill in at Ten Forums Windows 10 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

    Include PSU. cooler, case, peripherals and anything attached to the computer by wired or wireless (mouse, keyboard, headset, printer, xbox, USB wireless network card, etc.)

    2) Open administrative command prompt and type or copy and paste:
    3) sfc /scannow
    4) dism /online /cleanup-image /restorehealth
    5) chkdsk /scan
    6) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

    7) Increase the free space on C: so that there is 30 - 35 GB or more free space.

    8) Make sure that there is no over clocking while troubleshooting.

    9) Sometimes there are problems in the bios that produce bsod.
    The BIOS: Version/Date American Megatrends Inc. 1.60, 3/31/2017
    10) Please check to see if this is the most up to date version.

    11) Open the website for the computer or motherboard manufacturer to view the drivers and post a URL or hyperlink into the thread.

    12) To ensure that there are no improper bios settings please reset the bios.

    13) Sometimes there can be failure to boot after resetting the bios.
    14) Backup the computer files to another drive or to the cloud.
    15) Make a backup image using Macrium:
    Macrium Software | Macrium Reflect Free:
    Macrium Software | Macrium Reflect Free

    16) And please create a brand new restore point.

    How to Clear Your Computers CMOS to Reset BIOS Settings:
    How to Clear Your Computers CMOS to Reset BIOS Settings
    3 Ways to Reset Your BIOS - wikiHow:
    3 Ways to Reset Your BIOS - wikiHow

    17) If the computer has Ccleaner > click windows tab > scroll down to system and advanced > post an image into the thread

    18) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings
    a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery into the thread.
    b) > on the advanced tab under performance > click on settings > under performance options > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory tab into the thread

    19) Choose one of the temperature monitoring software applications: Speecy, HW monitor, Speed fan:Speccy - Free Download - Piriform: Speccy - System Information - Free
    Download Speccy | Find your computer specs, free!
    HWMONITOR | Softwares | CPUID: HWMONITOR | Softwares | CPUID
    HWMONITOR | Softwares | CPUID
    SpeedFan - Access temperature sensor in your computer: SpeedFan - Access temperature sensor in your computer
    SpeedFan - Access temperature sensor in your computer

    20) Ensure the GPU is free from dust build up and that the fan is working correctly

    21) Re-seat the GPU and check all connections are securely made

    22) Check PSU voltages in BIOS
    Post images for:
    a) BIOS 3.3, 5 and 12 voltage values
    b) CPU voltage and frequency?

    23) Run memtest86+ version 5.01 for at least 8 passes. Memtest86+ - Advanced Memory Diagnostic Tool
    This may take hours so plan to run it overnight.
    a) Please make sure you use the Memtest86+ version 5.01 with the link below.
    Memtest86+ - Advanced Memory Diagnostic Tool
    The testing is done not by time but by passes.
    The more passes the better.
    There are a significant number of false negatives if fewer than 8 passes are made.
    A false negative is a test pass when there is malfunctioning RAM.
    There is 16 GB of RAM on the computer.
    Memtest86+ version 5.01 testing takes approximately 1 - 2 hours /GB RAM
    Just 1 error is a fail and you can abort testing.
    Then test 1 RAM module at a time in the same DIMM each for 8 or more passes.
    b) When Memtest86+ version 5.01 has completed 8 or more passes use a camera or smart phone camera to take a picture and post an image into the thread.
    Memory problems. - Microsoft Community
    MemTest86+ - Test RAM Windows 10 Tutorials

    24) Turn off Windows fast startup:
    Turn On or Off Fast Startup in Windows 10 Windows 10 Tutorials


    Code:
    Event[6393]:  Log Name: System
      Source: Display
      Date: 2018-03-18T01:26:47.044
      Event ID: 4101
      Task: N/A
      Level: Warning
      Opcode: Info
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-LRK0CHV
      Description: 
    Display driver nvlddmkm stopped responding and has successfully recovered.
    Code:
    Name    NVIDIA GeForce GTX 1080PNP Device ID    PCI\VEN_10DE&DEV_1B80&SUBSYS_85AA1043&REV_A1\4&39014AC4&0&0008
    Adapter Type    GeForce GTX 1080, NVIDIA compatible
    Adapter Description    NVIDIA GeForce GTX 1080
    Adapter RAM    (1,048,576) bytes
    Installed Drivers    C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_048172e9d7cc483d\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_048172e9d7cc483d\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_048172e9d7cc483d\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_048172e9d7cc483d\nvldumdx.dll
    Driver Version    23.21.13.9101
    INF File    oem77.inf (Section118 section)
    Color Planes    Not Available
    Color Table Entries    4294967296
    Resolution    1440 x 900 x 59 hertz
    Bits/Pixel    32
    Memory Address    0xDE000000-0xDEFFFFFF
    Memory Address    0xC0000000-0xCFFFFFFF
    Memory Address    0xD0000000-0xD1FFFFFF
    I/O Port    0x0000E000-0x0000E07F
    IRQ Channel    IRQ 16
    I/O Port    0x000003B0-0x000003BB
    I/O Port    0x000003C0-0x000003DF
    Memory Address    0xA0000-0xBFFFF
    Driver    c:\windows\system32\driverstore\filerepository\nv_dispi.inf_amd64_048172e9d7cc483d\nvlddmkm.sys (23.21.13.9101, 16.71 MB (17,524,720 bytes), 3/2/2018 9:41 AM)
    Code:
    3/6/2018 5:13 AM    Windows Error Reporting    Fault bucket LKD_0x117_Tdr:3_TdrBug:575504_TdrVTR:0_IMAGE_nvlddmkm.sys, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 0ec1adb1-a3e4-4c55-8370-bb5a164ec4fd
    
    Problem signature:
    P1: 117
    P2: ffff96072cb8b4a0
    P3: fffff8058d57c170
    P4: 0
    P5: a70
    P6: 10_0_16299
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20180306-0013.dmp
    \\?\C:\WINDOWS\TEMP\WER-82146578-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7F05.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7F05.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7F25.tmp.txt
    \\?\C:\Windows\Temp\WERB846.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_117_e68875c29ac47ce182a38f37fddbd55171135358_00000000_cab_1bb9ba29
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 9cc78e93-aebe-4132-a65f-bfde4ade8fc1
    Report Status: 268435456
    Hashed bucket:3/6/2018 11:22 PM    Windows Error Reporting    Fault bucket LKD_0x117_Tdr:3_TdrBug:575504_TdrVTR:0_IMAGE_nvlddmkm.sys, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 109e66cf-ad0b-4a10-b860-cd25b91b5f33
    
    Problem signature:
    P1: 117
    P2: ffff96072fb284a0
    P3: fffff8058d57c170
    P4: 0
    P5: 93c
    P6: 10_0_16299
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20180306-1822.dmp
    \\?\C:\WINDOWS\TEMP\WER-147488609-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8A00.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8A00.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8A10.tmp.txt
    \\?\C:\Windows\Temp\WER9CFC.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_117_d7ac87e68a9899f3dd6dc58a46cbbc3ae904eaf_00000000_cab_2bae9e43
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: c4eb7a83-59de-41ab-8907-dac59ef3117e
    Report Status: 268435456
    Hashed bucket:
    3/6/2018 8:32 PM    Windows Error Reporting    Fault bucket LKD_0x117_Tdr:3_TdrBug:575504_TdrVTR:0_IMAGE_nvlddmkm.sys, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 485ae716-b994-4c46-baa0-6f78c70b5877
    
    Problem signature:
    P1: 117
    P2: ffff9607336594a0
    P3: fffff8058d57c170
    P4: 0
    P5: 29ac
    P6: 10_0_16299
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20180306-1531.dmp
    \\?\C:\WINDOWS\TEMP\WER-137266140-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8CC5.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8CC5.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8CD6.tmp.txt
    \\?\C:\Windows\Temp\WERB6E4.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_117_2e38125564927368de527ede86291aeacbf0e1a1_00000000_cab_2c1ab81b
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 26b2bac8-df52-4183-af7e-41b227a404bb
    Report Status: 268435456
    Hashed bucket:
    3/5/2018 1:39 AM    Windows Error Reporting    Fault bucket LKD_0x117_Tdr:3_TdrBug:575504_TdrVTR:0_IMAGE_nvlddmkm.sys, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 75ab03b0-df67-4900-ad3f-4f525c55506d
    
    Problem signature:
    P1: 117
    P2: ffffe400ec2604a0
    P3: fffff802304bc170
    P4: 0
    P5: 3a1c
    P6: 10_0_16299
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20180304-2039.dmp
    \\?\C:\WINDOWS\TEMP\WER-2733156-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBB88.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBB9E.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBBAE.tmp.txt
    \\?\C:\Windows\Temp\WERCD4C.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_117_15a89214bc27f4a2f172b2d88f780d08d5f13f3_00000000_cab_25edce06
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 74086605-b74b-43f9-93fb-dbca22f947e1
    Report Status: 268435456
    Hashed bucket:
    3/5/2018 1:39 AM    Windows Error Reporting    Fault bucket LKD_0x117_Tdr:3_TdrBug:575504_TdrVTR:0_IMAGE_nvlddmkm.sys, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 7b874a0e-4988-448e-94d1-897304a41ed2
    
    Problem signature:
    P1: 117
    P2: ffffe400ecf52010
    P3: fffff802304bc170
    P4: 0
    P5: 23f8
    P6: 10_0_16299
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20180304-2038.dmp
    \\?\C:\WINDOWS\TEMP\WER-2709218-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5E74.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5E87.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5E98.tmp.txt
    \\?\C:\Windows\Temp\WER87A8.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_117_f938ac72a776f5bfa57487d2fdea4aa13f64ad2_00000000_cab_1a618853
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 8dd701f2-067c-4e9a-b05b-a7b32d03c803
    Report Status: 268435456
    Hashed bucket:
    3/6/2018 5:26 AM    Windows Error Reporting    Fault bucket LKD_0x117_Tdr:3_TdrBug:575504_TdrVTR:0_IMAGE_nvlddmkm.sys, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: d9291859-55a6-4165-ac7f-2985012b2c40
    
    Problem signature:
    P1: 117
    P2: ffff96072ae14010
    P3: fffff8058d57c170
    P4: 0
    P5: 2270
    P6: 10_0_16299
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20180306-0026.dmp
    \\?\C:\WINDOWS\TEMP\WER-82943796-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA704.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA704.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA725.tmp.txt
    \\?\C:\Windows\Temp\WERC868.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_117_7cea9f695c8d5957e049ffb43523cb9581c2f887_00000000_cab_0d51c9af
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: cd56bf1d-fb47-441a-ab16-a8257c1bdba7
    Report Status: 268435456
    Hashed bucket:
    3/5/2018 1:37 AM    Windows Error Reporting    Fault bucket LKD_0x117_Tdr:3_TdrBug:575504_TdrVTR:0_IMAGE_nvlddmkm.sys, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: e27b297d-a472-4522-90e9-6498526b166a
    
    Problem signature:
    P1: 117
    P2: ffffe400ee8b2010
    P3: fffff802304bc170
    P4: 0
    P5: 3028
    P6: 10_0_16299
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20180304-2037.dmp
    \\?\C:\WINDOWS\TEMP\WER-2614953-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREE59.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREE59.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREE6A.tmp.txt
    \\?\C:\Windows\Temp\WERD4C.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_117_78ca6f241f93871ed417cd3296eb43d20adcfc_00000000_cab_18740e93
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 0c505733-4d42-413f-ba80-bcc0fda3c150
    Report Status: 268435456
    Hashed bucket:

    Code:
    3/4/2018 11:16 PM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 0e906c69-b1bc-4148-908e-30fc3a523df6
    
    Problem signature:
    P1: 141
    P2: ffffb681c8d30370
    P3: fffff803614bc170
    P4: 0
    P5: 14f0
    P6: 10_0_16299
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20180304-1816.dmp
    \\?\C:\WINDOWS\TEMP\WER-173772515-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER95F8.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER95FE.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER960E.tmp.txt
    \\?\C:\Windows\Temp\WERD0C9.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_c9ee96263a02d4b668f81f749da9777748ca95a_00000000_cab_2a7bd16a
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 8fc642d6-7f5d-4f04-acde-c2a520a91e7d
    Report Status: 268435456
    Hashed bucket:3/12/2018 11:53 PM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 10080705-e491-4aa4-9aca-0ebf846849b6
    
    Problem signature:
    P1: 141
    P2: ffffd20088bd74a0
    P3: fffff80e67bdc170
    P4: 0
    P5: 24ec
    P6: 10_0_16299
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20180312-1953.dmp
    \\?\C:\WINDOWS\TEMP\WER-90515-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6B28.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6B28.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6B39.tmp.txt
    \\?\C:\Windows\Temp\WER8068.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_c76f9213566593125a603e117d97ffead7_00000000_cab_399d824a
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: abfaddd2-9e6d-4e81-a145-15a67d710da3
    Report Status: 268435456
    Hashed bucket:
    3/16/2018 4:38 AM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 1d2d6e53-61fe-4317-b8e8-30c6726b8ecd
    
    Problem signature:
    P1: 141
    P2: ffff8e04703e24a0
    P3: fffff80d4b0dc170
    P4: 0
    P5: 3374
    P6: 10_0_16299
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20180316-0037.dmp
    \\?\C:\WINDOWS\TEMP\WER-18799484-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE55F.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE55F.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE57F.tmp.txt
    \\?\C:\Windows\Temp\WER4014.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_474b1a98e72bd823e44f426ec57aa0c9e127c11_00000000_cab_10934189
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 6ebf4c75-1a9b-47bd-b5e1-6bfb16cf920e
    Report Status: 268435456
    Hashed bucket:
    3/17/2018 2:04 AM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 215284f5-e156-4598-83d6-b26dcaf480c1
    
    Problem signature:
    P1: 141
    P2: ffffb3812ae844a0
    P3: fffff802e35cc170
    P4: 0
    P5: 2258
    P6: 10_0_16299
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20180316-2203.dmp
    \\?\C:\WINDOWS\TEMP\WER-1970093-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1C5F.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1C5F.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1C80.tmp.txt
    \\?\C:\Windows\Temp\WER3C9B.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_5b857aef5b4e5382fd78469553266fa162d3a96_00000000_cab_32f63d64
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: e4147157-6866-4f70-986e-243258efaf9e
    Report Status: 268435456
    Hashed bucket:
    3/12/2018 11:51 PM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 2243281a-f6f6-483c-ab43-fdf1b32a4335
    
    Problem signature:
    P1: 141
    P2: ffffe580adedf4a0
    P3: fffff80e51b8c170
    P4: 0
    P5: 311c
    P6: 10_0_16299
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20180312-1951.dmp
    \\?\C:\WINDOWS\TEMP\WER-64900093-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER539E.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER539E.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER53AF.tmp.txt
    \\?\C:\Windows\Temp\WER7DAE.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_2d4db09e9cc333534422ca84f8b092f5f3c3d58e_00000000_cab_28da801d
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 60fb91db-2924-41e8-b650-09cb1c3548fd
    Report Status: 268435456
    Hashed bucket:
    3/5/2018 1:00 AM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 28c091f1-80c6-4e53-8cb7-69ff18d64b5d
    
    Problem signature:
    P1: 141
    P2: ffffe400f80934a0
    P3: fffff802304bc170
    P4: 0
    P5: 32d8
    P6: 10_0_16299
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20180304-1959.dmp
    \\?\C:\WINDOWS\TEMP\WER-366015-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9CB4.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9CBE.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9CCF.tmp.txt
    \\?\C:\Windows\Temp\WER188C.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_b87741c3c657c93b1f945888e97ea2c6cea2fa_00000000_cab_21761a60
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: e3ba145d-d9ae-4d0d-a034-a03192e20083
    Report Status: 268435456
    Hashed bucket:
    3/5/2018 1:00 AM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 29885070-093e-44b7-aee6-7bf941d6de7f
    
    Problem signature:
    P1: 141
    P2: ffffe400f80934a0
    P3: fffff802304bc170
    P4: 0
    P5: 32d8
    P6: 10_0_16299
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20180304-1959.dmp
    \\?\C:\WINDOWS\TEMP\WER-343953-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER457C.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4592.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4593.tmp.txt
    \\?\C:\Windows\Temp\WERE04F.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_b87741c3c657c93b1f945888e97ea2c6cea2fa_00000000_cab_2175e259
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 934b3b42-843f-4651-81aa-0b3189805c71
    Report Status: 268435456
    Hashed bucket:
    3/18/2018 2:17 AM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 2ca6b6f6-a055-419b-9799-bc6498e5fe9c
    
    Problem signature:
    P1: 141
    P2: ffffe0810405d250
    P3: fffff805d3abc170
    P4: 0
    P5: 332c
    P6: 10_0_16299
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20180317-2217.dmp
    \\?\C:\WINDOWS\TEMP\WER-3329906-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE05A.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE05A.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE06B.tmp.txt
    \\?\C:\Windows\Temp\WERFC9.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_413d23c9bc89f1a7b1a686917ec0cfa8f9b7814b_00000000_cab_2f3b114d
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 98f5af8e-8b5c-47c8-a0d5-09ca1d414a32
    Report Status: 268435456
    Hashed bucket:
    3/2/2018 6:41 PM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 2cb056be-c342-43c3-b5c3-37ce368425a7
    
    Problem signature:
    P1: 141
    P2: ffffa80e0eaf8010
    P3: fffff80054d7c170
    P4: 0
    P5: 1f34
    P6: 10_0_16299
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20180302-1341.dmp
    \\?\C:\WINDOWS\TEMP\WER-140161171-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBB13.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBB23.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERBB24.tmp.txt
    \\?\C:\Windows\Temp\WERDE1D.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_436483ffa7d2a7486e7f98fe401842fe6d2fac6c_00000000_cab_17aee000
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 3f865f94-fe80-4910-bc6d-76d761229427
    Report Status: 268435456
    Hashed bucket:
    3/18/2018 3:38 AM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 2d757b11-49e8-46f3-925a-b1444411670b
    
    Problem signature:
    P1: 141
    P2: ffffe080edc63010
    P3: fffff805d3abc170
    P4: 0
    P5: 2f04
    P6: 10_0_16299
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20180317-2338.dmp
    \\?\C:\WINDOWS\TEMP\WER-8198078-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2182.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2184.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER21A4.tmp.txt
    \\?\C:\Windows\Temp\WER4721.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_15aa1ac4ce822ca7a2ed5254c243f94a4fc6b4_00000000_cab_0b25496c
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: d584dab1-9527-425f-8f81-fef208c4a84a
    Report Status: 268435456
    Hashed bucket:
    3/6/2018 2:41 AM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 32ac6acc-10ab-4839-955f-8a4b2f9e0cfe
    
    Problem signature:
    P1: 141
    P2: ffff960735e6f4a0
    P3: fffff8058d57c170
    P4: 0
    P5: 1734
    P6: 10_0_16299
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20180305-2140.dmp
    \\?\C:\WINDOWS\TEMP\WER-73010687-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1523.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1527.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1538.tmp.txt
    \\?\C:\Windows\Temp\WER5495.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_5868796f82d19b63bd60951e7b921e3e3d45eea_00000000_cab_23f25672
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 2e70768d-7ed1-4a31-a60c-37a4b982b7e7
    Report Status: 268435456
    Hashed bucket:
    3/12/2018 11:54 PM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 3888b8c5-6bc7-4d20-b607-5f5389e98782
    
    Problem signature:
    P1: 141
    P2: ffffd20088bd74a0
    P3: fffff80e67bdc170
    P4: 0
    P5: 24ec
    P6: 10_0_16299
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20180312-1953.dmp
    \\?\C:\WINDOWS\TEMP\WER-99406-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8C9B.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8CA1.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8CC1.tmp.txt
    \\?\C:\Windows\Temp\WER3CFC.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_c76f9213566593125a603e117d97ffead7_00000000_cab_399e3f03
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 8910589c-2ca1-4780-82ee-f9af1a6d2ed5
    Report Status: 268435456
    Hashed bucket:
    3/7/2018 1:27 AM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 3b83c13a-55c9-4e20-bc2f-c4d9e34d559f
    
    Problem signature:
    P1: 141
    P2: ffff9607319bb4a0
    P3: fffff8058d57c170
    P4: 0
    P5: 3140
    P6: 10_0_16299
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20180306-2026.dmp
    \\?\C:\WINDOWS\TEMP\WER-154962765-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER93D9.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER93D9.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER93E9.tmp.txt
    \\?\C:\Windows\Temp\WEREE4E.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_50d1239ccd3bfba9d1585468016cffe45932e5b_00000000_cab_0d58ef95
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: d9089b6f-8ad3-4433-be95-e302c8632275
    Report Status: 268435456
    Hashed bucket:
    3/8/2018 9:36 PM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 3fbfa755-2be8-41b9-95f7-a0d163d1c90b
    
    Problem signature:
    P1: 141
    P2: ffffc28c253d24a0
    P3: fffff80c9de9c170
    P4: 0
    P5: 2040
    P6: 10_0_16299
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20180308-1636.dmp
    \\?\C:\WINDOWS\TEMP\WER-65920093-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE3D0.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE3D2.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE3E2.tmp.txt
    \\?\C:\Windows\Temp\WER2BBC.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_7e8f994d201c9e8bc538986cf42c738865a1e4_00000000_cab_0d3a2d8b
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: b8a1abc9-1703-4c47-9b93-aed432868e67
    Report Status: 268435456
    Hashed bucket:
    3/8/2018 1:59 AM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 43db8900-72b3-41e1-8791-482c8faf85f2
    
    Problem signature:
    P1: 141
    P2: ffffcb08b49c04a0
    P3: fffff80b2bf2c170
    P4: 0
    P5: 3a38
    P6: 10_0_16299
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20180307-2059.dmp
    \\?\C:\WINDOWS\TEMP\WER-80412171-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7C0.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7C0.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7D0.tmp.txt
    \\?\C:\Windows\Temp\WER1A3F.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_175e93a7c33eaf9f8246b9695073b77ffb9ca18_00000000_cab_360b1bb5
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: d7657b6c-9598-4e8b-90ee-b5d71ee88a65
    Report Status: 268435456
    Hashed bucket:
    3/8/2018 3:17 AM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 444845d5-1d46-4f8c-a29e-d7497dd27adc
    
    Problem signature:
    P1: 141
    P2: ffff91019befd010
    P3: fffff80d0ee6c170
    P4: 0
    P5: 1ef0
    P6: 10_0_16299
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20180307-2217.dmp
    \\?\C:\WINDOWS\TEMP\WER-4610671-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6155.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6159.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER616A.tmp.txt
    \\?\C:\Windows\Temp\WERC382.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_2b3a1886f63813e64e3f99c6ffb759722f041be_00000000_cab_3232c520
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: f86ecfe2-2383-4938-a258-7f16b72e6a41
    Report Status: 268435456
    Hashed bucket:
    3/12/2018 11:54 PM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 4cf630f6-bbb4-4223-9a5b-0da71142ce3e
    
    Problem signature:
    P1: 141
    P2: ffffd20088bd74a0
    P3: fffff80e67bdc170
    P4: 0
    P5: 24ec
    P6: 10_0_16299
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20180312-1953.dmp
    \\?\C:\WINDOWS\TEMP\WER-93265-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7375.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7377.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7388.tmp.txt
    \\?\C:\Windows\Temp\WERD310.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_c76f9213566593125a603e117d97ffead7_00000000_cab_399dd54c
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 32278d05-170b-4f30-841b-7601dc297cdf
    Report Status: 268435456
    Hashed bucket:
    3/6/2018 2:41 AM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 4fc8002f-d60d-455d-9561-99fe2c7aaa98
    
    Problem signature:
    P1: 141
    P2: ffff960735e6f4a0
    P3: fffff8058d57c170
    P4: 0
    P5: 1734
    P6: 10_0_16299
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20180305-2140.dmp
    \\?\C:\WINDOWS\TEMP\WER-73007906-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA07.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA09.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA2A.tmp.txt
    \\?\C:\Windows\Temp\WER3DFC.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_5868796f82d19b63bd60951e7b921e3e3d45eea_00000000_cab_23f2401b
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: c21ded36-3801-430e-8769-8a7bf6fd29f4
    Report Status: 268435456
    Hashed bucket:
    3/4/2018 11:16 PM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 5be953f5-f633-4fe2-b289-e49bc3c9cfcf
    
    Problem signature:
    P1: 141
    P2: ffffb681c8d30370
    P3: fffff803614bc170
    P4: 0
    P5: 14f0
    P6: 10_0_16299
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20180304-1816.dmp
    \\?\C:\WINDOWS\TEMP\WER-173768484-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER856D.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8571.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8582.tmp.txt
    \\?\C:\Windows\Temp\WERB1B4.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_c9ee96263a02d4b668f81f749da9777748ca95a_00000000_cab_2a7bb269
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: b95889d3-9ac9-4244-b69c-522736bf1d2f
    Report Status: 268435456
    Hashed bucket:
    3/5/2018 1:00 AM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 60417eea-3ee8-4f44-b697-fd3d0be347c8
    
    Problem signature:
    P1: 141
    P2: ffffe400f80934a0
    P3: fffff802304bc170
    P4: 0
    P5: 32d8
    P6: 10_0_16299
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20180304-1959.dmp
    \\?\C:\WINDOWS\TEMP\WER-346015-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4F21.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4F29.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4F3A.tmp.txt
    \\?\C:\Windows\Temp\WERF63C.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_b87741c3c657c93b1f945888e97ea2c6cea2fa_00000000_cab_2175f813
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 03313f09-7498-4cd5-942f-9826bb94aaba
    Report Status: 268435456
    Hashed bucket:
    3/7/2018 1:28 AM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 6347e204-5776-4ef6-be42-9ec55b385182
    
    Problem signature:
    P1: 141
    P2: ffff9607426fc010
    P3: fffff8058d57c170
    P4: 0
    P5: 9c4
    P6: 10_0_16299
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20180306-2027.dmp
    \\?\C:\WINDOWS\TEMP\WER-155029375-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER975E.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9764.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9775.tmp.txt
    \\?\C:\Windows\Temp\WERD536.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_5f61cc377fbffa2ef29825921807225b8add29c_00000000_cab_0b11d67a
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 4b34e7ef-198c-4661-9f83-6a99d9e3d06c
    Report Status: 268435456
    Hashed bucket:
    3/8/2018 9:37 PM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 643029b5-9d3d-45d1-98f7-37ceba639307
    
    Problem signature:
    P1: 141
    P2: ffffc28c241314a0
    P3: fffff80c9de9c170
    P4: 0
    P5: 23a8
    P6: 10_0_16299
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20180308-1637.dmp
    \\?\C:\WINDOWS\TEMP\WER-65966828-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9A10.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9A14.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9A34.tmp.txt
    \\?\C:\Windows\Temp\WERAE46.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_a777a14528107ae9d071691ab8ca6ed06daf1514_00000000_cab_37c6aff9
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: fcad35af-83ea-46fc-b384-29e3ff1e6364
    Report Status: 268435456
    Hashed bucket:
    3/5/2018 12:54 AM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 68cc4411-b7f3-40f5-892b-0438ab724a85
    
    Problem signature:
    P1: 141
    P2: ffffa58a7ec05010
    P3: fffff805bd3ec170
    P4: 0
    P5: 2f7c
    P6: 10_0_16299
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20180304-1953.dmp
    \\?\C:\WINDOWS\TEMP\WER-5739265-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER99A8.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER99AE.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER99BF.tmp.txt
    \\?\C:\Windows\Temp\WERB152.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_a112cfc141ee309d339f4af43dd45b25db794db6_00000000_cab_0b24b333
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 5b34ecd3-e503-49b4-ad31-03856873e784
    Report Status: 268435456
    Hashed bucket:
    3/8/2018 9:37 PM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 6fc52e9a-751c-4a60-9484-b379d3746d09
    
    Problem signature:
    P1: 141
    P2: ffffc28c241314a0
    P3: fffff80c9de9c170
    P4: 0
    P5: 23a8
    P6: 10_0_16299
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20180308-1637.dmp
    \\?\C:\WINDOWS\TEMP\WER-65969843-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA5E7.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA5ED.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA60D.tmp.txt
    \\?\C:\Windows\Temp\WERC3B6.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_a777a14528107ae9d071691ab8ca6ed06daf1514_00000000_cab_37c6c594
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 9fef1d95-f6fa-4e45-b7c9-f47464b8e806
    Report Status: 268435456
    Hashed bucket:
    3/8/2018 3:04 AM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 70b86863-a27d-4b80-acbe-80e8789eadb2
    
    Problem signature:
    P1: 141
    P2: ffff9101b36c8010
    P3: fffff80d0ee6c170
    P4: 0
    P5: 10c8
    P6: 10_0_16299
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20180307-2204.dmp
    \\?\C:\WINDOWS\TEMP\WER-3850921-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCA0C.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCA0E.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCA1F.tmp.txt
    \\?\C:\Windows\Temp\WER17D2.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_b8f65191f266afe327285b2e2f4497ee29715629_00000000_cab_255319f1
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 57dd29b2-b91a-458f-8e10-694292d3f5e6
    Report Status: 268435456
    Hashed bucket:
    3/2/2018 10:42 PM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 70cc1176-2bc9-466b-b0bd-7e8d920099d9
    
    Problem signature:
    P1: 141
    P2: ffffac0c5bc7a4a0
    P3: fffff800641dc170
    P4: 0
    P5: de8
    P6: 10_0_16299
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20180302-1742.dmp
    \\?\C:\WINDOWS\TEMP\WER-14044578-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5756.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5766.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5776.tmp.txt
    \\?\C:\Windows\Temp\WER6C85.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_c434fb7ec2c7cd996194bd22e7ec24159e4ad0_00000000_cab_39926e59
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: c53583e8-250a-42cb-94a6-85af213ecced
    Report Status: 268435456
    Hashed bucket:
    3/3/2018 12:16 AM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 73d01e46-848f-4111-9e85-5ae4a5c8d88d
    
    Problem signature:
    P1: 141
    P2: ffffb681ca2962f0
    P3: fffff803614bc170
    P4: 0
    P5: 24a8
    P6: 10_0_16299
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20180302-1916.dmp
    \\?\C:\WINDOWS\TEMP\WER-4578000-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE39A.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE39A.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE3AA.tmp.txt
    \\?\C:\Windows\Temp\WERF629.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_ede4d1e93f20b82fc1af662e6749490e019175a_00000000_cab_3405f770
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 096cd195-1f31-48c3-b4c1-62187a718c5e
    Report Status: 268435456
    Hashed bucket:
    3/8/2018 1:59 AM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 7773217a-cd48-4293-acbb-38dfe2adc788
    
    Problem signature:
    P1: 141
    P2: ffffcb08b49c04a0
    P3: fffff80b2bf2c170
    P4: 0
    P5: 3a38
    P6: 10_0_16299
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20180307-2059.dmp
    \\?\C:\WINDOWS\TEMP\WER-80414968-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER101C.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER102E.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER103F.tmp.txt
    \\?\C:\Windows\Temp\WER2E18.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_175e93a7c33eaf9f8246b9695073b77ffb9ca18_00000000_cab_360b2f7c
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 42da95c8-ccf1-470a-b781-0931d660355d
    Report Status: 268435456
    Hashed bucket:
    3/17/2018 11:59 PM    Windows Error Reporting    Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 79712dc8-40fa-45c6-8687-dd6cf7959648
    
    Problem signature:
    P1: 141
    P2: ffffb90caa96c4a0
    P3: fffff80f1e0ec170
    P4: 0
    P5: 29bc
    P6: 10_0_16299
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20180317-1958.dmp
    \\?\C:\WINDOWS\TEMP\WER-1519984-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3A98.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3AA7.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3AB8.tmp.txt
    \\?\C:\Windows\Temp\WER6860.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_6ed36ef32df5764dc3381f08fc864959533d74f_00000000_cab_21cb6a62
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 7149d417-29ef-4bc5-8ecb-b63c11189732
    Report Status: 268435456
    Hashed bucket:
    Last edited by zbook; 19 Mar 2018 at 02:22.
      My ComputerSystem Spec

  3. ThrashZone's Avatar
    Posts : 3,882
    3-Win-7Prox64 2-Win10Prox64
       19 Mar 2018 #13

    Hi,
    If oc'ing the cpu I'd at least use xmp profile 1 which for your memory might be 2666
    XMP profile 2 would be 3000.
      My ComputersSystem Spec

  4. AddRAM's Avatar
    Posts : 2,112
    Windows 7 Pro x64 Windows 10 Pro x64
       19 Mar 2018 #14

    Always start at square 1 when troubleshooting, set the Bios to defaults. Do some of the same gaming and report your results.

    And Precision X is NOT compatible with all nvidia cards, use MSI Afterburner, and uninstall the Asus GPU tweak program, or if you like the Asus program then leave it installed, but make sure the card is at default settings.

    And turn off Discord. I see no reason to talk to anyone while playing Rainbow Six Siege

    I have EVGA 980 Ti`s on my Z170 and they chew up Rainbow Six Siege on max settings, so your 1080 should have no problems at all.
    Last edited by AddRAM; 19 Mar 2018 at 12:30.
      My ComputersSystem Spec

  5.    31 Mar 2018 #15

    So I switched my bios back to its defaults by selecting a different profile, i think thats how its done. No clue how to switch XMP profiles. What ram values should be changed with what timings? I turned off all overclocking, and I flashed the latest update for my bios onto my mobo. Im still working on some of the stuff from @zbook but im not sure if I want to reset my bios just yet, i know working with macrium reflect is anoying so im going to hold off on that for now. I got up to 42.3 GB free on my C drive with windows.

    Heres info from the command prompt:
    Microsoft Windows [Version 10.0.16299.309](c) 2017 Microsoft Corporation. All rights reserved.C:\WINDOWS\system32>C:\WINDOWS\system32>sfc/scannowBeginning system scan. This process will take some time.Beginning verification phase of system scan.Verification 100% complete.Windows Resource Protection found corrupt files and successfully repairedthem. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. Forexample C:\Windows\Logs\CBS\CBS.log. Note that logging is currently notsupported in offline servicing scenarios.C:\WINDOWS\system32> dism /online /cleanup-image /restorehealth dism /online /cleanup-image /restorehealthError: 87DISM doesn't recognize the command-line option "dism".For more information, refer to the help by running DISM.exe /?.The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.logC:\WINDOWS\system32> dism /online /cleanup-image /restorehealthDeployment Image Servicing and Management toolVersion: 10.0.16299.15Image Version: 10.0.16299.309[==========================100.0%==========================] The restore operation completed successfully.The operation completed successfully.C:\WINDOWS\system32>chkdsk /scanThe type of the file system is NTFS.Stage 1: Examining basic file system structure ... 329728 file records processed.File verification completed. 13565 large file records processed. 0 bad file records processed.Stage 2: Examining file name linkage ... 14542 reparse records processed. 413064 index entries processed.Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found. 14542 reparse records processed.Stage 3: Examining security descriptors ...Security descriptor verification completed. 41669 data files processed.CHKDSK is verifying Usn Journal... 34996368 USN bytes processed.Usn Journal verification completed.Windows has scanned the file system and found no problems.No further action is required. 124025032 KB total disk space. 81129176 KB in 195415 files. 130152 KB in 41670 indexes. 0 KB in bad sectors. 439980 KB in use by the system. 65536 KB occupied by the log file. 42325724 KB available on disk. 4096 bytes in each allocation unit. 31006258 total allocation units on disk. 10581431 allocation units available on disk.C:\WINDOWS\system32>
      My ComputerSystem Spec

  6. AddRAM's Avatar
    Posts : 2,112
    Windows 7 Pro x64 Windows 10 Pro x64
       31 Mar 2018 #16

    XMP is an option in the Bios, if you choose to enable it, it will show the XMP profile or profiles on your particular memory, if it has any. Just click on a profile to enable it. You don`t have to make any other changes, it does everything for you.

    What memory did you buy for it ?

    Post a link.
    Last edited by AddRAM; 31 Mar 2018 at 22:49.
      My ComputersSystem Spec

  7.   My ComputerSystem Spec

  8. AddRAM's Avatar
    Posts : 2,112
    Windows 7 Pro x64 Windows 10 Pro x64
       31 Mar 2018 #18

    ThrashZone said: View Post
    Hi,
    If oc'ing the cpu I'd at least use xmp profile 1 which for your memory might be 2666
    XMP profile 2 would be 3000.

    That is exactly what I do. I set my CPU to 4.6 and I enable my 2800 MHz XMP profile, and that`s it, and I never have any issues.
      My ComputersSystem Spec


  9. Posts : 20,986
    windows 10 professional version 1607 build 14393.969 64 bit
       31 Mar 2018 #19

    When available please post images for steps 17 and 18 and update the progress for each step.
      My ComputerSystem Spec


 
Page 2 of 2 FirstFirst 12

Related Threads
Graphics card in Graphic Cards
Hi guys i am having HP p6140in desktop having boston 1.0 msi motherboard :rolleyes::rolleyes: i want to upgrade graphics to 2GB which is now 256MB:cry::cry:, my query is which 2GB graphics card will my motherboard support... i am attaching my...
Can anyone tell me what graphics card for under 600 is the best? It's for my gaming PC. And will games run faster when using a DEDICATED Graphics card VS Motherboard-graphics card? In a month time I want to buy a Graphics card and well.... I'm...
I'm replacing my NVidia GTX750Ti card (it has a problem) with an NVidia GTX1050Ti. This is a Win10 x64 system. I downloaded the latest drivers for the card. It used to be said that one should uninstall the old driver first then install card, boot...
Graphics card now or later? in Graphic Cards
So got paid not too long ago and was wondering If I should get a GTX 1070 now or wait till the end of next month to buy a 1080? Still don't have a case and haven't had one since my last one smoked up with the wires melting (had that returned with my...
Hey, recently, I have came up with an idea of a fourth monitor, but my GPU (970) supports only three, which ones that I own. It has fourth one but I don't have the right cables for it for now. I noticed that my motherboard has two open video...

Tags for this Thread

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 18:03.
Find Us