"5) When available please post images and text reports from RAM testing in DIMM 1 and 3."
Im not sure what you mean...Are you talking about the Memory Test? i understand what you mean when you say in DIMM 1 and 3.
- - - Updated - - -
Attachment 233551
1) See post #4
a) step #12: Memtest86 version 8.1
b) step #1b: Memory.dmp
Code:Crash dump found at C:\Windows\MEMORY.DMP Creation date: 05/12/2019 21:31:08 Size on disk: 540 MB
2) Uninstall and reinstall: rt640x64.sys
Realtek PCIe GBE Family Controller
Code:rt640x64.sys Realtek NICDRV 8169 PCIe GBE Family Controller driver http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=13&PFid=5&Level=5&Conn=4&DownTypeID=3&GetDown=false
Code:Name [00000001] Realtek PCIe GBE Family Controller Adapter Type Ethernet 802.3 Product Type Realtek PCIe GBE Family Controller Installed Yes PNP Device ID PCI\VEN_10EC&DEV_8168&SUBSYS_81681849&REV_11\4&9B80F17&0&00AB Last Reset 5/12/2019 9:31 PM Index 1 Service Name rt640x64 IP Address 192.168.0.138, fe80::a007:e4da:b9f7:5ed4 IP Subnet 255.255.255.0, 64 Default IP Gateway 192.168.0.1 DHCP Enabled Yes DHCP Server 192.168.0.1 DHCP Lease Expires 8/16/1932 4:33 PM DHCP Lease Obtained 8/15/1932 4:33 PM MAC Address 70:85:C2:B6:E9:35 I/O Port 0x0000D000-0x0000D0FF Memory Address 0xFE100000-0xFE100FFF Memory Address 0xD2100000-0xD2103FFF IRQ Channel IRQ 4294967294 Driver c:\windows\system32\drivers\rt640x64.sys (10.7.107.2016, 914.25 KB (936,192 bytes), 5/10/2019 4:01 PM)Code:rt640x64 Realtek RT640 NT Driver c:\windows\system32\drivers\rt640x64.sys Kernel Driver No Manual Stopped OK Normal No NoCode:rt640x64.sys Wed Jan 6 23:48:31 2016 (568E184F)Code:rt640x64 Realtek RT640 NT Drive Realtek RT640 NT Drive Kernel Manual Stopped OK FALSE FALSE 4,096 888,832 0 1/7/2016 2:48:31 AM C:\Windows\system32\drivers\rt640x64.sys 8,192
The single core operation is normal for this test. Sometimes it takes more than 8 passes to show up problems and sometimes the test simply does not show anything so it can be frustrating but seeing your latest crash dumps I still can't rule out memory problems. In the meantime Zbook has picked up on the driver issues and so continue with those. It may then be necessary to try operating with just one memory module at a time to try and see if one works and the other fails.
1) For any BSOD:
a) Immediately upload results from the BETA log collector
b) Open file explorer > this PC > C: > in the right upper corner search for: C:\windows\memory.dmp > if the file size is < 1.5 GB then zip > post a separate share link into the thread using one drive, drop box, or google drive
2) The above steps should be performed when testing RAM.
3) Open administrative powershell and copy and paste:
Code:[Cmdletbinding()] Param( [string]$Computername = "localhost" ) cls $PysicalMemory = Get-WmiObject -class "win32_physicalmemory" -namespace "root\CIMV2" -ComputerName $Computername Write-Host "Memore Modules:" -ForegroundColor Green $PysicalMemory | Format-Table Tag,BankLabel,@{n="Capacity(GB)";e={$_.Capacity/1GB}},Manufacturer,PartNumber,Speed -AutoSize Write-Host "Total Memory:" -ForegroundColor Green Write-Host "$((($PysicalMemory).Capacity | Measure-Object -Sum).Sum/1GB)GB" $TotalSlots = ((Get-WmiObject -Class "win32_PhysicalMemoryArray" -namespace "root\CIMV2" -ComputerName $Computername).MemoryDevices | Measure-Object -Sum).Sum Write-Host "`nTotal Memory Slots:" -ForegroundColor Green Write-Host $TotalSlots $UsedSlots = (($PysicalMemory) | Measure-Object).Count Write-Host "`nUsed Memory Slots:" -ForegroundColor Green Write-Host $UsedSlots If($UsedSlots -eq $TotalSlots) { Write-Host "All memory slots are filled up, none is empty!" -ForegroundColor Yellow }
4) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread
5) Open administrative command prompt and copy and paste:
6) bcdedit /enum all
7) wmic memorychip get manufacturer, capacity, partnumber, speed, memorytype, devicelocator, formfactor
8) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread
Code:PS C:\Windows\system32> $PysicalMemory = Get-WmiObject -class "win32_physicalmemory" -namespace "root\CIMV2" -ComputerName $Computername PS C:\Windows\system32> PS C:\Windows\system32> Write-Host "Memore Modules:" -ForegroundColor Green Memore Modules: PS C:\Windows\system32> $PysicalMemory | Format-Table Tag,BankLabel,@{n="Capacity(GB)";e={$_.Capacity/1GB}},Manufacturer,PartNumber,Speed -AutoSize Tag BankLabel Capacity(GB) Manufacturer PartNumber Speed --- --------- ------------ ------------ ---------- ----- Physical Memory 1 A1_BANK1 4 Undefined EWB4GB681CA3-16IC 1600 Physical Memory 3 A1_BANK3 4 Undefined EWB4GB681CA3-16IC 1600 PS C:\Windows\system32> PS C:\Windows\system32> Write-Host "Total Memory:" -ForegroundColor Green Total Memory: PS C:\Windows\system32> Write-Host "$((($PysicalMemory).Capacity | Measure-Object -Sum).Sum/1GB)GB" 8GB PS C:\Windows\system32> PS C:\Windows\system32> $TotalSlots = ((Get-WmiObject -Class "win32_PhysicalMemoryArray" -namespace "root\CIMV2" -ComputerName $Computername).MemoryDevices | Measure-Object -Sum).Sum PS C:\Windows\system32> Write-Host "`nTotal Memory Slots:" -ForegroundColor Green Total Memory Slots: PS C:\Windows\system32> Write-Host $TotalSlots 4 PS C:\Windows\system32> PS C:\Windows\system32> $UsedSlots = (($PysicalMemory) | Measure-Object).Count PS C:\Windows\system32> Write-Host "`nUsed Memory Slots:" -ForegroundColor Green Used Memory Slots: PS C:\Windows\system32> Write-Host $UsedSlots 2 PS C:\Windows\system32> PS C:\Windows\system32> If($UsedSlots -eq $TotalSlots) >> { >> Write-Host "All memory slots are filled up, none is empty!" -ForegroundColor Yellow >> } PS C:\Windows\system32>I have attached all i could below, I did not have any Memory.DMP in my Windows folder, which i thought was weird because i was going to upload it last night but I ran the Memtest first and when I came back to upload it, it did not appear to be there.Code:Microsoft Windows [Version 10.0.17763.437] (c) 2018 Microsoft Corporation. All rights reserved. C:\Windows\system32>bcdedit /enum all Windows Boot Manager -------------------- identifier {bootmgr} device partition=\Device\HarddiskVolume1 description Windows Boot Manager locale en-US inherit {globalsettings} default {current} resumeobject {90bc5c90-737b-11e9-996f-a09de8f40a82} displayorder {current} toolsdisplayorder {memdiag} timeout 3 Windows Boot Loader ------------------- identifier {current} device partition=C: path \Windows\system32\winload.exe description Windows 10 locale en-US inherit {bootloadersettings} recoverysequence {90bc5c92-737b-11e9-996f-a09de8f40a82} displaymessageoverride Recovery recoveryenabled Yes allowedinmemorysettings 0x15000075 osdevice partition=C: systemroot \Windows resumeobject {90bc5c90-737b-11e9-996f-a09de8f40a82} nx OptIn bootmenupolicy Standard Windows Boot Loader ------------------- identifier {90bc5c92-737b-11e9-996f-a09de8f40a82} device ramdisk=[\Device\HarddiskVolume1]\Recovery\WindowsRE\Winre.wim,{90bc5c93-737b-11e9-996f-a09de8f40a82} path \windows\system32\winload.exe description Windows Recovery Environment locale en-us inherit {bootloadersettings} displaymessage Recovery osdevice ramdisk=[\Device\HarddiskVolume1]\Recovery\WindowsRE\Winre.wim,{90bc5c93-737b-11e9-996f-a09de8f40a82} systemroot \windows nx OptIn bootmenupolicy Standard winpe Yes Windows Boot Loader ------------------- identifier {c1fd1f2c-4e45-11e4-af2d-448a5b917f86} device ramdisk=[C:]\Recovery\c1fd1f2c-4e45-11e4-af2d-448a5b917f86\Winre.wim,{c1fd1f2d-4e45-11e4-af2d-448a5b917f86} path \windows\system32\winload.exe description Windows Recovery Environment inherit {bootloadersettings} osdevice ramdisk=[C:]\Recovery\c1fd1f2c-4e45-11e4-af2d-448a5b917f86\Winre.wim,{c1fd1f2d-4e45-11e4-af2d-448a5b917f86} systemroot \windows nx OptIn winpe Yes Resume from Hibernate --------------------- identifier {90bc5c90-737b-11e9-996f-a09de8f40a82} device partition=C: path \Windows\system32\winresume.exe description Windows Resume Application locale en-US inherit {resumeloadersettings} recoverysequence {90bc5c92-737b-11e9-996f-a09de8f40a82} recoveryenabled Yes allowedinmemorysettings 0x15000075 filedevice partition=C: filepath \hiberfil.sys bootmenupolicy Standard debugoptionenabled No Windows Memory Tester --------------------- identifier {memdiag} device partition=\Device\HarddiskVolume1 path \boot\memtest.exe description Windows Memory Diagnostic locale en-US inherit {globalsettings} badmemoryaccess Yes EMS Settings ------------ identifier {emssettings} bootems No Debugger Settings ----------------- identifier {dbgsettings} debugtype Serial debugport 1 baudrate 115200 RAM Defects ----------- identifier {badmemory} Global Settings --------------- identifier {globalsettings} inherit {dbgsettings} {emssettings} {badmemory} Boot Loader Settings -------------------- identifier {bootloadersettings} inherit {globalsettings} {hypervisorsettings} Hypervisor Settings ------------------- identifier {hypervisorsettings} hypervisordebugtype Serial hypervisordebugport 1 hypervisorbaudrate 115200 Resume Loader Settings ---------------------- identifier {resumeloadersettings} inherit {globalsettings} Device options -------------- identifier {90bc5c93-737b-11e9-996f-a09de8f40a82} description Windows Recovery ramdisksdidevice partition=\Device\HarddiskVolume1 ramdisksdipath \Recovery\WindowsRE\boot.sdi Device options -------------- identifier {c1fd1f2d-4e45-11e4-af2d-448a5b917f86} description Ramdisk Options ramdisksdidevice partition=C: ramdisksdipath \Recovery\c1fd1f2c-4e45-11e4-af2d-448a5b917f86\boot.sdi C:\Windows\system32>wmic memorychip get manufacturer, capacity, partnumber, speed, memorytype, devicelocator, formfactor Capacity DeviceLocator FormFactor Manufacturer MemoryType PartNumber Speed 4294967296 A1_DIMM1 8 Undefined 24 EWB4GB681CA3-16IC 1600 4294967296 A1_DIMM3 8 Undefined 24 EWB4GB681CA3-16IC 1600 C:\Windows\system32>
(Inside the folder is a a Log Collector .zip file and then pictures of my Memtest Results)
https://drive.google.com/open?id=1IJ...NhzNCzRan3ecsH
There were no dump files collected when V2 was ran.
Today is 5/15 and the last BSOD displayed in the logs was 2019-05-14T14:36:15.241
After any BSOD immediately run V2 and upload into the thread.
And upload a separate share link for C:\windows\memory.dmp
Memtest has the option to view text reports. Please upload the text report.
Ill run another test tonight with 8 runs instead of 4. I have attached another BlueScreen Report from today, and the MEMORY.DMP is Uploading as i type this. ill get the Text Report as soon as possible
1) There was a recurrent misbehaving driver: rt640x64.sys
2) Turn off Windows updates of non-Microsoft drivers:
Enable or Disable Driver Updates in Windows Update in Windows 10
3) Uninstall and reinstall: rt640x64.sys
Make sure that the new driver is a version different from:
10.34.307.2019
10.7.107.2016
4) If there is a third recurrent misbehaving driver plan to use wireless.
Then uninstall the driver and do not use Ethernet.
Monitor the computer for stability/instability using only wireless.
5) Please post a share link when available for the memory dump:
Code:Crash dump found at C:\Windows\MEMORY.DMP Creation date: 05/15/2019 22:18:35 Size on disk: 924 MB
Code:Name [00000001] Realtek PCIe GbE Family Controller Adapter Type Ethernet 802.3 Product Type Realtek PCIe GbE Family Controller Installed Yes PNP Device ID PCI\VEN_10EC&DEV_8168&SUBSYS_81681849&REV_11\4&9B80F17&0&00AB Last Reset 5/15/2019 10:19 PM Index 1 Service Name rt640x64 IP Address 192.168.0.138, fe80::95e9:998c:f5b:e828 IP Subnet 255.255.255.0, 64 Default IP Gateway 192.168.0.1 DHCP Enabled Yes DHCP Server 192.168.0.1 DHCP Lease Expires 8/22/1932 6:10 PM DHCP Lease Obtained 8/21/1932 6:10 PM MAC Address 70:85:C2:B6:E9:35 I/O Port 0x0000D000-0x0000D0FF Memory Address 0xFE100000-0xFE100FFF Memory Address 0xD2100000-0xD2103FFF IRQ Channel IRQ 4294967294 Driver c:\windows\system32\drivers\rt640x64.sys (10.34.307.2019, 1.09 MB (1,141,744 bytes), 5/10/2019 4:01 PM)Code:rt640x64 Realtek RT640 NT Drive Realtek RT640 NT Drive Kernel Manual Running OK TRUE FALSE 4,096 1,085,440 0 3/7/2019 2:53:18 AM C:\Windows\system32\drivers\rt640x64.sys 8,192
Code:rt640x64 Realtek RT640 NT Driver c:\windows\system32\drivers\rt640x64.sys Kernel Driver Yes Manual Running OK Normal No YesCode:rt640x64.sys Wed Mar 6 23:53:18 2019 (5C80CDEE)
the setting was already off, i must've re installed it wrong, ill re install again and make sure its right, here is the MEMORY.DMP
MEMORY.DMP - Google Drive
- - - Updated - - -
i have the latest drivers, however im un sure how to install them manually because Device Manager will not pick them up form using the option "Browse this device" or whatever. And i dont want to mess up anything too bad.
Quote