You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Do not install the trap_fatal hook on 13.00
install_hooks wrote three bytes and an absolute jmp at kernbase+0x1718D8, an
offset hardcoded for one firmware that never came from a per-firmware table.
On 13.00 that address is 0x68 bytes inside an unrelated function, on a
mov/test/jnz sequence. Overwriting it meant every thread that ran that
function jumped into hook_trap_fatal with the wrong registers.
That is what powered the console off whenever an app was launched: the crash
came from the kernel executing its own corrupted code, with the payload idle
and no request in flight, which is why throttling the dashboard and locking
the allproc walks did not help.
The hook only formats crash information into klog and nothing depends on it,
so it is skipped where the offset has not been checked rather than patched
blind. Every other firmware keeps the behaviour it had.