BSOD, STOP 0xc0000034

Question

This happened after a failed overclock. I got the initial BSOD for a failed overclock, reset the CMOS, and then rebooted and Windows started to load then went to a black screen. After waiting for about 10 minutes I decided to force a restart. That's when I got the second BSOD. STOP: 0x0000007b (0xFFFFF880009A9928, 0xFFFFFFc0000034 0x00000000, 0x00000000)
Windows auto recovery didn't fix the problem (even using the boot disc), system restore did not work, chkdsk didn't pick up any errors, I ran the diagnosis software for my HDD and that came up clean..
I cannot boot into Windows or Safe Mode at all.
I googled for hours and it might be corrupt or missing drivers, or maybe even settings are off somewhere. I'm at a loss.
AMD Phenom II X4 B55 BE @ 3.2 ghz (unlocked X2 555)
MSI 790X-G45 Bios V1.6
G.SKILL 4GB (2 x 2GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800) Dual Channel Model F3-12800CL9D-4GBNQ (9-9-9-24 2x command rate)
SAPPHIRE Radeon HD 5770 1GB 128-bit GDDR5 PCI Express 2.0 x16
Western Digital Caviar Black WD5001AALS 500GB 7200 RPM SATA 3.0Gb/s 3.5"
Rosewill RNX-N300X PCI Wireless Adapter
ASUS DRW-24B1ST/BLK/B/AS Black SATA 24X DVD Burner - Bulk - OEM
Windows 7 64bit Professional
RAIDMAX HYBRID 2 RX-530SS 530W ATX12V V2.2/ EPS12V +3.3V@28A, +5V@34A, +12V1@20A, +12V2@17A, [email protected], [email protected]

Answer 1

Quote from: Mark on 17-August-10, 19:18:43
As you reset the BIOS settings you need to go into the BIOS and check all is set correctly for your hard drive.
For now, set your RAM to 1333mhz as anything above that is overclocking. Test the modules thoroughly with >>Memtest86<<.
As far as I know, the settings are correct. The memory passed memtest.
Quote from: Fredrik on 17-August-10, 19:30:20
Pull power cable out when clearing CMOS.
But BIOS/CMOS has little to do with BSOD:s.  Use a singe stick at a time and look at them closely.
Raidmax makes decent cases but their choice of PSU:s for them is terrible! Don't trust the specs.
Try the most basic of SafeModes if you haven't.
Test the hard disk in another system, and no or another hard disk in yours.
Adr: It is the 7B in the blue-screen that is the top priority. And that can mean anything, why I think maybe your PSU is involved.
I picked out and bought the PSU myself and went by reviews on newegg.
What do you mean by most basic? I tried hitting F8 and accessing it from there and no dice.
I cannot test the HDD in another system, but I really do not think it is the problem anyway as it passed the manufacturer's diagnostic test. I also have another SS to post.
I was under the impression the second parameter inside the parenthesis is where to look. I found a lot of info from google about the 0xc00000034. I cannot find which file needs to be replaced though..
Quote from: Mark on 17-August-10, 21:23:14
Well, if certain settings are reset it certainly can.
Njchopper87, if you installed Windows 7 with AHCI mode enabled in the BIOS make sure you set it to AHCI again.
I do not know how it was configured when installed. I tried changing it to AHCI though and the screen just flashed a different BSOD with no error code.. just the "Your computer was shut down to avoid causing damage..." message.
Quote from: Bas on 17-August-10, 21:32:44
Are you sure all cores are properly functioning?
Positive. I've had it for a few weeks now. It passed an initial 12 hour stress test of Prime 95 on the first day, then I ran it for 24 hours a couple days later, and then it ran for 24 hours again bumped up to 3.6 ghz. The highest the voltage went was 1.4378 or close to that. Left it on auto to see how it would fair.
Quote from: Onslaught2k3 on 18-August-10, 02:04:14
That is definitely an overclocking-based issue mate.  BSODS are more specific than you think and when it says "a secondary processor didn't receive a clock request" OR "your computer was shut down to prevent damage" what this means is that Windows' rudimentary Hardware Application Layer.dll (HAL.DLL) starts to NOT respond to the hardware in the computer because of an overclock.  The components in the computer may not be fully communicating with windows properly, causing the blue screening.  You're going to have to lower the clocks OR increase the voltages if you haven't done so already to ensure a stable system.  Also, lowering the HT link speed can also remedy that blue screen using the HT multiplier editor in BIOS.  AMD's ceilings for HyperTransport speeds is 2.6 Ghz instead of 2.0 Ghz but for most users proven very unstable so most just bump the multi on the CPU anyways.  I have a x2 555 myself and had to bump the voltage to about 1.45 volts to get a 4.2-4.4 Ghz overclock (I've experienced a few freezes and blue screens with the 4.4 ghz  OC but 4.2 is rock stable).  Good luck!
I was attempting to raise the CPU-NB to 2200 from the 2000 stock. Left the voltage on auto. Kept the HT link speed at 2000.
Here are a couple screens of the startup repair error. It is a corrupt file of some sort.. I recall it mentioning system 32 the very first time I saw the BSOD.. I just do not know which file needs to be replaced..