Could RAM overclock cause screen flickering/black screens?

[mrfrank]

Hello everyone,
I am a new OC enthusiastic and this is my first thread! Nice to meet you all guys!

So first question, I got OC'ed my CPU, GPU at a stable level and now I moved on with RAM OC. I have the following sticks: Corsair Vengeance LPX DDR4 2400 C14 2x8G and by default they are running on 2133 14 16 16 31 and 1.20V, so I changed the values to 2200 13 15 15 30 and 1T without changing the voltages at all. I run a memtest and had no errors, and also was playing games for more than 3 hours without a single error/crash. However today and while I was running my Virtual Machine my screen went black for less than 1 second and then turned on by itself. I was wondering, could RAM overclock cause this issue? Did it happen because of the "not increased voltages"?
Note: I had the same issue with my previous overclock but I reverted everything and changed HDMI cable so I don't know what was causing the issue before. However with my current OC it happened only 1 time within 3 or 4 hours of running.

Thank you

[kkn]

activate xmp in bios.(this if running intel).
then the ram will go to the stated mhz its rated to.

[mrfrank]

kkn wrote:
activate xmp in bios.(this if running intel).
then the ram will go to the stated mhz its rated to.

Already done that and im getting bsod after a while. I have tried memtest also and there is no error shown at all. I am very confused.

[HiVizMan]

If you look at the OS event log do you have errors listed? That will give you a clue as to what is the cause.

Short answer yes, memory can impact on all aspects of a system

[mrfrank]

This is the latest Critical Level Event I have from the BSOD I received (that time I was running on same CPU OC, GPU OC and I had changed my RAM's command rate only from 2T to 1T, all rest timers were at stock values and frequency at 2133)

Source: Kernel-Power
Event ID: 41
BugcheckCode 26 
BugcheckParameter1 0x41201 
BugcheckParameter2 0xffffaf8131c4b300 
BugcheckParameter3 0x81000003f69df847 
BugcheckParameter4 0xffffc88f0c00c270 

After that I reverted command rate to 2T and ran an 8h stress test with RealBench which was ended successfully without any crash, however HWiNFO shows some errors while CPU is IDLE right now:
http://prntscr.com/lizkjb
And here is the event log from Application and Service Logs - Microsoft - Windows - Kernel-WHEA - Errors:
Note: Before stress test there were no WHEA errors at all, and I am pretty sure that If I reboot my PC now they won't be there. I am also running on latest BIOS UPDATE of my mobo ASUS Z170-A

Log Name: Microsoft-Windows-Kernel-WHEA/Errors
Source: Microsoft-Windows-Kernel-WHEA
Date: 15/11/2018 9:24:09 μμ
Event ID: 20
Task Category: None
Level: Information
Keywords: WHEA Error Events
User: SYSTEM
Computer: DESKTOP-6UJ7ESS
Description:
WHEA Event
Event Xml:



20
0
4
0
0
0x4000000000000800

373


Microsoft-Windows-Kernel-WHEA/Errors
DESKTOP-6UJ7ESS



864
435045521002FFFFFFFF0300020000000200000060030000091813000F0B12140000000000000000000000000000000000000000000000000000000000000000BDC407CF89B7184EB3C41F732CB57131B18BCE2DD7BD0E45B9AD9CF4EBD4F890BAFA4D26DC7CD40100000000000000000000000000000000000000000000000058010000C00000000003000001000000ADCC7698B447DB4BB65E16F193C4F3DB0000000000000000000000000000000002000000000000000000000000000000000000000000000018020000400000000003000000000000B0A03EDC44A19747B95B53FA242B6E1D0000000000000000000000000000000002000000000000000000000000000000000000000000000058020000080100000003000000000000011D1E8AF94257459C33565E5CC3F7E80000000000000000000000000000000002000000000000000000000000000000000000000000000057010000000000000002080000000000E30605000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000600000000000000000000000000000000000000000000000000000000000000000000000000000003000000000000000600000000000000E306050000081006BFFBFA7FFFFBEBBF00000000000000000000000000000000000000000000000000000000000000000200000001000000DADA60C8187DD4010600000000000000000000000000000000000000000000000500010040000090000000000000000000000000000000000000000006000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000

[HiVizMan]

Memory issues.

As to the exact location or cause of those issues that we can determine. Go back to the last settings that you had that were solid. Run some of the memory stressing software at that stable setting, pass and make one change repeat the stress test and that way identify the cause by when you see the first error.

[mrfrank]

HiVizMan wrote:
Memory issues.

As to the exact location or cause of those issues that we can determine. Go back to the last settings that you had that were solid. Run some of the memory stressing software at that stable setting, pass and make one change repeat the stress test and that way identify the cause by when you see the first error.

I reverted RAM to its stock timers and everything, and today while I was working I got a BSOD with the following code:
WHEA_UNCORRECTABLE ERROR

 BugcheckCode 292 
  BugcheckParameter1 0x0 
  BugcheckParameter2 0xffff878de0ace028 
  BugcheckParameter3 0xbe000000 
  BugcheckParameter4 0x800400 
  SleepInProgress 0 
  PowerButtonTimestamp 0 
  BootAppStatus 0 
  Checkpoint 0 
  ConnectedStandbyInProgress false 
  SystemSleepTransitionsToOn 0 
  CsEntryScenarioInstanceId 0 
  BugcheckInfoFromEFI false 
  CheckpointStatus 0 

So my next move was to increase CPU Voltage by 0.05. Currently running on Adaptive 1.34 and 4.6Ghz on my I7 6700k. Maybe my CPU OC was not so stable afterall even if it passed almost all benchmarks. Let's see...

[Silent_Scone]

mrfrank wrote:
I reverted RAM to its stock timers and everything, and today while I was working I got a BSOD with the following code:
WHEA_UNCORRECTABLE ERROR

 BugcheckCode 292 
  BugcheckParameter1 0x0 
  BugcheckParameter2 0xffff878de0ace028 
  BugcheckParameter3 0xbe000000 
  BugcheckParameter4 0x800400 
  SleepInProgress 0 
  PowerButtonTimestamp 0 
  BootAppStatus 0 
  Checkpoint 0 
  ConnectedStandbyInProgress false 
  SystemSleepTransitionsToOn 0 
  CsEntryScenarioInstanceId 0 
  BugcheckInfoFromEFI false 
  CheckpointStatus 0 

So my next move was to increase CPU Voltage by 0.05. Currently running on Adaptive 1.34 and 4.6Ghz on my I7 6700k. Maybe my CPU OC was not so stable afterall even if it passed almost all benchmarks. Let's see...

WHEA is normally insufficient vcore, yes. Please note that stock for memory is defaults (2133MHz), and not XMP settings. I'd recommend increasing vcore by 20mV, though.

[HiVizMan]

I have very definite views of stress tests and stuff like that. All passing those kinds of things show is that your system has passed THAT test and THAT time. There is no certainty that the system will do so again. Focus on the word certainty. Electronics just defy logic sometimes.

So it is very possible that your overclock was not as stable. Easy to test of course.

Go into your profile and save these settings as a profile. You can always load from the saved profiles later when you want to. If you want to.

OK once you have done that. System to defaults, yip you heard me. LOL Full default settings.

Run your machine for a while check for errors and if none then you know it was a setting change that played a role in the error.

We can work from that. This is only a test to determine if it is hardware (and needs attention) or something introduced, in other words a setting change.

[mrfrank]

HiVizMan wrote:
I have very definite views of stress tests and stuff like that. All passing those kinds of things show is that your system has passed THAT test and THAT time. There is no certainty that the system will do so again. Focus on the word certainty. Electronics just defy logic sometimes.

So it is very possible that your overclock was not as stable. Easy to test of course.

Go into your profile and save these settings as a profile. You can always load from the saved profiles later when you want to. If you want to.

OK once you have done that. System to defaults, yip you heard me. LOL Full default settings.

Run your machine for a while check for errors and if none then you know it was a setting change that played a role in the error.

We can work from that. This is only a test to determine if it is hardware (and needs attention) or something introduced, in other words a setting change.

Today I was playing games for more than 5 hours without any crash and when I finished and opened my Virtual Machine in order to work I came up with a bsod again after 40 minutes or so. This time the bsod was different though so I am wondering if the Virtual Machine engine is causing my issues.
Here is the new error:
SYSTEM_SERVICE_EXCEPTION
Kernel-Power
Event ID: 41
Task Category: 63

BugcheckCode 59 
BugcheckParameter1 0xc0000005 
BugcheckParameter2 0xfffff803567943f9 
BugcheckParameter3 0xffff83006c0be740 

Also I installed BlueScreenView app which shows me this on error's properties:
http://prntscr.com/lj8h1c
According to google Intel(R) Gigabit Adapter NDIS 6.x driver is the driver of my ethernet so I am very very confused now..

So I am guessing this error/bsod is different and have nothing to do with my OC? Also it's very weird that it only happens when my Virtual Machine is running and I am working and not while I am doing other stuff on my PC like gaming or watching videos or even stress testing for 8 hours+