Post problem reports here for Batch files for use in BSOD debugging

zbook said:

I've got to learn how @Ztruker has been managing modifications.
He may send PM using EF.

Many of the scripts have comments related to TF.
At some point all of the scripts will need modification for EF.

At some time I'll need to review the partitioned LOGS PS1 too.

Clean out you PM queue here on tenforums please so I don't have to jump back and forth between ten and eleven forums.


I'll see if I can come up with a tutorial on updating an existing batch file. It takes a couple steps so I'll try to record them and send them to you.

Hmmmm, actually, I can't that now that I no longer own the forum. I'll see if I can remember the steps and describe them.

Edit: Maybe we should have made Matthew the owner since he already knows how to edit the batch files. I can't get into edit mode so I can't describe the steps needed to replace an existing batch file with a new version. Thoughts?

Basically you need go into Edit mode by going to the bottom of the section for the batch file, then delete the existing batch file in the Manage files area.
Then upload the updated batch file and change the link in the download section (see below) to point to the newly upload batch file.



Then go to the top and change the date info here:



I think that's it. If any problems, contact @Brink as he's a wizard on this.

zbook said:

Isn't it possible to perform debugging on Windows servers, Windows 7, Windows 8, Windows 11, etc. even though the installed Windows is 10?


I've freed up some TF PM entries.

Windows Q and later Eleven Forum were developed with new webpages.
The new style is nice as there are unlimited PMs.
They no longer need to be monitored for possible fills.

Note that:



- - - Updated - - -

Matthew Wai said:

Use VirtualBox.

Or much better, Hyper-V. (because @zbook has a Pro version.)

This was the result with the new script:

Code:

Creation date and time  Size (MB)          File path
----------------------  ---------    -----------------------------
2028-01-02 8:39:49 PM   675.17      C:\WINDOWS\LiveKernelReports\WFP-20280102-2039.dmp

Note: 1 dump file(s) has/have been zipped.

This was the result that had been saved on this computer:

Code:

Creation date and time  Size (MB)          File path
----------------------  ---------    -----------------------------
2028-01-02 8:39:49 PM   675.17      C:\WINDOWS\LiveKernelReports\WFP-20280102-2039.dmp

Note: 0 dump file(s) has/have been zipped.

How come the new script is saving the file when it is dated 2028?
Isn't it a 30 day look back for the saved dump files?


This is a new thread for the preliminary vetting the TF BSOD scripts:
https://www.tenforums.com/vip/190694...ml#post2374013