PC Randomly rebooting after waking from sleep mode

[Diltoid24]

Recently my computer's started to do this.. strange thing. After waking from sleep mode, it will sometimes, and there's no set time duration when it happens, freeze for a few seconds and then reboot. Such as this morning, the most recent event. I turned it on at around 4:30 am, then at around 5:15, I was opening up a firefox window when it froze and restarted, no prompt or warning. Last night, I experienced another restart event, but it took place hours after waking my computer from sleep. Has anyone heard of something like this happening? Currently running windows 10 with the most recent updates installed.


OS Name Microsoft Windows 10 Home
Version 10.0.15063 Build 15063
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name RIGALPHA-PC
System Manufacturer To Be Filled By O.E.M.
System Model To Be Filled By O.E.M.
System Type x64-based PC
System SKU To Be Filled By O.E.M.
Processor AMD FX(tm)-9370 Eight-Core Processor, 4400 Mhz, 4 Core(s), 8 Logical Processor(s)
BIOS Version/Date American Megatrends Inc. P1.50, 10/2/2013
SMBIOS Version 2.7
Embedded Controller Version 255.255
BIOS Mode Legacy
BaseBoard Manufacturer ASRock
BaseBoard Model Not Available
BaseBoard Name Base Board
Platform Role Desktop
Secure Boot State Unsupported
PCR7 Configuration Binding Not Possible
Windows Directory C:\WINDOWS
System Directory C:\WINDOWS\system32
Boot Device \Device\HarddiskVolume2
Locale United States
Hardware Abstraction Layer Version = "10.0.15063.0"
User Name RigAlpha-PC\RigAlpha
Time Zone Eastern Daylight Time
Installed Physical Memory (RAM) 16.0 GB
Total Physical Memory 16.0 GB
Available Physical Memory 11.1 GB
Total Virtual Memory 32.0 GB
Available Virtual Memory 26.5 GB
Page File Space 16.0 GB
Page File C:\pagefile.sys
Device Encryption Support Reasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and device is not InstantGo, Un-allowed DMA capable bus/device(s) detected, Disabled by policy, TPM is not usable
Hyper-V - VM Monitor Mode Extensions Yes
Hyper-V - Second Level Address Translation Extensions Yes
Hyper-V - Virtualization Enabled in Firmware Yes
Hyper-V - Data Execution Protection Yes

 

[phaelax]

I have no hard evidence or reason, just a hunch, but try running MemTest86 and see if they all pass.

 

[Diltoid24]

Ok, I just woke the thing up, went to food lion and came back to find it'd rebooted again. Now I went into the event viewer and noticed it does list the shutdowns. They're listed as a critical level event, warning that the system rebooted without a clean shutdown first, and could be caused if the system stopped responding, crashed or lost power. I scanned down the list and noticed another error with the source Kernel-Power. This one reads:

The system firmware has changed the processor's memory type range registers (MTRRs) across a sleep state transition (S4). This can result in reduced resume performance.

I scanned back through the past four or five days, looking through the events and just before each critical level shutdown, that error showed up.

 

[Diltoid24]

As for the results of MemTest86, it came back sat, all passed.