IF it was mine… and IF it was NOT still under warranty… what I would do would be to open it up, then do a “cable jiggle” (carefully remove/replace the ribbon cable for the display module several times to scrape any oxide or other crud off the surface), then reassemble, power up, reboot, and try again. If there were still problems I’d do a reformat and then re-install the firmware. If there were STILL problems, I’d get another one and keep that one for spare parts (battery, display, case parts, switches, etc.)
Caveats: I am comfortable with working on things like that (in an earlier life I did similar kind of work for a living). it’s not rocket science, but if you’ve got three left thumbs on each hand and habitually trip over your shoelaces, and spill coffee due to congenital hand-shaking, then I’d look for a local high-school geek-course-major to do the gruntwork. That is, if “you” were “me.” A bit of hyperbole, but you get my drift.
Understand I am NOT advising that you DO *any* of this… I’m just saying what *I* would do in your position. I don’t want, or accept ANY liability for ANY problems that might ensue if someone reads this and decides to try doing any of those things.
That out of the way, very frequently this sort of problem (the symptoms described in the earlier posts) is due to bad connections. Back when i was doing computer support, the FIRST thing I would do when presented with a “broken” computer was to reseat ALL socketed chips (back then, memory came in the form of discrete 64Kx1 chips – LOTS of them on a motherboard to provide 640KB), and, likewise reseat ALL cards (monitor card, I/O card, etc.) AND reseat ALL cables (disk drives. com ports, etc., etc.)
More times than not, this would “repair” the malfunction.