Ok, so let me start at the beginning.
First, I spilled some water. Only a small amount got on the bottom of the laptop, and wasn't there very long as I went over it furiously with the closest cloth object I could find (blanket). Some also got onto the top of the laptop, which I also cleaned furiously, including pressing down on the laptop and sliding the blanket back and forth to clean the keys. It seemed fine.
Cleaned up everything else, and went back to my browsing session. After about 30 seconds, the screen went blue, and I got a message about checking my drivers, etc. It contained instructions on how to boot in safe mode and a few other things. I turned off the laptop by holding the power button.
Let it sit upside down (incase there had actually been some water in there) for a good 5-10 minutes, and re-booted. It booted fine, so I figured I might be out of the woods. I look away for a second, and when I return my glance is met with the same blue screen. I read the entire thing, and noticed a long code with lots of 0's in it. I started to copy it, incase it could help, but the bluescreen freaked out, something about the memory dump failing. Then I got a new blue screen, that just told me the program had failed, and told me to contact my hardware provider. The final line read something like **The program has halted**
Also, at the bottom of the original screen, it said: irql_not_less_or_equal
After googling said message, I have found nothing about water damage.
Some things I feel may be the culprit, or may be unrelated:
Running in "test mode"
At the time of the crash, I was running windows 7 in test mode. I also had an option to allow unsigned drivers to work. This was so I could use my PS3 controller as a gamepad, without having to do an advanced boot every time.
Firewall down
My firewall was down. Not a big believer that any malicious program could do so much harm without setting off AVG, but I figured anything and everything is worth mentioning.T
The unsigned driver
motioninjoy's driver
One thing that is interesting is that windows started for about 30 seconds, desktop and all. This was on my re-boot, obviously.
I thought about doing a safe mode>system restore, but I'm afraid the system will crash while booting safe mode, or even worse while doing the restore.
Ok, asking for all opinions on the issue.
Current plan of action is to wait until tomorrow night, then go ahead with the restore.
Comment