Computer shuts off randomly after installing Windows 10

Toggle sidebar Toggle sidebar
O

oHAMBURGLARo

Reputable
Jun 2, 2015
13
0
4,510
I wasn't sure where to put this, as I'm not sure whether I have a problem with my PSU, Windows 10, or system in general. Since upgrading to Windows 10, I have noticed that when I leave my computer on for a while and come back after hours have gone by, the computer has crashed and turned off. I thought it might be hibernating or something, but it appears that it is actually completely crashing.

According to PC Part Picker, my system draws a maximum of 462 Watts, although I am not sure how accurate this is. I have an EVGA SuperNOVA NEX 650W 80+ Gold Certified Fully-Modular ATX Power Supply, so I should have enough. I do not have anything overclocked. You can see my system here

What could be the problem?
 
Sort by date Sort by votes
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
-if it is crashing there should be a memory dump in c:\windows\minidump directory, you can put these on a server like microsoft onedrive, mark the public and post a link. Someone can take a quick look with a debugger.
-it is normal for windows to start sleep after 15 mins, then hibernate after 4 hours.
depending on what your settings are for power management.
 
Upvote 0 Downvote
O

oHAMBURGLARo

Reputable
Jun 2, 2015
13
0
4,510


Under the power settings, I have my computer to turn off the display after 10 minutes, sleep after 2 hours, and never hibernate. I do not have a C:\Windows\Minidump directory. I do have a Minidump directory in C:\Windows.old\Windows which I believe is from Windows 8 before I upgraded to Windows 10.

Hardware specs are in the link posted in the original message.
 
Upvote 0 Downvote
X

xeonight

Honorable
Nov 1, 2013
121
0
10,760
have you looked in the Event Viewer for information around the time of the power off/crash?

usually if it's hardware causing a hard reboot/shutdown, the event viewer will say something like "The previous shut down at xx:xx was unexpected"
 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
start cmd.exe as an admin then type the following commands
cd c:\
dir /s *.dmp

this will search for memory dump files, sometimes if windows makes a live dump for diagnostics it will put it in a different directory so it will be uploaded to microsoft for debugging and so a fix will be pushed out to your machine.

Last time I looked at this on someones machine it was caused from certain USB chips on the motherboard that required specific usb drivers. Windows made a live kernel memory dump because the USB controller stopped responding and the machine was rebooted to get it to function again. Root cause was they system needed to update the BIOS and update the chip driver. Too bad there was no BIOS update or driver update for the machine. We ended turning off the USB 3.0 host controller via BIOS just to prevent the machine reboots every day. I did not figure out the problem until we searched the system for .dmp files and took a look at one being sent to microsoft.

 
Upvote 0 Downvote
O

oHAMBURGLARo

Reputable
Jun 2, 2015
13
0
4,510


It happened again last night/early this morning. It seems I have a TON of things that have been going on in Event Viewer. I don't really know much about this stuff, but it doesn't seem good. Here is a screenshot of the summary of the number of events.

SX8jnzE.png


I found a "Kernel-Power" listing that may have information about what lead to the latest crash. Here are the details:

XML: 
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" ></Provider> 
  <EventID>41</EventID> 
  <Version>3</Version> 
  <Level>1</Level> 
  <Task>63</Task> 
  <Opcode>0</Opcode> 
  <Keywords>0x8000200000000002</Keywords> 
  <TimeCreated SystemTime="2015-10-02T07:29:51.924017600Z" ></TimeCreated> 
  <EventRecordID>2840</EventRecordID> 
  <Correlation ></Correlation> 
  <Execution ProcessID="4" ThreadID="8" ></Execution> 
  <Channel>System</Channel> 
  <Computer>brendan-desktop</Computer> 
  <Security UserID="S-1-5-18" ></Security> 
  </System>
- <EventData>
  <Data Name="BugcheckCode">0</Data> 
  <Data Name="BugcheckParameter1">0x0</Data> 
  <Data Name="BugcheckParameter2">0x0</Data> 
  <Data Name="BugcheckParameter3">0x0</Data> 
  <Data Name="BugcheckParameter4">0x0</Data> 
  <Data Name="SleepInProgress">4</Data> 
  <Data Name="PowerButtonTimestamp">0</Data> 
  <Data Name="BootAppStatus">0</Data> 
  </EventData>
  </Event>
 
Upvote 0 Downvote
Y

yodachoda

Reputable
Feb 26, 2015
65
0
4,630


I'm not sure if this applies to your issue but here's what happened to me:

For 100% certain, Windows 10 caused my PC to freeze during gaming randomly and sometimes the PC would restart on its own a few seconds after freezing.

This started happening after updating to windows 10 from 8.1 and completely stopped after I reverted back to Windows 8.1.
 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
the kernal power log entry will not be useful in this case.
either your power failed or you have a problem saving a memory dump.

you will want to google "how to force a memory dump using a keyboard"
make the registry settings, and force a memory dump. produce a memory dump while your system is running ok, put it on a server like microsoft onedrive, mark the dump for public access and post a link.

you might also: make sure your main power is plugged into a electrial wall outlet rather than a surge protector, sometimes power strips have problems.
make sure you update your motherboard chipset drivers for your sata controller.

you should also confirm that your system does not have a windows live dump on your drive (scan drive for .dmp files)
 
Upvote 0 Downvote
G

GarthVader152

Reputable
Dec 2, 2015
1
0
4,510



This is what I got after following your direction with the command prompt. I've been having the same issue with random complete shutdowns with no notification. Seemed to start after I installed the very large November Windows 10 update to build 10586. I have HW Monitor and I haven't seen any abnormal temps, either.


Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.

C:\Users\GarthVader>cd c:\

c:\>dir /s *.dmp
Volume in drive C has no label.
Volume Serial Number is 5CAA-239A

Directory of c:\ProgramData\Microsoft\WDF

08/31/2015 05:53 PM 131,896 DriverManager_1612.dmp
09/22/2015 03:28 PM 116,400 DriverManager_1760.dmp
2 File(s) 248,296 bytes

Directory of c:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_Explorer.EXE_12a53f408a4c4482eeb261651dfa88fa560fa16_43dcc54e_cab_1da0b2d1

12/02/2015 10:53 AM 612,336 triagedump.dmp
1 File(s) 612,336 bytes

Directory of c:\Users\All Users\Microsoft\WDF

08/31/2015 05:53 PM 131,896 DriverManager_1612.dmp
09/22/2015 03:28 PM 116,400 DriverManager_1760.dmp
2 File(s) 248,296 bytes

Directory of c:\Users\All Users\Microsoft\Windows\WER\ReportQueue\AppCrash_Explorer.EXE_12a53f408a4c4482eeb261651dfa88fa560fa16_43dcc54e_cab_1da0b2d1

12/02/2015 10:53 AM 612,336 triagedump.dmp
1 File(s) 612,336 bytes

Directory of c:\Users\GarthVader\AppData\Roaming\Mozilla\Firefox\Crash Reports\pending

04/08/2012 04:15 PM 76,544 00e338a2-8120-4f4a-98e8-1dfe2bcb9ffe.dmp
06/02/2014 04:13 PM 208,756 896b57c1-865a-42d8-b29e-f381f86104b8-browser.dmp
06/02/2014 04:13 PM 38,515 896b57c1-865a-42d8-b29e-f381f86104b8-flash1.dmp
06/02/2014 04:13 PM 64,905 896b57c1-865a-42d8-b29e-f381f86104b8-flash2.dmp
06/02/2014 04:13 PM 52,521 896b57c1-865a-42d8-b29e-f381f86104b8.dmp
02/28/2015 10:14 PM 60,061 a9cee23f-7853-44bb-9acb-a275d769b64d.dmp
04/23/2014 07:20 PM 20,418 dee0ae53-1047-4d51-8c38-c7b3880c18a8.dmp
03/17/2015 08:05 PM 280,165 e1fe5dc9-c22b-41ac-a0f4-5cfe66ff65f3-browser.dmp
03/17/2015 08:05 PM 38,781 e1fe5dc9-c22b-41ac-a0f4-5cfe66ff65f3-flash1.dmp
03/17/2015 08:05 PM 88,247 e1fe5dc9-c22b-41ac-a0f4-5cfe66ff65f3-flash2.dmp
03/17/2015 08:05 PM 52,631 e1fe5dc9-c22b-41ac-a0f4-5cfe66ff65f3.dmp
11 File(s) 981,544 bytes

Directory of c:\Users\GarthVader\AppData\Roaming\Mozilla\Firefox\Profiles\zmqu1q35.default\minidumps

01/07/2014 04:28 PM 0 0b50580f-3785-4e88-a9e7-7c27e1a5f3a0.dmp
09/17/2012 07:52 PM 0 0b685356-b3fd-4d73-9015-04ce6098f713.dmp
06/05/2013 10:16 AM 0 130ae1f0-8652-43f6-8ff3-eb7e885c16dd.dmp
09/13/2012 10:57 PM 0 1c053d51-8d70-4799-bd00-9208652be1cc.dmp
06/24/2012 04:50 PM 21,412 218965a2-b86a-4df2-bb7f-d71d491c48e5.dmp
01/03/2014 05:26 PM 0 38df2f32-a22f-474d-8b3a-e119a4b7a41d.dmp
05/03/2014 11:47 AM 0 4907c857-6259-48ef-8f14-9b82fab31ed1.dmp
03/12/2014 02:20 AM 0 603e8a80-50ec-45bc-b920-7f37db7e8dda.dmp
04/04/2014 10:58 AM 0 64cf48e2-3800-4eaa-bcd2-b252b2091f02.dmp
02/13/2014 09:26 PM 0 90b6553a-27cc-4276-acaa-354e1781b388.dmp
01/10/2014 07:23 AM 0 ada71067-5790-4170-857a-9347e4da0427.dmp
01/08/2014 03:42 PM 0 b237ffb9-341f-428d-a59d-f89aa79436de.dmp
01/06/2014 12:59 PM 0 ba16d6ab-d79f-442d-aa14-e979743936d7.dmp
09/23/2012 02:16 AM 0 ce89436c-eeaf-42e3-a4c9-8a1f0ed21870.dmp
05/02/2014 02:16 AM 27,594 e07d88ca-cd40-4ca4-af2a-789f890ee1c7.dmp
04/17/2014 08:54 PM 0 e6e164a5-16b5-4457-944d-7416adec0701.dmp
03/24/2014 06:37 PM 0 eb100913-f27d-4e96-adb5-38d6c862d1f1.dmp
09/23/2012 02:16 AM 26,756 f982da9e-0d21-4d7b-859a-6b8be7040a9c.dmp
18 File(s) 75,762 bytes

Directory of c:\Users\Noy\AppData\Roaming\Mozilla\Firefox\Crash Reports\pending

02/26/2012 12:47 PM 79,304 3e606971-9c8e-4742-96fa-ccb4c76a9136.dmp
02/26/2012 12:47 PM 136,803 5afa9a62-c87c-487d-bcae-80f77fc93d97.dmp
04/14/2012 10:05 AM 84,945 999095cf-2599-45de-91f1-047d9dd486f7.dmp
04/14/2012 10:05 AM 155,451 be8639cc-11d9-4555-8526-b875cf7eaaed.dmp
4 File(s) 456,503 bytes

Directory of c:\Users\Pzarks24\AppData\Local\CrashDumps

01/12/2012 03:36 PM 534,795 LifeFrame.exe.3708.dmp
01/12/2012 03:35 PM 534,795 LifeFrame.exe.4248.dmp
01/12/2012 03:37 PM 534,795 LifeFrame.exe.4900.dmp
01/18/2012 09:21 PM 24,566,045 Skype.exe.3080.dmp
4 File(s) 26,170,430 bytes

Directory of c:\Windows.old\Users\All Users\Microsoft\WDF

08/31/2015 05:53 PM 131,896 DriverManager_1612.dmp
09/22/2015 03:28 PM 116,400 DriverManager_1760.dmp
2 File(s) 248,296 bytes

Directory of c:\Windows.old\Users\All Users\Microsoft\Windows\WER\ReportQueue\AppCrash_Explorer.EXE_12a53f408a4c4482eeb261651dfa88fa560fa16_43dcc54e_cab_1da0b2d1

12/02/2015 10:53 AM 612,336 triagedump.dmp
1 File(s) 612,336 bytes

Total Files Listed:
46 File(s) 30,266,135 bytes
0 Dir(s) 447,439,421,440 bytes free

c:\>
 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
sometimes when a system is automatically debugged it will be rebooted after the debug session is over. this does not leave a log entry or a default memory dump. It seams rude to me but I understand, I have looked at some of the debug traces and the hardware was "confused" and the only way to reset it was to reboot until it happens again. (or get you to install a BIOS update that may or may not exist and microsoft does not have the ability to install for you anyway) Newer machines like the surface can update the BIOS for you.

put the triagedump.dmp
and the most current DriverManager*.dmp
on a server, these should be debug sessions of automated debugging that was reported to microsoft.
often they will indicate what is wrong. Microsoft then tries to push out a solution but might not if it is a hardware problem that requires a BIOS update or a special driver that they don't have rights to distribute.
(certain chips have known bugs in the chips and require custom to workaround the problems)



 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom