Windows Hardware Error in Reliability Monitor

I see occasionally in the Reliability Monitor , a Critical Event, Windows, Hardware error. If there is a pattern it is mostly when I am playing a game (Diablo 3), but it causes nothing noticeable until I go and I see there was an error.

I am trying to figure out if it is an actual hardware issue or just Windows (driver?). The WERInternalMetadata.xml file says the Report Source is Memory, but I am not sure I know how to read it?

When I open the error, I see:
---------------------------------------------------------------
Source
Windows

Summary
Hardware error

Date
‎4/‎27/‎2017 4:46 PM

Status
Not reported

Description
A problem with your hardware caused Windows to stop working correctly.

Problem signature
Problem Event Name: LiveKernelEvent
Code: 141
Parameter 1: ffffc488308484a0
Parameter 2: fffff80cc4bce060
Parameter 3: 0
Parameter 4: 5480
OS version: 10_0_15063
Service Pack: 0_0
Product: 256_1
OS Version: 10.0.15063.2.0.0.256.48
Locale ID: 1033

Files that help describe the problem
WATCHDOG-20170427-1646.dmp
sysdata.xml
WERInternalMetadata.xml
memory.csv
sysinfo.txt
----------------------------------------------------------
If I view the files the WERInternalMetadata.xml file contains:

---------------------------------------------------------------
<?xml version="1.0" encoding="UTF-16"?>
<WERReportMetadata>
<OSVersionInformation>
<WindowsNTVersion>10.0</WindowsNTVersion>
<Build>15063</Build>
<Product>(0x30): Windows 10 Pro</Product>
<Edition>Professional</Edition>
<BuildString>15063.250.amd64fre.rs2_release.170317-1834</BuildString>
<Revision>250</Revision>
<Flavor>Multiprocessor Free</Flavor>
<Architecture>X64</Architecture>
<LCID>1033</LCID>
</OSVersionInformation>
<ProblemSignatures>
<EventType>LiveKernelEvent</EventType>
<Parameter0>141</Parameter0>
<Parameter1>ffffc488308484a0</Parameter1>
<Parameter2>fffff80cc4bce060</Parameter2>
<Parameter3>0</Parameter3>
<Parameter4>5480</Parameter4>
<Parameter5>10_0_15063</Parameter5>
<Parameter6>0_0</Parameter6>
<Parameter7>256_1</Parameter7>
</ProblemSignatures>
<DynamicSignatures>
<Parameter1>10.0.15063.2.0.0.256.48</Parameter1>
<Parameter2>1033</Parameter2>
</DynamicSignatures>
<SystemInformation>
<MID>93EFC622-CECF-4013-8CA7-BE6BD5B2F011</MID>
<SystemManufacturer>To Be Filled By O.E.M.</SystemManufacturer>
<SystemProductName>To Be Filled By O.E.M.</SystemProductName>
<BIOSVersion>P7.20</BIOSVersion>
<OSInstallDate>1492101131</OSInstallDate>
<OSInstallTime>2017-04-13T16:32:05Z</OSInstallTime>
<TimeZoneBias>08:00</TimeZoneBias>
</SystemInformation>
<SecureBootState>
<UEFISecureBootEnabled>0</UEFISecureBootEnabled>
</SecureBootState>
<ReportInformation>
<Guid>29258d70-50f7-4255-9681-9f50237621d2</Guid>
<ReportSource>memory</ReportSource>
<CreationTime>2017-04-27T23:46:40Z</CreationTime>
</ReportInformation>
</WERReportMetadata>
--------------------------------------------

Hi
U can try disable Fast startup in Power Options and check
Turn On or Off Fast Startup in Windows 10 - Windows 10 Performance Maintenance Tutorials

ZyKLon said:

Hi
U can try disable Fast startup in Power Options and check
Turn On or Off Fast Startup in Windows 10 - Windows 10 Performance Maintenance Tutorials

I will try that.

I noticed by the Event Viewer looking at the same time that it is a Display driver issue:

Display driver nvlddmkm stopped responding and has successfully recovered.

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Display" />
<EventID Qualifiers="0">4101</EventID>
<Level>3</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2017-04-27T23:46:38.548290000Z" />
<EventRecordID>7461</EventRecordID>
<Channel>System</Channel>
<Computer>IsaacFL</Computer>
<Security />
</System>
- <EventData>
<Data>nvlddmkm</Data>
<Data />
</EventData>
</Event>