 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
Windows Forum / Windows Vista / Hardware / March 2008My disk is getting corrupt all the time
Something has been bothering me a lot in Vista 64 Ultimate SP1. Every now and then, when Windows starts, it says my disk structure is corrupt and I should run chkdsk in order to fix it. When I try to run CHKDSK under Vista, I get a "insufficient disk space to fix master table (MFT)", and CHKDSK aborts. I can't create folders, files, Windows Update fails ... The good thing is a have a dual boot system and when I choose XP, Windows XP detects that the Vista partition needs chkdsk and this time, chkdsk runs completely and fixes the Vista partition. So I can restart the computer, choose Vista partition again and this time everything will work fine. Problem is, this is happening too often. Like every day. And it is such a hassle to start Vista, get the error message, restart, choose XP, fix Vista, restart, choose Vista and then have everything normal. Any of you guys have an idea on WHY my disk structure is getting corrupt all the time? My Vista installation is very recent, and I did a full format in the partition before installing it. Thanks for the help.  Signaturejpedrosa Vista might be the first of the two operating systems to show the symtoms of faults in the drive. Have you run the hard drive manufacturer's test software on the drive? > Something has been bothering me a lot in Vista 64 Ultimate SP1. > [quoted text clipped - 19 lines] > > Thanks for the help. Colin Barnhorst;624075 Wrote: > Vista might be the first of the two operating systems to show the > symtoms of > faults in the drive. Have you run the hard drive manufacturer's test > software on the drive? I don't know, I'm thinking it may be a Vista problem ... I was having BSOD problems before changing RAM, and I had SEVERAL vista installations running fine with 2GB RAM and NO problem with disk structure ... now I finally changed my memory modules and now Vista runa flawlwessly with 4GB RAM, but I keep getting these annoying disk structure problem ... Signaturejpedrosa > Colin Barnhorst;624075 Wrote: > > Vista might be the first of the two operating systems to show the [quoted text clipped - 7 lines] > finally changed my memory modules and now Vista runa flawlwessly with > 4GB RAM, but I keep getting these annoying disk structure problem ... I too have what I think are similar problems. First I have an external usb drive that has worked beautifully on my xp machine. Plugged it into my new vista 64 machine and most of the 500gb of data is corrupted. have run chkdsk and it says it is fixed but can't use the drive as I keep getting corruption errors. I tried to partition the drive so I had the space to use but it won't allow it because of the corruption which it doesn't fix. Any solutions? I can copy one file at a time that doesn't give the corruption error to another small drive and burn to cd. But I can't copy a folder to another drive if there are corrupted files within. I have not yet attempted reformatting the drive as I am hoping a fix to retrieve files that weren't backed up. Second problem is my boot drives are WD Raptor scsi raid 0 drives. Last week the pc wouldn't boot. Tried my recovery cd and vista installer wouldn't install to the raptors (non system drives). Then I went to bios to check the raid and it was perfect. Went to boot sequence and selected HDD and it booted to vista fine. But.. and a big but.. I have to do that each time I boot. Get a lot of lock ups so have to use reset so I am having to go to bios several times a day to get back to vista. considering changing to vista 32 as I have about had it with 64 problems. Any advice or input to help me keep some hair would be wonderful. Oh did notice a repair utility, so is the boot problem the mbr that needs to be fixed? Or is there another utility that is the better choice. And is there a utility that will fix my external drive corruption problem. I remember back in the Dos days Norton Disk Doctor was outstanding but I haven't been able to find such a utility since 32 bit OSs came. Falde I second this motion... I've attempted installing Vista x64 a couple times and just had an obsolutely terrible time with drive corruption. The C drive always ends up having problems... I have an Intel D976XBX2 motherboard with a E6700 dual core processor (2.66 ghz). I also have 4 gigs of Corsair RAM... Signaturerichv Suggest you downgrade to 2GB of RAM and if that works don't upgrade back to your matched Corsair RAM till you are sure everything is working fine. > I second this motion... I've attempted installing Vista x64 a couple > times and just had an obsolutely terrible time with drive corruption. > The C drive always ends up having problems... > > I have an Intel D976XBX2 motherboard with a E6700 dual core processor > (2.66 ghz). I also have 4 gigs of Corsair RAM... Man... I ran memtest (memtest.org) for a couple hours last night as well as running Orthos stress tests yesterday. No problems at all under Vista 32... I hate to remove memory from the machine if it isn't going to resolve this long term... The purpose of the experiment is to get more memory useable!! Signaturerichv I fully understand your objective. Since my Vista installations have had trouble with 4GB of memory I was suggesting temporarily downgrading to 2GB to see if you can get the OS installed and if you can then upgrade the memory. > Man... I ran memtest (memtest.org) for a couple hours last night as > well as running Orthos stress tests yesterday. No problems at all under > Vista 32... I hate to remove memory from the machine if it isn't going > to resolve this long term... > > The purpose of the experiment is to get more memory useable!! Thanks for the info JW... The odd thing is that the actual installation seems to work fine. The problems seem to crop up after the installation. It is usually a couple reboots and driver installs that seem to cause the problem. Initially, it was SP1 for Vista, but when it would fail, so I got a copy with SP1 integrated. Then, it was the drivers later that caused the problem. Anyway, maybe I will give it another try with the 2 gigs of memory. And, thanks for the input! Signaturerichv Also make sure you have the latest BIOS from Intel for your MOBO if you have not done so already. > Thanks for the info JW... > [quoted text clipped - 7 lines] > > And, thanks for the input! > Also make sure you have the latest BIOS from Intel for your MOBO if you > have not done so already. [quoted text clipped - 10 lines] >> >> And, thanks for the input! Make sure you have ECC memory. The disk only writes what is in memory. The funny thing is that the files are not actually corrupt... It seems more like the read is the issue. Everything works fine and then bang... Things start going south... Have latest BIOS... Signaturerichv Our goal is to solve technical and operational problems by using this newsgroup as a collective forum. Please include enough of the previous message(s) so that others trying to follow this thread know what you are talking about. Also please try to "edit out" the non relevant portions. It helps everyone. If you are using Windows Mail, Go to: Tools > Options > Send > check - "Include message in reply" SignatureRegards, BobF. > > The funny thing is that the files are not actually corrupt... It seems > more like the read is the issue. Everything works fine and then bang... > Things start going south... > > Have latest BIOS... Did you ever try with 2GB of memory? Have you tried reseating or tried using a different drive cable and/or interface connection? > The funny thing is that the files are not actually corrupt... It seems > more like the read is the issue. Everything works fine and then bang... > Things start going south... > > Have latest BIOS... |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.