This is now resolved.

Managed to start SQL Server in single user access mode and login using named pipes through SSMS. Removed the offending trigger and bobs your uncle.