First thing to do is see: Crash, exit or high CPU when viewing certain directories
That guide has the most likely solutions to the kind of problem you're seeing. (It's unlikely to be the same was what is in the first post in this thread. I've split this to a separate thread.)
That just tells us it's a thread in dopus.exe so far. The displayed function name is the start address, not the code that is using all the CPU, which could be in another DLL.
You need to use Process Explorer (not Process Hacker), then select the thread, then click the Stack button.