K
kiersten
I have a feeling that if people do answer users asking for
help here what I'm going to hear is "reinstall xp over
itself", but I figured it couldn't hurt to ask anyways!
heehee.
Okay I didn't load any new software or run any clean up
utils of any kind. I was just going from using my
computer normally 1 day and then booted up the next and:
My XP Pro hyperthreading 2.8ghz 512MB RAM desktop now at
boot up the mouse shows the hourglass and won't let me do
anything like open the start menu.
The only thing to do is ctrl-alt-delete and TASK MANAGER
and lo and BEHOLD:
Explorer.exe is running at about 50%. I have the procnt
util and when I do properties of the only expolorer.exe
available that's cpuing at 50% when I go to the threads
tab only 1 thread is using 99% of the 50% CPU cycles and
it says this:
CSWITCHDELTA IS 6082 and
START ADDRESS IS :
ntdll.dll!RtlPcToFileHeader+0x352
CSWTICHDELTA IS 1 and
START ADDRESS IS:
explorer.exe+0xb644
there are a number of others but that top one's the one
the cpu cycles are going on. Then if I choose the STACK
button of that problematic cpu sucker it opens up to:
0 ntdll.dll+0x8090304
1 SHLWAPI.dll!Ordinal75+0x1b
2 SHLWAPI.dll!PathFileExistsW+0x20
3 SHELL32.dll!Ordinal748+0x459
4 SHELL32.dllSHLoadNonloadedIconOverlayIdentifiers+0x1f67
then 5 onward are just like number 4 with different
numbers after the plus which go down to a step 9
WHen I searched the internet for the SHLoadNonloaded crap
nothing but the definition of the function came up. No
error reports.
Finally the last important thing to note is :
If I KILL THE THREAD ITSELF ONLY DIRECTLY (not
explorer.exe just the ntdll.dll!RtlPcToFileHeader crap
then I get my computer back working like normal and can
access everything from the start menu and run apps and
programs.
Obviously booting your computer each time and having to
kill a specific thread is not an optimal way of living
with a computer though!
Has anyone any POSSIBLE CLUE about this insanity??? I've
run full virus-scans and spyware-scans and before I'm
giving up tonight just ran nortons windows problem scanner
and let it fix some things but upon reboot nothing is any
different.
Can anyone help a GRRL GOING CRAZY??!?!?? PLZ??!? thank
you so much for your precious time in responding!
--Kiersten
(respond here or to : xpcrash-hers(at)sneakemail.com )
help here what I'm going to hear is "reinstall xp over
itself", but I figured it couldn't hurt to ask anyways!
heehee.
Okay I didn't load any new software or run any clean up
utils of any kind. I was just going from using my
computer normally 1 day and then booted up the next and:
My XP Pro hyperthreading 2.8ghz 512MB RAM desktop now at
boot up the mouse shows the hourglass and won't let me do
anything like open the start menu.
The only thing to do is ctrl-alt-delete and TASK MANAGER
and lo and BEHOLD:
Explorer.exe is running at about 50%. I have the procnt
util and when I do properties of the only expolorer.exe
available that's cpuing at 50% when I go to the threads
tab only 1 thread is using 99% of the 50% CPU cycles and
it says this:
CSWITCHDELTA IS 6082 and
START ADDRESS IS :
ntdll.dll!RtlPcToFileHeader+0x352
CSWTICHDELTA IS 1 and
START ADDRESS IS:
explorer.exe+0xb644
there are a number of others but that top one's the one
the cpu cycles are going on. Then if I choose the STACK
button of that problematic cpu sucker it opens up to:
0 ntdll.dll+0x8090304
1 SHLWAPI.dll!Ordinal75+0x1b
2 SHLWAPI.dll!PathFileExistsW+0x20
3 SHELL32.dll!Ordinal748+0x459
4 SHELL32.dllSHLoadNonloadedIconOverlayIdentifiers+0x1f67
then 5 onward are just like number 4 with different
numbers after the plus which go down to a step 9
WHen I searched the internet for the SHLoadNonloaded crap
nothing but the definition of the function came up. No
error reports.
Finally the last important thing to note is :
If I KILL THE THREAD ITSELF ONLY DIRECTLY (not
explorer.exe just the ntdll.dll!RtlPcToFileHeader crap
then I get my computer back working like normal and can
access everything from the start menu and run apps and
programs.
Obviously booting your computer each time and having to
kill a specific thread is not an optimal way of living
with a computer though!
Has anyone any POSSIBLE CLUE about this insanity??? I've
run full virus-scans and spyware-scans and before I'm
giving up tonight just ran nortons windows problem scanner
and let it fix some things but upon reboot nothing is any
different.
Can anyone help a GRRL GOING CRAZY??!?!?? PLZ??!? thank
you so much for your precious time in responding!
--Kiersten
(respond here or to : xpcrash-hers(at)sneakemail.com )