New
#100
MS did not post that. Nonetheless, it seems that this is a resolved crisis.
Sinofsky:
Some have reported (as above) that this specific issue repros and then goes away with updated drivers. We haven’t yet confirmed that either but continue to try. We just kicked off overnight stress testing of 40 machines of variants as reported by FireRx. We’ll see.
"As above" refers to this:
FireRx:
After emailing back and forth with the VP Sinofsky, it was found that the chkdsk /r tool is not at fault here. It was simply a chipset controller issue. Please update you chipset drivers to the current driver from your motherboard manufacturer.
FireRX put words in Sinofsky's mouth.