The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Usually, only a little. Moving a shader cache from a hard disk to an SSD can lower the time needed to read and write already-compiled cache files. It does not eliminate the CPU and GPU work of compiling a shader the first time a game encounters it, so it cannot by itself cure shader-compilation stutter. The move is most useful when the cache is on an HDD, the drive is heavily busy, or the cache volume is so full that files are repeatedly evicted.
If the cache is already on a SATA SSD, moving it to an NVMe SSD normally produces an even smaller difference unless monitoring shows storage latency or queueing during the hitch. Persistent stutter is more often solved by letting the game and driver finish building a complete cache, preventing cache eviction, and using shader or pipeline precompilation features.
What a shader cache does
A shader is a small program used by the graphics pipeline for tasks such as transforming vertices, applying materials, calculating lighting, and producing post-processing effects. Before a GPU can use a shader, the game’s source or intermediate representation must be compiled into code suitable for the selected graphics API and GPU driver.
That compilation can happen before a level loads, during a loading screen, or just in time while you play. The last option is the familiar hitch: the render thread reaches a new effect, compilation work consumes CPU time and may involve driver and GPU synchronization, and one or more frames take far longer than normal. Average frames per second can remain high while frame-time spikes make camera movement feel uneven.
#1 Best Overall
- This product has been replaced by our latest generation. Please search for the SANDISK Optimus GX 7100 NVMe SSD
- HIGH-OCTANE GAMING. Experience speeds up to 7,250MB/s read and 6,900MB/s write (1-2TB models), with up to 35% faster performance than previous generation.
- PURPOSE-BUILT. Designed for serious on-the-go gamers, with a PCIe Gen4 interface and SANDISK’s next generation TLC 3D NAND.
- MORE TIME TO CLEAR THAT CHECKPOINT. Built with laptops and handheld gaming devices in mind, with up to 100% more power efficiency over the previous generation.
- DO MORE WITH DASHBOARD. Ensure your drive is optimized for prime performance with the downloadable WD_BLACK Dashboard (Windows only).
NVIDIA describes shader compilation as a common cause of gameplay stutter and says its shader cache stores compiled shaders so later runs of the same game do not need to compile them again. A cache therefore helps on a cache hit; it does not make the first compile free.
Three cache layers can be involved
“The shader cache” is not always one folder. A game may use several layers with different owners and locations:
- GPU-driver cache: The graphics driver stores compiled results for reuse by that game and driver combination.
- DirectX cache: Windows and DirectX components can maintain disk-backed shader data used by Direct3D applications.
- Game or engine cache: The title may save its own shader, pipeline-state, or derived-data cache. Unreal Engine games, for example, can use engine-level shader and pipeline mechanisms in addition to driver storage.
Relocating one layer does not automatically relocate the others. Before changing a path, identify which cache the game or driver is actually using; otherwise you may move a folder that has little effect while the active cache remains on the original drive.
What an SSD changes—and what it cannot
Where an SSD can help
Reading a cache entry from flash storage generally has lower access latency than reading a randomly located file from a mechanical hard disk. Writes during cache creation can also complete sooner. That can shorten loading after a cache hit, reduce the time needed to rebuild a cache, and lessen a hitch caused by storage being unable to deliver an already-compiled entry quickly enough.
The benefit is largest when the current cache is on an HDD that is seeking among many files, when another workload is saturating that disk, or when the cache volume is nearly full and the operating system is struggling with free space. An SSD can also make the post-update rebuild less painful because many cache files can be written faster.
Rank #2
- Ideal for high speed, low power storage
- Gen 4x4 NVMe PCle performance
- Up to 6,000MB/s read, 4,000MB/s write
- Includes Acronis cloning software
- 5-year limited warranty
Where an SSD does not help
An SSD cannot remove compilation work. If the game has never seen a shader variant, it must still compile it, regardless of whether the cache directory is on an HDD, SATA SSD, or NVMe SSD. The CPU time, driver processing, synchronization, and possible GPU work remain. A game that compiles just in time during traversal can therefore stutter on a fast NVMe drive.
No official source establishes a universal stutter reduction when moving a cache between HDD, SATA SSD, and NVMe SSD. The expected storage advantage is an inference from a disk-backed cache design, not a guaranteed benchmark result. The only reliable way to determine whether storage is involved in your system is to measure frame times and storage latency under identical conditions.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Why stutter returns even when the cache is on an SSD
The cache is empty or was invalidated
Installing a new graphics driver, changing some driver settings, updating a game, or changing hardware can invalidate compiled data. NVIDIA and Epic both warn that the first run after invalidation can involve longer loading or renewed compilation. An SSD may rebuild the files faster, but the first traversal still has to do the compilation work.
Epic Games’ Fortnite support also documents a failure mode in which the client repeatedly recompiles DirectX shaders, causing heavy stuttering in DirectX 12 mode. That is a software or cache-management problem, not evidence that the storage device is too slow.
The cache-size limit is too small
NVIDIA advises setting a cache limit large enough for the games you normally use without exceeding the available disk space. If the limit is undersized, older shaders are evicted as new ones arrive. Returning to an earlier area then causes the game to compile those variants again, producing recurring stutter that an SSD cannot prevent.
Rank #3
- PCIe 4.0 Performance: Delivers up to 7,100 MB/s read and 6,000 MB/s write speeds for quicker game load times, bootups, and smooth multitasking
- Spacious 1TB SSD: Provides space for AAA games, apps, and media with standard Gen4 NVMe performance for casual gamers and home users
- Broad Compatibility: Works seamlessly with laptops, desktops, and select gaming consoles including ROG Ally X, Lenovo Legion Go, and AYANEO Kun. Also backward compatible with PCIe Gen3 systems for flexible upgrades
- Better Productivity: Up to 2x faster than previous Gen3 generation. Improve performance for real world tasks like booting Windows, starting applications like Adobe Photoshop and Illustrator, and working in applications like Microsoft Excel and PowerPoint
- Trusted Micron Quality: Built with advanced G8 NAND and thermal control for reliable Gen4 performance trusted by gamers and home users
Increasing the limit does not create unlimited storage. Leave enough free space for Windows, game updates, and other temporary files; a full volume can cause its own performance and update problems.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsThe game compiles during play by design
Microsoft explains that compiling shaders at launch or “just in time” during gameplay leads to longer load times and in-game shader-compilation stutter. Some engines still discover variants dynamically because the complete set depends on user settings, downloadable content, weather, materials, or paths through a level. In that case, a cache reduces repeat work after the first encounter but cannot guarantee a hitch-free first encounter.
HDD, SATA SSD, or NVMe SSD: what to expect
Use the following as a decision guide, not as a promised performance ranking. The sources establish the cache and compilation mechanisms but do not provide a universal drive-to-drive stutter delta.
| Cache location | Cache-hit latency | Rebuild after invalidation | Likely frame-time result | Main risk or limitation |
|---|---|---|---|---|
| Hard disk drive | Highest of the three, especially for scattered small files or a busy disk | Usually the slowest | Can reduce storage-related hitches if the disk is the bottleneck; shader-compilation spikes remain | Mechanical seeks, competing workloads, and low free space can magnify delays |
| SATA SSD | Lower and more consistent than an HDD | Faster than an HDD | Often a sensible destination for a cache currently on an HDD; the gain over another SSD is commonly small | Still cannot avoid first-time compilation |
| NVMe SSD | Very low access latency, but the practical cache difference depends on workload | Fastest in many systems, though no universal cache benchmark is established | May help when monitoring shows storage queueing or high latency; may change little when the cache is already on an SSD | Buying a faster drive does not fix driver, engine, or cache-eviction defects |
Compare frame-time spikes, not just average FPS. A drive change that shortens a loading screen but leaves the same 100-millisecond spikes while entering new areas has not solved the problem the player feels.
How to test whether storage is the bottleneck
Use a repeatable A/B test. The objective is to change only the cache location while keeping the game state and rendering conditions the same.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Rank #4
- HUGE SPEED BOOST: Get random read/write speeds that are 40%/55% faster than 980 PRO; Experience up to 1400K/1550K IOPS, while sequential read/write speeds up to 7,450/6,900 MB/s reach near the max performance of PCIe 4.0*
- BREAKTHROUGH POWER EFFICIENCY: Use less power and get more performance; Enjoy up to 50% improved performance per watt over 980 PRO, plus optimal power efficiency with max PCIe 4.0 performance**
- SMART THERMAL CONTROL: Samsung's own nickel-coated controller delivers effective thermal control; With its slim size, 990 PRO is a perfect fit for desktops and laptops that meet the PCI-SIG D8 standard***
- THE CHAMPION MAKER: Up to 65% improvement in random performance enables faster loads for an ultimate gaming experience on PS5 and DirectStorage PC games****
- SAMSUNG MAGICIAN SOFTWARE: Get the most out of your SSD with Samsung Magician's advanced yet intuitive optimization tools; Monitor drive health, protect valuable data, and receive important updates for your 990 PRO
- Identify the layer. Determine whether you are moving the GPU-driver cache, a DirectX cache, or the game/engine cache. Record the original path and the method used to relocate it. Do not assume that moving one directory moves every cache.
- Capture a baseline. Use the same game build, graphics driver, resolution, quality settings, ray-tracing options, and save or test route. Start with the same cache state. Record frame times during a repeatable traversal or effect sequence, plus average FPS.
- Watch storage telemetry. During the hitch, monitor active time, read and write latency, throughput, and queue length for the drive that contains the cache. A storage spike that coincides with the frame-time spike supports an I/O bottleneck hypothesis; high CPU utilization with little disk activity points elsewhere.
- Move only the intended cache. Follow the game, driver, or operating-system procedure for that specific cache. Keep the old copy until the test succeeds, and make sure the destination has adequate free space.
- Reproduce the same run. Use the identical scene and route. The first run after relocation may rebuild or validate data, so perform enough runs to distinguish rebuild effects from steady-state cache hits.
- Compare frame-time distributions. Look at the number and duration of spikes during traversal, not merely the mean. Also note loading time, cache rebuild time, and whether the drive shows queueing at the exact hitch.
- Interpret cautiously. A clear improvement with the cache on an HDD, accompanied by lower storage latency, supports keeping it on an SSD. No change means the hitch is more likely compilation, synchronization, a driver issue, or an engine problem. An improvement only on the first run may reflect a faster rebuild rather than smoother gameplay.
What to do before buying a faster SSD
Let the cache finish building
After a driver or game update, allow the title to sit in its shader-processing or loading phase if it provides one. Avoid judging performance from the first few minutes after invalidation. The first launch can legitimately take longer because compiled data is missing.
Use the game’s precompilation features
Engine and platform features target the expensive part—the compilation workload—rather than merely accelerating file access. Depending on the title, look for:
- Unreal Engine shader predraw: Predraw can compile required shaders before they are needed in active gameplay.
- Pipeline-state-object (PSO) precaching: The engine can prepare pipeline combinations ahead of a draw, reducing just-in-time work.
- AMD background compilation: Supported workflows compile in the background so more work is completed before the player reaches a new effect.
- Microsoft Advanced Shader Delivery: This platform approach is designed to deliver precompiled shader data instead of making every player compile all work locally.
Availability and behavior vary by game, graphics API, driver, and hardware. A title must implement these features; installing an SSD does not enable them automatically.
Check cache limits and free space
Review the driver’s shader-cache size setting and select a limit large enough for the games you routinely play while staying within the volume’s capacity. If the cache is constantly evicting older entries, a larger limit can prevent repeated recompilation. Do not fill the drive to the point that updates or normal operating-system activity fail.
Update carefully
Driver updates can clear or invalidate a cache. Plan for a rebuild after updating, and avoid concluding that the new driver caused permanent stutter based solely on its first run. If stutter continues after several complete sessions, check the game’s support notes and known issues; repeated DirectX shader recompilation can indicate a defect that storage cannot correct.
Best Value
- SPEED UP PROJECTS. Launch creator applications fast with uncompromising PCIe 4.0 read speeds up to 7,100MB/s,[2] (1TB and 2TB[1] models) and write speeds up to 6,700MB/s[2] (1TB[1]-4TB[1] models).
- CREATE AND STORE MORE. Make more room for your 4K videos and high-resolution images with capacities from 500GB[1] up to 4TB[1] on M.2 2280 built with our trusted 8th generation SANDISK BiCS QLC 3D CBA NAND.
- IT GOES WHERE YOU GO. With an all-new power efficient design, your drive delivers high performance with low power, giving you more time to be productive while on the go.
- UNCOMPROMISED RELIABILITY. With up to 1,200 TBW[3] (4TB[1] model) endurance rating, your drive is designed for creators.
- KEEP YOUR DRIVE UPDATED. Monitor your SSD’s performance and check for updates with the downloadable SANDISK Dashboard application.[5]
When clearing the shader cache is useful—and when it backfires
Clearing a cache can remove corrupted or incompatible data after a driver or game change. It is a troubleshooting reset, not a performance tweak. The immediate consequence is that the next run has no compiled entries and must rebuild them, so stutter and longer loading are expected until the cache is repopulated.
Do not repeatedly clear the cache in an attempt to “refresh” performance. If a title is smooth after several runs and becomes stuttery only after each deletion, the deletion itself is creating the condition. Fortnite support notes that the first match can remain stuttery while new shaders compile, which is consistent with this behavior.
A practical decision framework
Move the cache from an HDD to an SSD when:
- Storage telemetry shows high latency, active time, or queueing during the hitch.
- The HDD is also handling the game installation, paging, recording, antivirus scans, or other heavy work.
- The cache volume is nearly full or rebuilds take an unacceptably long time.
- You can move the cache without reducing the space available for the game and operating system.
Do not expect an SSD upgrade to solve the problem when:
- The cache is already on an SSD and monitoring shows little storage activity during spikes.
- Spikes occur only on first encounters with new effects and disappear after the area has been revisited.
- The cache is repeatedly invalidated, undersized, or corrupted.
- The game is known to compile DirectX or pipeline shaders during gameplay.
- A driver or engine defect causes repeated recompilation.
Bottom line for common questions
Will moving a shader cache to an SSD stop stuttering?
Usually not. It can reduce I/O delay for cache hits and speed rebuilding, especially when the source is an HDD, but it cannot remove first-time shader compilation.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteDoes an NVMe drive help more than a SATA SSD?
There is no official universal measurement showing a particular stutter reduction. If the cache is already on a SATA SSD and storage telemetry is quiet during the hitch, an NVMe upgrade is unlikely to address the main cause.
What is the most reliable fix?
Keep the cache large enough, let it rebuild after invalidation, use available shader or PSO precompilation, and investigate driver or game bugs when compilation repeats. Measure frame-time spikes and storage latency before spending money on a faster drive.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
