chkdsk produces different errors every time after 40 tries
I was getting a BSOD even when trying to boot into safe mode, so I booted from the Windows 7 install disk, pressed Shift+F10 to enter command prompt mode right away (because I have several operating systems on this system, the infinitely despicable so-called "Repair Mode" -- what a misnomer! -- takes about 40 minutes searching for operating systems to "repair").
Then I determine which drive letter is associated with the system disk in question, then enter CHKDSK /F
It found errors the first couple of times and claimed to have repaired them, and eventually it reported that it had found no errors. But I've learned over the years that this can be a lie, so I've gotten in the habit of running the command again and again until it claims it found no errors twice in a row.
I've now run it about 40 times, and every single time now it reports errors, typically first the same one or two (corrupted attribute record x), then always one or more different error(s) every single time! Sometimes it reports that the volume is in use by a different process and asks if I want to dismount it first (to which I answer yes), but what other process could possibly have it attached at this point? Perhaps the infinitely stupid "searching for operating system" process, that's still running after all this time?
Anyway, what the heck do I do now?
windows-7 chkdsk
asked Jan 20 at 0:27
Nate BrazilNate Brazil
12
|
show 2 more comments
I was getting a BSOD even when trying to boot into safe mode, so I booted from the Windows 7 install disk, pressed Shift+F10 to enter command prompt mode right away (because I have several operating systems on this system, the infinitely despicable so-called "Repair Mode" -- what a misnomer! -- takes about 40 minutes searching for operating systems to "repair").
Then I determine which drive letter is associated with the system disk in question, then enter CHKDSK /F
It found errors the first couple of times and claimed to have repaired them, and eventually it reported that it had found no errors. But I've learned over the years that this can be a lie, so I've gotten in the habit of running the command again and again until it claims it found no errors twice in a row.
I've now run it about 40 times, and every single time now it reports errors, typically first the same one or two (corrupted attribute record x), then always one or more different error(s) every single time! Sometimes it reports that the volume is in use by a different process and asks if I want to dismount it first (to which I answer yes), but what other process could possibly have it attached at this point? Perhaps the infinitely stupid "searching for operating system" process, that's still running after all this time?
Anyway, what the heck do I do now?
windows-7 chkdsk
asked Jan 20 at 0:27
Nate BrazilNate Brazil
12
1
Is your RAM OK?
– Kamil Maciorowski
Jan 20 at 0:32
1
Have you checked the disk SMART status? howtogeek.com/134735/how-to-see-if-your-hard-drive-is-dying
– DrMoishe Pippik
Jan 20 at 0:34
Thanks to you both. I'll test both now...
– Nate Brazil
Jan 20 at 0:34
I'm running MemTest86+ right now. I'll report back after a good long run. As for the SMART status, that's trickier since the disk at issue is a two-SSD RAID 0 array, and you can't test SMART on a RAID array. But after the RAM testing is done, I can separate the two SSDs temporarily and then test the SMART status on both individually.
– Nate Brazil
Jan 20 at 0:50
MemTest86+ reported 12 errors, but I only now learned that it can't save a report. So I just started over using PassMark's MemTest86 V8 Free, which does save a report to the USB boot drive. Since I previously had XMP1 mode enabled, I have disabled it for this tool. it is most likely that it will also find errors, but the doc points out that given my Intel CPU, it will be too difficult to determine the specific problem DIMM from the report. Thus, I'll have to run it with one DIMM at a time. Is this correct, folks?
– Nate Brazil
Jan 20 at 18:52
|
show 2 more comments
I was getting a BSOD even when trying to boot into safe mode, so I booted from the Windows 7 install disk, pressed Shift+F10 to enter command prompt mode right away (because I have several operating systems on this system, the infinitely despicable so-called "Repair Mode" -- what a misnomer! -- takes about 40 minutes searching for operating systems to "repair").
Then I determine which drive letter is associated with the system disk in question, then enter CHKDSK /F
It found errors the first couple of times and claimed to have repaired them, and eventually it reported that it had found no errors. But I've learned over the years that this can be a lie, so I've gotten in the habit of running the command again and again until it claims it found no errors twice in a row.
I've now run it about 40 times, and every single time now it reports errors, typically first the same one or two (corrupted attribute record x), then always one or more different error(s) every single time! Sometimes it reports that the volume is in use by a different process and asks if I want to dismount it first (to which I answer yes), but what other process could possibly have it attached at this point? Perhaps the infinitely stupid "searching for operating system" process, that's still running after all this time?
Anyway, what the heck do I do now?
windows-7 chkdsk
asked Jan 20 at 0:27
Nate BrazilNate Brazil
12
I was getting a BSOD even when trying to boot into safe mode, so I booted from the Windows 7 install disk, pressed Shift+F10 to enter command prompt mode right away (because I have several operating systems on this system, the infinitely despicable so-called "Repair Mode" -- what a misnomer! -- takes about 40 minutes searching for operating systems to "repair").
Then I determine which drive letter is associated with the system disk in question, then enter CHKDSK /F
It found errors the first couple of times and claimed to have repaired them, and eventually it reported that it had found no errors. But I've learned over the years that this can be a lie, so I've gotten in the habit of running the command again and again until it claims it found no errors twice in a row.
I've now run it about 40 times, and every single time now it reports errors, typically first the same one or two (corrupted attribute record x), then always one or more different error(s) every single time! Sometimes it reports that the volume is in use by a different process and asks if I want to dismount it first (to which I answer yes), but what other process could possibly have it attached at this point? Perhaps the infinitely stupid "searching for operating system" process, that's still running after all this time?
Anyway, what the heck do I do now?
windows-7 chkdsk
windows-7 chkdsk
asked Jan 20 at 0:27
Nate BrazilNate Brazil
12
asked Jan 20 at 0:27
Nate BrazilNate Brazil
12
asked Jan 20 at 0:27
Nate BrazilNate Brazil
12
asked Jan 20 at 0:27
Nate BrazilNate Brazil
12
asked Jan 20 at 0:27
Nate BrazilNate Brazil
12
12
1
Is your RAM OK?
– Kamil Maciorowski
Jan 20 at 0:32
1
Have you checked the disk SMART status? howtogeek.com/134735/how-to-see-if-your-hard-drive-is-dying
– DrMoishe Pippik
Jan 20 at 0:34
Thanks to you both. I'll test both now...
– Nate Brazil
Jan 20 at 0:34
I'm running MemTest86+ right now. I'll report back after a good long run. As for the SMART status, that's trickier since the disk at issue is a two-SSD RAID 0 array, and you can't test SMART on a RAID array. But after the RAM testing is done, I can separate the two SSDs temporarily and then test the SMART status on both individually.
– Nate Brazil
Jan 20 at 0:50
MemTest86+ reported 12 errors, but I only now learned that it can't save a report. So I just started over using PassMark's MemTest86 V8 Free, which does save a report to the USB boot drive. Since I previously had XMP1 mode enabled, I have disabled it for this tool. it is most likely that it will also find errors, but the doc points out that given my Intel CPU, it will be too difficult to determine the specific problem DIMM from the report. Thus, I'll have to run it with one DIMM at a time. Is this correct, folks?
– Nate Brazil
Jan 20 at 18:52
|
show 2 more comments
1
Is your RAM OK?
– Kamil Maciorowski
Jan 20 at 0:32
1
Have you checked the disk SMART status? howtogeek.com/134735/how-to-see-if-your-hard-drive-is-dying
– DrMoishe Pippik
Jan 20 at 0:34
Thanks to you both. I'll test both now...
– Nate Brazil
Jan 20 at 0:34
I'm running MemTest86+ right now. I'll report back after a good long run. As for the SMART status, that's trickier since the disk at issue is a two-SSD RAID 0 array, and you can't test SMART on a RAID array. But after the RAM testing is done, I can separate the two SSDs temporarily and then test the SMART status on both individually.
– Nate Brazil
Jan 20 at 0:50
MemTest86+ reported 12 errors, but I only now learned that it can't save a report. So I just started over using PassMark's MemTest86 V8 Free, which does save a report to the USB boot drive. Since I previously had XMP1 mode enabled, I have disabled it for this tool. it is most likely that it will also find errors, but the doc points out that given my Intel CPU, it will be too difficult to determine the specific problem DIMM from the report. Thus, I'll have to run it with one DIMM at a time. Is this correct, folks?
– Nate Brazil
Jan 20 at 18:52
1
1
Is your RAM OK?
– Kamil Maciorowski
Jan 20 at 0:32
Is your RAM OK?
– Kamil Maciorowski
Jan 20 at 0:32
1
1
Have you checked the disk SMART status? howtogeek.com/134735/how-to-see-if-your-hard-drive-is-dying
– DrMoishe Pippik
Jan 20 at 0:34
Have you checked the disk SMART status? howtogeek.com/134735/how-to-see-if-your-hard-drive-is-dying
– DrMoishe Pippik
Jan 20 at 0:34
Thanks to you both. I'll test both now...
– Nate Brazil
Jan 20 at 0:34
Thanks to you both. I'll test both now...
– Nate Brazil
Jan 20 at 0:34
I'm running MemTest86+ right now. I'll report back after a good long run. As for the SMART status, that's trickier since the disk at issue is a two-SSD RAID 0 array, and you can't test SMART on a RAID array. But after the RAM testing is done, I can separate the two SSDs temporarily and then test the SMART status on both individually.
– Nate Brazil
Jan 20 at 0:50
I'm running MemTest86+ right now. I'll report back after a good long run. As for the SMART status, that's trickier since the disk at issue is a two-SSD RAID 0 array, and you can't test SMART on a RAID array. But after the RAM testing is done, I can separate the two SSDs temporarily and then test the SMART status on both individually.
– Nate Brazil
Jan 20 at 0:50
MemTest86+ reported 12 errors, but I only now learned that it can't save a report. So I just started over using PassMark's MemTest86 V8 Free, which does save a report to the USB boot drive. Since I previously had XMP1 mode enabled, I have disabled it for this tool. it is most likely that it will also find errors, but the doc points out that given my Intel CPU, it will be too difficult to determine the specific problem DIMM from the report. Thus, I'll have to run it with one DIMM at a time. Is this correct, folks?
– Nate Brazil
Jan 20 at 18:52
MemTest86+ reported 12 errors, but I only now learned that it can't save a report. So I just started over using PassMark's MemTest86 V8 Free, which does save a report to the USB boot drive. Since I previously had XMP1 mode enabled, I have disabled it for this tool. it is most likely that it will also find errors, but the doc points out that given my Intel CPU, it will be too difficult to determine the specific problem DIMM from the report. Thus, I'll have to run it with one DIMM at a time. Is this correct, folks?
– Nate Brazil
Jan 20 at 18:52
|
show 2 more comments
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1396204%2fchkdsk-produces-different-errors-every-time-after-40-tries%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1396204%2fchkdsk-produces-different-errors-every-time-after-40-tries%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
Is your RAM OK?
– Kamil Maciorowski
Jan 20 at 0:32
1
Have you checked the disk SMART status? howtogeek.com/134735/how-to-see-if-your-hard-drive-is-dying
– DrMoishe Pippik
Jan 20 at 0:34
Thanks to you both. I'll test both now...
– Nate Brazil
Jan 20 at 0:34
I'm running MemTest86+ right now. I'll report back after a good long run. As for the SMART status, that's trickier since the disk at issue is a two-SSD RAID 0 array, and you can't test SMART on a RAID array. But after the RAM testing is done, I can separate the two SSDs temporarily and then test the SMART status on both individually.
– Nate Brazil
Jan 20 at 0:50
MemTest86+ reported 12 errors, but I only now learned that it can't save a report. So I just started over using PassMark's MemTest86 V8 Free, which does save a report to the USB boot drive. Since I previously had XMP1 mode enabled, I have disabled it for this tool. it is most likely that it will also find errors, but the doc points out that given my Intel CPU, it will be too difficult to determine the specific problem DIMM from the report. Thus, I'll have to run it with one DIMM at a time. Is this correct, folks?
– Nate Brazil
Jan 20 at 18:52