The stacks are the important part (once the high-CPU thread(s) have been identified), so you were right the first time and Abr was just confusing matters. 
The three stacks in the root post all go through mf.dll, which is the Windows Media Foundation DLL. That, and the fact the file information thread isn't finishing, suggests the problem is triggered by a video file below the directory you are looking at, and may be a bug in a video codec/splitter which cannot process that file properly.
The Crash, exit or high CPU when viewing certain directories guide has suggestions which might help narrow things down.