BSOD fra helvete

[Gjest Slettet+512]

Hei. Bygde ny PC for et par uker siden. Plaget med BSOD jevnt og trutt. Har testet med andre RAM-brikker uten hell. BIOS er oppdatert. Måtte formatere hele dritten i går kveld siden BSOD kom i boot "BAD_SYSTEM_CONFIG_INFO". Etter formatering installerte jeg nyeste chipset drivere, Realtek LAN og Nvidia-drivere.

Noen som blir klok på dette her?

 

Quote

 System Information (local)  
Computer name: DESKTOP-L00Q5MG Windows version: Windows 10 , 10.0, build: 19041 Windows dir: C:\Windows Hardware: MS-7C84, Micro-Star International Co., Ltd., MAG X570 TOMAHAWK WIFI (MS-7C84) CPU: AuthenticAMD AMD Ryzen 7 3700X 8-Core Processor AMD8664, level: 23 16 logical processors, active mask: 65535 RAM: 34277810176 bytes (31.9GB)

 

Spoiler

 

Crash Dump Analysis  
Crash dumps are enabled on your computer.

Crash dump directories: 
C:\Windows C:\Windows\Minidump

On Fri 9/18/2020 9:25:51 AM your computer crashed or a problem was reported crash dump file: C:\Windows\Minidump\091820-6437-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x3F3EA0) Bugcheck code: 0xD1 (0x3, 0x2, 0x8, 0x3) 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  Fri 9/18/2020 9:25:51 AM your computer crashed or a problem was  reported
crash dump file: C:\Windows\MEMORY.DMP This was probably caused by the following module: afd.sys (afd+0x577A9) Bugcheck code: 0xD1 (0x3, 0x2, 0x8, 0x3) Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\drivers\afd.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: Ancillary Function Driver for WinSock 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  Thu 9/17/2020 12:13:40 PM your computer crashed or a problem was  reported
crash dump file: C:\Windows\Minidump\091720-7312-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x3F3EA0) Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF8046F0FA320) Error: DPC_WATCHDOG_VIOLATION file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (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 Thu 9/17/2020 2:58:04 AM your computer crashed or  a problem was reported
crash dump file: C:\Windows\Minidump\091720-6343-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x3F3EA0) Bugcheck code: 0x133 (0x1, 0x1E00, 0xFFFFF800190FA320, 0x0) Error: DPC_WATCHDOG_VIOLATION file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (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 Mon 9/21/2020 11:11:45 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\092120-6093-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F3EA0)
Bugcheck code: 0x1 (0x7FFCE586BE44, 0x0, 0xFFFF, 0xFFFFFD87D2ED8B80)
Error: APC_INDEX_MISMATCH
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 there has been a mismatch in the APC state index.
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 9/21/2020 11:11:45 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+0x8279)
Bugcheck code: 0x1 (0x7FFCE586BE44, 0x0, 0xFFFF, 0xFFFFFD87D2ED8B80)
Error: APC_INDEX_MISMATCH
Bug check description: This indicates that there has been a mismatch in the APC state index.
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 Tue 9/22/2020 9:20:34 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\092220-6171-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F3EA0)
Bugcheck code: 0x1 (0x7FFC6196BE44, 0x0, 0xFFFF, 0xFFFFA081A707DB80)
Error: APC_INDEX_MISMATCH
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 there has been a mismatch in the APC state index.
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 Tue 9/22/2020 9:20:34 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+0x8279)
Bugcheck code: 0x1 (0x7FFC6196BE44, 0x0, 0xFFFF, 0xFFFFA081A707DB80)
Error: APC_INDEX_MISMATCH
Bug check description: This indicates that there has been a mismatch in the APC state index.
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 9/21/2020 11:11:45 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\092120-6093-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F3EA0)
Bugcheck code: 0x1 (0x7FFCE586BE44, 0x0, 0xFFFF, 0xFFFFFD87D2ED8B80)
Error: APC_INDEX_MISMATCH
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 there has been a mismatch in the APC state index.
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 Tue 9/22/2020 11:20:53 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\092220-6421-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3FAC26)
Bugcheck code: 0x100000B8 (0xFFFF9A00AC00B440, 0xFFFF8387934CC080, 0x0, 0x0)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System

The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Tue 9/22/2020 11:20:53 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: win32kfull.sys (win32kfull+0x1544F2)
Bugcheck code: 0xB8 (0xFFFF9A00AC00B440, 0xFFFF8387934CC080, 0x0, 0x0)
Error: ATTEMPTED_SWITCH_FROM_DPC
file path: C:\Windows\system32\win32kfull.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Full/Desktop Win32k Kernel Driver
Bug check description: This indicates that an illegal operation was attempted by a delayed procedure call (DPC) routine.
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 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 9/22/2020 3:58:57 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\092220-6171-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F3EA0)
Bugcheck code: 0x18 (0x0, 0xFFFFCD0034468A00, 0x1, 0x77504630)
Error: REFERENCE_BY_POINTER
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 the reference count of an object is illegal for the current state of the object.
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 Tue 9/22/2020 3:58:57 PM 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!memset+0x6499C)
Bugcheck code: 0x18 (0x0, 0xFFFFCD0034468A00, 0x1, 0x77504630)
Error: REFERENCE_BY_POINTER
Bug check description: This indicates that the reference count of an object is illegal for the current state of the object.
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 Wed 9/23/2020 1:17:43 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\092320-6000-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F3EA0)
Bugcheck code: 0xA (0x24B, 0x2, 0x0, 0xFFFFF80342A0D411)
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 Wed 9/23/2020 1:17:43 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: afd.sys (afd+0x577A9)
Bugcheck code: 0xA (0x24B, 0x2, 0x0, 0xFFFFF80342A0D411)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\afd.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Ancillary Function Driver for WinSock
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 Wed 9/23/2020 10:02:18 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\092320-5937-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F3EA0)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF80330519522)
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 Wed 9/23/2020 10:02:18 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+0x8279)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF80330519522)
Error: IRQL_NOT_LESS_OR_EQUAL
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.