You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Like many others in the DDR5 overclocking space, I've used y-cruncher's VST stress test to help validate the stability of the IMC during RAM overclocks. The stress test is invaluable with how fast it catches errors in voltage configurations and it has become part of my stability testing regiment as a result. I've seen many recommend VT3 as an even more effective RAM stress testing tool, but a change made in v0.8.1.9517 has made VT3 somewhat more troublesome to use.
Up to v0.7.10.9513, upon failure, y-cruncher gives this message:
However, on failure from v0.8.1.9517, I get this message:
To my knowledge, the newer versions (all the ones containing VT3) only show the Test Speed upon failure instead of the Test Duration, meaning that I can't get a precise read as to when a failure occurs. Knowing how far into a run that a test fails is super important for gauging the stability and for seeing whether a change in the OC has a positive or negative effect, and while looking at the iteration count can provide a rough estimate as to the time of failure, the only way to get an exact time of failure on a version after v0.7.x is to manually try to time the runtime externally, a setup that's much less user friendly.
I understand the importance of the Test Speed metric and why it has been added, but would it be possible to at least add a setting that allows you to show both Test Speed and Test Duration upon failure or a setting to switch between the two?
The text was updated successfully, but these errors were encountered:
Like many others in the DDR5 overclocking space, I've used y-cruncher's VST stress test to help validate the stability of the IMC during RAM overclocks. The stress test is invaluable with how fast it catches errors in voltage configurations and it has become part of my stability testing regiment as a result. I've seen many recommend VT3 as an even more effective RAM stress testing tool, but a change made in v0.8.1.9517 has made VT3 somewhat more troublesome to use.
Up to v0.7.10.9513, upon failure, y-cruncher gives this message:
However, on failure from v0.8.1.9517, I get this message:
To my knowledge, the newer versions (all the ones containing VT3) only show the Test Speed upon failure instead of the Test Duration, meaning that I can't get a precise read as to when a failure occurs. Knowing how far into a run that a test fails is super important for gauging the stability and for seeing whether a change in the OC has a positive or negative effect, and while looking at the iteration count can provide a rough estimate as to the time of failure, the only way to get an exact time of failure on a version after v0.7.x is to manually try to time the runtime externally, a setup that's much less user friendly.
I understand the importance of the Test Speed metric and why it has been added, but would it be possible to at least add a setting that allows you to show both Test Speed and Test Duration upon failure or a setting to switch between the two?
The text was updated successfully, but these errors were encountered: