Share via

memory_corruption bsod

Anonymous
2023-12-15T03:14:11+00:00

Hello! i'am getting some random bsod's on my dell g15 ryzen version, and i can't see a pattern causing them. I appreciate the help, thanks

here's the last minidump: 

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041792, A corrupt PTE has been detected. Parameter 2 contains the address of
the PTE. Parameters 3/4 contain the low/high parts of the PTE.
Arg2: ffffd3bffeb3d930
Arg3: 0000000000000002
Arg4: 0000000000000000

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

*** WARNING: Check Image - Checksum mismatch - Dump: 0x20397e, File: 0x203a06 - C:\ProgramData\Dbg\sym\BTHport.sys\5249EE07202000\BTHport.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1218

    Key  : Analysis.Elapsed.mSec
    Value: 4782

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x1a

    Key  : Failure.Bucket
    Value: MEMORY_CORRUPTION_ONE_BIT

    Key  : Failure.Hash
    Value: {e3faf315-c3d0-81db-819a-6c43d23c63a7}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 1497cf94

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 1

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 0

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 0

    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 1

    Key  : Hypervisor.Flags.Epf
    Value: 0

    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 1

    Key  : Hypervisor.Flags.HardwareMbecAvailable
    Value: 1

    Key  : Hypervisor.Flags.MaxBankNumber
    Value: 0

    Key  : Hypervisor.Flags.MemoryZeroingControl
    Value: 0

    Key  : Hypervisor.Flags.NoExtendedRangeFlush
    Value: 0

    Key  : Hypervisor.Flags.NoNonArchCoreSharing
    Value: 1

    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 1

    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0

    Key  : Hypervisor.Flags.RootScheduler
    Value: 0

    Key  : Hypervisor.Flags.SynicAvailable
    Value: 1

    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0

    Key  : Hypervisor.Flags.Value
    Value: 4853999

    Key  : Hypervisor.Flags.ValueHex
    Value: 4a10ef

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 1

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 1

    Key  : Hypervisor.RootFlags.AccessStats
    Value: 1

    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0

    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 1

    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0

    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 1

    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 1

    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.Nested
    Value: 0

    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.Value
    Value: 1015

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 3f7

    Key  : MemoryManagement.PFN
    Value: 0

    Key  : WER.OS.Branch
    Value: ni_release_svc_prod3

    Key  : WER.OS.Version
    Value: 10.0.22621.2506

BUGCHECK_CODE:  1a

BUGCHECK_P1: 41792

BUGCHECK_P2: ffffd3bffeb3d930

BUGCHECK_P3: 2

BUGCHECK_P4: 0

FILE_IN_CAB:  121423-12484-01.dmp

MEMORY_CORRUPTOR:  ONE_BIT

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  chrome.exe

STACK_TEXT:  
ffffbc82`2a05ed98 fffff802`75e81c72     : 00000000`0000001a 00000000`00041792 ffffd3bf`feb3d930 00000000`00000002 : nt!KeBugCheckEx
ffffbc82`2a05eda0 fffff802`75c8a4e6     : ffffbc82`2a05f270 ffffd3bf`feb3dff8 ffffeabb`6a197039 ffffaa8f`cf865740 : nt!MiDeleteVa+0x2314f2
ffffbc82`2a05ee90 fffff802`75c8a8aa     : ffffbc82`00000000 ffffaa8f`cf865740 ffffd3e9`00000000 ffffbc82`2a05f2c0 : nt!MiWalkPageTablesRecursively+0x266
ffffbc82`2a05ef20 fffff802`75c8a8aa     : ffffbc82`2a05f270 ffffaa8f`cf865740 ffffd3e9`00000000 ffffbc82`2a05f2d0 : nt!MiWalkPageTablesRecursively+0x62a
ffffbc82`2a05efb0 fffff802`75c8a8aa     : ffffbc82`2a05f270 ffffaa8f`cf865740 ffffd3e9`00000000 ffffbc82`2a05f2e0 : nt!MiWalkPageTablesRecursively+0x62a
ffffbc82`2a05f040 fffff802`75c8a181     : 00000000`00000000 ffffaa8f`cf865740 0000007f`00000000 ffffbc82`2a05f2f0 : nt!MiWalkPageTablesRecursively+0x62a
ffffbc82`2a05f0d0 fffff802`75c506e2     : ffffbc82`2a05f270 00007ff6`00000001 00000000`00000002 00000000`00000000 : nt!MiWalkPageTables+0x371
ffffbc82`2a05f1d0 fffff802`75c4a67a     : ffffaa8f`cf865590 ffffaa8f`cb35e080 ffffbc82`2a05f570 ffffaa8f`cb35e780 : nt!MiDeletePagablePteRange+0x3c2
ffffbc82`2a05f4e0 fffff802`760e5117     : 00000000`00000000 ffffbc82`00000001 00007ff6`47270000 ffffaa8f`ba0132e0 : nt!MiDeleteVirtualAddresses+0x4e
ffffbc82`2a05f530 fffff802`7612e8fd     : 00007ffd`64740000 ffffaa8f`c9a60480 00000000`00000000 00000000`00000000 : nt!MiDeleteVad+0x1b7
ffffbc82`2a05f5f0 fffff802`7612e4c3     : ffffaa8f`c9a60480 00000000`00000000 ffffaa8f`cb35e080 00000000`00000000 : nt!MiUnmapVad+0x49
ffffbc82`2a05f620 fffff802`7610a6b5     : ffffaa8f`c9a4fc20 ffffaa8f`c9a4fc20 ffffaa8f`c9a4fc20 ffffaa8f`cf8650c0 : nt!MiCleanVad+0x2f
ffffbc82`2a05f650 fffff802`7608da6d     : ffffffff`00000000 ffffffff`ffffffff 00000000`00000001 ffffaa8f`cf8650c0 : nt!MmCleanProcessAddressSpace+0x10d
ffffbc82`2a05f6d0 fffff802`760dc6a2     : ffffaa8f`cf8650c0 ffffe702`aafbc770 ffffbc82`2a05f8f9 00000000`00000000 : nt!PspRundownSingleProcess+0xc1
ffffbc82`2a05f760 fffff802`761cdf88     : 00000000`00000000 00000000`00000001 ffffaa8f`cb35e0f4 000000bd`84fa1000 : nt!PspExitThread+0x64e
ffffbc82`2a05f860 fffff802`75d0b9ad     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSchedulerApcTerminate+0x38
ffffbc82`2a05f8a0 fffff802`75e1cb20     : 00000000`00000001 ffffbc82`2a05f960 00000000`00000000 ffffaa8f`cf8650c0 : nt!KiDeliverApc+0x47d
ffffbc82`2a05f960 fffff802`75e2b78f     : ffffaa8f`cb35e080 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInitiateUserApc+0x70
ffffbc82`2a05faa0 00007ffe`6d82f3f4     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9f
000000bd`8afff188 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`6d82f3f4

MODULE_NAME: hardware

IMAGE_NAME:  memory_corruption

STACK_COMMAND:  .cxr; .ecxr ; kb

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT

OS_VERSION:  10.0.22621.2506

BUILDLAB_STR:  ni_release_svc_prod3

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

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

Followup:     MachineOwner
---------
Windows for home | Windows 11 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Lester Bernard Reyes 82,025 Reputation points Independent Advisor
    2023-12-16T02:51:11+00:00

    You are always welcome and I hope it will be all good now since you will replace the RAM.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2023-12-15T19:32:19+00:00

    Hello Bernard, thank you very much for your attention.

    I had 2 8gb ram memory sticks that were installed in the PC since i bought it, on 2021, if i remember correctly. After your reply, I tested them, and one of them was defective, I already placed an order for a new one.

    Thanks again for the help!

    Marcos

    Was this answer helpful?

    0 comments
  3. Lester Bernard Reyes 82,025 Reputation points Independent Advisor
    2023-12-15T04:45:59+00:00

    Hi Marcos, thanks for reaching out. My name is Bernard a Windows fan like you. I'll be happy to help you out today.

    I understand the issue you have, there is nothing to worry I am here to help, upon analyzing and checking the DMP logs you have, the error you have is memory_corruption, this means there is a problem with the PC memory and RAM itself or the RAM slot on the motherboard, in this case, this might be a memory leak which is caused by third party services or there is a hardware-related problem, to eliminate any software issues, kindly follow the steps below:

    Method 1. Do clean boot:

    A “clean boot” starts Windows with a minimal set of drivers and startup programs, so that you can determine whether a background program is interfering with your game or program.

    • In the search box on the taskbar, type msconfig and select System Configuration from the results.
    • On the Services tab of System Configuration, select Hide all Microsoft services, and then select Disable all.
    • On the Startup tab of System Configuration, select Open Task Manager.
    • Under Startup in Task Manager, for each startup item, select the item and then select Disable.
    • Close Task Manager.
    • On the Startup tab of System Configuration, select OK. When you restart the computer, it's in a clean boot environment.

    Troubleshooting reference: https://support.microsoft.com/en-us/help/929135...

    Method 2. Run memory diagnostic tool: The memory diagnostic tool is a RAM test to check if there are any issues with RAM.

    • Press Windows key + R then type in mdsched.exe hit OK then restart the device.

    Note: If the issue persists, I highly suggest contacting a local technician to physically check the device as it is a hardware problem, it might need a RAM replacement or just need to clean the motherboard, another option is to try removing each RAM and test if that works fine, if yes, the RAM you removed is defective.

    Let me know how it goes and I hope that helps.

    Bernard

    Was this answer helpful?

    0 comments