B
Boy1245
I recently upgraded from a GTX 1070 to an RTX 3070. Ever since I got the new card, my PC keeps crashing constantly at random intervals with BSOD. I've included my dumps below. Would appreciate any help.
System:
Additional info: I don't know if this is connected, but at around the same time my PC stopped booting straight to Windows. No matter what I do, it insists on booting to BIOS. There doesn't seem to be anything wrong with my boot drive (SATA SSD), but I can only turn on the PC by going to BIOS first then closing it. From there it always boots normally to Windows with no problems.
Dumps (from WhoCrashed):
On Fri 11/13/2020 1:30:10 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\111320-19156-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x23994)
Bugcheck code: 0xA (0x5BC0, 0xFF, 0xCC, 0xFFFFF8032C012C27)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Fri 11/13/2020 1:11:14 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\111320-19031-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C3B20)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80026242B19, 0xFFFFB988ED316D40, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 11/12/2020 10:28:35 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\111220-11234-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C3B20)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF807545CBA07, 0xFFFFEC84A704DDF8, 0xFFFFD981E40D1930)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 11/12/2020 8:10:40 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\111220-40968-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2CE0)
Bugcheck code: 0xFC (0xFFFFF8007A600017, 0x80000007AE6E6829, 0xFFFFF90F4DB2EB60, 0x2)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an attempt was made to execute non-executable memory.
This may be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. Memory corruption can also occur because of overheating (thermal issue). There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 11/12/2020 7:59:44 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\111220-12156-01.dmp
This was probably caused by the following module: dxgmms2.sys (0xFFFFF8011DFE5A48)
Bugcheck code: 0xD1 (0x10, 0x2, 0x0, 0xFFFFF8011DFE5A48)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\dxgmms2.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Tue 11/10/2020 6:40:27 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\111020-18843-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF8061E51D705)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8061E51D705, 0xFFFF9F871E1169A0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.
On Mon 11/9/2020 6:06:19 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\110920-22343-01.dmp
This was probably caused by the following module: cfosspeed6.sys (0xFFFFF8062A26E549)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8062A26E549, 0xFFFFEE0273B66E18, 0xFFFFEE0273B66660)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\cfosspeed6.sys
product: cFosSpeed Driver
company: cFos Software GmbH
description: cFosSpeed Driver
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: cfosspeed6.sys (cFosSpeed Driver, cFos Software GmbH).
Google query: cfosspeed6.sys cFos Software GmbH SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
On Mon 11/9/2020 5:53:26 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\110920-17500-01.dmp
This was probably caused by the following module: hidclass.sys (0xFFFFF80055C0609F)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80055C0609F, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\hidclass.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hid Class Library
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Mon 11/9/2020 5:18:48 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\110920-20265-01.dmp
This was probably caused by the following module: cfosspeed6.sys (0xFFFFF8026BB8E505)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8026BB8E505, 0xFFFFFE8FFD5FEE18, 0xFFFFFE8FFD5FE660)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\cfosspeed6.sys
product: cFosSpeed Driver
company: cFos Software GmbH
description: cFosSpeed Driver
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: cfosspeed6.sys (cFosSpeed Driver, cFos Software GmbH).
Google query: cfosspeed6.sys cFos Software GmbH SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
On Mon 11/9/2020 5:13:29 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\110920-23859-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF8014F51D705)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8014F51D705, 0xFFFFF0881948E9A0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.
Continue reading...
System:
- CPU
Intel Core i7 6700K - Motherboard
MSI Z170A SLI Plus - RAM
G.SKILL Ripjaws V Series 32GB 3600 MHz - GPU
MSI GeForce RTX 3070 Gaming X Trio - PSU
Corsair RM650 80+ Gold - Operating System
Windows 10 Pro
Additional info: I don't know if this is connected, but at around the same time my PC stopped booting straight to Windows. No matter what I do, it insists on booting to BIOS. There doesn't seem to be anything wrong with my boot drive (SATA SSD), but I can only turn on the PC by going to BIOS first then closing it. From there it always boots normally to Windows with no problems.
Dumps (from WhoCrashed):
On Fri 11/13/2020 1:30:10 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\111320-19156-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x23994)
Bugcheck code: 0xA (0x5BC0, 0xFF, 0xCC, 0xFFFFF8032C012C27)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Fri 11/13/2020 1:11:14 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\111320-19031-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C3B20)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80026242B19, 0xFFFFB988ED316D40, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 11/12/2020 10:28:35 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\111220-11234-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C3B20)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF807545CBA07, 0xFFFFEC84A704DDF8, 0xFFFFD981E40D1930)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 11/12/2020 8:10:40 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\111220-40968-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2CE0)
Bugcheck code: 0xFC (0xFFFFF8007A600017, 0x80000007AE6E6829, 0xFFFFF90F4DB2EB60, 0x2)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an attempt was made to execute non-executable memory.
This may be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. Memory corruption can also occur because of overheating (thermal issue). There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 11/12/2020 7:59:44 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\111220-12156-01.dmp
This was probably caused by the following module: dxgmms2.sys (0xFFFFF8011DFE5A48)
Bugcheck code: 0xD1 (0x10, 0x2, 0x0, 0xFFFFF8011DFE5A48)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\dxgmms2.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Tue 11/10/2020 6:40:27 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\111020-18843-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF8061E51D705)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8061E51D705, 0xFFFF9F871E1169A0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.
On Mon 11/9/2020 6:06:19 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\110920-22343-01.dmp
This was probably caused by the following module: cfosspeed6.sys (0xFFFFF8062A26E549)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8062A26E549, 0xFFFFEE0273B66E18, 0xFFFFEE0273B66660)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\cfosspeed6.sys
product: cFosSpeed Driver
company: cFos Software GmbH
description: cFosSpeed Driver
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: cfosspeed6.sys (cFosSpeed Driver, cFos Software GmbH).
Google query: cfosspeed6.sys cFos Software GmbH SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
On Mon 11/9/2020 5:53:26 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\110920-17500-01.dmp
This was probably caused by the following module: hidclass.sys (0xFFFFF80055C0609F)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80055C0609F, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\hidclass.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hid Class Library
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Mon 11/9/2020 5:18:48 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\110920-20265-01.dmp
This was probably caused by the following module: cfosspeed6.sys (0xFFFFF8026BB8E505)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8026BB8E505, 0xFFFFFE8FFD5FEE18, 0xFFFFFE8FFD5FE660)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\cfosspeed6.sys
product: cFosSpeed Driver
company: cFos Software GmbH
description: cFosSpeed Driver
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: cfosspeed6.sys (cFosSpeed Driver, cFos Software GmbH).
Google query: cfosspeed6.sys cFos Software GmbH SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
On Mon 11/9/2020 5:13:29 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\110920-23859-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF8014F51D705)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8014F51D705, 0xFFFFF0881948E9A0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.
Continue reading...