Hard Disk Problem in Windows 7

Status
Not open for further replies.
T

TheBroker

Contributor
Hi, I'm having a recurring problem with my Hard Disk in Win 7, build 7100. This problem didn't surface in Vista Home premium that I used previously.

My operating system is installed in C Drive. Once when I tried to run certain files or save to C drive, it didn't save. When i've tried to run Disk Defragmenter, it didn't show up the C drive. I restart the computer - it goes into error check and then works fine. Hard disk shows in Disk defragmenter and works fine.

I'm very concerned about data loss. What is the problem? It's a Dell inspiron 1525 with a 250 Gb Hard Disk and the warranty ends on 30th September. I had a friend who has had a similar Hard Disk bug with another Dell Laptop. Is that a problem with the laptop or with some corrupt file?
 
Go to event viewer. For that go to command prompt and type eventvwr.
This should open event viewer. Under System logs check for any event with Disk errors or warnings.
Usually the "Source" column would say "Disk" or something equivalent. If you do find. Post the event logs here in the forum which will help us to guide you in the right direction.

Also under Application logs do check for any chkdsk events.
 
This is the message..

The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume Windows 7.
Click to expand...

Googling the above quote got me this

HELP! Corrupt disk - file system structure on disk is corrupt and unusable Chkdsk

Another link that Apparently worked ( but I didn't understand it fully )

http://www.computing.net/answers/windows-xp/hard-disk-is-corrupt-and-unusable/128620.html

Any suggestions. Should I download the RC once again and install it since this is a Beta? I don't want to go back to Vista :(
 
Ok this aint the complete error. Give us the Event ID. Double click the error in event logs and there is a copy option. Once you copy it paste it on the forum.

For Example -

Event Type:
Event Source:
Event Category:
Event ID:
Date:
Time:
User:
Computer:
Description:
Again from what it appears is a Disk issue which is corrupting the file system. So give the complete event log and do search for an event in application log which would have a Event type as "Information" which would have contents of what chkdsk really found and did.
 
  • Like
Reactions: 1 person
I did check the event ID that you sent. You can refer this article from Microsoft - Event ID 55 may be logged in the System log when you create many files on an NTFS partition on a Windows Server 2003-based or Windows XP-based computer

Though the article is on XP and 2003, the issue that you have is most likely OS related. And since you are using Beta its no use banging your head for the issue as the final release of Windows 7 would have lot of patches installed in it.

Just in case you want to be at a safer side loop in Dell since you mentioned that your warranty would be over in September.

Another thing you can try is disabling all the third party services and startup items from MSCONFIG and then monitor the Laptop. Because its most likely that any third party app. which would be incompatible with Windows 7 could cause File system corruption.
 
tush said:
Just in case you want to be at a safer side loop in Dell since you mentioned that your warranty would be over in September.

Another thing you can try is disabling all the third party services and startup items from MSCONFIG and then monitor the Laptop. Because its most likely that any third party app. which would be incompatible with Windows 7 could cause File system corruption.
Click to expand...

hardly any non-ms services are being used. It's only Avira, my Sound drivers and google desktop. Am a bit wary of doing that esp the Antivirus, but let's see..

Btw, I forgot to mention, I hibernate this system a lot. Could there be some corruption created in the Hibernate File?

Tush, I really appreciate your help :hap2::)
 
TheBroker said:
Tush, I really appreciate your help :hap2::)
Click to expand...

No problem dude. Any time :)

For hibernation disable it for a few days and use regular shutdown procedure. This way you can rule it to be the cause by seeing if that event is generated again.
 
Status
Not open for further replies.
Top Bottom