LOTS OF BSODS Lately out of nowhere While Playing Fifa21

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 Wed 10/21/2020 6:31:47 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\102120-25562-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F45A0)
Bugcheck code: 0xF7 (0xFFFFB00711C5F1E8, 0x25CCE2BE79E9, 0xFFFFDA331D418616, 0x0)
Error: DRIVER_OVERRAN_STACK_BUFFER
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 driver has overrun a stack-based buffer.
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 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.

Quote:
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.

Quote:
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.

Quote:
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
Quote:

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?

See - BSOD - Posting Instructions

MrPepka here is the v2 collector dump.

Hi

Ztruker thanks for the reply,

i did not have the Intel Rapid Storage Techology up to date but i did have the Chipest drivers up to date.

kind regards
donixo

Got another bluescreen with different name

here is the dumpfile
Dropbox - 102520-33875-01.dmp - Simplify your life


Event Viewer showed this before shutdown.
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

The description for Event ID 32 from source e1dexpress cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

Intel(R) Ethernet Connection (7) I219-V

The message resource is present but the message was not found in the message table

Unistalled the Lightningservice was used by AURA, that changes the Lights for the Fans.

but looking closer to the Dump file i got this


SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c000001d, Exception code that caused the bugcheck
Arg2: fffff8072fb22719, Address of the instruction which caused the bugcheck
Arg3: ffffe501a0d35920, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Debugging Details:
------------------


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2124

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on ELION

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 6723

Key : Analysis.Memory.CommitPeak.Mb
Value: 91

Key : Analysis.System
Value: CreateObject

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key : WER.OS.Version
Value: 10.0.19041.1


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE: 3b

BUGCHECK_P1: c000001d

BUGCHECK_P2: fffff8072fb22719

BUGCHECK_P3: ffffe501a0d35920

BUGCHECK_P4: 0

CONTEXT: ffffe501a0d35920 -- (.cxr 0xffffe501a0d35920)
rax=0000000000000001 rbx=ffff8a896bfa6590 rcx=ffff8a8979a03050
rdx=0000000000000000 rsi=ffff8a8979a03080 rdi=ffff8a8978e9e870
rip=fffff8072fb22719 rsp=ffff820089fbed20 rbp=ffff820089fbedc8
r8=0000000000000004 r9=0000000000000000 r10=ffff8a8979a03080
r11=ffff820089fbede8 r12=0000000000000002 r13=000000000000000b
r14=0000000000000001 r15=000000000000ff02
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050282
nt!ObpIncrPointerCount+0x9:
fffff807`2fb22719 f0480fc101 lock xadd qword ptr [rcx],rax ds:002b:ffff8a89`79a03050=0000000000036c28
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: NVIDIA Share.exe

BAD_STACK_POINTER: ffffe501a0d35018

STACK_TEXT:
ffff8200`89fbed20 fffff807`2fac1632 : ffff8a89`6bfa6590 ffff8a89`79a03080 ffff8a89`78e9e870 00000000`00000000 : nt!ObpIncrPointerCount+0x9
ffff8200`89fbed60 fffff807`2fadd7e7 : 00000000`00000000 00000000`00000002 00000072`095df500 fffff807`00000004 : nt!ExpApplyPriorityBoost+0x4a2
ffff8200`89fbedf0 fffff807`2fadc77c : ffffcc3a`e1c39480 00000000`00000001 ffff8200`86df7540 ffff8a89`6cb020c0 : nt!ExpAcquireResourceExclusiveLite+0x597
ffff8200`89fbeec0 ffffcc3a`e144eeb5 : 00000000`00000000 00000000`00989680 00000000`00000001 ffff8a89`6c18c8b0 : nt!ExEnterCriticalRegionAndAcquireResourceExclusive+0x3c
ffff8200`89fbef00 ffffcc3a`e1c676a3 : 00000000`00000000 00000000`00000000 00000072`095df4d8 00000000`00000000 : win32kbase!EnterCrit+0x85
ffff8200`89fbf020 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32kfull!NtUserMsgWaitForMultipleObjectsEx+0x43


SYMBOL_NAME: win32kbase!EnterCrit+85

MODULE_NAME: win32kbase

IMAGE_NAME: win32kbase.sys

IMAGE_VERSION: 10.0.19041.571

STACK_COMMAND: .cxr 0xffffe501a0d35920 ; kb

BUCKET_ID_FUNC_OFFSET: 85

FAILURE_BUCKET_ID: 0x3B_c000001d_STACKPTR_ERROR_win32kbase!EnterCrit

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {d1cba108-7392-867f-f616-f7568b98266c}

Followup: MachineOwner
---------