BSOD INVALID_DATA_ACCESS_TRAP when upgrading Windows 10 to Windows 11

Question

I have a Dell Precision 7550 that I'm trying to upgrade to Windows 11 and I'm getting a BSOD with a stop code of INVALID_DATA_ACCESS_TRAP.

When running setupdiag.exe after Windows 10 is rolled back and operational I get a result that is this:

Error: SetupDiag reports rollback failure found.
Last Phase = Pre OOBE Boot

Last Operation = Start system services for online actions

Error = 0xC1900101-0x40021

LogEntry:

Refer to "https://docs.microsoft.com/en-us/windows/desktop/Debug/system-error-codes" for error information.

Last Setup Phase: Phase Name: Pre OOBE Boot

Phase Started: 1/17/2022 3:54:57 PM

Phase Ended: 1/1/0001 12:00:00 AM

Phase Time Delta: 00:00:00

Completed Successfully? False

Last Setup Operation:

Operation Name: Start system services for online actions

Operation Started: 1/17/2022 3:54:57 PM

Operation Ended: 1/1/0001 12:00:00 AM

Operation Time Delta: 0:00:00:00.0000000

Completed Successfully? False

Where can I look in the logs/which logs to figure out what is causing this?

Answer 1

Sumit,

Thanks for taking a look.

These should be the files you are requesting: https://espatl-my.sharepoint.com/:f:/p/bschroeder/EpyiGJnOvO5Eg45FuzN8ivEBGA6vwH8kZeVLp7sAmAerSQ?e=dSp9xz

Answer 2

Hi Ben,

SSetupmem.dmp should tell the root cause.

Via the article:

Troubleshoot Windows 11 upgrade and Installation errors - Microsoft Community

https://answers.microsoft.com/en-us/windows/forum/all/how-to-troubleshoot-windows-11-upgrade-and/ebf722db-701d-460f-985f-35c4b71383e7

Let us check the following Logs to investigate why the upgrade to Windows 11 failed. Use a File sharing Website like Onedrive to share the files and post the link in the next response.

C:$Windows.~BT\Sources\Panther: File named Setupact.log records actions in the downlevel and SafeOS phase. As the log can be very large, the setup also creates a file named "Setuperr.log" that only has information about the errors encountered by the Setup to narrow the source of the problem.

C:$Windows.~BT\Sources\Rollback: File named Setupact.log records what happened after the update failed and Windows rolled back to Windows 10. The starting portion of the file may explain what happened and why the update failed.

Supplementary logs if present:

1. Device Install Log in C:/$Windows.~bt\Sources\Rollback\setupapi\setupapi.dev.log

2**.** Setupmem.dmp present in C:$Windows.~BT\Sources\Rollback if the PC BSODed during the process.

These folders may be hidden, so you need to either show the hidden files or paste the path in the Run Dialog box.

How to share diagnostic files/logs on the Microsoft community

https://answers.microsoft.com/en-us/feedback/forum/fdbk_commsite-fdbk_getstart/how-to-share-diagnostic-fileslogs-on-microsoft/f5a03ddd-2ccd-4d2a-b0e9-ab80675cd02c?tm=1581341417760