Corrupt Disk!!! Help!

[Chappy]

I had the same issue last month when building up my program base, and many others have had this as well.

I (and they) think this is just an issue with how well W7 is handling the disk controller(s) and it's having trouble seeing good space as corrupted.
The fact that Vista (and XP) don't report any disk corruptions kinda steers us towards this not being a disk problem itself, but how well W7 is able to read or access it sometimes.
This has been reported to MS by a great many people and I've heard rumor that MS is looking deep into it. It's possible that this problem for some of us, could be fixed in the next build release. I certainly haven't been installing programs lately like I did the first month, and that's why I haven't seen the problem arise since then, but it certainly did happen a few times for me and usually just being persistent got those programs to install.

Hopefully, this is all there is too it, and I think this is what's happening to many of us. Never know, it could be we all have the same controller chips on our HDD's and W7 is having an issue with that, but I hope that's all it is.

 

[Digger]

I had the same issue last month when building up my program base, and many others have had this as well.

I (and they) think this is just an issue with how well W7 is handling the disk controller(s) and it's having trouble seeing good space as corrupted.
The fact that Vista (and XP) don't report any disk corruptions kinda steers us towards this not being a disk problem itself, but how well W7 is able to read or access it sometimes.
This has been reported to MS by a great many people and I've heard rumor that MS is looking deep into it. It's possible that this problem for some of us, could be fixed in the next build release. I certainly haven't been installing programs lately like I did the first month, and that's why I haven't seen the problem arise since then, but it certainly did happen a few times for me and usually just being persistent got those programs to install.

Hopefully, this is all there is too it, and I think this is what's happening to many of us. Never know, it could be we all have the same controller chips on our HDD's and W7 is having an issue with that, but I hope that's all it is.

Well, not just some installs... but this is not a file on the system disk, this is a "storage" disk, that has been checked/scanned by win7 and reported no file system errors, bad sectors, ect. I have the system drive as a sata. The HD in question is on a IDE 0 or 1, i cant recall atm. I first thought it was the disk, then maybe winrar, even replaced cat5 cables, checked ram, replaced ram ect... This was also creating a problem with downloading a file (ms exchange) from MS actually, to both the system drive, and the "storage" drive... which both instances i got the corruption error download another error. Even if i boot into XP, unrar an app, and check installer to be good, then boot to 7, and corrrrrrupt... tis really frustrating

 

[darkassain]

Well, not just some installs... but this is not a file on the system disk, this is a "storage" disk, that has been checked/scanned by win7 and reported no file system errors, bad sectors, ect. I have the system drive as a sata. The HD in question is on a IDE 0 or 1, i cant recall atm. I first thought it was the disk, then maybe winrar, even replaced cat5 cables, checked ram, replaced ram ect... This was also creating a problem with downloading a file (ms exchange) from MS actually, to both the system drive, and the "storage" drive... which both instances i got the corruption error download another error. Even if i boot into XP, unrar an app, and check installer to be good, then boot to 7, and corrrrrrupt... tis really frustrating

i believe it might be that it might how 7 is writing to the indexes (not the windows search ones but the ntfs ones...)

 

[baarod]

I had this issue before and made it go away by defragging and compacting the mft with Paragon Partition Manager

 

[Digger]

i believe it might be that it might how 7 is writing to the indexes (not the windows search ones but the ntfs ones...)

These other files in question (rars) that were on the storage disk were not written while on win7... and yes ntfs format on both drives fyi

 

[Digger]

I had this issue before and made it go away by defragging and compacting the mft with Paragon Partition Manager

That is a thought, i will give this a go as I have had similar results. Pmagic seeing disks that needed to be chk'd when XP didnt see a problem. But I am leaning towards the driver IDE/sata/ controller

 

[Chappy]

Hi Digger

System or storage disk would make no difference as it's still W7 that's trying to access the disk in question. If Vista has no problem on the same disk with the same program, then that kinda shows it's a W7 issue. I know how much PITA it is too my friend...I know very well..
I found persistence paid off many times so far in W7. Like my TV tuner and Media center. For weeks I couldn't get MC to scan for my set-top box main channel properly, and then one night I just decided to keep trying. On the 7th try, it worked and has been working ever since. Also, it keeps saying "Viewing or Tuner Conflict" on start many times, but restarting MC always fixes that too.
I know it's frustrating, I can only imagine the issues it's causing you, but I really believe it's a W7 bug that will get fixed soon, an then you'll be Happy dancing...(LOL)

DA - that very well may be also. It does seem to be a very specific W7 issue, but just exactly where that issue is occuring is unknown to us ATM. I think MS has probably isolated it by now, and it should be addressed in the next build release (we hope)

 

[Digger]

Hi Digger

System or storage disk would make no difference as it's still W7 that's trying to access the disk in question. If Vista has no problem on the same disk with the same program, then that kinda shows it's a W7 issue. I know how much PITA it is too my friend...I know very well..
I found persistence paid off many times so far in W7. Like my TV tuner and Media center. For weeks I couldn't get MC to scan for my set-top box main channel properly, and then one night I just decided to keep trying. On the 7th try, it worked and has been working ever since. Also, it keeps saying "Viewing or Tuner Conflict" on start many times, but restarting MC always fixes that too.
I know it's frustrating, I can only imagine the issues it's causing you, but I really believe it's a W7 bug that will get fixed soon, an then you'll be Happy dancing...(LOL)

DA - that very well may be also. It does seem to be a very specific W7 issue, but just exactly where that issue is occuring is unknown to us ATM. I think MS has probably isolated it by now, and it should be addressed in the next build release (we hope)

Thanks for the reponses chappy, and the rest... But chappy this is a HUGE issue. I can understand issues with the likes of MC, or a camera driver or somthing like that, but this is the heart of the OS... if it reads data as being corrupt or whatever is going on, how can MS even release this publicly imo?? an old video card not found, sure i understand... but this really IS rediculous by any standards... I'm on x86, has this also been an issue with the x64 edition?

[edit] Nevermind, i see that you are on x64 chappy

 

[Chappy]

Hi Digger

Yes, it is a big problem for those experiencing it. But it's possible that MS had no idea about it (if it is the problem afterall) until it started showing up for some people. That's also why this Beta release program is such a good idea, they get to test this out on millions of different configurations and see what pops up. This is exactly what they're looking for in this release program and if it is a problem with W7 and disk I/O, I'm sure it's being addresses as we speak.
That is the nature of being a Beta after all...

Best of luck Digger!

 

[Digger]

Hi Digger

Yes, it is a big problem for those experiencing it. But it's possible that MS had no idea about it (if it is the problem afterall) until it started showing up for some people. That's also why this Beta release program is such a good idea, they get to test this out on millions of different configurations and see what pops up. This is exactly what they're looking for in this release program and if it is a problem with W7 and disk I/O, I'm sure it's being addresses as we speak.
That is the nature of being a Beta after all...

Best of luck Digger!

Well, it wasnt luck, but I managed to figure out (what i think) the problem is/was, atleast for me, and maybe a few others as well - mainly dual booters with this problem and other OS's used (particulary XP in my case).

Basically thru many trials and errors yesterday and about a half day of trying to reinstall 7 I have narrowed it down to something to do with the file system, as type/version of NTFS or in shorter terms, what 7 uses as Fdisk possibly... either or.

My first install i had formatted the partition -to be used for 7- with windows xp prior to install. I didnt use the windows7 installation setup of creating a partition nor the format (since i had done this already in xp). This time, well the final time I used 7 to DELETE the previous 7 partition, create new (which then automatically made it system/primary as an extended partition on Disk 0. That has stood as the answer to atleast my problem, as nothing else- including programs installed- has changed from my previous system setup and order of how i install things (old habit hard to break). A bad memory stick has not been the case for me, as this HAS been the answer in previous similar situation before with XP.

Of course i found alot of saved programs.exe that i had moved to a different drive from the previous 7 install and they ended up having corrupt installers (duh). while everything else on same drive had no problems, just the ones from the corrupt installation of 7. Some other "issues" that i had on that prior installation has gone away as well. Like some programs that i knew were not corrupt, now install and unarchive just fine... and a few other small nag errors i use to see.

Also, like my installation on my laptop (which i DID use 7 to format the system partition), my desktop install of 7 made the partiton with seven's install, C:. When before install, that same partition under 7 was marked D:. It also made my C:\xp windows primary partition DISAPPEAR. Since it did the same on laptop install as well i knew what had happened. I just cant explain for the life of me why the installation does that to the HD partiton setup. Nor why formatting with a partiton while under XP makes it a corrupt install. I did this many times before i finally let seven format the partiton. I got the C:\xp partiton back of course and renamed.

If i'm not mistaken, this same exact problem was an issue with winXP and win98 dual boot... i remember having to at first load the i386 folder on the marked partition with fdisk. Its been awhile but i do remember a similar problem referencing to those times. I am banking on the lines it goes back to the reason why i had corruption problems previously. I let XP control and say who what when where instead of letting 7 determine and distribute how the file system is written... my opionion of sorts......... But i am still monitoring the goings on as this install is only 24 hours old now. So far so good tho.

 

[Chappy]

Good job Digger!

I think that reinforces my claim that W7 is having trouble with disk I/O and seeing data as corrupt when it isn't.
This potentially is a very big problem and I've brought it up to some MS guys attention over at Connect. I haven't heard anything back yet but if I do I'll post about it.

I remember I also had problems back when XP was new, about how different tool used to create NTFS partitions, were not always recognized properly by the OS. Allot of 3rd party partitioning tools would create an NTFS part and the OS would want to reformat it again. I'm kinda getting the feeling that W7 is not seeing NTFS properly under certain circumstances..(?)

Be interesting to find out what is the root cause of these types of corruptions we're seeing.

Good luck Digger!

 

[baarod]

This time, well the final time I used 7 to DELETE the previous 7 partition, create new (which then automatically made it system/primary as an extended partition on Disk 0. That has stood as the answer to atleast my problem, as nothing else- including programs installed- has changed from my previous system setup and order of how i install things (old habit hard to break).

I just cant explain for the life of me why the installation does that to the HD partiton setup. Nor why formatting with a partiton while under XP makes it a corrupt install.

I let XP control and say who what when where instead of letting 7 determine and distribute how the file system is written... my opionion of sorts......... But i am still monitoring the goings on as this install is only 24 hours old now. So far so good tho.

I was trying to get you to do that when this was first reported.

http://www.sevenforums.com/general-discussion/1468-corrupt-disk-help.html#post13596

http://www.sevenforums.com/general-discussion/1468-corrupt-disk-help-2.html#post13933

Seems that 7 creates a subtly different mft than previous Windows versions. I've gotten it to "convert" by compressing an old volumes mft with Paragon Partition Manager. This forces a chkdsk at the next boot and after that, no more issues. Previously I'd avoided the corruption issues by making sure to create all partitions with Windows 7 either with the installer, Disk Management, or the diskpart command line utility.

 

[Chappy]

Yay Barrod, it is doing something different alright.
That's another good idea about maybe it's in the MFT. I guess there are a number of different possibilities why 7 is seeing some data as corrupt, I can't wait to find out just what iscausing these problems.

 

[Digger]

I was trying to get you to do that when this was first reported.
.

Yea baarod, i really thought about it, and figured your suggestion would work and was my only other alternative. I just hit the "fed up" meter that day and decided to just wipe it out and see if i couldnt reproduce results to see what exactly it was that i did to create the problem in the first place. I believe i took your measures with pmagic when i had this same problem in xp beta days.

 

[Digger]

Well i am back in the same saddle again. Baarod i tried acronis, paragon, windows... all didnt find any problems with target or system HD. Currently I am very suspect of one of my RAM sticks now. I have removed #2 stick and have yet to reproduce the corrupt problem. Thing is... when i run the mem diag tool, it doesnt report ANY problems? So, i'm wondering whats the deal? Is this mem tool a possible sham? or does it work with only ECC registered sticks (this one isnt). Both sticks same, dual channel.

This is the only thing i changed in the whole picture of things and so far no corruption. This was my first initial thought, but since the mem tool nor my own bios mem test came up with any problems. Could a scenario be that the mem stick could be good, but maybe HEAT could be causing the problem with the stick? While typing this i am unpacking and having no errors (which before it would have happened by now).

until then looks like i'm down to running 1 stick @ 64bit..... horror

 

[kindred]

INTEL CORE DUO E6300
GIGABYTE GA-N650SLI-DS4
SAMSUNG 1TBX2 HARD DRIVES

Well I'm also using a Gigabyte mobo, but I can't see how that's the problem, as I've had no problems with Vista Ultimate x64, which Windows 7 x64 is based on.

Has anyone used the latest Windows 7 build 7057. If so, is the problem fixed?

 

[elementalwindx]

Hey guys I found this thread on google. Are there any results to this issue? I have been running windows 7 for about 4-5 days now, and I just started having this issue after I went into safe mode and set a password to the administrator account. Now I'm constantly getting corrupt data errors and need to run chkdsk blahblah. It's ran chkdsk at least 5 times now. I'm running build 7077.

This is on a Intel RAID 1 setup with 2 new 640gig WD Caviar blacks with 4 gigs of DDR2 memory on an intel quad core cpu with an intel mobo. All parts less than a year old.

I am running dual boot with XP Pro 64. When I boot into that OS I have NO hard drive issues what so ever. But it did try to run chkdsk in XP but JUST on the partition that windows 7 is on.

 

[baarod]

Read the thread and make your own decision, I don't think anyone really came to a consensus. I'e maintained from the beginning that the partitioning and/or NTFS formatting that XP does is subtlety incompatible with 7 under certain conditions. I routinely use diskpart to clean, partition, format and activate exclusively. Other folks that have had the issue that followed my instructions to use diskpart to recreate the filesystem control structure on their "faulty" drives have probably forgotten all about it by now. You know you're going to need to find a place to back off that RAID array right? The operating theory is that there is MFT corruption that chkdsk won't fix. I've had good luck with Paragon Partition Manager's shrink and defrag MFT feature clearing up the issue. Other folks have needed to shrink the partition using disk manager (builtin to windows) create a new partition with windows 7 format with windows 7 and then move the data. In your case I think I'd mirror the RAID set (or sync or whatever your utility calls it) to make the disks perfect copies of each other, break the RAID array into JBOD completely clean one disk from the platters up (diskpart, clean, partition, format) copy the data to the fresh drive and the zero the other, finally recreating the array against the raw drive.

 

[elementalwindx]

I used the newest acronis disk director to make my partition. I guess I'll play around with how you said and see what happens. Kinda sucks because I was actually enjoying this. I remember when I installed vista on my test system and within 2 hours I said **** it and took that crap off my system and vowed to never let it touch my equipment ever again and I've never stopped using XP till now. Windows 7 however has made a much better impression on me seeing as how it didn't have 5 million bugs within the first 2 hours of using it

 

[TheTeZ]

i had a disk ive been using for a long time.... no problems, i installed win7 and it corrupted not long go after the install, lost A LOT of stuff, it was my storage disk... really with any disk or partition went except the one that did..... But oh well...