hi all:
I run a test by using netadapterCx client driver. but I encounter a BSOD, the bugcheck code is 19e. I can't find any defintion about this value. Can anybody explain it? Here are the dump analysis info.
0: kd> !analyze -v
*
Bugcheck Analysis *
*
BUGCODE_NETADAPTER_DRIVER (19e)
The operating system encountered an error caused by a networking driver managed by NetAdapterCx.
Arguments:
Arg1: 0000000000000047, NetAdapterCx BugCheck subcode
Arg2: ffffd18d949b1ae0
Arg3: 0000000000000000
Arg4: 0000000000000000
Debugging Details:
Unable to load image \SystemRoot\system32\drivers\netadaptercx.sys, Win32 error 0n2
Unable to load image \SystemRoot\System32\Drivers\ExecutionContext.sys, Win32 error 0n2
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
Either you specified an unqualified symbol, or your debugger doesn't have full symbol information. Unqualified symbol resolution is turned off by default. Please either specify a fully qualified symbol module!symbolname, or enable resolution of unqualified symbols by typing ".symopt- 100". Note that enabling unqualified symbol resolution with network symbol server shares in the symbol path may cause the debugger to appear to hang for long periods of time when an incorrect symbol name is typed or the network symbol server is down.
For some commands 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!_IMAGE_DOS_HEADER
Either you specified an unqualified symbol, or your debugger doesn't have full symbol information. Unqualified symbol resolution is turned off by default. Please either specify a fully qualified symbol module!symbolname, or enable resolution of unqualified symbols by typing ".symopt- 100". Note that enabling unqualified symbol resolution with network symbol server shares in the symbol path may cause the debugger to appear to hang for long periods of time when an incorrect symbol name is typed or the network symbol server is down.
For some commands 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!_IMAGE_DOS_HEADER
Either you specified an unqualified symbol, or your debugger doesn't have full symbol information. Unqualified symbol resolution is turned off by default. Please either specify a fully qualified symbol module!symbolname, or enable resolution of unqualified symbols by typing ".symopt- 100". Note that enabling unqualified symbol resolution with network symbol server shares in the symbol path may cause the debugger to appear to hang for long periods of time when an incorrect symbol name is typed or the network symbol server is down.
For some commands 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!_IMAGE_DOS_HEADER
Either you specified an unqualified symbol, or your debugger doesn't have full symbol information. Unqualified symbol resolution is turned off by default. Please either specify a fully qualified symbol module!symbolname, or enable resolution of unqualified symbols by typing ".symopt- 100". Note that enabling unqualified symbol resolution with network symbol server shares in the symbol path may cause the debugger to appear to hang for long periods of time when an incorrect symbol name is typed or the network symbol server is down.
For some commands 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!_IMAGE_DOS_HEADER
Either you specified an unqualified symbol, or your debugger doesn't have full symbol information. Unqualified symbol resolution is turned off by default. Please either specify a fully qualified symbol module!symbolname, or enable resolution of unqualified symbols by typing ".symopt- 100". Note that enabling unqualified symbol resolution with network symbol server shares in the symbol path may cause the debugger to appear to hang for long periods of time when an incorrect symbol name is typed or the network symbol server is down.
For some commands 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!_IMAGE_DOS_HEADER
Either you specified an unqualified symbol, or your debugger doesn't have full symbol information. Unqualified symbol resolution is turned off by default. Please either specify a fully qualified symbol module!symbolname, or enable resolution of unqualified symbols by typing ".symopt- 100". Note that enabling unqualified symbol resolution with network symbol server shares in the symbol path may cause the debugger to appear to hang for long periods of time when an incorrect symbol name is typed or the network symbol server is down.
For some commands 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!_IMAGE_DOS_HEADER
Either you specified an unqualified symbol, or your debugger doesn't have full symbol information. Unqualified symbol resolution is turned off by default. Please either specify a fully qualified symbol module!symbolname, or enable resolution of unqualified symbols by typing ".symopt- 100". Note that enabling unqualified symbol resolution with network symbol server shares in the symbol path may cause the debugger to appear to hang for long periods of time when an incorrect symbol name is typed or the network symbol server is down.
For some commands 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!_IMAGE_DOS_HEADER
Either you specified an unqualified symbol, or your debugger doesn't have full symbol information. Unqualified symbol resolution is turned off by default. Please either specify a fully qualified symbol module!symbolname, or enable resolution of unqualified symbols by typing ".symopt- 100". Note that enabling unqualified symbol resolution with network symbol server shares in the symbol path may cause the debugger to appear to hang for long periods of time when an incorrect symbol name is typed or the network symbol server is down.
For some commands 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!_IMAGE_DOS_HEADER
Either you specified an unqualified symbol, or your debugger doesn't have full symbol information. Unqualified symbol resolution is turned off by default. Please either specify a fully qualified symbol module!symbolname, or enable resolution of unqualified symbols by typing ".symopt- 100". Note that enabling unqualified symbol resolution with network symbol server shares in the symbol path may cause the debugger to appear to hang for long periods of time when an incorrect symbol name is typed or the network symbol server is down.
For some commands 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!_IMAGE_DOS_HEADER
Either you specified an unqualified symbol, or your debugger doesn't have full symbol information. Unqualified symbol resolution is turned off by default. Please either specify a fully qualified symbol module!symbolname, or enable resolution of unqualified symbols by typing ".symopt- 100". Note that enabling unqualified symbol resolution with network symbol server shares in the symbol path may cause the debugger to appear to hang for long periods of time when an incorrect symbol name is typed or the network symbol server is down.
For some commands 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!_IMAGE_DOS_HEADER
Either you specified an unqualified symbol, or your debugger doesn't have full symbol information. Unqualified symbol resolution is turned off by default. Please either specify a fully qualified symbol module!symbolname, or enable resolution of unqualified symbols by typing ".symopt- 100". Note that enabling unqualified symbol resolution with network symbol server shares in the symbol path may cause the debugger to appear to hang for long periods of time when an incorrect symbol name is typed or the network symbol server is down.
For some commands 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!_IMAGE_DOS_HEADER
Either you specified an unqualified symbol, or your debugger doesn't have full symbol information. Unqualified symbol resolution is turned off by default. Please either specify a fully qualified symbol module!symbolname, or enable resolution of unqualified symbols by typing ".symopt- 100". Note that enabling unqualified symbol resolution with network symbol server shares in the symbol path may cause the debugger to appear to hang for long periods of time when an incorrect symbol name is typed or the network symbol server is down.
For some commands 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!_IMAGE_DOS_HEADER
Either you specified an unqualified symbol, or your debugger doesn't have full symbol information. Unqualified symbol resolution is turned off by default. Please either specify a fully qualified symbol module!symbolname, or enable resolution of unqualified symbols by typing ".symopt- 100". Note that enabling unqualified symbol resolution with network symbol server shares in the symbol path may cause the debugger to appear to hang for long periods of time when an incorrect symbol name is typed or the network symbol server is down.
For some commands 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!_IMAGE_DOS_HEADER
Either you specified an unqualified symbol, or your debugger doesn't have full symbol information. Unqualified symbol resolution is turned off by default. Please either specify a fully qualified symbol module!symbolname, or enable resolution of unqualified symbols by typing ".symopt- 100". Note that enabling unqualified symbol resolution with network symbol server shares in the symbol path may cause the debugger to appear to hang for long periods of time when an incorrect symbol name is typed or the network symbol server is down.
For some commands 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!_IMAGE_DOS_HEADER
Either you specified an unqualified symbol, or your debugger doesn't have full symbol information. Unqualified symbol resolution is turned off by default. Please either specify a fully qualified symbol module!symbolname, or enable resolution of unqualified symbols by typing ".symopt- 100". Note that enabling unqualified symbol resolution with network symbol server shares in the symbol path may cause the debugger to appear to hang for long periods of time when an incorrect symbol name is typed or the network symbol server is down.
For some commands 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!_IMAGE_DOS_HEADER
Either you specified an unqualified symbol, or your debugger doesn't have full symbol information. Unqualified symbol resolution is turned off by default. Please either specify a fully qualified symbol module!symbolname, or enable resolution of unqualified symbols by typing ".symopt- 100". Note that enabling unqualified symbol resolution with network symbol server shares in the symbol path may cause the debugger to appear to hang for long periods of time when an incorrect symbol name is typed or the network symbol server is down.
For some commands 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!_IMAGE_DOS_HEADER
Either you specified an unqualified symbol, or your debugger doesn't have full symbol information. Unqualified symbol resolution is turned off by default. Please either specify a fully qualified symbol module!symbolname, or enable resolution of unqualified symbols by typing ".symopt- 100". Note that enabling unqualified symbol resolution with network symbol server shares in the symbol path may cause the debugger to appear to hang for long periods of time when an incorrect symbol name is typed or the network symbol server is down.
For some commands 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!_IMAGE_DOS_HEADER
Either you specified an unqualified symbol, or your debugger doesn't have full symbol information. Unqualified symbol resolution is turned off by default. Please either specify a fully qualified symbol module!symbolname, or enable resolution of unqualified symbols by typing ".symopt- 100". Note that enabling unqualified symbol resolution with network symbol server shares in the symbol path may cause the debugger to appear to hang for long periods of time when an incorrect symbol name is typed or the network symbol server is down.
For some commands 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!_IMAGE_DOS_HEADER
Either you specified an unqualified symbol, or your debugger doesn't have full symbol information. Unqualified symbol resolution is turned off by default. Please either specify a fully qualified symbol module!symbolname, or enable resolution of unqualified symbols by typing ".symopt- 100". Note that enabling unqualified symbol resolution with network symbol server shares in the symbol path may cause the debugger to appear to hang for long periods of time when an incorrect symbol name is typed or the network symbol server is down.
For some commands 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
Either you specified an unqualified symbol, or your debugger doesn't have full symbol information. Unqualified symbol resolution is turned off by default. Please either specify a fully qualified symbol module!symbolname, or enable resolution of unqualified symbols by typing ".symopt- 100". Note that enabling unqualified symbol resolution with network symbol server shares in the symbol path may cause the debugger to appear to hang for long periods of time when an incorrect symbol name is typed or the network symbol server is down.
For some commands 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
Either you specified an unqualified symbol, or your debugger doesn't have full symbol information. Unqualified symbol resolution is turned off by default. Please either specify a fully qualified symbol module!symbolname, or enable resolution of unqualified symbols by typing ".symopt- 100". Note that enabling unqualified symbol resolution with network symbol server shares in the symbol path may cause the debugger to appear to hang for long periods of time when an incorrect symbol name is typed or the network symbol server is down.
For some commands 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
Either you specified an unqualified symbol, or your debugger doesn't have full symbol information. Unqualified symbol resolution is turned off by default. Please either specify a fully qualified symbol module!symbolname, or enable resolution of unqualified symbols by typing ".symopt- 100". Note that enabling unqualified symbol resolution with network symbol server shares in the symbol path may cause the debugger to appear to hang for long periods of time when an incorrect symbol name is typed or the network symbol server is down.
For some commands 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
Either you specified an unqualified symbol, or your debugger doesn't have full symbol information. Unqualified symbol resolution is turned off by default. Please either specify a fully qualified symbol module!symbolname, or enable resolution of unqualified symbols by typing ".symopt- 100". Note that enabling unqualified symbol resolution with network symbol server shares in the symbol path may cause the debugger to appear to hang for long periods of time when an incorrect symbol name is typed or the network symbol server is down.
For some commands 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
Either you specified an unqualified symbol, or your debugger doesn't have full symbol information. Unqualified symbol resolution is turned off by default. Please either specify a fully qualified symbol module!symbolname, or enable resolution of unqualified symbols by typing ".symopt- 100". Note that enabling unqualified symbol resolution with network symbol server shares in the symbol path may cause the debugger to appear to hang for long periods of time when an incorrect symbol name is typed or the network symbol server is down.
For some commands 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!_EPROCESS
Either you specified an unqualified symbol, or your debugger doesn't have full symbol information. Unqualified symbol resolution is turned off by default. Please either specify a fully qualified symbol module!symbolname, or enable resolution of unqualified symbols by typing ".symopt- 100". Note that enabling unqualified symbol resolution with network symbol server shares in the symbol path may cause the debugger to appear to hang for long periods of time when an incorrect symbol name is typed or the network symbol server is down.
For some commands 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
Either you specified an unqualified symbol, or your debugger doesn't have full symbol information. Unqualified symbol resolution is turned off by default. Please either specify a fully qualified symbol module!symbolname, or enable resolution of unqualified symbols by typing ".symopt- 100". Note that enabling unqualified symbol resolution with network symbol server shares in the symbol path may cause the debugger to appear to hang for long periods of time when an incorrect symbol name is typed or the network symbol server is down.
For some commands 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
Either you specified an unqualified symbol, or your debugger doesn't have full symbol information. Unqualified symbol resolution is turned off by default. Please either specify a fully qualified symbol module!symbolname, or enable resolution of unqualified symbols by typing ".symopt- 100". Note that enabling unqualified symbol resolution with network symbol server shares in the symbol path may cause the debugger to appear to hang for long periods of time when an incorrect symbol name is typed or the network symbol server is down.
For some commands 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
Either you specified an unqualified symbol, or your debugger doesn't have full symbol information. Unqualified symbol resolution is turned off by default. Please either specify a fully qualified symbol module!symbolname, or enable resolution of unqualified symbols by typing ".symopt- 100". Note that enabling unqualified symbol resolution with network symbol server shares in the symbol path may cause the debugger to appear to hang for long periods of time when an incorrect symbol name is typed or the network symbol server is down.
For some commands 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.
hi all: I run a test by using netadapterCx client driver. but I encounter a BSOD, the bugcheck code is 19e. I can't find any defintion about this value. Can anybody explain it? Here are the dump analysis info.
0: kd> !analyze -v
BUGCODE_NETADAPTER_DRIVER (19e) The operating system encountered an error caused by a networking driver managed by NetAdapterCx. Arguments: Arg1: 0000000000000047, NetAdapterCx BugCheck subcode Arg2: ffffd18d949b1ae0 Arg3: 0000000000000000 Arg4: 0000000000000000
Debugging Details:
Unable to load image \SystemRoot\system32\drivers\netadaptercx.sys, Win32 error 0n2 Unable to load image \SystemRoot\System32\Drivers\ExecutionContext.sys, Win32 error 0n2 ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
Either you specified an unqualified symbol, or your debugger doesn't have full symbol information. Unqualified symbol resolution is turned off by default. Please either specify a fully qualified symbol module!symbolname, or enable resolution of unqualified symbols by typing ".symopt- 100". Note that enabling unqualified symbol resolution with network symbol server shares in the symbol path may cause the debugger to appear to hang for long periods of time when an incorrect symbol name is typed or the network symbol server is down.
For some commands 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!_IMAGE_DOS_HEADER
Either you specified an unqualified symbol, or your debugger doesn't have full symbol information. Unqualified symbol resolution is turned off by default. Please either specify a fully qualified symbol module!symbolname, or enable resolution of unqualified symbols by typing ".symopt- 100". Note that enabling unqualified symbol resolution with network symbol server shares in the symbol path may cause the debugger to appear to hang for long periods of time when an incorrect symbol name is typed or the network symbol server is down.
For some commands 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!_IMAGE_DOS_HEADER
Either you specified an unqualified symbol, or your debugger doesn't have full symbol information. Unqualified symbol resolution is turned off by default. Please either specify a fully qualified symbol module!symbolname, or enable resolution of unqualified symbols by typing ".symopt- 100". Note that enabling unqualified symbol resolution with network symbol server shares in the symbol path may cause the debugger to appear to hang for long periods of time when an incorrect symbol name is typed or the network symbol server is down.
For some commands 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!_IMAGE_DOS_HEADER
Either you specified an unqualified symbol, or your debugger doesn't have full symbol information. Unqualified symbol resolution is turned off by default. Please either specify a fully qualified symbol module!symbolname, or enable resolution of unqualified symbols by typing ".symopt- 100". Note that enabling unqualified symbol resolution with network symbol server shares in the symbol path may cause the debugger to appear to hang for long periods of time when an incorrect symbol name is typed or the network symbol server is down.
For some commands 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!_IMAGE_DOS_HEADER
Either you specified an unqualified symbol, or your debugger doesn't have full symbol information. Unqualified symbol resolution is turned off by default. Please either specify a fully qualified symbol module!symbolname, or enable resolution of unqualified symbols by typing ".symopt- 100". Note that enabling unqualified symbol resolution with network symbol server shares in the symbol path may cause the debugger to appear to hang for long periods of time when an incorrect symbol name is typed or the network symbol server is down.
For some commands 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!_IMAGE_DOS_HEADER
Either you specified an unqualified symbol, or your debugger doesn't have full symbol information. Unqualified symbol resolution is turned off by default. Please either specify a fully qualified symbol module!symbolname, or enable resolution of unqualified symbols by typing ".symopt- 100". Note that enabling unqualified symbol resolution with network symbol server shares in the symbol path may cause the debugger to appear to hang for long periods of time when an incorrect symbol name is typed or the network symbol server is down.
For some commands 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!_IMAGE_DOS_HEADER
Either you specified an unqualified symbol, or your debugger doesn't have full symbol information. Unqualified symbol resolution is turned off by default. Please either specify a fully qualified symbol module!symbolname, or enable resolution of unqualified symbols by typing ".symopt- 100". Note that enabling unqualified symbol resolution with network symbol server shares in the symbol path may cause the debugger to appear to hang for long periods of time when an incorrect symbol name is typed or the network symbol server is down.
For some commands 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!_IMAGE_DOS_HEADER
Either you specified an unqualified symbol, or your debugger doesn't have full symbol information. Unqualified symbol resolution is turned off by default. Please either specify a fully qualified symbol module!symbolname, or enable resolution of unqualified symbols by typing ".symopt- 100". Note that enabling unqualified symbol resolution with network symbol server shares in the symbol path may cause the debugger to appear to hang for long periods of time when an incorrect symbol name is typed or the network symbol server is down.
For some commands 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!_IMAGE_DOS_HEADER
Either you specified an unqualified symbol, or your debugger doesn't have full symbol information. Unqualified symbol resolution is turned off by default. Please either specify a fully qualified symbol module!symbolname, or enable resolution of unqualified symbols by typing ".symopt- 100". Note that enabling unqualified symbol resolution with network symbol server shares in the symbol path may cause the debugger to appear to hang for long periods of time when an incorrect symbol name is typed or the network symbol server is down.
For some commands 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!_IMAGE_DOS_HEADER
Either you specified an unqualified symbol, or your debugger doesn't have full symbol information. Unqualified symbol resolution is turned off by default. Please either specify a fully qualified symbol module!symbolname, or enable resolution of unqualified symbols by typing ".symopt- 100". Note that enabling unqualified symbol resolution with network symbol server shares in the symbol path may cause the debugger to appear to hang for long periods of time when an incorrect symbol name is typed or the network symbol server is down.
For some commands 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!_IMAGE_DOS_HEADER
Either you specified an unqualified symbol, or your debugger doesn't have full symbol information. Unqualified symbol resolution is turned off by default. Please either specify a fully qualified symbol module!symbolname, or enable resolution of unqualified symbols by typing ".symopt- 100". Note that enabling unqualified symbol resolution with network symbol server shares in the symbol path may cause the debugger to appear to hang for long periods of time when an incorrect symbol name is typed or the network symbol server is down.
For some commands 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!_IMAGE_DOS_HEADER
Either you specified an unqualified symbol, or your debugger doesn't have full symbol information. Unqualified symbol resolution is turned off by default. Please either specify a fully qualified symbol module!symbolname, or enable resolution of unqualified symbols by typing ".symopt- 100". Note that enabling unqualified symbol resolution with network symbol server shares in the symbol path may cause the debugger to appear to hang for long periods of time when an incorrect symbol name is typed or the network symbol server is down.
For some commands 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!_IMAGE_DOS_HEADER
Either you specified an unqualified symbol, or your debugger doesn't have full symbol information. Unqualified symbol resolution is turned off by default. Please either specify a fully qualified symbol module!symbolname, or enable resolution of unqualified symbols by typing ".symopt- 100". Note that enabling unqualified symbol resolution with network symbol server shares in the symbol path may cause the debugger to appear to hang for long periods of time when an incorrect symbol name is typed or the network symbol server is down.
For some commands 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!_IMAGE_DOS_HEADER
Either you specified an unqualified symbol, or your debugger doesn't have full symbol information. Unqualified symbol resolution is turned off by default. Please either specify a fully qualified symbol module!symbolname, or enable resolution of unqualified symbols by typing ".symopt- 100". Note that enabling unqualified symbol resolution with network symbol server shares in the symbol path may cause the debugger to appear to hang for long periods of time when an incorrect symbol name is typed or the network symbol server is down.
For some commands 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!_IMAGE_DOS_HEADER
Either you specified an unqualified symbol, or your debugger doesn't have full symbol information. Unqualified symbol resolution is turned off by default. Please either specify a fully qualified symbol module!symbolname, or enable resolution of unqualified symbols by typing ".symopt- 100". Note that enabling unqualified symbol resolution with network symbol server shares in the symbol path may cause the debugger to appear to hang for long periods of time when an incorrect symbol name is typed or the network symbol server is down.
For some commands 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!_IMAGE_DOS_HEADER
Either you specified an unqualified symbol, or your debugger doesn't have full symbol information. Unqualified symbol resolution is turned off by default. Please either specify a fully qualified symbol module!symbolname, or enable resolution of unqualified symbols by typing ".symopt- 100". Note that enabling unqualified symbol resolution with network symbol server shares in the symbol path may cause the debugger to appear to hang for long periods of time when an incorrect symbol name is typed or the network symbol server is down.
For some commands 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!_IMAGE_DOS_HEADER
Either you specified an unqualified symbol, or your debugger doesn't have full symbol information. Unqualified symbol resolution is turned off by default. Please either specify a fully qualified symbol module!symbolname, or enable resolution of unqualified symbols by typing ".symopt- 100". Note that enabling unqualified symbol resolution with network symbol server shares in the symbol path may cause the debugger to appear to hang for long periods of time when an incorrect symbol name is typed or the network symbol server is down.
For some commands 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!_IMAGE_DOS_HEADER
Either you specified an unqualified symbol, or your debugger doesn't have full symbol information. Unqualified symbol resolution is turned off by default. Please either specify a fully qualified symbol module!symbolname, or enable resolution of unqualified symbols by typing ".symopt- 100". Note that enabling unqualified symbol resolution with network symbol server shares in the symbol path may cause the debugger to appear to hang for long periods of time when an incorrect symbol name is typed or the network symbol server is down.
For some commands 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!_IMAGE_DOS_HEADER
Either you specified an unqualified symbol, or your debugger doesn't have full symbol information. Unqualified symbol resolution is turned off by default. Please either specify a fully qualified symbol module!symbolname, or enable resolution of unqualified symbols by typing ".symopt- 100". Note that enabling unqualified symbol resolution with network symbol server shares in the symbol path may cause the debugger to appear to hang for long periods of time when an incorrect symbol name is typed or the network symbol server is down.
For some commands 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
Either you specified an unqualified symbol, or your debugger doesn't have full symbol information. Unqualified symbol resolution is turned off by default. Please either specify a fully qualified symbol module!symbolname, or enable resolution of unqualified symbols by typing ".symopt- 100". Note that enabling unqualified symbol resolution with network symbol server shares in the symbol path may cause the debugger to appear to hang for long periods of time when an incorrect symbol name is typed or the network symbol server is down.
For some commands 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
Either you specified an unqualified symbol, or your debugger doesn't have full symbol information. Unqualified symbol resolution is turned off by default. Please either specify a fully qualified symbol module!symbolname, or enable resolution of unqualified symbols by typing ".symopt- 100". Note that enabling unqualified symbol resolution with network symbol server shares in the symbol path may cause the debugger to appear to hang for long periods of time when an incorrect symbol name is typed or the network symbol server is down.
For some commands 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
Either you specified an unqualified symbol, or your debugger doesn't have full symbol information. Unqualified symbol resolution is turned off by default. Please either specify a fully qualified symbol module!symbolname, or enable resolution of unqualified symbols by typing ".symopt- 100". Note that enabling unqualified symbol resolution with network symbol server shares in the symbol path may cause the debugger to appear to hang for long periods of time when an incorrect symbol name is typed or the network symbol server is down.
For some commands 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
Either you specified an unqualified symbol, or your debugger doesn't have full symbol information. Unqualified symbol resolution is turned off by default. Please either specify a fully qualified symbol module!symbolname, or enable resolution of unqualified symbols by typing ".symopt- 100". Note that enabling unqualified symbol resolution with network symbol server shares in the symbol path may cause the debugger to appear to hang for long periods of time when an incorrect symbol name is typed or the network symbol server is down.
For some commands 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
Either you specified an unqualified symbol, or your debugger doesn't have full symbol information. Unqualified symbol resolution is turned off by default. Please either specify a fully qualified symbol module!symbolname, or enable resolution of unqualified symbols by typing ".symopt- 100". Note that enabling unqualified symbol resolution with network symbol server shares in the symbol path may cause the debugger to appear to hang for long periods of time when an incorrect symbol name is typed or the network symbol server is down.
For some commands 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!_EPROCESS
Either you specified an unqualified symbol, or your debugger doesn't have full symbol information. Unqualified symbol resolution is turned off by default. Please either specify a fully qualified symbol module!symbolname, or enable resolution of unqualified symbols by typing ".symopt- 100". Note that enabling unqualified symbol resolution with network symbol server shares in the symbol path may cause the debugger to appear to hang for long periods of time when an incorrect symbol name is typed or the network symbol server is down.
For some commands 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
Either you specified an unqualified symbol, or your debugger doesn't have full symbol information. Unqualified symbol resolution is turned off by default. Please either specify a fully qualified symbol module!symbolname, or enable resolution of unqualified symbols by typing ".symopt- 100". Note that enabling unqualified symbol resolution with network symbol server shares in the symbol path may cause the debugger to appear to hang for long periods of time when an incorrect symbol name is typed or the network symbol server is down.
For some commands 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
Either you specified an unqualified symbol, or your debugger doesn't have full symbol information. Unqualified symbol resolution is turned off by default. Please either specify a fully qualified symbol module!symbolname, or enable resolution of unqualified symbols by typing ".symopt- 100". Note that enabling unqualified symbol resolution with network symbol server shares in the symbol path may cause the debugger to appear to hang for long periods of time when an incorrect symbol name is typed or the network symbol server is down.
For some commands 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
Either you specified an unqualified symbol, or your debugger doesn't have full symbol information. Unqualified symbol resolution is turned off by default. Please either specify a fully qualified symbol module!symbolname, or enable resolution of unqualified symbols by typing ".symopt- 100". Note that enabling unqualified symbol resolution with network symbol server shares in the symbol path may cause the debugger to appear to hang for long periods of time when an incorrect symbol name is typed or the network symbol server is down.
For some commands 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
KEY_VALUES_STRING: 1
FILE_IN_CAB: MEMORY.DMP
ADDITIONAL_DEBUG_TEXT:
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.
WRONG_SYMBOLS_TIMESTAMP: 62738c60
WRONG_SYMBOLS_SIZE: 144f000
FAULTING_MODULE: fffff801a0b50000 nt
DUMP_FILE_ATTRIBUTES: 0x21000
BUGCHECK_CODE: 19e
BUGCHECK_P1: 47
BUGCHECK_P2: ffffd18d949b1ae0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
STACK_TEXT:
ffff9409
ad37f6d8 fffff801326e57c3 : 000000000000019e 0000000000000047 ffffd18d949b1ae0 0000000000000000 : nt!KeBugCheckEx ffff9409ad37f6e0 fffff801326e136a : 0000000000000047 0000000000000047 ffffd18d95112fd0 0000000000000000 : Wdf01000+0x957c3 ffff9409ad37f720 fffff80130d6d619 : ffffd18d949b1ae0 ffffd18d91534e00 ffffd18d94cf7440 00000000000000d5 : Wdf01000+0x9136a ffff9409ad37f770 fffff80130d6e6f5 : ffffd18d949b1ae0 ffffd18d949b1ae8 ffffd18d8fe7cec0 ffffd18d8fe7cec0 : netadaptercx+0x1d619 ffff9409ad37f7c0 fffff80130d6df42 : ffffd18d94904ae0 00000000000000d5 ffffd18d94cf6001 ffffb97f9183d00e : netadaptercx+0x1e6f5 ffff9409ad37f810 fffff80130d6ce59 : ffffd18d8fe7af70 ffffd18d8fe12e68 ffffd18d94cf6001 ffffd18d949b0000 : netadaptercx+0x1df42 ffff9409ad37f880 fffff80130d6b10d : ffffd18d8fe72f10 ffff9409ad37f990 ffffd18d8fe72e90 ffffd18d8fe7af70 : netadaptercx+0x1ce59 ffff9409ad37f8c0 fffff80130d7bd9e : ffffd18d951d6a30 0000000000000002 0000000000000002 ffff9409ad37f968 : netadaptercx+0x1b10d ffff9409ad37f8f0 fffff80130db8acf : ffffd18d951d6a78 0000000000000000 0000000000000000 0000000000000000 : netadaptercx+0x2bd9e ffff9409ad37f920 fffff80130db6bda : 0000000000002700 0000000000002700 ffffd18d97b28570 ffffd18d9681b010 : ExecutionContext+0x8acf ffff9409ad37f9c0 fffff80130db7c02 : ffffd18d9681b010 0000000000000080 fffff80130db7ab0 fffff80100000000 : ExecutionContext+0x6bda ffff9409ad37fa90 fffff801a0faa5fa : ffffd18d8d3d34c0 ffffd18d8d3d34c0 fffff80130db7ab0 ffffd18d9681b010 : ExecutionContext+0x7c02 ffff9409ad37faf0 fffff801a11c2c94 : ffffa981ae791180 ffffd18d8d3d34c0 fffff801a0faa5a0 2b2b2b2b2b2b2b2b : nt!PsGetCurrentThreadStackLimit+0x61a ffff9409ad37fb40 0000000000000000 : ffff9409ad380000 ffff9409ad379000 0000000000000000 0000000000000000 : nt!KeSaveStateForHibernate+0x1084STACK_COMMAND: .cxr; .ecxr ; kb
EXCEPTION_CODE_STR: 62738C60
EXCEPTION_STR: WRONG_SYMBOLS
PROCESS_NAME: ntoskrnl.wrong.symbols.exe
IMAGE_NAME: ntoskrnl.wrong.symbols.exe
MODULE_NAME: nt_wrong_symbols
SYMBOL_NAME: nt_wrong_symbols!62738C60144F000
FAILURE_BUCKET_ID: WRONG_SYMBOLS_X64_26100.1.amd64fre.ge_release.240331-1435_TIMESTAMP_220505-083544_62738C60_nt_wrong_symbols!62738C60144F000
OS_VERSION: 10.0.26100.1
BUILDLAB_STR: ge_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {39aaf8eb-fab6-e138-8c04-af4d304b7cef}
Followup: MachineOwner