New
#41
@Ztruker thanks! I will try that and let you know if I get another BSOD
@zbook Are you sure it's not on the list? The list I'm looking at has the model # for my RAM.
The currently installed RAM displayed in the log collector is: F4-3200C16-8GVKB
Code:Location : DIMM 1 BankLabel : P0 CHANNEL A Manufacturer : Unknown MemoryType : DDR4 FormFactor : DIMM Capacity : 8GB Speed : 3200 Serial : 00000000 PartNumber : F4-3200C16-8GVKB ECC : False TypeDetail : {Synchronous, Unbuffered (Unregistered)} Location : DIMM 1 BankLabel : P0 CHANNEL B Manufacturer : Unknown MemoryType : DDR4 FormFactor : DIMM Capacity : 8GB Speed : 3200 Serial : 00000000 PartNumber : F4-3200C16-8GVKB ECC : False TypeDetail : {Synchronous, Unbuffered (Unregistered)}
Hmm that's weird. The F4-3200C16D-8GVKB is the model number for the 2x4GB RAM from GSkill. I have the 2x8 RAM installed (as you can probably see my system has 16GB of RAM) which is on the QVL as F4-3200C16D-16GVKB. Is it possible the log reader or my computer is reading it wrong?
Either way I am sending in my old RAM that had an error (which we thought was causing the BSODs) for a replacement so once that comes in I can try to swamp them out to see if it fixes the situation. They prob won't come in for 1-2 weeks though.
Not sure if this is helpful but here's my results from the Memtest that I did today:
Open administrative command prompt and copy and paste:
Code:wmic memorychip get manufacturer, capacity, partnumber, speed, memorytype, devicelocator, formfactor
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
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 }
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
Microsoft Windows [Version 10.0.19041.388]
(c) 2020 Microsoft Corporation. All rights reserved.
C:\Windows\system32>wmic memorychip get manufacturer, capacity, partnumber, speed, memorytype, devicelocator, formfactor
Capacity DeviceLocator FormFactor Manufacturer MemoryType PartNumber Speed
8589934592 DIMM 1 8 Unknown 0 F4-3200C16-8GVKB 2133
8589934592 DIMM 1 8 Unknown 0 F4-3200C16-8GVKB 2133
Memore Modules:
Tag BankLabel Capacity(GB) Manufacturer PartNumber Speed
--- --------- ------------ ------------ ---------- -----
Physical Memory 1 P0 CHANNEL A 8 Unknown F4-3200C16-8GVKB 2133
Physical Memory 3 P0 CHANNEL B 8 Unknown F4-3200C16-8GVKB 2133
Total Memory:
16GB
Total Memory Slots:
4
Used Memory Slots:
2
Memtest86 can test for malfunctioning RAM.
It does not test for incompatible RAM.
So install MSI tested (comptible RAM).
If the computer environment becomes stable then you're set.
If there are unexpected shutdowns and restarts more testing will be performed.
Hey guys, my new RAM finally came in. After about 30 minutes of Netflix and playing runescape (my runescape crashed multiple times) i recived another BSOD. Memory Dump and Log attached. Also here is the info on the new RAM.
Capacity DeviceLocator FormFactor Manufacturer MemoryType PartNumber Speed
8589934592 DIMM 1 8 Unknown 0 CMK16GX4M2B3000C15 2133
8589934592 DIMM 1 8 Unknown 0 CMK16GX4M2B3000C15 2133
Mem Dump.zip - Google Drive
What are the next steps?
Lets try Driver Verifier again.
Run Driver Verifier
Driver Verifier-- tracking down a mis-behaving driver.
Following the instructions in the above link will check for problems in all non-Microsoft drivers.
What we're looking for is a verifier generated BSOD with a mini dump that will tell us what driver caused it. If you get a BSOD, rerun the V2 log collector as soon as possible and upload the resulting zip file. Also see if there is a new C:\Windows \MEMORY.DMP file. If there is, copy it to another location then zip it an upload to a file sharing site like OneDrive and post a link to it here.
To check if verifier is active, open a Command Prompt and enter:
verifier /query
If not active it will respond with
No drivers are currently verified.
If you have questions, see this additional tutorial which may help to clear things up.
Enable and Disable Driver Verifier in Windows 10 <-- take a good look at this tutorial too
Sorry for the delay. I was traveling for work. I have been running driver verfier for about 7 hours now and got many BSODs but none of them, were created by the verifer. Any ideas on next steps?
Mem Dump:
Mem Dump.zip - Google Drive