Jump to content
GreggHL

Computer had a sudden shut-off, twice in one day.

Recommended Posts

So I was playing Battletech on my computer when the screen went black and my computer restarted.  Later on, I was playing Rimworld- which as far as I know is less intensive on system resources- when it restarted again.  I've run a check on my ram using mdsched.exe and there were no errors according to that.  I'm wondering what caused the reboots, so I'm tossing that to this forum as the guy who built my computer recommended here.

 

I've also pasted the log below.

 

- System 
 
  - Provider 
 
   [ Name]  Microsoft-Windows-Kernel-Power 
   [ Guid]  {331C3B3A-2005-44C2-AC5E-77220C37D6B4} 
 
   EventID 41 
 
   Version 6 
 
   Level 1 
 
   Task 63 
 
   Opcode 0 
 
   Keywords 0x8000400000000002 
 
  - TimeCreated 
 
   [ SystemTime]  2018-05-08T12:50:20.503981800Z 
 
   EventRecordID 9759 
 
   Correlation 
 
  - Execution 
 
   [ ProcessID]  4 
   [ ThreadID]  8 
 
   Channel System 
 
   Computer DESKTOP-OTGD1NQ 
 
  - Security 
 
   [ UserID]  S-1-5-18 
 
 
- EventData 
 
  BugcheckCode 278 
  BugcheckParameter1 0xffff8a884986f010 
  BugcheckParameter2 0x0 
  BugcheckParameter3 0x0 
  BugcheckParameter4 0x0 
  SleepInProgress 0 
  PowerButtonTimestamp 0 
  BootAppStatus 0 
  Checkpoint 0 
  ConnectedStandbyInProgress false 
  SystemSleepTransitionsToOn 1 
  CsEntryScenarioInstanceId 0 
  BugcheckInfoFromEFI true 
  CheckpointStatus 0 
 
Level Date and Time Source Event ID Task Category
Critical 5/8/2018 9:50:20 PM Microsoft-Windows-Kernel-Power 41 (63) The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
 
- <System>
  <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" /> 
  <EventID>41</EventID> 
  <Version>6</Version> 
  <Level>1</Level> 
  <Task>63</Task> 
  <Opcode>0</Opcode> 
  <Keywords>0x8000400000000002</Keywords> 
  <TimeCreated SystemTime="2018-05-08T06:39:26.606425500Z" /> 
  <EventRecordID>9684</EventRecordID> 
  <Correlation /> 
  <Execution ProcessID="4" ThreadID="8" /> 
  <Channel>System</Channel> 
  <Computer>DESKTOP-OTGD1NQ</Computer> 
  <Security UserID="S-1-5-18" /> 
  </System>
- <EventData>
  <Data Name="BugcheckCode">278</Data> 
  <Data Name="BugcheckParameter1">0xffffb7833f3fc010</Data> 
  <Data Name="BugcheckParameter2">0x0</Data> 
  <Data Name="BugcheckParameter3">0x0</Data> 
  <Data Name="BugcheckParameter4">0x0</Data> 
  <Data Name="SleepInProgress">0</Data> 
  <Data Name="PowerButtonTimestamp">0</Data> 
  <Data Name="BootAppStatus">0</Data> 
  <Data Name="Checkpoint">0</Data> 
  <Data Name="ConnectedStandbyInProgress">false</Data> 
  <Data Name="SystemSleepTransitionsToOn">2</Data> 
  <Data Name="CsEntryScenarioInstanceId">0</Data> 
  <Data Name="BugcheckInfoFromEFI">true</Data> 
  <Data Name="CheckpointStatus">0</Data> 
  </EventData>
  </Event>
 
Adding System information: 
OS Name Microsoft Windows 10 Pro
Version 10.0.16299 Build 16299
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name DESKTOP-OTGD1NQ
System Manufacturer MSI
System Model MS-7A69
System Type x64-based PC
System SKU Default string
Processor Intel® Core i7-7700 CPU @ 3.60GHz, 3600 Mhz, 4 Core(s), 8 Logical Processor(s)
BIOS Version/Date American Megatrends Inc. 2.20, 4/6/2017
SMBIOS Version 3.0
Embedded Controller Version 255.255
BIOS Mode UEFI
BaseBoard Manufacturer MSI
BaseBoard Model Not Available
BaseBoard Name Base Board
Platform Role Desktop
Secure Boot State Off
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.16299.371"
User Name DESKTOP-OTGD1NQ\Gregg
Time Zone Korea Standard Time
Installed Physical Memory (RAM) 16.0 GB
Total Physical Memory 16.0 GB
Available Physical Memory 12.0 GB
Total Virtual Memory 18.3 GB
Available Virtual Memory 13.9 GB
Page File Space 2.38 GB
Page File C:\pagefile.sys
Virtualization-based security Not enabled
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, 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
 
I also had another shutoff event.  Here's the log:
 
- System
    - Provider
      [ Name] Microsoft-Windows-Kernel-Power       [ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}
      EventID 41       Version 6       Level 1       Task 63       Opcode 0       Keywords 0x8000400000000002     - TimeCreated
      [ SystemTime] 2018-05-08T12:50:20.503981800Z
      EventRecordID 9759       Correlation     - Execution
      [ ProcessID] 4       [ ThreadID] 8
      Channel System       Computer DESKTOP-OTGD1NQ     - Security
      [ UserID] S-1-5-18
- EventData
    BugcheckCode 278     BugcheckParameter1 0xffff8a884986f010     BugcheckParameter2 0x0     BugcheckParameter3 0x0     BugcheckParameter4 0x0     SleepInProgress 0     PowerButtonTimestamp 0     BootAppStatus 0     Checkpoint 0     ConnectedStandbyInProgress false     SystemSleepTransitionsToOn 1     CsEntryScenarioInstanceId 0     BugcheckInfoFromEFI true     CheckpointStatus 0
Edited by GreggHL

Share this post


Link to post
Share on other sites

Can you list your system hardware specs,.. 

 

Bugcheck 278,..  indicates that an attempt to reset the display driver and recover from a timeout failed.

 

Perhaps, updating the video driver, downgrade the driver (if the latest doesn't work), or remove and reinstall the current driver.

 

Update the firmware, downgrade the firmware (if the latest doesn't work). Ensure you're using the latest BIOS for your motherboard as well. If your overclocking anything, stop doing so.

Edited by Braegnok

Share this post


Link to post
Share on other sites

Those errors may or may not be your problem, however 90% of the time it's hardware related, either a faulty psu or overheating seem to be the main reasons.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×