0

For past two days the system would hang up or enter black screen and won't restart right away (after pressing restart button) but at one instant it generated Blue Screen (BugCheck Code 278).

This issue has been occurring only during gaming(for one game during loading screen for other mid game or at loading screen) and at one instant during browsing on moving cursor on video thumbnail.

The only updates that were installed during this period

Definition Update for Microsoft Security Essentials - KB2310138 (Definition 1.269.141.0)

Definition Update for Microsoft Security Essentials - KB2310138 (Definition 1.269.141.0)2times!

Definition Update for Microsoft Security Essentials - KB2310138 (Definition 1.269.145.0)

Definition Update for Microsoft Security Essentials - KB2310138 (Definition 1.269.146.0)

Definition Update for Microsoft Security Essentials - KB2310138 (Definition 1.269.146.0)2times!

Strangely Definition Update for Microsoft Security Essentials - KB2310138 (Definition 1.269.148.0) was not shown under installed updates even after updating MSE to it and restarting system.

At that moment Graphics driver version Nvidia 388.31 was installed which has been working fine before, since then installed latest version 397.93 which gave similar issues.

After which uninstalled MSE gave similar issues. Since then reinstalled MSE and the updates now installed are.

Definition Update for Windows Defender - KB915597 (Definition 1.269.58.0) Definition Update for Microsoft Security Essentials - KB2310138 (Definition 1.269.148.0)

Also ran an sfc /scannow

Restore point also got deleted today and drive protection for system drive was turned off. Yesterday received a message that Shadow Storage Size not available.

System Info:
Windows 7 Ultimate (Service Pack 1) 64bit
Intel Core i5 760@2.8GHz
8Gb Ram
750GTX 2gb (397.93 driver)

Below are the memory dump files. Please note that there are only 4 files saved on the minidump folder while the system has been hanging for past two days.

052718-18064-01.dmp

    Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800a6ce4e0, fffff8800fb3671c, ffffffffc000009a, 4}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+a8871c )

Followup: MachineOwner
---------

1: kd> !analyze -v

BugCheck 116, {fffffa8009b404e0, fffff8800fccb71c, ffffffffc000009a, 4}

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+a8871c )


VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8009b404e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800fccb71c, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.

Debugging Details:
------------------


FAULTING_IP: 
nvlddmkm+a8871c
fffff880`0fccb71c 48ff252d12e4ff  jmp     qword ptr [nvlddmkm+0x8c9950 (fffff880`0fb0c950)]

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`03924b88 fffff880`10328134 : 00000000`00000116 fffffa80`09b404e0 fffff880`0fccb71c ffffffff`c000009a : nt!KeBugCheckEx
fffff880`03924b90 00000000`00000116 : fffffa80`09b404e0 fffff880`0fccb71c ffffffff`c000009a 00000000`00000004 : dxgkrnl+0x5d134
fffff880`03924b98 fffffa80`09b404e0 : fffff880`0fccb71c ffffffff`c000009a 00000000`00000004 00000000`00000001 : 0x116
fffff880`03924ba0 fffff880`0fccb71c : ffffffff`c000009a 00000000`00000004 00000000`00000001 fffffa80`09b404e0 : 0xfffffa80`09b404e0
fffff880`03924ba8 ffffffff`c000009a : 00000000`00000004 00000000`00000001 fffffa80`09b404e0 fffff880`102fb867 : nvlddmkm+0xa8871c
fffff880`03924bb0 00000000`00000004 : 00000000`00000001 fffffa80`09b404e0 fffff880`102fb867 fffff880`0fccb71c : 0xffffffff`c000009a
fffff880`03924bb8 00000000`00000001 : fffffa80`09b404e0 fffff880`102fb867 fffff880`0fccb71c fffffa80`08ebc000 : 0x4
fffff880`03924bc0 fffffa80`09b404e0 : fffff880`102fb867 fffff880`0fccb71c fffffa80`08ebc000 00000000`00000000 : 0x1
fffff880`03924bc8 fffff880`102fb867 : fffff880`0fccb71c fffffa80`08ebc000 00000000`00000000 ffffffff`c000009a : 0xfffffa80`09b404e0
fffff880`03924bd0 fffff880`0fccb71c : fffffa80`08ebc000 00000000`00000000 ffffffff`c000009a fffffa80`08e97010 : dxgkrnl+0x30867
fffff880`03924bd8 fffffa80`08ebc000 : 00000000`00000000 ffffffff`c000009a fffffa80`08e97010 ffffffff`feced300 : nvlddmkm+0xa8871c
fffff880`03924be0 00000000`00000000 : ffffffff`c000009a fffffa80`08e97010 ffffffff`feced300 fffffa80`08926d50 : 0xfffffa80`08ebc000


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvlddmkm+a8871c
fffff880`0fccb71c 48ff252d12e4ff  jmp     qword ptr [nvlddmkm+0x8c9950 (fffff880`0fb0c950)]

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nvlddmkm+a8871c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5b04745d

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

Followup: MachineOwner
---------

052718-19406-01.dmp

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800a9df4e0, fffff8800fd8471c, ffffffffc000009a, 4}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+a8871c )

Followup: MachineOwner
---------

1: kd> !analyze -v

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800a9df4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800fd8471c, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.

Debugging Details:
------------------


FAULTING_IP: 
nvlddmkm+a8871c
fffff880`0fd8471c 48ff252d12e4ff  jmp     qword ptr [nvlddmkm+0x8c9950 (fffff880`0fbc5950)]

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`0356eb88 fffff880`0f25d134 : 00000000`00000116 fffffa80`0a9df4e0 fffff880`0fd8471c ffffffff`c000009a : nt!KeBugCheckEx
fffff880`0356eb90 00000000`00000116 : fffffa80`0a9df4e0 fffff880`0fd8471c ffffffff`c000009a 00000000`00000004 : dxgkrnl+0x5d134
fffff880`0356eb98 fffffa80`0a9df4e0 : fffff880`0fd8471c ffffffff`c000009a 00000000`00000004 00000000`00000001 : 0x116
fffff880`0356eba0 fffff880`0fd8471c : ffffffff`c000009a 00000000`00000004 00000000`00000001 fffffa80`0a9df4e0 : 0xfffffa80`0a9df4e0
fffff880`0356eba8 ffffffff`c000009a : 00000000`00000004 00000000`00000001 fffffa80`0a9df4e0 fffff880`0f230867 : nvlddmkm+0xa8871c
fffff880`0356ebb0 00000000`00000004 : 00000000`00000001 fffffa80`0a9df4e0 fffff880`0f230867 fffff880`0fd8471c : 0xffffffff`c000009a
fffff880`0356ebb8 00000000`00000001 : fffffa80`0a9df4e0 fffff880`0f230867 fffff880`0fd8471c fffffa80`09024000 : 0x4
fffff880`0356ebc0 fffffa80`0a9df4e0 : fffff880`0f230867 fffff880`0fd8471c fffffa80`09024000 00000000`00000000 : 0x1
fffff880`0356ebc8 fffff880`0f230867 : fffff880`0fd8471c fffffa80`09024000 00000000`00000000 ffffffff`c000009a : 0xfffffa80`0a9df4e0
fffff880`0356ebd0 fffff880`0fd8471c : fffffa80`09024000 00000000`00000000 ffffffff`c000009a fffffa80`0900f010 : dxgkrnl+0x30867
fffff880`0356ebd8 fffffa80`09024000 : 00000000`00000000 ffffffff`c000009a fffffa80`0900f010 ffffffff`feced300 : nvlddmkm+0xa8871c
fffff880`0356ebe0 00000000`00000000 : ffffffff`c000009a fffffa80`0900f010 ffffffff`feced300 fffffa80`0c895010 : 0xfffffa80`09024000


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvlddmkm+a8871c
fffff880`0fd8471c 48ff252d12e4ff  jmp     qword ptr [nvlddmkm+0x8c9950 (fffff880`0fbc5950)]

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nvlddmkm+a8871c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5b04745d

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

Followup: MachineOwner
---------

052718-20904-01.dmp

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800add94e0, fffff8800fb5f71c, ffffffffc000009a, 4}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+a8871c )

Followup: MachineOwner
---------

1: kd> !analyze -v

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800add94e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800fb5f71c, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.

Debugging Details:
------------------


FAULTING_IP: 
nvlddmkm+a8871c
fffff880`0fb5f71c 48ff252d12e4ff  jmp     qword ptr [nvlddmkm+0x8c9950 (fffff880`0f9a0950)]

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`03367b88 fffff880`0448b134 : 00000000`00000116 fffffa80`0add94e0 fffff880`0fb5f71c ffffffff`c000009a : nt!KeBugCheckEx
fffff880`03367b90 00000000`00000116 : fffffa80`0add94e0 fffff880`0fb5f71c ffffffff`c000009a 00000000`00000004 : dxgkrnl+0x5d134
fffff880`03367b98 fffffa80`0add94e0 : fffff880`0fb5f71c ffffffff`c000009a 00000000`00000004 00000000`00000001 : 0x116
fffff880`03367ba0 fffff880`0fb5f71c : ffffffff`c000009a 00000000`00000004 00000000`00000001 fffffa80`0add94e0 : 0xfffffa80`0add94e0
fffff880`03367ba8 ffffffff`c000009a : 00000000`00000004 00000000`00000001 fffffa80`0add94e0 fffff880`0445e867 : nvlddmkm+0xa8871c
fffff880`03367bb0 00000000`00000004 : 00000000`00000001 fffffa80`0add94e0 fffff880`0445e867 fffff880`0fb5f71c : 0xffffffff`c000009a
fffff880`03367bb8 00000000`00000001 : fffffa80`0add94e0 fffff880`0445e867 fffff880`0fb5f71c fffffa80`07f04000 : 0x4
fffff880`03367bc0 fffffa80`0add94e0 : fffff880`0445e867 fffff880`0fb5f71c fffffa80`07f04000 00000000`00000000 : 0x1
fffff880`03367bc8 fffff880`0445e867 : fffff880`0fb5f71c fffffa80`07f04000 00000000`00000000 ffffffff`c000009a : 0xfffffa80`0add94e0
fffff880`03367bd0 fffff880`0fb5f71c : fffffa80`07f04000 00000000`00000000 ffffffff`c000009a fffffa80`07f03010 : dxgkrnl+0x30867
fffff880`03367bd8 fffffa80`07f04000 : 00000000`00000000 ffffffff`c000009a fffffa80`07f03010 ffffffff`feced300 : nvlddmkm+0xa8871c
fffff880`03367be0 00000000`00000000 : ffffffff`c000009a fffffa80`07f03010 ffffffff`feced300 fffffa80`0a587a30 : 0xfffffa80`07f04000


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvlddmkm+a8871c
fffff880`0fb5f71c 48ff252d12e4ff  jmp     qword ptr [nvlddmkm+0x8c9950 (fffff880`0f9a0950)]

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nvlddmkm+a8871c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5b04745d

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

Followup: MachineOwner
---------

052718-25100-01.dmp

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800a6ce4e0, fffff8800fb3671c, ffffffffc000009a, 4}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+a8871c )

Followup: MachineOwner
---------

1: kd> !analyze -v

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800a6ce4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800fb3671c, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.

Debugging Details:
------------------


FAULTING_IP: 
nvlddmkm+a8871c
fffff880`0fb3671c 48ff252d12e4ff  jmp     qword ptr [nvlddmkm+0x8c9950 (fffff880`0f977950)]

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`03392b88 fffff880`048b6134 : 00000000`00000116 fffffa80`0a6ce4e0 fffff880`0fb3671c ffffffff`c000009a : nt!KeBugCheckEx
fffff880`03392b90 00000000`00000116 : fffffa80`0a6ce4e0 fffff880`0fb3671c ffffffff`c000009a 00000000`00000004 : dxgkrnl+0x5d134
fffff880`03392b98 fffffa80`0a6ce4e0 : fffff880`0fb3671c ffffffff`c000009a 00000000`00000004 00000000`00000001 : 0x116
fffff880`03392ba0 fffff880`0fb3671c : ffffffff`c000009a 00000000`00000004 00000000`00000001 fffffa80`0a6ce4e0 : 0xfffffa80`0a6ce4e0
fffff880`03392ba8 ffffffff`c000009a : 00000000`00000004 00000000`00000001 fffffa80`0a6ce4e0 fffff880`04889867 : nvlddmkm+0xa8871c
fffff880`03392bb0 00000000`00000004 : 00000000`00000001 fffffa80`0a6ce4e0 fffff880`04889867 fffff880`0fb3671c : 0xffffffff`c000009a
fffff880`03392bb8 00000000`00000001 : fffffa80`0a6ce4e0 fffff880`04889867 fffff880`0fb3671c fffffa80`0906e000 : 0x4
fffff880`03392bc0 fffffa80`0a6ce4e0 : fffff880`04889867 fffff880`0fb3671c fffffa80`0906e000 00000000`00000000 : 0x1
fffff880`03392bc8 fffff880`04889867 : fffff880`0fb3671c fffffa80`0906e000 00000000`00000000 ffffffff`c000009a : 0xfffffa80`0a6ce4e0
fffff880`03392bd0 fffff880`0fb3671c : fffffa80`0906e000 00000000`00000000 ffffffff`c000009a fffffa80`0904d010 : dxgkrnl+0x30867
fffff880`03392bd8 fffffa80`0906e000 : 00000000`00000000 ffffffff`c000009a fffffa80`0904d010 ffffffff`feced300 : nvlddmkm+0xa8871c
fffff880`03392be0 00000000`00000000 : ffffffff`c000009a fffffa80`0904d010 ffffffff`feced300 fffffa80`06ccea30 : 0xfffffa80`0906e000


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvlddmkm+a8871c
fffff880`0fb3671c 48ff252d12e4ff  jmp     qword ptr [nvlddmkm+0x8c9950 (fffff880`0f977950)]

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nvlddmkm+a8871c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5b04745d

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

Followup: MachineOwner
---------

Below results are retrieved from Event Viewer and as advised is only left if it proves useful. Error Codes generated are Bug Check Code 0 and Bug Check Code 278

Log Name:      System 
Source:        Microsoft-Windows-Kernel-Power
Date:          5/26/2018 5:16:11 PM
Event ID:      41
Task Category: (63)
Level:         Critical
Keywords:      (2)
User:          SYSTEM
Computer:      MASTER-PC
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Event 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}" />
    <EventID>41</EventID>
    <Version>2</Version>
    <Level>1</Level>
    <Task>63</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000002</Keywords>
    <TimeCreated SystemTime="2018-05-26T11:46:11.927211300Z" />
    <EventRecordID>331327</EventRecordID>
    <Correlation />
    <Execution ProcessID="4" ThreadID="8" />
    <Channel>System</Channel>
    <Computer>MASTER-PC</Computer>
    <Security UserID="S-1-5-18" />
  </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">false</Data>
    <Data Name="PowerButtonTimestamp">0</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Kernel-Power
Date:          5/26/2018 7:09:38 PM
Event ID:      41
Task Category: (63)
Level:         Critical
Keywords:      (2)
User:          SYSTEM
Computer:      MASTER-PC
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    "Same"
  </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">false</Data>
    <Data Name="PowerButtonTimestamp">0</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Kernel-Power
Date:          5/26/2018 8:33:30 PM
Event ID:      41
Task Category: (63)
Level:         Critical
Keywords:      (2)
User:          SYSTEM
Computer:      MASTER-PC
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    "Same"
  </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">false</Data>
    <Data Name="PowerButtonTimestamp">0</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Kernel-Power
Date:          5/26/2018 8:52:13 PM
Event ID:      41
Task Category: (63)
Level:         Critical
Keywords:      (2)
User:          SYSTEM
Computer:      MASTER-PC
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    "Same"
  </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">false</Data>
    <Data Name="PowerButtonTimestamp">0</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Kernel-Power
Date:          5/26/2018 9:37:18 PM
Event ID:      41
Task Category: (63)
Level:         Critical
Keywords:      (2)
User:          SYSTEM
Computer:      MASTER-PC
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    "Same"
  </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">false</Data>
    <Data Name="PowerButtonTimestamp">0</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Kernel-Power
Date:          5/26/2018 10:50:31 PM
Event ID:      41
Task Category: (63)
Level:         Critical
Keywords:      (2)
User:          SYSTEM
Computer:      MASTER-PC
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    "Same"
  </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">false</Data>
    <Data Name="PowerButtonTimestamp">0</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Kernel-Power
Date:          5/27/2018 1:51:50 PM
Event ID:      41
Task Category: (63)
Level:         Critical
Keywords:      (2)
User:          SYSTEM
Computer:      MASTER-PC
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    "Same"
  </System>
  <EventData>
    <Data Name="BugcheckCode">278</Data>
    <Data Name="BugcheckParameter1">0xfffffa800a9df4e0</Data>
    <Data Name="BugcheckParameter2">0xfffff8800fd8471c</Data>
    <Data Name="BugcheckParameter3">0xffffffffc000009a</Data>
    <Data Name="BugcheckParameter4">0x4</Data>
    <Data Name="SleepInProgress">false</Data>
    <Data Name="PowerButtonTimestamp">0</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Kernel-Power
Date:          5/27/2018 2:09:57 PM
Event ID:      41
Task Category: (63)
Level:         Critical
Keywords:      (2)
User:          SYSTEM
Computer:      MASTER-PC
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    "Same"
  </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">false</Data>
    <Data Name="PowerButtonTimestamp">0</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Kernel-Power
Date:          5/27/2018 4:44:30 PM
Event ID:      41
Task Category: (63)
Level:         Critical
Keywords:      (2)
User:          SYSTEM
Computer:      MASTER-PC
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Event 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}" />
    <EventID>41</EventID>
    <Version>2</Version>
    <Level>1</Level>
    <Task>63</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000002</Keywords>
    <TimeCreated SystemTime="2018-05-27T11:14:30.410812200Z" />
    <EventRecordID>332900</EventRecordID>
    <Correlation />
    <Execution ProcessID="4" ThreadID="8" />
    <Channel>System</Channel>
    <Computer>MASTER-PC</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <EventData>
    <Data Name="BugcheckCode">278</Data>
    <Data Name="BugcheckParameter1">0xfffffa8009b404e0</Data>
    <Data Name="BugcheckParameter2">0xfffff8800fccb71c</Data>
    <Data Name="BugcheckParameter3">0xffffffffc000009a</Data>
    <Data Name="BugcheckParameter4">0x4</Data>
    <Data Name="SleepInProgress">false</Data>
    <Data Name="PowerButtonTimestamp">0</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Kernel-Power
Date:          5/27/2018 6:08:41 PM
Event ID:      41
Task Category: (63)
Level:         Critical
Keywords:      (2)
User:          SYSTEM
Computer:      MASTER-PC
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    "Same"
  </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">false</Data>
    <Data Name="PowerButtonTimestamp">0</Data>
  </EventData>
</Event>

Log Name:      System
Source:        Microsoft-Windows-Kernel-Power
Date:          5/27/2018 6:28:49 PM
Event ID:      41
Task Category: (63)
Level:         Critical
Keywords:      (2)
User:          SYSTEM
Computer:      MASTER-PC
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    "Same"
  </System>
  <EventData>
    <Data Name="BugcheckCode">278</Data>
    <Data Name="BugcheckParameter1">0xfffffa800a6ce4e0</Data>
    <Data Name="BugcheckParameter2">0xfffff8800fb3671c</Data>
    <Data Name="BugcheckParameter3">0xffffffffc000009a</Data>
    <Data Name="BugcheckParameter4">0x4</Data>
    <Data Name="SleepInProgress">false</Data>
    <Data Name="PowerButtonTimestamp">0</Data>
  </EventData>
</Event>
  • There is no Bluescreen with code 0x0. Please provide the minidump files these crashes produced. – Daniel B May 28 '18 at 9:15
  • Sure but BugCheckCode0x0 is logged many times in EventViewer after I had to manually restart the system but system won't restart right away and would either turn off or restart after some time. – cs90 May 28 '18 at 9:20
  • I understand. However, that log entry is incomplete and as such entirely worthless for troubleshooting. – Daniel B May 28 '18 at 9:24
  • I just uploaded the minidump files. – cs90 May 28 '18 at 14:43
  • update nVIDIA GPU drivers – magicandre1981 May 29 '18 at 14:49

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.