NtSerializeBoot
Triggers serialization of the boot trace buffer — finalizes performance data collected during early system start.
Prototype
NTSTATUS NtSerializeBoot(VOID);
Arguments
| Name | Type | Dir | Description |
|---|
Syscall IDs by Windows version
| Windows version | Syscall ID | Build |
|---|---|---|
| Win10 1507 | 0x16B | win10-1507 |
| Win10 1607 | 0x173 | win10-1607 |
| Win10 1703 | 0x179 | win10-1703 |
| Win10 1709 | 0x17C | win10-1709 |
| Win10 1803 | 0x17E | win10-1803 |
| Win10 1809 | 0x17F | win10-1809 |
| Win10 1903 | 0x180 | win10-1903 |
| Win10 1909 | 0x180 | win10-1909 |
| Win10 2004 | 0x186 | win10-2004 |
| Win10 20H2 | 0x186 | win10-20h2 |
| Win10 21H1 | 0x186 | win10-21h1 |
| Win10 21H2 | 0x188 | win10-21h2 |
| Win10 22H2 | 0x188 | win10-22h2 |
| Win11 21H2 | 0x190 | win11-21h2 |
| Win11 22H2 | 0x193 | win11-22h2 |
| Win11 23H2 | 0x193 | win11-23h2 |
| Win11 24H2 | 0x195 | win11-24h2 |
| Server 2016 | 0x173 | winserver-2016 |
| Server 2019 | 0x17F | winserver-2019 |
| Server 2022 | 0x18E | winserver-2022 |
| Server 2025 | 0x195 | winserver-2025 |
Kernel module
Related APIs
Syscall stub
4C 8B D1 mov r10, rcx B8 95 01 00 00 mov eax, 0x195 F6 04 25 08 03 FE 7F 01 test byte ptr [0x7FFE0308], 1 75 03 jne short +3 0F 05 syscall C3 ret CD 2E int 2Eh C3 ret
Undocumented notes
Performance-diagnostics primitive: called once by the Session Manager (smss.exe) and prefetcher infrastructure to signal that the boot phase is complete and the kernel may serialize the in-memory boot trace to disk (e.g. for `xperf -on Base+Boot` style sessions and the SuperFetch boot prefetcher). No arguments, no inputs to forge. Calling it outside the legitimate one-shot context is effectively a no-op or returns STATUS_UNSUCCESSFUL. Microsoft documentation is minimal because the routine is part of the prefetcher contract rather than a public Win32 surface.
Common malware usage
Minimal offensive value. There is no privilege-escalation primitive here, no information disclosure beyond what the prefetcher already writes to %SystemRoot%\Prefetch, and no behavioural change. Occasionally referenced as a curiosity in syscall-table tooling but not part of any documented malware family's TTPs.
Detection opportunities
Treat as a baseline curiosity. Microsoft-Windows-Kernel-Prefetch ETW provider records prefetcher state transitions; if NtSerializeBoot is invoked from anything other than smss.exe (or the prefetcher service) it is anomalous, but the practical false-positive cost of alerting is low because the legitimate caller count is one. Defenders generally do not need to track this — focus telemetry budget elsewhere.
Direct syscall examples
asmx64 direct stub (Win11 24H2)
; Direct syscall stub for NtSerializeBoot (SSN 0x195, Win11 24H2)
NtSerializeBoot PROC
mov r10, rcx
mov eax, 195h
syscall
ret
NtSerializeBoot ENDPcSmss-style finalize call
// This is what smss.exe does once the boot phase completes. Calling it again from // a user-mode process is a no-op in practice. extern NTSTATUS NTAPI NtSerializeBoot(VOID); NTSTATUS s = NtSerializeBoot(); // s == STATUS_SUCCESS only inside the one legitimate caller's lifetime.
MITRE ATT&CK mappings
Last verified: 2026-05-20