That's good news.
Looks like the situation is as follows then, there are some drivers running while you're booting. They interact with Microsoft drivers to run some processes, but whatever data they pass to the Microsoft drivers isn't good to the point that it can potentially cause crashes as driver verifier identified it as problematic.
From your FRST logs, we have a few driver candidates. There are more than these drivers running at boot, but they're developed by Microsoft, so I excluded them.
- Veracrypt (Veracrypt software)
- mrigflt (Macrium Reflect software)
- mrcbt (Macrium Reflect software)
- EUDCPEPM (EaseUS software)
- EPMVolFl (EaseUS software)
For the EaseUS software I don't know what version you're on, but Macrium and Veracrypt look like they can be updated. However, the safest bet would be to temporarily remove the software and thereafter I would recommend reconfiguring driver verifier to include those Microsoft drivers again that have been excluded and see if a crash occurs at boot or not. We need driver verifier to not cause crashes before considering the update again.