Code 64, 66 is normally a cmos error and usually fixed by clearing cmos and disable fast startup/hibernation.
Can also be System Error Codes,
https://docs.microsoft.com/en-us/windows/win32/debug/system-error-codes--0-499-
ERROR_NETNAME_DELETED
64 (0x40)
The specified network name is no longer available.
In the network level, this problem could be cause by:
Network connectivity problems have various causes, but they typically occur because of incorrect network adapters, incorrect switch settings, faulty hardware, or driver issues. Some connectivity symptoms are intermittent and do not clearly point to any one of these causes.
ERROR_BAD_DEV_TYPE
66 (0x42)
The network resource type is not correct.
https://docs.microsoft.com/en-us/windows/win32/api/winnetwk/nf-winnetwk-wnetaddconnectiona
What Causes Windows System Error Codes Errors Like Error 66?
The error can be caused by a variety of reasons. It is usually due to the system failing to properly run a program or application. It can be hardware or related to the installation or maintenance of Windows Operating System. Corrupted files, malfunctioned hardware, corrupted Registry, etc., can be the prime reasons for the occurrence of Windows System Errors.
http://www.registry-clean-up.net/kn...ystem-error-codes/error-66-error-bad-dev-type
5.2GHz would be rare to get stable at a decent voltage.
9900KS | 5.20GHz | 5.0GHz | 1.325V | Top 4% |
Source: -
https://siliconlottery.com/pages/statistics
WNetGetResourceInformation
When provided with a remote path to a network resource, the WNetGetResourceInformation function identifies the network provider that owns the resource and obtains information about the type of the resource. If the function fails, the return value is a system error code, such as one of the following values.
Return code - Description
ERROR_BAD_NET_NAME - The input lpRemoteName member is not an existing network resource for any network.
ERROR_BAD_DEV_TYPE -The input dwType member does not match the type of resource specified by the lpRemoteName member.
ERROR_EXTENDED_ERROR - A network-specific error occurred. Call WNetGetLastError to obtain a description of the error.
ERROR_MORE_DATA - The buffer pointed to by the lpBuffer parameter is too small.
ERROR_NO_NETWORK - The network is unavailable.
https://stackoverflow.com/questions/1189688/quickly-detect-if-a-file-mount-is-unavailable-in-windows https://docs.microsoft.com/en-us/wi...etgetresourceinformationa?redirectedfrom=MSDN
Appears to be network related.