Forum:Ylod during fallout:new vegas?

Ive been reading a lot of comments about the ylod lately since my 160gb model ps3 just tanked and have seen quite a few people mention they were playing new vegas when it happened. Since I was also, I was wondering if anyone here got yloded during new vegas and tried to fix it themselves, how, and if successful how long did it last with more fallout play.

In the time ive had my ps3 it only crashed once before new vegas and pretty frequently afterwards. It yloded after playing an hour and a half so overheating doesnt seem plausible. Ive taken it apart and there was very little dust and no visible burns. I dont think the psu is faulty because I was able to get the disc out by turning on the back switch while holding eject. I plan on trying a reflow but since it doesnt seem like the prevalent type of ylod due to lots of dust inside and/or burn marks Im wary of doing any damage to the motherboard when it may not be the problem.

And before you say send it to sony or a repair shop, dont bother, Im broke. If I had the money for repair or some kind of income I would just save for a brand new console. 174.132.58.186 11:53, January 4, 2011 (UTC)

Well, if the PS3 version has resource management problems like the Xbox version does, maybe it overworked the GPU or some other hot component and caused it/them to overheat despite lack of dust. Also, you probably know this, but you make sure your console is in an open enough space to allow ample airflow. Hopefully this pathetic game engineering debacle will catch up to them in the near future. Fingers crossed. "There was never a good knife made of bad steel" In fucking deed. 10:21, January 9, 2011 (UTC)

I'll be trying the reflow in a couple days and hopefully that will work for awhile. Whether it does or not I doubt I'll be getting another console unless future exclusives are too much to resist. If I build a PC and something fails at least I'll know which parts were bought dirt cheap. I'm down a 360 as well as a ps3 while my laptop which has seen a great deal more abuse remains (mostly) operational.98.20.61.54 18:26, January 10, 2011 (UTC)