Windows 11 21h2 upgrade to latest version errors and bsod (0x80070002, 0xc1900101-0x30017)
- Thread starter polo23
- Start date
yeah i tried verifier /reset also it didn't work only the system restore worked glad I make a restore point yesterday before starting
Hi for some reason didn’t see your reply
Okay so you say not to check the microsoft drivers that are specified in the post you sent me?
- Wdf01000.sys
- ndis.sys
- fltMgr.sys
- Storport.sys
They're not microsoft drivers are they, so you can include them too.
Well, except those starting with dump_*.sys, they can be left alone.
It looks like you didn't specify any settings, please specify the ones mentioned in the driver verifier instructions and re-enable driver verifier.
here I'm doing this now -They're not microsoft drivers are they, so you can include them too.
Well, except those starting with dump_*.sys, they can be left alone.
It looks like you didn't specify any settings, please specify the ones mentioned in the driver verifier instructions and re-enable driver verifier.
DDI Compliance Checking (Additional) also enabled here
i am doing this now
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.
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.
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.
so Just uninstall this programs?
hi do you have time to check the issue?
Can you provide the setuperr.log and setupact.log like you did before, and please also run driver verifier with the original settings meaning the mentioned Microsoft drivers in the driver verifier instructions enabled too. Keep it running for about 24 hours and use your computer like you normally would, do not attempt upgrading meanwhile.