I had exactly this problem (with Errors on EventIDs 17120, 17182, 17826 & 17190), and could never find a solution, other than tediously re-installing SQL Server. I'd tried disabling VIA, using different Port numbers and just about all the other suggestions I found online, none of which helped at all.

It happened again today and I just couldn't face the re-install for some reason, but as I had to have it fixed I did one last trawl through google and finally found a solution. It was roughly as described in the following blog post:

http://www.sqlserverblogforum.com/tag/could-not-spawn-fruncm-thread/

Although at the final stage he has entered LOCAL SERVICE as the log on, that wouldn't work for me, but selecting Local System account and ticking "Allow service to interact with desktop" did. Whatever the reason, it seems accessing the Services through Control Panel gives slightly different behaviour than accessing it through the SQL Server Configuration Manager. No idea why, but it worked for me so thought I'd share in case it helped anyone else avoid a re-install