Is this a memory issue ?

Associate
Joined
25 Jan 2012
Posts
14
Hi , i have just put together a new build but i am having real problems doing a clean install of the Windows 10 operating system . The install keeps failing at the second stage between 20% and 45% usually with a blue screen but with varying different stop codes e.g
IRQL NOT LESS OR EQUAL
KERNAL SECURITY CHECK FAILURE
SYSTEM SERVICE EXCEPTION
MEMORY CACHE
The build is

GIGABYTE AORUS ELITE X570 with bios q flashed to f11
CPU AMD RYZEN 5 3600X
POWER COLOR RADEON RX 590 RED DRAGON
PATRIOT VIPER STEEL 16gb ( 2x8gb) dual channel ddr4 3600mhz
M2 SAMSUNG 500GB 970 EVO PLUS
650W SEASONIC PLATINUM POWER SUPPLY
NXT H510i MIDI TOWER CASE

The install disc is from genuine windows 10 home purchased at overclockers and i have also tried a downloaded usb install from microsoft so unless both are corrupted it surely cannot be software .
I was trying to install on a new M2 nvme 500gb samsung 970 evo plus but also tried a 120gb ssd sata drive with same results with only one of these drives connected in at any one time .
I think i have set up the memory correctly and is showing in bios xmp profile 1 as correct ram speed and capacity . Is there something i could have missed as its been a while since i did a build and things seem to have moved on at a pace .
Any help would be much appreciated .
 
Hi and welcome,

Try and install with just 1 stick of ram (check the manual for the correct slot to use), if that fails then try the other stick on its own, if that sorts it out then you could have a faulty stick of ram :)
 
Hi thanks for your welcome and your reply . I did try with one of the sticks removed but don't think i tried swapping them over . I will give that a try thanks , unfortunately i may not get to try until Sunday night . I have got the two sticks in A2 and B2 at present as per manual .
 
Hi thanks for your welcome and your reply . I did try with one of the sticks removed but don't think i tried swapping them over . I will give that a try thanks , unfortunately i may not get to try until Sunday night . I have got the two sticks in A2 and B2 at present as per manual .
Also it's worth trying single sticks in different slots to rule out faulty motherboard slots?
 
Hi , just thought I would add an update . Turns out I do have a faulty A2 motherboard slot . I tried both sticks individually in A2 with same fault code results . Populated A1 and B1 and installation went through without a problem . So looks like i am going to have to return the motherboard unfortunately.
Once again thanks for your help in getting to the bottom of the problem .
 
Last edited:
Hi , just thought I would add an update . Turns out I do have a faulty A2 motherboard slot . I tried both sticks individually in A2 with same fault code results . Populated A1 and B1 and installation went through with a problem . So looks like i am going to have to return the motherboard unfortunately.
Once again thanks for your help in getting to the bottom of the problem .
Glad you've found the problem :)
 
Well it seems I was a little premature in declaring my problem solved .
I installed the new motherboard yesterday ( same Aorus elite model ) . I haven't done a windows 10 reinstall but updated the flash and enabled the xmp for the memory modules in slots A2 and B2 .
All looked good until I tried to load updates and applications and again I keep getting blue screen shutdowns and reboots . Seems like the memory is again unstable . Just did a quick windows memory test and almost instantly " hardware problems were detected " message appeared and recovery failed .
I'm going to try swapping sticks around later today but is there anything I could have missed .. voltages I should check ?
 
Update ..
I swapped the two memory sticks into A1 B1 slots and the windows mem test seemed happy .
But I noticed that even though xmp is enabled the memory is only being shown as 2137MHz?
When installed in slot A2 B2 it was shown as 3600MHz could this be the issue ?
I will post in the motherboard section of the forums as I think this is where the issue lies and not so much with the memory .
 
Back
Top Bottom