LOTS OF BSODS Lately out of nowhere While Playing Fifa21

[Donix]

Hi,

lately ive been getting lots of bluescreen with a good Computer.
could really use some help here..

MYSPECS

BIOS VERSION: 1401
Windows 10 2004
PSU: EVGA SuperNOVA 850 G3, 850W
Ram: Corsair Vengeance RGB PRO DDR4 3600MHz 16GB[CMW16GX4M2C3600C18]
Apprently my RAMs arent added into the Support List for the Mobo for some reason.
no idea if that effects it
MOBO :ASUS ROG MAXIMUS XI FORMULA, S-1151
GPU: RTX 2080ti Founders Edition
CPU: i9 9900k
SSD: Samsung 970 EVO

Whocrashed DUMP

On Sun 10/18/2020 4:37:15 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\101820-25500-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F45A0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8061EC077F0, 0x0, 0xFFFFFFFFFFFFFFFF)
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 Sun 10/18/2020 2:00:44 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\101820-25062-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F45A0)
Bugcheck code: 0x1E (0xFFFFFFFF80000003, 0xFFFFF80614EC2F7F, 0x0, 0xFFFFF806152F1600)
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 Sat 10/17/2020 6:02:41 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\101720-25312-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F45A0)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFF85, 0x2, 0xFFFFF8065A2BD11B, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 10/17/2020 5:33:54 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\101720-25156-01.dmp
This was probably caused by the following module: hardware.sys (hardware)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80028ACEAA3, 0xFFFFC308E7546360, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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.
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: hardware.sys .
Google query: hardware.sys SYSTEM_SERVICE_EXCEPTION

On Fri 10/16/2020 8:06:55 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\101620-25406-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F45A0)
Bugcheck code: 0xA (0x43FD7299, 0x2, 0x1, 0xFFFFF80448C6478B)
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.

Event viewer
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001e (0xffffffffc0000005, 0xfffff8061ec077f0, 0x0000000000000000, 0xffffffffffffffff). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 46f367af-f3e7-43b7-a37f-916bf3b23d3e.

The programspecifik permission settings do not grant Lokal Starta permission for the COM Server application with CLSID
{7022A3B3-D004-4F52-AF11-E9E987FEE25F}
and APPID
{ADA41B3C-C6FD-4A08-8CC1-D6EFDE67BE7D}
to the user PC\PC SID (S-1-5-21-110143569-205071645-1149743838-1001) from address LocalHost (med LRPC) running in the application container Inte tillgänglig SID (Inte tillgänglig). This security permission can be modified using the Component Services administrative tool.

Found passthru disk: SCSI Port: 0, SCSI Bus: 1, SCSI Target: 0, PCIe SSD, 500107862016 bytes, Samsung SSD 970 EVO 500GB



Could really need some help here.
could this be a cause with latest nvidia drivers?

 

[Megahertz07]

If you have overclock, return to the defaults.
Win 7 and Win 10 requires different drivers.

Post a thread at BSOD Crashes and Debugging - Windows 10 Forums

 

[GiulianoB54]

Hey Donix, nobody likes BSOD while their playing and neither do I, let me help you. First, i need you to send the specific version of your windows. Also, the problem isn't because of your driver, ntoskrnl.exe is a windows file. It sounds like you have a similar problem to the problem that i have, and by the time, more and more people report about a similar issue. The bug caused by increasing the usage of the CPU and RAM. Increasing enough the usage will cause randomly(it can happen anytime) BSOD. The BSOD seems to be pretty random, but they all caused by the same file, ntoskrnl.exe. Freezes can also be occurred, but more rare. You might be suffering from the same issue, and that's why I have to know what version of windows you have. Also, try opening cmd.exe(administrator) and type "sfc /scannow"(without quotes)

 

[Donix]

Windows 10 Home 2004 OS BUILD 19041.572

 

[GiulianoB54]

Hello again Donix, it looks like you have the latest version of windows 10. There is indeed a high chance that you are affected by the bug i have told you about. Unfortunately, there is no fix right now.

 

[Donix]

Hello again Donix, it looks like you have the latest version of windows 10. There is indeed a high chance that you are affected by the bug i have told you about. Unfortunately, there is no fix right now.

What bug? so its a windows issue as i thought cus i rarely had any crashes with same volt same clock.. and the bluescreens were rare very rare

 

[Megahertz07]

You're on the wrong place.
This is Win 7 forums.

Post a thread at BSOD Crashes and Debugging - Windows 10 Forums