Re: Tutorial creating & using Hirens Boot CD & MemTest86 diagnostic stress testing tools for USB boot to Windows 10 PE & WinXPmini on BIOS & UEFI

UPDATE <https://i.postimg.cc/HnY00z47/winbsod01b.jpg>

Got my first BSOD since 9/26 when I awoke this morning:
o Your device ran into a problem and needs to restart. 
o We're just collecting some error info, and then you can restart.
o 100% complete
o Unexpected kernel mode trap
  <https://i.postimg.cc/HnY00z47/winbsod01b.jpg>

Machine runs 24/7 with sleep, hibernate, fastboot all turned off
o Also disabled are reboot-after-crash & reboot after update

That way, I get the information from the BSOD screen
o And the machine doesn't restore to older RPs without me knowing it

All drivers have been updated to the latest I can possibly find:
o <https://i.postimg.cc/CKjgVNKK/driver16.jpg>

I shut down the machine to a cold state (light off the motherboard & PS)
o Then I shuffled the 4 memory cards, outside to middle, middle to outside

Then I did the cold reboot process with monitors on the power strip
o And the machine booted to the login prompt without argument

I immediately created a new restore point, so that I know where I was:
o Win+R > systempropertiesprotection > [Create]

I then ran "WhoCrashed", but it only sees the crash dumps from 9/26.
o Next I ran BlueScreenView, which also only sees the 9/26 crash logs.

Why doesn't this new BSOD today create a crash log file?

Let's check the "automatic memory dump" settings:
Win+R > systempropertiesadvanced > Startup and Recovery > [Settings]
 Default Operating system: 
  [Windows 10]
 System startup:
  [x]Time to display list of operating systems [10]seconds
  [x]Time to display recovery options when needed [30]seconds
 System failure:
  [x]Write an event to the system log
  [_]Automatically restart
 Write debugging information
  [Automatic memory dump]
 Dump file:
  [%SystemRoot%\memory.dmp]
  [_]Overwrite any existing file
  [x]Disable automatic deletion of memory dumps when disk space is low

Maybe I need to have checked the "overwrite" button?
o I would have presumed it can make a new one next to it?

For now, I checked the overwrite button...
o Whenever I get a crash log, I can manually copy it to a safe place

I ran these move commands to ensure the log name is available:
o Win+R > cmd {control+shift+enter}
o move %SystemRoot%\memory.dmp c:\data\sys\bsod\20200925_memory.dmp
o move %SystemRoot%\Minidump\092520-31906-01.dmp c:\data\sys\bsod\.
o move %LocalAppData%\crashdumps\*.dmp c:\data\sys\bsod\.

I decided to change my page size from the default 2.5GB managed by Windows 
to more than my memory (> 16GB) just in case that will help gather info.

Win+R > systempropertiesadvanced > Performance > [Settings] > [Advanced]
   Virtual memory Total paging file size for all drives: 2432 MB [Change]
   [x]Automaticaly manage paging file size for all drivers
      Uncheck that... and select
      (o)Custom size
      Initial size (MB): 9216
      Maximum size (MB): 9216
      (it says I need to reboot.)

As usual, I ran these obligatory steps after the BSOD:
1. sfc /scannow (should take about 10 minutes for the first run) 
   Windows Resource Protection did not find any integrity violations.
2. sfc /scannow (should take about 4 minutes for the second run)
3. sfc /scannow (should take about 4 minutes for the third run)
4. Dism /Online /Cleanup-Image /CheckHealth (should take 5 seconds)
   No component store corruption detected.
5. Dism /Online /Cleanup-Image /ScanHealth (should take about 13 minutes)
6. Dism /Online /Cleanup-Image /RestoreHealth should take about 10 minutes)
7. sfc /scannow (should take about 7 minutes for this last run)
8. chkdsk /f /r C:
9. shutdown.exe /r /f /t 5 /c "Reboot in 5 seconds"