Many BSOD crashes - allegedly memory

Windows 10 Professional machine running 21H1. 64GB ram. 21H1 was recently installed within the last couple of weeks. In the same general time frame, many BSODs relating to memory:

• FAULTY_HARDWARE_CORRUPTED_PAGE
• DRIVER_OVERRAN_STACK_BUFFER (new one for me)
• MEMORY_MANAGEMENT
• CRITICAL_STRUCTURE_CORRUPTION

I've looked at the dumps using WhoCrashed each time it's happened, and it's always been down in either ntdll.sys or ntoskrnl.exe. The description is pretty generic - maybe faulty ram, overheating or a buggy driver. I run Crucial RAM, and it tests fine. On a hail mary, I replaced the RAM with two new SODIMMS - still crashes. My laptop runs warm and always has, but the CPU is high 40s. My money is on a bad driver which this laptop has been notorious for.

Multiple malware scans - nothing found.

Dump files are here: dump files

I truly appreciate any insights you can provide.

Regards

Update BIOS - https://my.hidrive.com/share/yze8mg-wf8#$/BIOS%20and%20EC%20Firmware/CLEVO/P_Series/P6xx_Series/P6xxHx

Umm, any description of this zip content? :) I normally don't flash my BIOS unless necessary.

Hello cgilley

The crash dumps all point to memory corruption as the most likely cause. See below for a summary:

Code:

Debug session time: Wed Nov  3 00:08:57.292 2021 (UTC + 0:00)

Loading Dump File [C:\Users\philc\SysnativeBSODApps\110221-25718-01.dmp]

Built by: 19041.1.amd64fre.vb_release.191206-1406

System Uptime: 0 days 4:55:01.994

BugCheck Info: MEMORY_MANAGEMENT (1a)

Bugcheck code 0000001A

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

Arg3: 000000100c100000

Arg4: 0000000000000000

PROCESS_NAME:  WmiPrvSE.exe

Probably caused by: memory_corruption ( nt!MiDeleteVa+153a )

FAILURE_BUCKET_ID:  0x1a_41792_nt!MiDeleteVa

MaxSpeed:     2800

CurrentSpeed: 2808

¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Debug session time: Sat Oct 30 11:00:50.846 2021 (UTC + 0:00)

Loading Dump File [C:\Users\philc\SysnativeBSODApps\103021-28562-01.dmp]

Built by: 19041.1.amd64fre.vb_release.191206-1406

System Uptime: 1 days 19:32:13.537

BugCheck Info: FAULTY_HARDWARE_CORRUPTED_PAGE (12b)

Bugcheck code 0000012B

Arguments: 

Arg1: ffffffffc00002c4, virtual address mapping the corrupted page

Arg2: 00000000000003cb, physical page number

Arg3: 000001b91d1e8a10, zero

Arg4: ffffe4804a112000, zero

*** WARNING: Unable to verify timestamp for win32k.sys

PROCESS_NAME:  MemCompression

Probably caused by: ntkrnlmp.exe ( nt!ST_STORE::StDmPageError+10a )

FAILURE_BUCKET_ID:  0x12B_c00002c4_StCtDecompressFailed_nt!ST_STORE_SM_TRAITS_::StDmPageError

MaxSpeed:     2800

CurrentSpeed: 2808

¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Debug session time: Mon Oct 25 11:13:02.227 2021 (UTC + 0:00)

Loading Dump File [C:\Users\philc\SysnativeBSODApps\102521-13390-01.dmp]

Built by: 19041.1.amd64fre.vb_release.191206-1406

System Uptime: 1 days 16:11:19.930

BugCheck Info: MEMORY_MANAGEMENT (1a)

Bugcheck code 0000001A

Arguments: 

Arg1: 0000000000008886, The subtype of the bugcheck.

Arg2: ffff98801dc50a70

Arg3: ffff988030186000

Arg4: 0000000000000005

PROCESS_NAME:  chrome.exe

Probably caused by: memory_corruption ( nt!MiUnlinkPageFromList+cb0 )

FAILURE_BUCKET_ID:  0x1a_8886_nt!MiUnlinkPageFromList

MaxSpeed:     2800

CurrentSpeed: 2808

¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Debug session time: Fri Oct 22 21:25:47.657 2021 (UTC + 0:00)

Loading Dump File [C:\Users\philc\SysnativeBSODApps\102221-15234-01.dmp]

Built by: 19041.1.amd64fre.vb_release.191206-1406

System Uptime: 0 days 1:28:05.656

BugCheck Info: MEMORY_MANAGEMENT (1a)

Bugcheck code 0000001A

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

Arg3: 0000001014100000

Arg4: 0000000000000000

PROCESS_NAME:  ControlStation.exe

Probably caused by: memory_corruption ( nt!MiDeleteVa+153a )

FAILURE_BUCKET_ID:  0x1a_41792_nt!MiDeleteVa

MaxSpeed:     2800

CurrentSpeed: 2808

¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Debug session time: Fri Oct 22 07:05:03.046 2021 (UTC + 0:00)

Loading Dump File [C:\Users\philc\SysnativeBSODApps\102221-14531-01.dmp]

Built by: 19041.1.amd64fre.vb_release.191206-1406

System Uptime: 0 days 14:23:47.120

BugCheck Info: FAULTY_HARDWARE_CORRUPTED_PAGE (12b)

Bugcheck code 0000012B

Arguments: 

Arg1: ffffffffc00002c4, virtual address mapping the corrupted page

Arg2: 0000000000000d05, physical page number

Arg3: 00000226add01950, zero

Arg4: ffffb9818f1f4000, zero

*** WARNING: Unable to verify timestamp for win32k.sys

PROCESS_NAME:  MemCompression

Probably caused by: ntkrnlmp.exe ( nt!ST_STORE::StDmPageError+10a )

FAILURE_BUCKET_ID:  0x12B_c00002c4_StCtDecompressFailed_nt!ST_STORE_SM_TRAITS_::StDmPageError

MaxSpeed:     2800

CurrentSpeed: 2808

¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

I would begin by trying to narrow down to which pair of memory modules is responsible. Remove the two 16GB modules first and see if the problems go away. If not put them back in and remove the 32GB pair and try again.

Let me know the results and I will advise further.

Phil,

I agree with the memory assessment, but I suspect it's a bit more serious than just a module. I went ahead and purchased two new SO-DIMMs (instead of Crucial I went with G.Skill, nothing low end). Crashes continue. This would lead me to believe it's not RAM - might be the motherboard. The laptop is 4.5 years old, and I normally replace at 3. lol, it's just a PITA.

Historically, this laptop has had driver issues. When Microsoft decided to "help" with updating drivers by default, it was pure misery for a while. I have a spare NVMe drive, I'm going to install a clean copy of Windows and see what happens. I'll post results.

Lets see, today's tasks are

1. Copy development areas to backup machine.
2. Install clean Windows and start the update/installation misery.
3. Shop for new laptop.
4. Go to Urologist for guy things.

The upload you are looking at came from the machine with the G.Skill modules installed. For some reason, Windows sees 96GB - there is a phantom 32GB floating around. In the BIOS, the hardware sees 64GB. Task manager reports 96. I have no idea. :)

The evidence from your logs and the last crash dump file clearly shows you have both Crucial and G-Skill memory modules installed. The two Crucial modules are CT16G4SFD824A.C16FDD that is the 16GB pair giving you the 32GB RAM and thenj there are the two G-Skill modules F4-3200C22-32GRS, that is the 32GB pair giving you the 64GB making a total of 96GB RAM.

As I said maybe the motherboard has those Crucial modules permanently attached but in my view they are the faulty ones.

Sorry, I may have mixed up the hardware, bad on me. But I can tell you with dead certainty that the crashes started with the Crucial modules installed (they are 4 years old) and the G.Skill are brand new. Still crashes.

Just to be clear - I deliberately swapped both Crucial with the G.Skill. I did not want to mix them up. The fact that it still crashes is telling.

This is a laptop, so I know where the memory goes :) and there isn't anything else. The fact that the BIOS/base see just 64GB points at maybe a mismatch in the hardware. I'm not worried about that. Just need the crashes to go away.

I am not suggesting you have left behind or swapped modules. The laptop obviously comes with some extra RAM hardware built in to the motherboard. As I believe it is this RAM which is faulty the only way you can fix it is to replace the motherboard of the laptop - this is not usually a cost effective solution so if you were thinking of buying a new laptop anyway then that is probably the way to go.

I can't find any manual for your laptop otherwise I would look up its specifications and see if it was possible to repair the motherboard - may be a PC repair shop can help.

One other option is to run Memtest86 and see what that tells you. Let it run overnight as it will take sometime to complete the 4 passes. Ideally we like to see 8 passes so run it twice in succession if you can.