Black Screen, GPU Fan 100% When Playing Games  

Page 2 of 3 FirstFirst 123 LastLast

  1. Posts : 11
    Windows 10
    Thread Starter
       #11

    Yeah they sent back the same model of card after the RMA was processed.
      My Computer


  2. Posts : 14,018
    Windows 11 Pro X64 22H2 22621.1848
       #12

    Could be the card but not likely. Are you doing any OCing now or is everything set at nominal (default) values?

    What PSU do you have, what are it's specs? I know you've swapped cables on it but have you tried a different PSU?
      My Computers


  3. Posts : 11
    Windows 10
    Thread Starter
       #13

    Nope, everything is set to normal right now. I have never done any GPU overclocking, but my RAM was overclocked to 3200 Mhz via XMP for a while. I turned that off during troubleshooting and have never set it back.

    As for the PSU, I have a EVGA SuperNOVA 650 G1, 80+ GOLD 650W, Fully Modular. I do have a multimeter from my father, but I am pretty novice in what I would be measuring and how I would go about it. I do remember the 8 pin EPS cable being super short, so it needed to be stretched and twisted to get in place when I built ~2 years ago. I never see any flashing lights or any RGB go out and quickly come back on at the time of the crash, but it may be worth looking into.

    I have already made swaps to my RAM, CPU, and GPU at this point. My next steps of replacing pieces would be CPU, PSU, then MOBO, since that seems to be from quickest swap to hardest.
      My Computer


  4. Posts : 14,018
    Windows 11 Pro X64 22H2 22621.1848
       #14

    Do you have a spare hard drive? You could do a clean install to it then do all windows updates, install the game and test. That leaves everything asis on your current hard drive while checking the Windows 10 installation on the other hard drive. I'd do this prior to any more hardware swaps.

    You currently have three drives:

    SanDisk SSD PLUS 1000GB
    SanDisk Ultra II 500GB (Boot drive)
    WDC WD10EZEX-08WN4A0 (931.51)

    Disconnect all 3 drives, connect the spare then clean install as I mentioned above. That way your current setup is totally isolated and safe.

    Edit: I looked a the dump again and it definitely points to Nvidia.
      My Computers


  5. Posts : 11
    Windows 10
    Thread Starter
       #15

    I did the “Clean” option a few weeks back under Recovery options and kept my files. Should I go through that again and clear out all the files, or would my previous action be enough?

    Based on your edit, should I still go through with any Windows changes or is it for sure driver related at this point? Any useful snippets to show NVIDIA support?
      My Computer


  6. Posts : 14,018
    Windows 11 Pro X64 22H2 22621.1848
       #16

    If you kept your files you did not do a clean install, you did a OS reset keeping your files (and maybe apps). A clean install means deleting all partitions on the drive you install to so the install actually goes to a unallocated, unformatted drive that has no partitions on it. The installer itself creates the partitions it needs during the installation process.

    Send Nvidia support the mini dump. That's really all we have to go on.

    The point of clean installing to a different hard drive is to see if it makes a difference. If you can do it as I suggested that provides total isolation from the current install as well as total protection for the current install.
      My Computers


  7. Posts : 11
    Windows 10
    Thread Starter
       #17

    I was able to do a complete clean installation of Windows on its on HDD I had laying around. I went as far as formatting it before I started the process. Once finished, I only installed Steam and Rocket League on the drive. Unfortunately, as I launched Rocket League and navigated some opening windows, the same crashing behavior showed.

    With this in mind, should we go back to thinking hardware? I am thinking of swapping the PSU, as I noticed on the 5 white LEDs on the front of the GPU, the leftmost goes dim and lights back up occasionally. While it may be unrelated, my latest theory would be that the PSU fails to supply enough power at random times while gaming. Could be totally off base, but it will be the next thing I try this weekend.

    Any other suggestions or thoughts would be appreciated!
      My Computer


  8. Posts : 40,988
    windows 10 professional version 1607 build 14393.969 64 bit
       #18

    1) Upload a new V2 into this thread

    2) Upgrade the BIOS: F42d > F50a
    GA-AX370-Gaming K5 (rev. 1.x) | Motherboard - GIGABYTE U.S.A.

    3) The logs displayed Video Timeout Detection and Recovery (TDR)
    This indicates that the display driver failed to respond in a timely fashion.

    4) These are some troubleshooting steps:
    a) Try later and/or earlier drivers
    b) Measure the GPU's temperatures at idle and under load
    c) Ensure the GPU is free from dust build up and that the fan is working correctly
    d) Re-seat the GPU and check all connections are securely made
    e) Check PSU voltages in BIOS
    f) Try a different card in the system


    5) Post images of:
    BIOS 3.3, 5 and 12 voltage values
    CPU voltage and frequency


    6) 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!
    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
      My Computer


  9. Posts : 11
    Windows 10
    Thread Starter
       #19

    Hey - I will work on the BIOS update here in the next few minutes, but I have not found moving to 42a to be helpful in the past. Here are the other answers to your questions:

    a) Try later and/or earlier drivers
    • I have tried the stock driver with the 1080 after a display driver resintall, the earliest patch available on NVIDIAs site, as well as the latest. None of those 3 have remedied the problem.


    b) Measure the GPU's temperatures at idle and under load
    • Temps never exceed 70C. Most of the time, RL crashes out before temps can even build. 70C can be seen in COD and other games as well.


    c) Ensure the GPU is free from dust build up and that the fan is working correctly
    • Both fans are spinning problem and the stock fan curve is active, as I can hear it ramp during COD. No dust buildup.


    d) Re-seat the GPU and check all connections are securely made
    • I have reseated the card in the top PCI-E slot multiple times, as well as moved it to the lower port as well. No improvement.


    e) Check PSU voltages in BIOS
    Here are the voltages that were available in my BIOS:
    • CPU VCORE: 1.428-1.512V
    • CPU VDDP: .9V-.912V
    • DRAM Channel: 1.212-1.214V
    • +3.3V: 3.264V
    • +5V: 5.010V
    • +12V: 12.168V
    • VCORE SOC: .888V

    Not sure if any of these are out of range or abnormal.
    f) Try a different card in the system
    • I have had the original Classified for ~2 years that I RMA'd, so there have been two different GPUs producing this issue. Both have been CLASSIFIED 1080s.
      My Computer


  10. Posts : 40,988
    windows 10 professional version 1607 build 14393.969 64 bit
       #20

    See if you can find a friend, neighbor, relative, or local computer store to swap the GPU card.

    Either Nvidia or AMD can be used.

    Make two tests:

    1) Test the card from the problematic computer in another computer
    2) Test a new card in the problematic computer


    Code:
    12/22/2019 6:54 PM	Windows Error Reporting	Fault bucket LKD_0x117_Tdr:3_TdrBug:575504_TdrVTR:0_IMAGE_nvlddmkm.sys_Pascal, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 1b69df33-e9c3-4c33-91c4-5f7448613905
    
    Problem signature:
    P1: 117
    P2: ffffaf8903cd22c0
    P3: fffff806536ea998
    P4: 0
    P5: 49c
    P6: 10_0_18362
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20191222-1354.dmp
    \\?\C:\WINDOWS\TEMP\WER-9565750-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER568.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER579.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER578.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5A8.tmp.txt
    \\?\C:\Windows\Temp\WER3C96.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_117_826de462efb75571b4f818f036f83f2be32c059_00000000_cab_18c50cec-de5d-4c16-88f8-c8533731939f
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 18c50cec-de5d-4c16-88f8-c8533731939f
    Report Status: 2147483648
    Hashed bucket: 
    Cab Guid: 0
    1/4/2020 5:03 PM	Windows Error Reporting	Fault bucket LKD_0x117_Tdr:3_TdrBug:575504_TdrVTR:0_IMAGE_nvlddmkm.sys_Pascal, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 3615c6ae-0289-4547-ad0f-21ba76f2d5ae
    
    Problem signature:
    P1: 117
    P2: ffff878b51640450
    P3: fffff8064bf2a998
    P4: 0
    P5: 2a4c
    P6: 10_0_18362
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20200104-1203.dmp
    \\?\C:\WINDOWS\TEMP\WER-134949859-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3CCB.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3CDC.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3CDB.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3D0B.tmp.txt
    \\?\C:\Windows\Temp\WER765A.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_117_7e3b875ec6410d6566899b6c646a0ccff4c625c_00000000_cab_7caf1b4d-1755-4278-9223-29b973a7049f
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 7caf1b4d-1755-4278-9223-29b973a7049f
    Report Status: 2147483648
    Hashed bucket: 
    Cab Guid: 0
    1/5/2020 10:34 PM	Windows Error Reporting	Fault bucket LKD_0x117_Tdr:3_TdrBug:575504_TdrVTR:0_IMAGE_nvlddmkm.sys_Pascal, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 78c3801d-841d-4783-a1cc-e6098dd04f9c
    
    Problem signature:
    P1: 117
    P2: ffffc80aea3bf010
    P3: fffff8027faaa998
    P4: 0
    P5: 4a8
    P6: 10_0_18362
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20200105-1733.dmp
    \\?\C:\WINDOWS\TEMP\WER-1990937-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER72DC.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER72ED.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER72EC.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER731B.tmp.txt
    \\?\C:\Windows\Temp\WERAB23.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_117_edd620e3ff1dadb1a86fe9545ad6edf979254c1c_00000000_cab_10e62178-6725-421f-a256-3ece01c3a211
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 10e62178-6725-421f-a256-3ece01c3a211
    Report Status: 2147483648
    Hashed bucket: 
    Cab Guid: 0
    12/23/2019 12:22 AM	Windows Error Reporting	Fault bucket LKD_0x117_Tdr:3_TdrBug:575504_TdrVTR:0_IMAGE_nvlddmkm.sys_Pascal, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 8b02e1cd-0d34-4546-9358-10f88d20da1b
    
    Problem signature:
    P1: 117
    P2: ffffd68ab604f1f0
    P3: fffff8031228a998
    P4: 0
    P5: 24f4
    P6: 10_0_18362
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20191222-1922.dmp
    \\?\C:\WINDOWS\TEMP\WER-687015-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8C41.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8C52.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8C51.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8C81.tmp.txt
    \\?\C:\Windows\Temp\WERDAFE.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_117_bb5e98d02b9f514bfd8dd2688aed927de3fdc53b_00000000_cab_06c749d0-3586-4ca1-9865-476cc7fc95cd
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 06c749d0-3586-4ca1-9865-476cc7fc95cd
    Report Status: 2147483648
    Hashed bucket: 
    Cab Guid: 0
    12/26/2019 5:00 PM	Windows Error Reporting	Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Pascal, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: c5bfb517-e7bf-4513-8cae-e60108d1f6d8
    
    Problem signature:
    P1: 141
    P2: ffff840a34b6b1f0
    P3: fffff8055e52a998
    P4: 0
    P5: 2e00
    P6: 10_0_18362
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20191226-1200.dmp
    \\?\C:\WINDOWS\TEMP\WER-221362859-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCB16.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCB27.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCB26.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCB56.tmp.txt
    \\?\C:\Windows\Temp\WERF350.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_3ca92e4d45c7dc59b4c6957dcfaf1f9d6d7f597f_00000000_cab_b5d0b6d8-e322-4535-8ede-9886a64f0796
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: b5d0b6d8-e322-4535-8ede-9886a64f0796
    Report Status: 2147483648
    Hashed bucket: 
    Cab Guid: 0
    1/5/2020 4:02 AM	Windows Error Reporting	Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Pascal, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: ff8cbd10-f0d7-4e98-82ed-ea58d4daa165
    
    Problem signature:
    P1: 141
    P2: ffffd30864375050
    P3: fffff8072ebea998
    P4: 0
    P5: 36cc
    P6: 10_0_18362
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20200104-2302.dmp
    \\?\C:\WINDOWS\TEMP\WER-39404859-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5A1B.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5A2B.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5A2C.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5A5C.tmp.txt
    \\?\C:\Windows\Temp\WER82B2.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_a57ea0dd574ba772ef52fd85d6b5f69cfd1b4c_00000000_cab_c74defc4-5ec2-4af0-a05b-7a9ef13d2822
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: c74defc4-5ec2-4af0-a05b-7a9ef13d2822
    Report Status: 2147483648
    Hashed bucket: 
    Cab Guid: 0
    Code:
    1/5/2020 10:01 PM	Windows Error Reporting	Fault bucket 0x133_ISR_nvlddmkm!osDpcForIsr, type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 26db9fa7-1721-451a-add5-ff79e90e9700
    
    Problem signature:
    P1: 133
    P2: 1
    P3: 1e00
    P4: fffff80547573358
    P5: 0
    P6: 10_0_18362
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\010520-8156-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-11937-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER413F.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER414F.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER416E.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER418E.tmp.txt
    
    These files may be available here:
    \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_133_521de4c71e0bb94cf5a698a65bac420235f4b1e_00000000_cab_7985d320-1335-4aba-8f55-fe2a56b4f3d5
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: da24863c-c993-41dd-8a28-f1e11e7edcc7
    Report Status: 268435456
    Hashed bucket: 
    Cab Guid: 0
    12/23/2019 2:20 AM	Windows Error Reporting	Fault bucket 0x133_ISR_nvlddmkm!osDpcForIsr, type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: d1312183-9575-4e26-aa61-2bf2502014cb
    
    Problem signature:
    P1: 133
    P2: 1
    P3: 1e00
    P4: fffff8064e373358
    P5: 0
    P6: 10_0_18362
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\122219-7625-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-11031-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3A0B.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3A1C.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3A3A.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3A4A.tmp.txt
    
    These files may be available here:
    \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_133_57faf97ff45714076e37581b639b3e4f0f7236_00000000_cab_aa3c10e3-e387-47fe-ad24-8f303c052ccb
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 20160587-0410-4645-a944-ec182fe79961
    Report Status: 268435456
    Hashed bucket: 
    Cab Guid: 0
    12/22/2019 7:56 PM	Windows Error Reporting	Fault bucket 0x74_2_c000014c_nt!CmpLoadHiveThread, type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 37e34d61-5644-4aea-84f5-a9bd9a1f068c
    
    Problem signature:
    P1: 74
    P2: 2
    P3: fffff98dc4884a70
    P4: 2
    P5: ffffffffc000014c
    P6: 10_0_18362
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\122219-7250-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-10531-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER394F.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3960.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER396F.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER397F.tmp.txt
    
    These files may be available here:
    \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_74_8c43ef1363a2515e20548d7050ecbd37962afc5c_00000000_cab_a13be311-bc42-4fb4-869d-c5fd21cd4704
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: e6753002-fb26-4b5c-baa1-de7b8b7b7cec
    Report Status: 268435456
    Hashed bucket: 
    Cab Guid: 0
    Code:
    1/5/2020 10:01 PM	Windows Error Reporting	Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: 133
    P2: 1
    P3: 1e00
    P4: fffff80547573358
    P5: 0
    P6: 10_0_18362
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\010520-8156-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-11937-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER413F.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER414F.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER416E.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER418E.tmp.txt
    
    These files may be available here:
    \\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_133_521de4c71e0bb94cf5a698a65bac420235f4b1e_00000000_cab_7985d320-1335-4aba-8f55-fe2a56b4f3d5
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: da24863c-c993-41dd-8a28-f1e11e7edcc7
    Report Status: 4
    Hashed bucket: 
    Cab Guid: 0
    12/23/2019 2:19 AM	Windows Error Reporting	Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: 133
    P2: 1
    P3: 1e00
    P4: fffff8064e373358
    P5: 0
    P6: 10_0_18362
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\122219-7625-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-11031-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3A0B.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3A1C.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3A3A.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3A4A.tmp.txt
    
    These files may be available here:
    \\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_133_57faf97ff45714076e37581b639b3e4f0f7236_00000000_cab_aa3c10e3-e387-47fe-ad24-8f303c052ccb
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 20160587-0410-4645-a944-ec182fe79961
    Report Status: 4
    Hashed bucket: 
    Cab Guid: 0
    12/22/2019 7:56 PM	Windows Error Reporting	Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: 74
    P2: 2
    P3: fffff98dc4884a70
    P4: 2
    P5: ffffffffc000014c
    P6: 10_0_18362
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\122219-7250-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-10531-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER394F.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3960.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER396F.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER397F.tmp.txt
    
    These files may be available here:
    \\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_74_8c43ef1363a2515e20548d7050ecbd37962afc5c_00000000_cab_a13be311-bc42-4fb4-869d-c5fd21cd4704
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: e6753002-fb26-4b5c-baa1-de7b8b7b7cec
    Report Status: 4
    Hashed bucket: 
    Cab Guid: 0
    Code:
    1/4/2020 5:03 PM	Windows Error Reporting	Fault bucket , type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: 117
    P2: ffff878b51640450
    P3: fffff8064bf2a998
    P4: 0
    P5: 2a4c
    P6: 10_0_18362
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20200104-1203.dmp
    \\?\C:\WINDOWS\TEMP\WER-134949859-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3CCB.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3CDC.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3CDB.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3D0B.tmp.txt
    
    These files may be available here:
    \\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_117_7e3b875ec6410d6566899b6c646a0ccff4c625c_00000000_cab_7caf1b4d-1755-4278-9223-29b973a7049f
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 7caf1b4d-1755-4278-9223-29b973a7049f
    Report Status: 4
    Hashed bucket: 
    Cab Guid: 0
    12/22/2019 6:54 PM	Windows Error Reporting	Fault bucket , type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: 117
    P2: ffffaf8903cd22c0
    P3: fffff806536ea998
    P4: 0
    P5: 49c
    P6: 10_0_18362
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20191222-1354.dmp
    \\?\C:\WINDOWS\TEMP\WER-9565750-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER568.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER579.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER578.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5A8.tmp.txt
    
    These files may be available here:
    \\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_117_826de462efb75571b4f818f036f83f2be32c059_00000000_cab_18c50cec-de5d-4c16-88f8-c8533731939f
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 18c50cec-de5d-4c16-88f8-c8533731939f
    Report Status: 4
    Hashed bucket: 
    Cab Guid: 0
    1/5/2020 10:34 PM	Windows Error Reporting	Fault bucket , type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: 117
    P2: ffffc80aea3bf010
    P3: fffff8027faaa998
    P4: 0
    P5: 4a8
    P6: 10_0_18362
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20200105-1733.dmp
    \\?\C:\WINDOWS\TEMP\WER-1990937-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER72DC.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER72ED.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER72EC.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER731B.tmp.txt
    
    These files may be available here:
    \\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_117_edd620e3ff1dadb1a86fe9545ad6edf979254c1c_00000000_cab_10e62178-6725-421f-a256-3ece01c3a211
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 10e62178-6725-421f-a256-3ece01c3a211
    Report Status: 4
    Hashed bucket: 
    Cab Guid: 0
    12/23/2019 12:22 AM	Windows Error Reporting	Fault bucket , type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: 117
    P2: ffffd68ab604f1f0
    P3: fffff8031228a998
    P4: 0
    P5: 24f4
    P6: 10_0_18362
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20191222-1922.dmp
    \\?\C:\WINDOWS\TEMP\WER-687015-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8C41.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8C52.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8C51.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8C81.tmp.txt
    
    These files may be available here:
    \\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_117_bb5e98d02b9f514bfd8dd2688aed927de3fdc53b_00000000_cab_06c749d0-3586-4ca1-9865-476cc7fc95cd
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 06c749d0-3586-4ca1-9865-476cc7fc95cd
    Report Status: 4
    Hashed bucket: 
    Cab Guid: 0
    12/26/2019 5:00 PM	Windows Error Reporting	Fault bucket , type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: 141
    P2: ffff840a34b6b1f0
    P3: fffff8055e52a998
    P4: 0
    P5: 2e00
    P6: 10_0_18362
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20191226-1200.dmp
    \\?\C:\WINDOWS\TEMP\WER-221362859-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCB16.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCB27.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCB26.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCB56.tmp.txt
    
    These files may be available here:
    \\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_141_3ca92e4d45c7dc59b4c6957dcfaf1f9d6d7f597f_00000000_cab_b5d0b6d8-e322-4535-8ede-9886a64f0796
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: b5d0b6d8-e322-4535-8ede-9886a64f0796
    Report Status: 4
    Hashed bucket: 
    Cab Guid: 0
    1/5/2020 4:02 AM	Windows Error Reporting	Fault bucket , type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: 141
    P2: ffffd30864375050
    P3: fffff8072ebea998
    P4: 0
    P5: 36cc
    P6: 10_0_18362
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20200104-2302.dmp
    \\?\C:\WINDOWS\TEMP\WER-39404859-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5A1B.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5A2B.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5A2C.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5A5C.tmp.txt
    
    These files may be available here:
    \\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_141_a57ea0dd574ba772ef52fd85d6b5f69cfd1b4c_00000000_cab_c74defc4-5ec2-4af0-a05b-7a9ef13d2822
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: c74defc4-5ec2-4af0-a05b-7a9ef13d2822
    Report Status: 4
    Hashed bucket: 
    Cab Guid: 0
      My Computer


 

  Related Discussions
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 13:51.
Find Us




Windows 10 Forums