BSOD continuing post format.

Meany · 02 Jun 2014

Hey there, situation is whenever the system is under load it bsods and restarts in an instant, I have removed and shuffled my RAM to try and narrow down a hardware issue, aswell as removing my SSD and installed windows on my 1Tb samsung internal to no avail, so have reconnected it. The last Bsod occured as soon as I turned on a rarely used 1Tb Lacie external I use for backups, within .5s of the disk spinning up. Bsods beforehand have had the 3Tb WD Elements attached and most often not in use. My fear is a power supply issue.

Attached are the logs using the DM log collector, aswell as my own recording from earlier.

Arc · 02 Jun 2014

Hi Meany.

A stop 0x124 might be a power supply issue. But first of all let us take care of some drivers.

Install Service pack 1 and all other windows updates. Otherwise the system will remain vulnerable to threats.
Learn how to install Windows 7 Service Pack 1 (SP1)
Service Pack and Update Center - Microsoft Windows

Make it sure that the NETGEAR A6200 is running with the latest driver.
A6200

You also need to update Renesas USB3 drivers; but ASUS does not have any update with them. Try a third party source like Renesas/Nec uPD720200/720200a USB3 Controller Drivers Version 2.1.39.0 WHQL

Make it sure that the SSD is having the latest firmware.
How to Upgrade OCZ SSD Firmware | StorageReview.com - Storage Reviews

Let us know the results. After seeing those, we will start hardware testing.
______________________________

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8008f72028, b424a000, 8d000145}

Probably caused by : AuthenticAMD

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

5: 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: fffffa8008f72028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b424a000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000008d000145, 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:  f

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

STACK_TEXT:  
fffff880`03090b08 fffff800`03009903 : 00000000`00000124 00000000`00000000 fffffa80`08f72028 00000000`b424a000 : nt!KeBugCheckEx
fffff880`03090b10 fffff800`02ba0513 : 00000000`00000001 fffffa80`081192b0 00000000`00000000 fffffa80`08119300 : hal!HalBugCheckSystem+0x1e3
fffff880`03090b50 fffff800`030095c8 : 00000000`00000728 fffffa80`081192b0 fffff880`03090eb0 00000000`00000000 : nt!WheaReportHwError+0x263
fffff880`03090bb0 fffff800`03008f1a : fffffa80`081192b0 fffff880`03090eb0 fffffa80`081192b0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`03090d00 fffff800`02ffce8f : fffff880`03088180 00000000`00000001 fffff880`03090f30 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`03090d40 fffff800`02a8a7ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x47
fffff880`03090d70 fffff800`02a8a613 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`03090eb0 fffff800`02a89f85 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`030b09a0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x105


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: AuthenticAMD

IMAGE_NAME:  AuthenticAMD

DEBUG_FLR_IMAGE_TIMESTAMP:  0

IMAGE_VERSION:  

FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE

BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x124_authenticamd_processor_cache

FAILURE_ID_HASH:  {8bb1abe1-5cc5-4642-921b-5e3d4790100e}

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

Meany · 03 Jun 2014

I've updated to SP1 again, updated the OCZ firmware, updated the USB3 drivers, and removed 2 or the 4 Ram sticks. I have been stable for about 3 hours now. I will add back in the 2 RAM sticks tomorrow, and if it crashes again, I will upload another report.

Arc · 03 Jun 2014

OK, let us know how the troubleshooting goes.

Meany · 05 Jun 2014

RAM swapped out for the other 2 sticks as the first 2 BSOD, no crashes as of yet, but slight intermittent freezes, expecting it to do so soon.

Arc · 05 Jun 2014

I see that stop 0x124 is continuing.
Next:

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.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

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

Stress test the CPU.
Hardware - Stress Test With Prime95

Let us know the results.

Also fill up your system specs.
See your system specs and fill it up here.

Meany · 16 Jun 2014

No errors with memtest, furmark, or Prime95. Still bluescreening.

Arc · 16 Jun 2014

Good news about the hardware tests.

Now enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

Tip

If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.
_________________________________

Code:

BugCheck 3B, {c0000005, fffff80002f6d5dd, fffff880089ecda0, 0}

Probably caused by : ntkrnlmp.exe ( nt!ObInsertObjectEx+23d )

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

Meany · 22 Jun 2014

I've run the verifier, crashed the comp a few times, no logs I have found were left over if there were meant to be unique reports, but here's the collector report. Funnily enough the last BSOD was simply with vlc and mozilla open.

Arc · 22 Jun 2014

Unfortunately there is no crash dump after 16/06. So it is not possible to say anything about those crashes.

Can you take a camera snap of the next BSOD screen and upload it here, provided there is still no crash dump? If some info is available from the codes etc.