Using WinDebug

  • Thread starter Thread starter Gateway man
  • Start date Start date
G

Gateway man

Guest
I have downloaded WinDebug & the Debugging tools from the following two sites:
http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx
http://msdl.microsoft.com/download/symbols/packages/windows2003/Windows2003
But I still get error messages that the correct tools are not loaded to
analyze see below:
Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini041408-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\DEBUG*http://msdl.microsoft.com/download/symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for
ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 3.3311) MP (2 procs) Free x86
compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Mon Apr 14 21:44:52.109 2008 (GMT-5)
System Uptime: 0 days 0:19:40.665
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for
ntoskrnl.exe
Loading Kernel Symbols
.......................................................................................................................................................
Loading User Symbols
Loading unloaded module list
.....................
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck B8, {0, 0, 0, 0}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** 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: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: nt!_KPRCB ***
*** ***
*************************************************************************
*** WARNING: Unable to verify timestamp for hal.dll
*** ERROR: Module load completed but symbols could not be loaded for hal.dll
*** WARNING: Unable to verify timestamp for Dvd43.sys
*** ERROR: Module load completed but symbols could not be loaded for Dvd43.sys
*** WARNING: Unable to verify timestamp for CLASSPNP.SYS
*** ERROR: Module load completed but symbols could not be loaded for
CLASSPNP.SYS
*** WARNING: Unable to verify timestamp for cdrom.sys
*** ERROR: Module load completed but symbols could not be loaded for cdrom.sys
*** WARNING: Unable to verify timestamp for atapi.sys
*** ERROR: Module load completed but symbols could not be loaded for atapi.sys
*************************************************************************
*** ***
*** ***
*** 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: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: nt!_KPRCB ***
*** ***
*************************************************************************


Probably caused by : Dvd43.sys ( Dvd43+2347 )

Followup: MachineOwner
What am I doing wrong? How do I correct this error? Your help & assistance
are appreciated.
 
RE: Using WinDebug


In your old post it seems your DVD is the problem, please uninstall and
reinstall with the latest driver for it.

"Gateway man" wrote:

> I have downloaded WinDebug & the Debugging tools from the following two sites:
> http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx
> http://msdl.microsoft.com/download/symbols/packages/windows2003/Windows2003
> But I still get error messages that the correct tools are not loaded to
> analyze see below:
> Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
> Copyright (c) Microsoft Corporation. All rights reserved.
>
>
> Loading Dump File [C:\WINDOWS\Minidump\Mini041408-02.dmp]
> Mini Kernel Dump File: Only registers and stack trace are available
>
> Symbol search path is: SRV*c:\DEBUG*http://msdl.microsoft.com/download/symbols
> Executable search path is:
> Unable to load image ntoskrnl.exe, Win32 error 0n2
> *** WARNING: Unable to verify timestamp for ntoskrnl.exe
> *** ERROR: Module load completed but symbols could not be loaded for
> ntoskrnl.exe
> Windows XP Kernel Version 2600 (Service Pack 3.3311) MP (2 procs) Free x86
> compatible
> Product: WinNt, suite: TerminalServer SingleUserTS Personal
> Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
> Debug session time: Mon Apr 14 21:44:52.109 2008 (GMT-5)
> System Uptime: 0 days 0:19:40.665
> Unable to load image ntoskrnl.exe, Win32 error 0n2
> *** WARNING: Unable to verify timestamp for ntoskrnl.exe
> *** ERROR: Module load completed but symbols could not be loaded for
> ntoskrnl.exe
> Loading Kernel Symbols
> ......................................................................................................................................................
> Loading User Symbols
> Loading unloaded module list
> ....................
> *******************************************************************************
> *
> *
> * Bugcheck Analysis
> *
> *
> *
> *******************************************************************************
>
> Use !analyze -v to get detailed debugging information.
>
> BugCheck B8, {0, 0, 0, 0}
>
> ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
>
> *************************************************************************
> *** ***
> *** ***
> *** 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: nt!_KPRCB ***
> *** ***
> *************************************************************************
> *************************************************************************
> *** ***
> *** ***
> *** 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: nt!KPRCB ***
> *** ***
> *************************************************************************
> *************************************************************************
> *** ***
> *** ***
> *** 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: nt!_KPRCB ***
> *** ***
> *************************************************************************
> *************************************************************************
> *** ***
> *** ***
> *** 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: nt!KPRCB ***
> *** ***
> *************************************************************************
> *************************************************************************
> *** ***
> *** ***
> *** 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: nt!_KPRCB ***
> *** ***
> *************************************************************************
> *** WARNING: Unable to verify timestamp for hal.dll
> *** ERROR: Module load completed but symbols could not be loaded for hal.dll
> *** WARNING: Unable to verify timestamp for Dvd43.sys
> *** ERROR: Module load completed but symbols could not be loaded for Dvd43.sys
> *** WARNING: Unable to verify timestamp for CLASSPNP.SYS
> *** ERROR: Module load completed but symbols could not be loaded for
> CLASSPNP.SYS
> *** WARNING: Unable to verify timestamp for cdrom.sys
> *** ERROR: Module load completed but symbols could not be loaded for cdrom.sys
> *** WARNING: Unable to verify timestamp for atapi.sys
> *** ERROR: Module load completed but symbols could not be loaded for atapi.sys
> *************************************************************************
> *** ***
> *** ***
> *** 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: nt!_KPRCB ***
> *** ***
> *************************************************************************
> *************************************************************************
> *** ***
> *** ***
> *** 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: nt!_KPRCB ***
> *** ***
> *************************************************************************
>
>
> Probably caused by : Dvd43.sys ( Dvd43+2347 )
>
> Followup: MachineOwner
> What am I doing wrong? How do I correct this error? Your help & assistance
> are appreciated.
 
RE: Using WinDebug

You may have downloaded the wrong symbols. I used the command bellow while
connected to the internet. I did not download the symbols.

windbg -y srv*c:\symbols*http://msdl.microsoft.com/download/symbols -i
c:\windows\i386 -z c:\windows\minidump\Mini041408-02.dmp

If you download the symbols to a local folder, use the path of that folder
as your symbol path.

The instructions I used:
How to read the small memory dump files that Windows creates for debugging
http://support.microsoft.com/kb/315263

--
Rey


"Gateway man" wrote:

> I have downloaded WinDebug & the Debugging tools from the following two sites:
> http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx
> http://msdl.microsoft.com/download/symbols/packages/windows2003/Windows2003
> But I still get error messages that the correct tools are not loaded to
> analyze see below:
> Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
> Copyright (c) Microsoft Corporation. All rights reserved.
>
>
> Loading Dump File [C:\WINDOWS\Minidump\Mini041408-02.dmp]
> Mini Kernel Dump File: Only registers and stack trace are available
>
> Symbol search path is: SRV*c:\DEBUG*http://msdl.microsoft.com/download/symbols
> Executable search path is:
> Unable to load image ntoskrnl.exe, Win32 error 0n2
> *** WARNING: Unable to verify timestamp for ntoskrnl.exe
> *** ERROR: Module load completed but symbols could not be loaded for
> ntoskrnl.exe
> Windows XP Kernel Version 2600 (Service Pack 3.3311) MP (2 procs) Free x86
> compatible
> Product: WinNt, suite: TerminalServer SingleUserTS Personal
> Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
> Debug session time: Mon Apr 14 21:44:52.109 2008 (GMT-5)
> System Uptime: 0 days 0:19:40.665
> Unable to load image ntoskrnl.exe, Win32 error 0n2
> *** WARNING: Unable to verify timestamp for ntoskrnl.exe
> *** ERROR: Module load completed but symbols could not be loaded for
> ntoskrnl.exe
> Loading Kernel Symbols
> ......................................................................................................................................................
> Loading User Symbols
> Loading unloaded module list
> ....................
> *******************************************************************************
> *
> *
> * Bugcheck Analysis
> *
> *
> *
> *******************************************************************************
>
> Use !analyze -v to get detailed debugging information.
>
> BugCheck B8, {0, 0, 0, 0}
>
> ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
>
> *************************************************************************
> *** ***
> *** ***
> *** 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: nt!_KPRCB ***
> *** ***
> *************************************************************************
> *************************************************************************
> *** ***
> *** ***
> *** 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: nt!KPRCB ***
> *** ***
> *************************************************************************
> *************************************************************************
> *** ***
> *** ***
> *** 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: nt!_KPRCB ***
> *** ***
> *************************************************************************
> *************************************************************************
> *** ***
> *** ***
> *** 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: nt!KPRCB ***
> *** ***
> *************************************************************************
> *************************************************************************
> *** ***
> *** ***
> *** 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: nt!_KPRCB ***
> *** ***
> *************************************************************************
> *** WARNING: Unable to verify timestamp for hal.dll
> *** ERROR: Module load completed but symbols could not be loaded for hal.dll
> *** WARNING: Unable to verify timestamp for Dvd43.sys
> *** ERROR: Module load completed but symbols could not be loaded for Dvd43.sys
> *** WARNING: Unable to verify timestamp for CLASSPNP.SYS
> *** ERROR: Module load completed but symbols could not be loaded for
> CLASSPNP.SYS
> *** WARNING: Unable to verify timestamp for cdrom.sys
> *** ERROR: Module load completed but symbols could not be loaded for cdrom.sys
> *** WARNING: Unable to verify timestamp for atapi.sys
> *** ERROR: Module load completed but symbols could not be loaded for atapi.sys
> *************************************************************************
> *** ***
> *** ***
> *** 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: nt!_KPRCB ***
> *** ***
> *************************************************************************
> *************************************************************************
> *** ***
> *** ***
> *** 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: nt!_KPRCB ***
> *** ***
> *************************************************************************
>
>
> Probably caused by : Dvd43.sys ( Dvd43+2347 )
>
> Followup: MachineOwner
> What am I doing wrong? How do I correct this error? Your help & assistance
> are appreciated.
 
RE: Using WinDebug

From my previous post: I cleaned up my hard drive with ccleaner, I deleted
DVD 43 from my programs & now iTunes works perfectly. I run my F-Secure
Suites every week to check for viruses & spyware. I truly appreciate your
help. I tried to uninstall SP3 for windows XP but it said the following
programs may not work if you uninstall SP3 so I left it alone. I originally
thought I could uninstall it after I installed it but I guess I can't. Again
thank you very much for your assistance.


"nass" wrote:

>
> In your old post it seems your DVD is the problem, please uninstall and
> reinstall with the latest driver for it.
>
> "Gateway man" wrote:
>
> > I have downloaded WinDebug & the Debugging tools from the following two sites:
> > http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx
> > http://msdl.microsoft.com/download/symbols/packages/windows2003/Windows2003
> > But I still get error messages that the correct tools are not loaded to
> > analyze see below:
> > Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
> > Copyright (c) Microsoft Corporation. All rights reserved.
> >
> >
> > Loading Dump File [C:\WINDOWS\Minidump\Mini041408-02.dmp]
> > Mini Kernel Dump File: Only registers and stack trace are available
> >
> > Symbol search path is: SRV*c:\DEBUG*http://msdl.microsoft.com/download/symbols
> > Executable search path is:
> > Unable to load image ntoskrnl.exe, Win32 error 0n2
> > *** WARNING: Unable to verify timestamp for ntoskrnl.exe
> > *** ERROR: Module load completed but symbols could not be loaded for
> > ntoskrnl.exe
> > Windows XP Kernel Version 2600 (Service Pack 3.3311) MP (2 procs) Free x86
> > compatible
> > Product: WinNt, suite: TerminalServer SingleUserTS Personal
> > Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
> > Debug session time: Mon Apr 14 21:44:52.109 2008 (GMT-5)
> > System Uptime: 0 days 0:19:40.665
> > Unable to load image ntoskrnl.exe, Win32 error 0n2
> > *** WARNING: Unable to verify timestamp for ntoskrnl.exe
> > *** ERROR: Module load completed but symbols could not be loaded for
> > ntoskrnl.exe
> > Loading Kernel Symbols
> > ......................................................................................................................................................
> > Loading User Symbols
> > Loading unloaded module list
> > ....................
> > *******************************************************************************
> > *
> > *
> > * Bugcheck Analysis
> > *
> > *
> > *
> > *******************************************************************************
> >
> > Use !analyze -v to get detailed debugging information.
> >
> > BugCheck B8, {0, 0, 0, 0}
> >
> > ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
> >
> > *************************************************************************
> > *** ***
> > *** ***
> > *** 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: nt!_KPRCB ***
> > *** ***
> > *************************************************************************
> > *************************************************************************
> > *** ***
> > *** ***
> > *** 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: nt!KPRCB ***
> > *** ***
> > *************************************************************************
> > *************************************************************************
> > *** ***
> > *** ***
> > *** 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: nt!_KPRCB ***
> > *** ***
> > *************************************************************************
> > *************************************************************************
> > *** ***
> > *** ***
> > *** 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: nt!KPRCB ***
> > *** ***
> > *************************************************************************
> > *************************************************************************
> > *** ***
> > *** ***
> > *** 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: nt!_KPRCB ***
> > *** ***
> > *************************************************************************
> > *** WARNING: Unable to verify timestamp for hal.dll
> > *** ERROR: Module load completed but symbols could not be loaded for hal.dll
> > *** WARNING: Unable to verify timestamp for Dvd43.sys
> > *** ERROR: Module load completed but symbols could not be loaded for Dvd43.sys
> > *** WARNING: Unable to verify timestamp for CLASSPNP.SYS
> > *** ERROR: Module load completed but symbols could not be loaded for
> > CLASSPNP.SYS
> > *** WARNING: Unable to verify timestamp for cdrom.sys
> > *** ERROR: Module load completed but symbols could not be loaded for cdrom.sys
> > *** WARNING: Unable to verify timestamp for atapi.sys
> > *** ERROR: Module load completed but symbols could not be loaded for atapi.sys
> > *************************************************************************
> > *** ***
> > *** ***
> > *** 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: nt!_KPRCB ***
> > *** ***
> > *************************************************************************
> > *************************************************************************
> > *** ***
> > *** ***
> > *** 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: nt!_KPRCB ***
> > *** ***
> > *************************************************************************
> >
> >
> > Probably caused by : Dvd43.sys ( Dvd43+2347 )
> >
> > Followup: MachineOwner
> > What am I doing wrong? How do I correct this error? Your help & assistance
> > are appreciated.
 
Back
Top