Multiple BSOD's after Windows 10 Clean re-installation

  • Thread starter Thread starter KeithThomasG
  • Start date Start date
K

KeithThomasG

Guest
Hey everyone! I'm in a bit of a hiccup as my recent Windows 10 re-installation gifted me with a bunch of BSOD errors. They seemingly occur randomly (idle or while browsing).


Note: I've encountered a BSOD after installation when it booted for the first time.


My Build:

Operating System: Windows 10 Pro 64-bit (10.0, Build 19041) (19041.vb_release.191206-1406)

Language: English (Regional Setting: English)

System Manufacturer: Micro-Star International Co., Ltd.

System Model: MS-7B89

BIOS: 2.80 (type: UEFI)

Processor: AMD Ryzen 5 3600 6-Core Processor (12 CPUs), ~3.6GHz

Memory: 16384MB RAM

Available OS Memory: 16334MB RAM

Page File: 8147MB used, 11131MB available



Here's a bunch of the BSOD codes:


On Sat 01/08/2020 2:08:46 am your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\080120-11593-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3DDB60)
Bugcheck code: 0xD1 (0x0, 0xFF, 0x0, 0x0)
Error: DRIVER_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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 01/08/2020 1:50:26 am your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\080120-11640-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3DDB60)
Bugcheck code: 0x192 (0xFFFFA80DA8321080, 0xFFFFBE070145AD00, 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 01/08/2020 1:27:49 am your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\080120-11468-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3DDB60)
Bugcheck code: 0xA (0xFFFFA58F01000000, 0x2, 0x0, 0xFFFFF800783E4F32)
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 Sat 01/08/2020 2:08:46 am your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!setjmpex+0x8179)
Bugcheck code: 0xD1 (0x0, 0xFF, 0x0, 0x0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 31/07/2020 11:56:14 pm your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\073120-12031-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3DDB60)
Bugcheck code: 0x192 (0xFFFFB98124032080, 0xFFFFE08E95D2EE30, 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 Fri 31/07/2020 11:28:49 pm your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\073120-11781-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3DDB60)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80464E27581, 0xFFFFC080FF6D2920, 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.


Continue reading...
 

Similar threads

Back
Top