Literally hundreds of people have been posting in two forum threads at both the Bungie and Xbox sites saying that they are having serious problems with disc reading errors and Halo 3. The issue appears to happen for various people at different places in the game, and is not related to whether the disc is scratched or not. User Muffy had the following to say on the
Bungie forums:
I'm on my 3rd copy of Halo 3 - after the 2nd Limited copy was found to be scratched I upgraded to Legendary hoping the REAL DVD CASE you get when you by the "PLASTIC EDITION" (PE) would yield a clean disk - and it did - the surface is perfect.But... I'm still getting read error intermittently at various points in Solo or Campaign - usually when I reboot I can get by the read error and continue on. This is happening on a spanking new 360 Elite - 4 days old.So the read error are not necessarily always related to a scratch... Might be just really poor reproduction. I wonder if a DVD utility would tell us what rate they burned it at... Maybe they cooked them too quickly.BattleAxe77 had the following to say on the
Xbox.com forums:
My original copy of the Halo LE was scratched and after playing for awhile I got the Disc error message. I called the store and they said it was a common problem with the LE. I got an exchange and the new copy was perfect. I played for about 45 minutes and the same disc error showed up. I can only play a select few of the MP maps without this same error. I hope there is a fix to this problem. I'm probably going to downgrade to a regular copy but I hear the same problem is happening with that version as well.One user also reportedly got in touch with Xbox support, who told him that there is actually a bad batch of discs out there:
Just got off the phone with Microsoft, again, and they admitted that there was a bad batch of Halo 3 games that were released that will not work on certain 360's.And finally, someone submitted a YouTube to TeamXbox just to prove that they are having the problems without their disc being scratched.
It will be very interesting to see how this plays out. Have any of our readers experienced the same issue?
