F5F Stay Refreshed Power Users Overclocking i7 4790K & XMP Profile for Corsair Vengeance 2400MHz leads to BSOD issues.

i7 4790K & XMP Profile for Corsair Vengeance 2400MHz leads to BSOD issues.

i7 4790K & XMP Profile for Corsair Vengeance 2400MHz leads to BSOD issues.

Pages (2): 1 2 Next
N
Noctaflo
Member
118
04-06-2016, 09:00 PM
#1
Hi there, I just received a pair of 2 x 8gb Corsair Vengeance 2400MHz RAM for my Z97 system (i7 4790K with Gigabyte Z97 D3H). I turned on XMP and noticed a noticeable performance improvement in Flight Simulator (P3D) by around 20 FPS. It's hard to believe how much better it felt. Everything was fine for about 20 minutes until a BSOD appeared. I then reduced the XMP profile back to 1333MHz and restarted. After that, I attempted a manual overclock to 2000MHz, which lasted longer—about 40 minutes—and was more stable. Since I'm new to RAM overclocking, I'm looking for guidance to achieve stability at 2000MHz, especially since there didn't seem to be a significant difference between 2000MHz and 2400MHz on my machine. Thanks!
N
Noctaflo
04-06-2016, 09:00 PM #1

Hi there, I just received a pair of 2 x 8gb Corsair Vengeance 2400MHz RAM for my Z97 system (i7 4790K with Gigabyte Z97 D3H). I turned on XMP and noticed a noticeable performance improvement in Flight Simulator (P3D) by around 20 FPS. It's hard to believe how much better it felt. Everything was fine for about 20 minutes until a BSOD appeared. I then reduced the XMP profile back to 1333MHz and restarted. After that, I attempted a manual overclock to 2000MHz, which lasted longer—about 40 minutes—and was more stable. Since I'm new to RAM overclocking, I'm looking for guidance to achieve stability at 2000MHz, especially since there didn't seem to be a significant difference between 2000MHz and 2400MHz on my machine. Thanks!

C
craej
Junior Member
17
04-14-2016, 08:40 AM
#2
Review your MB manual. It usually suggests a particular memory configuration (for example, using black slots for two sticks in dual channel). What settings are available on the VTTDDR in the BIOS? Is it set to auto? Regarding the CPU voltage, since you're overclocking the memory, you'll need to provide more power—those two parameters manage that. You might also find this guide helpful:
C
craej
04-14-2016, 08:40 AM #2

Review your MB manual. It usually suggests a particular memory configuration (for example, using black slots for two sticks in dual channel). What settings are available on the VTTDDR in the BIOS? Is it set to auto? Regarding the CPU voltage, since you're overclocking the memory, you'll need to provide more power—those two parameters manage that. You might also find this guide helpful:

P
PemahiXD007YT
Member
120
04-14-2016, 09:16 AM
#3
Post images from CPU-Z. Look for any BIOS updates that might resolve the issue. If the problem continues, run MEMTEST86 to eliminate faulty memory modules. It's odd the BSOD appears on a timer—verify your temperatures and share the BSOD message. There may be an app that keeps the BSOD active until you provide input, allowing you to capture it. Also, confirm the XML profile includes the manufacturer's timing specifications; if not, manually adjust them in the BIOS.
P
PemahiXD007YT
04-14-2016, 09:16 AM #3

Post images from CPU-Z. Look for any BIOS updates that might resolve the issue. If the problem continues, run MEMTEST86 to eliminate faulty memory modules. It's odd the BSOD appears on a timer—verify your temperatures and share the BSOD message. There may be an app that keeps the BSOD active until you provide input, allowing you to capture it. Also, confirm the XML profile includes the manufacturer's timing specifications; if not, manually adjust them in the BIOS.

J
joshuacl9
Junior Member
16
04-16-2016, 03:34 AM
#4
blacknemesist :
Can you post images from CPU-Z?
Check if there are any bios updates for your MB that fix the problem.
If problem presists run MEMTEST86 to rule out faulty memory sticks.
It is weird that the BSOD is on a timer. Check your temps and give us the message from the BSOD. There is an application that will keep the BSOD showing until you input something so you can take a picture of it.
Also check if the XML profile has the timings that the manufacture provided, if they are different manually set them in the bios.
Hi, I updated to the most recent Bios update today and I had no luck. As for CPU-Z I checked everything thing earlier including the voltages and they were set as instructed by the XMP profile with the correct timings aswell. This also matched up with what I was seeing in the Bios.
The errors from the BSODs tend to be "MEMORY_MANAGEMENT" It's also not that the BSODs were on timers it was just usually what I got to when I applied 2000MHz and I only got around 15 minutes with the XMP.
I will start with MEMTEST86 and see where I go from there. Many Thanks
J
joshuacl9
04-16-2016, 03:34 AM #4

blacknemesist :
Can you post images from CPU-Z?
Check if there are any bios updates for your MB that fix the problem.
If problem presists run MEMTEST86 to rule out faulty memory sticks.
It is weird that the BSOD is on a timer. Check your temps and give us the message from the BSOD. There is an application that will keep the BSOD showing until you input something so you can take a picture of it.
Also check if the XML profile has the timings that the manufacture provided, if they are different manually set them in the bios.
Hi, I updated to the most recent Bios update today and I had no luck. As for CPU-Z I checked everything thing earlier including the voltages and they were set as instructed by the XMP profile with the correct timings aswell. This also matched up with what I was seeing in the Bios.
The errors from the BSODs tend to be "MEMORY_MANAGEMENT" It's also not that the BSODs were on timers it was just usually what I got to when I applied 2000MHz and I only got around 15 minutes with the XMP.
I will start with MEMTEST86 and see where I go from there. Many Thanks

_
_Jill
Junior Member
29
04-17-2016, 10:51 PM
#5
blacknemesist :
Can you share images from CPU-Z?
Look for any BIOS updates that might resolve the issue.
If the problem persists, try running MEMTEST86 to eliminate faulty memory modules.
It’s odd that the BSOD appears on a timer—verify your temperatures and provide the error message.
There’s an app that can keep the BSOD active until you input something, allowing you to capture it.
Also, confirm if the XML profile includes the manufacturer’s timing specifications; if not, manually adjust them in the BIOS.
I completed Memtest86 and everything showed no errors. This shouldn’t be a hardware problem, just a technique issue.
Do you have any suggestions about why XMP or evening settings like 2000MHz might be unstable? Could it be related to your voltage?
_
_Jill
04-17-2016, 10:51 PM #5

blacknemesist :
Can you share images from CPU-Z?
Look for any BIOS updates that might resolve the issue.
If the problem persists, try running MEMTEST86 to eliminate faulty memory modules.
It’s odd that the BSOD appears on a timer—verify your temperatures and provide the error message.
There’s an app that can keep the BSOD active until you input something, allowing you to capture it.
Also, confirm if the XML profile includes the manufacturer’s timing specifications; if not, manually adjust them in the BIOS.
I completed Memtest86 and everything showed no errors. This shouldn’t be a hardware problem, just a technique issue.
Do you have any suggestions about why XMP or evening settings like 2000MHz might be unstable? Could it be related to your voltage?

B
174
04-25-2016, 04:59 PM
#6
Yes, voltage might be an issue. Review the XMP profile and verify that the timings and voltage match the values on the Corsair RAM webpage. I encountered the same issue with my g.skill RAM, where the MB loaded a different XMP profile with varying timings. You can adjust them manually if they don't align with the BIOS settings.
B
BudderKing0428
04-25-2016, 04:59 PM #6

Yes, voltage might be an issue. Review the XMP profile and verify that the timings and voltage match the values on the Corsair RAM webpage. I encountered the same issue with my g.skill RAM, where the MB loaded a different XMP profile with varying timings. You can adjust them manually if they don't align with the BIOS settings.

K
KoKo_OJ
Member
206
04-30-2016, 11:38 AM
#7
Blacknemesist:
Yes, voltage might be an issue. Look at the XMP profile and verify if the timings and voltage match the Corsair RAM webpage. I faced the same problem with my g.skill RAM, which had a different XMP profile with varied timings. You can adjust them manually if they don’t match on the BIOS.

Hi again, I checked before and could only select 1.64 and 1.66 volts. My kit is rated at 1.65, so I chose 1.66 earlier and double-checked all the timers too. I’ll try again soon and will share the results later. Thanks. 😀
K
KoKo_OJ
04-30-2016, 11:38 AM #7

Blacknemesist:
Yes, voltage might be an issue. Look at the XMP profile and verify if the timings and voltage match the Corsair RAM webpage. I faced the same problem with my g.skill RAM, which had a different XMP profile with varied timings. You can adjust them manually if they don’t match on the BIOS.

Hi again, I checked before and could only select 1.64 and 1.66 volts. My kit is rated at 1.65, so I chose 1.66 earlier and double-checked all the timers too. I’ll try again soon and will share the results later. Thanks. 😀

G
Gamergirl073
Member
112
04-30-2016, 07:51 PM
#8
have you experimented with different settings and adjusted it to 1.64? also SPECCY can be helpful for this issue—run it, check your PC's memory section, and you'll see a table of possible XMP values on the chips, which could guide you toward what the Corsair RAM recommends.
G
Gamergirl073
04-30-2016, 07:51 PM #8

have you experimented with different settings and adjusted it to 1.64? also SPECCY can be helpful for this issue—run it, check your PC's memory section, and you'll see a table of possible XMP values on the chips, which could guide you toward what the Corsair RAM recommends.

M
MrAsePlow
Member
52
05-01-2016, 04:00 AM
#9
Have you considered adjusting the settings differently and setting it to 1.64? Also, SPECCY might be helpful here—run it and check the memory section of your PC; it should show possible XMP values from the chips themselves, which could help align it with what the Corsair RAM requires.
Example below my RAM setup.
Yes, I've tried 2000MHz at 1.64 and had no success. I'll try SPECCY now and will update later. Thanks.
M
MrAsePlow
05-01-2016, 04:00 AM #9

Have you considered adjusting the settings differently and setting it to 1.64? Also, SPECCY might be helpful here—run it and check the memory section of your PC; it should show possible XMP values from the chips themselves, which could help align it with what the Corsair RAM requires.
Example below my RAM setup.
Yes, I've tried 2000MHz at 1.64 and had no success. I'll try SPECCY now and will update later. Thanks.

D
Dementus
Member
87
05-01-2016, 05:13 AM
#10
Have you considered adjusting the settings differently and setting it to 1.64? Also, SPECCY might be helpful here—run it and check the memory section of your PC, which will show possible XMP values from the chips themselves, potentially guiding you closer to what the Corsair RAM requires.
D
Dementus
05-01-2016, 05:13 AM #10

Have you considered adjusting the settings differently and setting it to 1.64? Also, SPECCY might be helpful here—run it and check the memory section of your PC, which will show possible XMP values from the chips themselves, potentially guiding you closer to what the Corsair RAM requires.

Pages (2): 1 2 Next