Solved BSOD problem , dmp file included

[MissGrimsby]

Hello all!

Hoping you guys can help, I'm getting a repeated bluescreen when trying to load Cubase.

No new software has been installed/updated [to my knowledge] so I'm guessing it may be a hardware issue.

I backed everything up using Windows Backup, and attempted a System Restore to 3 weeks prior. This didn't work unfortunately, and after another bluescreen/reset Windows started and proceeded to desktop with this message:

Windows has recovered from an unexpected shutdown:

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

Additional information about the problem:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA800811D748
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\100213-15007-01.dmp
C:\Users\Bouch\AppData\Local\Temp\WER-26020-0.sysdata.xml

I have included the dmp file as an attachment to this post.

Many thanks for any help in advance!

 

[Arc]

Hi MissGrimsby.

The BSOD that you supplied is a stop 0x124, usually it is assumed to be a hardware related error. To debug that issue, we need some more information.

First, Post it following the Blue Screen of Death (BSOD) Posting Instructions.

Second, fill up your system specs.
See your system specs and fill it up here.

Also, take some hardware tests.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Stress test the CPU.
Hardware - Stress Test With Prime95

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator
Also let us know the wattage of the PSU.

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy.

Let us know the results.

BTW, we have noticed BSODs with Cubase earlier ... make it sure that the software is properly updated and the hardware is working fine.
________________________________________________________________________

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

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800811d748, 0, 0}

Probably caused by : AuthenticAMD

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

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: fffffa800811d748, 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`031715b0 fffff800`02f0ed29 : fffffa80`0811d720 fffffa80`06db7040 00000000`00000006 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`03171ad0 fffff800`02dee217 : fffffa80`0811d720 fffff800`02e68658 fffffa80`06db7040 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`03171b00 fffff800`02d55865 : fffff800`02eca3a0 00000000`00000001 fffffa80`0785f980 fffffa80`06db7040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`03171b40 fffff800`02cd5a21 : fffff880`0110be00 fffff800`02d55840 fffffa80`06db7000 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`03171b70 fffff800`02f68cce : 00000000`00000000 fffffa80`06db7040 00000000`00000080 fffffa80`06cad990 : nt!ExpWorkerThread+0x111
fffff880`03171c00 fffff800`02cbcfe6 : fffff880`03090180 fffffa80`06db7040 fffff880`0309b040 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03171c40 00000000`00000000 : fffff880`03172000 fffff880`0316c000 fffff880`03fa6400 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
---------

 

[MissGrimsby]

Thank you Arc, for the prompt response!

I guess I was hoping for a quick fix, there are many steps to take but I'm on it!

I will report back when I have all the information required.

Thanks again!

 

[Arc]

Unfortunately a stop 0x124 does not have a quick fix.

 

[MissGrimsby]

How unfortunate! My gut instinct tells me it's going to be the RAM. I've had problems with failing RAM modules in the past on other systems... due to the time required using Memtest 86+, I'm starting there. I've booted the program from USB and it's rolling now. I was tempted to just remove each module independendly and try loading Cubase to save time without running the program. Opinions?

UPDATE: It's found an error already. Time to shuffle these modules!

 

[Arc]

UPDATE: It's found an error already. Time to shuffle these modules!

Now follow the "Part 3: If You Have Errors:" of How to Test and Diagnose RAM Issues with Memtest86+

Errors/red lines means one or more RAM is faulty. But the fault may occur due to a faulty DIMM slot, too, which is a motherboard component. Using memtest86+, you can discriminate between a faulty RAM and a faulty motherboard.

How? Say you have two RAM sticks and two DIMM slots. You obtained errors at the test with all RAM sticks installed. Now, remove all the sticks but one. Test it in all the available slots, one by one. Continue the same procedure for all the available sticks.
How to make the inference that is it a RAM issue or it is a motherboard issue? Suppose you have got the result like that:

test|Slot1|Slot2
RAM1| Error | Error
RAM2|Good|Good

It is a RAM, a bad RAM.

But if you have got a result like that:

test|Slot1|Slot2
RAM1| Error |Good
RAM2| Error |Good

It is a motherboard issue. The particular slot is bad.

 

[MissGrimsby]

Tested a single module - Memtest86+ gave errors in both slots. Removed the offending module and inserted the other. Tested good for one pass, took a gamble and fired up Windows/Cubase - success! Huge thanks to you Arc, it's been a testing 36 hours since first having the problem and your help has been invaluable. Thanks again!

 

[Arc]

Good to know

Let us know for any further issue.