Repository files navigation

CoreRipperX_logo

CoreRipperX

A CPU stress-testing tool for evaluating core performance and stability using AVX2/AVX-512 operations.

Overview

CoreRipperX evaluates CPU stability and performance by placing heavy computational loads on individual cores or all cores simultaneously. It uses SIMD vector instructions (AVX2 and AVX-512) to stress-test the floating-point and integer execution units, helping identify unstable cores or overclocking issues.

Version 2.0 introduces a WPF desktop application with real-time hardware monitoring.

Features

  • Multiple Stress Test Algorithms: Choose from AVX2 or AVX-512 workloads with varying intensity levels
  • Single-Thread (1T) and Multi-Thread (nT) Modes: Test cores individually or all at once
  • Real-Time Hardware Monitoring: View CPU temperatures, power consumption, clock speeds, and per-core metrics
  • Error Detection: Validates computation results to detect CPU instability
  • Hybrid CPU Support: Correctly handles Intel/AMD processors with different core types

Requirements

  • Operating System: Windows (WPF UI requires Windows)
  • CPU: Processor with AVX2 support (AVX-512 optional for additional algorithms)
  • Runtime: .NET 8
  • Privileges: Administrator rights required for hardware monitoring

Installation

  1. Download the latest release from the CoreRipperX GitHub releases
  2. Extract the archive to your desired location
  3. Run CoreRipperX.UI.exe

Stress Test Algorithms

CoreRipperX provides stress test algorithms in both single-thread (1T) and multi-thread (nT) variants:

Light Load (Mixed)

AlgorithmDescription
AVX2 Mixed 1T/nTCycles through multiple workload phases: FMA compute, memory+compute, mixed integer/float operations, and shuffle/permute. Exercises different CPU execution units for comprehensive testing with lower sustained power.
AVX512 Mixed 1T/nTSame multi-phase approach using 512-bit vectors. Broader coverage of CPU subsystems. Requires AVX-512 capable CPU.

Medium Load (FP64)

AlgorithmDescription
AVX2 FP64 1T/nTDouble-precision (64-bit) floating-point FMA operations using 256-bit vectors. 8 independent computation chains to saturate FMA units. Moderate power consumption.
AVX512 FP64 1T/nTDouble-precision FMA using 512-bit vectors. 12 independent chains for maximum FP64 throughput. Requires AVX-512 capable CPU.

Heavy Load (Compute)

AlgorithmDescription
AVX2 Compute 1T/nTSingle-precision (32-bit) FMA-intensive workload using 256-bit vectors. 16 independent computation chains maximize FMA unit utilization. High power consumption.
AVX512 Compute 1T/nTSingle-precision FMA using 512-bit vectors. 24 independent chains for extreme compute density. Maximum power draw. Requires AVX-512 capable CPU.

Thread Modes

  • 1T (Single-Thread): Tests each core sequentially for the configured duration before moving to the next core. Useful for identifying specific unstable cores.
  • nT (Multi-Thread): Stresses all cores simultaneously. Best for testing overall system stability under full load.

User Guide

System Monitor Tab

System Monitor

The System Monitor tab displays real-time CPU information:

Header Section

  • CPU: Processor model name
  • Physical Cores: Number of physical CPU cores
  • Logical Cores: Total thread count (including SMT/Hyper-Threading)
  • Power: Current CPU package power consumption in watts
  • Temp: Current CPU temperature

Per-Core Table

  • Core: Physical core identifier
  • Clock (MHz): Current core clock speed
  • Eff. 1T (MHz): Effective clock under single-thread load
  • Eff. 2T (MHz): Effective clock under dual-thread load (SMT)
  • Deviation %: Performance deviation from expected (highlighted in red when high - may indicate instability)
  • Load 1T/2T %: Current load percentage per hardware thread

Error Counter: Displays the number of computation errors detected during stress testing. Any non-zero value indicates potential CPU instability.

Settings Tab

Settings

Configure stress test parameters before starting:

Monitoring Settings

  • Polling Rate (ms): How frequently to update sensor readings (default: 1000ms)
  • Critical Deviation (%): Threshold for flagging core performance deviation
  • Critical Temperature (°C): Temperature threshold for warnings

Stress Test Settings

  • Runtime per Cycle (s): Duration to stress each core in 1T mode, or total test duration in nT mode
  • Algorithm: Select the stress test workload (see Stress Test Algorithms above)

Controls

  • START: Begin the stress test with current settings
  • STOP: Cancel the running stress test

Running a Stress Test

  1. Open the Settings tab
  2. Select an algorithm appropriate for your testing goals:
    • Use Mixed algorithms for varied workloads that exercise different CPU subsystems
    • Use FP64 algorithms for moderate stress with lower temperatures
    • Use Compute algorithms for maximum stress and power draw
    • Use 1T variants to identify specific problematic cores
    • Use nT variants for full-system stability testing
  3. Set the Runtime per Cycle (10-60 seconds recommended for 1T mode)
  4. Click START to begin testing
  5. Switch to System Monitor to observe temperatures, clocks, and error counts
  6. Click STOP to end the test early if needed

Interpreting Results

  • Errors > 0: Computation validation failed, indicating CPU instability. Consider lowering overclock settings or increasing voltage.
  • High Deviation %: Core performance is inconsistent, which may indicate thermal throttling or instability.
  • Temperature warnings: If temperatures approach critical levels, the CPU may throttle or become unstable.

Notes

  • Save all work before running stress tests, as system instability may cause crashes
  • Monitor temperatures closely, especially with Compute/nT algorithms
  • AVX-512 algorithms are only available on supported CPUs (Intel Ice Lake+, AMD Zen 4+)
  • Hardware monitoring requires administrator privileges for full sensor access

License

CoreRipperX is licensed under the MIT License. See the LICENSE file for details.

Contact

For issues, questions, or suggestions, please open an issue on the GitHub repository.

About

CPU stress test using AVX operations

Resources

Stars

12 stars

Watchers

1 watching

Forks

Releases

Packages

Used by

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Add copy buttons to all
 blocks\n(function() {\n function addCopyButtons() {\n document.querySelectorAll('pre code').forEach(function(codeBlock) {\n if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;\n codeBlock.parentElement.setAttribute('data-copy-added', 'true');\n \n var btn = document.createElement('button');\n btn.textContent = 'Copy';\n btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';\n btn.onmouseover = function() { this.style.opacity = '1'; };\n btn.onmouseout = function() { this.style.opacity = '0.7'; };\n btn.onclick = function() {\n navigator.clipboard.writeText(codeBlock.textContent).then(function() {\n btn.textContent = 'Copied!';\n setTimeout(function() { btn.textContent = 'Copy'; }, 1500);\n });\n };\n codeBlock.parentElement.style.position = 'relative';\n codeBlock.parentElement.appendChild(btn);\n });\n }\n \n addCopyButtons();\n \n // Re-run on dynamic content\n var observer = new MutationObserver(addCopyButtons);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Add Copy Buttons to Code Blocks");
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
Skip to content

Repository files navigation

CoreRipperX_logo

CoreRipperX

A CPU stress-testing tool for evaluating core performance and stability using AVX2/AVX-512 operations.

Overview

CoreRipperX evaluates CPU stability and performance by placing heavy computational loads on individual cores or all cores simultaneously. It uses SIMD vector instructions (AVX2 and AVX-512) to stress-test the floating-point and integer execution units, helping identify unstable cores or overclocking issues.

Version 2.0 introduces a WPF desktop application with real-time hardware monitoring.

Features

  • Multiple Stress Test Algorithms: Choose from AVX2 or AVX-512 workloads with varying intensity levels
  • Single-Thread (1T) and Multi-Thread (nT) Modes: Test cores individually or all at once
  • Real-Time Hardware Monitoring: View CPU temperatures, power consumption, clock speeds, and per-core metrics
  • Error Detection: Validates computation results to detect CPU instability
  • Hybrid CPU Support: Correctly handles Intel/AMD processors with different core types

Requirements

  • Operating System: Windows (WPF UI requires Windows)
  • CPU: Processor with AVX2 support (AVX-512 optional for additional algorithms)
  • Runtime: .NET 8
  • Privileges: Administrator rights required for hardware monitoring

Installation

  1. Download the latest release from the CoreRipperX GitHub releases
  2. Extract the archive to your desired location
  3. Run CoreRipperX.UI.exe

Stress Test Algorithms

CoreRipperX provides stress test algorithms in both single-thread (1T) and multi-thread (nT) variants:

Light Load (Mixed)

AlgorithmDescription
AVX2 Mixed 1T/nTCycles through multiple workload phases: FMA compute, memory+compute, mixed integer/float operations, and shuffle/permute. Exercises different CPU execution units for comprehensive testing with lower sustained power.
AVX512 Mixed 1T/nTSame multi-phase approach using 512-bit vectors. Broader coverage of CPU subsystems. Requires AVX-512 capable CPU.

Medium Load (FP64)

AlgorithmDescription
AVX2 FP64 1T/nTDouble-precision (64-bit) floating-point FMA operations using 256-bit vectors. 8 independent computation chains to saturate FMA units. Moderate power consumption.
AVX512 FP64 1T/nTDouble-precision FMA using 512-bit vectors. 12 independent chains for maximum FP64 throughput. Requires AVX-512 capable CPU.

Heavy Load (Compute)

AlgorithmDescription
AVX2 Compute 1T/nTSingle-precision (32-bit) FMA-intensive workload using 256-bit vectors. 16 independent computation chains maximize FMA unit utilization. High power consumption.
AVX512 Compute 1T/nTSingle-precision FMA using 512-bit vectors. 24 independent chains for extreme compute density. Maximum power draw. Requires AVX-512 capable CPU.

Thread Modes

  • 1T (Single-Thread): Tests each core sequentially for the configured duration before moving to the next core. Useful for identifying specific unstable cores.
  • nT (Multi-Thread): Stresses all cores simultaneously. Best for testing overall system stability under full load.

User Guide

System Monitor Tab

System Monitor

The System Monitor tab displays real-time CPU information:

Header Section

  • CPU: Processor model name
  • Physical Cores: Number of physical CPU cores
  • Logical Cores: Total thread count (including SMT/Hyper-Threading)
  • Power: Current CPU package power consumption in watts
  • Temp: Current CPU temperature

Per-Core Table

  • Core: Physical core identifier
  • Clock (MHz): Current core clock speed
  • Eff. 1T (MHz): Effective clock under single-thread load
  • Eff. 2T (MHz): Effective clock under dual-thread load (SMT)
  • Deviation %: Performance deviation from expected (highlighted in red when high - may indicate instability)
  • Load 1T/2T %: Current load percentage per hardware thread

Error Counter: Displays the number of computation errors detected during stress testing. Any non-zero value indicates potential CPU instability.

Settings Tab

Settings

Configure stress test parameters before starting:

Monitoring Settings

  • Polling Rate (ms): How frequently to update sensor readings (default: 1000ms)
  • Critical Deviation (%): Threshold for flagging core performance deviation
  • Critical Temperature (°C): Temperature threshold for warnings

Stress Test Settings

  • Runtime per Cycle (s): Duration to stress each core in 1T mode, or total test duration in nT mode
  • Algorithm: Select the stress test workload (see Stress Test Algorithms above)

Controls

  • START: Begin the stress test with current settings
  • STOP: Cancel the running stress test

Running a Stress Test

  1. Open the Settings tab
  2. Select an algorithm appropriate for your testing goals:
    • Use Mixed algorithms for varied workloads that exercise different CPU subsystems
    • Use FP64 algorithms for moderate stress with lower temperatures
    • Use Compute algorithms for maximum stress and power draw
    • Use 1T variants to identify specific problematic cores
    • Use nT variants for full-system stability testing
  3. Set the Runtime per Cycle (10-60 seconds recommended for 1T mode)
  4. Click START to begin testing
  5. Switch to System Monitor to observe temperatures, clocks, and error counts
  6. Click STOP to end the test early if needed

Interpreting Results

  • Errors > 0: Computation validation failed, indicating CPU instability. Consider lowering overclock settings or increasing voltage.
  • High Deviation %: Core performance is inconsistent, which may indicate thermal throttling or instability.
  • Temperature warnings: If temperatures approach critical levels, the CPU may throttle or become unstable.

Notes

  • Save all work before running stress tests, as system instability may cause crashes
  • Monitor temperatures closely, especially with Compute/nT algorithms
  • AVX-512 algorithms are only available on supported CPUs (Intel Ice Lake+, AMD Zen 4+)
  • Hardware monitoring requires administrator privileges for full sensor access

License

CoreRipperX is licensed under the MIT License. See the LICENSE file for details.

Contact

For issues, questions, or suggestions, please open an issue on the GitHub repository.

About

CPU stress test using AVX operations

Resources

Stars

12 stars

Watchers

1 watching

Forks

Releases

Packages

Used by

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Force GitHub README to respect dark mode\n(function() {\n var style = document.createElement('style');\n style.textContent = '\n .markdown-body {\n color-scheme: dark light;\n }\n .markdown-body pre { background: #161b22 !important; }\n .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }\n .markdown-body table th, .markdown-body table td { border-color: #30363d !important; }\n .markdown-body img { background: #0d1117; }\n .markdown-body blockquote { border-left-color: #8b949e; }\n .markdown-body hr { border-color: #30363d; }\n ';\n document.head.appendChild(style);\n})();", "GitHub Dark Mode README Fix"); } } catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

Repository files navigation

CoreRipperX_logo

CoreRipperX

A CPU stress-testing tool for evaluating core performance and stability using AVX2/AVX-512 operations.

Overview

CoreRipperX evaluates CPU stability and performance by placing heavy computational loads on individual cores or all cores simultaneously. It uses SIMD vector instructions (AVX2 and AVX-512) to stress-test the floating-point and integer execution units, helping identify unstable cores or overclocking issues.

Version 2.0 introduces a WPF desktop application with real-time hardware monitoring.

Features

  • Multiple Stress Test Algorithms: Choose from AVX2 or AVX-512 workloads with varying intensity levels
  • Single-Thread (1T) and Multi-Thread (nT) Modes: Test cores individually or all at once
  • Real-Time Hardware Monitoring: View CPU temperatures, power consumption, clock speeds, and per-core metrics
  • Error Detection: Validates computation results to detect CPU instability
  • Hybrid CPU Support: Correctly handles Intel/AMD processors with different core types

Requirements

  • Operating System: Windows (WPF UI requires Windows)
  • CPU: Processor with AVX2 support (AVX-512 optional for additional algorithms)
  • Runtime: .NET 8
  • Privileges: Administrator rights required for hardware monitoring

Installation

  1. Download the latest release from the CoreRipperX GitHub releases
  2. Extract the archive to your desired location
  3. Run CoreRipperX.UI.exe

Stress Test Algorithms

CoreRipperX provides stress test algorithms in both single-thread (1T) and multi-thread (nT) variants:

Light Load (Mixed)

AlgorithmDescription
AVX2 Mixed 1T/nTCycles through multiple workload phases: FMA compute, memory+compute, mixed integer/float operations, and shuffle/permute. Exercises different CPU execution units for comprehensive testing with lower sustained power.
AVX512 Mixed 1T/nTSame multi-phase approach using 512-bit vectors. Broader coverage of CPU subsystems. Requires AVX-512 capable CPU.

Medium Load (FP64)

AlgorithmDescription
AVX2 FP64 1T/nTDouble-precision (64-bit) floating-point FMA operations using 256-bit vectors. 8 independent computation chains to saturate FMA units. Moderate power consumption.
AVX512 FP64 1T/nTDouble-precision FMA using 512-bit vectors. 12 independent chains for maximum FP64 throughput. Requires AVX-512 capable CPU.

Heavy Load (Compute)

AlgorithmDescription
AVX2 Compute 1T/nTSingle-precision (32-bit) FMA-intensive workload using 256-bit vectors. 16 independent computation chains maximize FMA unit utilization. High power consumption.
AVX512 Compute 1T/nTSingle-precision FMA using 512-bit vectors. 24 independent chains for extreme compute density. Maximum power draw. Requires AVX-512 capable CPU.

Thread Modes

  • 1T (Single-Thread): Tests each core sequentially for the configured duration before moving to the next core. Useful for identifying specific unstable cores.
  • nT (Multi-Thread): Stresses all cores simultaneously. Best for testing overall system stability under full load.

User Guide

System Monitor Tab

System Monitor

The System Monitor tab displays real-time CPU information:

Header Section

  • CPU: Processor model name
  • Physical Cores: Number of physical CPU cores
  • Logical Cores: Total thread count (including SMT/Hyper-Threading)
  • Power: Current CPU package power consumption in watts
  • Temp: Current CPU temperature

Per-Core Table

  • Core: Physical core identifier
  • Clock (MHz): Current core clock speed
  • Eff. 1T (MHz): Effective clock under single-thread load
  • Eff. 2T (MHz): Effective clock under dual-thread load (SMT)
  • Deviation %: Performance deviation from expected (highlighted in red when high - may indicate instability)
  • Load 1T/2T %: Current load percentage per hardware thread

Error Counter: Displays the number of computation errors detected during stress testing. Any non-zero value indicates potential CPU instability.

Settings Tab

Settings

Configure stress test parameters before starting:

Monitoring Settings

  • Polling Rate (ms): How frequently to update sensor readings (default: 1000ms)
  • Critical Deviation (%): Threshold for flagging core performance deviation
  • Critical Temperature (°C): Temperature threshold for warnings

Stress Test Settings

  • Runtime per Cycle (s): Duration to stress each core in 1T mode, or total test duration in nT mode
  • Algorithm: Select the stress test workload (see Stress Test Algorithms above)

Controls

  • START: Begin the stress test with current settings
  • STOP: Cancel the running stress test

Running a Stress Test

  1. Open the Settings tab
  2. Select an algorithm appropriate for your testing goals:
    • Use Mixed algorithms for varied workloads that exercise different CPU subsystems
    • Use FP64 algorithms for moderate stress with lower temperatures
    • Use Compute algorithms for maximum stress and power draw
    • Use 1T variants to identify specific problematic cores
    • Use nT variants for full-system stability testing
  3. Set the Runtime per Cycle (10-60 seconds recommended for 1T mode)
  4. Click START to begin testing
  5. Switch to System Monitor to observe temperatures, clocks, and error counts
  6. Click STOP to end the test early if needed

Interpreting Results

  • Errors > 0: Computation validation failed, indicating CPU instability. Consider lowering overclock settings or increasing voltage.
  • High Deviation %: Core performance is inconsistent, which may indicate thermal throttling or instability.
  • Temperature warnings: If temperatures approach critical levels, the CPU may throttle or become unstable.

Notes

  • Save all work before running stress tests, as system instability may cause crashes
  • Monitor temperatures closely, especially with Compute/nT algorithms
  • AVX-512 algorithms are only available on supported CPUs (Intel Ice Lake+, AMD Zen 4+)
  • Hardware monitoring requires administrator privileges for full sensor access

License

CoreRipperX is licensed under the MIT License. See the LICENSE file for details.

Contact

For issues, questions, or suggestions, please open an issue on the GitHub repository.

About

CPU stress test using AVX operations

Resources

Stars

12 stars

Watchers

1 watching

Forks

Releases

Packages

Used by

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Highlight search terms from Google/DuckDuckGo/Bing referrer\n(function() {\n var ref = document.referrer;\n var terms = [];\n \n if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {\n var url = new URL(ref);\n var q = url.searchParams.get('q') || url.searchParams.get('p');\n if (q) {\n terms = q.split(/\\s+/).filter(function(t) { return t.length > 2; });\n }\n }\n \n if (terms.length === 0) return;\n \n var style = document.createElement('style');\n style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';\n document.head.appendChild(style);\n \n function highlight(node) {\n if (node.nodeType === 3) { // text node\n var text = node.textContent;\n var found = false;\n terms.forEach(function(term) {\n var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\\]\\\\]/g, '\\\\') + ')', 'gi');\n if (regex.test(text)) {\n found = true;\n var frag = document.createDocumentFragment();\n var parts = text.split(regex);\n parts.forEach(function(part, i) {\n if (i % 2 === 0) {\n frag.appendChild(document.createTextNode(part));\n } else {\n var span = document.createElement('span');\n span.className = 'userscript-highlight';\n span.textContent = part;\n frag.appendChild(span);\n }\n });\n node.parentNode.replaceChild(frag, node);\n }\n });\n } else if (node.nodeType === 1 && node.childNodes) { // element\n var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];\n if (!skipTags.includes(node.tagName)) {\n Array.from(node.childNodes).forEach(highlight);\n }\n }\n }\n \n highlight(document.body);\n \n // Re-highlight on dynamic content\n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1 || node.nodeType === 3) highlight(node);\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Highlight Search Terms"); } } catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

Repository files navigation

CoreRipperX_logo

CoreRipperX

A CPU stress-testing tool for evaluating core performance and stability using AVX2/AVX-512 operations.

Overview

CoreRipperX evaluates CPU stability and performance by placing heavy computational loads on individual cores or all cores simultaneously. It uses SIMD vector instructions (AVX2 and AVX-512) to stress-test the floating-point and integer execution units, helping identify unstable cores or overclocking issues.

Version 2.0 introduces a WPF desktop application with real-time hardware monitoring.

Features

  • Multiple Stress Test Algorithms: Choose from AVX2 or AVX-512 workloads with varying intensity levels
  • Single-Thread (1T) and Multi-Thread (nT) Modes: Test cores individually or all at once
  • Real-Time Hardware Monitoring: View CPU temperatures, power consumption, clock speeds, and per-core metrics
  • Error Detection: Validates computation results to detect CPU instability
  • Hybrid CPU Support: Correctly handles Intel/AMD processors with different core types

Requirements

  • Operating System: Windows (WPF UI requires Windows)
  • CPU: Processor with AVX2 support (AVX-512 optional for additional algorithms)
  • Runtime: .NET 8
  • Privileges: Administrator rights required for hardware monitoring

Installation

  1. Download the latest release from the CoreRipperX GitHub releases
  2. Extract the archive to your desired location
  3. Run CoreRipperX.UI.exe

Stress Test Algorithms

CoreRipperX provides stress test algorithms in both single-thread (1T) and multi-thread (nT) variants:

Light Load (Mixed)

AlgorithmDescription
AVX2 Mixed 1T/nTCycles through multiple workload phases: FMA compute, memory+compute, mixed integer/float operations, and shuffle/permute. Exercises different CPU execution units for comprehensive testing with lower sustained power.
AVX512 Mixed 1T/nTSame multi-phase approach using 512-bit vectors. Broader coverage of CPU subsystems. Requires AVX-512 capable CPU.

Medium Load (FP64)

AlgorithmDescription
AVX2 FP64 1T/nTDouble-precision (64-bit) floating-point FMA operations using 256-bit vectors. 8 independent computation chains to saturate FMA units. Moderate power consumption.
AVX512 FP64 1T/nTDouble-precision FMA using 512-bit vectors. 12 independent chains for maximum FP64 throughput. Requires AVX-512 capable CPU.

Heavy Load (Compute)

AlgorithmDescription
AVX2 Compute 1T/nTSingle-precision (32-bit) FMA-intensive workload using 256-bit vectors. 16 independent computation chains maximize FMA unit utilization. High power consumption.
AVX512 Compute 1T/nTSingle-precision FMA using 512-bit vectors. 24 independent chains for extreme compute density. Maximum power draw. Requires AVX-512 capable CPU.

Thread Modes

  • 1T (Single-Thread): Tests each core sequentially for the configured duration before moving to the next core. Useful for identifying specific unstable cores.
  • nT (Multi-Thread): Stresses all cores simultaneously. Best for testing overall system stability under full load.

User Guide

System Monitor Tab

System Monitor

The System Monitor tab displays real-time CPU information:

Header Section

  • CPU: Processor model name
  • Physical Cores: Number of physical CPU cores
  • Logical Cores: Total thread count (including SMT/Hyper-Threading)
  • Power: Current CPU package power consumption in watts
  • Temp: Current CPU temperature

Per-Core Table

  • Core: Physical core identifier
  • Clock (MHz): Current core clock speed
  • Eff. 1T (MHz): Effective clock under single-thread load
  • Eff. 2T (MHz): Effective clock under dual-thread load (SMT)
  • Deviation %: Performance deviation from expected (highlighted in red when high - may indicate instability)
  • Load 1T/2T %: Current load percentage per hardware thread

Error Counter: Displays the number of computation errors detected during stress testing. Any non-zero value indicates potential CPU instability.

Settings Tab

Settings

Configure stress test parameters before starting:

Monitoring Settings

  • Polling Rate (ms): How frequently to update sensor readings (default: 1000ms)
  • Critical Deviation (%): Threshold for flagging core performance deviation
  • Critical Temperature (°C): Temperature threshold for warnings

Stress Test Settings

  • Runtime per Cycle (s): Duration to stress each core in 1T mode, or total test duration in nT mode
  • Algorithm: Select the stress test workload (see Stress Test Algorithms above)

Controls

  • START: Begin the stress test with current settings
  • STOP: Cancel the running stress test

Running a Stress Test

  1. Open the Settings tab
  2. Select an algorithm appropriate for your testing goals:
    • Use Mixed algorithms for varied workloads that exercise different CPU subsystems
    • Use FP64 algorithms for moderate stress with lower temperatures
    • Use Compute algorithms for maximum stress and power draw
    • Use 1T variants to identify specific problematic cores
    • Use nT variants for full-system stability testing
  3. Set the Runtime per Cycle (10-60 seconds recommended for 1T mode)
  4. Click START to begin testing
  5. Switch to System Monitor to observe temperatures, clocks, and error counts
  6. Click STOP to end the test early if needed

Interpreting Results

  • Errors > 0: Computation validation failed, indicating CPU instability. Consider lowering overclock settings or increasing voltage.
  • High Deviation %: Core performance is inconsistent, which may indicate thermal throttling or instability.
  • Temperature warnings: If temperatures approach critical levels, the CPU may throttle or become unstable.

Notes

  • Save all work before running stress tests, as system instability may cause crashes
  • Monitor temperatures closely, especially with Compute/nT algorithms
  • AVX-512 algorithms are only available on supported CPUs (Intel Ice Lake+, AMD Zen 4+)
  • Hardware monitoring requires administrator privileges for full sensor access

License

CoreRipperX is licensed under the MIT License. See the LICENSE file for details.

Contact

For issues, questions, or suggestions, please open an issue on the GitHub repository.

About

CPU stress test using AVX operations

Resources

Stars

12 stars

Watchers

1 watching

Forks

Releases

Packages

Used by

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Strip utm_, fbclid, gclid, etc. from all links on page\n(function() {\n var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',\n 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',\n 'ref', 'ref_src', 'source', 'medium', 'campaign'];\n \n function cleanUrl(url) {\n try {\n var u = new URL(url, window.location.origin);\n var changed = false;\n trackingParams.forEach(function(p) {\n if (u.searchParams.has(p)) {\n u.searchParams.delete(p);\n changed = true;\n }\n });\n return changed ? u.toString() : url;\n } catch (e) {\n return url;\n }\n }\n \n function cleanLinks() {\n document.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n \n cleanLinks();\n \n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1) {\n if (node.tagName === 'A') cleanLinks();\n node.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Remove Tracking Parameters from Links"); } } catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); } })(); (function(){ try { var __m = "youtube.com"; var __re = new RegExp('^' + "youtube\\.com" + '
Skip to content

Repository files navigation

CoreRipperX_logo

CoreRipperX

A CPU stress-testing tool for evaluating core performance and stability using AVX2/AVX-512 operations.

Overview

CoreRipperX evaluates CPU stability and performance by placing heavy computational loads on individual cores or all cores simultaneously. It uses SIMD vector instructions (AVX2 and AVX-512) to stress-test the floating-point and integer execution units, helping identify unstable cores or overclocking issues.

Version 2.0 introduces a WPF desktop application with real-time hardware monitoring.

Features

  • Multiple Stress Test Algorithms: Choose from AVX2 or AVX-512 workloads with varying intensity levels
  • Single-Thread (1T) and Multi-Thread (nT) Modes: Test cores individually or all at once
  • Real-Time Hardware Monitoring: View CPU temperatures, power consumption, clock speeds, and per-core metrics
  • Error Detection: Validates computation results to detect CPU instability
  • Hybrid CPU Support: Correctly handles Intel/AMD processors with different core types

Requirements

  • Operating System: Windows (WPF UI requires Windows)
  • CPU: Processor with AVX2 support (AVX-512 optional for additional algorithms)
  • Runtime: .NET 8
  • Privileges: Administrator rights required for hardware monitoring

Installation

  1. Download the latest release from the CoreRipperX GitHub releases
  2. Extract the archive to your desired location
  3. Run CoreRipperX.UI.exe

Stress Test Algorithms

CoreRipperX provides stress test algorithms in both single-thread (1T) and multi-thread (nT) variants:

Light Load (Mixed)

AlgorithmDescription
AVX2 Mixed 1T/nTCycles through multiple workload phases: FMA compute, memory+compute, mixed integer/float operations, and shuffle/permute. Exercises different CPU execution units for comprehensive testing with lower sustained power.
AVX512 Mixed 1T/nTSame multi-phase approach using 512-bit vectors. Broader coverage of CPU subsystems. Requires AVX-512 capable CPU.

Medium Load (FP64)

AlgorithmDescription
AVX2 FP64 1T/nTDouble-precision (64-bit) floating-point FMA operations using 256-bit vectors. 8 independent computation chains to saturate FMA units. Moderate power consumption.
AVX512 FP64 1T/nTDouble-precision FMA using 512-bit vectors. 12 independent chains for maximum FP64 throughput. Requires AVX-512 capable CPU.

Heavy Load (Compute)

AlgorithmDescription
AVX2 Compute 1T/nTSingle-precision (32-bit) FMA-intensive workload using 256-bit vectors. 16 independent computation chains maximize FMA unit utilization. High power consumption.
AVX512 Compute 1T/nTSingle-precision FMA using 512-bit vectors. 24 independent chains for extreme compute density. Maximum power draw. Requires AVX-512 capable CPU.

Thread Modes

  • 1T (Single-Thread): Tests each core sequentially for the configured duration before moving to the next core. Useful for identifying specific unstable cores.
  • nT (Multi-Thread): Stresses all cores simultaneously. Best for testing overall system stability under full load.

User Guide

System Monitor Tab

System Monitor

The System Monitor tab displays real-time CPU information:

Header Section

  • CPU: Processor model name
  • Physical Cores: Number of physical CPU cores
  • Logical Cores: Total thread count (including SMT/Hyper-Threading)
  • Power: Current CPU package power consumption in watts
  • Temp: Current CPU temperature

Per-Core Table

  • Core: Physical core identifier
  • Clock (MHz): Current core clock speed
  • Eff. 1T (MHz): Effective clock under single-thread load
  • Eff. 2T (MHz): Effective clock under dual-thread load (SMT)
  • Deviation %: Performance deviation from expected (highlighted in red when high - may indicate instability)
  • Load 1T/2T %: Current load percentage per hardware thread

Error Counter: Displays the number of computation errors detected during stress testing. Any non-zero value indicates potential CPU instability.

Settings Tab

Settings

Configure stress test parameters before starting:

Monitoring Settings

  • Polling Rate (ms): How frequently to update sensor readings (default: 1000ms)
  • Critical Deviation (%): Threshold for flagging core performance deviation
  • Critical Temperature (°C): Temperature threshold for warnings

Stress Test Settings

  • Runtime per Cycle (s): Duration to stress each core in 1T mode, or total test duration in nT mode
  • Algorithm: Select the stress test workload (see Stress Test Algorithms above)

Controls

  • START: Begin the stress test with current settings
  • STOP: Cancel the running stress test

Running a Stress Test

  1. Open the Settings tab
  2. Select an algorithm appropriate for your testing goals:
    • Use Mixed algorithms for varied workloads that exercise different CPU subsystems
    • Use FP64 algorithms for moderate stress with lower temperatures
    • Use Compute algorithms for maximum stress and power draw
    • Use 1T variants to identify specific problematic cores
    • Use nT variants for full-system stability testing
  3. Set the Runtime per Cycle (10-60 seconds recommended for 1T mode)
  4. Click START to begin testing
  5. Switch to System Monitor to observe temperatures, clocks, and error counts
  6. Click STOP to end the test early if needed

Interpreting Results

  • Errors > 0: Computation validation failed, indicating CPU instability. Consider lowering overclock settings or increasing voltage.
  • High Deviation %: Core performance is inconsistent, which may indicate thermal throttling or instability.
  • Temperature warnings: If temperatures approach critical levels, the CPU may throttle or become unstable.

Notes

  • Save all work before running stress tests, as system instability may cause crashes
  • Monitor temperatures closely, especially with Compute/nT algorithms
  • AVX-512 algorithms are only available on supported CPUs (Intel Ice Lake+, AMD Zen 4+)
  • Hardware monitoring requires administrator privileges for full sensor access

License

CoreRipperX is licensed under the MIT License. See the LICENSE file for details.

Contact

For issues, questions, or suggestions, please open an issue on the GitHub repository.

About

CPU stress test using AVX operations

Resources

Stars

12 stars

Watchers

1 watching

Forks

Releases

Packages

Used by

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Auto-enable theater mode on YouTube\n(function() {\n function tryTheater() {\n var btn = document.querySelector('button[aria-label=\"Theater mode\"], ytd-player #player button[title=\"Theater mode\"]');\n if (btn && !btn.classList.contains('activated')) {\n btn.click();\n }\n }\n \n // Try immediately\n tryTheater();\n \n // Try after navigation (SPA)\n var lastUrl = location.href;\n setInterval(function() {\n if (location.href !== lastUrl) {\n lastUrl = location.href;\n setTimeout(tryTheater, 500);\n }\n }, 1000);\n \n // Also try on player load\n var observer = new MutationObserver(tryTheater);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "YouTube Theater Mode Default"); } } catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

Repository files navigation

CoreRipperX_logo

CoreRipperX

A CPU stress-testing tool for evaluating core performance and stability using AVX2/AVX-512 operations.

Overview

CoreRipperX evaluates CPU stability and performance by placing heavy computational loads on individual cores or all cores simultaneously. It uses SIMD vector instructions (AVX2 and AVX-512) to stress-test the floating-point and integer execution units, helping identify unstable cores or overclocking issues.

Version 2.0 introduces a WPF desktop application with real-time hardware monitoring.

Features

  • Multiple Stress Test Algorithms: Choose from AVX2 or AVX-512 workloads with varying intensity levels
  • Single-Thread (1T) and Multi-Thread (nT) Modes: Test cores individually or all at once
  • Real-Time Hardware Monitoring: View CPU temperatures, power consumption, clock speeds, and per-core metrics
  • Error Detection: Validates computation results to detect CPU instability
  • Hybrid CPU Support: Correctly handles Intel/AMD processors with different core types

Requirements

  • Operating System: Windows (WPF UI requires Windows)
  • CPU: Processor with AVX2 support (AVX-512 optional for additional algorithms)
  • Runtime: .NET 8
  • Privileges: Administrator rights required for hardware monitoring

Installation

  1. Download the latest release from the CoreRipperX GitHub releases
  2. Extract the archive to your desired location
  3. Run CoreRipperX.UI.exe

Stress Test Algorithms

CoreRipperX provides stress test algorithms in both single-thread (1T) and multi-thread (nT) variants:

Light Load (Mixed)

AlgorithmDescription
AVX2 Mixed 1T/nTCycles through multiple workload phases: FMA compute, memory+compute, mixed integer/float operations, and shuffle/permute. Exercises different CPU execution units for comprehensive testing with lower sustained power.
AVX512 Mixed 1T/nTSame multi-phase approach using 512-bit vectors. Broader coverage of CPU subsystems. Requires AVX-512 capable CPU.

Medium Load (FP64)

AlgorithmDescription
AVX2 FP64 1T/nTDouble-precision (64-bit) floating-point FMA operations using 256-bit vectors. 8 independent computation chains to saturate FMA units. Moderate power consumption.
AVX512 FP64 1T/nTDouble-precision FMA using 512-bit vectors. 12 independent chains for maximum FP64 throughput. Requires AVX-512 capable CPU.

Heavy Load (Compute)

AlgorithmDescription
AVX2 Compute 1T/nTSingle-precision (32-bit) FMA-intensive workload using 256-bit vectors. 16 independent computation chains maximize FMA unit utilization. High power consumption.
AVX512 Compute 1T/nTSingle-precision FMA using 512-bit vectors. 24 independent chains for extreme compute density. Maximum power draw. Requires AVX-512 capable CPU.

Thread Modes

  • 1T (Single-Thread): Tests each core sequentially for the configured duration before moving to the next core. Useful for identifying specific unstable cores.
  • nT (Multi-Thread): Stresses all cores simultaneously. Best for testing overall system stability under full load.

User Guide

System Monitor Tab

System Monitor

The System Monitor tab displays real-time CPU information:

Header Section

  • CPU: Processor model name
  • Physical Cores: Number of physical CPU cores
  • Logical Cores: Total thread count (including SMT/Hyper-Threading)
  • Power: Current CPU package power consumption in watts
  • Temp: Current CPU temperature

Per-Core Table

  • Core: Physical core identifier
  • Clock (MHz): Current core clock speed
  • Eff. 1T (MHz): Effective clock under single-thread load
  • Eff. 2T (MHz): Effective clock under dual-thread load (SMT)
  • Deviation %: Performance deviation from expected (highlighted in red when high - may indicate instability)
  • Load 1T/2T %: Current load percentage per hardware thread

Error Counter: Displays the number of computation errors detected during stress testing. Any non-zero value indicates potential CPU instability.

Settings Tab

Settings

Configure stress test parameters before starting:

Monitoring Settings

  • Polling Rate (ms): How frequently to update sensor readings (default: 1000ms)
  • Critical Deviation (%): Threshold for flagging core performance deviation
  • Critical Temperature (°C): Temperature threshold for warnings

Stress Test Settings

  • Runtime per Cycle (s): Duration to stress each core in 1T mode, or total test duration in nT mode
  • Algorithm: Select the stress test workload (see Stress Test Algorithms above)

Controls

  • START: Begin the stress test with current settings
  • STOP: Cancel the running stress test

Running a Stress Test

  1. Open the Settings tab
  2. Select an algorithm appropriate for your testing goals:
    • Use Mixed algorithms for varied workloads that exercise different CPU subsystems
    • Use FP64 algorithms for moderate stress with lower temperatures
    • Use Compute algorithms for maximum stress and power draw
    • Use 1T variants to identify specific problematic cores
    • Use nT variants for full-system stability testing
  3. Set the Runtime per Cycle (10-60 seconds recommended for 1T mode)
  4. Click START to begin testing
  5. Switch to System Monitor to observe temperatures, clocks, and error counts
  6. Click STOP to end the test early if needed

Interpreting Results

  • Errors > 0: Computation validation failed, indicating CPU instability. Consider lowering overclock settings or increasing voltage.
  • High Deviation %: Core performance is inconsistent, which may indicate thermal throttling or instability.
  • Temperature warnings: If temperatures approach critical levels, the CPU may throttle or become unstable.

Notes

  • Save all work before running stress tests, as system instability may cause crashes
  • Monitor temperatures closely, especially with Compute/nT algorithms
  • AVX-512 algorithms are only available on supported CPUs (Intel Ice Lake+, AMD Zen 4+)
  • Hardware monitoring requires administrator privileges for full sensor access

License

CoreRipperX is licensed under the MIT License. See the LICENSE file for details.

Contact

For issues, questions, or suggestions, please open an issue on the GitHub repository.

About

CPU stress test using AVX operations

Resources

Stars

12 stars

Watchers

1 watching

Forks

Releases

Packages

Used by

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Remove or un-stick sticky/fixed headers that block content\n(function() {\n function unstick() {\n document.querySelectorAll('header, nav, [role=\"banner\"], .header, .navbar, .sticky, .fixed-top, [style*=\"position: fixed\"], [style*=\"position:sticky\"]').forEach(function(el) {\n if (el.style.position === 'fixed' || el.style.position === 'sticky' || \n getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {\n el.style.position = 'static';\n el.style.top = 'auto';\n el.style.zIndex = 'auto';\n }\n });\n }\n \n unstick();\n \n var observer = new MutationObserver(unstick);\n observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });\n})();", "Kill Sticky Headers"); } } catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

Repository files navigation

CoreRipperX_logo

CoreRipperX

A CPU stress-testing tool for evaluating core performance and stability using AVX2/AVX-512 operations.

Overview

CoreRipperX evaluates CPU stability and performance by placing heavy computational loads on individual cores or all cores simultaneously. It uses SIMD vector instructions (AVX2 and AVX-512) to stress-test the floating-point and integer execution units, helping identify unstable cores or overclocking issues.

Version 2.0 introduces a WPF desktop application with real-time hardware monitoring.

Features

  • Multiple Stress Test Algorithms: Choose from AVX2 or AVX-512 workloads with varying intensity levels
  • Single-Thread (1T) and Multi-Thread (nT) Modes: Test cores individually or all at once
  • Real-Time Hardware Monitoring: View CPU temperatures, power consumption, clock speeds, and per-core metrics
  • Error Detection: Validates computation results to detect CPU instability
  • Hybrid CPU Support: Correctly handles Intel/AMD processors with different core types

Requirements

  • Operating System: Windows (WPF UI requires Windows)
  • CPU: Processor with AVX2 support (AVX-512 optional for additional algorithms)
  • Runtime: .NET 8
  • Privileges: Administrator rights required for hardware monitoring

Installation

  1. Download the latest release from the CoreRipperX GitHub releases
  2. Extract the archive to your desired location
  3. Run CoreRipperX.UI.exe

Stress Test Algorithms

CoreRipperX provides stress test algorithms in both single-thread (1T) and multi-thread (nT) variants:

Light Load (Mixed)

AlgorithmDescription
AVX2 Mixed 1T/nTCycles through multiple workload phases: FMA compute, memory+compute, mixed integer/float operations, and shuffle/permute. Exercises different CPU execution units for comprehensive testing with lower sustained power.
AVX512 Mixed 1T/nTSame multi-phase approach using 512-bit vectors. Broader coverage of CPU subsystems. Requires AVX-512 capable CPU.

Medium Load (FP64)

AlgorithmDescription
AVX2 FP64 1T/nTDouble-precision (64-bit) floating-point FMA operations using 256-bit vectors. 8 independent computation chains to saturate FMA units. Moderate power consumption.
AVX512 FP64 1T/nTDouble-precision FMA using 512-bit vectors. 12 independent chains for maximum FP64 throughput. Requires AVX-512 capable CPU.

Heavy Load (Compute)

AlgorithmDescription
AVX2 Compute 1T/nTSingle-precision (32-bit) FMA-intensive workload using 256-bit vectors. 16 independent computation chains maximize FMA unit utilization. High power consumption.
AVX512 Compute 1T/nTSingle-precision FMA using 512-bit vectors. 24 independent chains for extreme compute density. Maximum power draw. Requires AVX-512 capable CPU.

Thread Modes

  • 1T (Single-Thread): Tests each core sequentially for the configured duration before moving to the next core. Useful for identifying specific unstable cores.
  • nT (Multi-Thread): Stresses all cores simultaneously. Best for testing overall system stability under full load.

User Guide

System Monitor Tab

System Monitor

The System Monitor tab displays real-time CPU information:

Header Section

  • CPU: Processor model name
  • Physical Cores: Number of physical CPU cores
  • Logical Cores: Total thread count (including SMT/Hyper-Threading)
  • Power: Current CPU package power consumption in watts
  • Temp: Current CPU temperature

Per-Core Table

  • Core: Physical core identifier
  • Clock (MHz): Current core clock speed
  • Eff. 1T (MHz): Effective clock under single-thread load
  • Eff. 2T (MHz): Effective clock under dual-thread load (SMT)
  • Deviation %: Performance deviation from expected (highlighted in red when high - may indicate instability)
  • Load 1T/2T %: Current load percentage per hardware thread

Error Counter: Displays the number of computation errors detected during stress testing. Any non-zero value indicates potential CPU instability.

Settings Tab

Settings

Configure stress test parameters before starting:

Monitoring Settings

  • Polling Rate (ms): How frequently to update sensor readings (default: 1000ms)
  • Critical Deviation (%): Threshold for flagging core performance deviation
  • Critical Temperature (°C): Temperature threshold for warnings

Stress Test Settings

  • Runtime per Cycle (s): Duration to stress each core in 1T mode, or total test duration in nT mode
  • Algorithm: Select the stress test workload (see Stress Test Algorithms above)

Controls

  • START: Begin the stress test with current settings
  • STOP: Cancel the running stress test

Running a Stress Test

  1. Open the Settings tab
  2. Select an algorithm appropriate for your testing goals:
    • Use Mixed algorithms for varied workloads that exercise different CPU subsystems
    • Use FP64 algorithms for moderate stress with lower temperatures
    • Use Compute algorithms for maximum stress and power draw
    • Use 1T variants to identify specific problematic cores
    • Use nT variants for full-system stability testing
  3. Set the Runtime per Cycle (10-60 seconds recommended for 1T mode)
  4. Click START to begin testing
  5. Switch to System Monitor to observe temperatures, clocks, and error counts
  6. Click STOP to end the test early if needed

Interpreting Results

  • Errors > 0: Computation validation failed, indicating CPU instability. Consider lowering overclock settings or increasing voltage.
  • High Deviation %: Core performance is inconsistent, which may indicate thermal throttling or instability.
  • Temperature warnings: If temperatures approach critical levels, the CPU may throttle or become unstable.

Notes

  • Save all work before running stress tests, as system instability may cause crashes
  • Monitor temperatures closely, especially with Compute/nT algorithms
  • AVX-512 algorithms are only available on supported CPUs (Intel Ice Lake+, AMD Zen 4+)
  • Hardware monitoring requires administrator privileges for full sensor access

License

CoreRipperX is licensed under the MIT License. See the LICENSE file for details.

Contact

For issues, questions, or suggestions, please open an issue on the GitHub repository.

About

CPU stress test using AVX operations

Resources

Stars

12 stars

Watchers

1 watching

Forks

Releases

Packages

Used by

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Universal Dark Mode - works on any site\n(function() {\n var enabled = true;\n \n function applyDarkMode() {\n if (!enabled) return;\n \n // Create style element if it doesn't exist\n var style = document.getElementById('universal-dark-mode-style');\n if (!style) {\n style = document.createElement('style');\n style.id = 'universal-dark-mode-style';\n document.head.appendChild(style);\n }\n \n // Dark mode CSS - inverts colors but preserves images/video\n style.textContent = '\n /* Invert everything except media */\n html {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #1a1a2e !important;\n }\n \n /* Restore images, videos, iframes, canvas */\n img, video, iframe, canvas, svg, picture, [style*=\"background-image\"] {\n filter: invert(1) hue-rotate(180deg) !important;\n }\n \n /* Preserve specific elements that should not be inverted */\n .no-dark-mode, .no-dark-mode *,\n [data-theme=\"light\"], [data-theme=\"light\"],\n .ace_editor, .ace_editor *,\n .CodeMirror, .CodeMirror *,\n .monaco-editor, .monaco-editor *,\n .markdown-body pre, .markdown-body pre *,\n .highlight, .highlight *,\n pre code, pre code * {\n filter: none !important;\n }\n \n /* Fix common UI elements */\n .modal, .popup, .dropdown-menu, .tooltip, .popover {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #2d2d44 !important;\n border-color: #444 !important;\n }\n \n /* Scrollbars */\n ::-webkit-scrollbar { background: #1a1a2e !important; }\n ::-webkit-scrollbar-thumb { background: #444 !important; }\n ::-webkit-scrollbar-thumb:hover { background: #555 !important; }\n \n /* Selection */\n ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ';\n }\n \n function removeDarkMode() {\n var style = document.getElementById('universal-dark-mode-style');\n if (style) style.remove();\n }\n \n // Toggle with Alt+Shift+D\n document.addEventListener('keydown', function(e) {\n if (e.altKey && e.shiftKey && e.key === 'D') {\n e.preventDefault();\n enabled = !enabled;\n if (enabled) {\n applyDarkMode();\n console.log('[Universal Dark Mode] Enabled');\n } else {\n removeDarkMode();\n console.log('[Universal Dark Mode] Disabled');\n }\n }\n });\n \n // Apply on load\n applyDarkMode();\n \n // Re-apply on dynamic content\n var observer = new MutationObserver(function(mutations) {\n if (enabled && !document.getElementById('universal-dark-mode-style')) {\n applyDarkMode();\n }\n });\n observer.observe(document.head, { childList: true });\n \n console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');\n})();", "Universal Dark Mode"); } } catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); } })(); })();
Skip to content

Repository files navigation

CoreRipperX_logo

CoreRipperX

A CPU stress-testing tool for evaluating core performance and stability using AVX2/AVX-512 operations.

Overview

CoreRipperX evaluates CPU stability and performance by placing heavy computational loads on individual cores or all cores simultaneously. It uses SIMD vector instructions (AVX2 and AVX-512) to stress-test the floating-point and integer execution units, helping identify unstable cores or overclocking issues.

Version 2.0 introduces a WPF desktop application with real-time hardware monitoring.

Features

  • Multiple Stress Test Algorithms: Choose from AVX2 or AVX-512 workloads with varying intensity levels
  • Single-Thread (1T) and Multi-Thread (nT) Modes: Test cores individually or all at once
  • Real-Time Hardware Monitoring: View CPU temperatures, power consumption, clock speeds, and per-core metrics
  • Error Detection: Validates computation results to detect CPU instability
  • Hybrid CPU Support: Correctly handles Intel/AMD processors with different core types

Requirements

  • Operating System: Windows (WPF UI requires Windows)
  • CPU: Processor with AVX2 support (AVX-512 optional for additional algorithms)
  • Runtime: .NET 8
  • Privileges: Administrator rights required for hardware monitoring

Installation

  1. Download the latest release from the CoreRipperX GitHub releases
  2. Extract the archive to your desired location
  3. Run CoreRipperX.UI.exe

Stress Test Algorithms

CoreRipperX provides stress test algorithms in both single-thread (1T) and multi-thread (nT) variants:

Light Load (Mixed)

AlgorithmDescription
AVX2 Mixed 1T/nTCycles through multiple workload phases: FMA compute, memory+compute, mixed integer/float operations, and shuffle/permute. Exercises different CPU execution units for comprehensive testing with lower sustained power.
AVX512 Mixed 1T/nTSame multi-phase approach using 512-bit vectors. Broader coverage of CPU subsystems. Requires AVX-512 capable CPU.

Medium Load (FP64)

AlgorithmDescription
AVX2 FP64 1T/nTDouble-precision (64-bit) floating-point FMA operations using 256-bit vectors. 8 independent computation chains to saturate FMA units. Moderate power consumption.
AVX512 FP64 1T/nTDouble-precision FMA using 512-bit vectors. 12 independent chains for maximum FP64 throughput. Requires AVX-512 capable CPU.

Heavy Load (Compute)

AlgorithmDescription
AVX2 Compute 1T/nTSingle-precision (32-bit) FMA-intensive workload using 256-bit vectors. 16 independent computation chains maximize FMA unit utilization. High power consumption.
AVX512 Compute 1T/nTSingle-precision FMA using 512-bit vectors. 24 independent chains for extreme compute density. Maximum power draw. Requires AVX-512 capable CPU.

Thread Modes

  • 1T (Single-Thread): Tests each core sequentially for the configured duration before moving to the next core. Useful for identifying specific unstable cores.
  • nT (Multi-Thread): Stresses all cores simultaneously. Best for testing overall system stability under full load.

User Guide

System Monitor Tab

System Monitor

The System Monitor tab displays real-time CPU information:

Header Section

  • CPU: Processor model name
  • Physical Cores: Number of physical CPU cores
  • Logical Cores: Total thread count (including SMT/Hyper-Threading)
  • Power: Current CPU package power consumption in watts
  • Temp: Current CPU temperature

Per-Core Table

  • Core: Physical core identifier
  • Clock (MHz): Current core clock speed
  • Eff. 1T (MHz): Effective clock under single-thread load
  • Eff. 2T (MHz): Effective clock under dual-thread load (SMT)
  • Deviation %: Performance deviation from expected (highlighted in red when high - may indicate instability)
  • Load 1T/2T %: Current load percentage per hardware thread

Error Counter: Displays the number of computation errors detected during stress testing. Any non-zero value indicates potential CPU instability.

Settings Tab

Settings

Configure stress test parameters before starting:

Monitoring Settings

  • Polling Rate (ms): How frequently to update sensor readings (default: 1000ms)
  • Critical Deviation (%): Threshold for flagging core performance deviation
  • Critical Temperature (°C): Temperature threshold for warnings

Stress Test Settings

  • Runtime per Cycle (s): Duration to stress each core in 1T mode, or total test duration in nT mode
  • Algorithm: Select the stress test workload (see Stress Test Algorithms above)

Controls

  • START: Begin the stress test with current settings
  • STOP: Cancel the running stress test

Running a Stress Test

  1. Open the Settings tab
  2. Select an algorithm appropriate for your testing goals:
    • Use Mixed algorithms for varied workloads that exercise different CPU subsystems
    • Use FP64 algorithms for moderate stress with lower temperatures
    • Use Compute algorithms for maximum stress and power draw
    • Use 1T variants to identify specific problematic cores
    • Use nT variants for full-system stability testing
  3. Set the Runtime per Cycle (10-60 seconds recommended for 1T mode)
  4. Click START to begin testing
  5. Switch to System Monitor to observe temperatures, clocks, and error counts
  6. Click STOP to end the test early if needed

Interpreting Results

  • Errors > 0: Computation validation failed, indicating CPU instability. Consider lowering overclock settings or increasing voltage.
  • High Deviation %: Core performance is inconsistent, which may indicate thermal throttling or instability.
  • Temperature warnings: If temperatures approach critical levels, the CPU may throttle or become unstable.

Notes

  • Save all work before running stress tests, as system instability may cause crashes
  • Monitor temperatures closely, especially with Compute/nT algorithms
  • AVX-512 algorithms are only available on supported CPUs (Intel Ice Lake+, AMD Zen 4+)
  • Hardware monitoring requires administrator privileges for full sensor access

License

CoreRipperX is licensed under the MIT License. See the LICENSE file for details.

Contact

For issues, questions, or suggestions, please open an issue on the GitHub repository.

About

CPU stress test using AVX operations

Resources

Stars

12 stars

Watchers

1 watching

Forks

Releases

Packages

Used by

Contributors

Languages