Blue Screen only during start up or reboot

Alright, so i've had this issue for a while, and it's only been getting worse.

Whenever I have to reboot my computer, or when i'm turning it on after it's been powered down, it is rebooting just as it gets to the Windows loading screen, and usually fails to start up on second boot sending me to the start up repair tool.

Typically to resolve the issue temporarily, I have had to use the last known good configuration, but recently that isn't even working. I am now having to use system restore to go back a couple of days, no matter what i've done, or have been doing.

It has also been having issues waking from sleep (which is the primary method of "shutting it down" as of the last 6 months) Often times my computer will simply say "No signal" until I restart or shut down the computer.

Most often during these auto-reboot loops a BSOD will flash up briefly before it restarts. It has also been mentioning something of possible graphics card issues, and most recently has mentioned hardware being recently connected that could be causing the issue. Though if I remember correctly, that is a generic message.

When going through the start up repair last night I gathered this information.

Root Cause Found:
------------------
Unknown Bugcheck: Bugcheck 124. Parameters = 0x0, 0xFFFFFa8008231038, 0xb2000040, 0x800.

Repair Action: System files integrity check and repair.

Result: Failed. Error Code = 0x490
Time Taken = 753594ms

I then later got a BSOD:

Stop 0x0000009C
0x0000000000000000
0xFFFFF880009C7AB0
0x00000000B2000040
0x0000000000000800

And finally I had a list of 15 unreported problems that popped up on me after I finally got into Windows last night. All 15 were exactly the same, which are as follows:

Windows
Problem: Video hardware error
Files that help describe the problem:
WD-20121001-1239.dmp
sysdata.xml
WERInternalMetadata.xml
View a temporary copy of these files
Warning: If a virus or other security threat caused the problem, opening a copy of the files could harm your computer.

This is all the information I have, and i'm more than willing to provide what ever else is needed to help resolve this issue, thanks ahead of time.

The only dump included indicates a BugCheck 124 and is an unrecoverable hardware failure. These are hard to track down even when the WHEA record is present. In your case, it's indicating a CPU L0 cache error. This is the primary processor cache from which all data and code flows. Processor cache errors can be caused by low voltage, high temperatures and/or system memory errors.

If you are OCing the CPU, return it to default timings and voltages.
If you are not OCing, use a hardware monitor that will display voltages and temperatures and monitor for excessive heat and low voltages. Intel specifies a maximum of +/- 5%

Code:

 
 1: kd> !errrec fffffa80082d5038
===============================================================================
Common Platform Error Record @ fffffa80082d5038
-------------------------------------------------------------------------------
Record Id     : 01cd60ce340a8ac4
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 7/13/2012 8:05:14
Flags         : 0x00000000
===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa80082d50b8
Section       @ fffffa80082d5190
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal
Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : BUS error
Operation     : Generic
Flags         : 0x00
Level         : 0
CPU Version   : 0x000000000001067a
Processor ID  : 0x0000000000000001
===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa80082d5100
Section       @ fffffa80082d5250
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal
Local APIC Id : 0x0000000000000001
CPU Id        : 7a 06 01 00 00 08 02 01 - 9d e3 08 0c ff fb eb bf
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
Proc. Info 0  @ fffffa80082d5250
===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa80082d5148
Section       @ fffffa80082d52d0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal
Error         : BUSL0_SRC_ERR_M_NOTIMEOUT_ERR (Proc 1 Bank 0)
  Status      : 0xb200004000000800

FuriousMike5

Open up a new thread inside SYSTEM SECURITY and we will have the malware removal experts run a few programs and see if you have any adware or viruses roaming around that is causing your BSODs . Just as a precaution .

This computer was built by a co-worker of mine, wasn't a fresh install of Windows either.

Unless it's a Dell computer, the version of Windows the builder installed is fraudulent.

BIOS Version/Date Phoenix Technologies, LTD 6.00 PG, 9/1/2008

Return the PC to the builder and have him install a legal version of Windows 7 then update it along with the BIOS and drivers for the motherboard. We can't assist with repairing fraudulent software.

On a side note:
I don't particularly trust Ad-Aware. It's considered malware in its own right. Also, AVG is often troublesome in Windows 7. I would recommend uninstalling both and use Microsoft Security Essentials (MSE) as a real-time AV scanner and the FREE version of MalwareBytes Anti-malware (MBAM) as a stand alone scanner.

Yep, I see that now. I misread BUSL0... to be the cache. Sorry.

Good to hear you got it going. Do check on your OS though. The product code comes back on a Dell OEM machine and you may find it not working after a period of time. Or the builder installed an old Dell motherboard in your new build. The BIOS is old. Good luck.

You can do a Repair Install but only for the same product code. A new product code will require a new install with a valid key for that product code. There are many product codes for Windows 7 Ultimate. (That how we can tell the origin of the product code.)