Stuck in Windows11 23H2 with "pending reboot"

Dunge · Dec 27, 2025

Once again I'll ask if you could please edit out this time the computer domain name from your quoted texts at the end.

The crash dump not generating seems weird.

I was wondering if it was nor al that tests would seem to accumulate instead of having on those checked during the last attempt. I still wonder this for this new batch. Do I need to call /reset between each?

That's also quite a long list of test to collect and upload data each runs.. shouldn't I just try the in-place repair first? Would that delete my corporation custom group policies and such?

zbook · Dec 28, 2025

If the problematic driver(s) are identified and fixed then the probability of a successful upgrade is increased.

Yes, each run of WDV can narrow down problematic drivers.

Creating crashes with specific tests are to identify problematic drivers.

If there is something in a post that you want deleted please specify the post #.

Dunge · Dec 28, 2025

The one you just did before that, #20, computer name at the end includes the domain name.

You also haven't been clear as if/why the selected tests seemed to accumulate instead of getting replaced with the new batch and if it's normal or not.

joeandmarg0 · Dec 28, 2025

Are there entries in Reliability History ?To access it,start typing ---reliability ---into the Search box.
In which order did you use sfc and dism.If it was sfc first,could you use dism first then sfc.

zbook · Dec 28, 2025

Dunge said:
The one you just did before that, #20, computer name at the end includes the domain name.

Done.

Dunge said:
You also haven't been clear as if/why the selected tests seemed to accumulate instead of getting replaced with the new batch and if it's normal or not.

Each test is customized.

Customized allows any testing method (tests and drivers).

zbook · Dec 28, 2025

Please update.

Heading to bed soon.

Dunge · Dec 28, 2025

@joeandmarg0

Reliability monitor shows a lot of crash of MoUsoCoreWorker.exe (MoUSO Core Process) which seems to be related to windows update. The timestamp correlates with each boot. I also saw those under the event viewer.

As for your second part, since dism didn't find any issues I doubt it. I also believe zbook scripts did run sfc again. But I launched it again to be sure, it found no issue and didn't impact anything.

@zbook

I was gone to bed way before you.

Each test is customized.

I don't think you understood my message. The point is that, if you take for example my previously attached verifierD.txt, even though only 4 tests were selected for this block, ALL tests had a [x] next to it. As in, creating a new test group doesn't unselect the previous ones even if they are not selected in the UI.

That didn't feel right to me, so this time to make sure the test groups are really just the groups themselves and not inheriting from the previous ones, I launched a /reset before creating a new one to make sure to clear the previous one.

And doing it this way, all 7 of your test blocks passed successfully, no BSOD at all.

Now, when you say "perform an in place repair", which method is that exactly? Using the Windows Installation Assistant? Using the Media Creation Tool (via mounting the ISO)? Or using the Windows Recovery "reset my PC" method?

Thanks

zbook · Dec 28, 2025

1) Please open administrative PS and copy and paste:

wevtutil epl System "$env:USERPROFILE\Desktop\application.evtx" /ow:true

wevtutil epl System "$env:USERPROFILE\Desktop\system.evtx" /ow:true

Post share links.

2) Post querysetting share links for WDV groups A - F.

3) Post a new V2 share link into the newest post.

Dunge · Dec 28, 2025

tenforums - Google Drive

drive.google.com

1) You made a mistake in your instructions by having System twice instead of Application for the first line. Anyway, added both files to the shared drive.

2) I'm sorry but no I won't go through another hours of running 7 tests and collecting output. It seems absolutely unnecessary considering we already know the difference in the content of those output will simply be the list of tests you requested with an [x] next to them.

3) Again, seems unnecessary considering there is practically no change to the system since the last upload from yesterday. But I'll play along nevertheless. Added to the drive with the name VL-RD-19-(2025-12-28_15-02-53).zip

Now since these event viewer logs are also filled with personal information, I'll ask you to please double check before pasting anything containing some. You will most likely find traces of some group policies scripts added by our IT department.

zbook · Dec 28, 2025

Please post a new share link with just the new share links.

Dunge · Dec 28, 2025

application

system

logs

zbook · Dec 28, 2025

Dunge said:
Each querysettings call only prints the same thing with the additional tests checked, so not too useful, but I attached them anyway.

I shared my drive folder with the v2 log collector results again. tenforums - Google Drive

Group A: Booted fined

Group B: Had a BSOD on the first boot. Booted fine after a reboot. VL-RD-19-(2025-12-27_21-28-23).zip

Group C: Had a BSOD on the first boot. Booted fine after a reboot. VL-RD-19-(2025-12-27_21-48-56).zip

Group D: Had a black screen on first boot, had to hard power off. Booted fine after a reboot. VL-RD-19-(2025-12-27_22-04-03).zip

I'm quite curious as to where this is headed by simulating kernel timings errors and such, it's not as if we are trying to find issues on the intel drivers under certain stress conditions.

Windows had failed to create some dump files.

There was an unexpected shutdown an restart today: 12/28.

Did you perform a manual power off?

Was the unexpected shutdown and restart noted?

If your willing to post WDV testing share links then it may be possible to make more progress.

If you're unwilling to post share links then I'll not get the useful information.

Code:

Event[7179]
  Log Name: System
  Source: Microsoft-Windows-Kernel-Power
  Date: 2025-12-28T13:20:24.7940000Z
  Event ID: 41
  Task: N/A
  Level: Critical
  Opcode: Info  a
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: 
  Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Code:

Event[7161]
  Log Name: System
  Source: EventLog
  Date: 2025-12-28T13:20:44.8130000Z
  Event ID: 6008
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic,
  User: N/A
  User Name: N/A
  Computer: 
  Description:
The previous system shutdown at 08:55:17 on ?2025-?12-?28 was unexpected.

Dunge · Dec 28, 2025

The inability to create the crash dump was yesterday during the first batch of tests. I remember the BSOD remaining at 100% for a few minutes and didn't progress so I shut it down. These batch of tests were most likely not valid anyway since they had all tests checked instead of just the requested groups. We now determined today the individuals groups don't cause BSOD.

The unexpected shutdown was most likely the battery running out of juice during the night. Not caused by the tests or a crash. It was shut down and empty when I opened the laptop this morning. At 9h am I was sleeping.

I appreciate your efforts and understand most of your tools are automatized. But again, I'm not sure what kind of information you would get from having a list of tests with different checkmarks next to them, those you selected yourself. Since the tests did not cause issues I really don't see why that would help in any way. We could easily reproduce these output by just adding X in notepad.

The fact that the windows update process crash, or that the winre command mentioned it's not installed seems much more relevant than very common drivers possibly crashing under abnormal situations.

zbook · Dec 28, 2025

When you had activated WDV you reported immediate BSOD.

Windows had failed to create dump files.

The information is incomplete.

Code:

Event[6403]
  Log Name: System
  Source: volmgr
  Date: 2025-12-27T21:59:32.5970000Z
  Event ID: 46
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic,
  User: N/A
  User Name: N/A
  Computer: 
  Description:
Crash dump initialization failed!

Code:

Event[6177]
  Log Name: System
  Source: volmgr
  Date: 2025-12-27T21:41:18.6700000Z
  Event ID: 46
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic,
  User: N/A
  User Name: N/A
  Computer: 
  Description:
Crash dump initialization failed!

Code:

Event[5951]
  Log Name: System
  Source: volmgr
  Date: 2025-12-27T21:19:26.9370000Z
  Event ID: 46
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic,
  User: N/A
  User Name: N/A
  Computer: 
  Description:
Crash dump initialization failed!

Code:

Event[5950]
  Log Name: System
  Source: volmgr
  Date: 2025-12-27T21:19:26.9370000Z
  Event ID: 161
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic,
  User: N/A
  User Name: N/A
  Computer: 
  Description:
Dump file creation failed due to error during dump creation.

Dunge · Dec 28, 2025

But as I keep explaining, the BSOD happened with more than a single group of 5 tests active simultaneously.

I can try to reproduce it again and enable both group A and B from the first batch and the original one from the article and let it wait longer during the BSOD for it to hopefully manage to take a complete dump.

zbook · Dec 28, 2025

Isn't querysettings a quick command?

When there is no BSOD they all can run quickly?

Dunge · Dec 28, 2025

Yes querysettings is fast. The long part is doing all individual test groups, checking the driver list each time, rebooting to apply, saving the output of querysettings to a text file and uploading it.

Anyway. I'm now at the same point as my BSOD from yesterday. Exact same output as the verifierB.txt file when it crashed. 13 test checked, same list of driver. And somehow, it works perfectly fine now.

zbook · Dec 28, 2025

Please make sure that share links are posted for all steps / tests.

Dunge · Dec 28, 2025

Ok one mistake from my part was when selecting drivers and sorting by provider in the list I was only selecting the top portion and stopped at Microsoft, forgetting the ones coming after (which includes nvidia/realtek/steelseries and a few others).

I did the same set of 13 tests with them checked and it worked fine. So did another batch of nearly all tests (except the last group) and it crashed. This time I let the BSOD idle for about 30 minutes hoping it would finish, but it stayed at 100% without ever finishing. STOP code DRIVER_VERIFIER_DETECTED_VIOLATION (of course). It then refused to reboot correctly and crashed a few times until I managed to enter safe boot with command prompt and disabled the tests.

Fortunately I do see a new crash dump was created. So I executed the log v2 tool again. Link : VL-RD-19-(2025-12-28_18-30-13).zip

I also then reproduced the verifier test list so I could take an output of the querysettings (attached to this post).

I assume you'll say it's too many tests, and I should start again from scratch and go block by block. I believe the crash only happen with a combination of different blocks are selected simultaneously.

But hopefully this new crash dump will give something to analyze. I'm not sure if it's included in the v2 bundle or not, if I need to upload it independently.

zbook · Dec 28, 2025

1) Please open administrative PS and copy and paste:

Code:

Compress-Archive -Path "$env:homeDrive\Windows\MEMORY.DMP" -DestinationPath "$env:homeDrive$env:homePath\Desktop\Memory_dmp"

Post a share link.

2) Restart WDV with these customized tests:

Code:

    [ ] (0x00008000) Power framework delay fuzzing
    [ ] (0x00010000) Port/miniport interface checking
    [ ] (0x00040000) Systematic low resources simulation
    [ ] (0x00800000) Kernel synchronization delay fuzzing
    [ ] (0x02000000) Code integrity checks

Stuck in Windows11 23H2 with "pending reboot"

New member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

New member

Attachments

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer