Miguel and I just purchased our second PC unit here in Hong Kong, and I was pretty happy about my new specs:

• Intel Core 2 Duo E4600 2.4GHz
• P35 Chipset Motherboard
• 4G 1800 MHz RAM
• 160 Gig SATA Hard Drive
• 20xDVD+RW
• GeForce 8600GT Graphics Card
• 480 Watts Power Supply
• XP Home Edition (OS)
• Acer X243W 24-inch flat screen LCD monitor
• Logitech laser mouse and keyboard

There. That was indeed a mouthful.

Anyways, It has just been 2 days since we bought this, and I have managed to install all of my software, so this PC is ready to rumble, or at least just about.

• ZoneAlarm
• AVG Antivirus
• Dreamweaver CS3
• Adobe Acrobat Professional
• Adobe Illustrator
• Photoshop
• Fireworks
• Contribute
• PhotoImpact
• iTunes
• VLC Player
• Microsoft Office 2007
• Skype, YM, MSN
• Firefox
• Lifecam
• Nokia PC Suite

After having installed everything, I figured I was going to put my new hardware to the test by overworking it a bit. Load speed has been pretty good so far, and internet speed (as well as FTP time) is pretty decent. However I encountered my first problem, which is an error message that looks a little something like this:

BCCode : 44 BCP1 : 8902E008 BCP2 : 00000D63 BCP3 : 00000000
BCP4 : 00000000 OSVer : 5_1_2600 SP : 2_0 Product : 768_1

[SIGH]

This happened when I left my PC on for too long and the monitor shuts down because of inactivity. I got back to my PC, opened my screen and found an error message reporting to me that a SERIOUS ERROR HAD OCCURRED – and as all things Microsoft go, it gave me a bunch of error codes, but no solution to fix it with.

So there I was, sitting shocked at what could have been more than HK$5k down the drain when I went to the internet to try to figure things out. Apparently the BCCode 44 pertains to something related to the automatic hibernation of the screen, or at least that was what it said on a forum thread about a Dell laptop having the same error message. So what I did was proceed to change the hibernation and energy savings settings on my by accessing the menu through my desktop, and hopefully I will never have to see that error message again.

I really do have high hopes for this PC. I just hope I won’t ever get a scare like that again.