New build
ryzen 5 3600 in an msi b450 carbon pro ac mb with aio cooler (max 70 degrees with 30mins stress test)
2x 16gb oloy drr4 3200 rgb memory
sabrent 2tb nvme ssd
1080ti asus rog strix gpu
as title says keep getting random bsod with varying errors...sometimes when idle or during VR gaming
have displayed below report from WHOCRASHED
have tried a clean fresh install and updated ALL drivers inc amd chipset
no idea what issue is....sometimes can leave pc running all night without a bsod and sometimes it can bsod several times within an hour
i play mostly steam vr games and guaranteed it will crash within 30mins or less and sometimes crash to destop more frequently
Crash dumps are enabled on your computer.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Mon 07/12/2020 14:46:26 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\120720-5921-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5210)
Bugcheck code: 0x162 (0xFFFFD1072AF6B0C0, 0xFFFFD107228FF6A0, 0xFFFFFFFF, 0x0)
Error: KERNEL_AUTO_BOOST_INVALID_LOCK_RELEASE
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 lock tracked by AutoBoost was released by a thread that did not own the lock.
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 Mon 07/12/2020 14:46:26 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: fltmgr.sys (FLTMGR!FltDecodeParameters+0x1CAD)
Bugcheck code: 0x162 (0xFFFFD1072AF6B0C0, 0xFFFFD107228FF6A0, 0xFFFFFFFF, 0x0)
Error: KERNEL_AUTO_BOOST_INVALID_LOCK_RELEASE
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
Bug check description: This indicates that a lock tracked by AutoBoost was released by a thread that did not own the lock.
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 Sat 28/11/2020 12:56:00 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\112820-5984-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5210)
Bugcheck code: 0x192 (0xFFFFBF064663C080, 0xFFFFCF0F8F1058B8, 0x0, 0x0)
Error: KERNEL_AUTO_BOOST_LOCK_ACQUISITION_WITH_RAISED_IRQL
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 lock tracked by AutoBoost was acquired while executing at DISPATCH_LEVEL or above.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 28/11/2020 12:28:46 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\112820-5984-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5210)
Bugcheck code: 0x162 (0xFFFFC683BF8BD080, 0xFFFFC683C0936BB8, 0xFFFFFFFF, 0x0)
Error: KERNEL_AUTO_BOOST_INVALID_LOCK_RELEASE
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 lock tracked by AutoBoost was released by a thread that did not own the lock.
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 Sat 28/11/2020 03:11:43 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\112820-5906-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5210)
Bugcheck code: 0xA0 (0x107, 0xA, 0xFFFFB58C38DD5D70, 0x0)
Error: INTERNAL_POWER_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the power policy manager experienced a fatal error.
This is likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 27/11/2020 23:45:29 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\112720-6656-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5210)
Bugcheck code: 0xA (0x60020, 0x2, 0x0, 0xFFFFF8020E638FA0)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 27/11/2020 23:43:56 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\112720-5937-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5210)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8064D6EDEE1, 0xFFFFFE02CC3477C0, 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.
