Windows 10: MEMORY_CORRUPTION_ONE_BIT (18446744073709551615)

Recently my PC has been crashing (BSOD). I ran a diagnostic tool and see the below error (among others). Any ideas what this could be>?


Description

Faulting Application Path: C:\Windows\System32\WerFault.exe
Creation Time: 12/13/2019 1:15:25 PM
Problem: Shut down unexpectedly
Status: Report sent

Problem signature
Problem Event Name: BlueScreen
Code: 1a
Parameter 1: 41792
Parameter 2: ffff9500628e1868
Parameter 3: 80000000
Parameter 4: 0
OS version: 10_0_18362
Service Pack: 0_0
Product: 768_1

Extra information about the problem
Bucket ID: MEMORY_CORRUPTION_ONE_BIT (18446744073709551615)

:)

 

Various BSOD errors happening on startup and after login.


Some dumps can be a bit clear , this + various BSODs + BSODs in safe mode are clear signs of hardware errors.
Code:

Code:

SYMBOL_NAME:  ONE_BIT  FOLLOWUP_NAME:  MachineOwner  MODULE_NAME: hardware  IMAGE_NAME:  memory_corruption  DEBUG_FLR_IMAGE_TIMESTAMP:  0  IMAGE_VERSION:    FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT  BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT  PRIMARY_PROBLEM_CLASS:  MEMORY_CORRUPTION_ONE_BIT

 

Multiple BSOD after startup

Hi Sindre,

I am Sumit, an Independent Advisor and a 2-Year Windows Insider MVP here to help.

I see a problem with Memory

BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT

PRIMARY_PROBLEM_CLASS: MEMORY_CORRUPTION_ONE_BIT

Let us check the Memory.

I suggest you to Run memory test for at least 8 passes, prefarably Overnight.

https://www.tenforums.com/tutorials/14201-memte...

If you have a DDR4 RAM, use MemTest86 rather than MemTest86+

MemTest86 - Official Site of the x86 Memory Testing Tool

When the test completes post back the Image(You can use your phone's camera).

Disclaimer:

There are links to non-Microsoft websites which would provide accurate and safe information. Watch out for ads on the sites which are frequently classified as a PUP (Potentially Unwanted Products). There is no need to buy paid products to fix your computers
as they do more harm than good sometimes.

 

BSOD: ntoskrnl.exe and more


It isn't the RAM the reports are talking about, they never do.

Both are memory related crashes, not only because it says 'memory_corruption'
Code:

Code:

******************************************************************************* *                                                                             * *                        Bugcheck Analysis                                    * *                                                                             * *******************************************************************************  Use !analyze -v to get detailed debugging information.  BugCheck 3B, {c0000005, fffff8015fe9d1fa, ffffd0005deb06f0, 0}  Probably caused by : memory_corruption  Followup:     memory_corruption  MODULE_NAME: memory_corruption  IMAGE_NAME:  memory_corruption  FOLLOWUP_NAME:  memory_corruption  DEBUG_FLR_IMAGE_TIMESTAMP:  0  MEMORY_CORRUPTOR:  ONE_BIT  STACK_COMMAND:  .cxr 0xffffd0005deb06f0 ; kb  FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT  BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT  PRIMARY_PROBLEM_CLASS:  MEMORY_CORRUPTION_ONE_BIT   ******************************************************************************* *                                                                             * *                        Bugcheck Analysis                                    * *                                                                             * *******************************************************************************  Use !analyze -v to get detailed debugging information.  BugCheck 1A, {41792, fffff6bffaf4a638, 20000, 0}  Probably caused by : memory_corruption ( ONE_BIT )  Followup:     MachineOwner  MODULE_NAME: hardware  IMAGE_NAME:  memory_corruption  DEBUG_FLR_IMAGE_TIMESTAMP:  0  IMAGE_VERSION:    FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT  BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT  PRIMARY_PROBLEM_CLASS:  MEMORY_CORRUPTION_ONE_BIT