@Wilson.Wang Perhaps the developer will find a way in Streamfab 6 or 7 to optimize the processing or remuxing so that fewer disk writes occur. My Streamfab hard drive is now dead. [upl-image-preview uuid=a494316c-2e75-433f-bd24-5f6966e32b38 url=https://forum.dvdfab.cn/assets/files/2025-11-16/1763306001-223600-image.png alt={TEXT?}]

perhaps add second hdd for archive purposes, or use better brand of nvme like WD black. no issues here

My D: drive, which I use for downloading, was like this a year ago when I designated it for that purpose. Be sure to turn off defragmentation in Windows. ![](https://i.postimg.cc/4y4TGHtS/Snap574.jpg) Btw, try HDD Regenerator

@"simchris"#p471073 Well, every SSD eventually fails, regardless of the manufacturer...and an HDD for Streamfab isn't an option, that takes way too long.

It's the original one that was in the device when I bought it... I've now decided on a Seagate FireCuda 530R 1TB...

When I think of Redfox now, I remember the processing took less than a second...they solved it differently...

@"Sebastian001"#p471069 isn't 512GiB Intel Pro 6000p rated for something stupidly low like 72TB of lifetime writes? and it looks like the firmware in it was never updated (I doubt HP is still on firmware release 1 for that, and do they still think that trim is overrated? I was so done with them when they proudly stated that their enterprise SAS SSDs didn't do unmap) TL;DR: cheap TLC SSD, rated as READ-intensive, not expected to last by any measure. 🤷♂️

@"Sebastian001"#p471077 they used a different set of tools... BUT what SF can do is at the very least have a switch that disables the daft faststart flag of ffmpeg, or make that a registry key so the lowest common denominator has faststart switched on, and those who want it switched off (and know the potential consequences) can have a means of disabling it.

@"0xFeedBeef"#p471083 https://dl.dvdfab.cn/download/StreamFab_x64_6263official_2025_11_17_17_44_39_utility_tool_dev_disablefaststart_streameta_dev_vs2019_d43046fa.exe A test version that disable the ffmpeg faststart. You can check it first. Wilson

@"Wilson.Wang"#p471098 just tried with a 4K download from D+, download, remux, and playback seem absolutely fine! Now I can move away from my 500GiB RAM disk 😏 @"Sebastian001"#p471069 provided that "available spare" and "available spare threshold" are reported correctly, you can safely ignore the "percentage used" that's no more than a "best before" date for gullible customers- it's not like the SSD is gonna turn into a pumpkin at the turn of midnight 😉 It's just a value based on statistical _modelling_... The problem with SSD drive wear is that you lose ability to program a cell, not read its value (well, within limits). So when you fail to program a cell, you just use a spare block, so so long as you have those to go (recall that the SMART-reported values are normalised (100%)), you're fine; it's when you start eating into them and they get close to the available threshold that you need to start thinking about replacing. In your case, you actually are already eating into the available spare (your counter is at 0x54, or 84%) and that's probably being down to it being TLC. In my case, and I'm using MLC, I'm at 120% (0x78) "used" on my boot drive, and it's still not touched a spare block... 👇 [upl-image-preview uuid=349572e3-0708-4b4e-964f-c211e714d930 url=https://forum.dvdfab.cn/assets/files/2025-11-17/1763389084-384615-image.png alt={TEXT?}]

The OP has a very valid point. When I was using a regular HDD as the temp and download folder, the drive noise was horrendous. Moving it to a spare SSD simply made the noise go away, but the constant IO is still happening. To those out there ready to point out "Get a better drive" --- Samsung has the best drives out there.

SSD Bad

Germania

0xFeedBeef -disposition:a:0 default -movflags +disable_chpl

This is the correct cmdline but for me always space before -movflags is missing
I try amazon.com + PrimeVideo.com later (but why it should be different?) ..

0xFeedBeef

Germania literally have no idea why, that’s why I’m trying to find the discriminating factor so that people at SF roll out “no faststart” for good

Germania

0xFeedBeef I’m trying to find the discriminating factor so that people at SF roll out “no faststart” for good

Okay, I found the trigger for my missing space ..
.. this happen if the MetaPicture\cover.png is missing

This only affects those who prevent MetaPicture
because they do not want a cover - see my workaround here

0xFeedBeef

Germania what if you meet SF half-way: make a 1×1px cover.png, stick that into the MetaPicture folder and make both read-only?

AGuyWithAComputer

Apparently, my SSD I’ve been using for Plex transcodes for the last 10 years see less action.

Ok, nearly 10 years. It was purchased in July 2016

I use a spinner for SF downloads

Sebastian001

Oh, I haven’t been here for three days and there are already three updates… I’m confused. Which stable version contains the SSD (Fast Start) fix?

Germania

Sebastian001 Which stable version contains the SSD (Fast Start) fix?

None - the two subsequent releases (6265+6) were merely AppleTV corrections
(initially for the queue and only 3 DL available, 2nd for non-US customers)

MrGrackle

october262 Excessive SSD writes
can be caused by factors like malware, continuous disk swapping due to low RAM, and certain background processes, but can also be due to legitimate heavy workloads like video streaming or large file caching. To fix this, increase RAM, scan for malware, disable unnecessary services like Superfetch (SysMain), or check for Windows/driver updates

Are you suggesting SF is malware? 😂
The only time I would see major disk access is when SF is downloading. Even the processing phase doesn’t hit the drive very much.
Redfox didn’t nail the drive as much.

MrGrackle

My Samsung 860 Pro 2Tb Sata drive that I have been using for SF’s download/temp files for several years is still showing 97%.
My system drive, a Samsung 990 Pro 2 Tb NVM drive that is only ⅓ as old is showing 98%.
So I don’t know. Yes SF hammers the download drive, but maybe it’s how you manage it.
My SF download drive also temporarily stores the downloads. From time to time when the drive starts to get >80% full, I move the data to other drives. This is probably a more prudent approach because you are not writing to the same blocks over and over again.

MrGrackle

Shown here.. (is funny what the NVM drive shows for temperature. It literally sits below the graphics card)

Sebastian001

My new NVMe SSD reaches up to 140 degrees Fahrenheit during remuxing. Should I be worried?

0xFeedBeef

Sebastian001 virtually all SSDs have thermal throttling. Having said that, SSDs are a weird creatures in that you actually want the memory cells to be warmer (easier to program) while you want the controller to be cooler…

BearBo

Temp of 140F/60C is hot, but not dangerous. NVME SSD should be throttling at these temps to prevent harm.
I’d be more concerned with the slowdown the throttling will be causing.
Is your SSD Gen4 or Gen5 ? Faster Gen5 drives generate more heat to dissipate.
Are you using a SSD heatsink? Any generation NVME will benefit from a good sink, but especially G5 drives.
When recoding, my primary Samsung 9100 Pro will hit 55C even with Samsung heatsink.
My 2 Intel Gen3 2TB NVME storage drives only max at 33C under recoding load.

Regarding the original question, Both the Intel NVMes have had over 13+ TB written and 5000+ hours uptime.
Neither shows any flags and CyrstalDiskInfo status for both is 100%
Sebastian001’s CDInfo image shows the drive has been really hammered for a little drive. It needs to be retired and something newer/larger & more appropriate to such usage installed.

Sebastian001

New: SeagateFireCuda 530R ZP1000GM30063

It doesn’t have a heatsink, just like the old one in the laptop. Now I’m using a laptop cooling pad.

« Previous Page