NZXT-1 BSOD Windows 10


  1. wreckingball
    Posts : 4
    Windows 10
       New #1

    NZXT-1 BSOD Windows 10


    Dear all,

    I'm having no luck figuring out what is happening here. I hope that someone here can help.

    Thank you in advance.

    - - - Updated - - -

    I saw a bat file which provides additional information. Those results are below.


    ###########################################################
    # The following commands will be run in sequence. #
    # The first 5 will take quite a while to run, be patient. #
    ###########################################################

    sfc /scannow
    dism /online /cleanup-image /scanhealth
    dism /online /cleanup-image /restorehealth
    sfc /scannow

    chkdsk /scan

    wmic recoveros get autoreboot
    wmic recoveros set autoreboot = false
    wmic recoveros get autoreboot
    wmic recoveros get DebugInfoType
    wmic recoveros set DebugInfoType = 7
    wmic recoveros get DebugInfoType

    wmic pagefile list /format:list
    wmic Computersystem where name="NZXT-1" get AutomaticManagedPagefile
    wmic Computersystem where name="NZXT-1" set AutomaticManagedPagefile=True
    wmic Computersystem where name="NZXT-1" get AutomaticManagedPagefile

    bcdedit /enum {badmemory}


    C:\WINDOWS\system32>sfc /scannow

    Beginning system scan. This process will take some time.

    Beginning verification phase of system scan.
    Verification 0% complete.

    Windows Resource Protection did not find any integrity violations.

    C:\WINDOWS\system32>dism /online /cleanup-image /scanhealth

    Deployment Image Servicing and Management tool
    Version: 10.0.19041.572

    Image Version: 10.0.19042.662

    [==========================100.0%==========================] No component store corruption detected.
    The operation completed successfully.

    C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth

    Deployment Image Servicing and Management tool
    Version: 10.0.19041.572

    Image Version: 10.0.19042.662

    [==========================100.0%==========================] The restore operation completed successfully.
    The operation completed successfully.

    C:\WINDOWS\system32>sfc /scannow

    Beginning system scan. This process will take some time.

    Beginning verification phase of system scan.
    Verification 0% complete.

    Windows Resource Protection did not find any integrity violations.

    C:\WINDOWS\system32>chkdsk /scan
    The type of the file system is NTFS.

    Stage 1: Examining basic file system structure ...
    978432 file records processed.
    File verification completed.
    Phase duration (File record verification): 5.50 seconds.
    5273 large file records processed.
    Phase duration (Orphan file record recovery): 0.00 milliseconds.
    0 bad file records processed.
    Phase duration (Bad file record checking): 1.06 milliseconds.

    Stage 2: Examining file name linkage ...
    2019 reparse records processed.
    1213320 index entries processed.
    Index verification completed.
    Phase duration (Index verification): 13.66 seconds.
    0 unindexed files scanned.
    Phase duration (Orphan reconnection): 3.38 seconds.
    0 unindexed files recovered to lost and found.
    Phase duration (Orphan recovery to lost and found): 1.43 milliseconds.
    2019 reparse records processed.
    Phase duration (Reparse point and Object ID verification): 9.12 milliseconds.

    Stage 3: Examining security descriptors ...
    Security descriptor verification completed.
    Phase duration (Security descriptor verification): 52.24 milliseconds.
    117445 data files processed.
    Phase duration (Data attribute verification): 0.54 milliseconds.
    CHKDSK is verifying Usn Journal...
    42002240 USN bytes processed.
    Usn Journal verification completed.
    Phase duration (USN journal verification): 112.53 milliseconds.
    Windows has found problems that must be fixed offline.
    Please run "chkdsk /f" to fix the issues.

    999103700 KB total disk space.
    571777860 KB in 652536 files.
    458656 KB in 117446 indexes.
    0 KB in bad sectors.
    1122476 KB in use by the system.
    65536 KB occupied by the log file.
    425744708 KB available on disk.

    4096 bytes in each allocation unit.
    249775925 total allocation units on disk.
    106436177 allocation units available on disk.
    Total duration: 22.74 seconds (22744 ms).

    C:\WINDOWS\system32>wmic recoveros get autoreboot
    AutoReboot
    TRUE


    C:\WINDOWS\system32>wmic recoveros set autoreboot = false
    Updating property(s) of '\\NZXT-1\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\WINDOWS|\\Device\\Harddisk1\\Partition2"'
    Property(s) update successful.

    C:\WINDOWS\system32>wmic recoveros get autoreboot
    AutoReboot
    FALSE


    C:\WINDOWS\system32>wmic recoveros get DebugInfoType
    DebugInfoType
    7


    C:\WINDOWS\system32>wmic recoveros set DebugInfoType = 7
    Updating property(s) of '\\NZXT-1\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\WINDOWS|\\Device\\Harddisk1\\Partition2"'
    Property(s) update successful.

    C:\WINDOWS\system32>wmic recoveros get DebugInfoType
    DebugInfoType
    7


    C:\WINDOWS\system32>wmic pagefile list /format:list


    AllocatedBaseSize=4864
    CurrentUsage=0
    Description=C:\pagefile.sys
    InstallDate=20181104075251.000694-420
    Name=C:\pagefile.sys
    PeakUsage=1
    Status=
    TempPageFile=FALSE




    C:\WINDOWS\system32>wmic Computersystem where name="NZXT-1" get AutomaticManagedPagefile
    AutomaticManagedPagefile
    TRUE


    C:\WINDOWS\system32>wmic Computersystem where name="NZXT-1" set AutomaticManagedPagefile=True
    Updating property(s) of '\\NZXT-1\ROOT\CIMV2:Win32_ComputerSystem.Name="NZXT-1"'
    Property(s) update successful.

    C:\WINDOWS\system32>wmic Computersystem where name="NZXT-1" get AutomaticManagedPagefile
    AutomaticManagedPagefile
    TRUE


    C:\WINDOWS\system32>bcdedit /enum {badmemory}

    RAM Defects
    -----------
    identifier {badmemory}
    badmemorylist 0x20f5ae
    0x20f5be
    0x24f5e9
    0x25ede9
    0x25edf9
    0x29d9ec
    0x29d9fc
    0x30fde7
    0x30fdf7
    0x31d5e8
    0x31d5f8
    0x3361e4
    0x3361f4
    0x33f68c
    0x3ae9ee
    0x3ae9fe
    0x3af1a9
    0x3af5ae
    0x3af5be
    0x3af9ac
    0x3b0284
    0x3b0294
    0x3b19f9
    0x3df1a4
    0x3efdec
    0x3efdfc
    0x62fda4
    0x62fdb4
    0x6a05ab
    0x70d5be
    0x70e1bb
    0x75dda0
    0x7bf9a4
    0x7bf9b4
    0x7df1a8
    0x7df1b8

    - - - Updated - - -

    The system has 4 8 GB sticks of RAM. One pair is at 2333 Mhz, and the other is at 1833 Mhz. I've tried running the bcdedit /enum {badmemory} test against each pair, and in each pair of DIMMS. I get the same badmemorylist with each test.

    It's possible, but it seems unlikely that all four sticks are bad. Does this indicate that the motherboard is failing?
      My Computer
    Quote Quote

  3. Ztruker
    Posts : 14,050
    Windows 11 Pro X64 22H2 22621.1848
       New #2

    ===================================================
    Up through DDR3, follow this tutorial: MemTest86+ - Test RAM - Windows 10 Forums
    DDR4, follow this tutorial: MemTest86 v8.1 Free Memory Testing Tool Review

    Both of these are diagnostic tools designed to test Random Access Memory (RAM) for faults. They will verify that:
    • RAM will accept and keep random patterns of data sent to it
    • There are no errors when different parts of memory try to interact
    • There are no conflicts between memory addresses

    They run from bootable media to isolate the RAM from the system, no other components are taken into account during the test.

    warning   Warning
    MemTest86+ and Memtest86 need to run for at least 8 passes to be anywhere near conclusive, anything less will not give a complete analysis of the RAM. The new version of Memtest86 only allows 4 passes for the free version so run it twice, back to back.

    If you are asked to run MemTest86+ or Memtest86 by a Ten Forums member make sure you run the full 8 (or 4+4) passes for conclusive results. If you run less than 8 passes you will be asked to run it again.

    Note   Note
    Both of these diagnostics has been known to discover errors in RAM in later passes than the eighth pass. This is for information only; if you feel there is a definite problem with the RAM and 8 passes have shown no errors feel free to continue for longer.

    Running 8 passes of MemTest86+ or 4+4 passes of Memtest86 is a long and drawn out exercise and the more RAM you have the longer it will take. It's recommended to run it overnight, starting just before you go to bed and leave it overnight.

    Take a picture when done and post in the forum please.
      My Computers
    Quote Quote

  4. zbook
    Posts : 41,560
    windows 10 professional version 1607 build 14393.969 64 bit
       New #3

    Bad memory typically requires a manual reset.

    Let's see the Memtest86+ results:

    If there are errors > replace the RAM with identical pairs > make sure they are on the Qualified Vendor List (QVL)
    Z97-AR Memory / Device Support | Motherboards | ASUS USA


    If there are no errors > the bad memory blocked regions will be reset > retest each module with 8 passes to differentiate malfunctioning from normal RAM.


    The logs displayed drive file system corruption.

    There were problems in the above chkdsk /scan:

    Code:
    Windows has found problems that must be fixed offline.
Please run "chkdsk /f" to fix the issues.


    Please complete the RAM testing first.



    Open administrative command prompt and type or copy and paste:
    chkdsk /r /v
    This may take hours to run so plan to run overnight.
    Run on all drives using the syntax: chkdsk /r /v C: or chkdsk /r /v D: changing the drive letter to the applicable drive.

    C:\Windows\system32>chkdsk /r /v
    The type of the file system is NTFS.
    Cannot lock current drive.

    Chkdsk cannot run because the volume is in use by another
    process. Would you like to schedule this volume to be
    checked the next time the system restarts? (Y/N)

    Type: Y
    reboot


    Use the information in this link to find the chkdsk report in the event viewer.
    Copy and paste into notepad > save to desktop > post into the thread using a one drive, drop box, or google drive share link:
    Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials
    Read Chkdsk Log in Event Viewer in Windows 10


    The logs also displayed possible problems with GPU drivers.


    Code:
    Event[1059]:
  Log Name: System
  Source: Microsoft-Windows-Memory-Diagnostic-Task-Handler
  Date: 2020-11-17T13:48:16.4390000Z
  Event ID: 1001
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-21-894128607-3556545708-3895487983-1001
  User Name: NZXT-1\micha
  Computer: NZXT-1
  Description: 
Windows removed bad memory regions from this PC.
    Code:
    Event[6166]:
  Log Name: System
  Source: Microsoft-Windows-Memory-Diagnostic-Task-Handler
  Date: 2020-12-08T16:49:41.3650000Z
  Event ID: 1001
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-21-894128607-3556545708-3895487983-1001
  User Name: NZXT-1\micha
  Computer: NZXT-1
  Description: 
Windows removed bad memory regions from this PC.

    Code:
    Location     : DIMM_A1
BankLabel    : BANK 0
Manufacturer : 0215
MemoryType   : DDR3
FormFactor   : DIMM
Capacity     : 8GB
Speed        : 2133
Serial       : 00000000
PartNumber   : CMD32GX3M4A2133C9 
ECC          : False
TypeDetail   : {Synchronous}

Location     : DIMM_A2
BankLabel    : BANK 1
Manufacturer : 0215
MemoryType   : DDR3
FormFactor   : DIMM
Capacity     : 8GB
Speed        : 1333
Serial       : 00000000
PartNumber   : CMD16GX3M2A1866C9 
ECC          : False
TypeDetail   : {Synchronous}

Location     : DIMM_B1
BankLabel    : BANK 2
Manufacturer : 0215
MemoryType   : DDR3
FormFactor   : DIMM
Capacity     : 8GB
Speed        : 2133
Serial       : 00000000
PartNumber   : CMD32GX3M4A2133C9 
ECC          : False
TypeDetail   : {Synchronous}

Location     : DIMM_B2
BankLabel    : BANK 3
Manufacturer : 0215
MemoryType   : DDR3
FormFactor   : DIMM
Capacity     : 8GB
Speed        : 1333
Serial       : 00000000
PartNumber   : CMD16GX3M2A1866C9 
ECC          : False
TypeDetail   : {Synchronous}

    Code:
    Event[8242]:
  Log Name: System
  Source: Ntfs
  Date: 2020-12-11T12:14:52.8730000Z
  Event ID: 55
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: NZXT-1
  Description: 
A corruption was discovered in the file system structure on volume C:.

The exact nature of the corruption is unknown.  The file system structures need to be scanned online.

    Code:
    C:\WINDOWS\system32>bcdedit /enum {badmemory}

RAM Defects
-----------
identifier {badmemory}
badmemorylist 0x20f5ae
0x20f5be
0x24f5e9
0x25ede9
0x25edf9
0x29d9ec
0x29d9fc
0x30fde7
0x30fdf7
0x31d5e8
0x31d5f8
0x3361e4
0x3361f4
0x33f68c
0x3ae9ee
0x3ae9fe
0x3af1a9
0x3af5ae
0x3af5be
0x3af9ac
0x3b0284
0x3b0294
0x3b19f9
0x3df1a4
0x3efdec
0x3efdfc
0x62fda4
0x62fdb4
0x6a05ab
0x70d5be
0x70e1bb
0x75dda0
0x7bf9a4
0x7bf9b4
0x7df1a8
0x7df1b8

    Code:
    12/6/2020 4:23 AM	Windows Error Reporting	Fault bucket AV_nvlddmkm!CNvLSchedulerFermi::pushSemaphoreRelease, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 16eea3c8-54de-42b9-ac54-faec7e12e05c

Problem signature:
P1: d1
P2: b2
P3: 2
P4: 0
P5: fffff8064ac4c13d
P6: 10_0_19042
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\Minidump\120520-5125-01.dmp
\\?\C:\WINDOWS\TEMP\WER-10312-0.sysdata.xml
\\?\C:\WINDOWS\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3DA5.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3DB5.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3DC4.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3DD5.tmp.txt
\\?\C:\Windows\Temp\WER67E2.tmp.WERDataCollectionStatus.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_d1_833d484c29a1baa4c5e5fdb8daa4583188b163_00000000_cab_7be0af75-58df-4ad0-8ae5-d028b0de2b37

Analysis symbol: 
Rechecking for solution: 0
Report Id: b02684f2-9ba1-4a2e-9fa9-81089539d448
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0

    Code:
    11/24/2020 2:07 PM	Windows Error Reporting	Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Turing, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 38df8a44-4fd3-4c48-b7ae-38723976060f

Problem signature:
P1: 141
P2: ffffaf0680491060
P3: fffff8045efc2298
P4: 0
P5: 4
P6: 10_0_19042
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20201124-0706.dmp
\\?\C:\WINDOWS\TEMP\WER-150728250-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFEA5.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFEA6.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFEB6.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFEC7.tmp.txt
\\?\C:\Windows\Temp\WERB94B.tmp.WERDataCollectionStatus.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_d8a65b7db6e4530b5c1c2da7620799e9643f97_00000000_cab_452b010b-15e6-4d19-a007-348d52c026ce

Analysis symbol: 
Rechecking for solution: 0
Report Id: 452b010b-15e6-4d19-a007-348d52c026ce
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0
11/22/2020 8:13 PM	Windows Error Reporting	Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Turing, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 5181c048-86d4-4bcb-b50c-f6ed26522396

Problem signature:
P1: 141
P2: ffff930f574a7010
P3: fffff80616aa2298
P4: 0
P5: 4
P6: 10_0_19042
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20201122-1313.dmp
\\?\C:\WINDOWS\TEMP\WER-22645671-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9B19.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9B29.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9B3A.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9B5A.tmp.txt
\\?\C:\Windows\Temp\WERC1EB.tmp.WERDataCollectionStatus.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_8bb36c22123074aac914bd4e2d77e9d432ba6e4_00000000_cab_a86c2dba-7fba-4c9c-9bb6-83c8eb9d066d

Analysis symbol: 
Rechecking for solution: 0
Report Id: a86c2dba-7fba-4c9c-9bb6-83c8eb9d066d
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0
12/1/2020 1:39 AM	Windows Error Reporting	Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Turing, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 6af17b37-3b7a-4c4d-a0ef-63ca9ca7d7f1

Problem signature:
P1: 141
P2: ffff898f4f3d52c0
P3: fffff800733e2298
P4: 0
P5: 4
P6: 10_0_19042
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20201130-1838.dmp
\\?\C:\WINDOWS\TEMP\WER-83596328-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA474.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA484.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA485.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA4A5.tmp.txt
\\?\C:\Windows\Temp\WER2A6D.tmp.WERDataCollectionStatus.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_950f1718498a8f317b47e712bc66f4b5de847d_00000000_cab_f67d17ad-fc56-4371-b679-5aa6ab899a48

Analysis symbol: 
Rechecking for solution: 0
Report Id: f67d17ad-fc56-4371-b679-5aa6ab899a48
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0
11/30/2020 12:11 AM	Windows Error Reporting	Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Turing, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: b8187f97-6164-4169-a722-a2c461b869a8

Problem signature:
P1: 141
P2: ffffbb8bd1ae7050
P3: fffff80544a32298
P4: 0
P5: 4
P6: 10_0_19042
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20201129-1711.dmp
\\?\C:\WINDOWS\TEMP\WER-16212171-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER707B.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER708C.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER708D.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER70AD.tmp.txt
\\?\C:\Windows\Temp\WERD5AE.tmp.WERDataCollectionStatus.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_4e186b2a823ec828145ab453bb36dea9889ff4b_00000000_cab_5e106764-a5c2-42e4-a07e-0bcd5c1add8e

Analysis symbol: 
Rechecking for solution: 0
Report Id: 5e106764-a5c2-42e4-a07e-0bcd5c1add8e
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0
11/1/2020 2:55 PM	Windows Error Reporting	Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Turing_3D, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0ce62ecb-3833-4009-aabf-67e7d4ba3893

Problem signature:
P1: 141
P2: ffffb707ba993460
P3: fffff80125390188
P4: 0
P5: 0
P6: 10_0_19041
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20201101-0754.dmp
\\?\C:\WINDOWS\TEMP\WER-133974578-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5D3D.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5D3E.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5D4C.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5D6D.tmp.txt
\\?\C:\Windows\Temp\WERF7F7.tmp.WERDataCollectionStatus.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_4ed4d31ba9e7e5f49ae4f39fa798ff20753e_00000000_cab_0ccc78d2-9c0a-4231-af7d-986a4251edab

Analysis symbol: 
Rechecking for solution: 0
Report Id: 0ccc78d2-9c0a-4231-af7d-986a4251edab
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0
11/1/2020 4:00 PM	Windows Error Reporting	Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Turing_3D, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: adfef2b4-9cab-46be-b3f9-0edbd909091f

Problem signature:
P1: 141
P2: ffffb707b75e2400
P3: fffff80125390188
P4: 0
P5: 4bfc
P6: 10_0_19041
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20201101-0824.dmp
\\?\C:\WINDOWS\TEMP\WER-135809906-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5C89.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5C99.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5C98.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5CB9.tmp.txt
\\?\C:\Windows\Temp\WER8803.tmp.WERDataCollectionStatus.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_dfa4fd3b59e3b9f6af614f9ad7447accd47757c_00000000_cab_f908c400-c129-475f-8f46-fe8ae90534a8

Analysis symbol: 
Rechecking for solution: 0
Report Id: f908c400-c129-475f-8f46-fe8ae90534a8
Report Status: 268435460
Hashed bucket: 
Cab Guid: 0
11/28/2020 2:18 AM	Windows Error Reporting	Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Turing_SCG3D, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 1a553f57-08e5-46fb-996c-e79afcb60227

Problem signature:
P1: 141
P2: ffffac05766ee060
P3: fffff80174482298
P4: 0
P5: 27d8
P6: 10_0_19042
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20201127-1918.dmp
\\?\C:\WINDOWS\TEMP\WER-113434328-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERECB3.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERECC3.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERECC4.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERECE4.tmp.txt
\\?\C:\Windows\Temp\WER224A.tmp.WERDataCollectionStatus.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_f64f4e93821627b85b549819d91975f16ada8e4_00000000_cab_9f183aca-dfd7-4135-97f1-c11b2266cd2f

Analysis symbol: 
Rechecking for solution: 0
Report Id: 9f183aca-dfd7-4135-97f1-c11b2266cd2f
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0
11/30/2020 12:57 AM	Windows Error Reporting	Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Turing_SCG3D, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 1f0b9abf-d26e-41d4-8c1c-844c9929cba6

Problem signature:
P1: 141
P2: ffffbb8bc6338010
P3: fffff80544a32298
P4: 0
P5: 4d4
P6: 10_0_19042
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20201129-1756.dmp
\\?\C:\WINDOWS\TEMP\WER-18944265-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1CB2.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1CC2.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1CC1.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1CE1.tmp.txt
\\?\C:\Windows\Temp\WER5297.tmp.WERDataCollectionStatus.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_ecdf8f60c7c5c4c5949f5ae5cccc846077361d9_00000000_cab_27850f5f-9535-4c10-8f71-bc44de4b263c

Analysis symbol: 
Rechecking for solution: 0
Report Id: 27850f5f-9535-4c10-8f71-bc44de4b263c
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0
12/10/2020 2:02 PM	Windows Error Reporting	Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Turing_SCG3D, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 24f5b507-9cb9-42c8-b654-79717b9f5ee3

Problem signature:
P1: 141
P2: ffffa98ef91ba460
P3: fffff8066439372c
P4: 0
P5: 71e8
P6: 10_0_19042
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20201210-0702.dmp
\\?\C:\WINDOWS\TEMP\WER-53034421-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4B42.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4B43.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4B54.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4B64.tmp.txt
\\?\C:\Windows\Temp\WER7409.tmp.WERDataCollectionStatus.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_fa3e41ac87e55efeacf832dd6d59f3dda4517929_00000000_cab_22335daf-ad5c-4977-941b-2f90fa4775ad

Analysis symbol: 
Rechecking for solution: 0
Report Id: 22335daf-ad5c-4977-941b-2f90fa4775ad
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0
12/1/2020 3:30 AM	Windows Error Reporting	Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Turing_SCG3D, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 35ed1bb9-6d44-44c3-95ec-8654f18c80b8

Problem signature:
P1: 141
P2: ffffd689339a4460
P3: fffff804348f2298
P4: 0
P5: 4050
P6: 10_0_19042
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20201130-2030.dmp
\\?\C:\WINDOWS\TEMP\WER-754750-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER915D.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER916E.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER917C.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER918D.tmp.txt
\\?\C:\Windows\Temp\WERAEF8.tmp.WERDataCollectionStatus.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_84a36d24cee2476b4429ecdab72fca1c94ba5_00000000_cab_83125ef9-ffaf-4a06-8408-183aeae8f41a

Analysis symbol: 
Rechecking for solution: 0
Report Id: 83125ef9-ffaf-4a06-8408-183aeae8f41a
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0
12/1/2020 2:23 PM	Windows Error Reporting	Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Turing_SCG3D, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 3910cf45-5242-40fa-8e7d-cd77c1feb33a

Problem signature:
P1: 141
P2: ffff8806c527f460
P3: fffff8070df62298
P4: 0
P5: 2050
P6: 10_0_19042
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20201201-0723.dmp
\\?\C:\WINDOWS\TEMP\WER-34989140-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF099.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF0A9.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF0B8.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF0C9.tmp.txt
\\?\C:\Windows\Temp\WER32B4.tmp.WERDataCollectionStatus.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_cfe6757d9b40dbb51812d09863bbd75cc21869_00000000_cab_0c66e5c9-bd4a-4105-849e-78f606bb200a

Analysis symbol: 
Rechecking for solution: 0
Report Id: 0c66e5c9-bd4a-4105-849e-78f606bb200a
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0
12/4/2020 1:24 PM	Windows Error Reporting	Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Turing_SCG3D, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 3b74aa66-a7ac-4454-a017-ef21b8e07e1c

Problem signature:
P1: 141
P2: ffffe7816717e010
P3: fffff8027f812298
P4: 0
P5: 253c
P6: 10_0_19042
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20201204-0623.dmp
\\?\C:\WINDOWS\TEMP\WER-124818312-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA069.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA06A.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA079.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA089.tmp.txt
\\?\C:\Windows\Temp\WER1135.tmp.WERDataCollectionStatus.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_3271dea4f2eb7f72f2a2f89a9f4f8aae88b3468_00000000_cab_6563ccdd-b844-48c2-b1e2-770c5815c733

Analysis symbol: 
Rechecking for solution: 0
Report Id: 6563ccdd-b844-48c2-b1e2-770c5815c733
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0
12/1/2020 1:39 AM	Windows Error Reporting	Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Turing_SCG3D, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 3ba71af8-e26e-4e3c-be47-7f04732ca6fa

Problem signature:
P1: 141
P2: ffff898f4f2fe010
P3: fffff800733e2298
P4: 0
P5: 49dc
P6: 10_0_19042
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20201130-1838.dmp
\\?\C:\WINDOWS\TEMP\WER-83589593-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER86D9.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER86DA.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER86D9.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER86FA.tmp.txt
\\?\C:\Windows\Temp\WERE064.tmp.WERDataCollectionStatus.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_eb9c1078ecc37de7948038f4509ef011f8ec299_00000000_cab_638da4c2-45cb-4934-b5c0-36204d6c1563

Analysis symbol: 
Rechecking for solution: 0
Report Id: 638da4c2-45cb-4934-b5c0-36204d6c1563
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0
12/2/2020 12:53 PM	Windows Error Reporting	Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Turing_SCG3D, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 53500543-6b0f-4fb1-b698-0bd54499a3b1

Problem signature:
P1: 141
P2: ffff8806cbc44470
P3: fffff8070df62298
P4: 0
P5: b54
P6: 10_0_19042
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20201202-0553.dmp
\\?\C:\WINDOWS\TEMP\WER-115987343-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDF47.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDF58.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDF57.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDF77.tmp.txt
\\?\C:\Windows\Temp\WER1F4F.tmp.WERDataCollectionStatus.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_6134e587a6315267361075de2fc6f5d8d189356_00000000_cab_aa147b40-2f30-4d86-b190-731532cfc6dc

Analysis symbol: 
Rechecking for solution: 0
Report Id: aa147b40-2f30-4d86-b190-731532cfc6dc
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0
12/5/2020 2:55 AM	Windows Error Reporting	Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Turing_SCG3D, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 536505f2-935b-4741-af74-d3eea58b23c1

Problem signature:
P1: 141
P2: ffff9c8288ee7010
P3: fffff8060fea2298
P4: 0
P5: 2a88
P6: 10_0_19042
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20201204-1955.dmp
\\?\C:\WINDOWS\TEMP\WER-47918796-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3C88.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3C89.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3C98.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3CA8.tmp.txt
\\?\C:\Windows\Temp\WER67A0.tmp.WERDataCollectionStatus.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_86f5cd76a9c6e94ca5dcea96704fb3df74af19_00000000_cab_da1c3287-1f37-4205-a0c1-80ac870eee02

Analysis symbol: 
Rechecking for solution: 0
Report Id: da1c3287-1f37-4205-a0c1-80ac870eee02
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0
12/6/2020 1:53 AM	Windows Error Reporting	Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Turing_SCG3D, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 5a9f7be8-3350-4885-b0e8-5716624cb211

Problem signature:
P1: 141
P2: ffffbb89929ad460
P3: fffff8064b072298
P4: 0
P5: 2ee0
P6: 10_0_19042
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20201205-1853.dmp
\\?\C:\WINDOWS\TEMP\WER-255593-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF3F6.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF407.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF408.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF428.tmp.txt
\\?\C:\Windows\Temp\WER1EA1.tmp.WERDataCollectionStatus.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_8ce419858da7f5c67ac742a071b3c4d88145a04f_00000000_cab_2a32e045-7ea6-4201-b183-1b90e8066c50

Analysis symbol: 
Rechecking for solution: 0
Report Id: 2a32e045-7ea6-4201-b183-1b90e8066c50
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0
12/1/2020 3:16 AM	Windows Error Reporting	Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Turing_SCG3D, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 5e22c07b-0059-4078-b470-2eac55e163d3

Problem signature:
P1: 141
P2: ffff898f3cbf8060
P3: fffff800733e2298
P4: 0
P5: 17a0
P6: 10_0_19042
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20201130-2016.dmp
\\?\C:\WINDOWS\TEMP\WER-89476265-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER59A9.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER59BA.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER59B9.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER59E9.tmp.txt
\\?\C:\Windows\Temp\WER75FC.tmp.WERDataCollectionStatus.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_15ed945c577ceae88a8a5f568948b6c9901c4b_00000000_cab_5f6346c4-6347-460d-b8d6-a47703abf2bc

Analysis symbol: 
Rechecking for solution: 0
Report Id: 5f6346c4-6347-460d-b8d6-a47703abf2bc
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0
12/9/2020 2:21 AM	Windows Error Reporting	Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Turing_SCG3D, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 6f92e8c8-1685-4b64-952d-23fcc9d4bb60

Problem signature:
P1: 141
P2: ffffe78855ae3050
P3: fffff8071c0a2298
P4: 0
P5: 854
P6: 10_0_19042
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20201208-1921.dmp
\\?\C:\WINDOWS\TEMP\WER-3900906-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9367.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9378.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9377.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9397.tmp.txt
\\?\C:\Windows\Temp\WERCAD3.tmp.WERDataCollectionStatus.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_40e098a188b61cd528d9a87b31d2ad4f5f897_00000000_cab_e4e3339b-b084-47e3-9927-1823854d7e26

Analysis symbol: 
Rechecking for solution: 0
Report Id: e4e3339b-b084-47e3-9927-1823854d7e26
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0
12/6/2020 11:44 PM	Windows Error Reporting	Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Turing_SCG3D, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 7f8a56ca-326c-4aa1-8d43-bdc4e7783deb

Problem signature:
P1: 141
P2: ffff8d06b9f79050
P3: fffff80445f92298
P4: 0
P5: 451c
P6: 10_0_19042
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20201206-1644.dmp
\\?\C:\WINDOWS\TEMP\WER-1311015-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREE3.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREF3.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREF4.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF05.tmp.txt
\\?\C:\Windows\Temp\WER2CCC.tmp.WERDataCollectionStatus.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_6220ef79f967adb2b6a3429b8a3d3e226b8593c_00000000_cab_a4b7e510-aed4-4208-a8ae-f21e06dd55d7

Analysis symbol: 
Rechecking for solution: 0
Report Id: a4b7e510-aed4-4208-a8ae-f21e06dd55d7
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0
12/7/2020 3:46 AM	Windows Error Reporting	Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Turing_SCG3D, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 876a90d5-aaff-4b24-8f36-9a94fa927291

Problem signature:
P1: 141
P2: ffff8d06b226b460
P3: fffff80445f92298
P4: 0
P5: 34b4
P6: 10_0_19042
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20201206-2046.dmp
\\?\C:\WINDOWS\TEMP\WER-15825875-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER87C9.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER87DA.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER87E8.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER87F9.tmp.txt
\\?\C:\Windows\Temp\WERB274.tmp.WERDataCollectionStatus.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_dcacacbbdc144fc0ef19bdc23242d452cb757ff_00000000_cab_c8c6a73c-0696-43c5-b9ca-790348b9c4a8

Analysis symbol: 
Rechecking for solution: 0
Report Id: c8c6a73c-0696-43c5-b9ca-790348b9c4a8
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0
12/7/2020 1:56 PM	Windows Error Reporting	Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Turing_SCG3D, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 8d9ae5fc-479b-4c2f-a173-0d06f68f25f9

Problem signature:
P1: 141
P2: ffff888e9f67e010
P3: fffff80763432298
P4: 0
P5: 201c
P6: 10_0_19042
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20201207-0656.dmp
\\?\C:\WINDOWS\TEMP\WER-36059359-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER45FE.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER460F.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4610.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4621.tmp.txt
\\?\C:\Windows\Temp\WER7AEA.tmp.WERDataCollectionStatus.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_295020983f685d9e3e2cfda19901da75ecd2a0_00000000_cab_40bfaa6f-5b12-4ef4-8dec-678e25b10bc8

Analysis symbol: 
Rechecking for solution: 0
Report Id: 40bfaa6f-5b12-4ef4-8dec-678e25b10bc8
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0
11/14/2020 3:10 PM	Windows Error Reporting	Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Turing_SCG3D, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: a1d31a3a-1d05-4ae4-aafa-0de7a2e8636e

Problem signature:
P1: 141
P2: ffff9a0fbc1e8010
P3: fffff80755390188
P4: 0
P5: 3354
P6: 10_0_19042
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20201114-0809.dmp
\\?\C:\WINDOWS\TEMP\WER-65383187-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB9C9.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB9D9.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB9DA.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB9EB.tmp.txt
\\?\C:\Windows\Temp\WERE7DF.tmp.WERDataCollectionStatus.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_f8de89c832017abf7ff091154474ab8e3b9fac_00000000_cab_a6b8b28f-ccef-4d2e-a73c-1defe3359641

Analysis symbol: 
Rechecking for solution: 0
Report Id: a6b8b28f-ccef-4d2e-a73c-1defe3359641
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0
11/29/2020 2:34 PM	Windows Error Reporting	Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Turing_SCG3D, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: a67bbba6-9034-4439-909d-beb781b658c2

Problem signature:
P1: 141
P2: ffffd90fbb8c2460
P3: fffff800707e2298
P4: 0
P5: 4410
P6: 10_0_19042
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20201129-0733.dmp
\\?\C:\WINDOWS\TEMP\WER-48195187-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7298.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER72A9.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER72A8.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER72C8.tmp.txt
\\?\C:\Windows\Temp\WER95D1.tmp.WERDataCollectionStatus.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_a11dfcd6896db4d189d97f287f1bd6e85912b731_00000000_cab_b3e618e1-a9a8-4dea-90c7-48be3153ba0c

Analysis symbol: 
Rechecking for solution: 0
Report Id: b3e618e1-a9a8-4dea-90c7-48be3153ba0c
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0
11/14/2020 5:03 AM	Windows Error Reporting	Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Turing_SCG3D, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: aa68800e-560c-4920-9e3a-6d83505c351a

Problem signature:
P1: 141
P2: ffff9a0faf92f010
P3: fffff80755390188
P4: 0
P5: 3bec
P6: 10_0_19042
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20201113-2203.dmp
\\?\C:\WINDOWS\TEMP\WER-28990625-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER68F5.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6905.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6914.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6925.tmp.txt
\\?\C:\Windows\Temp\WERB61C.tmp.WERDataCollectionStatus.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_da6512a46f299d689bc05b1e77582835c60f6f4_00000000_cab_32634c0f-c791-4cb1-a335-3cf71d63ede2

Analysis symbol: 
Rechecking for solution: 0
Report Id: 32634c0f-c791-4cb1-a335-3cf71d63ede2
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0
11/13/2020 3:22 PM	Windows Error Reporting	Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Turing_SCG3D, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: b28670c5-743e-4b14-a844-0275d3ca4d77

Problem signature:
P1: 141
P2: ffffc88ed117b010
P3: fffff804207e0188
P4: 0
P5: 4aec
P6: 10_0_19042
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20201113-0822.dmp
\\?\C:\WINDOWS\TEMP\WER-143850421-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER867.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER868.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER877.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER888.tmp.txt
\\?\C:\Windows\Temp\WER2893.tmp.WERDataCollectionStatus.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_9d6b9cb529fc61e93e76e6173be4f2ccd22b9350_00000000_cab_2d781226-915f-43da-8487-f3d4d6687825

Analysis symbol: 
Rechecking for solution: 0
Report Id: 2d781226-915f-43da-8487-f3d4d6687825
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0
11/25/2020 9:24 PM	Windows Error Reporting	Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Turing_SCG3D, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: b51f9f50-0679-4072-a1cc-06dea32fca20

Problem signature:
P1: 141
P2: ffffaf06812e9010
P3: fffff8045efc2298
P4: 0
P5: 0
P6: 10_0_19042
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20201125-1424.dmp
\\?\C:\WINDOWS\TEMP\WER-263404203-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER470F.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER471F.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER471E.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER473E.tmp.txt
\\?\C:\Windows\Temp\WER71B9.tmp.WERDataCollectionStatus.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_daef2584885ee528cb8bde992b1a6be50abefab_00000000_cab_a83bedfb-1cfc-4660-b805-1b9912a54b62

Analysis symbol: 
Rechecking for solution: 0
Report Id: a83bedfb-1cfc-4660-b805-1b9912a54b62
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0
11/30/2020 12:11 AM	Windows Error Reporting	Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Turing_SCG3D, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: b69a1d78-5501-4166-85d2-0b9a127c8b7f

Problem signature:
P1: 141
P2: ffffbb8bd45d6050
P3: fffff80544a32298
P4: 0
P5: 50bc
P6: 10_0_19042
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20201129-1711.dmp
\\?\C:\WINDOWS\TEMP\WER-16207343-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5A24.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5A25.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5A34.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5A45.tmp.txt
\\?\C:\Windows\Temp\WER8FDB.tmp.WERDataCollectionStatus.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_c4b3855e2cf435233f8b22418648e7186bdb479_00000000_cab_830f0751-4652-4228-b347-b919cba94d76

Analysis symbol: 
Rechecking for solution: 0
Report Id: 830f0751-4652-4228-b347-b919cba94d76
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0
11/21/2020 11:59 PM	Windows Error Reporting	Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Turing_SCG3D, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: c487b6c3-04ae-4d9c-8784-815d99285828

Problem signature:
P1: 141
P2: ffffc78e9986c060
P3: fffff80243262298
P4: 0
P5: 2170
P6: 10_0_19042
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20201121-1658.dmp
\\?\C:\WINDOWS\TEMP\WER-200940437-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER28B4.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER28C5.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER28C4.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER28E4.tmp.txt
\\?\C:\Windows\Temp\WER50CF.tmp.WERDataCollectionStatus.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_421fa4d9af10b24164f6c3f1afe80caab0e253_00000000_cab_e70fe497-a96f-459c-b4ba-24f941c1347c

Analysis symbol: 
Rechecking for solution: 0
Report Id: e70fe497-a96f-459c-b4ba-24f941c1347c
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0
12/2/2020 3:28 AM	Windows Error Reporting	Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Turing_SCG3D, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: ca4c6835-0e58-4ebf-9e91-eee5f3c30926

Problem signature:
P1: 141
P2: ffff8806cd58d200
P3: fffff8070df62298
P4: 0
P5: 1a78
P6: 10_0_19042
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20201201-2028.dmp
\\?\C:\WINDOWS\TEMP\WER-82112937-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFF26.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFF37.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFF36.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFF46.tmp.txt
\\?\C:\Windows\Temp\WER2E26.tmp.WERDataCollectionStatus.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_1b53596c3c48cb170a43391e6a57cc6ab1c5879_00000000_cab_9be174a7-3da8-41e9-80cc-afce1676e94d

Analysis symbol: 
Rechecking for solution: 0
Report Id: 9be174a7-3da8-41e9-80cc-afce1676e94d
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0
11/22/2020 8:13 PM	Windows Error Reporting	Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Turing_SCG3D, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: cf58694a-325e-4c46-8221-cbdf4e6025f6

Problem signature:
P1: 141
P2: ffff930f589e5010
P3: fffff80616aa2298
P4: 0
P5: 3918
P6: 10_0_19042
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20201122-1313.dmp
\\?\C:\WINDOWS\TEMP\WER-22639812-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER80CA.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER80DB.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER80DA.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER80FA.tmp.txt
\\?\C:\Windows\Temp\WERA0E6.tmp.WERDataCollectionStatus.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_1a1e1ee3f72b97aeab9f977e251181983d48c6f3_00000000_cab_fa91c759-abb2-4d57-887b-e326245f475a

Analysis symbol: 
Rechecking for solution: 0
Report Id: fa91c759-abb2-4d57-887b-e326245f475a
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0
12/6/2020 3:12 AM	Windows Error Reporting	Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Turing_SCG3D, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: d1cc0f0a-a6f6-400b-ac48-93ea7fdc935d

Problem signature:
P1: 141
P2: ffffbb89986bf010
P3: fffff8064b072298
P4: 0
P5: 3fec
P6: 10_0_19042
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20201205-2011.dmp
\\?\C:\WINDOWS\TEMP\WER-4952890-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA27C.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA28D.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA28E.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA29F.tmp.txt
\\?\C:\Windows\Temp\WERCE8F.tmp.WERDataCollectionStatus.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_7ba631111923f1943dd7a0d9d7f29d5c67bee9f3_00000000_cab_f357e8d3-f955-48f0-b4ef-d703a230969f

Analysis symbol: 
Rechecking for solution: 0
Report Id: f357e8d3-f955-48f0-b4ef-d703a230969f
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0
12/2/2020 3:51 AM	Windows Error Reporting	Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Turing_SCG3D, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: d31a45c4-d682-48b7-a423-dfc3f171d853

Problem signature:
P1: 141
P2: ffff8806cc033050
P3: fffff8070df62298
P4: 0
P5: 29dc
P6: 10_0_19042
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20201201-2050.dmp
\\?\C:\WINDOWS\TEMP\WER-83455828-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7AEC.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7AED.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7AFC.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7B0D.tmp.txt
\\?\C:\Windows\Temp\WERB98D.tmp.WERDataCollectionStatus.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_71353926f93404fb84d398f4e6bee51483c415_00000000_cab_195469ae-73bc-4682-8448-f7cfa4a0c3df

Analysis symbol: 
Rechecking for solution: 0
Report Id: 195469ae-73bc-4682-8448-f7cfa4a0c3df
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0
11/24/2020 2:06 PM	Windows Error Reporting	Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Turing_SCG3D, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: f6bde533-cb0d-40a2-972f-0b4f56517291

Problem signature:
P1: 141
P2: ffffaf067d665010
P3: fffff8045efc2298
P4: 0
P5: 5b04
P6: 10_0_19042
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20201124-0706.dmp
\\?\C:\WINDOWS\TEMP\WER-150720687-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDE0D.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDE1E.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDE1D.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDE3D.tmp.txt
\\?\C:\Windows\Temp\WERB67.tmp.WERDataCollectionStatus.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_d019da75151d4043d6c177acaedc59a9708587_00000000_cab_d27b5767-8d87-4398-be8d-06a68ac4f549

Analysis symbol: 
Rechecking for solution: 0
Report Id: d27b5767-8d87-4398-be8d-06a68ac4f549
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0
12/11/2020 12:32 AM	Windows Error Reporting	Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Turing_SCGCompute, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 1041c0bf-61e8-4f07-a0a0-1a5fba35e3de

Problem signature:
P1: 141
P2: ffffab8826bd3010
P3: fffff8057d1b372c
P4: 0
P5: 46e8
P6: 10_0_19042
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20201210-1732.dmp
\\?\C:\WINDOWS\TEMP\WER-27752328-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8505.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8515.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8516.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8527.tmp.txt
\\?\C:\Windows\Temp\WERB9F1.tmp.WERDataCollectionStatus.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_a8cc01e46326272fa853fb6be6038ccfb7_00000000_cab_4587581e-dcb2-4637-98f5-e51c72bfd31f

Analysis symbol: 
Rechecking for solution: 0
Report Id: 4587581e-dcb2-4637-98f5-e51c72bfd31f
Report Status: 268435456
Hashed bucket: 
Cab Guid: 0
    Last edited by zbook; 12 Dec 2020 at 03:34.
      My Computer
    Quote Quote

  6. wreckingball
    Posts : 4
    Windows 10
    Thread Starter
       New #4

    Thank for your replies and for all the replies I've found in this forum.

    After reading, a lot, I cleared the badmemory list. Rebooted into memtest. Found 30 + errors in the first 6 tests. Then tested each stick individually. Found the faulty stick.

    It's currently running with half the RAM, but has been stable. Now I have to find some place to get replacement Corsair Dominator Platinum DDR3. A little tough to find, but at least I know what was the problem.

    Again, thank you all so very much.
      My Computer
    Quote Quote

  7. zbook
    Posts : 41,560
    windows 10 professional version 1607 build 14393.969 64 bit
       New #5

    Please post images.

    Please fix the drive file system corruption as per the earlier post.

    Please select RAM on the QVL with the same speed.

    The computer needs to be monitored after replacing the RAM.


    Corsair may have a lifetime warranty.


    Also run:
    Crucial System Scanner
      My Computer
    Quote Quote

  8. wreckingball
    Posts : 4
    Windows 10
    Thread Starter
       New #6

    I attempted to fix the disk corruption. It seems to have worked. I've tried to give the output below.

    I also reinstalled the graphics driver, but I don't see any errors.

    Thank you for the advice to use the QVL for ordering and to check if Corsair has a warranty. You were right, there is a limited lifetime warranty on memory. We'll see what if anything they come back with on my RMA request.

    At the moment, I'm not seeing any of the behaviors that I saw before. Again, thank you all.

    Chkdisk C:
    Code:
    Chkdsk was executed in scan mode on a volume snapshot.  

Checking file system on C:
The type of the file system is NTFS.

Stage 1: Examining basic file system structure ...
  978432 file records processed.                                                         File verification completed.
 Phase duration (File record verification): 5.41 seconds.
  5283 large file records processed.                                     Phase duration (Orphan file record recovery): 0.00 milliseconds.
  0 bad file records processed.                                       Phase duration (Bad file record checking): 0.29 milliseconds.

Stage 2: Examining file name linkage ...
  2014 reparse records processed.                                         1213962 index entries processed.                                                        Index verification completed.
 Phase duration (Index verification): 14.07 seconds.
  0 unindexed files scanned.                                          Phase duration (Orphan reconnection): 2.37 seconds.
  0 unindexed files recovered to lost and found.                      Phase duration (Orphan recovery to lost and found): 1.32 milliseconds.
  2014 reparse records processed.                                        Phase duration (Reparse point and Object ID verification): 8.77 milliseconds.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
 Phase duration (Security descriptor verification): 57.74 milliseconds.
  117766 data files processed.                                             Phase duration (Data attribute verification): 3.02 milliseconds.
CHKDSK is verifying Usn Journal...
  37477320 USN bytes processed.                                                            Usn Journal verification completed.
 Phase duration (USN journal verification): 156.85 milliseconds.

Windows has scanned the file system and found no problems.
No further action is required.

 999103700 KB total disk space.
 565264152 KB in 657515 files.
    461272 KB in 117767 indexes.
         0 KB in bad sectors.
   1117928 KB in use by the system.
     65536 KB occupied by the log file.
 432260348 KB available on disk.

      4096 bytes in each allocation unit.
 249775925 total allocation units on disk.
 108065087 allocation units available on disk.
Total duration: 22.10 seconds (22106 ms).

----------------------------------------------------------------------


Stage 1: Examining basic file system structure ...

Stage 2: Examining file name linkage ...

Stage 3: Examining security descriptors ...
    Chkdisk D:
    Code:
    Chkdsk was executed in read/write mode.  

Checking file system on D:
The type of the file system is NTFS.

Chkdsk cannot run because the volume is in use by another
process.  Chkdsk may run if this volume is dismounted first.
ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID.
Would you like to force a dismount on this volume? (Y/N) Volume dismounted.  All opened handles to this volume are now invalid.
Volume label is New Volume.

Stage 1: Examining basic file system structure ...
  278272 file records processed.                                                         File verification completed.
 Phase duration (File record verification): 1.96 seconds.
  1540 large file records processed.                                     Phase duration (Orphan file record recovery): 0.00 milliseconds.
  0 bad file records processed.                                       Phase duration (Bad file record checking): 0.29 milliseconds.

Stage 2: Examining file name linkage ...
  161768 reparse records processed.                                         330240 index entries processed.                                                        Index verification completed.
 Phase duration (Index verification): 4.66 seconds.
  0 unindexed files scanned.                                          Phase duration (Orphan reconnection): 92.34 milliseconds.
  0 unindexed files recovered to lost and found.                      Phase duration (Orphan recovery to lost and found): 1.96 milliseconds.
  161768 reparse records processed.                                        Phase duration (Reparse point and Object ID verification): 257.09 milliseconds.

Stage 3: Examining security descriptors ...
Cleaning up 187 unused index entries from index $SII of file 9.
Cleaning up 187 unused index entries from index $SDH of file 9.
Cleaning up 187 unused security descriptors.
Security descriptor verification completed.
 Phase duration (Security descriptor verification): 2.56 milliseconds.
  25985 data files processed.                                             Phase duration (Data attribute verification): 0.21 milliseconds.
CHKDSK is verifying Usn Journal...
  41211448 USN bytes processed.                                                            Usn Journal verification completed.
 Phase duration (USN journal verification): 121.37 milliseconds.

Stage 4: Looking for bad clusters in user file data ...
  278256 files processed.                                                                File data verification completed.
 Phase duration (User file recovery): 35.97 minutes.

Stage 5: Looking for bad, free clusters ...
  291622880 free clusters processed.                                                        Free space verification is complete.
 Phase duration (Free space recovery): 0.00 milliseconds.

Windows has scanned the file system and found no problems.
No further action is required.

1953382399 KB total disk space.
 786365044 KB in 250715 files.
     81168 KB in 25986 indexes.
         0 KB in bad sectors.
    444663 KB in use by the system.
     65536 KB occupied by the log file.
1166491524 KB available on disk.

      4096 bytes in each allocation unit.
 488345599 total allocation units on disk.
 291622881 allocation units available on disk.
Total duration: 36.09 minutes (2165820 ms).
      My Computer
    Quote Quote

  9. zbook
    Posts : 41,560
    windows 10 professional version 1607 build 14393.969 64 bit
       New #7

    Please run overnight a deep scan on C:

    Open administrative command prompt and type or copy and paste:
    chkdsk /b /v C:
      My Computer
    Quote Quote

  10. wreckingball
    Posts : 4
    Windows 10
    Thread Starter
       New #8

    Well, it crashed again. I had it set to do the deep scan on next reboot. Here's that log. Thank you.

    Code:
    Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.                         

Stage 1: Examining basic file system structure ...
  978432 file records processed.                                                         
File verification completed.
 Phase duration (File record verification): 4.50 seconds.
  4645 large file records processed.                                    
 Phase duration (Orphan file record recovery): 0.00 milliseconds.
  0 bad file records processed.                                      
 Phase duration (Bad file record checking): 0.61 milliseconds.

Stage 2: Examining file name linkage ...
  2021 reparse records processed.                                       
  1193828 index entries processed.                                                        
Index verification completed.
 Phase duration (Index verification): 12.27 seconds.
  0 unindexed files scanned.                                         
 Phase duration (Orphan reconnection): 1.43 seconds.
  0 unindexed files recovered to lost and found.                     
 Phase duration (Orphan recovery to lost and found): 18.71 milliseconds.
  2021 reparse records processed.                                       
 Phase duration (Reparse point and Object ID verification): 6.97 milliseconds.

Stage 3: Examining security descriptors ...
Cleaning up 24 unused index entries from index $SII of file 0x9.
Cleaning up 24 unused index entries from index $SDH of file 0x9.
Cleaning up 24 unused security descriptors.
Security descriptor verification completed.
 Phase duration (Security descriptor verification): 34.18 milliseconds.
  107699 data files processed.                                            
 Phase duration (Data attribute verification): 0.67 milliseconds.
CHKDSK is verifying Usn Journal...
  41054744 USN bytes processed.                                                            
Usn Journal verification completed.
 Phase duration (USN journal verification): 122.19 milliseconds.

Stage 4: Looking for bad clusters in user file data ...
  978416 files processed.                                                                
File data verification completed.
 Phase duration (User file recovery): 22.46 minutes.

Stage 5: Looking for bad, free clusters ...
  110307276 free clusters processed.                                                        
Free space verification is complete.
 Phase duration (Free space recovery): 0.00 milliseconds.

Windows has scanned the file system and found no problems.
No further action is required.

 999103700 KB total disk space.
 556301332 KB in 648730 files.
    451736 KB in 107700 indexes.
         0 KB in bad sectors.
   1121528 KB in use by the system.
     65536 KB occupied by the log file.
 441229104 KB available on disk.

      4096 bytes in each allocation unit.
 249775925 total allocation units on disk.
 110307276 allocation units available on disk.
Total duration: 22.77 minutes (1366527 ms).

Internal Info:
00 ee 0e 00 90 89 0b 00 f9 56 14 00 00 00 00 00  .........V......
18 02 00 00 cd 05 00 00 00 00 00 00 00 00 00 00  ................
      My Computer
    Quote Quote

  12. zbook
    Posts : 41,560
    windows 10 professional version 1607 build 14393.969 64 bit
       New #9

    Once you have new RAM the computer can be monitored for stability / instability.
    Check the owners manual for DIMM slot when only using each 1, 2, and 3 RAM modules.
    Until the new RAM is available consider using only 1 RAM module in the applicable DIMM.
      My Computer
    Quote Quote

 

  Related Discussions
NZXT Cam Fan Issues
in PC Custom Builds and Overclocking

Ive been scratching my head here trying to figure this out.. I have 2 X62 kraken. One for cpu and gpu.. I have on the gpu one for about 3 months now some noctua fans. Today i went to install the same fans on the cpu in place of the NZXT fans and the...
NZXT Phantom 410 Case
in PC Custom Builds and Overclocking

There is a constant blinking LED light on the top of my case. It annoys me. Lol. I'm assuming it's the Power LED. Can someone confirm this and tell me why it constantly flashes? It is very bright. 198280
Random BSOD - First BSOD after windows format
in BSOD Crashes and Debugging

I got a bsod 4 days after a fresh windows installation. For many months I have been trying to figure out a kernel41 error with no bugcheck that would intermittently restart either idle or under stress, more so could take a month to restart or do it...
Hello, so i think i have dealt with this bluescreen 3times now, and it seemed to have gone away after i went from my amd system to intel. But now its there again. The most useful function ever, wake from sleep, is now bluescreening my computer. I...
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 19:56.
Find Us




Windows 10 Forums