Exit code 1 with nothing at all in the log directory almost always means openvpn died while parsing options, before it ever opened a log file. The quickest way to see the real message is to run it in the foreground from an elevated command prompt:
"C:\Program Files\OpenVPN\bin\openvpn.exe" --config "<path to your server.ovpn>"
Whatever Options error it prints there is your answer. Two things in the config you posted would produce exactly this, though.
First, the quotes around every path are typographic guillemets and not ASCII double quotes. If that is what is actually in the file, and not just how it pasted here, then the quote character becomes part of the filename and every file option fails at parse time. Open the file in an editor that does not autocorrect and replace them with plain " characters. While you are there, note that the backslash is an escape character inside a quoted string in OpenVPN, so either double it or use forward slashes:
ca "C:/Program Files/OpenVPN/easy-rsa/pki/ca.crt"
Second, server 172.19.0.0 255.240.0.0 is not a valid network and netmask pair. 255.240.0.0 is a /12, and the /12 that contains 172.19.x.x starts at 172.16.0.0, so OpenVPN rejects the combination. Use 172.19.0.0 255.255.0.0 for that range, or 172.16.0.0 255.240.0.0 if you really want the whole /12, although for a client pool a /24 or /22 is normally more than enough.
One more thing to check while testing: C:\OPVN_log has to exist already, OpenVPN will not create the directory, and the account the service runs under needs write access to it. A missing or unwritable log path is another way to end up with exit 1 and no log to read.
Unrelated to the crash, but on 2.7 I would drop cipher AES-256-GCM and set data-ciphers AES-256-GCM:AES-128-GCM instead. The old cipher directive is only there for compatibility with very old peers and it produces confusing negotiation warnings.
If the foreground run works and only the service fails, say which of the two services is starting it and which directory the config sits in. The automatic service and the interactive service use different config directories and run under different accounts, and that changes where to look next.
