Computer keeps randomly Hard rebooting whilst playing games (and some programs)

nash_is_here · Feb 5, 2018

I just build my computer recently, i have Windows 10 OS, 16GB RAm, 7700K processor with water cooled, GTX 1070 and Asus Rog Maximum VII Hero motherboard, I build it from scratch to everything is about a month old. While I am playing game (i did not over clock the processor) my screen will freeze for 5 seconds and then the system will generate random window error and reboot. I have done a lot of troubleshooting like updating drivers, flashing BIOS to new version, updating windows, reinstalling clean install. I still have same issue, I have checked temperature and it is normal nothing is getting over heated, not sure what else can I do. please advise, FYI, all my hard is still under warranty since it was purchased 12/10/2017.
Thank you,
Nash

Hellfire13 · Feb 5, 2018

I just build my computer recently, i have Windows 10 OS, 16GB RAm, 7700K processor with water cooled, GTX 1070 and Asus Rog Maximum VII Hero motherboard

Are you sure about that board??? You should be on the IX Hero and not the VII Hero... https://www.asus.com/in/Motherboards/MAXIMUS_VII_HERO/
If that is not a typo, you might be on the wrong platform.

If the above is fine, then you need to check your PSU. It might not be able to generate enough on the 12v rail. You have not mentioned the unit, by the way. You can test with a substitute, if you got one laying around.

nash_is_here · Feb 5, 2018

https://www.newegg.com/Product/Product.aspx?Item=N82E16813132855

No i did not test PSU, I do not have one laying around. I have Thermaltake
https://www.newegg.com/Product/Product.aspx?Item=N82E16817153311

Hellfire13 · Feb 5, 2018

The board is fine if it has been BIOS updated for KabyLake support, which i am assuming you did.
The PSU is also very good... https://linustechtips.com/main/topic/631048-psu-tier-list-updated/

Did you check into EventViewer around the crash times. What does the critical events say during crash times???

nash_is_here · Feb 5, 2018

Hellfire13 :

I have checked event viewer and that to points to different things, I am not by the computer right now, but later in the evening I can provide the error report.

Hellfire13 · Feb 5, 2018

If it is doing this specifically during high loads, as you said gaming and stuff, then the usual suspect should be your PSU. It might be a faulty unit. You need to eliminate that point first. If the PSU is ok then it could be some other issue.

ko888 · Feb 5, 2018

It can be a faulty CPU.

Post the error messages.

nash_is_here · Feb 5, 2018

Hellfire13 :

This is the message i see in event viewer
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{6B3B8D23-FA8D-40B9-8DBD-B950333E2C52}
and APPID
{4839DDB7-58C2-48F5-8283-E1D1807D0D7D}
to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

nash_is_here · Feb 5, 2018

ko888 :

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{6B3B8D23-FA8D-40B9-8DBD-B950333E2C52}
and APPID
{4839DDB7-58C2-48F5-8283-E1D1807D0D7D}
to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

Hellfire13 · Feb 5, 2018

Are you sure about these messages being generated exactly at crash times???
If thats the case, one of the updates after your Windows installation might be screwing the system files. Or certainly looks like it.

ko888 · Feb 5, 2018

nash_is_here :

That DistributedCOM error doesn't cause reboots.

Look for other Error messages, maybe even Warning messages, that have a time stamp just before the reboots occurred.

nash_is_here · Feb 5, 2018

ko888 :

It just rebooted now, and here is what it says, multiple errors

1. The computer has rebooted from a bugcheck. The bugcheck was: 0x00000109 (0xa3a014e763ad24f1, 0xb3b7216db62b4d18, 0xfffff802bd6e655c, 0x0000000000000001). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 28c803c1-246f-4d7f-b5d7-9b27ae900780.

2. The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{6B3B8D23-FA8D-40B9-8DBD-B950333E2C52}
and APPID
{4839DDB7-58C2-48F5-8283-E1D1807D0D7D}
to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
3. The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{6B3B8D23-FA8D-40B9-8DBD-B950333E2C52}
and APPID
{4839DDB7-58C2-48F5-8283-E1D1807D0D7D}
to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
4. The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{6B3B8D23-FA8D-40B9-8DBD-B950333E2C52}
and APPID
{4839DDB7-58C2-48F5-8283-E1D1807D0D7D}
to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
5. The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{6B3B8D23-FA8D-40B9-8DBD-B950333E2C52}
and APPID
{4839DDB7-58C2-48F5-8283-E1D1807D0D7D}
to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

Number # was the last error before it reboots

nash_is_here · Feb 5, 2018

ko888 :

nash_is_here :

That DistributedCOM error doesn't cause reboots.

Look for other Error messages, maybe even Warning messages, that have a time stamp just before the reboots occurred.

I Mean #1 was the last error

andrebieller · Feb 5, 2018

I'm having the exact same issue, with pretty much the exact same error messages.

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xffff988338e2b4b8, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\WINDOWS\Minidump\020518-29171-01.dmp. Report Id: fbb8d085-d8c3-4e67-a22b-eee970166aa1

When I tried to open the dump file, Visual Studio says it can't debug older format dump files.

nash_is_here · Feb 6, 2018

andrebieller :

Try an app, called whocrashed that will analyze your dump files.
http://www.resplendence.com/whocrashed
that is what I used.

Hellfire13 · Feb 6, 2018

Looks more and more Windows to me.

Run SFC and DISM as per requirement... https://www.howtogeek.com/222532/how-to-repair-corrupted-windows-system-files-with-the-sfc-and-dism-commands/
Also run Driver Verifier to check Driver integrity.

ko888 · Feb 6, 2018

nash_is_here :

ko888 :

I Mean #1 was the last error

Bug check 0x00000109 is CRITICAL_STRUCTURE_CORRUPTION.

I had an i7-7700K do that to me back in July 2017. Problem got worse with time. Turned out to be a failing CPU.

andrebieller · Feb 6, 2018

Hellfire13 :

I ran SFC and it tells me I have no missing or corrupted files.

Also, my error is slightly different from the OP's, so I doubt it's what ko888 suggested for him. (Failing CPU)

Hellfire13 · Feb 6, 2018

Bugcheck runs commonly when the pc lacks enough integrity to run under safe operational environment. That can range from a host of issues.

andrebieller · Feb 6, 2018

Okay, so mine does still seem to be a hardware or driver error, but I can't seem to figure out which. I'll keep looking.

UPDATE: Upon further research, two possible culprits is that it could be either graphics card drivers, or weirdly enough, that the Fast Startup feature actually conflicts with some processors. I've updated drivers and turned off Fast Startup. Here's hoping.

Hellfire13 · Feb 6, 2018

do keep us updated

nash_is_here · Feb 6, 2018

I will try your suggestion hellfire13 about SFC, then Since all my items are under warranty, I have started started RMA process on RAM and PSU. if that does not fix the issue then I will RMA my processor and motherboard.

nash_is_here · Feb 6, 2018

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

nash_is_here · Feb 6, 2018

C:\WINDOWS\system32>DISM /Online /Cleanup-Image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.16299.20

Image Version: 10.0.16299.10

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

nash_is_here · Feb 6, 2018

ok this is what happened, driver verification first step when fine, after that I rebooted and windows came up but than the system kept on rebooting on window starting. I was finally able to log it off and get into safe mode and delete existing setting. so now it booted up fine. what should I try next? any suggestions.

And by the way I really want to thank hellfire13 and andrebieller for all the support

After all that i ran application whocrashed and this is what came up as common
On Tue 2/6/2018 6:44:55 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\020618-14187-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7A0945)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80131420945, 0xFFFFC80B58C86CD8, 0xFFFFC80B58C86520)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

Computer keeps randomly Hard rebooting whilst playing games (and some programs)

Prominent

Titan

Prominent

Titan

Prominent

Titan

Titan

Prominent

Prominent

Titan

Titan

Prominent

Prominent

Prominent

Prominent

Titan

Titan

Prominent

Titan

Prominent

Titan

Prominent

Prominent

Prominent

Prominent

Share this page