Emulator

Recently I re-installed Windows 7 on one of my gaming machines, and had done some RAID testing with Intel RST (long story but it involved 4TB hard drives and Intel RST crashing).
After this was over with apparently my collection of Wii/GC games become corrupted, but had the correct file size listed still in the NTFS directory.
After re-installing everything and Dolphin, it would run, but as soon as I set a game directory (and clicked ok in the settings menu) Dolphin would crash.
If I then tried to load Dolphin again, it would hang. No error message would pop up. If I moved the game ISO away to a folder Dolphin couldn't see, then Dolphin would load again.
While Dolphin was crashing, I was observing 10-20% CPU usage on my 4.8GHz i5-2500k. Also the RAM usage would slowly go up continuously because of a RAM leak. I saw it go from about 100MB to at least 2 GB while watching.

This problem was observed from Dolphin 3.5 to 4.0-2599-x64 (latest version available today).

Dolphin needs some error handling in it's game checking routine so that it doesn't crash and can tell the user something is wrong
with the ISO. As of right now it looks like a single bad ISO will cause the whole app to crash if it is in a Dolphin game folder.

After replacing the bad isos with backup copies Dolphin started working again.

What steps will reproduce the problem?

1. Get a game ISO, any .iso file that you use with Dolphin.
2. Open it in a hex editor and have fun then save it.
3. Open Dolphin with that ISO in one of your game directors in Windows.
4. Repeat Steps 2-3 until Dolphin crashes when opening the file.

What are your PC specifications?
AsRock Z68-Extreme 4
i5-2500k @4.8GHz
16GB DDR 3 1333 7-7-7-21
(currently) AMD HD7870.
Windows 7 pro x86_x64
ALC892

Is there any other relevant information? (e.g. logs, screenshots,
configuration files)
Dolphin didn't create any logs of this issue or generate any error message.
The games were loaded from NTSC discs. One was a single disc MFT initialized, the other was an Intel RST RAID5 GPT disk with NTSF partition. Both crash the same way so it doesn't appear related to the file system.