isayni2u
Vendor
- Jul 27, 2005
- 15
Oh, I feel as if I have been shot!
My "child", a gaming Box which I created as a freshman at WashU died on me 15 min. before work this morning!!!
NOoOooooOooo....
Specs:
3.2 Pentium 4 HT
GeForce nVida 6600 Pro
500W ULTRA
1G Corsair DDR2
250G Maxtor
[Asus A5PGD2 Premium]
-" Marvell PCIe 88E8053 Gigabit LAN controller
-" Marvell PCI 88E8001 Gigabit LAN controller
-" 802.11g Wireless
-" IEEE1394a (rear I/O)
-" IEEE1394b (via bracket)
-" both 4x IDE and SATA RAID
- with certain Special Features:
Stack Cool heat spreader
Copper MOSFET cooler
LAN cable checker
Q-Fan2 fan control
Ai NOS dynamic overclocking
CrashFree BIOS 2
The problem started after I did a massive bug removal utilizing Adaware, Spysweeper, and Norton Anti-virus. The CPU seemed a little taxed, so I checked the internal core temp and glanced at my voltage monitor. Everything was within normal limits...
After the cleaning, I decided to alter the overclocking settings. In anticipation of a LAN, I set the AI NOS to 115% [it ran fine at 120 and 125% nearly a year ago!]. As I clicked on the option for 115%, the computer froze. I waited 3 min and then rebooted...
Bad move.
I knew something was deathly wrong when Bios began POST [checking IDE...] flashed the ASUS bios screen for about a sec...then it went blank and started POST again. As fate would have it, just when windows began to load, a BSOD [BLUE SCREEN OF DOOM] appeared:
0X0000008E (0XC0000005, 0X8053684 (5?-can't recall last digit atm)) virtual memory dump!
Since this is a RAM error, I believe at least,...I reseated the RAM and rebooted.
No change.
In desperation, I rebooted again! Everything was the same except the BSOD didn't appear. Instead, the Window's XP user/administrator log-in screen was displayed. I attempted to log in...
and got another BSOD with [fatal error] code: c000021a f 0X00000080 (0X00000000, oX00000000).
After trying to reboot and log in three times to no avail. I gave up at least for the moment, and went to work. Each time, the fatal error code c000021a showed up!
From what I have read, this is a window's log-in error resulting from a WinLOgon faliure. But I suspect that somehow...
I killed my CPU!
-Any Thoughts?
ALL YOUR BASE ARE BELONG TO ME!
My "child", a gaming Box which I created as a freshman at WashU died on me 15 min. before work this morning!!!
NOoOooooOooo....
Specs:
3.2 Pentium 4 HT
GeForce nVida 6600 Pro
500W ULTRA
1G Corsair DDR2
250G Maxtor
[Asus A5PGD2 Premium]
-" Marvell PCIe 88E8053 Gigabit LAN controller
-" Marvell PCI 88E8001 Gigabit LAN controller
-" 802.11g Wireless
-" IEEE1394a (rear I/O)
-" IEEE1394b (via bracket)
-" both 4x IDE and SATA RAID
- with certain Special Features:
Stack Cool heat spreader
Copper MOSFET cooler
LAN cable checker
Q-Fan2 fan control
Ai NOS dynamic overclocking
CrashFree BIOS 2
The problem started after I did a massive bug removal utilizing Adaware, Spysweeper, and Norton Anti-virus. The CPU seemed a little taxed, so I checked the internal core temp and glanced at my voltage monitor. Everything was within normal limits...
After the cleaning, I decided to alter the overclocking settings. In anticipation of a LAN, I set the AI NOS to 115% [it ran fine at 120 and 125% nearly a year ago!]. As I clicked on the option for 115%, the computer froze. I waited 3 min and then rebooted...
Bad move.
I knew something was deathly wrong when Bios began POST [checking IDE...] flashed the ASUS bios screen for about a sec...then it went blank and started POST again. As fate would have it, just when windows began to load, a BSOD [BLUE SCREEN OF DOOM] appeared:
0X0000008E (0XC0000005, 0X8053684 (5?-can't recall last digit atm)) virtual memory dump!
Since this is a RAM error, I believe at least,...I reseated the RAM and rebooted.
No change.
In desperation, I rebooted again! Everything was the same except the BSOD didn't appear. Instead, the Window's XP user/administrator log-in screen was displayed. I attempted to log in...
and got another BSOD with [fatal error] code: c000021a f 0X00000080 (0X00000000, oX00000000).
After trying to reboot and log in three times to no avail. I gave up at least for the moment, and went to work. Each time, the fatal error code c000021a showed up!
From what I have read, this is a window's log-in error resulting from a WinLOgon faliure. But I suspect that somehow...
I killed my CPU!
-Any Thoughts?
ALL YOUR BASE ARE BELONG TO ME!