BSOD on all windows

Why the fuck would inspecting the MFT cause a kernel panic?

>>60528589
Because Windows.

>>60528589
it's a magic!

>>60528577
lololol it hung VIsta SP2 :DDDDD

Not BSOD but still wtf.

>>60528577
just tried the console one on Win7 Ultimate
It didn't bluescreen but it did freeze the system.
>embed the html
>if you cannot open that link, you don't belong to /g/

so windows is fucked up... again..

>>60528790
*still fucked up

The Apple Macbook Pro with Retina Display doesn't have this problem.

>>60528577
doesn't work on XP SP3, neither of those two, actually.

>>60528891
It does if you install Windows on it.

File: u wot.png (40KB, 943x555px) Image search: [Google]

40KB, 943x555px

Have I been taken on a ruse cruise

>>60528947
RIP anon, he won't be posting before he reboots.

>>60528577
No BSoD, but it did freeze my PC. Windows 7.

Explanation in russian - https://habrahabr.ru/company/aladdinrd/blog/329166/

tl:dr - last updates (mosly) resolve this issue.

File: pop-command-prompt.png (25KB, 559x417px) Image search: [Google]

25KB, 559x417px

>>60528947
Why windows 10 path is all capital like in windows xp?

doesn't work on xp

>>60529188
This bug works on Vista+

>>60529129
Kek

So basically it's a system file/directory where NTFS logs all file operations or something like that, for concurrency safety if I understand correctly. So every time a file gets e.g. opened, the system obtains a lock on $mft, writes whatever synchronisation info is needed, opens the file (or whatever other operation was requested), does more stuff on $mft to signal the end of the transaction, releases $mft.

Obviously, if the file operation requested takes place inside $mft, that results in a problem.

>>60528577
Only works as admin.

>>60530446
Nope, done it on Vista as regular user.

>>60529425
so it's a semaphore that isn't meant to be directly accessed?

>>60531407
Something along those lines, if my understanding of the linked article is correct.

I can't into technical russian very well though.

>>60531407
$mft is system file which is always opened. When OS tries to find $mft/hello it locks it and when it finds out that it's not directory it closes it and because it can't do it it fucks up.

I guess that similar BS happens with any other file: if OS tries to treat it as directory the handle closes without program which uses it knowing that.