Solved Blue Screen only during start up or reboot

[FuriousMike5]

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.

 

[carwiz]

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%

 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]

Why doesn't it crash, freeze, or give me a BSOD while i'm actively using it?

Personally I feel it's virus related. When I was using Ad-Aware, I was continuously receiving alerts that it shut down unexpectedly.

I haven't tampered with the CPU timing or voltages, i'm not that advanced of a user. This computer was built by a co-worker of mine, wasn't a fresh install of Windows either.

So, where would I start by tracking down these potential hardware issues?

*On another note* It's nearly impossible to boot up with my DVD ROM connected. The initial boot screen that shows the IDE slave and master connections. (Which is also strange because it's not IDE connection, it's SATA) Figured that might be useful.

 

[VistaKing]

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 .

 

[carwiz]

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.

 

[FuriousMike5]

Issue Resolved

Yeah, that's all well and nice and everything, good to know my co-worker lied to me, but whatever.

I just wanted to point out that it was my graphics card that failed.

Boots like a charm now.

 

[carwiz]

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.

 

[FuriousMike5]

Eh, it happens. Yeah, my neighbor actually had the exact same card, but wasn't using it. Actually had two, which he said I could hook together and have some fancy doodad that i'm gonna look into later.

Regardless, yes, i will look into my OS, my buddy is gonna see if he can find a cheap copy of 7 Ultimate for me.

I hear that you can install the OS over the current one without affecting user installed items now (like the Mac OS) Is that true?

 

[carwiz]

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.)

 

[FuriousMike5]

Good to know, but that kinda sucks.

Is it possible that he just installed in on another computer first, and then on this one?

 

[carwiz]

Perhaps. It's not uncommon for an OEM to use one copy of an OS and load it to hundreds of PCs. What makes each install unique is the key and a license is purchased for that key. The problem is that your OS product code was assigned to Dell and your PC is not an OEM Dell. It means the builder stole the OS and is using a fraudulent key. I wouldn't be surprised if the OS stops working after 90 days.

 

[FuriousMike5]

Interesting that. I purchased this computer over a year ago. So if it was invalid wouldn't it have stopped working in the 90 days like you say?

I'm very confused on this matter, changing the terminology doesn't help.

The key refers to the product key on the Windows 7 Ultimate box that was purchased.

The licence is acquired when you register it with Microsoft.

So what is this product code that is assigned to this Dell?

Also, you can purchase and register Windows 7 on up to a certain number of computers before issues arise, correct?

I just want to see if there is a way to correct this issue without having to fork out close to 200 bucks for a valid copy, which i'm more than happy to do if that is the only way.

 

[carwiz]

I'm not intentionally changing the terminology. There are two codes associated with every Windows product. Product Code is Product ID. This the 18-20 character designation for each Windows version. It will look something like this: 89578-OEM-7332157-00056.

Product Key is a one-of-a-kind 25 character code used to register your product. It will look something like this: *****-*****-WWR7C-QF2M7-2TB37. (Asterisks replaced valid characters.) And ALWAYS keep this code private.

While there may be millions of duplicate Product IDs, each Product Key is unique and becomes part of your Globally Unique ID (GUID) for a specific machine, including CPU, Motherboard and other hardware. Any significant changes to the PC will cause Windows to generate a new GUID and link it to Microsoft.

Did you get a Windows CD or is there a Certificate of Authenticity (CoA) sticker attached to your PC? The CoA sticker should be attached on the back or side of the PC and will contain both the Product ID and the unique Product Key. Since your Product ID was originally assigned to Dell for use in Dell computers, the CoA sticker will show the OEM name. Any other use of the Dell Product is fraudulent. The builder may be using a product key assigned to him by a license subscription from Microsoft. This license is for products HE uses or has available as a developer. When his subscription runs out so will the keys. It is illegal for him to transfer the product keys to someone else.

The sticker will look something like this.

 

[FuriousMike5]

Alright, well that spells it out for me.

Turns out my buddy may be able to get a copy of Windows 7 Ultimate for pretty cheap for me, so i'm gonna look into that and just re-install, because I don't see any sticker as you've described.

Thanks for all the help and info.

 

[carwiz]

Be careful where you buy Windows 7 Ultimate for "cheap". There's a lot of counterfeit copies being sold. If the price is too good to be true, it probably is.

How to know you're buying genuine Windows - Microsoft Windows
Take special note of the edge-to-edge hologram. Counterfeit copies will have a label and you can feel the edge of the label. A Genuine CD will have the hologram embedded into the CD itself.

Here's a YouTube example of a fake CD. Bogus Windows 7 warning - YouTube

 

[FuriousMike5]

I am glad you informed me of this.

Here I was thinking "If it's not in the sealed package, i'm not gonna get it."

HA! XD Apparently that doesn't matter!

Thanks again guys, you've been super helpful.