MEMORY_CORRUPTION_ONE_BIT

Question

I just built my new PC and I consistently keep getting a BSOD with different error codes, I was wondering what the cause of this could be. below is my Windbg error codes and build. I do not know if this is hardware, software, what tests I need to do, or what a solution is. (had to remove some repeating code of the long sections as it was too long)

Ryzen 5500

RTX 3060

Corsair Vengeance 2x 8GB

Western Digital SN570 M.2

MSI B550 Tomahawk

Samsung 870 SATA hardrive

RM 650X Gold

Microsoft (R) Windows Debugger Version 10.0.25136.1001 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\WINDOWS\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff807`36e00000 PsLoadedModuleList = 0xfffff807`37a2a2b0
Debug session time: Sat Jul  2 21:24:31.879 2022 (UTC - 7:00)
System Uptime: 0 days 0:59:59.475
Loading Kernel Symbols
...............................................................
................................................................
...............................................
Loading User Symbols

Loading unloaded module list
..........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff807`371f7dd0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffff807`3c671b20=0000000000000139
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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: 0000000000000002, Stack cookie instrumentation code detected a stack-based
buffer overrun.
Arg2: fffff8073c671e40, Address of the trap frame for the exception that caused the BugCheck
Arg3: fffff8073c671d98, Address of the exception record for the exception that caused the BugCheck
Arg4: 0000000000000000, Reserved

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

Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nvmdig.inf_amd64_4a922d3e93437ff6\nvlddmkm.sys, Win32 error 0n2

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3859

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 19345

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

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

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x139

    Key  : Bugcheck.Code.KiBugCheckData
    Value: 0x139

    Key  : Bugcheck.Code.Register
    Value: 0x139

    Key  : FailFast.Name
    Value: STACK_COOKIE_CHECK_FAILURE

    Key  : FailFast.Type
    Value: 2

    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

FILE_IN_CAB:  MEMORY.DMP

BUGCHECK_CODE:  139

BUGCHECK_P1: 2

BUGCHECK_P2: fffff8073c671e40

BUGCHECK_P3: fffff8073c671d98

BUGCHECK_P4: 0

TRAP_FRAME:  fffff8073c671e40 -- (.trap 0xfffff8073c671e40)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffff23033eb07f06 rbx=0000000000000000 rcx=0000000000000002
rdx=ffffb504def28ca0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80748aa7775 rsp=fffff8073c671fd8 rbp=fffff8073c672061
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
r11=ffffb504d128c5a0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz ac po nc
dxgmms2!_report_gsfailure+0x5:
fffff807`48aa7775 cd29            int     29h
Resetting default scope

EXCEPTION_RECORD:  fffff8073c671d98 -- (.exr 0xfffff8073c671d98)
ExceptionAddress: fffff80748aa7775 (dxgmms2!_report_gsfailure+0x0000000000000005)
   ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
  ExceptionFlags: 00000001
NumberParameters: 1
   Parameter[0]: 0000000000000002
Subcode: 0x2 FAST_FAIL_STACK_COOKIE_CHECK_FAILURE 

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 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:  0000000000000002

EXCEPTION_STR:  0xc0000409

STACK_TEXT:  
fffff807`3c671b18 fffff807`37209d69     : 00000000`00000139 00000000`00000002 fffff807`3c671e40 fffff807`3c671d98 : nt!KeBugCheckEx
fffff807`3c671b20 fffff807`3720a190     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff807`3c671c60 fffff807`37208523     : 00000000`00000000 00000000`00000000 fffff807`48ad44b0 ffffb504`d9850000 : nt!KiFastFailDispatch+0xd0
fffff807`3c671e40 fffff807`48aa7775     : fffff807`48abe6e2 00000000`00000000 00000000`00000000 fffff807`00000004 : nt!KiRaiseSecurityCheckFailure+0x323
fffff807`3c671fd8 fffff807`48abe6e2     : 00000000`00000000 00000000`00000000 fffff807`00000004 fffff807`3c672080 : dxgmms2!_report_gsfailure+0x5
fffff807`3c671fe0 fffff807`48aadbfa     : 00000000`00000000 00000000`00989680 ffffb504`e60f6320 ffffb504`d9977000 : dxgmms2!McTemplateK0pqxxxx_EtwWriteTransfer+0xae
fffff807`3c6720a0 fffff807`48a99763     : ffffb504`0000000a fffff807`3c672260 ffffb504`00003200 00000000`00000001 : dxgmms2!VidSchiUpdateLastCompletedPresentTimestamp+0x119fa
fffff807`3c672160 fffff807`48a98acc     : ffffb504`d9979602 fffff807`00000001 ffffb504`00000000 ffffb504`00000000 : dxgmms2!VidSchiProcessCompletedQueuePacketInternal+0x8f3
fffff807`3c672300 fffff807`48a95af5     : ffffb504`d99e1a02 00000000`00000a68 00000000`00000001 fffff807`00000001 : dxgmms2!VidSchiProcessDpcCompletedPacket+0x70c
fffff807`3c672460 fffff807`47cdd5d1     : fffff807`3c672559 00000000`00000000 ffffb504`d6575520 00000bd1`37e13598 : dxgmms2!VidSchDdiNotifyDpc+0x225
fffff807`3c672510 fffff807`4bad28f9     : ffffb504`d65a9030 00000000`00000000 ffffb504`d65a9030 ffffb504`d6572000 : dxgkrnl!DxgNotifyDpcCB+0x91
fffff807`3c6725c0 fffff807`4c2c5cc3     : fffff807`4bad287e ffffb504`d6572000 00000000`00000000 00000000`00000000 : nvlddmkm+0x628f9
fffff807`3c672650 fffff807`4c2c5f1f     : fffff807`4c2c5c5b ffffb504`d6572000 ffffb504`d6572000 ffffb504`d6575520 : nvlddmkm+0x855cc3
fffff807`3c6726e0 fffff807`4c2c525c     : ffffb504`d66b2000 00000000`00000000 ffffa380`363f7470 ffffb504`d65a96e8 : nvlddmkm+0x855f1f
fffff807`3c672710 fffff807`4bae224f     : ffffb504`d6572000 00000000`00000000 ffffb504`d6575520 ffffb504`d65754e0 : nvlddmkm+0x85525c
fffff807`3c672740 fffff807`47ce42e6     : fffff807`4bae21c4 ffffb504`d65a9180 fffff807`3c672920 fffff807`3c672ae0 : nvlddmkm+0x7224f
fffff807`3c6727d0 fffff807`370a181e     : fffff807`3454e240 ffffb504`cfa75000 fffff807`3454b180 fffff807`00000002 : dxgkrnl!DpiFdoDpcForIsr+0x66
fffff807`3c672820 fffff807`370a0b04     : 00000000`00000000 fffff807`370e4535 00000000`00140001 00000000`00000000 : nt!KiExecuteAllDpcs+0x30e
fffff807`3c672990 fffff807`371fb93e     : 00000000`00000000 fffff807`3454b180 fffff807`37b27a00 ffffb504`e52b4080 : nt!KiRetireDpcList+0x1f4
fffff807`3c672c20 00000000`00000000     : fffff807`3c673000 fffff807`3c66c000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e

CHKIMG_EXTENSION: !chkimg -lo 50 -d !dxgmms2

    fffff80748abe6d8 - dxgmms2!McTemplateK0pqxxxx_EtwWriteTransfer+a4
[ 4d:45 ]
Page 22544d not present in the dump file. Type ".hh dbgerr004" for details
Page 39bc4f not present in the dump file. Type ".hh dbgerr004" for details
Page 3dba50 not present in the dump file. Type ".hh dbgerr004" for details
Page 3fae51 not present in the dump file. Type ".hh dbgerr004" for details
Page 3e3154 not present in the dump file. Type ".hh dbgerr004" for details
Page 358d55 not present in the dump file. Type ".hh dbgerr004" for details
Page 38b756 not present in the dump file. Type ".hh dbgerr004" for details
Page 239257 not present in the dump file. Type ".hh dbgerr004" for details
1 error : !dxgmms2 (fffff80748abe6d8)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

MEMORY_CORRUPTOR:  ONE_BIT

STACK_COMMAND:  .cxr; .ecxr ; kb

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {e3faf315-c3d0-81db-819a-6c43d23c63a7}

Followup:     memory_corruption
--------

Answer 1

I tried that ddu and it seemed to be working for a while but then my PC crashed again, no blue screen this time just restarted. Do you think if I completely format my hardrives this could fix the issue? here is the link to the google drive again with the new minidump copied into it but 3 files it said were unreadable for google drive so I hope this still works.

https://drive.google.com/drive/folders/1eKhqNxlmbcxpcsIeHJCqNbaqhaJyxuSr?usp=sharing

Answer 2

Hi Brandon,

Thanks for sharing the minidump files and sorry for the late reply as I was offline.

The minidump files indicate nvlddmkm.sys file as a cause of the BSOD which is related to Nvidia Graphics card driver.

If you do have an Nvidia graphics card installed on your computer, try to uninstall its driver completely using this DDU free utility, then download/install the latest graphics card driver or a driver that is compatible with your computer from the manufacturer's official website:

https://www.guru3d.com/files-details/display-dr...

Please let me know if you need further assistance and keep me updated.

____________________________________________________________

Standard Disclaimer: There are links to non-Microsoft websites. The pages appear to be providing accurate, safe information. Watch out for ads on the sites that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the sites before you decide to download and install it.

Answer 3

Hey Dyari, I was wondering if there was an update on what the solution could be?

Answer 4

here is the link to the google drive folder copy of my minidump folder.

https://drive.google.com/drive/folders/1eKhqNxlmbcxpcsIeHJCqNbaqhaJyxuSr?usp=sharing

Answer 5

Hi Brandon,

I'm Dyari. Thanks for reaching out. I will be happy to assist you in this regard.

Kindly check C:\Windows\Minidump and copy available minidump files to the desktop then share them via One Drive or Google Drive in order to be analyzed and indicate which file is causing the crash.

Regards,