DebugPrivilege
@debugger.bsky.social
System Administrator | Ex-MSFT | Microsoft MVP in Windows and Devices | Interested in Security, Debugging, and Windows Internals. Tweets are my own.
To be honest, I can't believe I missed this. The !analyze -v command was already pointing to the driver as the cause, but I ignored it. I guess I'll have to double-check more carefully next time, but I'm satisfied with the analysis I've done. 😅
October 8, 2025 at 1:29 AM
To be honest, I can't believe I missed this. The !analyze -v command was already pointing to the driver as the cause, but I ignored it. I guess I'll have to double-check more carefully next time, but I'm satisfied with the analysis I've done. 😅
Of course the private symbols are not available, so the ETW traces might be difficult to read. Other than that, it collects relevant data though :-)
September 21, 2025 at 10:01 AM
Of course the private symbols are not available, so the ETW traces might be difficult to read. Other than that, it collects relevant data though :-)
Agreed. I still use Twitter though, but I've reduced my social media time a lot.
April 7, 2025 at 9:04 AM
Agreed. I still use Twitter though, but I've reduced my social media time a lot.
- No more pizza with pineapple
January 7, 2025 at 5:14 PM
- No more pizza with pineapple