*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa80098ee518, 0, 0}
Probably caused by : AuthenticAMD
Followup: MachineOwner
Go to Start and type in sysdm.cpl and press Enter
Click on the Advanced tab
Click on the Startup and Recovery Settings button
Ensure that Automatically restart is unchecked
Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump << where your .dmp files can be
found later.
Click OK twice to exit the dialogs, then reboot for the changes to take effect.
HOW TO USE PRIME95 EFFECTIVELY
First, install the program as you would any other. Next, run it, and go to the ‘Advanced’ tab – select ‘Password’. Type in the password 9876 and enter it. Now go back to the ‘Advanced’ tab, and select ‘Priority’. Set the priority level to 10.
This effectively gives all of your system resources to Prime95 when it is running – now any processes running hidden in the background won’t be able to steal work time from Prime95, ensuring the most effective stress test possible.
At the very bottom of this post, a picture has been uploaded to further clarify Priority Ten setup for Prime95.
When you want to stress test your processor, run Prime95, go to the ‘Options’ tab, and select ‘Torture Test’. Run the Torture test at the default settings.
Make sure that you have turned off any screensavers, and closed all other applications when Prime95 is running.
Prime95 should never be run in tandem with any other stress testing programs, period. Prime95 is known and proven to be most effective when run by itself, and is less thorough when used with something else running at the same time. If you use Motherboard Monitor Five to monitor your temperatures, you should turn the interval time way down – 60 seconds is appropriate.
If you have an Intel processor with Hyper Threading, you need to run two instances of Prime95 for complete effectiveness. This is proven fact; in that two instances of Prime95 will catch instability that one instance won’t, on an Intel machine with HT. In order to run two instances simultaneously, simply install a second copy of Prime95 in a different folder, and run it in tandem with your original. Priority ten should be used for both instances of Prime95 in this case.
When you are stability testing with Prime95, you want to run the Torture Test for at least 24 hours. Why 24 hours?
There is a very common misconception that if your machine can pass Prime95 stability testing for, say, four hours, your machine will be able to run stable, regardless of what you are doing, for four hours as well, without issue. This is simply not the case.
Prime95 often finds errors in its 16th - 20th hour of testing, a potential for instability that wasn’t found after only four hours of testing. After only four hours of Prime95, the potentialfor instability still exists. 24 hours is widely viewed as a sufficient time period to catch any instability that may be present, but by all means test longer if you are able.
If 24 hours seems like an extraordinarily long time to leave your computer on, keeping your machine unusable because of the processes it’s doing, try running Prime95 overnight, and then through to all day while you’re at school or work.
For CPU specific testing, a Large FFT Prime95 test is an alternative to the more "system-stress" oriented Blend test that runs by default. The choice is ultimately up to the end user - the Blend test is reccomended in these guidelines because of it's qualities as both a processor and system stress test.
That’s all there is to Prime95 – 24 hours of Prime95 at Priority ten is "certified stable", and ready to rock for 24/7 use.
===============================================================================
Common Platform Error Record @ fffffa800848c8f8
-------------------------------------------------------------------------------
Record Id : 01cf8b0dd89cbcad
Severity : Fatal (1)
Length : 928
Creator : Microsoft
Notify Type : Machine Check Exception
Timestamp : 6/18/2014 15:56:29 (UTC)
Flags : 0x00000002 PreviousError
===============================================================================
Section 0 : Processor Generic
-------------------------------------------------------------------------------
Descriptor @ fffffa800848c978
Section @ fffffa800848ca50
Offset : 344
Length : 192
Flags : 0x00000001 Primary
Severity : Fatal
Proc. Type : x86/x64
Instr. Set : x64
Error Type : Cache error
Operation : Generic
Flags : 0x00
Level : 3
CPU Version : 0x0000000000600f20
Processor ID : 0x0000000000000000
===============================================================================
Section 1 : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor @ fffffa800848c9c0
Section @ fffffa800848cb10
Offset : 536
Length : 128
Flags : 0x00000000
Severity : Fatal
Local APIC Id : 0x0000000000000000
CPU Id : 20 0f 60 00 00 08 06 00 - 0b 32 98 3e 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 @ fffffa800848cb10
===============================================================================
Section 2 : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor @ fffffa800848ca08
Section @ fffffa800848cb90
Offset : 664
Length : 264
Flags : 0x00000000
Severity : Fatal
Error : DCACHELG_WR_ERR (Proc 0 Bank 4)
Status : 0xf300000200190127
After looking at the error info in parameter 2, most certainly this is related to the processor. Check that your CPU's fan is running correctly, remove and re-seat the processor, and see if that helps.
Code:=============================================================================== Common Platform Error Record @ fffffa800848c8f8 ------------------------------------------------------------------------------- Record Id : 01cf8b0dd89cbcad Severity : Fatal (1) Length : 928 Creator : Microsoft Notify Type : Machine Check Exception Timestamp : 6/18/2014 15:56:29 (UTC) Flags : 0x00000002 PreviousError =============================================================================== Section 0 : Processor Generic ------------------------------------------------------------------------------- Descriptor @ fffffa800848c978 Section @ fffffa800848ca50 Offset : 344 Length : 192 Flags : 0x00000001 Primary Severity : Fatal Proc. Type : x86/x64 Instr. Set : x64 Error Type : Cache error Operation : Generic Flags : 0x00 Level : 3 CPU Version : 0x0000000000600f20 Processor ID : 0x0000000000000000 =============================================================================== Section 1 : x86/x64 Processor Specific ------------------------------------------------------------------------------- Descriptor @ fffffa800848c9c0 Section @ fffffa800848cb10 Offset : 536 Length : 128 Flags : 0x00000000 Severity : Fatal Local APIC Id : 0x0000000000000000 CPU Id : 20 0f 60 00 00 08 06 00 - 0b 32 98 3e 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 @ fffffa800848cb10 =============================================================================== Section 2 : x86/x64 MCA ------------------------------------------------------------------------------- Descriptor @ fffffa800848ca08 Section @ fffffa800848cb90 Offset : 664 Length : 264 Flags : 0x00000000 Severity : Fatal Error : DCACHELG_WR_ERR (Proc 0 Bank 4) Status : 0xf300000200190127
I strongly suggest you don't do that as it may invalidate the warranty.I would remove and reseat the processor, believe it or not it may be that simple...