BSOD when updating to 21H2

Software & Operating Systems Windows
1

Hi. I’ve got quite an old Clevo 240HUQ laptop from about 2011 (2620M, 8GB, 128 M4 SSD). It hadn’t updated in a while and has been stuck on 1809 without any updates appearing since, which I thought was odd as updating on other machines hadn’t been an issue. So I decided to force the issue and first ran the Update Assistant but that didn’t work (to do with it thinking I was installing from a USB, which I wasn’t, but I solved it by changing a registry entry from 1 to 0). I eventually got it installed using the Media Creation tool so it’s running 21H2 but blue screens sometimes after a minute or so, other times I can leave it for nearly half an hour until it does it.
In safe mode it’s okay, but a clean boot (disabled all non-MS programs and startups) still blue screens. Only today I got a Recovery warning about Windows needing a repair but it was pointing to MbamElam.sys which is Malwarebytes. Now before this I’d removed Malwarebytes as it had insisted on starting on startup, so I removed it so I could do a clean boot.

Reading the blue screens in Bluescreenview, they all look the same (ntoskrnl.exe). I have the minidumps as a link, ready to post. Shall I just post the link here?

I’ve also got Linux running dual boot on it and that works fine, just so you know.

Any help appreciated, thanks.

2

Blue screens link

3

Since Windows is proprietary there is not really much I believe anyone can do to diagnose this. What I would do in your situation is backup the data. Test the hardware as best as I can. The reason for this is that maybe there is something wrong and Linux is just more robust in handling the errors. I would at least test the RAM with Memtest86+, run a full SMART test on the SSD and maybe a stress test to see if the CPU, and the system as a whole, stays stable under load. If all these test return no errors, I would freshly reinstall Windows, because sometimes Windows is picky or destroys itself through some update.

4

I cant point to any in particular but there have been a few posts around here of people with laptops that do not like the latest major windows update. Similar issues as you are reporting, boots loops and bsod.

Could just be a bad update.

5

Here’s the blue screen link.

6

I had the same issue with 20h2 that I did before I tried the Creation Tool 21h2 update. It was weird to me that automatic updates refused to find anything past 1809 apart from a few antivirus ones, but then they kept failing to install.

1 Like
7

I’ve run Memtest and it’s had two passes. I know it’s not much but seeing as I had no issues with 1809 I don’t think it’s the RAM.

Can I run these other stress tests within Linux then?

I was on your line of thinking with just a fresh install of 21h2 from a Creation Tool CD / USB if I get nowhere trying to translate the BSODs.

1 Like
8

I believe you can run the windows upgrade tool with an external USB drive. It does something along the lines of preserving all your user data while wiping and replacing the “broken” existing windows 10 install. Its how I got past broken Windows 10 upgrades before

9

Thanks. Does it backup your data onto the USB drive then? I don’t think I’ve got a USB device big enough. But I think I’ve got the majority of things I need to keep backed up anyway, I’ll probably just go through it again later this week and then try a fresh reinstall of 21h2 as suggested and see how it goes.

1 Like
10

I just processed all your BSODs, there is no common program among them, but it might be your memory modules going bad.

BSODs 
BugCheck 1E, {ffffffffc0000094, fffff8037bcc3906, ffffbf05d6e8aa60, 5a}
Probably caused by : memory_corruption
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1E, {ffffffffc0000094, fffff80103ac3906, ffffa609b985e8f0, 5a}
Probably caused by : memory_corruption
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1E, {ffffffffc0000094, fffff801734c3906, ffffbb0dc6055bd0, 5a}
Probably caused by : memory_corruption
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1E, {ffffffffc0000094, fffff8065cac3906, ffffa70beb468610, 5a}
Probably caused by : memory_corruption
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1E, {ffffffffc0000094, fffff80062cc3906, ffffdf042646ee80, 5a}
Probably caused by : memory_corruption
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1E, {ffffffffc0000094, fffff8027b2c3906, ffffdf87283fd780, 5a}
Probably caused by : memory_corruption
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1E, {ffffffffc0000094, fffff8024f6c3906, ffffbc0d7b25ce80, 5a}
Probably caused by : memory_corruption
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1E, {ffffffffc0000094, fffff800526c3906, ffffd207324818f0, 5a}
Probably caused by : memory_corruption
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1E, {ffffffffc0000094, fffff80653ec3906, ffff9681147f35e0, 5a}
Probably caused by : memory_corruption
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1E, {ffffffffc0000094, fffff8007a0c3906, ffffb182424581c0, 5a}
Probably caused by : memory_corruption
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1E, {ffffffffc0000094, fffff805688c3906, ffffa981ff0628c0, 5a}
Probably caused by : memory_corruption
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1E, {ffffffffc0000094, fffff80117ac3906, ffffb70ac5c64a30, 5a}
Probably caused by : memory_corruption
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1E, {ffffffffc0000094, fffff80053ac3906, ffff8286d62418c0, 5a}
Probably caused by : memory_corruption
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1E, {ffffffffc0000094, fffff807238c3906, ffff9e0eea7951e0, 5a}
Probably caused by : memory_corruption
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1E, {ffffffffc0000094, fffff8045f8c3906, ffffe10305462750, 5a}
Probably caused by : memory_corruption
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
The process that initiated the BSOD 
Built by: 19041.1.amd64fre.vb_release.191206-1406
Debug session time: Fri Jun 18 06:07:15.649 2021 (UTC - 6:00)
System Uptime: 0 days 0:14:00.904
BugCheck 1E, {ffffffffc0000094, fffff8037bcc3906, ffffbf05d6e8aa60, 5a}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x1E_c0000094
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 19041.1.amd64fre.vb_release.191206-1406
Debug session time: Thu Jun 17 12:40:58.963 2021 (UTC - 6:00)
System Uptime: 0 days 0:00:51.678
BugCheck 1E, {ffffffffc0000094, fffff80103ac3906, ffffa609b985e8f0, 5a}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x1E_c0000094
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 19041.1.amd64fre.vb_release.191206-1406
Debug session time: Thu Jun 17 09:24:51.032 2021 (UTC - 6:00)
System Uptime: 0 days 0:09:13.748
BugCheck 1E, {ffffffffc0000094, fffff801734c3906, ffffbb0dc6055bd0, 5a}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x1E_c0000094
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 19041.1.amd64fre.vb_release.191206-1406
Debug session time: Thu Jun 17 08:38:22.064 2021 (UTC - 6:00)
System Uptime: 0 days 0:00:51.780
BugCheck 1E, {ffffffffc0000094, fffff8065cac3906, ffffa70beb468610, 5a}
Probably caused by : memory_corruption
BUGCHECK_STR:  0x1E_c0000094
PROCESS_NAME:  mmc.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 19041.1.amd64fre.vb_release.191206-1406
Debug session time: Thu Jun 17 08:17:50.480 2021 (UTC - 6:00)
System Uptime: 0 days 0:01:03.196
BugCheck 1E, {ffffffffc0000094, fffff80062cc3906, ffffdf042646ee80, 5a}
Probably caused by : memory_corruption
BUGCHECK_STR:  0x1E_c0000094
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 19041.1.amd64fre.vb_release.191206-1406
Debug session time: Thu Jun 17 08:13:20.217 2021 (UTC - 6:00)
System Uptime: 0 days 0:05:41.932
BugCheck 1E, {ffffffffc0000094, fffff8027b2c3906, ffffdf87283fd780, 5a}
Probably caused by : memory_corruption
BUGCHECK_STR:  0x1E_c0000094
PROCESS_NAME:  MoUsoCoreWorker.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 19041.1.amd64fre.vb_release.191206-1406
Debug session time: Thu Jun 17 07:03:45.008 2021 (UTC - 6:00)
System Uptime: 0 days 0:01:41.724
BugCheck 1E, {ffffffffc0000094, fffff8024f6c3906, ffffbc0d7b25ce80, 5a}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x1E_c0000094
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 19041.1.amd64fre.vb_release.191206-1406
Debug session time: Thu Jun 17 06:58:46.049 2021 (UTC - 6:00)
System Uptime: 0 days 0:01:31.765
BugCheck 1E, {ffffffffc0000094, fffff800526c3906, ffffd207324818f0, 5a}
Probably caused by : memory_corruption
BUGCHECK_STR:  0x1E_c0000094
PROCESS_NAME:  MBAMService.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 19041.1.amd64fre.vb_release.191206-1406
Debug session time: Thu Jun 17 06:02:25.834 2021 (UTC - 6:00)
System Uptime: 0 days 0:04:28.550
BugCheck 1E, {ffffffffc0000094, fffff80653ec3906, ffff9681147f35e0, 5a}
Probably caused by : memory_corruption
BUGCHECK_STR:  0x1E_c0000094
PROCESS_NAME:  WMIADAP.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 19041.1.amd64fre.vb_release.191206-1406
Debug session time: Thu Jun 17 05:42:18.547 2021 (UTC - 6:00)
System Uptime: 0 days 13:18:34.262
BugCheck 1E, {ffffffffc0000094, fffff8007a0c3906, ffffb182424581c0, 5a}
Probably caused by : memory_corruption
BUGCHECK_STR:  0x1E_c0000094
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 19041.1.amd64fre.vb_release.191206-1406
Debug session time: Wed Jun 16 16:23:00.708 2021 (UTC - 6:00)
System Uptime: 0 days 0:05:16.424
BugCheck 1E, {ffffffffc0000094, fffff805688c3906, ffffa981ff0628c0, 5a}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x1E_c0000094
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 19041.1.amd64fre.vb_release.191206-1406
Debug session time: Wed Jun 16 14:27:42.493 2021 (UTC - 6:00)
System Uptime: 0 days 0:15:48.209
BugCheck 1E, {ffffffffc0000094, fffff80117ac3906, ffffb70ac5c64a30, 5a}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x1E_c0000094
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 19041.1.amd64fre.vb_release.191206-1406
Debug session time: Wed Jun 16 14:06:49.537 2021 (UTC - 6:00)
System Uptime: 0 days 0:09:32.253
BugCheck 1E, {ffffffffc0000094, fffff80053ac3906, ffff8286d62418c0, 5a}
Probably caused by : memory_corruption
BUGCHECK_STR:  0x1E_c0000094
PROCESS_NAME:  amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.19041.1022_none_7e372e9e7c6e
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 19041.1.amd64fre.vb_release.191206-1406
Debug session time: Wed Jun 16 13:52:07.558 2021 (UTC - 6:00)
System Uptime: 0 days 0:09:08.273
BugCheck 1E, {ffffffffc0000094, fffff807238c3906, ffff9e0eea7951e0, 5a}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x1E_c0000094
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 19041.1.amd64fre.vb_release.191206-1406
Debug session time: Wed Jun 16 13:42:01.605 2021 (UTC - 6:00)
System Uptime: 0 days 0:03:23.321
BugCheck 1E, {ffffffffc0000094, fffff8045f8c3906, ffffe10305462750, 5a}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x1E_c0000094
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
1 Like
11

Okay, thanks very much for all the information. I think I’ll try the fresh reinstall and if that still turns sour, I’ll test the RAM for a couple of days.

1 Like
12

So I tried to wipe the Windows partition with Active Kill Disk with Hiren Bootdisk but that failed (something about drivers). Then tried Parted Magic but immediately had errors when I tried to boot it from disk. I then ran Memtest 5.01 for ten hours (six passes) but typically had no errors.

So I wiped the SSD in another computer, SMART tested it and it was okay. Installed 21h2 onto it back in the laptop which then proceeded to blue screen during setup (region and language choice etc.). It eventually installed though but still blue screened. I tried with just single sticks in either slots (as the setup is 2x4GB) but still got blue screens with both.

With Linux I tried using stresstestapp, but running it just locked up the system for a minute until it gradually came back to usable again. The app itself didn’t actually run though.

I also tried the memory in another laptop, but it just wasn’t recognised. Both slots worked as I tested them with the memory that the other laptop came with, but both sticks from the first laptop just weren’t working. But were both recognised and ‘working’ when back in the original laptop.

I’m still due to test that memory for a few days but I feel it’ll just come back as error free. I believe Novasty’s right by it probably being the memory at fault, I just can’t find any direct evidence that it is.

13

I’ve tested the memory in a third laptop and it ran fine for an hour or so. I then put other memory, from another laptop that hasn’t had issues, in this one and I got the same blue screen (Kmode not handled) after half an hour.
So I think I can rule out the memory. It’s either these latest versions of Windows not playing nice with something or there’s some controller or something that deals with the memory that’s broken. I may leave it just as a Linux machine for now and see how it goes until another big Windows update comes along.