The INVALID DATA ACCESS TRAP bugcheck, which has a value of 0x4, occurs when a Windows upgrade fails due to an incompatible driver.

In most cases, this BSOD results from problematic third-party media drivers. As such, uninstalling the faulty software will resolve this error in most cases.

If you may’t upgrade despite that, we’ve also detailed otherways to resolve BSODerror in this article.

uninstall-obs

How to Fix INVALID DATA ACCESS TRAP

We recommend trying the first two methods, as they will most likely resolve the issue. In case they don’t, you may analyze the dump file to get further information.

Remove Media Software

Most users have reported third-party capture software like AVerMedia Capture, PowerDVD, OBS Studio, etc., as the cause of this BSOD. Uninstalling such software allowed them to proceed with the upgrade without any issues, so we recommend that you do the same with the following steps:

Uninstalling the softwarewill remove the corresponding driver, which resolves the issue. But do note that if a separate driver update is available from the manufacturer, installing said update could be another way to fix the problem. Additionally, using an older stable software/driver version could also do the same.

hide-all-microsoft-services-to-clean-boot

Clean Boot and Upgrade

Certain third-party services could also be the reason for this BSOD. We recommend clean booting and trying to update, and if it does work, you may always re-enable the services afterward. Here’s how you can do so:

Install Pending Updates

Some users were also able to resolve this BSOD byinstalling all pending updatesbefore upgrading. Here’s how you may do the same:

Numerous log files are created during the Windows Upgrade process. These are very helpful for diagnosing upgrade issues.

setupact-log

Thesetupact.logfile from the$Windows.~BT\Sources\Pantherdirectory will be most helpful. The log file from$Windows.~BT\Sources\Rollbackis more generic, but it may still be worth analyzing as a second resort.

Although this won’t be as helpful, you could also check the Event Viewer logs for further information. Here’s how you may do this:

event-viewer-system-logs

event-viewer-bugcheck

event-viewer-bugcheck-details

open-dump-file-1024x821

windbg-analyze-1024x614