BSOD with screen corruption

zbook · Apr 25, 2026

1) Please temporarily uninstall: Lenovo vantage

acpivpc Lenovo Virtual Power Controller Driver c:\windows\system32\drivers\acpivpc.sys

2) Create a new restore point

3) Restart WDV with these groups of customized tests:

If there is no immediate BSOD then open administrative command prompt and copy and paste:

verifier /querysettings

Post a share link.

For any BSOD post a new V2 share link into the newest post.

Group A:

Code:

    [ ] 0x00000001 Special pool.
    [ ] 0x00010000 Port/miniport interface checking.

Group B:

Code:

    [ ] 0x00008000 Power framework delay fuzzing.

Group C:

Code:

    [ ] 0x00000001 Special pool.
    [ ] 0x00000002 Force IRQL checking.
    [ ] 0x00000008 Pool tracking.
    [ ] 0x00000020 Deadlock detection.
    [ ] 0x00000080 DMA checking.
    [ ] 0x00000100 Security checks.
    [ ] 0x00000800 Miscellaneous checks.
    [ ] 0x00020000 DDI compliance checking.
    [ ] 0x00080000 DDI compliance checking (additional).
    [ ] 0x00000010 I/O verification.
    [ ] 0x00000200 Force pending I/O requests.
    [ ] 0x00000400 IRP logging.
    [ ] 0x00002000 Invariant MDL checking for stack.
    [ ] 0x00004000 Invariant MDL checking for driver.
    [ ] 0x00040000 Systematic low resources simulation.
    [ ] 0x00200000 NDIS/WIFI verification.
    [ ] 0x00800000 Kernel synchronization delay fuzzing.
    [ ] 0x01000000 VM switch verification.
    [ ] 0x02000000 Code integrity checks.

Code:

AcpiVpc.sys  Thu Aug 14 02:51:01 2025 (689D9565)

tony359 · Apr 25, 2026

Thanks - I forgot to mention that the first BSOD which happened about 1 minute after I got safely into Windows, happened when I hit FN-Q which is the Lenovo hotkey to change the power settings. I could see the laptop was struggling a bit because of Verifier so I wanted to switch to a performance mode but the screen got scrambled immediately and I could see a BSOD happening.

One question: once I get back into Windows with Verifier on and no BSOD happened, do I need to

Query verifier settings and save
Reset Verifier
Reboot
Set verifier to new parameters
reboot

Or can I just avoid the "reset/reboot" and just set the new parameter set and reboot?

Thanks

zbook · Apr 25, 2026

If there is a WDV BSOD then turn off the tool with verifier /reset to return to the desktop.

Then run V2 to collect applicable log files.

V2 can run from either normal boot or safe mode but normal boot has more useful files.

New WDV commands or GUI are needed for each new WDV run.

After WDV testing has completed plan to monitor stability / instability for 3 days using

View Reliability History in Windows 11

This tutorial will show you how to view reliability history for your Windows 11 device. The Reliability Monitor provides a system stability overview and details about events that impact reliability. It calculates the Stability Index shown in the System Stability Chart. Reliability Monitor...

www.elevenforum.com

Lenovo vantage can be reinstalled if there was no instability.

tony359 · Apr 25, 2026

Thanks but that is not what I meant, sorry for not being clear.

If there is NO BSOD, once I reset WDV via terminal, do I need to reboot before running the next batch of WDV settings?

zbook · Apr 25, 2026

tony359 said:
Thanks but that is not what I meant, sorry for not being clear.

If there is NO BSOD, once I reset WDV via terminal, do I need to reboot before running the next batch of WDV settings?

A new command should be able to run.
The run command will trigger the next reboot to run WDV.

tony359 · Apr 25, 2026

test results.

Microsoft OneDrive

You didn't say but I used the GUI this time, selecting the tests you listed. I've also selected all drivers.

Last group wasn't a verifier BSOD it was SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

zbook · Apr 25, 2026

Please run:

Code:

[ ] 0x00000001 Special pool.

Code:

[ ] 0x00010000 Port/miniport interface checking.

Code:

    [ ] 0x00000002 Force IRQL checking.
    [ ] 0x00000008 Pool tracking.
    [ ] 0x00000010 I/O verification.
    [ ] 0x00000020 Deadlock detection.
    [ ] 0x00000080 DMA checking.
    [ ] 0x00000100 Security checks.
    [ ] 0x00000800 Miscellaneous checks.
    [ ] 0x00020000 DDI compliance checking.
    [ ] 0x00080000 DDI compliance checking (additional).

.

Code:

    [ ] 0x00000010 I/O verification.
    [ ] 0x00000200 Force pending I/O requests.
    [ ] 0x00000400 IRP logging.
    [ ] 0x00002000 Invariant MDL checking for stack.
    [ ] 0x00004000 Invariant MDL checking for driver.
    [ ] 0x00008000 Power framework delay fuzzing.

Code:

    [ ] 0x00040000 Systematic low resources simulation.
    [ ] 0x00200000 NDIS/WIFI verification.
    [ ] 0x00800000 Kernel synchronization delay fuzzing.
    [ ] 0x01000000 VM switch verification.
    [ ] 0x02000000 Code integrity checks.

Code:

Event[22250]
  Log Name: System
  Source: volmgr
  Date: 2026-04-25T20:00:31.0230000Z
  Event ID: 46
  Task: None
  Level: Error
  Opcode: N/A
  Keyword: Classic,
  User: N/A
  User Name: N/A
  Computer: Yoga
  Description:
Crash dump initialization failed!

tony359 · Apr 25, 2026

While I appreciate your help, where are we with the troubleshooting? Because I've lost count on how many tests I've done. Yes, I know you're not Microsoft but I feel there is a threshold where at some point I'll go out and buy another laptop

What are you seeing? It seems that my Windows is unable to write dumps, can I fix that somehow? The tests we've been running are all the same, just different combinations. What is the purpose of running different sets of tests? I am not questioning, I am asking.

zbook · Apr 25, 2026

We have switched from commands to GUI.

There will be some new and some repeats to get new data after uninstalling Lenovo Vantage.

tony359 · Apr 25, 2026

but you're not telling me anything about the process, what you're seeing, what the purpose of the tests is. Why the secrecy?

zbook · Apr 25, 2026

There are tests that are used to troubleshoot.

Hopefully you have found a method to work around bitlocker.

tony359 · Apr 25, 2026

I have but I'm not sure I am willing to continue forever without any feedback on your end.

I appreciate your help though.

zbook · Apr 25, 2026

The thread was started on

Apr 11, 2026

If you need help then please post results for the GUI commands.

If you no longer need help then the thread can be closed.

tony359 · Apr 26, 2026

I'd love to look more into my issue but I'd like some feedback while we proceed.

zbook · Apr 26, 2026

tony359 said:
I'd love to look more into my issue but I'd like some feedback while we proceed.

Please see posts #26, #29, #49 and #51.

tony359 · Apr 26, 2026

I appreciate you're trying to help me but you gave me very little feedback.

"There are tests that are used to troubleshoot" does not qualify as feedback in my book.

I've done almost 22 separate tests and before doing 5 more tests, I'd like to know more on the process happening behind the scenes.
In post 47 you pasted some text showing the memory dump failed to create but then didn't answer my question on whether that's expected and what you're expecting from further tests.

Without some feedback and understanding it's difficult for me to justify spending more time blindly running WDV tests.

zbook · Apr 26, 2026

The WDV tool is designed to find misbehaving drivers.

The customized tests are modified as needed.

The customized tests are being modified to get useful results.

If you're able to plan to use the tool as needed to find the misbehaving drivers then we can make quicker progress.

Nothing has changed.

tony359 · Apr 26, 2026

zbook, I know what WDC does and I know we are testing drivers to see if we can find a misbehaving one.

I've been diligently following your instructions, I would like some feedback. Why are we testing different combinations, what did you see in the logs I sent you that made you issue a different combination. Why am I testing [ ] 0x00000001 Special pool and on next test I'm testing [ ] 0x00010000 Port/miniport interface checking. What is the rationale behind that decision.

You posted

Code:

Event[22250]
  Log Name: System
  Source: volmgr
  Date: 2026-04-25T20:00:31.0230000Z
  Event ID: 46
  Task: None
  Level: Error
  Opcode: N/A
  Keyword: Classic,
  User: N/A
  User Name: N/A
  Computer: Yoga
  Description:
Crash dump initialization failed!

What did you want to say with that? Highlight that the system was unable to write a crash dump? Is that expected? Is that something that I could fix? Is that affecting the type of WDV tests we are running and why?

Some Feedback, if you please.

zbook · Apr 26, 2026

Let's close the thread so that you can open a teaching thread.

tony359 · Apr 27, 2026

Guess I poked a sensitive area here

BSOD with screen corruption

Well-known member

My Computer

Well-known member

My Computers

Well-known member

My Computer

Well-known member

My Computers

Well-known member

My Computer

Well-known member

My Computers

Well-known member

My Computer

Well-known member

My Computers

Well-known member

My Computer

Well-known member

My Computers

Well-known member

My Computer

Well-known member

My Computers

Well-known member

My Computer

Well-known member

My Computers

Well-known member

My Computer

Well-known member

My Computers

Well-known member

My Computer

Well-known member

My Computers

Well-known member

My Computer

Well-known member

My Computers

Similar threads