Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
Sometimes, when I open a folder containing a number of different AVI-files in my windows explorer, the explorer crashes, telling me "Application error: File corrupt".
I first thought of really corrupt files, but even when there are only two or three AVIs in the folder, which otherwise seem totally okay and are playable, it keeps crashing.
I did numerous thorough anti-virus checks which led to nothing, and dleted the thumbs.db files, in case those were faulty, but the problem did not go away. Instead, it is occurring more and more often.
Anybody know what the problem might be?
Thnaks a bunch!

What size are the files?
What size is the drive?
What format is in use on the partition, FAT32 or NTFS?
Is this an External drive?

There is no 125GB hard drive size.
Watch the POST screens at start up to verify the drive is properly identified by both model AND full capacity.
You may have an issue with 48 bit LBA compliance. Look at the link below for more information on that.

Sorry, 250 GB, I meant. (Wow, I didn't even know I have this much space!) But thanks for the link, I'll check it out. The HD size just might be the problem ...

If your BIOS can't recognise the 250GB and you use it in WinXP anyway the result will eventually be data corruption.

That makes sense, but what does "data corruption" mean exactly? Until now, I have found no file that could not be played on my DVD player or on the WMP, but still it tells me "file" corrupt and the explorer shuts down.
Also, I have been using this HD for half a year until the problem started. Would that fit in the picture?

I have now run the "EnableBigLBA" Program, and it has told me that large LBA is already enabled with my Service Pack 3. However, when I run "HDInfo", it says "48Bit-LBA: no". What now??

WinXP with any service packs can access your entire hard drive. Unfortunately, if the BIOS can't do the same then IF Windows writes files to BIOS inaccessable portions of the drive the result is unreadable (corrupted) data.
WinXP may have not used the portions of the drive that are inaccessable by the BIOS until now. As the drive fills up Windows will eventually write to those sections of the drive.
None of this is important IF your BIOS sees the entire drive. You need to watch the screens at startup. If those screens don't show during startup then enter the BIOS (setup) screens and disable fast start and any logos that are enabled. Reboot and the screens should show.

![]() |
Reinstall xp but misplace...
|
device manager problems
|

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |