xboxscene.org forums

Author Topic: 0102 Oh Damn! Now Im F*cked  (Read 151 times)

pliskin024

  • Archived User
  • Newbie
  • *
  • Posts: 3
0102 Oh Damn! Now Im F*cked
« on: June 02, 2006, 07:32:00 AM »

for all you people with the 0102 error, i was getting the same error, and i opened up my 360 and i found out that the cause was humidity or moister on the back of the motherboard i just cleaned it up and let it dry for a while and now works smoothly, it is not the cables, it is not the HDD, it's not even the DVD, it is not overheating, for me it was humidity, if there is much of it in the room you have it take it out or something...i really dont know how to avoid it, because i live in Dominican Republic and it's a tropical weather so there is a lot of humidity here...so what im gon' do is get an intercooler or a liquid cooler...but for me the 0102 was a humidity on the back of the m/b
Logged

twistedsymphony

  • Recovered User
  • Hero Member
  • *
  • Posts: 6955
0102 Oh Damn! Now Im F*cked
« Reply #1 on: June 02, 2006, 07:49:00 AM »

well AFAIK 0102 is litterally "unknown error" meaning not even the Xbox knows what the problem is... based on various descriptions of how people solved the problem It sounds like it's most commonly caused by a short or a break somewhere...
Logged

pliskin024

  • Archived User
  • Newbie
  • *
  • Posts: 3
0102 Oh Damn! Now Im F*cked
« Reply #2 on: June 02, 2006, 09:38:00 AM »

i said for ME it was humidity...it damaged 2 capasitors and i had to exchange them after i cleaned up the back of the m/b...i am NOT telling people to do this im just giving people a possible reason...for me this WAS the reason...MS won't tell you that humidity damages capasitors because by doing so they are suggesting you to open up your thing and fix it...they know the problem they just will not tell you open it up and fix it because more than half of damaged 360s will be fucked up for good
Logged

Shepdog

  • Archived User
  • Newbie
  • *
  • Posts: 49
0102 Oh Damn! Now Im F*cked
« Reply #3 on: June 02, 2006, 01:17:00 PM »

how do you tell if a capacitor is bad?
Logged

JEB-101

  • Archived User
  • Sr. Member
  • *
  • Posts: 254
0102 Oh Damn! Now Im F*cked
« Reply #4 on: June 04, 2006, 08:37:00 AM »

QUOTE(Shepdog @ Jun 2 2006, 03:48 PM) *
how do you tell if a capacitor is bad?


the easyest way to tell if the top of it is swollen and\or blown... if so means it's bad.. the odds that a cap is bad is verry slim tho...


(IMG:style_emoticons/default/beerchug.gif)
JEB
Logged

illidur

  • Archived User
  • Newbie
  • *
  • Posts: 7
0102 Oh Damn! Now Im F*cked
« Reply #5 on: June 04, 2006, 08:31:00 PM »

i think my 0102 might be a surge problem... but even after the surge it worked for a while. definitly not humidity for me. like 10 more screws and im inside my box.. but can't get em with my tools.
Logged

sidewinder33

  • Archived User
  • Hero Member
  • *
  • Posts: 518
0102 Oh Damn! Now Im F*cked
« Reply #6 on: June 05, 2006, 01:51:00 AM »

I have the 0102 also but its weird, my 360 just started freezing randomly, so I added the nyko intercooler thinking it was overheating (playing with the case open seemed to keep it running without freezing) eventually as I’m sure most has happened the 360 would just boot and freeze almost immediately. Now about 1 in 20 times my 360 will boot and run. Mine isn’t a humidity issue as I live in Arizona, one of the driest places in the US.  

Kudos on taking the initiative and fixing your 360. I have to agree that the 0102 seems to be a short, possibly why mine boots occasionally, shit must line up just right.

On a side note when were your 360s made, or when did you get them? I got mine in the second shipment, about 3 weeks after launch. The official MFR date is 11-21-05 for mine. Who knows if this line seems to be faulty maybe a class action could be started.
Logged

snow rider221

  • Archived User
  • Sr. Member
  • *
  • Posts: 384
0102 Oh Damn! Now Im F*cked
« Reply #7 on: June 05, 2006, 05:39:00 PM »

sidewinder, i have all of the same problems as you, and live in the same place as you... heh


only differance is, mine wont turn on at all... always the three red lights
Logged

sidewinder33

  • Archived User
  • Hero Member
  • *
  • Posts: 518
0102 Oh Damn! Now Im F*cked
« Reply #8 on: June 05, 2006, 09:14:00 PM »

Hmmm When was yours made? have you opened yours yet? if not send it to M$ to have them fix it. The only thing I can think of is a faulty production set. There is no other reason for it to just up and crap out, for no reason. Did yours make some kinda random digital video errors, like when you booted did the boot screen flash like a line of graphic when its supposed to be all black? And did it flash green like when you entered the guide menu? because mine did that, before it died. Maybe keep trying to start it up, mine doesn't go all the time.
On a side note where do you live (IMG:style_emoticons/default/smile.gif) I'm rocking tempe.
Logged

Jimz360

  • Archived User
  • Newbie
  • *
  • Posts: 15
0102 Oh Damn! Now Im F*cked
« Reply #9 on: June 06, 2006, 10:36:00 AM »

I'd advise you to buy a de-humidifier, not only would it keep your console dry but it should help any other electrical appliances you have. And help you if you sweat alot while playing games. (IMG:style_emoticons/default/tongue.gif)
Logged

kingpickle

  • Archived User
  • Full Member
  • *
  • Posts: 118
0102 Oh Damn! Now Im F*cked
« Reply #10 on: December 29, 2006, 04:27:00 PM »

I was gettin this error. What fixed it for me was removing the HS, cleaning off the gpu/cpu and applying arctic silver. Before this I would get 0102 9 times out of 10 and ingame crashes. Everything is smooth atm with 3 days of hard testing.
Logged