As is clear from the information coming from different sources, checking the media data with the command chkdsk / r (find bad sectors, and giving play to read the files) in certain circumstances, absorbs so much RAM that the system crashes, resets, or emergency exits. In the first test of our editors did not manage to play as if this behavior.
Exactly the circumstances of the occurrence of this error is not clear: the comments can be concluded that the error does not appear every time, but its presence is dependent on the amount of memory, which has computer classes and the extent of media data. At issue in this blog has already Steven Sinofsky (the main Windows developer). It confirms that the chkdsk with the / r requires 50 MB of RAM, so that the work carried out as soon as possible. Developer reassured, however, claiming that he did not play the system or so-called exemptions. blue screens due to defective work of this tool.
Microsoft conducts stringent tests and suspected that the presence of this error may be related to outdated drivers or damaged equipment, as confirmed by one of the other commentators.