mach327;703624 Wrote:
I have had a similar problem since about noon of yesterday, where
explorer.exe takes up an entire core. According to ProcessExplorer, the
thread is the same as mentioned above,
ntdll.dll!RTlIntegerToUnicodeString+0x67

Around the same time as i noticed this, my start menu's recently opened
program list went blank:
http://i233.photobucket.com/albums/e...kstartmenu.jpg

I had recently (that day) downloaded and installed: TeamSpeak Noise and
TeamSpeak Overlay (TSNoise didnt work, uninstalled and deleted it)
neither seems to be the trouble as far as i can tell.

I have tried several fixes that others on other forums and here have
suggested for similar problems, specifically those regarding: disabling
XML file indexing, the Windows zip support mentioned above, and I can't
locate any file that Windows appears to be trying to scan/open
continuously.(even working with ProcessMonitor) (like he
'explorer.exe (ntdll.dll!RtIntegerToUnicodeString+0x67) - Microsoft
Windows Vista Community Forums - Vistaheads'
(http://www.vistaheads.com/forums/mic...ing-0x67.html))

ProcessMonitor including only that thread reveals nothing, and I can't
find any more info or ideas so i decided to post here in case those of
us with this problem can find a common "thread" (i made a funny!) or a
recent install or -something- that might help fix this problem.

Vista Home Premium 32bit with all updates "Automatic Update" installs.
AMD Turion 64x2 1.8Ghz
1 gig ram


Hi all, I've been fighting this identical issue on a Vista 64x machine
for most of the night. Through a process of elimination, research, and
frustrated headbanging, I believe I have identified the problem - at
least for my system. I have all of the above symptoms, but killing the
process does not fix the issue.

Out of curiosity, and frustration, I started prodding around in the
user folders, and found on my user desktop a series of several hundred
1-2k files, with a series of sequential file extensions. It turns out
that 7zip, when given instructions to make a series of connected 100MB
archives of a large file, actually produced several hundred small files
instead. These were invisible on the desktop itself, but visible in the
user/desktop directory.

Thus far I have been going through and manually deleting these (about
10 at the time) which is taking several hours. However, I suspect these
files have caused a glitch in the indexing service, and that has caused
the above DLL to be called improperly.

I will keep you guys updated.


--
strixus