OCCT v17 stable released with modular Memory Test and new launcher

OCCT v17 stable version adds AM5 Margin Probe memory preset

OCCT v17 is now available as a stable release. The update brings the redesigned Memory Test introduced during the beta phase, a new launcher, lower memory usage, and reliability changes across the application.

The new Memory Test was rebuilt around a modular system. OCCT says it currently includes 16 individual testing blocks that can be combined into custom memory stress tests. This gives users more control over how memory is written, moved, looped, and checked during validation.

The stable release also adds six Memory Test presets. One of them is AM5 Margin Probe, a community-made preset by a contributor. OCCT says more presets may be added later through internal testing and community submissions.

Startup time reduced by up to 30%

Alongside the new Memory Test, OCCT v17 delivers major improvements to performance, reliability, and overall usability.

  • FASTER STARTUP TIME – A brand-new launcher improves startup times by approximately 10% to 30%.
  • LOWER MEMORY USAGE – Overall memory consumption has been reduced by approximately 15% to 30%, with monitoring data now written directly to disk for improved efficiency during long test sessions.
  • IMPROVED RELIABILITY – Better support for portable installations, a reworked auto-update system, and enhanced crash recovery make OCCT more stable and easier to troubleshoot than ever.

OCCT v17 also ships with a new launcher. According to OCCT, startup times are now around 10% to 30% lower depending on the system. The application’s memory usage has also been reduced by around 15% to 30%.

Monitoring data is now written directly to disk, which should help during longer test sessions. The update also brings better support for portable installations, a reworked auto-update system, and improved crash recovery.

We already covered the OCCT v17 beta in April , when the new Memory Test was first introduced. At the time, OCCT said the system was inspired by TestMem5 and MemTest86-style testing, but implemented internally rather than copied.

Source: OCCT