I was doing a RAM upgrade for a friend tonight, and in all my >10 years in computer support I've never had such confusing issues.
Current RAM: HX421C14FBK2/8 Kingston HyperX Fury 8GB Kit - 2x4GB
New Ram: HX421C14FBK2/8 (same)
The only difference is the revision numbers. The new ram says 059.A00LF while the old ram was 035 or something in the 03x range. Visually, they are identical.
Placing the RAM in the PC is fine. Bios reports 16GB of ram.
The only thing I noticed different in BIOS were the memory stats for Channel A being 1 number different from Channel B.
The tWTR was 4 on one channel, and 5 on the other if memory serves correctly.
Now the issue:
Windows 10 is not happy and bluescreens on any and all attempts to boot, be it in automated recovery or standard boot modes.
Bluescreens have random messages. Sometimes Kernel errors, sometimes IRQL, sometimes memory management, etc etc.
This only happens when the old RAM and the new RAM are mixed... which is odd, because they are the same model numbers.
This build is not even 1 year old, so I wouldn't imagine that the box of new ram will have changed so much that it's incompatible!
I did windows memory diagnostics with just the two new sticks in (and on the two new slots), and everything was fine.
I tested ram in all slots and in all combinations.
Everything is fine until I insert 1 or more of the new ram sticks in combination with the old.
The system is even fine running the new ram alone in slots 1 & 3 (Channel A) or in slots 2 & 4 (Channel B ).
The only thing that causes an issue is when the new and old RAM are mixed.
I tried changing the tWTR timing on the new ram to be 1 unit slower to match the stats of the old ram, and that doesn't help either.
No BIOS updates exist for this motherboard, and Windows 10 is fully up-to-date.
Does anyone have any advice on how to get this working?
I don't have the PC with me now, but I can go back and try some things.
I wouldn't like to return the RAM, as I believe it is not faulty, nor is the motherboard. Every stick of ram works fine in every slot until they are mixed...
I have yet to run a memtestx86 or ubuntu boot disk with all ram inside... that is the next step... but that's probably not going to resolve the windows issues.
Edit: Attached memory dumps and BlueScreenView report
After cross-referencing the bug check codes with the documentation on the MSDN
The following errors were found matching from the parameters:
- The allocation bitmap is corrupt. The memory manager is about to overwrite a virtual address that was already in use.
- A memory access violation occurred
Edited by hamluis, 13 October 2016 - 02:29 PM.
Moved from Internal Hardware to Crashes/BSODs - Hamluis.