Microsoft (R) Windows Debugger Version 6.8.0004.0 X86

Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [L:\新建文件夹\102819-20264-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***

****************************************************************************

* Symbol loading may be unreliable without a symbol search path.           *

* Use .symfix to have the debugger choose a symbol path.                   *

* After setting your symbol path, use .reload to refresh symbol locations. *

****************************************************************************

Executable search path is:

*********************************************************************

* Symbols can not be loaded because symbol path is not initialized. *

*

*

* The Symbol Path can be set by:                                    *

*   using the _NT_SYMBOL_PATH environment variable.                 *

*   using the -y argument when starting the debugger. *

*   using .sympath and .sympath+

*

*********************************************************************

Unable to load image \SystemRoot\system32\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 Kernel Version 7601 (Service Pack 1) MP (16 procs) Free x64

Product: Server, suite: Enterprise TerminalServer SingleUserTS

Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850

Kernel base = 0xfffff800`01663000 PsLoadedModuleList = 0xfffff800`018a8e90

Debug session time: Mon Oct 28 09:18:37.264 2019 (GMT+8)

System Uptime: 0 days 0:21:32.811

*********************************************************************

* Symbols can not be loaded because symbol path is not initialized. *

*

*

* The Symbol Path can be set by:                                    *

*   using the _NT_SYMBOL_PATH environment variable.                 *

*   using the -y argument when starting the debugger. *

*   using .sympath and .sympath+

*

*********************************************************************

Unable to load image \SystemRoot\system32\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 D1, {ffffffffffdff128, 2, 0, fffff88001009a91}

Unable to load image \SystemRoot\system32\DRIVERS\NETIO.SYS, Win32 error 0n2

*** WARNING: Unable to verify timestamp for NETIO.SYS

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

Unable to load image \SystemRoot\System32\drivers\tcpip.sys, Win32 error 0n2

*** WARNING: Unable to verify timestamp for tcpip.sys

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

Unable to load image \SystemRoot\System32\DRIVERS\srvnet.sys, Win32 error 0n2

*** WARNING: Unable to verify timestamp for srvnet.sys

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

Unable to load image \SystemRoot\system32\drivers\afd.sys, Win32 error 0n2

*** WARNING: Unable to verify timestamp for afd.sys

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

***** 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

***

***

***

*************************************************************************

*************************************************************************

***

***

***

***

***    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

***

***

***

*************************************************************************

*********************************************************************

* Symbols can not be loaded because symbol path is not initialized. *

*

*

* The Symbol Path can be set by:                                    *

*   using the _NT_SYMBOL_PATH environment variable.                 *

*   using the -y argument when starting the debugger. *

*   using .sympath and .sympath+

*

*********************************************************************

*********************************************************************

* Symbols can not be loaded because symbol path is not initialized. *

*

*

* The Symbol Path can be set by:                                    *

*   using the _NT_SYMBOL_PATH environment variable.                 *

*   using the -y argument when starting the debugger. *

*   using .sympath and .sympath+

*

*********************************************************************

Probably caused by : NETIO.SYS ( NETIO+9a91 )

Followup: MachineOwner

---------