Sudden restarts after upgrading memory

The event log displayed WHEA hardware error problems: - what does it mean for a layman?

link to the motherboard site: GA-H81M-HD3 (rev. 1.0) | Motherboard - GIGABYTE


Added speedfan screenshot

axe0 said:

Please remove either of the modules, you appear to be running with mixed memory.

and maybe it's a driver problem? Is there a way to check this? I already update to the latest but maybe this is the problem, is there an application that can check contradictions with the drivers?

Please download and install HWINFO and use the drop down arrow on the right for the memory.
Make sure the product number for each RAM module is in full view.

Info displayed on the Gigabyte website for memory:

1. 2 x 1.5V DDR3 DIMM sockets supporting up to 16 GB of system memory
   * Due to a Windows 32-bit operating system limitation, when more than 4 GB of physical memory is installed, the actual memory size displayed will be less than the size of the physical memory installed.
2. Dual channel memory architecture
3. Support for DDR3 1600/1333 MHz memory modules
4. Support for non-ECC memory modules
5. Support for Extreme Memory Profile (XMP) memory modules

Are you 32x or 64x bit?
How come you have not updated windows 10 version 1607 to 1703?
Was it not capable of being upgraded without fixing underlying problems?

Please run the Memtest86+ version 5.01 on each RAM module in the same DIMM for 8 or more passes.
Please use a camera or smart phone camera to take pictures and post images into the thread.

Please see post # 2 for resetting the BIOS.

Attached, If I missed something, let me know
The page was too big so I created 2 images, one per memory stick

OK, I dug into event viewer and found some things that may be related. Based on my UPS log, in 3:12am, the computer was AFTER the restart, following is what I see around that time

Administrative events:
20/10/2017 01:51:40
'Windows.MiracastView_cw5n1h2txyewy' uninstall failed for Amos. Error: 'Removal failed. Please contact your software vendor.' (0.5456572 seconds)

20/10/2017 03:10:19:
The Update Orchestrator Service service terminated with the following error:
This operation returned because the timeout period expired.

20/10/2017 03:12:29
Session "" failed to start with the following error: 0xC0000022

20/10/2017 03:14:52
Faulting application name: IAStorDataMgrSvc.exe, version: 14.8.16.1063, time stamp: 0x58eb8338
Faulting module name: ntdll.dll, version: 10.0.16299.15, time stamp: 0xac8afc81
Exception code: 0xc0000374
Fault offset: 0x000da849
Faulting process id: 0x1db0
Faulting application start time: 0x01d349386886c0af
Faulting application path: C:\Program Files\Intel\Intel(R) Rapid Storage Technology\IAStorDataMgrSvc.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: c706507a-61f9-43e9-b6e4-074e84ebbdf2
Faulting package full name:
Faulting package-relative application ID:

System
20/10/2017 03:12:16 / 20/10/2017 03:12:15 (twice)
NtpClient was unable to set a manual peer to use as a time source because of DNS resolution error on 'time.windows.com,0x9'. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: No such host is known. (0x80072AF9)

Microsot windows Diagnostics
20/10/2017 03:14:59 (notice it's after the restart but it's critical, the others were Error)
Windows has started up:
Boot Duration : 189288ms
IsDegradation : false
Incident Time (UTC) : ‎2017‎-‎10‎-‎20T00:11:00.684707300Z

xml of the critical:
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Microsoft-Windows-Diagnostics-Performance" Guid="{CFC18EC0-96B1-4EBA-961B-622CAEE05B0A}" />

<EventID>100</EventID>

<Version>2</Version>

<Level>1</Level>

<Task>4002</Task>

<Opcode>34</Opcode>

<Keywords>0x8000000000010000</Keywords>

<TimeCreated SystemTime="2017-10-20T00:14:59.700167800Z" />

<EventRecordID>1</EventRecordID>

<Correlation ActivityID="{E91C3C61-4937-0002-D840-1CE93749D301}" />

<Execution ProcessID="3148" ThreadID="3408" />

<Channel>Microsoft-Windows-Diagnostics-Performance/Operational</Channel>

<Computer>DESKTOP-K0H9K1I</Computer>

<Security UserID="S-1-5-19" />

</System>


- <EventData>
<Data Name="BootTsVersion">2</Data>

<Data Name="BootStartTime">2017-10-20T00:11:00.684707300Z</Data>

<Data Name="BootEndTime">2017-10-20T00:14:34.894924900Z</Data>

<Data Name="SystemBootInstance">1</Data>

<Data Name="UserBootInstance">1</Data>

<Data Name="BootTime">189288</Data>

<Data Name="MainPathBootTime">144938</Data>

<Data Name="BootKernelInitTime">29</Data>

<Data Name="BootDriverInitTime">1747</Data>

<Data Name="BootDevicesInitTime">6411</Data>

<Data Name="BootPrefetchInitTime">0</Data>

<Data Name="BootPrefetchBytes">0</Data>

<Data Name="BootAutoChkTime">0</Data>

<Data Name="BootSmssInitTime">16723</Data>

<Data Name="BootCriticalServicesInitTime">16465</Data>

<Data Name="BootUserProfileProcessingTime">5034</Data>

<Data Name="BootMachineProfileProcessingTime">2370</Data>

<Data Name="BootExplorerInitTime">54756</Data>

<Data Name="BootNumStartupApps">8</Data>

<Data Name="BootPostBootTime">44350</Data>

<Data Name="BootIsRebootAfterInstall">false</Data>

<Data Name="BootRootCauseStepImprovementBits">0</Data>

<Data Name="BootRootCauseGradualImprovementBits">0</Data>

<Data Name="BootRootCauseStepDegradationBits">0</Data>

<Data Name="BootRootCauseGradualDegradationBits">0</Data>

<Data Name="BootIsDegradation">false</Data>

<Data Name="BootIsStepDegradation">false</Data>

<Data Name="BootIsGradualDegradation">false</Data>

<Data Name="BootImprovementDelta">0</Data>

<Data Name="BootDegradationDelta">0</Data>

<Data Name="BootIsRootCauseIdentified">false</Data>

<Data Name="OSLoaderDuration">2908</Data>

<Data Name="BootPNPInitStartTimeMS">29</Data>

<Data Name="BootPNPInitDuration">6838</Data>

<Data Name="OtherKernelInitDuration">3383</Data>

<Data Name="SystemPNPInitStartTimeMS">9018</Data>

<Data Name="SystemPNPInitDuration">1585</Data>

<Data Name="SessionInitStartTimeMS">11807</Data>

<Data Name="Session0InitDuration">4017</Data>

<Data Name="Session1InitDuration">243</Data>

<Data Name="SessionInitOtherDuration">12461</Data>

<Data Name="WinLogonStartTimeMS">28531</Data>

<Data Name="OtherLogonInitActivityDuration">54244</Data>

<Data Name="UserLogonWaitDuration">24924</Data>


</EventData>


</Event>

1) Are you using just 1 RAM module?
The RAM modules are similar but differ by 1 character (6 versus 0).
When using dual channel RAM they should be identical.
2) Which RAM module are you using 6 or 0?
For the DM log collectors please leave the zips already in the thread and post a new one so that they can be compared over time.
3) Were you able to reset the bios?
4) Have you been able to start testing 1 RAM module at a time in the same DIMM?
5) For all tests please post images into the thread.
6) For Memtest86+ version 5.01 please use a camera or smart phone camera to take pictures and post images into the thread.
7) The Windows version that the computer has is 1607. Were you not able to update it to either 1703 or 1709?
8) Please post an updated zip into the thread so that we can see the event logs when there is only 1 RAM module in typical use.

1. What do you mean by 1 ram module? How can I make them dual? I thought it's automatic, I do know I only have 2 slots
2. I think I'm using both?
3. I didn't try to reset the bios, I changed the memory to "better stability". Because the problem can happen even a week from now, I have nothing left to do but wait and see if/when it happens again.
4. DIMM is the stick itself or the slot? :) Now I have 2 sticks, 1 per slot.
5. What tests are you referring to? memtest simply wrote there are no errors (6 passes), same with Windows memory tester.
7. Where did you see 1607? Yesterday I updated to 1709 and it went smooth. After the update did it last restart, I saw a weird error that now I regret not printing. I didn't receive this popup again since.
8. I will do that test later. After seeing everything else is not helping.
9. Did the event viewer helped in anyway?

Thank you very much for your patience and help

For RAM the 2 RAM modules are different.
They should not be used at the same time.
One of the RAM modules should be replaced so that the SKU or product numbers are identical.
Alternatively you can use the largest size RAM module available in 1 DIMM.
Each RAM module needs to be tested.
Testing is not done by time but by passes.
Proper testing requires at least 8 passes and the more the passes the better the testing.
It sometimes takes passes in the 20's to find malfunctioning RAM.
Fewer than 8 passes has a significant incidence of false negatives.
A false negative is a test result that is a pass when there is malfunctioning RAM.
Just 1 error is a fail and you can abort testing.
Test each RAM module in the same DIMM for 8 or more passes.
When the testing is complete use a camera or smart phone camera to take a picture and post images into the thread.

There are many methods to test RAM.
Each software has a different testing algorithm.
Make sure that you use Memtest86+ version 5.01:
Memtest86+ - Advanced Memory Diagnostic Tool
Memtest86+ - Advanced Memory Diagnostic Tool