Event ID 1001 Bugcheck

Coach81 said:

The script unfortunately does not work.

Put the script into the root folder of drive C: and run it there.

Matthew Wai said:

Put the script into the root folder of drive C: and run it there.

Still a no go unfortunately.

Coach81 said:

Still a no go unfortunately.

Please run the script attached below and see whether an error message will be displayed.

Matthew Wai said:

Please run the script attached below and see whether an error message will be displayed.

No error messages

2 pauses followed by a key press prompt.

There are definately DMP files in the folder - almost as if the programme doesnt detect them. Not sure to be honest.

Coach81 said:

2 pauses followed by a key press prompt.

I need your help to pinpoint the problem. Please run the attached script and see how many pauses there will be.

Matthew Wai said:

I need your help to pinpoint the problem. Please run the attached script and see how many pauses there will be.

It gets up to 6 pauses then after the 6th key prompt the script window closes.

Read these links on Windows driver verifier:

a) learn how to use the Windows Recovery Environment (RE) commands: reset and bootmode to turn off the tool

b) do not use the tool until it is communicated in the thread


Enable and Disable Driver Verifier in Windows 10
https://answers.microsoft.com/en-us/...3-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 the 3 customized test settings in the Ten Forums link.

Increase the simultaneous customized test settings by 3 - 5 / 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 the 3 customized test settings in the Ten Forums link
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

Regarding the links that were sent:

Under the "create custom settings" section, the one link says to check everything except two options while the other only has a few selected.

Will both scenarios be ok depending what was picked?

In any case havnt run it yet - will only do so if absolutely necessary.

Havnt had a BSOD in a few days now but still trying to properly upload the liverkernel dump files.

When using WDV start with the TF link with 3 customized settings.

The customized settings will be modified if there are no major performance problems or problems related to very slow boot.

If there are no major problems the 3 customized settings are to be increased up to the 19 in the Microsoft link.

The customized test settings can be modified as needed.

When there are BSOD you can wait for the next one or you can stress test the system to see if they occur.

If you wait then the BSOD can occur at an unexpected time.

Stressing testing the system can find misbehaving drivers that can be replaced or uninstalled.

zbook said:

When using WDV start with the TF link with 3 customized settings.

The customized settings will be modified if there are no major performance problems or problems related to very slow boot.

If there are no major problems the 3 customized settings are to be increased up to the 19 in the Microsoft link.

The customized test settings can be modified as needed.

When there are BSOD you can wait for the next one or you can stress test the system to see if they occur.

If you wait then the BSOD can occur at an unexpected time.

Stressing testing the system can find misbehaving drivers that can be replaced or uninstalled.

Thank you for the clarification.

Should i now proceed with WDV or should i just wait?

The problem with my BSOD is that it is too random - i can go weeks without it then all of a sudden it comes in a wave.

I understand how to use WDV a bit better just unsure if i should go ahead.