Blue screen pops up for a split second right after Windows starts

Right after the Windows logo appears—basically during the "Windows is starting" screen—I get hit with a blue screen.
I'll upload a photo later, but the error code is 0x0000007B (0xFFFF880009A...........).
Safe Mode won't load, and the Windows recovery options aren't finding any fixes. I even tried swapping in a new Hard Disk Drive and had a friend try to install Windows on it, but it still won't boot. I've tried starting up without a mouse or keyboard, and I've even tried reseating the RAM sticks one by one, but nothing works.
This all started after the computer froze up once; I tried to do a hard reset, and since then, it's been stuck.
My specs are a Gigabyte motherboard, an Intel Core i3, and Windows 7 64-bit.

Even with a fresh Hard Disk Drive and Windows? That’s weird. Try resetting the CMOS. Basically, just pull that tiny battery out of the motherboard for about 30 to 60 seconds, pop it back in, and give it another shot.

Adam Moore3 said:Even with a brand new Hard Disk Drive and Windows? That's strange. Try resetting the CMOS. Basically, pull that tiny battery out of the motherboard for about 30 to 60 seconds, pop it back in, and give it another shot.

Now I'm not even getting a blue screen.

So, what’s it showing you? It’ll probably just throw up a message saying the CMOS was reset and tell you to press any key to continue, or something like that...

Adam Moore3 said:What exactly is it showing you? It'll probably just give you a message saying the CMOS was reset and ask you to "press any key to continue," right?

When I boot the PC, it asks if I want to start normally or run a repair. If I choose to start normally, it gets to the "Windows is starting" screen and then just reboots itself.

Looking at the situation and considering what you've said... I'd say either your power supply is failing or your graphics card is dead.

Standard procedure would be to check your voltage levels in the BIOS. Go ahead and look—specifically at the 12V rail. What's the reading?

As for the GPU, it's simple. During the transition from MS-DOS to Windows, the card isn't utilizing its full suite of features, which is why you still see an image. Once Windows loads, the hardware initializes fully. If there's a fault there, everything fails.

There could be other causes, but only God knows what you're actually doing.