Windows 11 BSODs & failure of windows to update

[ubuysa]

You're running a version of Windows 11 (21H2) that is no longer supported, it reached end of servicing in June 2023. My best advice would be to download the latest version of Windows (24H2) and clean install that.

 

[Caliopus]

OK. Will try that. But first two questions.

Shouldn't the automatic updates have updated the version to 24H2?

Will the 21H2 product key work to activate (or automatically activate) the downloaded 24H4 version?

 

[ubuysa]

No, the Feature update (to a new version) aren't automatic until you're well out of date.

 

[Caliopus]

installation of linked download failed several times at 71% 0x8007007f

 

[Caliopus]

linked download finally installed. But, 2023-10 cumulative update still won't install and winver therefore is still 21H2

 

[Caliopus]

The above attempt was the uppermost download option. Second option (to thumb drive) crashed with BSOD (in black) and stop code: kernal_mode_heap_corruption.

I'm about ready to give up. Given all the various attempts using different downloads, and even full clean installs failing twice now, I'm increasingly coming to believe the problem is in the hardware. Is there any way to determine what aspect of the hardware is causing the problem, since I would have to otherwise buy and test out everything until I hit the right one (and at that point I'm tempted to indulge my impulse to throw the comp through a window and start from scratch).

 

[ET_Explorer]

kernal_mode_heap_corruption.

Indicates corruption in the heap or a specific data structure. This error screen is displayed when the computer detects an issue with the system memory or encounters missing or damaged system files. Other reasons could also cause your computer to show this error.

 

[ubuysa]

It's frowned on to suggest a clean install on here without exhausting all other options, but I believe that trying to upgrade a potentially broken system to 24H2 is unwise. Upgrade-in-place really only works reliably when the base system is clean. If this were mine I would clean install 24H2 from bootbale media and delete all existing UEFI partitions. Take a disk image of your existing system first (via Acronis or Macrium Reflect) so you have a way back to where you are now.

 

[Caliopus]

Indicates corruption in the heap or a specific data structure. This error screen is displayed when the computer detects an issue with the system memory or encounters missing or damaged system files. Other reasons could also cause your computer to show this error.

The stop codes have been all over the place. I listed a sample of 4 of them in the original post. I'm not very confident that any single one would be the key in itself. Is there a pattern in the group?

 

[Caliopus]

It's frowned on to suggest a clean install on here without exhausting all other options, but I believe that trying to upgrade a potentially broken system to 24H2 is unwise. Upgrade-in-place really only works reliably when the base system is clean. If this were mine I would clean install 24H2 from bootbale media and delete all existing UEFI partitions. Take a disk image of your existing system first (via Acronis or Macrium Reflect) so you have a way back to where you are now.

I did just that once already (though I left the original default partitions in place) to get the clean install I'm currently using and the system crashed a few times while doing that install, though it eventually completed everything except the cumulative update. So, it was no improvement.

 

[xilolee]

New minidump to check on Norton removal. Logs folder showed up this time. No clue what I did wrong the other day.

The logs you uploaded contains the logs.bat...
I'll repeat.
If there's a LOGS folder on your desktop, check if it contains 15 files.
Zip it up and send the file.
If it's not present:

• Download AlternativeLogs.zip.
• Decompress the folder on the desktop.
• On the desktop now you should see a folder named AlternativeLogs.
  Read More:

  
• Open the AlternativeLogs folder.
• Right-click logs.bat, click run as administrator, click yes in the user account control window that should appear.
  Read More:

  
• Click ok in the autoruns window dialog.
  Read More:

  
• After three to six minutes have passed, the new LOGS folder on the desktop should contain fifteen files.
  Read More:

  
• Zip the LOGS folder up and upload the resulting file here.
  Read More:

  

 

[Caliopus]

I ran it yet again and got the same result. When I run the bat file, the progress screen that opens begins with 2 error messages, but then eventually proceeds to a progress bar and then the attached final screen. Perhaps the answer to why nothing is in the logs file is there. The logs folder does not have a visible 15 files in it, but on the assumption I'm missing something, I've been attaching it anyway. The current run did not produce anything different (zipped file attached). I did however, just notice that the progress screen pathway says system32. Is that correct?