Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
- Copyright (c) Microsoft Corporation. All rights reserved.
- Opened \\.\com3
- Waiting to reconnect...
- Connected to Windows Server 2003 3790 x64 target at (Sun Dec 11 10:16:23.753 2022 (GMT+1)), ptr64 TRUE
- Kernel Debugger connection established.
- 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 <symbol_path> argument when starting the debugger. *
- * using .sympath and .sympath+ *
- *********************************************************************
- *** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
- Windows Server 2003 Kernel Version 3790 MP (1 procs) Free x64
- Built by: 3790.srv03_sp2_rtm.070216-1710
- Machine Name:
- Kernel base = 0xfffff800`01800000 PsLoadedModuleList = 0xfffff800`019d5100
- System Uptime: not available
- Intel Storage Driver Ver: 11.2.0.1006
- *** Fatal System Error: 0x0000007b
- (0xFFFFFADF2CC163C0,0xFFFFFFFFC0000034,0x0000000000000000,0x0000000000000000)
- Break instruction exception - code 80000003 (first chance)
- A fatal system error has occurred.
- Debugger entered on first try; Bugcheck callbacks have not been invoked.
- A fatal system error has occurred.
- *********************************************************************
- * 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 <symbol_path> argument when starting the debugger. *
- * using .sympath and .sympath+ *
- *********************************************************************
- *** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
- *******************************************************************************
- * *
- * Bugcheck Analysis *
- * *
- *******************************************************************************
- Use !analyze -v to get detailed debugging information.
- BugCheck 7B, {fffffadf2cc163c0, ffffffffc0000034, 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 ***
- *** ***
- *************************************************************************
- *********************************************************************
- * 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 <symbol_path> 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 <symbol_path> argument when starting the debugger. *
- * using .sympath and .sympath+ *
- *********************************************************************
- Probably caused by : ntkrnlmp.exe ( nt!KeDisconnectInterrupt+48e )
- Followup: MachineOwner
- ---------
- nt!DbgBreakPointWithStatus:
- fffff800`01826db0 cc int 3
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement