UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.75 Safari/537.36

Example URL:
www.google.com

Steps to reproduce the problem:
1. Start Chrome with --origin-to-force-quic-on=www.google.com:443 (not strictly needed, but will prevent fallback to http/2)
2. Connect to google.com with QUIC enabled
3. Have a pc where it doesn't work :-(

What is the expected behavior?

What went wrong?
Quic connection establishment failed.

I wasn't expecting any plaintext in this dump, but it quite clearly states "Write failed with error: -142 (Unknown Error)"

Hex + Ascii dump of payload:

0000   0d 57 12 ff b5 f5 d1 af 80 51 30 33 39 02 cd 9f  .W.......Q039...
0010   42 64 1d a8 1f 77 9d b9 91 a8 02 00 00 00 1b 00  Bd...w..........
0020   2d 57 72 69 74 65 20 66 61 69 6c 65 64 20 77 69  -Write failed wi
0030   74 68 20 65 72 72 6f 72 3a 20 2d 31 34 32 20 28  th error: -142 (
0040   55 6e 6b 6e 6f 77 6e 20 65 72 72 6f 72 29        Unknown error)

Did this work before? N/A 

Chrome version: 62.0.3202.75  Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: