Oops..๐Ÿคฃ๐Ÿคฃ
276
8,557
1,120
35,094
714,900
Replying to @c0dehard @duff22b
Wrong BSOD code for this case. ๐Ÿง

11:03 PM ยท Nov 14, 2020

2
0
0
25
Good catch ๐Ÿ‘
0
0
0
0
Entirely possible that an allocation call in a critical process (e.g. smss/winlogon) failed because of an OOM condition, causing it to crash (e.g. unchecked malloc result causing null pointer deref), leading to this BSOD code.
1
0
0
7
It is even easier if you mark your own process as critical and make it fail. Just not very realistic for me :)
0
0
0
0