WinDbg 6.11.0001.404

I’ve been using for a few days now, and have not had any reall problems
until today. Loading symbols seemingly take forever. An example:

kd> .reload

Connected to Windows 7 7600 x64 target at (Thu Jan 7 14:04:44.136 2010
(GMT-6)), ptr64 TRUE

Loading Kernel Symbols

Loading User Symbols

kd> g

*** ERROR: Module load completed but symbols could not be loaded for
ehdrv.sys

*** ERROR: Symbol file could not be found. Defaulted to export symbols for
igdkmd64.sys -

*** ERROR: Module load completed but symbols could not be loaded for
msasn1.dll

KDTARGET: Refreshing KD connection

*** ERROR: Module load completed but symbols could not be loaded for
tifm21.sys

*** ERROR: Module load completed but symbols could not be loaded for
SynTP.sys

*** ERROR: Module load completed but symbols could not be loaded for
Epfwndis.sys

*** ERROR: Symbol file could not be found. Defaulted to export symbols for
drmk.sys -

*** ERROR: Module load completed but symbols could not be loaded for
eamon.sys

*** ERROR: Module load completed but symbols could not be loaded for
epfw.sys

*** ERROR: Module load completed but symbols could not be loaded for
epfwwfp.sys

*** ERROR: Module load completed but symbols could not be loaded for
peauth.sys

*** ERROR: Module load completed but symbols could not be loaded for
secdrv.SYS

*** ERROR: Symbol file could not be found. Defaulted to export symbols for
spsys.sys -

It is now 14:27. It took nearly 30 minutes for those symbol files to fail to
load. Yesterday it was much faster . not instantaneous, but faster. Kind of
makes quick debug session turn into hours, or days. Symbol path looks like
this:

srv*C:\Symbols*http://msdl.microsoft.com/download/symbols

Is it because it snowed in Minnesota today?

Gary G. Little

H (952) 223-1349

C (952) 454-4629

xxxxx@comcast.net

The squirrels powering the internet in Minnesota were tired today. Maybe they’ll have a better day tomorrow…

From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Gary G. Little
Sent: Thursday, January 07, 2010 3:31 PM
To: Kernel Debugging Interest List
Subject: [windbg] WinDbg 6.11.0001.404

I’ve been using for a few days now, and have not had any reall problems until today. Loading symbols seemingly take forever. An example:

kd> .reload
Connected to Windows 7 7600 x64 target at (Thu Jan 7 14:04:44.136 2010 (GMT-6)), ptr64 TRUE
Loading Kernel Symbols

Loading User Symbols

kd> g
*** ERROR: Module load completed but symbols could not be loaded for ehdrv.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for igdkmd64.sys -
*** ERROR: Module load completed but symbols could not be loaded for msasn1.dll
KDTARGET: Refreshing KD connection
*** ERROR: Module load completed but symbols could not be loaded for tifm21.sys
*** ERROR: Module load completed but symbols could not be loaded for SynTP.sys
*** ERROR: Module load completed but symbols could not be loaded for Epfwndis.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for drmk.sys -
*** ERROR: Module load completed but symbols could not be loaded for eamon.sys
*** ERROR: Module load completed but symbols could not be loaded for epfw.sys
*** ERROR: Module load completed but symbols could not be loaded for epfwwfp.sys
*** ERROR: Module load completed but symbols could not be loaded for peauth.sys
*** ERROR: Module load completed but symbols could not be loaded for secdrv.SYS
*** ERROR: Symbol file could not be found. Defaulted to export symbols for spsys.sys -

It is now 14:27. It took nearly 30 minutes for those symbol files to fail to load. Yesterday it was much faster … not instantaneous, but faster. Kind of makes quick debug session turn into hours, or days. Symbol path looks like this:

srv*C:\Symbols*http://msdl.microsoft.com/download/symbols

Is it because it snowed in Minnesota today?

Gary G. Little
H (952) 223-1349
C (952) 454-4629
xxxxx@comcast.net

__________ Information from ESET Smart Security, version of virus signature database 4751 (20100107) __________

The message was checked by ESET Smart Security.

http://www.eset.com


WINDBG is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

Uhhh . they did Mark . got above 0 and they were looking for nuts allo over
the place . J

Gary G. Little

H (952) 223-1349

C (952) 454-4629

xxxxx@comcast.net

From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Mark Cariddi
Sent: Thursday, January 07, 2010 2:56 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] WinDbg 6.11.0001.404

The squirrels powering the internet in Minnesota were tired today. Maybe
they’ll have a better day tomorrow…

From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Gary G. Little
Sent: Thursday, January 07, 2010 3:31 PM
To: Kernel Debugging Interest List
Subject: [windbg] WinDbg 6.11.0001.404

I’ve been using for a few days now, and have not had any reall problems
until today. Loading symbols seemingly take forever. An example:

kd> .reload

Connected to Windows 7 7600 x64 target at (Thu Jan 7 14:04:44.136 2010
(GMT-6)), ptr64 TRUE

Loading Kernel Symbols

Loading User Symbols

kd> g

*** ERROR: Module load completed but symbols could not be loaded for
ehdrv.sys

*** ERROR: Symbol file could not be found. Defaulted to export symbols for
igdkmd64.sys -

*** ERROR: Module load completed but symbols could not be loaded for
msasn1.dll

KDTARGET: Refreshing KD connection

*** ERROR: Module load completed but symbols could not be loaded for
tifm21.sys

*** ERROR: Module load completed but symbols could not be loaded for
SynTP.sys

*** ERROR: Module load completed but symbols could not be loaded for
Epfwndis.sys

*** ERROR: Symbol file could not be found. Defaulted to export symbols for
drmk.sys -

*** ERROR: Module load completed but symbols could not be loaded for
eamon.sys

*** ERROR: Module load completed but symbols could not be loaded for
epfw.sys

*** ERROR: Module load completed but symbols could not be loaded for
epfwwfp.sys

*** ERROR: Module load completed but symbols could not be loaded for
peauth.sys

*** ERROR: Module load completed but symbols could not be loaded for
secdrv.SYS

*** ERROR: Symbol file could not be found. Defaulted to export symbols for
spsys.sys -

It is now 14:27. It took nearly 30 minutes for those symbol files to fail to
load. Yesterday it was much faster . not instantaneous, but faster. Kind of
makes quick debug session turn into hours, or days. Symbol path looks like
this:

srv*C:\Symbols*http://msdl.microsoft.com/download/symbols

Is it because it snowed in Minnesota today?

Gary G. Little

H (952) 223-1349

C (952) 454-4629

xxxxx@comcast.net

__________ Information from ESET Smart Security, version of virus signature
database 4751 (20100107) __________

The message was checked by ESET Smart Security.

http://www.eset.com


WINDBG is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer


WINDBG is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

__________ Information from ESET Smart Security, version of virus signature
database 4752 (20100107) __________

The message was checked by ESET Smart Security.

http://www.eset.com

__________ Information from ESET Smart Security, version of virus signature
database 4783 (20100118) __________

The message was checked by ESET Smart Security.

http://www.eset.com