ClickRight
06-26-2008, 03:34 AM
Today I was met with an interesting problem. Here are the symptoms:
Upon opening the "My Videos" folder, the computer would do one of three things:
Reboot.
Display the message "the file is corrupt" and hang.
Display the message "File is corrupt" and explorer.exe would close.
Otherwise the machine was perfectly fine, it was only this single folder folder giving issues. After ensuring the machine was free of viruses and spyware, and testing the hard drive, I ran chkdsk which found some minor issues, but didn't solve the problem. From there, I fired up UBCD4Win and started moving files out of the folder into a different one in groups, in attempt to find the file causing the crash. Unfortunately, after several attempts of shifting files back and forth I got nowhere.
I decided it was time to fire up a debugger to debug the memory dumps from when the machine reset. Attempting to install the debugger off my USB lead to an error dialog about one of the files it attempted to install being corrupt, so I decided to download it only to receive the same error. With all the corruption issues, I decided to run memtest on the RAM, and sure enough, hundreds of red lines went running down the screen. That's right, this whole thing was caused by a RAM issue.
Usually a stick this bad (errors came up immediately in memtest) causes a heck of a lot more problems and is easier to troubleshoot. I decided to debug the dump file, and sure enough that indicated memory corruption as well; should have looked there first :)
Hope anyone else that runs into this benefits from this information.
Upon opening the "My Videos" folder, the computer would do one of three things:
Reboot.
Display the message "the file is corrupt" and hang.
Display the message "File is corrupt" and explorer.exe would close.
Otherwise the machine was perfectly fine, it was only this single folder folder giving issues. After ensuring the machine was free of viruses and spyware, and testing the hard drive, I ran chkdsk which found some minor issues, but didn't solve the problem. From there, I fired up UBCD4Win and started moving files out of the folder into a different one in groups, in attempt to find the file causing the crash. Unfortunately, after several attempts of shifting files back and forth I got nowhere.
I decided it was time to fire up a debugger to debug the memory dumps from when the machine reset. Attempting to install the debugger off my USB lead to an error dialog about one of the files it attempted to install being corrupt, so I decided to download it only to receive the same error. With all the corruption issues, I decided to run memtest on the RAM, and sure enough, hundreds of red lines went running down the screen. That's right, this whole thing was caused by a RAM issue.
Usually a stick this bad (errors came up immediately in memtest) causes a heck of a lot more problems and is easier to troubleshoot. I decided to debug the dump file, and sure enough that indicated memory corruption as well; should have looked there first :)
Hope anyone else that runs into this benefits from this information.