Not your normal BSOD post

jbcarreon123 · Jan 29, 2022

Matthew Wai said:
Please run the following PowerShell command and see whether it will return the same error.

get-winevent -ProviderName "*ChkDsk*" | fl timecreated, message

Powershell:

[COLOR=white]Windows PowerShell[/COLOR]
Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

Install the latest PowerShell for new features and improvements! https://aka.ms/PSWindows

PS C:\Users\jbcarreon123> get-winevent -ProviderName "*ChkDsk*" | fl timecreated, message
get-winevent : There is not an event provider on the localhost computer that matches "*ChkDsk*".
At line:1 char:1
+ get-winevent -ProviderName "*ChkDsk*" | fl timecreated, message
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (*ChkDsk*:String) [Get-WinEvent], Exception
    + FullyQualifiedErrorId : NoMatchingProvidersFound,Microsoft.PowerShell.Commands.GetWinEventCommand

PS C:\Users\jbcarreon123>

jbcarreon123 · Jan 29, 2022

WDV UPDATE:

It seems it slows down my system, that it made it unusable. the CPU is 100% and taken by System Interrupts.

Disabled temporalily (by using System Restore because verifier /reset shows me No settings were changed.), and waiting for @zbook to guide me for the correct options.

Matthew Wai · Jan 29, 2022

jbcarreon123 said:
Rich (BB code):

get-winevent : There is not an event provider on the localhost computer that matches "*ChkDsk*". At line:1 char:1

Please run the following command and see whether the output will include something related to disk check.

Get-WinEvent -ListProvider * | FT -A

jbcarreon123 · Jan 29, 2022

Matthew Wai said:
Please run the following command and see whether the output will include something related to disk check.

Get-WinEvent -ListProvider * | FT -A

Here's a PS log. Might take 2GB ram if I pasted the whole output to here.

Code:

PS C:\Users\jbcarreon123> powershell | Out-File D:\RELDesktop\PS.log
Get-WinEvent -ListProvider * | FT -A
exit
PS C:\Users\jbcarreon123>

Matthew Wai · Jan 29, 2022

@jbcarreon123,

Please run the following commands and see whether they will get some logs.

get-winevent -ProviderName "*DiskDiagnostic"|fl timecreated, message
get-winevent -ProviderName "*Disk Diagnostic"|fl timecreated, message

jbcarreon123 · Jan 29, 2022

Matthew Wai said:
@jbcarreon123,

Please run the following commands and see whether they will get some logs.

get-winevent -ProviderName "*DiskDiagnostic"|fl timecreated, message
get-winevent -ProviderName "*Disk Diagnostic"|fl timecreated, message

Here:

zbook · Jan 29, 2022

WDV stresses the computer.

The computer may become sluggish and have very slow boots while using the tool.

The customized settings can be modified as needed.

Please run administrative command prompt: (post a share link into this thread)

verifier /querysettings

jbcarreon123 · Jan 29, 2022

zbook said:
WDV stresses the computer.

The computer may become sluggish and have very slow boots while using the tool.

The customized settings can be modified as needed.

Please run administrative command prompt: (post a share link into this thread)

verifier /querysettings

Thanks, When I configured verifier, I used
1. Default settings
2. All drivers

That may be the reason why my PC is unusable.

zbook · Jan 29, 2022

Did you run in this sequence:
verifier /reset
verifier /bootmode resetonbootfail
system restore

tomdsr · Jan 29, 2022

Stigg said:
Can someone please explain to me what this thread is about?
I haven't got a clue.

I've tried to read it sober and drunk, and it still doesn't make any sense.
Do I need to take something stronger?

Its simply a discussion about if people notice less bluescreens, and if windows 11 reduces bluescreens some even on unsupported hardware.

jbcarreon123 · Jan 29, 2022

tomdsr said:
Its simply a discussion about if people notice less bluescreens, and if windows 11 reduces bluescreens some even on unsupported hardware.

If the drivers is not malfunctioning on newer versions of Windows.

axe0 · Jan 30, 2022

jbcarreon123 said:
If the drivers is not malfunctioning on newer versions of Windows.

And there is no bug in Windows leading to a crash and there is no hardware problem.

The 0xEF (critical process died) is a good example, doesn't involve drivers yet is a fatal problem usually as a result of a hardware problem.

jbcarreon123 · Jan 30, 2022

zbook said:
Did you run in this sequence:
verifier /reset
verifier /bootmode resetonbootfail
system restore

Verifier /reset shows No settings was changed.
Verifier /bootmode resetonbootfail not works because the system is booting property, but it SLOWS DOWN my system.
I used system restore to go back.

There is no BSOD since yesterday.

zbook · Jan 30, 2022

Please post results for verifier / querysettings

jbcarreon123 · Jan 30, 2022

zbook said:
Please post results for verifier / querysettings

NOTE: After restoring

Code:

C:\Users\jbcarreon123>verifier /querysettings

Verifier Flags: 0x00000000

  Standard Flags:

    [ ] 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.

  Additional Flags:

    [ ] 0x00000004 Randomized low resources simulation.
    [ ] 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.
    [ ] 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.

    [X] Indicates flag is enabled.

  Boot Mode:

    Persistent

  Rules:

    All rules are using default settings

  Verified Drivers:

    None

C:\Users\jbcarreon123>

zbook · Jan 30, 2022

Read these links on Windows driver verifier:

Enable and Disable Driver Verifier in Windows 10

How to Enable and Disable Driver Verifier in Windows 10

www.tenforums.com

https://answers.microsoft.com/en-us/windows/forum/windows_10-update/driver-verifier-tracking-down-a-mis-behaving/f5cb4faf-556b-4b6d-95b3-c48669e4c983

Windows driver verifier is designed to stress test drivers.

If there are misbehaving drivers the computer will crash.

If dump files are created they can be debugged.

Misbehaving drivers are then uninstalled or uninstalled and reinstalled.

The tool is run for approximately 48 hours and then an additional 36 hours after the last BSOD.

If there are no further BSOD this concludes the use of the tool.

After each BSOD you must turn off the tool in order to return to the desktop.

Learn the Windows RE commands reset and bootmode.

These are run in safe mode or safe mode with command prompt.

In case these fail the next option is system restore.

If system restore fails you can restore a backup image or use registry commands.

Start the tool with only 0x00000010 I/O verification.

Increase the simultaneous customized test settings by 1 - 2 / hour up to the 19 customized test settings in the Microsoft link.

There can be performance problems and / or slow boot while using the tool.

If necessary the customized test settings can be modified.

Summary:
a) make a new restore point
b) test all non-Microsoft drivers
c) test no Microsoft drivers
d) after each BSOD use the reset command to turn off the tool
e) if the reset command does not work then use the bootmode command
f) only if both reset and bootmode command fail to turn off the tool then use restore
g) start with only 0x00000010 I/O verification
h) increase the customized test settings up to the 19 customized test settings in the Microsoft link
i) report any performance problems or very slow boot so that the customized settings can be modified

zbook · Jan 30, 2022

Plan to test all drivers.

Modify the customized tests.

Start with only one.

Then increase to two, then three, then four, etc.

If there are performance problems then no longer test one of the customized tests that had ran for three or more hours.

You will decide which tests are added or subtracted.

Make sure that all customized tests except 0x00000004 Randomized low resources simulation are used.

jbcarreon123 · Jan 30, 2022

zbook said:
Read these links on Windows driver verifier:

Enable and Disable Driver Verifier in Windows 10

How to Enable and Disable Driver Verifier in Windows 10

www.tenforums.com

https://answers.microsoft.com/en-us/windows/forum/windows_10-update/driver-verifier-tracking-down-a-mis-behaving/f5cb4faf-556b-4b6d-95b3-c48669e4c983

Windows driver verifier is designed to stress test drivers.

If there are misbehaving drivers the computer will crash.

If dump files are created they can be debugged.

Misbehaving drivers are then uninstalled or uninstalled and reinstalled.

The tool is run for approximately 48 hours and then an additional 36 hours after the last BSOD.

If there are no further BSOD this concludes the use of the tool.

After each BSOD you must turn off the tool in order to return to the desktop.

Learn the Windows RE commands reset and bootmode.

These are run in safe mode or safe mode with command prompt.

In case these fail the next option is system restore.

If system restore fails you can restore a backup image or use registry commands.

Start the tool with only 0x00000010 I/O verification.

Increase the simultaneous customized test settings by 1 - 2 / hour up to the 19 customized test settings in the Microsoft link.

There can be performance problems and / or slow boot while using the tool.

If necessary the customized test settings can be modified.

Summary:
a) make a new restore point
b) test all non-Microsoft drivers
c) test no Microsoft drivers
d) after each BSOD use the reset command to turn off the tool
e) if the reset command does not work then use the bootmode command
f) only if both reset and bootmode command fail to turn off the tool then use restore
g) start with only 0x00000010 I/O verification
h) increase the customized test settings up to the 19 customized test settings in the Microsoft link
i) report any performance problems or very slow boot so that the customized settings can be modified

zbook said:
Plan to test all drivers.

Modify the customized tests.

Start with only one.

Then increase to two, then three, then four, etc.

If there are performance problems then no longer test one of the customized tests that had ran for three or more hours.

You will decide which tests are added or subtracted.

Make sure that all customized tests except 0x00000004 Randomized low resources simulation are used.

Thanks.

Configuring verifier later to:
0x00000010 I/O verification,
and non-Microsoft drivers
in the next 3 hours.

Question: I always shut down my system, to save power. How do I measure the time? Pause the time remaining while on shutdown then resuming the time again if the system booted?

zbook · Jan 30, 2022

The computer was sluggish earlier and there may be one or more customized tests that caused the sluggishness.
You may be able to run 5 to 10 or 15 customized tests at any one time without problems.
So you've got the flexibility to decide which customized tests to run in combination.
The customized tests typically can run in the background while you're using the computer for regular activities.
Plan approximately three hours of testing for each of the customized tests except randomized low resources stimultation.

You can post verifier /querysettings to keep track of what has been completed.

jbcarreon123 · Jan 30, 2022

zbook said:
The computer was sluggish earlier and there may be one or more customized tests that caused the sluggishness.
You may be able to run 5 to 10 or 15 customized tests at any one time without problems.
So you've got the flexibility to decide which customized tests to run in combination.
The customized tests typically can run in the background while you're using the computer for regular activities.
Plan approximately three hours of testing for each of the customized tests except randomized low resources stimultation.

You can post verifier /querysettings to keep track of what has been completed.

Thanks.

Question.
I code and test batch files/PowerShell scripts, with a YouTube video playing in a background. Can this be run with a intensive task? For me it's chrome with a 10 tabs running.