• Hi there and welcome to PC Help Forum (PCHF), a more effective way to get the Tech Support you need!
    We have Experts in all areas of Tech, including Malware Removal, Crash Fixing and BSOD's , Microsoft Windows, Computer DIY and PC Hardware, Networking, Gaming, Tablets and iPads, General and Specific Software Support and so much more.

    Why not Click Here To Sign Up and start enjoying great FREE Tech Support.

    This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Solved X99 Freezes and Restarts

Status
Not open for further replies.

TheDiagGuy

PCHF Member
Jul 28, 2019
123
6
36
Hello all,
Been a while since I've had to tap into your knowledge base. I've learned a lot from you guys and through much experience and trial and error I've been able to solve most of my computer building problems on my own so much so that I now do computer building for a living since I have to stay home with my son for "distance learning."

This issue is with my own personal gaming rig, and it's most frustrating because it's a bit of a one-off build on a x99 socket and I don't have a spare motherboard or processor for this socket to test and rule out components.

Specs are as follows:
Motherboard: Asus X99 Deluxe (LGA 2011 ver 3)
CPU: i7-5930k
CPU Cooler: Thermaltake Water3.0 (360mm)
RAM: G-Skill Ripjaws 4 2x8 GB 2800 MHz installed in slots A1 and C1 in dual channel. (I originally had 8 sticks of RGB RAM installed but in chasing this issue I installed known good RAM that is on the QVL list to rule this out)
GPU: Asus Turbo GTX 1070 Ti
Boot Drive: Samsung 950 Pro M.2 NVME SSD 512 GB
Storage: Seagate Barracuda 2 TB 7200 RPM HDD
PSU: Corsair RM1000 (I know that's a bit much, lol)
OS: Windows 10 Pro 64 Bit.

The issue: The computer will randomly freeze visual output for about 3-5 seconds, and restart the computer on it's own. No BSOD or error tones or messages. During the period of freezing, if there is audio playing, the audio will continue as normal even though the screen is frozen. As far as overclocking and XMP profiles go, it will do this with or without overclocking or XMP profiles. It can freeze after 3 minutes of usage or 3 hours, it's very random. I can be just idle on the desktop or in a full gaming experience, it doesn't seem to have a preference. One thing I tried was moving the SSD off of a 4x PCIE card onto the actal M.2 slot on the board (it's one of those weird vertical slots and I don't have the holder for it so, I prefer to have it on the card to avoid me accidentally damaging my system with my clumsy hands.) - same issue. I also tried reformatting as the OS used to be on a Ryzen system, and I've had problems in the past with Ryzen software and drivers causing problems for Intel systems, so I thought I'd give that a try. Also, as I stated before I used to be using 8 sticks of RGB RAM and swapped down to the RAM kit listed above. According to HW monitor, nothing is overheating, and physically nothing feels hot. I'm close to just swapping out the motherboard and processor for a Z390 and a i5-9600k, but I'd like to get this figured out before it comes to that.

Speccy for those of you who know what to do with it.

Thanks in advance gents!
 
Hello

I see HW monitor shows no over heating over all.. But how about sudden spikes in temps during those 3 to 5 seconds?

@Bruce
I would love to be able to answer that but the video is frozen during this time, I know that when the screen is frozen there are no spikes immediately beforehand. Also today while I was using it it would freeze for about three seconds and then resume as normal. It did this twice. I didn't expect it to start behaving in this way so I didn't have HW monitor running to see if it showed a spike on the max temps. I will make sure to have HW monitor running in the background to see if I can get some data if it survives the next freezing episode.
 
I realise it is a nice little exercise for a rainy weekend but to trouble-shoot it, I'd be stripping the rig down, cleaning everything and reassembling but leaving out all non-essential hardware like CD, extra HDDs, GPU etc.
I would then do a fresh install of Windows and reload only the core programs I need to run the PC.
see how that goes for a few days.
then gradually add hardware and software, one at a time, and seeing when the issue appears again.

the other alternative is to trail this and that and gamble on getting lucky early on.
not having access to some spare parts ties your hands a bit.

as to some background: how old is the rig, does it only occur during a certain program or series of events, anything helpful in the event logs, OS, BIOS, hardware firmware and drivers all up to date?
 
Thanks for the reply,

So history on this rig: About 2 months ago I switched this rig over from a Ryzen 5 2600x and a MSI X470 Gaming Pro and at the same time I also switched from a RM850 PSU to the RM1000 and switched to Kingston HyperX RGB RAM 8x8 GB at 3200 MHz which I had to run at 3000 MHz because that's all this motherboard supports with a 5th gen CPU. I never mentioned this RAM because it also misbehaves with the current RAM which is on the QVL list I have listed on the specs above. I also switched from a 500 GB m.2 SATA SSD for storage to the 2 TB HDD. I've had the GPU, the WiFi adapter, the water cooler, and all the fans in the setup for quite a while. The rig never acted up once before I started messing with it again, lol.

As far as drivers and firmware go, everything is up-to-date - I'm actually quite the stickler about this on every rig I put together. Reformatting is usually one of the first places I go to diagnose issues on a gaming rig just to rule that out since I do clean installs of Windows 10 multiple times a day and I can do it in my sleep lol.

As far as specific events go, there doesn't seem to be anything specific that causes it. I know that it seems to do it more often when I'm playing Warframe, but that's mostly all I do with this rig currently, so it makes sense it would act up then since that's how it spends most of it's life currently. However, after I did the last clean install of Windows I left the computer on overnight to install all my games (cause full games can be 100GB+ now...) When I checked on it in the morning all the installation windows were gone indicating the computer had restarted itself overnight. So it did it when I wasn't gaming there. Initially, the computer would do this once every like three days or so, and I set the CPU to stock clocks and it still continued to happen more frequently until it did it almost one minute after every start up. When I swapped out the RAM with the current kit and it didn't act up right away I thought I had cured it. Now it still does it, just not as frequently.

In other news, Nvidia just released a new driver package. I seem to remember just installing another new driver package just before this issue began. I'm going to run the unit with everything at base clocks (GPU CPU and RAM) with HW monitor open and play Warframe and see if it acts up.

As far as event viewer goes, I get the critical event ID 41 Task 63. Basically just means the computer restarted improperly due to holding the power button, a system hang or a power loss. I have 20 of these in the last four days which coincides with my random freezing/restarting issues.
The event data is identical on all 20 and is as follows:

BugcheckCode0

BugcheckParameter10x0

BugcheckParameter20x0

BugcheckParameter30x0

BugcheckParameter40x0

SleepInProgress0

PowerButtonTimestamp0

BootAppStatus0

Checkpoint0

ConnectedStandbyInProgressfalse

SystemSleepTransitionsToOn0

CsEntryScenarioInstanceId0

BugcheckInfoFromEFIfalse

CheckpointStatus0

CsEntryScenarioInstanceIdV20

LongPowerButtonPressDetectedfalse
 
I know double posting is frowned upon but I wanted to update you guys on this. I updated to Nvidia's newest driver package yesterday.
I was running Warframe again today with everything at stock clocks and HWMonitor running in the background and it froze again but it recovered and continued as normal. HWMonitor does not report anything overheating, in fact, I'm quite surprised how cool this machine runs on stock clocks. The event viewer does not report anything that coincides with this issue except for this error. This error however sets when there is nothing noticeably going wrong with the computer and it set five times in the hour before the actual freeze happened. However this particular one set at the same time that the last freeze and recovery happened. I'm still drawing a blank. Looking into getting another motherboard and processor, but will keep wrestling with this until then. By the way I have no idea what any of that error information means and google searches are quite vague :/


+System

-Provider
[ Name] Microsoft-Windows-AppModel-Runtime
[ Guid] {f1ef270a-0d32-4352-ba52-dbab41e1d859}

EventID65

Version0

Level2

Task0

Opcode0

Keywords0x2000000000000001

-TimeCreated
[ SystemTime] 2020-09-20T00:47:53.2897422Z

EventRecordID1670

Correlation

-Execution
[ ProcessID] 5980
[ ThreadID] 8308

ChannelMicrosoft-Windows-AppModel-Runtime/Admin

ComputerDESKTOP-4QF4FGL

-Security
[ UserID] S-1-5-21-4229754423-2071179631-3426880879-1001

-EventData

ErrorCode87

PackageFullNameWindows
 
there were certainly some major hardware changes, so logic would state that one or more of these are the root cause.
and there-in lies the needle in a hay stack problem.
dialing things back, one component at a time.
 
Update:
Having felt confident after a day of gaming that my issue was solved, I overclocked all my hardware and reinstalled my original RAM. Boy was my rig unhappy with that. It would barely run for a minute before it would restart on it's own. So today I tried a fresh install of windows on a brand new PCIE M.2 and removed my Samsung and have been running my game for about half a day now with full overclocking. Not confident that this is the problem, but I'm gonna keep running it until it either goes three days without an issue or restarts again and at that time I will be trying a GTX 980 I have laying around. Will keep you guys posted.
 
  • Like
Reactions: veeg
Yes, I'm not sure how but it seems to be that the issue was the Samsung 950 Pro 512 GB M.2. My system is working great on my Mushkin Helix 256 GB M.2.. Really odd failure... Any thoughts? Mind you the Samsung drive did the same thing before and after a clean install.
 
would point to the old m.2 SSD by the looks of things.
exactly what/why - heck, that's anyone's guess.

I seem to recall many 2.5" SSD's ago that I had something with the same outcome, weird shite happening, no logical explanation, changed the SSD, all good.

my uneducated guess is it's related to the NAND cells in the m.2 drive being faulty and Windows not being able to recover from whatever error they were reporting.
any chance you have SMART values for that dodgy drive?
 
  • Like
Reactions: veeg
Unfortunately only my internal hard drive gave me SMART Values.

Well either way mark this sucker solved. Going on a week with no issues.

Gonna try the suspect drive in another rig eventually and we'll see if it gives me the same issues - if it does, I'll chuck it :cry::cry:

Thanks for your help gents!
 
Status
Not open for further replies.