Halo: Reach Forum
This topic has moved here: Subject: Disc Not Reading
  • Subject: Disc Not Reading
Subject: Disc Not Reading
  • gamertag: Tsuarn
  • user homepage:

got so bored i actually wrote this signature...

ye just called ms support (netherlands) they told me to send my xbox over so it can be repaired. oh ye got a Elite bought it in 2008.

can play solo campaign up to mission 5.
Cant play co-op (disk error).
Cant do multiplayer (disk error).
Firefight is a no go.
And forge works perfectly XD.

Edit: Its not just Reach that doesnt work for me.
Mass Effect 2, Red dead redemption, Bioshock 2 also dont work anyway i hope i can play it again in 2 weeks :p

[Edited on 09.15.2010 6:43 AM PDT]

  • 09.15.2010 6:41 AM PDT

I feel sorry for yas, that's stupid that the first xbox360 console can't play the game. Just retarded.

  • 09.15.2010 6:45 AM PDT

Legion Leader of the Damned.

I don't have a launch console, yet I am still having problems.

  • 09.15.2010 6:59 AM PDT

bump

  • 09.15.2010 6:59 AM PDT

My rough guess is that it is the DVD drive that's the problem... I have the Phillips/BenQ VAD6038 which i think i got when i sent it to be repaired a couple of years ago...

my console is a launch one.. MFD: 24/12/2005..

Don't know how many other people here have the same drive as me..

[Edited on 09.15.2010 7:06 AM PDT]

  • 09.15.2010 7:06 AM PDT

Anyone called ms support and their console not been in warranty?

  • 09.15.2010 7:12 AM PDT

Im calling them within the hour and my xbox is long out of warranty. It's a 2005 model that still hasn't gotten the ROD. My reach symptoms are the same as a few others on here. One thing that I've been getting that i haven't heard anyone report on here is when i complete the 3rd level my screen either A. Goes black and restarts the level, B. Goes black and puts me at the last checkpoint (and when it puts me back in game their is no sound except for music and fragmentation grenades), or C. Goes black and fades to the main menu. Anyone else having this problem?

  • 09.15.2010 7:22 AM PDT

Once on the second level after a cutscene it put me back to the last checkpoint but i just played through it again and got past it. It won't let me play the third mission though

  • 09.15.2010 7:25 AM PDT

bump

  • 09.15.2010 7:35 AM PDT

Hopefully get an answer from bungie in a few hours

  • 09.15.2010 7:49 AM PDT

Just got off the phone with Microsoft, they told me that i have 90 says to return reach to where i purchased it, and that they don't believe its a problem with the xbox. So no help there.

  • 09.15.2010 7:49 AM PDT


Posted by: x Takkun x
Just got off the phone with Microsoft, they told me that i have 90 says to return reach to where i purchased it, and that they don't believe its a problem with the xbox. So no help there.


Ugh typical, now i bet bungie says that it's the console's fault so they're not doing anything

  • 09.15.2010 7:50 AM PDT

Nice try, Takkun. It was worth a shot.

  • 09.15.2010 7:51 AM PDT

I'm hoping its just some obscure problem with a mass number of discs that they didn't seem to notice in testing and can be fixed with a simple update.

  • 09.15.2010 7:52 AM PDT

Ummm.... yeah...

I have a replaced original from RRoD and managed to get to the first driving point when everything froze. Afterward, nothing but disc read errors. Gonna try the HD install to see if it works, but REALLY would love some sort of acknowledgment from somebody about why this is an issue.

Funny thing is my original RRoD the day before Halo 2 came out. Figures this would happen.

[Edited on 09.15.2010 7:55 AM PDT]

  • 09.15.2010 7:53 AM PDT

Something new here, I just got off the phone with a friend who purchased a legendary edition of Reach as well as a new Reach console. He is getting disc read errors on both discs but the one that came with the console seems to run multiplayer, firefight, and forge perfectly but with errors just starting the campaign. The possibility that it is just the disc is increasing.

  • 09.15.2010 7:56 AM PDT

Hey look what i just found on google

http://www.product-reviews.net/2010/09/15/halo-reach-problems -with-disc-and-co-op-on-xbox-360-slim/

  • 09.15.2010 7:56 AM PDT

I got disks from 2 separate shops and both failed. last night i only found 1 person moaning about this problem, now today the are over 28 pages of complaints and microsoft says there is no problem with the consoles. will they accept that they have a problem.

  • 09.15.2010 7:57 AM PDT
  • gamertag: [none]
  • user homepage:

You may also know me as: StalkerGrunt117, at halopedia,
and Alex117100, at youtube,


Posted by: x Takkun x
I'm hoping its just some obscure problem with a mass number of discs that they didn't seem to notice in testing and can be fixed with a simple update.


Yeah, some people complain about all thse kinds of glitches and framerate issues, and a lo of other stuff ans say Bungie didnt test the game enough, while others say theu had no problems with it, including myself. I dont get it, why are some people experiencing these things and others are not? I really think there something wrong with certain disks.

  • 09.15.2010 7:58 AM PDT


Posted by: HydroConzie
Hey look what i just found on google

http://www.product-reviews.net/2010/09/15/halo-reach-problems -with-disc-and-co-op-on-xbox-360-slim/


The only thing wrong with that is that it says there is problems with the discs but i have tried 3 seperate discs and none work and i even tried 2 of them on a friend's xbox elite and they worked fine

  • 09.15.2010 7:59 AM PDT

Woke up just to bump this thread.

/Dedication.

...back to bed.

  • 09.15.2010 8:04 AM PDT

bump

  • 09.15.2010 8:05 AM PDT

Anyone read the link i posted?

  • 09.15.2010 8:07 AM PDT

just read you link, it looks like microsoft know there is a problem but will they fix it time will tell

  • 09.15.2010 8:11 AM PDT

Yeah i read it along with the followup link on that page about the disc problems. In the comments one user said something about Microsoft possibly putting a new security lock out on the disc that the xbox can't bypass but i don't think they were being too serious.

  • 09.15.2010 8:11 AM PDT