Win32 Services errors and delayed drop down menus

I have 2 problems: Repeated Win32 services errors when starting the computer. And a delay of up to 90 sec when accessing any drop down menu.

 

Hi, kbrei.

If you can provide more details about how you use your computer (such as the applications you normally use and their versions...and whether you are using Windows XP Pro or Home, OEM or retail, and is it SP2 with all hotfixes installed?) we might be able to locate a solution more quickly.

I Googled Win32 services errors when starting the computer and got a bunch of results. However, the first result was a Microsoft Knowledge Base article.

• Microsoft KB894391: You receive a "Generic Host Process" error message after you start the computer, or DBCS attachment file names are not displayed in Rich Text e-mail messages

 

Perhaps Event Viewer will shed some light on your issues.

Instructions About How to Access and Use "Event Viewer ":

• Click Start.
• Right-click My Computer.
• Select "Manage" to open the "Computer Management" window.
  (Event Viewer will be displayed under the "System Tools" directory item.)
• Expand "Event Viewer" and then select "Application ", "Security ", and "System" to view the logs.
• Look for "error" events that occurred around the time your problem occurred. These events will be displayed as icons with either a white X on red background or a black exclamation point on yellow background. In the security section of Event Viewer, events of possible concern are ones that display a padlock icon instead of a key icon.
  Error events that may have occurred during shutdown might also relate to your issue(s).
• Double-click on an individual event to open the "Event Properties" window which shows details about the event.
  • You can use the up/down arrow buttons in the "Event Properties" window to move your focus to other events in the list.
  • Use the button below the up/down arrows to copy the details for an event to your clipboard for pasting elsewhere.
  • Click on the "http://go.microsoft.com/fwlink/events.asp" link in the "Event Properties" window to view more information from Microsoft about the event.

Alternatively, Event Viewer may be accessed as follows.

• Click Start > Run...
• Type [FONT= "Courier New"][SIZE= "3"]eventvwr.msc[/SIZE][/FONT] in the "Open:" field.
• Click the OK button.

EDIT: Perhaps the pull-down menu delays are caused by multiple anti-virus applications running resident in memory as "guards" in the background. Be sure you have only one anti-virus application running in the background. Else, they may "fight" each other for control. Likewise for software firewall and perhaps anti-spyware as well.

EDIT #2: Can you recall any software/hardware changes you may have made immediately prior to the time your problems started occurring? If yes, then I suggest you investigate those.

EDIT #3: If your problems started fairly recently, then perhaps you can use System Restore to revert your computer to the configuration it had before the problems surfaced. If you use System Restore to an earlier date/time, then you'll likely have to reinstall any applications and updates that were applied since that date/time. If System Restore clears up your issue(s), then I suggest you perform those reinstalls one at a time (and create a new System Restore point before each reinstall) and run your computer for awhile (including a few shutdowns and startups) to see if you can reproduce your problems after each reinstall. That may help you identify the culprit.

• Click Start > All Programs > Accessories > System Tools > System Restore

 

I can somewhat eliminate the win32 services error on startup if I uncheck the dumprep 0 -u startup option in the registry. However, I can't get this setting (unchecking the startup option) to hold. After two or three startups, the check is back and so are the win32 services errors along with the drop down menu delays. On hijack this logs, a log that says:

O4 - HKLM\..\Run: [UserFaultCheck] %systemroot%\system32\dumprep 0 -u

occurs if the startup option is not checked.

 

I have XP Home (SP2), all updates and hot fixes. The computer is used large for word processing, Excel, Quickbooks. No new applications have been added or changed. The error log in the event viewer is Faulting application svchost.exe, version 5.1.2600.2180, faulting module unknown, version 0.0.0.0, fault address 0x009a96bc. The link to Microsoft does not help with my two problems.

 

I did some poking around the Internet but I haven't found anything that appears promising.

I noticed you have used HijackThis. Have you also scanned your computer for viruses and other malware with a few reputable scanners and/or reputable online scanning services? If so, then did they detect anything?

==========

Please carefully follow the instructions in this link and then use DebugWiz to generate a program crash dump log and paste it into this thread for us to look at. Looks like we should focus on analyzing a C:\Documents and Settings\All Users\Application Data\Microsoft\Dr Watson\user.dmp file.

I'm fishing for even more details since the svchost error information you have provided so far seems pretty generic. Svchost.exe is typically involved with several processes.

NOTE:

==========

Perhaps Windows XP's System File Checker (SFC) will help you resolve your issue.

• Have your Windows XP CD handy because you may be prompted to insert it into your CD drive during this process.
• Click Start > Run...
• Type [FONT= "Courier New"][SIZE= "3"]sfc /scannow[/SIZE][/FONT] in the "Open:" field.
• Click the OK button.

A "Windows File Protection" window will open and display its progress. If SFC runs successfully without any intervention from you, it will take approximately 15-25 minutes to complete. When SFC completes, the "Windows File Protection" window will simply disappear.

To see any changes that may have been made by SFC after it completes:

• Click Start > Run...
• Type [FONT= "Courier New"][SIZE= "3"]eventvwr.msc[/SIZE][/FONT] in the "Open:" field.
• Click the OK button.
• Click the "System" item on the left side of the "Event Viewer" window.

Any changes made by SFC will be displayed (in reverse order) as "Windows File Protection" events between Event ID 64016 (Windows File Protection started) and 64017 (Windows File Protection completed).

Double-click on an event (or right-click on the event and select "Properties ") to view details about the event. You can use the up/down arrow buttons on the right side of the event's "Properties" window to view details about adjacent events without having to close the event's "Properties" window.

If you want to copy event details to your clipboard (for pasting into Notepad or a forum message, for example), use the button immediately below the up/down arrow buttons in the event's "Properties" window.

 

Sometimes the Context Menu Shell can get corrupted by a program that is not sociable. You can test that by disabling all non-MicroSoft context menu items. That's easy to do and easy to undo by using ShellExView which is freeware. Aside from troubleshooting, it's quite handy for trimming the context menu down when the need arises.

 

Here is the log from Debug:

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

BUCKET_ID: CPU_CALL_ERROR

FAILURE_BUCKET_ID: hardware!Unloaded_c0000005_BAD_INSTRUCTION_PTR

Followup: MachineOwner
---------
*** Possible invalid call from 7c9105c3 ( ntdll!RtlpFreeToHeapLookaside+0x1d )
*** Expected target 7c902f2f ( ntdll!RtlpInterlockedPushEntrySList+0x0 )

eax=00000000 ebx=00000000 ecx=0065eef8 edx=71ac4070 esi=00843784 edi=008437cc
eip=00974cb3 esp=0065ed08 ebp=0065ef04 iopl=0 nv up ei pl nz na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000202
00974cb3 ?? ???
ChildEBP RetAddr Args to Child
WARNING: Frame IP not in any known module. Following frames may be wrong.
0065ed04 7c9105c8 000b0240 0065eddc 009f43a8 0x974cb3
0065ef04 00984f50 000001ac 0065f450 0065ef2c ntdll!RtlpFreeToHeapLookaside+0x22 (FPO: [Non-Fpo])
0065f7a4 7c809a36 0097bbf7 0097bc11 008437cc 0x984f50
0065fa84 1000de63 009f2e98 008437d8 00000005 kernel32!lstrlenW+0x38 (FPO: [Non-Fpo])
0065fcac 75abab9f 0065fadc 008437b8 00000002 hpgwiamd!DllUnregisterServer+0xcd96
0065fcec 75abaf7e 000b958c 00000002 000001a8 wiaservc!CDrvWrap::STI_Initialize+0x35 (FPO: [Non-Fpo])
0065fd20 75ac780f 000001a8 00000000 000affe0 wiaservc!CDrvWrap::LoadInitDriver+0x179 (FPO: [Non-Fpo])
0065fd3c 75ac7b66 00000000 000ae008 00000000 wiaservc!ACTIVE_DEVICE::LoadDriver+0xe8 (FPO: [Non-Fpo])
0065fd5c 75ab8fac 00099cc8 000ba208 000ae008 wiaservc!ACTIVE_DEVICE::ACTIVE_DEVICE+0x148 (FPO: [Non-Fpo])
0065fd8c 75ab99bb 00000005 000ba208 00000fa0 wiaservc!CWiaDevMan::AddDevice+0x45 (FPO: [Non-Fpo])
0065fee8 75aba7ba 00000005 00000040 7c80998d wiaservc!CWiaDevMan::EnumDevNodeDevices+0x33d (FPO: [Non-Fpo])
0065ff10 75ac7e1b 00000004 00094e44 00098ba0 wiaservc!CWiaDevMan::ReEnumerateDevices+0xa9 (FPO: [Non-Fpo])
0065ff54 75ac8330 00000001 00094e40 75aabc84 wiaservc!DoGlobalInit+0x1f0 (FPO: [Non-Fpo])
0065ff6c 010011cc 00000001 00094e40 00000000 wiaservc!ServiceMain+0x28 (FPO: [Non-Fpo])
0065ffa0 77deb48b 00000001 00094e40 0007e898 svchost!ServiceStarter+0x9e (FPO: [Non-Fpo])
0065ffb4 7c80b683 00094e38 00000000 0007e898 advapi32!ScSvcctrlThreadA+0x12 (FPO: [Non-Fpo])
0065ffec 00000000 77deb479 00094e38 00000000 kernel32!BaseThreadStart+0x37 (FPO: [Non-Fpo])
start end module name
00a00000 00a25000 hpzjrd01 hpzjrd01.dll Mon Aug 01 09:29:15 2005 (42EE31BB)
01000000 01006000 svchost svchost.exe Wed Aug 04 01:14:46 2004 (41107ED6)
10000000 10046000 hpgwiamd hpgwiamd.dll Thu Mar 11 11:26:30 2004 (40509336)
20000000 202c5000 xpsp2res xpsp2res.dll Wed Aug 04 02:56:41 2004 (411096B9)
30460000 3047b000 dnsq dnsq.dll Fri Feb 08 10:36:07 2008 (47AC76E7)
5ad70000 5ada8000 uxtheme uxtheme.dll Wed Aug 04 02:56:43 2004 (411096BB)
5b860000 5b8b4000 netapi32 netapi32.dll Thu Aug 17 07:28:27 2006 (44E460EB)
5cb70000 5cb96000 shimeng shimeng.dll Wed Aug 04 02:56:42 2004 (411096BA)
5d090000 5d12a000 comctl32_5d090000 comctl32.dll Fri Aug 25 10:45:58 2006 (44EF1B36)
6f880000 6fa4a000 acgenral acgenral.dll Wed Aug 04 02:55:58 2004 (4110968E)
71a50000 71a8f000 mswsock mswsock.dll Wed Aug 04 02:59:20 2004 (41109758)
71aa0000 71aa8000 ws2help ws2help.dll Wed Aug 04 02:57:39 2004 (411096F3)
71ab0000 71ac7000 ws2_32 ws2_32.dll Wed Aug 04 02:57:38 2004 (411096F2)
73000000 73026000 winspool winspool.drv Wed Aug 04 02:56:38 2004 (411096B6)
73b30000 73b45000 mscms mscms.dll Tue Jun 28 20:46:00 2005 (42C1FD58)
74ae0000 74ae7000 cfgmgr32 cfgmgr32.dll Wed Aug 04 02:56:13 2004 (4110969D)
75aa0000 75af5000 wiaservc wiaservc.dll Tue Dec 19 13:16:47 2006 (45882C8F)
76360000 76370000 winsta winsta.dll Wed Aug 04 02:56:40 2004 (411096B8)
76390000 763ad000 imm32 imm32.dll Wed Aug 04 02:56:30 2004 (411096AE)
76400000 765a6000 netshell netshell.dll Wed Aug 04 02:56:37 2004 (411096B5)
769c0000 76a73000 userenv userenv.dll Wed Aug 04 02:56:41 2004 (411096B9)
76b20000 76b31000 atl atl.dll Wed Aug 04 02:56:55 2004 (411096C7)
76b40000 76b6d000 winmm winmm.dll Wed Aug 04 02:57:10 2004 (411096D6)
76c00000 76c2e000 credui credui.dll Wed Aug 04 02:56:42 2004 (411096BA)
76c30000 76c5e000 wintrust wintrust.dll Wed Aug 04 02:56:41 2004 (411096B9)
76c90000 76cb8000 imagehlp imagehlp.dll Wed Aug 04 02:56:25 2004 (411096A9)
76d60000 76d79000 iphlpapi iphlpapi.dll Fri May 19 07:59:41 2006 (446DC13D)
76e80000 76e8e000 rtutils rtutils.dll Wed Aug 04 02:56:36 2004 (411096B4)
76f20000 76f47000 dnsapi dnsapi.dll Mon Jun 26 12:37:10 2006 (44A01B46)
76fc0000 76fc6000 rasadhlp rasadhlp.dll Mon Jun 26 12:37:10 2006 (44A01B46)
76fd0000 7704f000 clbcatq clbcatq.dll Mon Jul 25 23:39:44 2005 (42E5BE90)
77050000 77115000 comres comres.dll Wed Aug 04 02:56:36 2004 (411096B4)
77120000 771ab000 oleaut32 oleaut32.dll Tue Dec 04 13:38:12 2007 (47559E94)
773d0000 774d3000 comctl32 comctl32.dll Fri Aug 25 10:45:55 2006 (44EF1B33)
774e0000 7761d000 ole32 ole32.dll Mon Jul 25 23:39:47 2005 (42E5BE93)
77920000 77a13000 setupapi setupapi.dll Wed Aug 04 02:56:32 2004 (411096B0)
77a80000 77b14000 crypt32 crypt32.dll Wed Aug 04 02:56:01 2004 (41109691)
77b20000 77b32000 msasn1 msasn1.dll Wed Aug 04 02:57:23 2004 (411096E3)
77b40000 77b62000 apphelp apphelp.dll Wed Aug 04 02:56:36 2004 (411096B4)
77be0000 77bf5000 msacm32 msacm32.dll Wed Aug 04 02:57:03 2004 (411096CF)
77c00000 77c08000 version version.dll Wed Aug 04 02:56:39 2004 (411096B7)
77c10000 77c68000 msvcrt msvcrt.dll Wed Aug 04 02:59:14 2004 (41109752)
77dd0000 77e6b000 advapi32 advapi32.dll Wed Aug 04 02:56:23 2004 (411096A7)
77e70000 77f02000 rpcrt4 rpcrt4.dll Mon Jul 09 08:09:42 2007 (46923396)
77f10000 77f57000 gdi32 gdi32.dll Tue Jun 19 08:31:19 2007 (4677DAA7)
77f60000 77fd6000 shlwapi shlwapi.dll Thu Dec 06 19:44:36 2007 (47589774)
77fe0000 77ff1000 secur32 secur32.dll Wed Aug 04 02:56:49 2004 (411096C1)
7c800000 7c8f5000 kernel32 kernel32.dll Mon Apr 16 10:52:53 2007 (46239BD5)
7c900000 7c9b0000 ntdll ntdll.dll Wed Aug 04 02:56:36 2004 (411096B4)
7c9c0000 7d1d7000 shell32 shell32.dll Thu Oct 25 22:33:59 2007 (47216027)
7e410000 7e4a0000 user32 user32.dll Thu Mar 08 10:36:28 2007 (45F02D7C)
Closing open log file c:\debuglog.txt

 

kbrei,

I assume you used DebugWiz to generate the dump analysis log. If so, then the first part of the dump log is missing from your post.

I expect the additional details you omitted would be helpful for a dump log analysis expert (and, perhaps, the rest of us as well).

Perhaps you have a better idea than us about what information may be helpful in resolving your issue.

I will be leaving town soon for a few days anyway so I am glad surferdude has stepped in with ideas.

Good luck!

 

Here is the entire Debug log.

I have run several different malware and anti spam software and am apparently clean. I use only one Anti Virus program, Kaspersky.

Again, the win32 services error can be eliminated if in the start up registry, the dumprep setting stays turned off. Unfortunately, it doesn't stay turned off. Even with this 'fix', it does not speed up the 90 second delay on any drop down menu.

Opened log file 'c:\debuglog.txt'

Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Documents and Settings\All Users\Application Data\Microsoft\Dr Watson\user.dmp]
User Mini Dump File: Only registers, stack and portions of memory are available

Comment: 'Dr. Watson generated MiniDump'
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS\system32\drivers
Windows XP Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: SingleUserTS Personal
Debug session time: Tue Apr 1 14:35:10.000 2008 (GMT-5)
System Uptime: not available
Process Uptime: 0 days 0:00:32.000
...................................................
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(9b0.c9c): Access violation - code c0000005 (first/second chance not available)
eax=00000000 ebx=00000000 ecx=0065eef8 edx=71ac4070 esi=00843784 edi=008437cc
eip=00974cb3 esp=0065ed08 ebp=0065ef04 iopl=0 nv up ei pl nz na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000202
00974cb3 ?? ???
0:001> !analyze -v;r;kv;lmtn;.logclose;q
*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************

*** WARNING: Unable to verify checksum for hpgwiamd.dll
*** ERROR: Symbol file could not be found. Defaulted to export symbols for hpgwiamd.dll -
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: kernel32!pNlsUserInfo ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: kernel32!pNlsUserInfo ***
*** ***
*************************************************************************

FAULTING_IP:
+974cb3
00974cb3 ?? ???

EXCEPTION_RECORD: ffffffff -- (.exr 0xffffffffffffffff)
.exr 0xffffffffffffffff
ExceptionAddress: 00974cb3
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000008
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 00974cb3
Attempt to read from address 00974cb3

DEFAULT_BUCKET_ID: BAD_INSTRUCTION_PTR

PROCESS_NAME: svchost.exe

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx ". The memory could not be "%s ".

READ_ADDRESS: 00974cb3

FAILED_INSTRUCTION_ADDRESS:
+974cb3
00974cb3 ?? ???

IP_ON_HEAP: 00974cb3

LAST_CONTROL_TRANSFER: from 7c9105c8 to 00974cb3

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
0065ed04 7c9105c8 000b0240 0065eddc 009f43a8 0x974cb3
0065ef04 00984f50 000001ac 0065f450 0065ef2c ntdll!RtlpFreeToHeapLookaside+0x22
0065f7a4 7c809a36 0097bbf7 0097bc11 008437cc 0x984f50
0065fa84 1000de63 009f2e98 008437d8 00000005 kernel32!lstrlenW+0x38
0065fcac 75abab9f 0065fadc 008437b8 00000002 hpgwiamd!DllUnregisterServer+0xcd96
0065fcec 75abaf7e 000b958c 00000002 000001a8 wiaservc!CDrvWrap::STI_Initialize+0x35
0065fd20 75ac780f 000001a8 00000000 000affe0 wiaservc!CDrvWrap::LoadInitDriver+0x179
0065fd3c 75ac7b66 00000000 000ae008 00000000 wiaservc!ACTIVE_DEVICE::LoadDriver+0xe8
0065fd5c 75ab8fac 00099cc8 000ba208 000ae008 wiaservc!ACTIVE_DEVICE::ACTIVE_DEVICE+0x148
0065fd8c 75ab99bb 00000005 000ba208 00000fa0 wiaservc!CWiaDevMan::AddDevice+0x45
0065fee8 75aba7ba 00000005 00000040 7c80998d wiaservc!CWiaDevMan::EnumDevNodeDevices+0x33d
0065ff10 75ac7e1b 00000004 00094e44 00098ba0 wiaservc!CWiaDevMan::ReEnumerateDevices+0xa9
0065ff54 75ac8330 00000001 00094e40 75aabc84 wiaservc!DoGlobalInit+0x1f0
0065ff6c 010011cc 00000001 00094e40 00000000 wiaservc!ServiceMain+0x28
0065ffa0 77deb48b 00000001 00094e40 0007e898 svchost!ServiceStarter+0x9e
0065ffb4 7c80b683 00094e38 00000000 0007e898 advapi32!ScSvcctrlThreadA+0x12
0065ffec 00000000 77deb479 00094e38 00000000 kernel32!BaseThreadStart+0x37


STACK_COMMAND: ~1s; .ecxr ; kb

FAULTING_THREAD: 00000c9c

PRIMARY_PROBLEM_CLASS: BAD_INSTRUCTION_PTR

BUGCHECK_STR: APPLICATION_FAULT_BAD_INSTRUCTION_PTR_CODE_RUNNING_ON_STACK

POSSIBLE_INVALID_CONTROL_TRANSFER: from 7c9105c3 to 7c902f2f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

BUCKET_ID: CPU_CALL_ERROR

FAILURE_BUCKET_ID: hardware!Unloaded_c0000005_BAD_INSTRUCTION_PTR

Followup: MachineOwner
---------
*** Possible invalid call from 7c9105c3 ( ntdll!RtlpFreeToHeapLookaside+0x1d )
*** Expected target 7c902f2f ( ntdll!RtlpInterlockedPushEntrySList+0x0 )

eax=00000000 ebx=00000000 ecx=0065eef8 edx=71ac4070 esi=00843784 edi=008437cc
eip=00974cb3 esp=0065ed08 ebp=0065ef04 iopl=0 nv up ei pl nz na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000202
00974cb3 ?? ???
ChildEBP RetAddr Args to Child
WARNING: Frame IP not in any known module. Following frames may be wrong.
0065ed04 7c9105c8 000b0240 0065eddc 009f43a8 0x974cb3
0065ef04 00984f50 000001ac 0065f450 0065ef2c ntdll!RtlpFreeToHeapLookaside+0x22 (FPO: [Non-Fpo])
0065f7a4 7c809a36 0097bbf7 0097bc11 008437cc 0x984f50
0065fa84 1000de63 009f2e98 008437d8 00000005 kernel32!lstrlenW+0x38 (FPO: [Non-Fpo])
0065fcac 75abab9f 0065fadc 008437b8 00000002 hpgwiamd!DllUnregisterServer+0xcd96
0065fcec 75abaf7e 000b958c 00000002 000001a8 wiaservc!CDrvWrap::STI_Initialize+0x35 (FPO: [Non-Fpo])
0065fd20 75ac780f 000001a8 00000000 000affe0 wiaservc!CDrvWrap::LoadInitDriver+0x179 (FPO: [Non-Fpo])
0065fd3c 75ac7b66 00000000 000ae008 00000000 wiaservc!ACTIVE_DEVICE::LoadDriver+0xe8 (FPO: [Non-Fpo])
0065fd5c 75ab8fac 00099cc8 000ba208 000ae008 wiaservc!ACTIVE_DEVICE::ACTIVE_DEVICE+0x148 (FPO: [Non-Fpo])
0065fd8c 75ab99bb 00000005 000ba208 00000fa0 wiaservc!CWiaDevMan::AddDevice+0x45 (FPO: [Non-Fpo])
0065fee8 75aba7ba 00000005 00000040 7c80998d wiaservc!CWiaDevMan::EnumDevNodeDevices+0x33d (FPO: [Non-Fpo])
0065ff10 75ac7e1b 00000004 00094e44 00098ba0 wiaservc!CWiaDevMan::ReEnumerateDevices+0xa9 (FPO: [Non-Fpo])
0065ff54 75ac8330 00000001 00094e40 75aabc84 wiaservc!DoGlobalInit+0x1f0 (FPO: [Non-Fpo])
0065ff6c 010011cc 00000001 00094e40 00000000 wiaservc!ServiceMain+0x28 (FPO: [Non-Fpo])
0065ffa0 77deb48b 00000001 00094e40 0007e898 svchost!ServiceStarter+0x9e (FPO: [Non-Fpo])
0065ffb4 7c80b683 00094e38 00000000 0007e898 advapi32!ScSvcctrlThreadA+0x12 (FPO: [Non-Fpo])
0065ffec 00000000 77deb479 00094e38 00000000 kernel32!BaseThreadStart+0x37 (FPO: [Non-Fpo])
start end module name
00a00000 00a25000 hpzjrd01 hpzjrd01.dll Mon Aug 01 09:29:15 2005 (42EE31BB)
01000000 01006000 svchost svchost.exe Wed Aug 04 01:14:46 2004 (41107ED6)
10000000 10046000 hpgwiamd hpgwiamd.dll Thu Mar 11 11:26:30 2004 (40509336)
20000000 202c5000 xpsp2res xpsp2res.dll Wed Aug 04 02:56:41 2004 (411096B9)
30460000 3047b000 dnsq dnsq.dll Fri Feb 08 10:36:07 2008 (47AC76E7)
5ad70000 5ada8000 uxtheme uxtheme.dll Wed Aug 04 02:56:43 2004 (411096BB)
5b860000 5b8b4000 netapi32 netapi32.dll Thu Aug 17 07:28:27 2006 (44E460EB)
5cb70000 5cb96000 shimeng shimeng.dll Wed Aug 04 02:56:42 2004 (411096BA)
5d090000 5d12a000 comctl32_5d090000 comctl32.dll Fri Aug 25 10:45:58 2006 (44EF1B36)
6f880000 6fa4a000 acgenral acgenral.dll Wed Aug 04 02:55:58 2004 (4110968E)
71a50000 71a8f000 mswsock mswsock.dll Wed Aug 04 02:59:20 2004 (41109758)
71aa0000 71aa8000 ws2help ws2help.dll Wed Aug 04 02:57:39 2004 (411096F3)
71ab0000 71ac7000 ws2_32 ws2_32.dll Wed Aug 04 02:57:38 2004 (411096F2)
73000000 73026000 winspool winspool.drv Wed Aug 04 02:56:38 2004 (411096B6)
73b30000 73b45000 mscms mscms.dll Tue Jun 28 20:46:00 2005 (42C1FD58)
74ae0000 74ae7000 cfgmgr32 cfgmgr32.dll Wed Aug 04 02:56:13 2004 (4110969D)
75aa0000 75af5000 wiaservc wiaservc.dll Tue Dec 19 13:16:47 2006 (45882C8F)
76360000 76370000 winsta winsta.dll Wed Aug 04 02:56:40 2004 (411096B8)
76390000 763ad000 imm32 imm32.dll Wed Aug 04 02:56:30 2004 (411096AE)
76400000 765a6000 netshell netshell.dll Wed Aug 04 02:56:37 2004 (411096B5)
769c0000 76a73000 userenv userenv.dll Wed Aug 04 02:56:41 2004 (411096B9)
76b20000 76b31000 atl atl.dll Wed Aug 04 02:56:55 2004 (411096C7)
76b40000 76b6d000 winmm winmm.dll Wed Aug 04 02:57:10 2004 (411096D6)
76c00000 76c2e000 credui credui.dll Wed Aug 04 02:56:42 2004 (411096BA)
76c30000 76c5e000 wintrust wintrust.dll Wed Aug 04 02:56:41 2004 (411096B9)
76c90000 76cb8000 imagehlp imagehlp.dll Wed Aug 04 02:56:25 2004 (411096A9)
76d60000 76d79000 iphlpapi iphlpapi.dll Fri May 19 07:59:41 2006 (446DC13D)
76e80000 76e8e000 rtutils rtutils.dll Wed Aug 04 02:56:36 2004 (411096B4)
76f20000 76f47000 dnsapi dnsapi.dll Mon Jun 26 12:37:10 2006 (44A01B46)
76fc0000 76fc6000 rasadhlp rasadhlp.dll Mon Jun 26 12:37:10 2006 (44A01B46)
76fd0000 7704f000 clbcatq clbcatq.dll Mon Jul 25 23:39:44 2005 (42E5BE90)
77050000 77115000 comres comres.dll Wed Aug 04 02:56:36 2004 (411096B4)
77120000 771ab000 oleaut32 oleaut32.dll Tue Dec 04 13:38:12 2007 (47559E94)
773d0000 774d3000 comctl32 comctl32.dll Fri Aug 25 10:45:55 2006 (44EF1B33)
774e0000 7761d000 ole32 ole32.dll Mon Jul 25 23:39:47 2005 (42E5BE93)
77920000 77a13000 setupapi setupapi.dll Wed Aug 04 02:56:32 2004 (411096B0)
77a80000 77b14000 crypt32 crypt32.dll Wed Aug 04 02:56:01 2004 (41109691)
77b20000 77b32000 msasn1 msasn1.dll Wed Aug 04 02:57:23 2004 (411096E3)
77b40000 77b62000 apphelp apphelp.dll Wed Aug 04 02:56:36 2004 (411096B4)
77be0000 77bf5000 msacm32 msacm32.dll Wed Aug 04 02:57:03 2004 (411096CF)
77c00000 77c08000 version version.dll Wed Aug 04 02:56:39 2004 (411096B7)
77c10000 77c68000 msvcrt msvcrt.dll Wed Aug 04 02:59:14 2004 (41109752)
77dd0000 77e6b000 advapi32 advapi32.dll Wed Aug 04 02:56:23 2004 (411096A7)
77e70000 77f02000 rpcrt4 rpcrt4.dll Mon Jul 09 08:09:42 2007 (46923396)
77f10000 77f57000 gdi32 gdi32.dll Tue Jun 19 08:31:19 2007 (4677DAA7)
77f60000 77fd6000 shlwapi shlwapi.dll Thu Dec 06 19:44:36 2007 (47589774)
77fe0000 77ff1000 secur32 secur32.dll Wed Aug 04 02:56:49 2004 (411096C1)
7c800000 7c8f5000 kernel32 kernel32.dll Mon Apr 16 10:52:53 2007 (46239BD5)
7c900000 7c9b0000 ntdll ntdll.dll Wed Aug 04 02:56:36 2004 (411096B4)
7c9c0000 7d1d7000 shell32 shell32.dll Thu Oct 25 22:33:59 2007 (47216027)
7e410000 7e4a0000 user32 user32.dll Thu Mar 08 10:36:28 2007 (45F02D7C)
Closing open log file c:\debuglog.txt

 

Thanks for posting the entire dump log.

I have noticed the "wrong symbols" issue with my own user mode (application) dump logs and I'm fairly certain I have been doing it correctly. Therefore, for now, I am disregarding such "wrong symbols" notices in application dump logs.

I had a hunch about this when I viewed your partial log the other day. I wonder whether your HP printer software is involved or not (because the hpgwiamd.dll and hpzjrd01.dll modules are near the top of your module list).

Please see if updating your HP printer driver/software (or disconnecting and uninstalling your HP printer and associated software) has any effect.

 

If you have an HP scanner connected, then your HP scanner hardware, firmware, or software may be involved.

http://www.liutilities.com/products/wintaskspro/dlllibrary/wiaservc/

Makes me suspect you may have HP scanner hardware/firmware/software that is misbehaving.


EDIT: svchost.exe is Windows' "Generic Host Process for Win32 Services" (involved in the error you have identified).

If I understand correctly "wia" means "Windows Image Acquisition" (which I assume is related to image/document scanners).

 

Ahhh. Good thought on the HP scanner which has been nothing but trouble. Due to ongoing problems with it, the software has been uninstalled/reinstalled a few times. I'll take it off again and see how the computer works. I will be out town for a few days so it may be Monday before I can clearly assess it. Thanks!