Error code 766f6c756d652e63 3f1 when running CHKDSK

[gr8sho]

Greetings.

My system has 4 drives, 1 SSD and 3 HDDs. Windows 7 is installed on the SDD and one of the HDDs. I also have Windows XP installed on one of the HDDs.

I cannot get Chkdsk to run on either of the Windows 7 installs with the error code shown. Chkdsk will run fine on the XP install against all 4 disks no problem.

I've scoured the web looking for a solution and nothing has worked. This includes booting into Safe Mode, uninstalling AV software, and even using a command prompt repair option from the Windows 7 install DVD.

Any suggestions on helping me resolve this dilemma are greatly appreciated.

Thanks and Cheers

 

[zigzag3143]

Greetings.

My system has 4 drives, 1 SSD and 3 HDDs. Windows 7 is installed on the SDD and one of the HDDs. I also have Windows XP installed on one of the HDDs.

I cannot get Chkdsk to run on either of the Windows 7 installs with the error code shown. Chkdsk will run fine on the XP install against all 4 disks no problem.

I've scoured the web looking for a solution and nothing has worked. This includes booting into Safe Mode, uninstalling AV software, and even using a command prompt repair option from the Windows 7 install DVD.

Any suggestions on helping me resolve this dilemma are greatly appreciated.

Thanks and Cheers

Error code 766f6c756d652e63 3f1 when running CHKDSK - Microsoft Answers

 

[gr8sho]

Error code 766f6c756d652e63 3f1 when running CHKDSK - Microsoft Answers

Thanks.

I had seen that post but discounted it mostly because I'm not experiencing BSOD. There's an implied undertone of a hardware issue.

Chkdsk starts and pretty much dies instantly.

When I retried it in Safe mode last night and tried to do a /F on one of the other drives, it said something about needing to unmount because of handles in use. I decided not to proceed because I shouldn't have to do that, and considering that the machine was in Safe mode, there shouldn't be anything holding files or handles on those drives.

I'm stumped really. The numeric error message MS gives is useless because I can't look it it up anywhere and doesn't give any clue as to what's wrong. Again, when I run CHKDSK on these disks from XP, no issues whatsoever.

 

[zigzag3143]

Error code 766f6c756d652e63 3f1 when running CHKDSK - Microsoft Answers

Thanks.

I had seen that post but discounted it mostly because I'm not experiencing BSOD. There's an implied undertone of a hardware issue.

Chkdsk starts and pretty much dies instantly.

When I retried it in Safe mode last night and tried to do a /F on one of the other drives, it said something about needing to unmount because of handles in use. I decided not to proceed because I shouldn't have to do that, and considering that the machine was in Safe mode, there shouldn't be anything holding files or handles on those drives.

I'm stumped really. The numeric error message MS gives is useless because I can't look it it up anywhere and doesn't give any clue as to what's wrong. Again, when I run CHKDSK on these disks from XP, no issues whatsoever.

As long as win 7 is running the volume is mounted. When it asks about that it is asking if you want it to do the chkdsk/f/r on the next reboot.

 

[gr8sho]

As long as win 7 is running the volume is mounted. When it asks about that it is asking if you want it to do the chkdsk/f/r on the next reboot.

That's fine for the boot drive, but I'm talking about one of the other 3 drives that shouldn't be doing anything whatsoever. I shouldn't have to unmount anything to run Chkdsk on those secondary drives. It's really bizarre.

As I said, I'm about at wits-end with this issue and am ready to do something drastic like wipe the disk completely. I'm just frustrated I don't know why this is happening and am at risk of it happening again.

 

[zigzag3143]

As long as win 7 is running the volume is mounted. When it asks about that it is asking if you want it to do the chkdsk/f/r on the next reboot.

That's fine for the boot drive, but I'm talking about one of the other 3 drives that shouldn't be doing anything whatsoever. I shouldn't have to unmount anything to run Chkdsk on those secondary drives. It's really bizarre.

As I said, I'm about at wits-end with this issue and am ready to do something drastic like wipe the disk completely. I'm just frustrated I don't know why this is happening and am at risk of it happening again.

Things like disk defraggers, malware apps, and others mount the volume (as does windows itself) so that message is not at all unusual

 

[gr8sho]

Things like disk defraggers, malware apps, and others mount the volume (as does windows itself) so that message is not at all unusual

Even in SAFE MODE or running off of the Install disk recovery options? There's something seriously wrong here.

I wish I could fix this without taking a sledgehammer approach.

 

[gr8sho]

Maybe Windows 7 has a bug. What's the best way to get them to address this.

 

[Golden]

Hi,

I agree with zigzag - run the chkdsk /r and if prompted to unmount, you should do so.

Regards,
Golden

 

[gr8sho]

Hi,

I agree with zigzag - run the chkdsk /r and if prompted to unmount, you should do so.

Regards,
Golden

This will only run in safe mode. But I will try one more time to see if that shows anything. I'd prefer to not purposely cause any corruption of the data if possible.

I'm really leaning to a bug in windows 7 since XP has no trouble at all handling this mixed HDD / SSD configuration. Do you guys have a back door way to get Redmond's attention?

I happened last night to do a restore from a backup image I took on the 21st but I can't swear the issue wasn't present then. This did not clear up my problem. So what I plan to do is rebuild this disk from scratch and create a backup image immediately. If that's successful, at least I have a faster way to get back to a known working state.

 

[zigzag3143]

Hi,

I agree with zigzag - run the chkdsk /r and if prompted to unmount, you should do so.

Regards,
Golden

This will only run in safe mode. But I will try one more time to see if that shows anything. I'd prefer to not purposely cause any corruption of the data if possible.

I'm really leaning to a bug in windows 7 since XP has no trouble at all handling this mixed HDD / SSD configuration. Do you guys have a back door way to get Redmond's attention?

I happened last night to do a restore from a backup image I took on the 21st but I can't swear the issue wasn't present then. This did not clear up my problem. So what I plan to do is rebuild this disk from scratch and create a backup image immediately. If that's successful, at least I have a faster way to get back to a known working state.

It is not a known bug and I can find no other references to it, so I doubt it is a bug.

 

[gr8sho]

It is not a known bug and I can find no other references to it, so I doubt it is a bug.

What's implied in that statement is that there are no new bugs are to be found in the product... :sarc:

The fact of the matter is that XP has no issues with this configuration and two separate copies of Windows 7 can't run CHKDSK on these drives.

 

[gr8sho]

I just did a complete OS reload and the problem with CHKDSK still occurs. Appreciate any additional suggestions.

 

[zigzag3143]

I just did a complete OS reload and the problem with CHKDSK still occurs. Appreciate any additional suggestions.

You may be experiencing what is called a "dirty bit" chkdsk. Please read her to decide and possibly fix.

How do I clear the dirty bit?

 

[gr8sho]

I just did a complete OS reload and the problem with CHKDSK still occurs. Appreciate any additional suggestions.

You may be experiencing what is called a "dirty bit" chkdsk. Please read her to decide and possibly fix.

How do I clear the dirty bit?

Thanks, but BTDT. The fsutil command says disk is NOT dirty.

Remember that XP sees no problem with these drives.

There is a system reserved partition on this boot drive, and whether or not it has an assigned drive letter makes no difference either.