taskkill taskkill and ssd's

[I-Emil]

Hello dear people of the internet,

 

I'm using a boot-up batch file for my computers in order to delete some... junk and reset some app preferences and i actively refuse to use deepfreeze due to the frequency of random modifications that need to stick.

 

My batch contains... about 10 taskkill /f /im app.exe commands and a friend suggested that using taskkill in combination with /f command can lead to bad sectors on the ssd or cause the system to crash (even if the app is not a system dependent task).

 

After looking around on the internet, I have found no proof and no documentation on this effect, my question is, has anyone encountered this issue before? Or heard of this?

 

Best Regards,

Random nerd on the web

[slightlyjaded]

Okay, not actually familiar with this, so I'm seeking more info. Guessing this is a WIN 10 problem? Honestly if it isn't writing to the page file then it shouldn't be an issue. SSD's fail due to excessive overwrite (thank you dragon age) Or overheat problems.

[Windows7ge]

To my knowledge what you're doing there is effectively the same as going into the Task manager and killing an active task. Besides logging that a task has been killed in Event Viewer I don't see any meaningful degradation that would come from having this run once or twice on a daily basis.

[I-Emil]

28 minutes ago, slightlyjaded said:

Okay, not actually familiar with this, so I'm seeking more info. Guessing this is a WIN 10 problem? Honestly if it isn't writing to the page file then it shouldn't be an issue. SSD's fail due to excessive overwrite (thank you dragon age) Or overheat problems.

yes, it's a w10 machine...

 

thank you

[GoodBytes]

All I can see, is that the SSD is fine, but rather file got corrupted as you killed task that were writing data on it mid-way.