Hi,
I am facing a blue screen of death with my NDIS miniport driver at some
instance.
I wanted to debug the cause of this.I am getting a C5 stop error.I have
downloaded the XP SP2 symbol files and installed them in my machine.Can anyone
tell me the path I have to point to in the WinDbg for symbol path,source path
and image path.
I am not able to get the !analyze -v dump.I am getting an error
Use !analyze -v to get detailed debugging information.
BugCheck D6, {85c7b000, 1, ba3f9d5d, 0}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*** ERROR: Module load completed but symbols could not be loaded for my.sys
*** ERROR: Module load completed but symbols could not be loaded for sdbus.sys
Probably caused by : my.sys ( my+27d5d )
thanks in advance.
Abhishek.N
Use the Micorosoft symbol server, trying to use the symbol files is a waste
of time, the second a hotfix is applied the symbol files are out of date.
Using the symbol server will pull down the symbol files that match the
actual binaries on system being debugged.
–
Don Burn (MVP, Windows DKD)
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
wrote in message news:xxxxx@ntdev…
> Hi,
>
> I am facing a blue screen of death with my NDIS miniport driver at some
> instance.
> I wanted to debug the cause of this.I am getting a C5 stop error.I have
> downloaded the XP SP2 symbol files and installed them in my machine.Can
> anyone
> tell me the path I have to point to in the WinDbg for symbol path,source
> path
> and image path.
> I am not able to get the !analyze -v dump.I am getting an error
>
> Use !analyze -v to get detailed debugging information.
>
> BugCheck D6, {85c7b000, 1, ba3f9d5d, 0}
>
> **Kernel symbols are WRONG. Please fix symbols to do analysis.
>
> ERROR: Module load completed but symbols could not be loaded for
> my.sys
> *** ERROR: Module load completed but symbols could not be loaded for
> sdbus.sys
> Probably caused by : my.sys ( my+27d5d )
>
> thanks in advance.
> Abhishek.N
>
>
>
>
> Information from ESET NOD32 Antivirus, version of virus
> signature database 4692 (20091216)
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>
Information from ESET NOD32 Antivirus, version of virus signature database 4692 (20091216)
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
!symfix
.sympath+
!analyze -v
Good Luck,
Dave Cattley
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@redpinesignals.com
Sent: Wednesday, December 16, 2009 8:52 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] How to include Symbol files
Hi,
I am facing a blue screen of death with my NDIS miniport driver at some
instance.
I wanted to debug the cause of this.I am getting a C5 stop error.I have
downloaded the XP SP2 symbol files and installed them in my machine.Can
anyone
tell me the path I have to point to in the WinDbg for symbol path,source
path
and image path.
I am not able to get the !analyze -v dump.I am getting an error
Use !analyze -v to get detailed debugging information.
BugCheck D6, {85c7b000, 1, ba3f9d5d, 0}
Kernel symbols are WRONG. Please fix symbols to do analysis.
ERROR: Module load completed but symbols could not be loaded for my.sys
* ERROR: Module load completed but symbols could not be loaded for
sdbus.sys
Probably caused by : my.sys ( my+27d5d )
thanks in advance.
Abhishek.N
—
NTDEV 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
Thank you Dave and Don.I have posted if WinDbg forum, which is the correct place for this.