Windows Vista Hogging 51% CPU all the time

I am having the problem of windows vista taking up 51% CPU all the time once
it startups

The Process that is hogging up the cpu is explorer.exe

I tried to look further into it using Process Explorer and it showed
SHLWAPI.dll!Ordinal629+0x161

Did a Stack for this thread and this is what it shows:

ntkrnlpa.exe!KiUnexpectedInterrupt+0x40
ntkrnlpa.exe!KeWaitForMutexObject+0x418
ntkrnlpa.exe!CcSetDirtyPinnedData+0x1147
ntkrnlpa.exe!KiCheckForKernelApcDelivery+0x24
ntkrnlpa.exe!KeReleaseInStackQueuedSpinLockFromDpc Level+0xba2
ntdll.dll!KiFastSystemCallRet
DpoFeedb.dll!gettraceinfo+0xf93
USER32.dll!EnumDisplaySettingsW+0x12c
USER32.dll!PrivateRegisterICSProc+0xb4
USER32.dll!OffsetRect+0x4d
ntdll.dll!KiUserCallbackDispatcher+0x2e
tiptsf.dll!ProcessCaretEvents+0x4f4
USER32.dll!EnumDisplaySettingsW+0x12c
USER32.dll!PrivateRegisterICSProc+0xb4
USER32.dll!OffsetRect+0x4d
ntdll.dll!KiUserCallbackDispatcher+0x2e
USER32.dll!SendMessageW+0x49
Explorer.EXE+0xb81e
Explorer.EXE+0xb83c
Explorer.EXE+0xbe5c
Explorer.EXE+0xd917
Explorer.EXE+0xb8ff
Explorer.EXE+0x77cd
Explorer.EXE+0x1ed0
USER32.dll!GetMessageW+0x6e
USER32.dll!GetMessageW+0x146
USER32.dll!GetMessageW+0x261
USER32.dll!HungWindowFromGhostWindow+0x55
ntdll.dll!KiUserCallbackDispatcher+0x2e
USER32.dll!MsgWaitForMultipleObjectsEx+0xc5
Explorer.EXE+0x1c75
Explorer.EXE+0x1a684
SHLWAPI.dll!Ordinal629+0x1f9
kernel32.dll!BaseThreadInitThunk+0x12
ntdll.dll!LdrInitializeThunk+0x4d


I tried creating a new user acct and deleting the old one.. It does work for
a while but the problem will come back after a few reboot or installation of
files. Anyone has the same problem or a solution to it?

You need to install symbols for, at least, the Operating System components.
A stack trace without reliable symbol information is not helpful. Configure
Process Explorer to download symbols from the MS symbol server and
investigate again. (Check Process Explorer documentation to learn how to do
this.)

Anyway, an Internet search shows that the DLL DpoFeedb.dll is installed by
the following program: C:\Program Files\DigitalPersona. Have you tried to
uninstall it temporarily? Do you have a fingerprint reader?

--
Regards,
Daniel MartÃ*n
Microsoft MVP Windows Desktop Experience


"Jayson" <Jayson@discussions.microsoft.com> wrote in message
news:773469B3-BBC8-412A-8A47-8E4A3EAF2871@microsoft.com...
>I am having the problem of windows vista taking up 51% CPU all the time
>once
> it startups
>
> The Process that is hogging up the cpu is explorer.exe
>
> I tried to look further into it using Process Explorer and it showed
> SHLWAPI.dll!Ordinal629+0x161
>
> Did a Stack for this thread and this is what it shows:
>
> ntkrnlpa.exe!KiUnexpectedInterrupt+0x40
> ntkrnlpa.exe!KeWaitForMutexObject+0x418
> ntkrnlpa.exe!CcSetDirtyPinnedData+0x1147
> ntkrnlpa.exe!KiCheckForKernelApcDelivery+0x24
> ntkrnlpa.exe!KeReleaseInStackQueuedSpinLockFromDpc Level+0xba2
> ntdll.dll!KiFastSystemCallRet
> DpoFeedb.dll!gettraceinfo+0xf93
> USER32.dll!EnumDisplaySettingsW+0x12c
> USER32.dll!PrivateRegisterICSProc+0xb4
> USER32.dll!OffsetRect+0x4d
> ntdll.dll!KiUserCallbackDispatcher+0x2e
> tiptsf.dll!ProcessCaretEvents+0x4f4
> USER32.dll!EnumDisplaySettingsW+0x12c
> USER32.dll!PrivateRegisterICSProc+0xb4
> USER32.dll!OffsetRect+0x4d
> ntdll.dll!KiUserCallbackDispatcher+0x2e
> USER32.dll!SendMessageW+0x49
> Explorer.EXE+0xb81e
> Explorer.EXE+0xb83c
> Explorer.EXE+0xbe5c
> Explorer.EXE+0xd917
> Explorer.EXE+0xb8ff
> Explorer.EXE+0x77cd
> Explorer.EXE+0x1ed0
> USER32.dll!GetMessageW+0x6e
> USER32.dll!GetMessageW+0x146
> USER32.dll!GetMessageW+0x261
> USER32.dll!HungWindowFromGhostWindow+0x55
> ntdll.dll!KiUserCallbackDispatcher+0x2e
> USER32.dll!MsgWaitForMultipleObjectsEx+0xc5
> Explorer.EXE+0x1c75
> Explorer.EXE+0x1a684
> SHLWAPI.dll!Ordinal629+0x1f9
> kernel32.dll!BaseThreadInitThunk+0x12
> ntdll.dll!LdrInitializeThunk+0x4d
>
>
> I tried creating a new user acct and deleting the old one.. It does work
> for
> a while but the problem will come back after a few reboot or installation
> of
> files. Anyone has the same problem or a solution to it?