The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000124 (0x0000000000000000, 0xffffe001ad9b05d8, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\Minidump\021715-15656-01.dmp. Report Id: 021715-15656-01.

My computer is rebooting and that's the error I'm getting in the event viewer. A link to the dump can be found below. Please help and thank you.

• Edited by Patrick K1 20 hours 23 minutes ago

Patrick

Sorry your link kicks off my malware alert.  Please put it somewhere else

Sorry about that. Try this: http://www.mediafire.com/download/fi286784aad2atm/021715-15656-01.dmp

Patrick

Better and no worries it happens

These are called BCC124 and are related to hardware.  Read how to diagnose and hopefully to fix them read this wiki

Since they refer to "authentic AMD" I would start by running a CPU stress test

Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Ken\Desktop\021715-15656-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at start of path element
WARNING: Whitespace at end of path element
Error: Empty Path.
Symbol search path is: 
SRV*e:\symbols*http://msdl.microsoft.com/download/symbols 
Executable search path is: 
Windows 8 Kernel Version 9600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9600.17328.amd64fre.winblue_r3.140827-1500
Machine Name:
Kernel base = 0xfffff802`cca1a000 PsLoadedModuleList = 0xfffff802`cccf0370
Debug session time: Tue Feb 17 08:37:15.708 2015 (UTC - 5:00)
System Uptime: 0 days 0:00:06.408
Loading Kernel Symbols
..

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

.............................................................
.......
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, ffffe001ad9b05d8, 0, 0}

Probably caused by : AuthenticAMD

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

0: 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: ffffe001ad9b05d8, 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:  WIN8_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre

STACK_TEXT:  
ffffd000`e116f500 fffff802`ccd9ffd0 : ffffd000`e5950180 ffffe001`ad9b05b0 fffff802`cccff800 fffff802`cca9a339 : nt!WheapCreateLiveTriageDump+0x81
ffffd000`e116fa30 fffff802`ccbde454 : ffffe001`ad9b05b0 ffffd000`e116fb50 fffff802`cccff8e0 ffffe001`ab557880 : nt!WheapCreateTriageDumpFromPreviousSession+0x44
ffffd000`e116fa60 fffff802`ccbdf271 : fffff802`cccff8e0 ffffd000`e116fb50 fffff802`cccff8e0 ffffd000`e116fb50 : nt!WheapProcessWorkQueueItem+0x48
ffffd000`e116faa0 fffff802`cca895e3 : fffff802`ccf2ed20 fffff802`ccbdf24c ffffc001`7f38d280 ffffe001`ab557880 : nt!WheapWorkQueueWorkerRoutine+0x25
ffffd000`e116fad0 fffff802`ccb18e70 : 00000000`00000000 ffffe001`ab557880 ffffe001`ab557880 ffffe001`ab4ac040 : nt!ExpWorkerThread+0x293
ffffd000`e116fb80 fffff802`ccb6f7c6 : fffff802`ccd1a180 ffffe001`ab557880 fffff802`ccd73a00 00000000`00000000 : nt!PspSystemThreadStartup+0x58
ffffd000`e116fbe0 00000000`00000000 : ffffd000`e1170000 ffffd000`e1169000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: AuthenticAMD

IMAGE_NAME:  AuthenticAMD

DEBUG_FLR_IMAGE_TIMESTAMP:  0

IMAGE_VERSION:  

FAILURE_BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_BUS_PRV

BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_BUS_PRV

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x124_authenticamd_processor_bus_prv

FAILURE_ID_HASH:  {6fd7875b-9a1b-9e09-d6d6-816026a875c8}

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