Advertisement
jzef

break_debug

May 30th, 2024
23
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 5.98 KB | None | 0 0
  1.  
  2. Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
  3. Copyright (c) Microsoft Corporation. All rights reserved.
  4.  
  5. Opened \\.\com3
  6. Waiting to reconnect...
  7. BD: Boot Debugger Initialized
  8. Connected to Windows Boot Debugger 6001 x64 target at (Thu May 30 07:16:57.873 2024 (UTC + 2:00)), ptr64 TRUE
  9. Kernel Debugger connection established.
  10. Symbol search path is: C:\Windows\Symbols
  11. Executable search path is:
  12. *** ERROR: Module load completed but symbols could not be loaded for winload.efi
  13. Windows Boot Debugger Kernel Version 6001 UP Free x64
  14. Machine Name:
  15. Primary image base = 0x00000000`00350000 Loaded module list = 0x00000000`00466c40
  16. System Uptime: not available
  17. Shutdown occurred at (Thu May 30 07:17:03.045 2024 (UTC + 2:00))...unloading all symbol tables.
  18. Waiting to reconnect...
  19. Connected to Windows Server 2003 3790 x64 target at (Thu May 30 07:17:03.936 2024 (UTC + 2:00)), ptr64 TRUE
  20. Kernel Debugger connection established.
  21. Symbol search path is: C:\Windows\Symbols
  22. Executable search path is:
  23. Windows Server 2003 Kernel Version 3790 MP (1 procs) Free x64
  24. Built by: 3790.srv03_sp2_rtm.070216-1710
  25. Machine Name:
  26. Kernel base = 0xfffff800`01600000 PsLoadedModuleList = 0xfffff800`017d5100
  27. System Uptime: not available
  28. KDTARGET: Refreshing KD connection
  29. gLog = 723d3000 , index = FFFFFADE505D9400Break instruction exception - code 80000003 (first chance)
  30. *******************************************************************************
  31. * *
  32. * You are seeing this message because you pressed either *
  33. * CTRL+C (if you run kd.exe) or, *
  34. * CTRL+BREAK (if you run WinDBG), *
  35. * on your debugger machine's keyboard. *
  36. * *
  37. * THIS IS NOT A BUG OR A SYSTEM CRASH *
  38. * *
  39. * If you did not intend to break into the debugger, press the "g" key, then *
  40. * press the "Enter" key now. This message might immediately reappear. If it *
  41. * does, press "g" and "Enter" again. *
  42. * *
  43. *******************************************************************************
  44. nt!DbgBreakPointWithStatus:
  45. fffff800`01626db0 cc int 3
  46. *** WARNING: Unable to verify timestamp for ntdll.dll
  47. 3: kd> !analyze -v
  48. Connected to Windows Server 2003 3790 x64 target at (Thu May 30 07:18:47.987 2024 (UTC + 2:00)), ptr64 TRUE
  49. Loading Kernel Symbols
  50. ...............................................................
  51. ......................................
  52. Loading User Symbols
  53.  
  54. Loading unloaded module list
  55. .......
  56. *** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
  57. *******************************************************************************
  58. * *
  59. * Bugcheck Analysis *
  60. * *
  61. *******************************************************************************
  62.  
  63. Unknown bugcheck code (0)
  64. Unknown bugcheck description
  65. Arguments:
  66. Arg1: 0000000000000000
  67. Arg2: 0000000000000000
  68. Arg3: 0000000000000000
  69. Arg4: 0000000000000000
  70.  
  71. Debugging Details:
  72. ------------------
  73.  
  74.  
  75. PROCESS_NAME: Idle
  76.  
  77. FAULTING_IP:
  78. nt!DbgBreakPointWithStatus+0
  79. fffff800`01626db0 cc int 3
  80.  
  81. EXCEPTION_RECORD: ffffffffffffffff -- (.exr 0xffffffffffffffff)
  82. ExceptionAddress: fffff80001626db0 (nt!DbgBreakPointWithStatus)
  83. ExceptionCode: 80000003 (Break instruction exception)
  84. ExceptionFlags: 00000000
  85. NumberParameters: 1
  86. Parameter[0]: 0000000000000000
  87.  
  88. ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION} Breakpoint A breakpoint has been reached.
  89.  
  90. EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments are invalid
  91.  
  92. EXCEPTION_PARAMETER1: 0000000000000000
  93.  
  94. DEFAULT_BUCKET_ID: DRIVER_FAULT
  95.  
  96. BUGCHECK_STR: 0x0
  97.  
  98. CURRENT_IRQL: d
  99.  
  100. STACK_TEXT:
  101. fffffade`5ea32b38 fffff800`016791ff : 00000000`00000062 00000000`00000000 00000000`00000000 00000000`00000000 : nt!DbgBreakPointWithStatus
  102. fffffade`5ea32b40 fffff800`016299fb : fffffade`00000004 fffff800`016680c9 fffffade`5e6cb180 fffffade`7318c0d0 : nt!KdCheckForDebugBreak+0xb5
  103. fffffade`5ea32b80 fffff800`01629794 : fffffade`5e6cd480 fffffade`5ea32c30 fffffade`5e6cd480 fffffade`7318c0d0 : nt!KeUpdateRunTime+0x19e
  104. fffffade`5ea32bb0 fffffade`5e309b42 : fffffade`5e309759 fffff800`017b5940 fffffade`73ce3bf0 fffffade`5ea32d70 : nt!KiSecondaryClockInterrupt+0xe4
  105. fffffade`5ea32d48 fffffade`5e309759 : fffff800`017b5940 fffffade`73ce3bf0 fffffade`5ea32d70 fffffade`7318c0d0 : intelppm+0x3b42
  106. fffffade`5ea32d50 fffff800`016319cc : fffffade`5e6cd600 fffff800`017b5901 fffffade`5e6cd450 00000000`00000000 : intelppm+0x3759
  107. fffffade`5ea32d80 fffff800`01667cde : fffffade`5e6cb180 fffffade`5e6cb180 fffffade`5e6d3680 fffffade`73ce3bf0 : nt!PopProcessorIdle+0x114
  108. fffffade`5ea32db0 fffff800`01a151d1 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x1e
  109. fffffade`5ea32de0 00000000`fffffade : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemStartup+0x1bf
  110. fffffade`5e6cd640 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00680000`00000000 : 0xfffffade
  111.  
  112.  
  113. STACK_COMMAND: kb
  114.  
  115. FOLLOWUP_IP:
  116. nt!DbgBreakPointWithStatus+0
  117. fffff800`01626db0 cc int 3
  118.  
  119. SYMBOL_STACK_INDEX: 0
  120.  
  121. SYMBOL_NAME: nt!DbgBreakPointWithStatus+0
  122.  
  123. FOLLOWUP_NAME: MachineOwner
  124.  
  125. MODULE_NAME: nt
  126.  
  127. IMAGE_NAME: ntkrnlmp.exe
  128.  
  129. DEBUG_FLR_IMAGE_TIMESTAMP: 45d69ab4
  130.  
  131. BUCKET_ID: MANUAL_BREAKIN
  132.  
  133. Followup: MachineOwner
  134. ---------
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement