Windows 10 bug
This one is kind of neat, I would love to know how an RO operation "corrupts" something, maybe a file trigger?: https://www.bleepingcomputer.com/news/security/windows-10-bug-corrupts-your-hard-drive-on-seeing-this-files-icon/
Or maybe it borks the file table pointer? I thought it was neat.
EDIT: For anyone who wants to play with it but doesn't have a Hypervisor, Windows Sandbox is a thing.
Or maybe it borks the file table pointer? I thought it was neat.
EDIT: For anyone who wants to play with it but doesn't have a Hypervisor, Windows Sandbox is a thing.
Last edited on
Typical ... put in some special hidden something and someone will find it and cause trouble with it.
There have been so many complete fails like this... at one time there was a hidden cpu instruction and if you called it, the computer froze and needed a boot (early pentium, I think?). Edit: there have been many, many of these, early pentium included.
There have been so many complete fails like this... at one time there was a hidden cpu instruction and if you called it, the computer froze and needed a boot (early pentium, I think?). Edit: there have been many, many of these, early pentium included.
Last edited on
Although it looks like a read-only (RO) operation, it must somehow not be. If the $i30 file contains timestamps for access time then updating the time is a write operation. Is it some kind of strange loop since you're accessing the $i30 file itself?
| at one time there was a hidden cpu instruction and if you called it, the computer froze and needed a boot |
Maybe the infamous F00F bug:
https://en.wikipedia.org/wiki/Pentium_F00F_bug
Topic archived. No new replies allowed.