Bluescreening with XMP enabled.

Puppetmaster

Puppetmaster

Puppetmaster

Soldato
Joined
17 Jun 2005
Posts
6,514
Location
Near Brighton
Upgraded my PC 2 weeks ago. Running this:

5930K @ Stock
Rampage V Extreme
16GB Kingston Predator 2666MHz https://www.overclockers.co.uk/showproduct.php?prodid=MY-201-KS&groupid=701&catid=8&subcat=2554

When it is running @ 2133 with defaults in BIOS I have no issues. If I set XMP profile for 2666 or even 2400 my PC will bluescreen pretty quickly.

I tried upping the voltage to 1.36 (auto seemed to be around 1.34) but no change (I'm unsure of what is safe voltage for DDR4)

Can anyone help? I've not used XMP as my previous board didn't have it but I thought it was pretty much set it and go.
 
With XMP you should just be able to set it at the XMP profile then leave it, send it back and get it replaced if it's not stable using it's XMP profile.
 
thebennyboy said:
With XMP you should just be able to set it at the XMP profile then leave it, send it back and get it replaced if it's not stable using it's XMP profile.
Click to expand...


Sorry but this is misinformation.

XMP is the memory profile programmed in to serial presence detect (SPD) in order for the user to apply the memory's binned timings.

It's a huge common misconception that XMP should 'just work' out of the box but it simply isn't true. When surpassing 2133 on X99 you are in effect overclocking, and thus although the memory has been binned for the XMP speed you are applying - you are putting extra strain on the CPU's memory controller and other components and tuning may be required by the user.

You need to be looking at System Agent voltage which is the voltage for the memory controller. Using the offset function aim for a final voltage of between 1.05 - 1.15. X99 overclocking is slightly more cantankerous than previous platforms due to the nature of VCCSA (system agent) on this platform. It has what is best described as dead spots, and occasionally auto parametrises will not work as desired.
 
+1

its only a saved profile stored on the ram,it doesn't take into account the cpu's varying imc/voltage ect

with 16gb and above you'll probably need more memory controller voltage
 
Reset Bios.
Boot
Into Bios
Set XMP, make sure for 2666mhz you are on 125 strap this is native multi. When you set XMP this should be set automatically.
Then set 32 multi for 4g
Cache 26 or similar so as to keep this in check.
Then
Core 1.2
Cache 1.2
SA 1.15
Vccin 1.85
Memory volts 1.35

In digi power set all the memory power delivery to optimised and maybe level 6 LLC.

Test.

XMP is not guaranteed to work no.... although at 2666 should be fine. But Intel give out XMP Certification to DDR4 3200 and 3000 for example which often don't even work on the socket they certify. So go figure.....
 
Last edited:
8 Pack said:
Reset Bios.
Boot
Into Bios
Set XMP, make sure for 2666mhz you are on 125 strap this is native multi. When you set XMP this should be set automatically.
Then set 32 multi for 4g
Cache 26 or similar so as to keep this in check.
Then
Core 1.2
Cache 1.2
SA 1.15
Vccin 1.85
Memory volts 1.35

In digi power set all the memory power delivery to optimised and maybe level 6 LLC.

Test.

XMP is not guaranteed to work no.... although at 2666 should be fine. But Intel give out XMP Certification to DDR4 3200 and 3000 for example which often don't even work on the socket they certify. So go figure.....
Click to expand...

Thanks for those settings 8 Pack, will try those tomorrow :)

Managed to get it stable initially by dropping the timings by 1 and upping the system agent voltage.
 
Pay attention to these timings in Bios for stability.
TRFC
TWCL

Also CLK De emphasis Voltage will help with Memory stability try about 1.28v
 
thebennyboy said:
With XMP you should just be able to set it at the XMP profile then leave it, send it back and get it replaced if it's not stable using it's XMP profile.
Click to expand...

XMP can't take into consideration the memory controller on the CPU, the quality of voltage given to the chips by every single board etc..
 
Actually with X99 often its nothing to even do with IMC just simple fact does MB have OC socket or not!!

If you don't have voltage to the extra pins no matter what you do 3000+ mhz difficult stable.
 
Most if not dare I say close to all samples should be able to achieve 3000mhz DRAM frequency of some description if the memory modules are capable. As Pack says it comes down to the motherboard and whether it's equipped with OCsocket pins to provide the additional power. VCCSA should only really be adjusted if all else fails, it's not always a case of the IMC needing much additional voltage, more that it becomes more compliant at the desired frequency and timings at a specific voltage. Simply dialing in huge amount of SA doesn't normally help.

As an example my sample at 3200Mhz likes around 1.03v System Agent at the desired timings. Above 1.06v the memory becomes unstable.
 
Last edited:
Sorry to bump an old thread.

I never really got around to getting the RAM working @ 2666 and overclocking but have just started again.

I followed the settings in 8 packs above post. With those settings it would give me an IRQL error just after boot. Tried slightly changing a few things but nothing helped. I then decided to set cpu ratio to auto (thinking it would go back to stock) but it changed it to x37 @ 125 (giving 4.6GHz). I had also set the CPU Cache to auto as well. System seemed more stable, could actually run games but it eventually bluescreened on me.

I have tried upping cpu voltage to 1.25, changing cpu overclock, slightly upping all of the other voltages but nothing is helping. I am also running 1701 bios.

Any suggestions? Below are the bluescreens I am getting

On Fri 18/12/2015 23:47:35 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: Unknown (0xFFFFFA8C03EF1F54)
Bugcheck code: 0xA (0xFFFFFA8C03EF1F54, 0x2, 0x1, 0xFFFFF800EBA6F56C)
Error: IRQL_NOT_LESS_OR_EQUAL

On Fri 18/12/2015 20:05:16 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\121815-15484-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F4D0)
Bugcheck code: 0xA (0xFFFFFA8C04FE8AB4, 0x2, 0x1, 0xFFFFF803CE2CB56C)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\ntoskrnl.exe
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom