Explorer.exe crash loop, combase / OneDrive

Hi,

I know this isn't a BSOD, but I definitely need y'all's dump analysis skills on this problem. I'm posting this on behalf of my twin while I troubleshoot and try to fix this issue for him. I've come to a standstill now and can't proceed - I'm not sure what the source of the problem is. The problem was described to me as the computer 'flickering', but I've determined through logs that, since April 3, explorer.exe has been stuck crashing and restarting a couple of times a second. taskkill /im explorer.exe does successfully prevent explorer from turning back on, which allows me to troubleshoot on the computer without focus being continually lost while typing etc.

I've browsed the event logs and analyzed a full dump of the crash. The closest thing I can guess is that it's related to OneDrive and its FileSyncShell64 library. He's getting an invalid pointer read error when explorer loads the library. Attached is a copy of the event logs, the crash dump, and the msinfo32 NFO file. I ran the DM log collector on his computer, but no files were created, so I generated the NFO manually in case it helps.

Potential relevant information:

• sfc /scannow crashes (at 37% if that means anything to you) on any run.
• Explorer.exe does not crash on other users (e.g. his separate Administrator account)
• As long as explorer has been killed, he can use the computer mostly as normal (no file browsers, start bar, or related hotkeys, but everything else is clear as expected)

Please let me know if there's anything else I can provide to help. I'm honestly clueless on where to go from here.


Event log files:
Selected Events.evtx - Google Drive

Explorer.exe crash dump:
explorer.exe.12560.zip - Google Drive

MSInfo32 NFO:
MSINFO32.NFO - Google Drive

Ah yeah. My twin had set that up earlier and checked it out, so I hadn't thought to try it. Just in case, I ran it today and made sure the registry is good. The problem still persists.

Ugh, my apologies, I fell sick the night of posting in the thread and have been swamped between health, school, and work ever since then. I've got the information, but the short answer is that dism failed, and I'm getting an image of Win10 over to him. I'll post the event logs as soon as I'm able.

Here we go. https://drive.google.com/a/techfocus...ew?usp=sharing Contained is a log of the commandline for the DISM command, the event log, and the log file produced by DISM. Creating an image of Win10 on his machine has been failing, so I'm sending him a thumb drive with Win10 that I've created instead.

No luck.