BSoD after fresh Windows 7 install

[tehmerlin]

Hello everyone,

New member to the forums here and I was able to be pretty ninja-like when it came to getting information required to make a post in this forum.

Bought a new computer 2 weeks ago, came in 3 days ago. Been having trouble with it since. Usually I'm the "Mr. Fix-it" when it comes to PC's but I've never messed around with any debugging tools, so I need some assistance please; any help is greatly appreciated.

I've tried all the troubleshooting you can possibly do when trying to diagnose a blue screen of death. Tried both RAM sticks separately, took the video card out and used on-board video. I even tried both RAM sticks with on-board video separately. Unplugged the DVD-ROM, no avail. I called ASRock and got a technician who I could barely understand, but was telling me something about "XMP". I didn't see the XMP option under the DRAM configuration, even if my sticks don't support it wouldn't the option still be there? I think he has my motherboard confused with another one. He told me to either replace the RAM with new RAM or send the motherboard back in and exchange it.

I came here to see what the BSoD DMP files REALLY have to say the problem is, so I can solve it once and for all. I didn't pay for new hardware to let it sit here and collect dust.

I appreciate any help you guys can offer.

SPECS: Nothing is OC'd except the GPU, it was OC'd straight from the factory

MOBO: ASRock Z68 Extreme3 Gen3 @ P1.30 (latest BIOS update)
CPU: Intel Core i5 2500 Sandy Bridge @ 3.30ghz
RAM: GSkill RIPJAWS 2x4gb DDR3 1333
GPU: MSI 560 GTX-TI Twin Frozr ii 2gb
PSU: Corsair TX750W
HDD: 1TB Samsung SATAII @ 3gb/sec
DVD-ROM: ASUS SATA DVD-ROM
OS: Windows 7 Ultimate 64bit RETAIL

 

[tehmerlin]

BSoD 0x00000124 after fresh Win7 install

Anyone...?

 

[Vir Gnarus]

In the single crashdump you provided, it reported an unknown micro-architectural error manifesting within your CPU. Your syslog also shows that the previous crashes were similar if not identical in this case. Since you stated your CPU is not overclocked, we can rule that out. You'll want to check to make sure your CPU temp is good using something like HWInfo (check Sensors only at startup) and logging both a 30-minute idle session and a high load session (if it crashes during either that's actually preferable, it'll retain the log up to latest data collection point). Send to us for evaluation.

You can try installing updated motherboard drivers, as well as flashing your BIOS with any new version available. Make sure to remove all motherboard utilities and software, as they have a history and tendency of producing WHEA errors like this due to bugs. This also includes any OCing and sensor software that came with your mobo.

In addition, you can run Prime95 on Torture Test with Blend for about 9 hours. Any errors at all are indicative of a CPU malfunction.

If you want my honest diagnosis, I would trust the WHEA error in that this is indeed a malfunctioning CPU that needs replacing.

Analysts:

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: [COLOR=DarkGreen]fffffa8007069028[/COLOR], Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000f2001a00, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000010005, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------

TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2

BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  Adobe AIR Appl

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`031dda58 fffff800`03027903 : 00000000`00000124 00000000`00000000 fffffa80`07069028 00000000`f2001a00 : nt!KeBugCheckEx
fffff880`031dda60 fffff800`031e4513 : 00000000`00000001 fffffa80`0706ad30 00000000`00000000 fffffa80`0706ad80 : hal!HalBugCheckSystem+0x1e3
fffff880`031ddaa0 fffff800`030275c8 : 00000000`00000728 fffffa80`0706ad30 fffff880`031dde30 fffff880`031dde00 : nt!WheaReportHwError+0x263
fffff880`031ddb00 fffff800`03026f1a : fffffa80`0706ad30 fffff880`031dde30 fffffa80`0706ad30 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`031ddc50 fffff800`03026dd5 : 00000000`00000004 00000000`00000001 fffff880`031ddeb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`031ddc90 fffff800`0301ae88 : 00000000`06e4f26c 00000000`0000000a 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`031ddcc0 fffff800`030ce7ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`031ddcf0 fffff800`030ce613 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`031dde30 00000000`766e9b79 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`06e4eddc 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x766e9b79


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

Followup: MachineOwner
---------

3: kd> !errrec [COLOR=DarkGreen]fffffa8007069028[/COLOR]
===============================================================================
Common Platform Error Record @ fffffa8007069028
-------------------------------------------------------------------------------
Record Id     : 01cd0632d6d5fcee
Severity      : Fatal (1)
Length        : 864
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 3/20/2012 0:48:41 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa80070690a8
Section       @ fffffa8007069180
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : [COLOR=Red]Micro-Architectural Error[/COLOR]
Flags         : 0x00
CPU Version   : 0x00000000000206a7
Processor ID  : 0x0000000000000006

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa80070690f0
Section       @ fffffa8007069240
Offset        : 536
Length        : 64
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000006
CPU Id        : a7 06 02 00 00 08 10 06 - ff e3 ba 1f 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

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa8007069138
Section       @ fffffa8007069280
Offset        : 600
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : [COLOR=Red]Unknown[/COLOR] (Proc 3 Bank 0)
  Status      : 0xf2001a0000010005

 

[tehmerlin]

I believe it is the CPU as well. It took me hours to fight the BSoD to even install Windows 7. When I finally got it to the desktop it would BSoD and wouldn't let me back onto the desktop. It would even BSoD in safe mode. I ran several memtest86+s on extended on each stick several times and no errors were found. I even flashed the BIOS to the latest version the first time it started BSoD'ing.

In regards to using HWmonitor, that's going to be an issue because I can't even use my computer since it BSoD's before it loads the desktop. :/ That's the only crash dump I could manage to provide before it stopped letting me on the desktop.

I'll try to run that Prime95 test and get back to you all. Thanks for the help so far!

 

[tehmerlin]

Blue screened before I could get into the desktop. I'm going to keep trying to get into the desktop so I can grab another DMP file for you.

 

[tehmerlin]

I by some miracle managed to get to the desktop, and ran maybe 15 seconds worth of the DMP file tester before it blue screened again. Also included all the DMP files in the minidump folder.

 

[Vir Gnarus]

The new crashdumps offer nothing new other than providing further evidence convicting the CPU. I do find interesting that they all point to the same core and cpu cache bank as faulting. Maybe it's core 3 accessing its cache that's triggering the problem. Either way, it's a bugged CPU, I'm afraid. You can check all the previous recommendations before you start putting money towards a new CPU, as a just in case.

 

[tehmerlin]

Thank you much Vir. I was wanting to double check to be absolutely 100% positive.

Should I RMA the motherboard as well as the CPU chip to be safe?

 

[Vir Gnarus]

It's up to you. There is always a slight chance of the motherboard being responsible. I personally don't see anything that involves the mobo being involved here, but if you have the opportunity to RMA both, it's up to your discretion whether you wish to do so or not. Be aware that there's always the chance you could be sending your perfectly good mobo in for a replacement that ends up bad!