Windows 10: Windows 10 random reboot issue

For the past 3+ months, my machine has been randomly rebooting. There's no BSOD, it just switches to a black screen and then shows the Windows 10 loading icon. It will happen at different times of day but, has never happened more than once in a day. It doesn't seem to be related to the load as I can be doing anything from editing a TXT file or running a game.

Windows / system drivers / BIOS are all up to date. Ran a memory test a few times and had no issues. Bought/installed a new power supply (Seasonic FOCUS Gold - 750w). I'm not seeing anything relevant in the Event Viewer. Power scheme is at 'High Performance'.

Specs:
Windows 10 Home 64-bit
CPU - AMD A10-6700
Motherboard - MSI 2AE0
Graphics - NVIDIA GeForce GTX 780
RAM - 10.0GB Dual-Channel DDR3
-- Patriot Memory DDR3 1024 MBytes (x2)
-- Micron Technology DDR3 4096 MBytes (x2)


I've has this RAM setup for the last 3+ years. The issue didn't turn up until a few months ago. That said, I've been playing with some different RAM configurations and I'm still having issues. With only the 2 Patriot sticks installed, my computer would turn on but, my monitor wouldn't get any signal. Double checked the monitor connection, graphics card and even held down the power button for 30 seconds.

So I took out one of the Patriot sticks and added a Micron stick. This was okay about a day, before it rebooted unexpectedly, again.

Then, I took the other Patriot stick out and put both Micron sticks in there. I thought it was resolved at this point because I went through about 3 days of heavy use with no reboots. Until this morning. Shortly after I turned my machine on and signed in, I opened a few tabs in Chrome and boom, reboot.

I'm at a loss. I've run a few memory tests and no problems were found.


Both SpeedFan & Open Hardware Monitor show the CPU at about 104F.

:)

 

Windows 10 random reboot issue

RAM was worth a try anyway... Windows 10 has been running fine on this machine for almost a year now, and this PC setup has been very faithful and reliable for many years, so I won't feel too bad about replacing it with a new machine.. I appreciate all
of the advice and help,...!!

 

Windows 10 random reboot issue

So we're thinking it may be a RAM issue? Should I start thinking about replacing it now? The requested msinfo32 file can be found here

onedrive msinfo32

Thanks for the help.....

 

Try using the same brand of RAM. Although different brands having the same specs but if the timing is a little off then you'll have this problem. That's why even the same brand of RAM is being sold in pair.

In addition, check your MB manual if the RAM used is in the compatible list.

 

I'll look into this. Any idea why the RAM would've just recently started having problems? Also, if this was the case, why did I still have reboot issues when I had just the 2 Micron sticks in?

 

Change in temperature can also cause the problem. That's why when running Memtest, you'll need to run for at least 10 passes. The first few passed may succeed then fail later on.

 

Change in RAM temperature? Do you have info on running multiple passes in Memtest?

 

I,recommend testing with the following. it will find memory errors that MemTest86+ won't sometimes

Stress Test Your CPU - Prime 95
Prime95 - Stress Test Your CPU Windows 10 Tutorials
Select the Blended Test
test for approx 3 hrs and abort testing as needed for freezing, high temp changes, etc

 

I work for a major supplier and this may be an issue that we and AMD have been working on for a while. It can never be duplicated in test environments and has been impossible to isolate. It seems to have occurred with Win 10 some before but much much more after the latest RS3 update. It affects all Carrizo and Bristol Ridge AMD, not Ryzen the latest. It seems to be fixed by setting a machine register bit in bios. It is MSR register C001_0015 bit 3.
set MSRC001_0015 Hardware Configuration (HWCR) Bit 3 TlbCacheDis to 1 to all cores
You could use RWeverything to check that bit on your machine. If it is not set then try and get a new bios that has it set.
Did you upgrade to RS3?
Many users that have been seeing this are reported that it is fixed with the new bios.
Also, check system event log for WHEA errors. AMD northbridge. If you have those then you are seeing this issue,

 

Thanks for this info. I have an AMD A10-6700. How do I check if it's Carrizo or Bristol Ridge?

Also, my motherboard is MSI 2AE0 and I should have the latest BIOS (80.35), according to MSI.

I've yet to see anything relevant in Event Viewer but, I can check again. What is an "WHEA error"?

 

Another update. It hasn't rebooted in a couple days but, did again this morning. I had about 4-5 tabs in Chrome open and Notepad++, at the time.

Again, this doesn't seem temperature or memory related. As a test, I spent the rest of the afternoon doing some resource intensive tasks (Photoshop editing, playing a game, installing Avast & running a full system scan, approx 10 Chrome tabs open, etc) and did not have another reboot. Everything is running as normal.

One thing I've noticed (and this may not be relevant) is that when looking at the Event Viewer logs, the time stamps seem off when this happens. For today example:

- There's a kernel-general (12) event @ 11:04 AM (The operating system started at system time ‎2018‎-‎03‎-‎28T18:04:32.491512700Z.)
- Immediately following that, there's an Error (6008) @ 11:05 AM (The previous system shutdown at 10:25:23 AM on ‎3/‎28/‎2018 was unexpected.)

But in the log, the event immediately before the kernel-general event is @ 9:11 AM. So, no events appear to be registered for about 2 hours. This seems to be the case every time I have one of these reboots.

The events immediately before this kernal-general event are both Service Control Manager (7040) events.
- 9:11 AM (The start type of the Background Intelligent Transfer Service service was changed from auto start to demand start.)
- 9:08 AM (The start type of the Background Intelligent Transfer Service service was changed from demand start to auto start.)

This also seems to be the case every time.

 

Code: Background Intelligent Transfer Service service[/quote] It looks like it was restarted due to a Windows update.