H
henriklöndahl
I recently switched to a Asus rog strix z390-f motherboard after having problems with booting on my old one. Now I've been getting random bsod's nearly everytime i play a game. Descriptions from whocrashed:
System Information (local)
Computer name: DESKTOP-U3TJNO9
Windows version: Windows 10 , 10.0, build: 19041
Windows dir: C:\WINDOWS
Hardware: ASUSTeK COMPUTER INC., ROG STRIX Z390-F GAMING
CPU: GenuineIntel Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz Intel8664, level: 6
12 logical processors, active mask: 4095
RAM: 34266963968 bytes (31.9GB)
Crash Dump Analysis
Crash dumps are enabled on your computer.
Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump
On Fri 7/31/2020 2:11:37 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\073120-5046-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3DDB60)
Bugcheck code: 0xEF (0xFFFF81876CC17140, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
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 critical system process died.
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 Fri 7/31/2020 2:10:03 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\073120-5359-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3DDB60)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8075D425A38, 0xFFFFB880040E68B0, 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.
Crash dumps:
Continue reading...
System Information (local)
Computer name: DESKTOP-U3TJNO9
Windows version: Windows 10 , 10.0, build: 19041
Windows dir: C:\WINDOWS
Hardware: ASUSTeK COMPUTER INC., ROG STRIX Z390-F GAMING
CPU: GenuineIntel Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz Intel8664, level: 6
12 logical processors, active mask: 4095
RAM: 34266963968 bytes (31.9GB)
Crash Dump Analysis
Crash dumps are enabled on your computer.
Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump
On Fri 7/31/2020 2:11:37 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\073120-5046-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3DDB60)
Bugcheck code: 0xEF (0xFFFF81876CC17140, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
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 critical system process died.
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 Fri 7/31/2020 2:10:03 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\073120-5359-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3DDB60)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8075D425A38, 0xFFFFB880040E68B0, 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.
Crash dumps:
Continue reading...