Ida GDB Remote Debugging

In the snow to answer the question, someone asked in WinDbg down Kidebugroutine or Kdenterdebugger function will cause a blue screen! Because it was debugging the kernel debugging engine for Windows, the workaround I gave was to debug it with a kernel debug engine that doesn't rely on windows, and to use Ida's remote debugging when I previously analyzed the Windows startup process. Debug the system when the Windows kernel debug engine is not initialized, and use Ida's remote debugging to fix it.

Ida--->debugger--->attacth---->remote GDB Debugger

Kd>u kdenterdebuggernt!kdenterdebugger:8414116d 8BFF mov edi,edi8414116f -Push EBP841411708bec mov ebp,esp84141172 Wuyipush ECX84141173  -push EBX841411748B5D08 mov ebx,dword ptr [ebp+8]84141177  Aboutpush ESI84141178  $Push EDI

And then down to the absolute address of Kdenterdebugger directly in Ida.

Ida's accelerator G enters the absolute address of the Kdenterdebugger, then F2 down the breakpoint, F9 runs, and when WinDbg down the breakpoint again, it breaks in the Kdenterdebugger function in Ida.

Ida GDB Remote debugging