could a spilled drink on my macbook cause problems 3 years later??

[koots55]

So I spilled some Sprite on my macbook keyboard about 3 years ago. Everything has always worked fine except a couple sticky keys, which over time got better. A few days ago I did a "System Update". Then my computer would not let me login. It kept going in a loop from the password screen, to blue screen, to login screen.

What was worse is that it would not recognize any of the key combinations for starting up in a different mode. Or just trying to start up from the disc, since I had the mac os x startup disc in the drive.

So.... I took it in. The guys there didn't know how to fix it right away so I left it. They call back the next day, said they took it apart, and found "sticky stuff" inside which was the cause of the problem.

I think that is ********..... but I want to know what you guys think before I call them back.

 

[miles01110]

could a spilled drink on my macbook cause problems 3 years later??

Yes.

 

[RyanTheGeneral]

well I would almost say you should tell them its sprite, seeing as you said they found "Sticky stuff". I don't know about you but my first reaction when they said that would of been- its definitely not what you may think.

On a more serious note, you should of found some way of cleaning it out. Cant be good for dried up soda to be sitting inside of your computer, something tells me that can't be good.

 

[BEASTMAN]

A liquid like that can cause issues after a significant amount of time. Just takes some corrosion that was left to change a bit with the humidity of the summer to short something out.

But it is very unlikely that your issue that you are describing is caused from that. Your issue is likely a software issue with a particular file in your user library.

Easiest way to tell is to try to log into another user account on the computer. If you do not have one, you can boot up into your startup disc, go to reset password, reset the password for the root user, restart and login to "other" username: root password: whatyouchose

From the root user you can start pulling user library files that could be causing it, but if you are unfamiliar with these I would recommend just letting your tech do this.