Windows 11 BSODs & failure of windows to update

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?
 
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).
 
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.
 
ET_Explorer said:
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.
Click to expand...
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?
 
ubuysa said:
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.
Click to expand...
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.
 
Caliopus said:
New minidump to check on Norton removal. Logs folder showed up this time. No clue what I did wrong the other day.
Click to expand...

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:
 

Attachments

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?
 

Attachments

  • final screen.webp
    final screen.webp
    27.7 KB · Views: 1
  • LOGS.zip
    LOGS.zip
    1 MB · Views: 1
Still empty.

Run the following commands (one at a time) from an elevated command prompt (and wait until the command finishes before continuing with the next one).
The first two commands need the alternativelogs folder because it contains autoruns, hence keep it on the desktop.
Code: 
"%userprofile%\desktop\AlternativeLogs\AutoRuns\autoruns64" -e -a "%userprofile%\desktop\autoruns.arn"
"%userprofile%\desktop\AlternativeLogs\AutoRuns\autorunsc64" -a * -c -m -s -t -nobanner -o "%userprofile%\desktop\autoruns.txt"
c:\windows\system32\wevtutil epl system "%userprofile%\desktop\system-event-viewer.evtx"
c:\windows\system32\wevtutil epl application "%userprofile%\desktop\application-event-viewer.evtx"
c:\windows\system32\dxdiag /whql:on /t "%userprofile%\desktop\dxdiag.txt"
c:\windows\system32\systeminfo > "%userprofile%\desktop\systeminfo.txt"
c:\windows\system32\msinfo32 /nfo "%userprofile%\desktop\msinfo32.nfo"
c:\windows\system32\pnputil /enum-devices /connected /ids /relations /drivers > "%userprofile%\desktop\Connected-Devices.txt"
c:\windows\system32\pnputil /enum-devices /disconnected /ids /relations /drivers > "%userprofile%\desktop\Disconnected-Devices.txt"
c:\windows\system32\pnputil /enum-interfaces /enabled > "%userprofile%\desktop\Enabled-Interfaces.txt"
c:\windows\system32\pnputil /enum-interfaces /disabled > "%userprofile%\desktop\Disabled-Interfaces.txt"
c:\windows\system32\pnputil /enum-drivers > "%userprofile%\desktop\Drivers-PNPutil.txt"
c:\windows\system32\dism /online /get-drivers /format:table > "%userprofile%\desktop\Drivers-DISM.txt"
(c:\windows\system32\driverquery /fo table && c:\windows\system32\driverquery /fo list && c:\windows\system32\driverquery /fo csv && c:\windows\system32\driverquery /si) > "%userprofile%\desktop\driverquery.txt"
(path && dir c:\windows\memory.dmp /a && dir c:\windows\minidump /a && dir C:\ProgramData\Microsoft\Windows\WER\*.wer /a /s) > "%userprofile%\desktop\PathEnvVar-and-DUMPS.txt"

At the end, you should see 15 files on the desktop (if there are not errors).
Then zip the files up and post the file.
Otherwise, if you see errors, post them here.
 
Last edited:
Click windows start, type command prompt, click run as administrator, click yes in the user account control window that should appear: this should open a black window (named Administrator: command prompt).
Run the commands in that window.
This is from windows 10 (sorry):

commandprompt.webp


commandprompt2.webp
 
From an elevated command prompt (35th post), run these commands:
Code: 
dism /online /cleanup-image /checkhealth
dism /online /cleanup-image /scanhealth
sfc /scannow
chkdsk c: /v

These are the results we expect:
1st dism command: No component store corruption detected.
2nd dism command: No component store corruption detected.
3rd sfc command: Windows resource protection did not find any integrity violations. (OR Windows Resource Protection found corrupt files and successfully repaired them.)
4th chkdsk command: Windows has scanned the file system and found no problems. (0 KB in bad sectors.)
Click to expand...

I get (real example):
Read More:
 
Thanks for sharing the output. If I understand it correctly, the only thing of potential interest is that some corrupt files were repaired. What next? Try to install windows again? Or is there something else I need to do before the next try?
 
The second and third command lines indicate problems



Microsoft Windows [Version 10.0.22000.318]
(c) Microsoft Corporation. All rights reserved.

C:\Windows\system32>dism /online /cleanup-image /checkhealth

Deployment Image Servicing and Management tool
Version: 10.0.22000.1

Image Version: 10.0.22000.318

No component store corruption detected.
The operation completed successfully.

C:\Windows\system32>dism /online /cleanup-image /scanhealth

Deployment Image Servicing and Management tool
Version: 10.0.22000.1

Image Version: 10.0.22000.318

[== 4.9% ]
Error: 1009

The configuration registry database is corrupt.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

C:\Windows\system32>sfc /scannow

Beginning system scan. This process will take some time.


Windows Resource Protection could not perform the requested operation.

C:\Windows\system32>chkdsk c: /v
The type of the file system is NTFS.

WARNING! /F parameter not specified.
Running CHKDSK in read-only mode.

Stage 1: Examining basic file system structure ...
1059584 file records processed.
File verification completed.
Phase duration (File record verification): 11.26 seconds.
6566 large file records processed.
Phase duration (Orphan file record recovery): 2.03 milliseconds.
0 bad file records processed.
Phase duration (Bad file record checking): 0.27 milliseconds.

Stage 2: Examining file name linkage ...
230 reparse records processed.
1299522 index entries processed.
Index verification completed.
Phase duration (Index verification): 15.08 seconds.
0 unindexed files scanned.
Phase duration (Orphan reconnection): 1.39 seconds.
0 unindexed files recovered to lost and found.
Phase duration (Orphan recovery to lost and found): 0.14 milliseconds.
230 reparse records processed.
Phase duration (Reparse point and Object ID verification): 3.67 milliseconds.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
Phase duration (Security descriptor verification): 73.06 milliseconds.
119970 data files processed.
Phase duration (Data attribute verification): 0.97 milliseconds.
CHKDSK is verifying Usn Journal...
38970008 USN bytes processed.
Usn Journal verification completed.
Phase duration (USN journal verification): 348.12 milliseconds.

Windows has scanned the file system and found no problems.
No further action is required.

487567359 KB total disk space.
124237352 KB in 605368 files.
357472 KB in 119971 indexes.
0 KB in bad sectors.
1188743 KB in use by the system.
65536 KB occupied by the log file.
361783792 KB available on disk.

4096 bytes in each allocation unit.
121891839 total allocation units on disk.
90445948 allocation units available on disk.
Total duration: 28.16 seconds (28169 ms).

C:\Windows\system32>
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top