Windows 7: Unexpected shutdowns/BlueScreen event name

lane472 · 27 Nov 2012

I don't actually get a blue screen, but on the Problem Event Name, it lists bluescreen, so I'm not sure if I should post this here or not, but here are the details:

Quote:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA80085294F8
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\112712-23322-01.dmp
C:\Users\Admin\AppData\Local\Temp\WER-48282-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

When I click check for solution, it acts like it's checking for a minute or two, closes, and nothing shows up.

I've made sure my drivers are all up to date, I've tried reformatting, I've made sure Windows is completely up to date, etc, etc, etc. Not even sure what's left to try at this point. Thanks in advance for any help.

lane472 · 27 Nov 2012

Sorry for double post, but figure I would add that for the past 4 or 5 hours I've left it in safe mode and it has not crashed. Also, this is a brand new custom PC(bought, not built myself). Only been using it today.

**koolkat77** · 27 Nov 2012

Welcome to SevenForums.

Go through this thread step by step for an insight on the bugcheck: Stop 0x124 - what it means and what to try

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa80085294f8, 0, 0}

Probably caused by : AuthenticAMD

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

1: 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: fffffa80085294f8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`031a16f0 fffff800`02cc9ca9 : fffffa80`085294d0 fffffa80`06acb040 00000000`0000000c 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`031a1c10 fffff800`02baa557 : fffffa80`085294d0 fffff800`02c242d8 fffffa80`06acb040 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`031a1c40 fffff800`02b11935 : fffff800`02c85ae0 00000000`00000001 fffffa80`079b5820 fffffa80`06acb040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`031a1c80 fffff800`02a90641 : fffff880`01068e00 fffff800`02b11910 fffffa80`06acb000 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`031a1cb0 fffff800`02d1de5a : 00000000`00000000 fffffa80`06acb040 00000000`00000080 fffffa80`069ab9e0 : nt!ExpWorkerThread+0x111
fffff880`031a1d40 fffff800`02a77d26 : fffff880`02f64180 fffffa80`06acb040 fffff880`02f6efc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031a1d80 00000000`00000000 : fffff880`031a2000 fffff880`0319c000 fffff880`031a1200 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: AuthenticAMD

IMAGE_NAME:  AuthenticAMD

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

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

1: kd> !errrec fffffa80085294f8
===============================================================================
Common Platform Error Record @ fffffa80085294f8
-------------------------------------------------------------------------------
Record Id     : 01cdcd1ea94f4d45
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 11/28/2012 4:13:12 (UTC)
Flags         : 0x00000002 PreviousError

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa8008529578
Section       @ fffffa8008529650
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         : 3
CPU Version   : 0x0000000000100f43
Processor ID  : 0x0000000000000000

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa80085295c0
Section       @ fffffa8008529710
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000000
CPU Id        : 43 0f 10 00 00 08 04 00 - 09 20 80 00 ff fb 8b 17
                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  @ fffffa8008529710

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa8008529608
Section       @ fffffa8008529790
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : BUSLG_OBS_ERR_*_NOTIMEOUT_ERR (Proc 0 Bank 4)
  Status      : 0xf6000000000c0c0f
  Address     : 0x0000000000000002
  Misc.       : 0x0000000000000000

1: kd> !sysinfo cpuspeed
sysinfo: could not find necessary interfaces.
sysinfo: note that mssmbios.sys must be loaded (XPSP2+).

lane472 · 27 Nov 2012

Thanks for the assistance, Koolkat.

I also talked to the guy who built the computer, and he suggested I take out one of the sticks of ram and try it. I've done that, and now it's going on 4 hours without crashing; the longest period of time it's went, so I feel that did the trick.

Again, thanks for your assistance and quick response, some places I've waited days for someone to respond, lol.

Edit: it crashed after 6 or so hours, so that turned out not to be the fix.

**koolkat77** · 27 Nov 2012

I see..you can test the RAM sticks if you have time.

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

RAM - Test with Memtest86+

Quote:

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.
Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.
If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
3. Test the next stick of RAM (stick #2) in the next motherboard slot.
If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

Errors are sometimes found after 8 passes.

Do this test overnight, before going to bed.

Windows 7: Unexpected shutdowns/BlueScreen event name

Unexpected shutdowns/BlueScreen event name problems?