Windows 7 Error Code: STOP: 0x000000A5 - A New Solution
Saturday, January 16, 2010 8:04:09 PM
I have been running Windows 7 for the past 2 months, and it's been fine. A really good effort by Microsoft to repair the damage done since Windows ME. And I for one have been very happy with it, until last night.
For the past few days, I had noticed the computer was slowing down a little bit. So I decided to buy a Flash drive to use this "ReadyBoost" option that Windows has told me about since Vista. Anyway, on powering on my machine, I felt the cable of an external hard drive and it was red hot. So hot it melted in to the plastic of the PC case. And this is where the problems started.
When Windows booted up, it went straight to a BSOD (Blue Screen Of Death). It displayed this:
I googled the code, and all the posts I read referred to Windows XP having this error when the motherboard's ACPI is incompatible with Windows, and a BIOS upgrade was needed. I fiddled about with the BIOS settings, such as enabling ACPI 2.0 support, and nothing would work. But, Windows would sometimes work, but then switch off.
Getting desperate I decided to try the Live CD of openSuSE 11.2 to see if I could at least use the computer itself. On trying to use Live KDE or Live GNOME, I got a Kernel error. Nothing had started yet! I tried an Installation, and that only got so far until a Kernel panic ended it. On restarting, I decided to do a Memtest. Because, to me, if the Live KDE or Live GNOME wouldn't work, then it must be RAM related. I ran the test, and the RAM failed.
I took out one stick of RAM (my computer is comprised of a single 1GB and a single 256MB). openSuSE ran with the 256MB, but I thought Windows 7 wouldn't run with that. So I swapped them around, and I'm writing this blog to you from inside Windows 7.
Now I'm not a huge hardware wizzard. But I think my burning USB cable and this failed RAM issue are related. So far, I haven't tried the computer running either RAM stick in the second RAM slot. A duffed RAM slot may be the problem? I don't know, but hopefully some one out there could shed some light on this?
So to you guys who are experiencing this problem. Before attempting a risky BIOS upgrade, CHECK YOUR RAM!