Share via

MEMORY_CORRUPTION_ONE_BIT

Anonymous
2023-08-17T04:33:36+00:00

My pc was working fine until few days ago when i decided to update the gpu drivers (radeon rx460) after that i kept getting bsod every 30ish mins or so and some times i bsod after a bsod. I tried rolling back drivers and that didnt fix it, i tried restore to previous point that also didnt, i even formatted my windows and when i plugged my mouse this bsod happened. When i checked the ram with windows memory diagnostic showed no errors neither did any other piece of hardware like the nvme which was checked both by the windows checker and the samsung magician.

Windbg showed this when i checked:
******************************************************************************* * * * Bugcheck Analysis * * * *******************************************************************************

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: ffffd900d17109c8 Arg3: 0000000001000000 Arg4: 0000000000000000

Debugging Details:

*** WARNING: Check Image - Checksum mismatch - Dump: 0x7b5e, File: 0xaa2d - C:\ProgramData\Dbg\sym\hal.dll\1A7BE8E96000\hal.dll

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec
Value: 2827

Key  : Analysis.Elapsed.mSec
Value: 4178

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

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

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

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

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

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

Key  : Bugcheck.Code.KiBugCheckData
Value: 0x1a

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.Value
Value: 0

Key  : Hypervisor.Enlightenments.ValueHex
Value: 0

Key  : Hypervisor.Flags.AnyHypervisorPresent
Value: 0

Key  : Hypervisor.Flags.ApicEnlightened
Value: 0

Key  : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 1

Key  : Hypervisor.Flags.AsyncMemoryHint
Value: 0

Key  : Hypervisor.Flags.CoreSchedulerRequested
Value: 0

Key  : Hypervisor.Flags.CpuManager
Value: 0

Key  : Hypervisor.Flags.DeprecateAutoEoi
Value: 0

Key  : Hypervisor.Flags.DynamicCpuDisabled
Value: 0

Key  : Hypervisor.Flags.Epf
Value: 0

Key  : Hypervisor.Flags.ExtendedProcessorMasks
Value: 0

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

Key  : Hypervisor.Flags.Phase0InitDone
Value: 0

Key  : Hypervisor.Flags.PowerSchedulerQos
Value: 0

Key  : Hypervisor.Flags.RootScheduler
Value: 0

Key  : Hypervisor.Flags.SynicAvailable
Value: 0

Key  : Hypervisor.Flags.UseQpcBias
Value: 0

Key  : Hypervisor.Flags.Value
Value: 16908288

Key  : Hypervisor.Flags.ValueHex
Value: 1020000

Key  : Hypervisor.Flags.VpAssistPage
Value: 0

Key  : Hypervisor.Flags.VsmAvailable
Value: 0

Key  : Hypervisor.RootFlags.AccessStats
Value: 0

Key  : Hypervisor.RootFlags.CrashdumpEnlightened
Value: 0

Key  : Hypervisor.RootFlags.CreateVirtualProcessor
Value: 0

Key  : Hypervisor.RootFlags.DisableHyperthreading
Value: 0

Key  : Hypervisor.RootFlags.HostTimelineSync
Value: 0

Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0

Key  : Hypervisor.RootFlags.IsHyperV
Value: 0

Key  : Hypervisor.RootFlags.LivedumpEnlightened
Value: 0

Key  : Hypervisor.RootFlags.MapDeviceInterrupt
Value: 0

Key  : Hypervisor.RootFlags.MceEnlightened
Value: 0

Key  : Hypervisor.RootFlags.Nested
Value: 0

Key  : Hypervisor.RootFlags.StartLogicalProcessor
Value: 0

Key  : Hypervisor.RootFlags.Value
Value: 0

Key  : Hypervisor.RootFlags.ValueHex
Value: 0

Key  : MemoryManagement.PFN
Value: 1000

Key  : SecureKernel.HalpHvciEnabled
Value: 0

Key  : WER.OS.Branch
Value: vb\_release

Key  : WER.OS.Version
Value: 10.0.19041.1

BUGCHECK_CODE: 1a

BUGCHECK_P1: 41792

BUGCHECK_P2: ffffd900d17109c8

BUGCHECK_P3: 1000000

BUGCHECK_P4: 0

FILE_IN_CAB: MEMORY.DMP

MEMORY_CORRUPTOR: ONE_BIT

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

PROCESS_NAME: SearchApp.exe

STACK_TEXT:
fffffd086007f0e8 fffff803542bc49a : 000000000000001a 0000000000041792 ffffd900d17109c8 0000000001000000 : nt!KeBugCheckEx fffffd086007f0f0 fffff8035426d836 : 0000000000000000 ffffd96c8068b880 0000000000000026 ffffd900d17109c8 : nt!MiDeleteVa+0x153a fffffd086007f1f0 fffff8035426d94b : ffffd96c00000000 ffffa80ba9895700 fffffd0800000000 fffffd086007f660 : nt!MiWalkPageTablesRecursively+0x776 fffffd086007f290 fffff8035426d94b : ffffd96cb6403458 ffffa80ba9895700 fffffd0800000001 fffffd086007f670 : nt!MiWalkPageTablesRecursively+0x88b fffffd086007f330 fffff8035426d94b : ffffd96cb6403000 ffffa80ba9895700 fffffd0800000002 fffffd086007f680 : nt!MiWalkPageTablesRecursively+0x88b fffffd086007f3d0 fffff8035426a94b : fffffd086007f4e8 ffffa80ba9895700 fffffd0800000003 fffffd086007f690 : nt!MiWalkPageTablesRecursively+0x88b fffffd086007f470 fffff803542bad31 : fffffd086007f610 ffffa80b00000000 ffffffff00000002 0000000000000000 : nt!MiWalkPageTables+0x36b fffffd086007f570 fffff8035427e830 : 0000000000000001 fffffd0800000000 ffffa80ba9895550 ffffa80ba3fa7040 : nt!MiDeletePagablePteRange+0x4f1 fffffd086007f880 fffff80354685ba9 : ffffa80ba6b7abc0 0000000000000000 ffffa80b00000000 ffffa80b00000000 : nt!MiDeleteVad+0x360 fffffd086007f990 fffff8035468554c : ffffa80ba6b7abc0 ffffa80bad96ba70 ffffa80ba3fa7040 0000000000000000 : nt!MiUnmapVad+0x49 fffffd086007f9c0 fffff8035462441f : ffffa80ba6b7b160 ffffa80ba6b7b160 ffffa80ba6b7abc0 ffffa80ba9895080 : nt!MiCleanVad+0x30 fffffd086007f9f0 fffff80354631550 : ffffffff00000000 ffffffffffffffff 0000000000000001 ffffa80ba9895080 : nt!MmCleanProcessAddressSpace+0x137 fffffd086007fa70 fffff8035490da62 : fffff80354d25440 ffffa80ba9895080 fffff8035490da30 0000000000000000 : nt!PspRundownSingleProcess+0x20c fffffd086007fb00 fffff8035428e5c5 : ffffa80ba3fa7040 fffff803546cdbb0 ffffa80b95870a20 ffffa80b00000000 : nt!PspProcessRundownWorkerSingle+0x32 fffffd086007fb30 fffff803543265f5 : ffffa80ba3fa7040 0000000000000080 ffffa80b958c1080 0000000000000000 : nt!ExpWorkerThread+0x105 fffffd086007fbd0 fffff803544048d8 : ffffd98175840180 ffffa80ba3fa7040 fffff803543265a0 0000000000000246 : nt!PspSystemThreadStartup+0x55 fffffd086007fc20 0000000000000000 : fffffd0860080000 fffffd0860079000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x28

MODULE_NAME: hardware

IMAGE_NAME: memory_corruption

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

I need help to figure out if it is due to a hardware issue or if its an incompatible driver since pc was working fine up until the first gpu driver update

Windows for home | Windows 10 | 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 No comments

11 answers

Sort by: Most helpful
  1. DaveM121 891.6K Reputation points Independent Advisor
    2023-08-18T18:21:45+00:00

    Glad to help!

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2023-08-18T06:01:30+00:00

    When i tested with all rams there were errors at the first one so i removed the slot 1/3 so im gonna replace them . Afterwards i tried the 2/4 and actually had 8 passes and then it found an error does that mean that my 2/4 rams are also bad?

    Was this answer helpful?

    0 comments No comments
  3. DaveM121 891.6K Reputation points Independent Advisor
    2023-08-17T12:26:06+00:00

    Your minidump file just indicates memory (RAM) corruption no specific driver is listed

    I understand you have already used the Windows Memory Diagnostics tool, but the best option is to download the widely available free utility MemTest86, then run a full 4 pass scan with that to test your RAM for physical errors

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2023-08-17T10:51:26+00:00

    https://1drv.ms/u/s!AhMwwqEHjV3Jk1GQobJEyhJ6_Qj0?e=SJIa5d

    Here it is, its only once since this happened only once after the format

    Was this answer helpful?

    0 comments No comments
  5. DaveM121 891.6K Reputation points Independent Advisor
    2023-08-17T07:05:56+00:00

    Hi, I am Dave, I will help you with this.

    Please check to see if your PC is producing any minidump files, I will check those to see if they provide any insight into a potential cause of the system crashes.

    Open Windows File Explorer.

    Navigate to C:\Windows\Minidump

    Copy any minidump files onto your Desktop, then zip those up.

    Upload the zip file to the Cloud (OneDrive, DropBox... etc.), then choose to share those and get a share link.

    Then post the link here to the zip file, so we can take a look for you.

    Was this answer helpful?

    0 comments No comments