Windows Hardware Breakpoints-Implementing a single-step exception

The offending one-step exception is the current eflags instead of the eflags that triggered the exception

That is

Pushf

MOV EAX, DWORD Ptr[esp]

OR EAX, 0x100

MOV DWORD PTR [ESP], EAX
Popf

To implement a single-step exception (especially if you need to be aware that the next statement will trigger a single-step exception after the single-step exception setting). If you do not do the processing. Will cause the crash or even the blue aunt)

Windows Hardware Breakpoints-Implementing a single-step exception