Fall 0.1.3 BSOD regression test trunk 65495 ok last trunk build of explorer_old, i did not manage to get that BSOD here trunk 65496 ok welcome to trunk explorer_new: i did not manage to get that BSOD here trunk 68000 ok i did not manage to get that BSOD here trunk 69000 ok i did not manage to get that BSOD here trunk 70068 ok i did not manage to get that BSOD here trunk 70742 ok i did not manage to get that BSOD here trunk 71259 ok i did not manage to get that BSOD here trunk 71318 ok i did not manage to get that BSOD here 0.4.0RC1 ok i did not manage to get that BSOD here 0.4.0RC2 broken i did get BSOD after doing some manual startup + esc-exit-loops 0.4.0 broken i did get BSOD after doing some manual startup + esc-exit-loops 0.4.1RC broken i did get BSOD after doing some manual startup + esc-exit-loops 0.4.1RC3(r71326) broken i did get BSOD after doing some manual startup + esc-exit-loops --------------------------------------------------------------- Seeing that result I was almost 100% sure that we introduced the fall-BSOD regression with the 2 HANDLE_ENTRY_INDESTROY hackfixes from CORE-9836, since we introduced them in-between 0.4.0RC1 & 0.4.0RC2. So I rebuilt with my local-workspace @trunk r71322 and applied those 2 hacks - to my surprise I could not trigger that BSOD in Fall then. My only conclusion is, that it must be some other hack-fix that we currently apply to our release branches, but that is not part of our trunk! It should have been come also in 0.4.0 and it must have been in between 0.4.0RC1 & 0.4.0RC2.