Upgrading windows 8.1 to windows 10 failing

The settings look good.


Run: verifier /querysettings > post results into the thread


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 ran 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 the 8 customized test settings in the Ten Forums link.

Increase the simultaneous customized test settings by 3 - 5 / hour

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 the 8 customized test settings in the Sysnative link
h) increase the customized test settings over time so that they are similar to the Microsoft link
i) report any performance problems or very slow boot so that the customized settings can be modified
j) Run the Sysnative log collector after any BSOD
 
Here is the verifier output.

The only BSOD I get is at the end of the windows install. Is the verifier running this stress testing in the background until it produces a BSOD?

Thanks
 

Attachments

If there are no performance problems or very slow boot add 5 customized tests similar to those displayed in the Microsoft link:
Driver Verifier-- tracking down a mis-behaving driver.

WDV will stress test the drivers.
The computer can be used as needed (play games, etc.)
If there are no misbehaving drivers after 48 hours then that will complete the testing.

The second Sea Tools link is for a bootable flash drive.
It would interrupt WDV testing.
So it can be ran after the driver stress testing.

The log indicated that ESET is still installed.
It must be completely uninstalled.
 
Last edited:
For Eset, I do a complete uninstall before running each of the windows upgrade attempts. But i need to have virus protection when in between attempts.
I was able to download the sea tools program, i will run it after the 48 hours for the WDV test.

Thanks
 
Please add these customized tests now:

Code: 
[ ] (0x00000010) I/O verification
[ ] (0x00000080) DMA checking
[ ] (0x00000200) Force pending I/O requests
[ ] (0x00000400) IRP logging
[ ] (0x00002000) Invariant MDL checking for stack
[ ] (0x00004000) Invariant MDL checking for driver


If there are no performance problems or very slow boot then add these an hour later:

Code: 
[ ] (0x00040000) Systematic low resources simulation
[ ] (0x00080000) DDI compliance checking (additional)
[ ] (0x00200000) NDIS/WIFI verification
[ ] (0x00800000) Kernel synchronization delay fuzzing
[ ] (0x01000000) VM switch verification


For any BSOD upload the Sysnative log collector results.
 
Here is the sea tool scan.
I will start the other tests.
 

Attachments

  • seatool.JPG
    seatool.JPG
    61.1 KB · Views: 1
Just got BSOD upon restart with the first set of drivers. Screen say collecting error info, but it seems locked as the screen hasn't changed from 0%. Error message says attempted execute of noexecute memory. Should I wait for it to complete or power down to restart?
 

Attachments

  • Bsod.jpg
    Bsod.jpg
    487.3 KB · Views: 5
Got bsod, got into safe mode,did querysettings and reset command. Not sure about the boot mode command is this system32>verifier /bootmode?
 
The bootmode command is used in case the reset command fails to turn off the tool.
(See Ten Forums link)

The querysettings command is used when the tool is started and before a BSOD.

Upload the Sysnative log collector results after each BSOD.
 
Last edited:
One BSOD crash was seen in the logs.
There were no new collected dump files.

Use WDV frequently to create dump files.
The collected dump files can be debugged.

You have flexibility in adding and removing the customized tests.

Add the second group in post #27.

As long as there are no performance problems or very slow boot you can use 19 simultaneous customized tests (all except Randomized low resources simulation)


Code: 
Event[478]:
  Log Name: System
  Source: volmgr
  Date: 2020-10-06T13:12:17.853
  Event ID: 46
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: the-spot
  Description:
Crash dump initialization failed!
 
Last edited:
Windows seems is becoming unstable. boot ups are fine but it will hang up trying to open other apps.
 
The number of simultaneous customized tests can impact performance.
You can add and remove tests as needed.
The goal is to create WDV BSOD crashes with dump files.
The latest BSOD crashes appear to be spontaneous with bugchecks 44 and 50 (per posted images).
So rotate the customized test settings as needed to create more WDV BSOD > run the log collector
 

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

Back
Top