XMP Profile 1 experiences issues on the Kingston Fury Renegade 7200.
XMP Profile 1 experiences issues on the Kingston Fury Renegade 7200.
It's feasible, though those error codes tend to appear more often in memory issues than driver problems. Consider executing JEDEC to check for resolution. The memory assessments you've performed aren't the most effective at detecting memory faults. I've encountered inconsistent OCs that succeed both in MemTest86 and Aida64. Moreover, this issue likely stems from an IMC problem, which those tests don't fully capture—TestMem5 does show some instability, while VST performs well, though it's not perfect.
Switched to JEDEC and experienced 10 hours without crashes or BSOD. The Y cruncher VST test wasn’t listed initially; it’s the first time I’m trying it. Can you clarify?
To start it, open the command prompt and go to the folder with the Y cruncher executable. Use the specified sequence of commands: double-click the file, select stress, choose VST, then begin the test. The process may use a lot of memory, so be aware you might run into issues.
The results confirm everything is functioning properly according to the JEDEC test. Regarding the CPU and RAM, it suggests no major issues, likely just minor factory defects. For the Y cruncher, try pressing the specific button you mentioned—it should display the options for 8 and 18 as expected.
I’d re-download it to check for any issues during the process. Could you clarify how you obtained the download link?
I used the identical download link, assuming I wasn’t running Y cruncher as an administrator. After switching to admin mode, the screenshot matches what you saw. I reattempted the stability check with all six tests enabled (BKT, BBP, SFT, N64, HNT, VST) and encountered a blue screen during the SFT phase. An IRQL_NOT_LESS_OR_EQUAL error appeared: the system tried to access an invalid memory location at a high interrupt level. This often results from faulty drivers using wrong addresses. If you have a kernel debugger, retrieve the stack trace. Key details: Arg1: 0x0000000000000000, memory referenced; Arg2: 0x0000000000000002, IRQL; Bit flags indicate a read operation, no execute, and a specific address involved. The crash was reported by Chrome.exe with a trap frame that shows some register values as zero or incorrect.
Yes, the results indicate stability. The tests completed successfully after adjusting the settings. You can consider it reliable.
I extended the testing duration and, because the undervolt setting was turned off, focused on VST using the 6400MT/s profile to verify stability. For reliability, I aim to run VST for an hour to confirm it works consistently.