0x0000010E: STATUS_PRIMARY_TRANSPORT_CONNECT_FAILED
Windows Error Code Lookup: Decode Windows error codes: Win32, HRESULT (0x80070005), NTSTATUS, Windows Update, msiexec and blue-screen stop codes, with what to check next.
Paste the number from an error dialog, event log, script or setup log: 0x80070005, 80070005,
-2147024891, 1603, 0xC0000005, a stop code like 0x7E, a name like
E_ACCESSDENIED, or a few words. You get every way Windows could mean that number (an HRESULT often wraps a
Win32 error, so 0x80070005 is "Access is denied" too), its parts decoded, and what to check for the common ones. Names
and messages come from the Windows SDK headers and Windows' own message tables; see Microsoft's
System Error Codes and
[MS-ERREF] for the full references.
Try: 0x80070005, 1603, 0xC0000005, 0x800F081F, 0x8024402C, 0x7E, access denied
0x0000010E = 270
NTSTATUS 0x0000010E
{Connect Failure on Primary Transport} An attempt was made to connect to the remote server %hs on the primary transport, but the connection failed. The computer WAS able to connect on a secondary transport.
Becomes the Win32 error: 746ERROR_PRIMARY_TRANSPORT_CONNECT_FAILED: {Connect Failure on Primary Transport} An attempt was made to connect to the remote server %hs on the primary transport, but the connection failed. The computer WAS able to connect on a secondary transport.
| Severity (bits 30-31) | 0: Success |
|---|---|
| Customer (bit 29) | 0: Microsoft |
| Facility | 0 (0x000) |
| Code | 270 (0x010E) |
Stop code 0x0000010E (blue screen)
Open the dump in C:\Windows\Minidump with WinDbg and run !analyze -v to see which driver was involved. Microsoft's bug check reference explains the four parameters for each code.