HP Omnibook with Snapdragon X Elite (on ARM) - Restarting Randomly

zbook · Aug 24, 2024

Are the "tests" supposed to just be putting it into safe mode and running those commands?

7) Learn the methods to recover from BSOD caused by WDV by booting into safe mode and running one or more of these commands:

verifier /reset

verifier /bootmode resetonbootfail

Enable and Disable Driver Verifier in Windows 10

How to Enable and Disable Driver Verifier in Windows 10

www.tenforums.com

zbook · Aug 24, 2024

No idea how to "test all microsoft drivers" or "all non-microsoft drivers". Again I guess I selected all non-microsoft drivers.

Please see the tutorial images.

androiddigest · Aug 24, 2024

zbook said:
c) For the first run of WDV select the 3 customized tests displayed in the TF tutorial

Enable and Disable Driver Verifier in Windows 10

How to Enable and Disable Driver Verifier in Windows 10

www.tenforums.com

I appreciate you taking your time, again, it means a lot, but these very quick answers are leaving me confused, and I think would leave many confused.

1: When you say "test". What do you mean? Again, I know how to turn driver verifier on. I know how to select all windows and non-windows drivers. But again, I've seen 0 tests to run.

There are 0 customized tests in that tutorial that I'm seeing. The tutorial only tells you how to get into driver verifier and turn it off. That's all. And it tells you multiple ways to get in, but that's all I'm seeing in the tutorial you posted.

I am seeing the two things to do in safe mode, again, not listed in the tutorial you just linked in your post, but I Can do those two safe mode tests.

I can also do the verifier /querysettings. Are those the 3 tests you're referring to?

I appreciate the time that went into tutorials, but there are some things that still aren't explained. I'm told to run tests but the link you give me to run tests just says to start driver verifier. Again, so some clarification would help.

Now I know you also shared to do this:
2) Whenever the WDV tool is started if there is no immediate BSOD then open administrative command prompt and copy and paste:

verifier /querysettings

And ran it in command prompt. Again, nothing saved that I'm aware of, I don't have a file to share, if there is, I don't know where it would save. But if I knew the location, I'd be happy to share asap!!!

Again, you are a hero for helping. Thank you.

PS: One last addition: Maybe a good idea to edit the tutorial because nowadays, getting into safe mode is a lot more challenging, and typically involves adding in a code from microsoft's bitlocker. Just a heads up.

androiddigest · Aug 24, 2024

So I never had a blue screen of death "caused" by driver verifier.

Either way, I did go into safe mode, it had the same issues I had earlier with safe mode (it was pretty much frozen unless clicked on the taskbar and "ended" whatever was running. Immediately it would let me run things (for a second) so I ran the commands below:

"7) Learn the methods to recover from BSOD caused by WDV by booting into safe mode and running one or more of these commands:

verifier /reset

verifier /bootmode resetonbootfail"

I restarted as it told me to do.

Nothing happened. No blue screen of death. No blue screen of death on driver verifier, no blue screen of death in safe mode, or on my desktop.

Are these the tests I was supposed to do? If so am I supposed to do this same thing with the Windows drivers? Just trying to figure out what to do, and it feels like I'm not understanding what we are intending to do at this point. From what I understand we are trying to work the drivers harder to get a blue screen of death, but not sure those commands would do it? So not sure how we "test" those things.

zbook · Aug 24, 2024

androiddigest said:
1: When you say "test". What do you mean? Again, I know how to turn driver verifier on. I know how to select all windows and non-windows drivers. But again, I've seen 0 tests to run.

Check the following options:

I/O Verification
Force pending I/O requests
IRP logging

androiddigest said:
There are 0 customized tests in that tutorial that I'm seeing. The tutorial only tells you how to get into driver verifier and turn it off. That's all. And it tells you multiple ways to get in, but that's all I'm seeing in the tutorial you posted.

See above.

androiddigest said:
I am seeing the two things to do in safe mode, again, not listed in the tutorial you just linked in your post, but I Can do those two safe mode tests.

No, tests are not run in safe mode.

The WDV tool is turned off after a BSOD by booting into safe mode.

4: At the Command Prompt type the command below you want to use and hit enter. Reboot the PC for the changes to take effect.

verifier /reset

OR

verifier /bootmode resetonbootfail

androiddigest said:
I can also do the verifier /querysettings. Are those the 3 tests you're referring to?

9) Whenever the WDV tool is started if there is no immediate BSOD then open administrative command prompt and copy and paste:

verifier /querysettings

Post a share link.

androiddigest said:
Now I know you also shared to do this:
2) Whenever the WDV tool is started if there is no immediate BSOD then open administrative command prompt and copy and paste:

verifier /querysettings

And ran it in command prompt. Again, nothing saved that I'm aware of, I don't have a file to share, if there is, I don't know where it would save. But if I knew the location, I'd be happy to share asap!!!

Take pictures > post images or share links

androiddigest said:
PS: One last addition: Maybe a good idea to edit the tutorial because nowadays, getting into safe mode is a lot more challenging, and typically involves adding in a code from microsoft's bitlocker. Just a heads up.

Boot to Advanced Startup (WinRE) in Windows 11

This tutorial will show you how to boot to the advanced startup (WinRE) in Windows 11. The Windows Recovery Environment (WinRE) is a companion operating system installed alongside Windows 11, typically in a separate partition, that can help with troubleshooting, recovery, or booting from...

www.elevenforum.com

androiddigest · Aug 24, 2024

zbook said:
Check the following options:

I/O Verification

Force pending I/O requests

IRP logging

See above.

No, tests are not run in safe mode.

The WDV tool is turned off after a BSOD by booting into safe mode.

4: At the Command Prompt type the command below you want to use and hit enter. Reboot the PC for the changes to take effect.

verifier /reset

OR

verifier /bootmode resetonbootfail

9) Whenever the WDV tool is started if there is no immediate BSOD then open administrative command prompt and copy and paste:

verifier /querysettings

Post a share link.

Take pictures > post images or share links

Boot to Advanced Startup (WinRE) in Windows 11

This tutorial will show you how to boot to the advanced startup (WinRE) in Windows 11. The Windows Recovery Environment (WinRE) is a companion operating system installed alongside Windows 11, typically in a separate partition, that can help with troubleshooting, recovery, or booting from...

www.elevenforum.com

It sounds like the test is just to turn on driver verifier. Check those options whenever turning it on, select the correct drivers, and reboot, and see if a blue screen of death immediately happens. If it doesn't, I verifier /querysettings and I can take a picture of the results.

Then I do the same for the microsoft drivers and test it that way. I think that's what I'm supposed to do. Thank you for explaining. If I'm off let me know. Otherwise I'll be running these and posting back shortly.

androiddigest · Aug 24, 2024

Screenshot 1-3 here show what I'm seeing in command prompt, with all non-microsoft drivers.

zbook · Aug 24, 2024

Restart WDV with these customized tests:

Code:

    [ ] 0x00000001 Special pool.
    [ ] 0x00000002 Force IRQL checking.
    [ ] 0x00000008 Pool tracking.
    [ ] 0x00000010 I/O verification.
    [ ] 0x00000020 Deadlock detection.
    [ ] 0x00000080 DMA checking.
    [ ] 0x00000100 Security checks.
    [ ] 0x00000800 Miscellaneous checks.
    [ ] 0x00002000 Invariant MDL checking for stack.
    [ ] 0x00004000 Invariant MDL checking for driver.

androiddigest · Aug 24, 2024

zbook said:

Restart WDV with these customized tests:

Code:

    [ ] 0x00000001 Special pool.
    [ ] 0x00000002 Force IRQL checking.
    [ ] 0x00000008 Pool tracking.
    [ ] 0x00000010 I/O verification.
    [ ] 0x00000020 Deadlock detection.
    [ ] 0x00000080 DMA checking.
    [ ] 0x00000100 Security checks.
    [ ] 0x00000800 Miscellaneous checks.
    [ ] 0x00002000 Invariant MDL checking for stack.
    [ ] 0x00004000 Invariant MDL checking for driver.

androiddigest · Aug 24, 2024

Not to get off track but I did run the same INITIAL test with the Microsoft Drivers only, if you don't need it, feel free to ignore. But I was going off of stuff I thought I saw earlier.

zbook · Aug 24, 2024

Please restart WDV with these customized tests:

Code:

    [ ] 0x00020000 DDI compliance checking.
    [ ] 0x00008000 Power framework delay fuzzing.
    [ ] 0x00010000 Port/miniport interface checking.
    [ ] 0x00040000 Systematic low resources simulation.
    [ ] 0x00080000 DDI compliance checking (additional).
    [ ] 0x00200000 NDIS/WIFI verification.
    [ ] 0x00800000 Kernel synchronization delay fuzzing.
    [ ] 0x01000000 VM switch verification.
    [ ] 0x02000000 Code integrity checks.

androiddigest · Aug 24, 2024

zbook said:

Please restart WDV with these customized tests:

Code:

    [ ] 0x00020000 DDI compliance checking.
    [ ] 0x00008000 Power framework delay fuzzing.
    [ ] 0x00010000 Port/miniport interface checking.
    [ ] 0x00040000 Systematic low resources simulation.
    [ ] 0x00080000 DDI compliance checking (additional).
    [ ] 0x00200000 NDIS/WIFI verification.
    [ ] 0x00800000 Kernel synchronization delay fuzzing.
    [ ] 0x01000000 VM switch verification.
    [ ] 0x02000000 Code integrity checks.

zbook · Aug 24, 2024

Restart WDV testing only:

Code:

[ ] 0x00000004 Randomized low resources simulation.

zbook · Aug 24, 2024

If there were no significant performance problems with the prior tests then run all customized tests for 24 - 48 hours.

Then post a new V2 share link and event viewer links:

BSOD - Posting Instructions

BSOD - Posting Instructions This will show you how to help provide needed information about your system and dump files. It will not contain any personal or sensitive information about you or your data. To get better help with your Windows BSOD issue, please read these instructions and follow...

www.elevenforum.com

How to share event logs in case of a computer issue - Your Windows Guide

This article explains how to share Event Logs from the event viewer in case if you have a Windows problem as investigation would help.

www.yourwindowsguide.com

androiddigest · Aug 24, 2024

zbook said:
Restart WDV testing only:

Code:

[ ] 0x00000004 Randomized low resources simulation.

androiddigest · Aug 24, 2024

zbook said:
If there were no significant performance problems with the prior tests then run all customized tests for 24 - 48 hours.

Then post a new V2 share link and event viewer links:

BSOD - Posting Instructions

BSOD - Posting Instructions This will show you how to help provide needed information about your system and dump files. It will not contain any personal or sensitive information about you or your data. To get better help with your Windows BSOD issue, please read these instructions and follow...

www.elevenforum.com

How to share event logs in case of a computer issue - Your Windows Guide

This article explains how to share Event Logs from the event viewer in case if you have a Windows problem as investigation would help.

www.yourwindowsguide.com

A couple of things:

When I ran the test with all of these :

[ ] 0x00020000 DDI compliance checking.
[ ] 0x00008000 Power framework delay fuzzing.
[ ] 0x00010000 Port/miniport interface checking.
[ ] 0x00040000 Systematic low resources simulation.
[ ] 0x00080000 DDI compliance checking (additional).
[ ] 0x00200000 NDIS/WIFI verification.
[ ] 0x00800000 Kernel synchronization delay fuzzing.
[ ] 0x01000000 VM switch verification.
[ ] 0x02000000 Code integrity checks.

That's when I did experience SOME lag. My mouse would lag a little, or I'd have to wait a second for chrome before things started, this was the test that gave me the most issues. But that's all. It still ran fine.

Also, can you simplify what is next for me so I can determine if it's even worth it to troubleshoot moving forward? This was probably 2 hours easily of testing if not more.

androiddigest · Aug 24, 2024

With this one setting still active, while my Google Chrome was still up, I left the room to talk to my wife.

I came back to my computer having nothing on the display and fans running pretty hard. Still doing it. But can't get the display back on

(Referring to the 1 setting you last told me to turn on)

zbook · Aug 24, 2024

See the link in post #25.

androiddigest · Aug 24, 2024

zbook said:
See the link in post #25.

To do what? I did the verifier reset command in the command prompt.

If that's what you're referring to. Then it just needs to restart. Is there something else I'm supposed to do? I know I could boot into safe mode, do I need to do something there at this point?

zbook · Aug 24, 2024

WDV can run in the background.

Run each of these groups of customized tests for approximately 24 hours each:

Code:

    [ ] 0x00000001 Special pool.
    [ ] 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.
    [ ] 0x00002000 Invariant MDL checking for stack.
    [ ] 0x00004000 Invariant MDL checking for driver.
    [ ] 0x00008000 Power framework delay fuzzing.
    [ ] 0x00010000 Port/miniport interface checking.
    [ ] 0x00040000 Systematic low resources simulation.
    [ ] 0x00200000 NDIS/WIFI verification.
    [ ] 0x00800000 Kernel synchronization delay fuzzing.
    [ ] 0x01000000 VM switch verification.
    [ ] 0x02000000 Code integrity checks.

If there are no misbehaving drivers then the next step is hardware testing.

HP Omnibook with Snapdragon X Elite (on ARM) - Restarting Randomly

Well-known member

My Computer

Well-known member

My Computer

Member

My Computer

Member

My Computer

Well-known member

My Computer

Member

My Computer

Member

Attachments

My Computer

Well-known member

My Computer

Member

Attachments

My Computer

Member

Attachments

My Computer

Well-known member

My Computer

Member

Attachments

My Computer

Well-known member

My Computer

Well-known member

My Computer

Member

Attachments

My Computer

Member

My Computer

Member

My Computer

Well-known member

My Computer

Member

My Computer

Well-known member

My Computer

Similar threads