Random hard resets with no errors, pop-ups, or bsod.

Sanztrack · 04 Nov 2015

Hello!

I am usually pretty self sufficient when it comes to building/troubleshooting computers, but i am at a complete loss on this one. :/

So, I rebuilt a PC for a friend with a bunch of new parts and it started crashing about a week after he took it home (specs below). At first it was crashing ALL the time...playing games, watching twitch, anything. It would just randomly do a hard reset and restart normally without any sort of error codes, pop-ups, or even a bsod. I really mean random too, i desperately tried finding some consistency to the problem, but no luck on that.

Long story short, i have tested and swapped just about every part in this computer (except for the dvd drive). I have ran Memtest overnight on several occasions with no errors. I have checked and rechecked all bios settings and nothing is overclocked, memory timings are all dialed in correctly. Temperatures have not surpassed 55C on the CPU, and 70C is the max on the GPU. I have done a completely fresh reinstall of Windows 10 Pro 64-bit, and installed several different versions of drivers (and yes i cleaned out the old files after each uninstall). I unchecked that little box that auto restarts on system failure. I've read through several posts on stuff similar to this and tried different suggestions. Nothing. This was even happening with Windows 7 beforehand.

All of this, among other things i can't quite remember at the moment, have only slowed down the crashing to a minimum. After installing a new ssd and installing slightly older drivers, it seems to have cut down the crashing quite a bit. Right now it has reset twice in the past 24 hours, and it has only happened after exiting games, specifically BF4 and Garden Warfare.

I have checked the Event Viewer several times and three things pop out at me.

1) Kernal-Power (event id:41)
2) Whea-Logger (event id:20, AMD Northbridge)
3) bug-check (event id:1001)

It seems like it is trying to tell me there is a fatal error with the CPU...but i have pretty much ruled out every possible hardware issue there could be at this point, including lack of power and bad video cables.

i want to say it is a driver issue of some sort...but i am running a barebones OS right now with only the essentials running, and i have tried several different driver versions to no avail. I am totally dumbfounded and hopefully you guys could delve into my dmp files and help me out since i have no idea how. :P

Here's the specs, and i appreciate any help! Debugging files are attached.

Windows 10 Pro 64-bit
-AMD FX-8120
-Gigabyte 78LMT mATX mobo
-2x4GB G.Skill Ripjaw X 1600Mhz 9-9-9-24
-Corsair CX 600w Bronze
-MSI GeForce 960 2GB (355.58 driver installed, graphic and audio drivers ONLY)
-OCZ Trion 100 120GB SSD
-WD Blue 1TB 7200rpm HDD
-Enermax Ostrog case w/ several 140mm fans

I'm going to bed for now, ill check back tomorrow while I'm at work and provide any needed info. Thank you!

Sanztrack · 04 Nov 2015

Also, I just finished running BF4 for about 24 hours straight without it crashing, and Garden Warfare for about 8 hours straight without a crash...until i exited out of the game. THEN it crashed.

axe0 · 09 Nov 2015

Hi Sanztrack,

Welcome to the 10forums.

I'm very sorry for the delay, there aren't many people in this section.
Are you still requiring help?
If so, please use the tool again and upload a new zip file.

Sanztrack · 09 Nov 2015

Hi Axe, thanks for the reply. No worries on timing, I'm patient (:

Unfortunately, yes, i do still need help. Here are the updated files.

axe0 · 09 Nov 2015

A component didn't respond to the request of the CPU for the data.
The CPU never got the requested data due to the delay in the data, there was too much time out.
Please follow the instructions below for hardware troubleshooting as first step.

Code:

4: kd> !errrec ffffe000ca99f038
===============================================================================
Common Platform Error Record @ ffffe000ca99f038
-------------------------------------------------------------------------------
Record Id     : 01d116d1225f3a03
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 11/4/2015 7:19:26 (UTC)
Flags         : 0x00000002 PreviousError

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ ffffe000ca99f0b8
Section       @ ffffe000ca99f190
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   : 0x0000000000600f12
Processor ID  : 0x0000000000000000

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

Local APIC Id : 0x0000000000000000
CPU Id        : 12 0f 60 00 00 08 08 00 - 0b 22 98 1e 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  @ ffffe000ca99f250

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

Error         : BUSLG_GENERIC_ERR_*_TIMEOUT_ERR (Proc 0 Bank 4)
  Status      : 0xfe00000000070f0f
  Address     : 0x00000000fcffe104
  Misc.       : 0xc00a0fff01000000

The errors are 0x124 WHEA_UNCORRECTABLE_ERROR (Windows Hardware Error Architecture)
This means that there are problems with your hardware, but this error is also caused by overclocking, faulty drivers or BIOS problems.

STOP 0x124 Troubleshooting

Read carefully before proceeding.

Warning

If you're overclocking your system, revert back to stock clocks now.

Note

Test the system once the overclock is removed before continuing with the steps outlined below.

Part One: CPU Stress Test
Part Two: MemTest86+ RAM Diagnostic
Part Three: Hard Drive Diagnostics
Part Four: GPU Stress Test

ONE

CPU TEST

Run Prime95 to stress test your CPU. Prime95 - Stress Test Your CPU - Windows 10 Forums

Warning

Your CPU temperatures will rise quickly while under this stress test. Keep a keen eye on them and abort the test if overheating occurs.

TWO

RAM TEST

Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 10 Forums

Note

MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking forzero errors here. Even a single error will indicate RAM failure.

THREE

HDD TEST

Run SeaTools to check the integrity of your HDD. http://www.sevenforums.com/tutorials...s-how-use.html

Note

Do not run SeaTools on an SSD as the results will be invalid.

Run chkdsk http://www.sevenforums.com/tutorials...isk-check.html

FOUR

GPU TEST

Run Furmark to stress test your GPU. FurMark - GPU Stress Test - Windows 10 Forums

Note

Run Furmark for around 30 minutes.

Warning

Your GPU temperatures will rise quickly while Furmark is running. Keep a keen eye on them and abort the test if overheating occurs.

Sanztrack · 09 Nov 2015

Thank you Axe,

I will go through those tests again tonight and report back in the morning. Nothing is overclocked. If everything comes back clean, i will try and get the computer to crash and upload updated debug files as well.

Sanztrack · 11 Nov 2015

Ok, so i have run all above mentioned tests. No issues were reported with any of them.

Sanztrack · 11 Nov 2015

The computer just crashed again, here are the updated files.

axe0 · 12 Nov 2015

No record of new BSOD's
What kind of a crash was it?

BSOD Crash
Sudden restart/shutdown crash
Freeze crash

Sanztrack · 12 Nov 2015

Sorry for the really delayed responses, work is killing me...

Last night i came home and checked the event viewer. There was another Kernal-41 at 7:11PM, though i was not home to see it. Im assuming it had another hard reset, though i could be wrong. The computer was idling at the time.