"ipconfig /all" is a commonly used diagnostic tool.
Here is the "ipconfig /all" from my computer:
Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.
Install the latest PowerShell for new features and improvements! https://aka.ms/PSWindows
PS C:\Users\XXXXX> ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : XXXX
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : hsd1.XXXX.comcast.net
Ethernet adapter McCoole:
Connection-specific DNS Suffix . : hsd1XXXX.comcast.net
Description . . . . . . . . . . . : Realtek PCIe GbE Family Controller
Physical Address. . . . . . . . . : 8C-EC-4B-7E-7E-D4
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.1.117(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Tuesday, January 7, 2025 5:54:08 AM
Lease Expires . . . . . . . . . . : Wednesday, January 15, 2025 5:54:07 AM
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 8.8.8.8
8.8.4.4
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter Bluetooth Network Connection:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network)
Physical Address. . . . . . . . . : 74-40-BB-D5-2D-BE
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
PS C:\Users\XXXX>
Where XXXX represents possibly personally identifying information that I redacted: user name, host name, and U.S. State abbreviation which probably could be left in place.
FYI about IP addresses:
https://www.lifewire.com/what-is-a-public-ip-address-2625974
https://www.lifewire.com/what-is-a-private-ip-address-2625970
You can easily find other similar explanations and tutorials....
= = = =
Regarding:
"As for ip/v6, I use nekobox(nekoray) with custom settings that I made myself,"
I am not familar with nekobox/nekoray but it appears to be software used for circumvention purposes.
I will therefore defer to those more familar with custom IPv6 configurations and Nekobox/Nekoray.
There were no death screens for one day, but another BSOD with the same error code just happened. That's what appeared before the BSOD. "Notification of user login for the software quality improvement program" - > "The following system boot or startup drivers are not loaded:
dam" -> "This event activates the preparation or verification of the status of the trusted platform module." -> "The device identifier of the TBS service has been created." -> "The trusted platform module has been successfully prepared for operation and is ready for use." -> BSOD (The computer was restarted after a critical error. Error code: 0x0000013a (0x0000000000000012, 0xffff818e89e02140, 0xffff818e952af000, 0x0000000000000000). The memory dump is saved in: C:\WINDOWS\MEMORY.DMP . Report code: b8fc1d46-46cc-4324-84e1-e5a5b5685520.) -> "Initialization failed due to the inability to create a driver device. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface that failed initialization. The string represents the MAC address of the interface that failed initialization, or the global unique interface identifier (GUID) if NetBT failed to match the GUID to the MAC address. If neither the MAC address nor the GUID is available, then this string represents the name of the device in the cluster. (+ System
- Provider
[ Name] NetBT
- EventID 4311
[ Qualifiers] 49152
Version 0
Level 2
Task 0
Opcode 0
Keywords 0x80000000000000
- TimeCreated
[ SystemTime] 2025-01-09T18:12:28.1930923Z
EventRecordID 41525
Correlation
- Execution
[ ProcessID] 4
[ ThreadID] 332
Channel System
Computer DESKTOP-XXX
Security
- EventData
000000000100320000000000D71000C013010000250200C000000000000000000000000000000000
--------------------------------------------------------------------------------
Binary files:
According to
0000: 00000000 00320001 00000000 C00010D7
0010: 00000113 C0000225 00000000 00000000
0020: 00000000 00000000
By bytes
0000: 00 00 00 00 01 00 32 00 ......2.
0008: 00 00 00 00 D7 10 00 C0 ....×..À
0010: 13 01 00 00 25 02 00 C0 ....%..À
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
) -> "Initialization failed due to the inability to create a driver device. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface that failed initialization. The string represents the MAC address of the interface that failed initialization, or the global unique interface identifier (GUID) if NetBT failed to match the GUID to the MAC address. If neither the MAC address nor the GUID is available, then this string represents the name of the device in the cluster. (+ System
- Provider
[ Name] NetBT
- EventID 4311
[ Qualifiers] 49152
Version 0
Level 2
Task 0
Opcode 0
Keywords 0x80000000000000
- TimeCreated
[ SystemTime] 2025-01-09T18:12:28.1931486Z
EventRecordID 41526
Correlation
- Execution
[ ProcessID] 4
[ ThreadID] 332
Channel System
Computer DESKTOP-XXX
Security
- EventData
000000000100320000000000D71000C011010000250200C001000000000000000000000000000000
--------------------------------------------------------------------------------
Binary files:
According to
0000: 00000000 00320001 00000000 C00010D7
0010: 00000111 C0000225 00000001 00000000
0020: 00000000 00000000
By bytes
0000: 00 00 00 00 01 00 32 00 ......2.
0008: 00 00 00 00 D7 10 00 C0 ....×..À
0010: 11 01 00 00 25 02 00 C0 ....%..À
0018: 01 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
)" -> "Initialization failed due to the inability to create a driver device. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface that failed initialization. The string represents the MAC address of the interface that failed initialization, or the global unique interface identifier (GUID) if NetBT failed to match the GUID to the MAC address. If neither the MAC address nor the GUID is available, then this string represents the name of the device in the cluster. (+ System
- Provider
[ Name] NetBT
- EventID 4311
[ Qualifiers] 49152
Version 0
Level 2
Task 0
Opcode 0
Keywords 0x80000000000000
- TimeCreated
[ SystemTime] 2025-01-09T18:13:11.5337326Z
EventRecordID 41527
Correlation
- Execution
[ ProcessID] 4
[ ThreadID] 8124
Channel System
Computer DESKTOP-XXX
Security
- EventData
000000000100320000000000D71000C013010000250200C002000000000000000000000000000000
--------------------------------------------------------------------------------
Binary files:
According to
0000: 00000000 00320001 00000000 C00010D7
0010: 00000113 C0000225 00000002 00000000
0020: 00000000 00000000
By bytes
0000: 00 00 00 00 01 00 32 00 ......2.
0008: 00 00 00 00 D7 10 00 C0 ....×..À
0010: 13 01 00 00 25 02 00 C0 ....%..À
0018: 02 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........)" -> " Initialization failed due to the inability to create a driver device. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface that failed initialization. The string represents the MAC address of the interface that failed initialization, or the global unique interface identifier (GUID) if NetBT failed to match the GUID to the MAC address. If neither the MAC address nor the GUID is available, then this string represents the name of the device in the cluster. (+ System
- Provider
[ Name] NetBT
- EventID 4311
[ Qualifiers] 49152
Version 0
Level 2
Task 0
Opcode 0
Keywords 0x80000000000000
- TimeCreated
[ SystemTime] 2025-01-09T18:13:11.5337326Z
EventRecordID 41528
Correlation
- Execution
[ ProcessID] 4
[ ThreadID] 8124
Channel System
Computer DESKTOP-XXX
Security
- EventData
000000000100320000000000D71000C011010000250200C003000000000000000000000000000000
--------------------------------------------------------------------------------
Binary files:
According to
0000: 00000000 00320001 00000000 C00010D7
0010: 00000111 C0000225 00000003 00000000
0020: 00000000 00000000
By bytes
0000: 00 00 00 00 01 00 32 00 ......2.
0008: 00 00 00 00 D7 10 00 C0 ....×..À
0010: 11 01 00 00 25 02 00 C0 ....%..À
0018: 03 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........)" -> " The application-specific permission settings do not grant Local Launch permission for a COM server application with CLSID
Windows.SecurityCenter.SecurityAppBroker
and the APPID
Unavailable
to the NT AUTHORITY user\A SYSTEM with a security ID (S-1-5-18 ) and the LocalHost address (using LRPC) running in the application container is Unavailable with the Security ID (Unavailable). This security permission can be changed using the Component Services Administration tool.(+ System
- Provider
[ Name] Microsoft-Windows-DistributedCOM
[ Guid] {1B562E86-B7AA-4131-BADC-B6F3A001407E}
[ EventSourceName] DCOM
- EventID 10016
[ Qualifiers] 0
Version 0
Level 3
Task 0
Opcode 0
Keywords 0x8080000000000000
- TimeCreated
[ SystemTime] 2025-01-09T18:13:59.3129485Z
EventRecordID 41529
Correlation
- Execution
[ ProcessID] 1280
[ ThreadID] 1296
Channel System
Computer DESKTOP-XXX
- Security
[ UserID] S-1-5-18
- EventData
param1 for a specific application
param2 Locally
param3 Launch
param4 Windows.SecurityCenter.SecurityAppBroker
param5 is not available
param6 NT AUTHORITY
param7 SYSTEM
param8 S-1-5-18
param9 LocalHost (using LRPC)
param10 Unavailable
param11 is not available
)"