4
Windows 8 has a new approach to checking the disk for inconsistencies, and I'm confused about what I'm seeing.
- In the properties dialog for
C:
I launch the disk error checker. - It says I don't need to scan the drive, but I can check if I want.
- Going ahead with the check pops up a dialog saying:
Error Checking (OS (C:)) - Repair this drive
Windows has found errors on this drive that need to be repaired. Close this dialogue box and then repair the drive.
Google turns up nothing on that message.
The only options I have are 'show details' and 'close'. Showing details launches the Event Viewer, showing the Application log with no entries in the list at all.
Hunting through the Administrative Events list I see this entry as the first one since booting:
NTFS - The default transaction resource manager on volume C: encountered a non-retryable error and could not start. The data contains the error code.
The data follows:
Log Name: System
Source: Ntfs
Date: 11/02/2013 17:40:12
Event ID: 137
Task Category: (2)
Level: Error
Keywords: Classic
User: N/A
Computer: bert
Description:
The default transaction resource manager on volume C: encountered a non-retryable error and could not start. The data contains the error code.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Ntfs" />
<EventID Qualifiers="49156">137</EventID>
<Level>2</Level>
<Task>2</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-02-11T17:40:12.670134500Z" />
<EventRecordID>61524</EventRecordID>
<Channel>System</Channel>
<Computer>bert</Computer>
<Security />
</System>
<EventData>
<Data>
</Data>
<Data>C:</Data>
<Binary>1C0004000200300002000000890004C0000000007F0000C0000000000000000000000000000000007F0000C0</Binary>
</EventData>
</Event>
I'm unsure that these two problems are related. In fact, the reason I'm trying to check the disk at all is that my Ubuntu (WUBI) is failing to boot, and I suspect volume trouble. Someone on ubuntuforums suggested I chkdsk the volume first from Windows.
So my question is, how am I to verify that the disk has no errors when the tools are providing contradictory and unhelpful messages?
Based on the event log, it looks like, Windows wasn't even able to scan the volume for errors. Clearly based on your answer that was exactly the case. – Ramhound – 2013-02-12T12:42:21.490