Windows 2000!!

Hmm... okay, what's with Windows 2000? Well, actually, nothing. It's just for fun. Alright, alright. Here:

My desktop is actually incredibly unstable. Most of the time, I suspect my hardware is failing. Now, after the clean install of Windows XP, the graphics driver didn't really crash that much. Well, the last time I remember it crashing was before I started fixing my desktop. However, even after the clean install, with fresh new drivers, the stupid file, win32k.sys always dies and displays the Blue Screen of Death. Most of the time, the bug check code was 0x0000008E, or KERNEL_MODE_EXCEPTION_NOT_HANDLED. The first parameter after that code was 0xC0000005, which is STATUS_ACCESS_VIOLATION. What does this all mean leh? According to the microsoft website. This means there was a memory access violation. More googling tells me that me RAM may be faulty. But, I can't really do anything about it right now. Sorry for dumping all the technical jargon at you. You see, whenever I see anything new regarding my desktop, I always try to dive deeper into my desktop to investigate. It's kinda fun at first, but incredibly frustrating.

Now, since I suspect my RAM is faulty, and couldn't do anything about it right now, the of guilt points to Windows XP. Windows XP requires at least 128MB of RAM, which is basically 1/2 of what I have. I thought "hey, that's kinda a lot". And since I have my Windows 2000 disc with me, I re-installed my Windows 2000. Why re-install? I destroyed my previous installation of Windows 2000. And I've learnt a very important lesson: You should never mess with drivers. What I did was, I used the audio driver that is for Windows XP in my Windows 2000. Incompatibility caused my Windows 2000 to die.

So, in the end, my desktop is working better than before. I hope nothing bad will happen after saying that. Lol!

Alright, onto even more serious stuff!!

Percubaan Setara PMR!!

It's just 2 more days!! I'm panicking for BM (like what I said 2 posts earlier). Sigh...