I can only guess but my guess is that the error is coming from a shell extension which is relying on a component or piece of configuration data which is there (or which is writeable) for the admin user but not there (or not writeable) for the power user.
Try using ShellExView, running as the affected account, to disable all shell extensions except for the Microsoft and Opus ones, then logout of the account and log back in with the same account.
More details and other suggestions are here: Crash, exit or high CPU when viewing certain directories.