random bsods???

Junt Polt 0 Reputation points
2026-09-14T23:51:30.85+00:00

so i had ALOT of problems with the new nvidia drivers that were released september 9th, ended up having to completley reset my pc and it took care of the bsods for a few days and now they are back, i have brand new ram 32gb ddr4, gpu isa 3060 and my cpu is A AMD RYZEN 5 3600, i did test with chkdsk and it got done very quickly, estimated time was 50 minutes it was done in about 25-30, no errors were detected, i tested with prime95 i ran it for like 10 minutes but shut it off because the cpu cores tempratures were really close to 95 celsius, i have yet to test my ram with memtest86 but i have 3 with windows memory diagnostics and none of them showed anything, my mother board is a asus prime b550-plus ac-hes, im running windows 10 home 10.0.19045 build 19045, im not sure what other info i should post but thats that

KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure.  The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: ffff8802676b57d0, Address of the trap frame for the exception that caused the BugCheck
Arg3: ffff8802676b5728, Address of the exception record for the exception that caused the BugCheck
Arg4: 0000000000000000, Reserved

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1765

    Key  : Analysis.Elapsed.mSec
    Value: 2644

    Key  : Analysis.IO.Other.Mb
    Value: 0

    Key  : Analysis.IO.Read.Mb
    Value: 1

    Key  : Analysis.IO.Write.Mb
    Value: 0

    Key  : Analysis.Init.CPU.mSec
    Value: 359

    Key  : Analysis.Init.Elapsed.mSec
    Value: 2153

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.29617.1000

    Key  : Analysis.Version.Description
    Value: 10.2604.29.1 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2604.29.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x139

    Key  : Bugcheck.Code.TargetModel
    Value: 0x139

    Key  : FailFast.Name
    Value: CORRUPT_LIST_ENTRY

    Key  : FailFast.Type
    Value: 3

    Key  : Failure.Bucket
    Value: 0x139_3_CORRUPT_LIST_ENTRY_KTIMER_LIST_CORRUPTION_nt!KiRemoveEntryTimer

    Key  : Failure.Exception.Code
    Value: 0xc0000409

    Key  : Failure.Exception.Record
    Value: 0xffff8802676b5728

    Key  : Failure.Hash
    Value: {5cf1a79f-75db-1c81-82ec-116a11522249}

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1

    Key  : WER.System.BIOSRevision
    Value: 5.17.0.0


BUGCHECK_CODE:  139

BUGCHECK_P1: 3

BUGCHECK_P2: ffff8802676b57d0

BUGCHECK_P3: ffff8802676b5728

BUGCHECK_P4: 0

FILE_IN_CAB:  091426-13390-01.dmp

FAULTING_THREAD:  ffffbe00bedeb340

TRAP_FRAME:  ffff8802676b57d0 -- (.trap 0xffff8802676b57d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff80228c7f8c8 rbx=0000000000000000 rcx=0000000000000003
rdx=ffffd682747761a0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8022b82fbef rsp=ffff8802676b5960 rbp=0000000000000060
 r8=0000000000000001  r9=ffff8802676b5a58 r10=fffff80228c7cac0
r11=000000f82982ee80 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!KiRemoveEntryTimer+0x1e8aef:
fffff802`2b82fbef cd29            int     29h
Resetting default scope

EXCEPTION_RECORD:  ffff8802676b5728 -- (.exr 0xffff8802676b5728)
ExceptionAddress: fffff8022b82fbef (nt!KiRemoveEntryTimer+0x00000000001e8aef)
   ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
  ExceptionFlags: 00000001
NumberParameters: 1
   Parameter[0]: 0000000000000003
Subcode: 0x3 FAST_FAIL_CORRUPT_LIST_ENTRY 

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1 (!blackboxwinlogon) (!blackboxwinlogonnotify)


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

ERROR_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.

EXCEPTION_CODE_STR:  c0000409

EXCEPTION_PARAMETER1:  0000000000000003

EXCEPTION_STR:  0xc0000409

STACK_TEXT:  
ffff8802`676b54a8 fffff802`2b811da9     : 00000000`00000139 00000000`00000003 ffff8802`676b57d0 ffff8802`676b5728 : nt!KeBugCheckEx
ffff8802`676b54b0 fffff802`2b812350     : 00000000`00040046 fffff802`2b62485e 00000000`00000000 fffff802`2b70bf5d : nt!KiBugCheckDispatch+0x69
ffff8802`676b55f0 fffff802`2b8101f2     : 00000000`00000000 00000000`00000000 00000000`00000002 00000000`00989680 : nt!KiFastFailDispatch+0xd0
ffff8802`676b57d0 fffff802`2b82fbef     : ffffd682`61f45050 000000f8`2982ef83 ffffffff`00000001 ffffd682`61f45238 : nt!KiRaiseSecurityCheckFailure+0x332
ffff8802`676b5960 fffff802`2b64675a     : 00000000`00000000 00000000`00000000 00000000`00140001 ffff8802`676b5a58 : nt!KiRemoveEntryTimer+0x1e8aef
ffff8802`676b59d0 fffff802`2b8020be     : ffffffff`00000000 ffffbe00`bede0180 ffffbe00`bedeb340 ffffd682`817e9540 : nt!KiRetireDpcList+0x73a
ffff8802`676b5c60 00000000`00000000     : ffff8802`676b6000 ffff8802`676b0000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e


SYMBOL_NAME:  nt!KiRemoveEntryTimer+1e8aef

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.6456

STACK_COMMAND: .process /r /p 0xfffff8022c124a00; .thread /r /p 0xffffbe00bedeb340 ; kb

BUCKET_ID_FUNC_OFFSET:  1e8aef

FAILURE_BUCKET_ID:  0x139_3_CORRUPT_LIST_ENTRY_KTIMER_LIST_CORRUPTION_nt!KiRemoveEntryTimer

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {5cf1a79f-75db-1c81-82ec-116a11522249}

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

this bsod happened last night after i closed gears of war 4
PAGE_FAULT_IN_NONPAGED_AREA (50)

Invalid system memory was referenced. This cannot be protected by try-except.

Typically the address is just plain bad or it is pointing at freed memory.

Arguments:

Arg1: ffffbf0700000193, memory referenced.

Arg2: 0000000000000000, X64: bit 0 set if the fault was due to a not-present PTE.

bit 1 is set if the fault was due to a write, clear if a read.

bit 3 is set if the processor decided the fault was due to a corrupted PTE.

bit 4 is set if the fault was due to attempted execute of a no-execute PTE.

- ARM64: bit 1 is set if the fault was due to a write, clear if a read.

bit 3 is set if the fault was due to attempted execute of a no-execute PTE.
```Arg3: fffff80414bf2e49, If non-zero, the instruction address which referenced the bad memory

address.


Debugging Details:

------------------

KEY_VALUES_STRING: 1

```scala
Key  : AV.PTE

Value: Invalid

Key  : AV.Page.Virtual

Value: 0xffffbf0700000000

Key  : AV.Type

Value: Read

Key  : Analysis.CPU.mSec

Value: 1312

Key  : Analysis.Elapsed.mSec

Value: 1603

Key  : Analysis.IO.Other.Mb

Value: 0

Key  : Analysis.IO.Read.Mb

Value: 1

Key  : Analysis.IO.Write.Mb

Value: 0

Key  : Analysis.Init.CPU.mSec

Value: 390

Key  : Analysis.Init.Elapsed.mSec

Value: 2408

Key  : Analysis.Memory.CommitPeak.Mb

Value: 80

Key  : Analysis.Version.DbgEng

Value: 10.0.29617.1000

Key  : Analysis.Version.Description

Value: 10.2604.29.1 amd64fre

Key  : Analysis.Version.Ext

Value: 1.2604.29.1

Key  : Bugcheck.Code.LegacyAPI

Value: 0x50

Key  : Bugcheck.Code.TargetModel

Value: 0x50

Key  : Failure.Bucket

Value: AV_Ntfs!NtfsProcessUsnRecordsForCommit

Key  : Failure.Exception.IP.Address

Value: 0xfffff80414bf2e49

Key  : Failure.Exception.IP.Module

Value: Ntfs

Key  : Failure.Exception.IP.Offset

Value: 0x12e49

Key  : Failure.Hash

Value: {8118c9c0-892c-8fef-d176-fe51f8c17c54}

Key  : Faulting.IP.Type

Value: Paged

Key  : WER.OS.Branch

Value: vb_release

Key  : WER.OS.Version

Value: 10.0.19041.1

Key  : WER.System.BIOSRevision

Value: 5.17.0.0
```BUGCHECK_CODE:  50

BUGCHECK_P1: ffffbf0700000193

BUGCHECK_P2: 0

BUGCHECK_P3: fffff80414bf2e49

BUGCHECK_P4: 2

FILE_IN_CAB:  091426-24703-01.dmp

FAULTING_THREAD:  ffffa783b8b82080

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffbf0700000193

READ_ADDRESS: fffff804102fb390: Unable to get MiVisibleState

 ffffbf0700000193 

MM_INTERNAL_CODE:  2

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1 (!blackboxwinlogon) (!blackboxwinlogonnotify)

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  opera.exe

IP_IN_PAGED_CODE: 

Ntfs!NtfsProcessUsnRecordsForCommit+179

fffff804`14bf2e49 8b8190000000    mov     eax,dword ptr [rcx+90h]

STACK_TEXT:  

ffffee0e`453bef08 fffff804`0fa48b23     : 00000000`00000050 ffffbf07`00000193 00000000`00000000 ffffee0e`453bf1b0 : nt!KeBugCheckEx

ffffee0e`453bef10 fffff804`0f80d450     : 00000000`00000000 00000000`00000000 ffffee0e`453bf230 00000000`00000000 : nt!MiSystemFault+0x1b70a3

ffffee0e`453bf010 fffff804`0fa0d66d     : 00000000`00000000 ffffd408`ffffffff 00000001`2035d2d5 00000000`00000000 : nt!MmAccessFault+0x400

ffffee0e`453bf1b0 fffff804`14bf2e49     : ffffa783`b8a990f8 ffffa783`00000002 00000000`00000000 00000000`00000028 : nt!KiPageFault+0x36d

ffffee0e`453bf340 fffff804`14cead46     : 00000001`2035d2d5 00000000`00000008 ffffa783`a4b64180 ffffa783`b8a99018 : Ntfs!NtfsProcessUsnRecordsForCommit+0x179

ffffee0e`453bf370 fffff804`14cc9578     : ffffbf07`167eeb60 00000000`00000008 ffffa783`b8a99018 ffffbf07`2b13be30 : Ntfs!NtfsCommitCurrentTransaction+0x276

ffffee0e`453bf410 fffff804`14cc89e9     : ffffa783`b8a99018 ffffa783`b8a99018 ffffbf07`167eeb60 ffffa783`9fff3601 : Ntfs!NtfsSetEndOfFileInfo+0x608

ffffee0e`453bf610 fffff804`14cc7b21     : ffffa783`b8a99018 ffffa783`bcb34a20 ffffa783`bcb34a00 00000000`00000000 : Ntfs!NtfsCommonSetInformation+0xd19

ffffee0e`453bf6e0 fffff804`0f8d21c5     : ffffa783`bcb34a20 ffffa783`bcb34a20 ffffa783`b8a99018 ffffee0e`453c0000 : Ntfs!NtfsFsdSetInformation+0x151

ffffee0e`453bf7b0 fffff804`0eba710f     : 00000000`00000007 00000000`00000000 ffffa783`bdec2580 00000000`00000208 : nt!IofCallDriver+0x55

ffffee0e`453bf7f0 fffff804`0eba4a43     : ffffee0e`453bf880 00000000`00000008 ffffa783`b7ce70c0 fffff804`0ffb418e : FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x28f

ffffee0e`453bf860 fffff804`0f8d21c5     : ffffa783`bcb34e50 fffff804`0f8d23a2 00000000`00000001 fffff804`0fc3e30e : FLTMGR!FltpDispatch+0xa3

ffffee0e`453bf8c0 fffff804`0f82b740     : ffffa783`bdec2580 ffffa783`bcb34a20 00000000`00000014 ffffa783`bdec2530 : nt!IofCallDriver+0x55

ffffee0e`453bf900 fffff804`0f8d35ce     : ffffee0e`453bfb80 ffffa783`bcb34e50 ffffa783`bcb34a20 00000000`00000000 : nt!IopCallDriverReference+0xd0

ffffee0e`453bf970 fffff804`0fa11508     : 00000000`00000df0 00000032`763ff1b0 00000032`763ff1e0 fffff804`00000008 : nt!NtSetInformationFile+0xbae

ffffee0e`453bfa90 00007fff`4a8cda84     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28

00000032`763ff178 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`4a8cda84

SYMBOL_NAME:  Ntfs!NtfsProcessUsnRecordsForCommit+179

MODULE_NAME: Ntfs

IMAGE_NAME:  Ntfs.sys

IMAGE_VERSION:  10.0.19041.6456

STACK_COMMAND: .process /r /p 0xffffa783b7ce70c0; .thread /r /p 0xffffa783b8b82080 ; kb

BUCKET_ID_FUNC_OFFSET:  179

FAILURE_BUCKET_ID:  AV_Ntfs!NtfsProcessUsnRecordsForCommit

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {8118c9c0-892c-8fef-d176-fe51f8c17c54}

Followup:     MachineOwner

---------

this one was randomly i dont even remember what i was doing i went to go take a picture of my dog came back and it was blue screened


```yaml
DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
	DISPATCH_LEVEL or above.
Arg2: 0000000000001e00, The watchdog period (in ticks).
Arg3: fffff80608cfb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
	additional information regarding the cumulative timeout
Arg4: 0000000000000000

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1453

    Key  : Analysis.Elapsed.mSec
    Value: 2198

    Key  : Analysis.IO.Other.Mb
    Value: 0

    Key  : Analysis.IO.Read.Mb
    Value: 1

    Key  : Analysis.IO.Write.Mb
    Value: 0

    Key  : Analysis.Init.CPU.mSec
    Value: 406

    Key  : Analysis.Init.Elapsed.mSec
    Value: 1887

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.29617.1000

    Key  : Analysis.Version.Description
    Value: 10.2604.29.1 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2604.29.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x133

    Key  : Bugcheck.Code.TargetModel
    Value: 0x133

    Key  : Failure.Bucket
    Value: 0x133_ISR_nt!HalPerformEndOfInterrupt

    Key  : Failure.Hash
    Value: {c6ddb0fb-7956-8f06-76ab-edacd87ecafb}

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1

    Key  : WER.System.BIOSRevision
    Value: 5.17.0.0


BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff80608cfb320

BUGCHECK_P4: 0

FILE_IN_CAB:  091426-14703-01.dmp

FAULTING_THREAD:  ffffa283eeac3300

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

TRAP_FRAME:  ffff870957daa800 -- (.trap 0xffff870957daa800)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000006cfc306d rbx=0000000000000000 rcx=ffff870957daaa48
rdx=ffffa283eeac3440 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8060824ac0c rsp=ffff870957daa998 rbp=ffff8c0170380180
 r8=0000000000000000  r9=0000000c7648c90f r10=0000fffff8060836
r11=ffff870957daaa38 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
nt!KeYieldProcessorEx+0x1c:
fffff806`0824ac0c c3              ret
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1 (!blackboxwinlogon) (!blackboxwinlogonnotify)


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  Crysis3Remastered.exe

STACK_TEXT:  
ffff8709`57daa7b0 fffff806`083ffeb4     : ffff8709`57daaa48 ffffa283`eeac3300 00000000`00000082 fffff806`083ffdf0 : nt!HalPerformEndOfInterrupt+0x1a
ffff8709`57daa7e0 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0xc4


SYMBOL_NAME:  nt!HalPerformEndOfInterrupt+1a

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.6456

STACK_COMMAND: .process /r /p 0xffffa283ee89a0c0; .thread /r /p 0xffffa283eeac3300 ; kb

BUCKET_ID_FUNC_OFFSET:  1a

FAILURE_BUCKET_ID:  0x133_ISR_nt!HalPerformEndOfInterrupt

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {c6ddb0fb-7956-8f06-76ab-edacd87ecafb}

Followup:     MachineOwner

this one happened while i was running crysis 3 i was only in the menu tbf it was on a crappy drive

Windows for home | Windows 10 | Performance and system failures
0 comments No comments

1 answer

Sort by: Most helpful
  1. Carl-L 21,565 Reputation points Microsoft External Staff Moderator
    2026-09-15T10:00:26.6533333+00:00

    Hello Junt Polt,

    Welcome to Microsoft Q&A forum.

    As I checked, the most likely cause of this is your RAM has been corrupted. Before we proceed, can you please try to run Memtest86 first and let me know if there are any errors? Also, can you please try to swap the RAM slot if possible and see if it helps?

    I'm waiting for your reply.

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.