F5F Stay Refreshed Hardware Desktop Question BSOD - Bugcheck 0x00000139 in Windows 11?

Question BSOD - Bugcheck 0x00000139 in Windows 11?

Question BSOD - Bugcheck 0x00000139 in Windows 11?

Pages (3): Previous 1 2 3 Next
T
tippestwolf70
Member
227
01-29-2022, 02:30 AM
#11
In reality, there isn't a fixed pattern, but a subtle one exists. Initially, between BSOD events, an error occurred twice—specifically, the message "Initialization failed due to the inability to create a driver device." To pinpoint the faulty interface, the provided string is used: "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000". This indicates which interface didn't initialize properly. If neither MAC address nor GUID is available, the error refers to the device name in the cluster.

Additionally, similar issues appear in sequences like "When updating secure boot, the secure boot variable could not be updated. Mistake: Secure Boot is not enabled on this computer.. For more information, see on the page https://go.microsoft.com/fwlink/?linkid=2169931". Other warnings include: "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."

There are also references to registration failures such as "Registration of the {server name} DCOM server failed during the allotted waiting time." and "The TCP/IP IPv6 interface with index 10 could not bind to the provider." These clues suggest possible network or service configuration problems.

Other entries mention driver updates preceding BSODs, differing each time, and logs vanishing for certain reasons. A screenshot of one BSOD is available: https://learn.microsoft.com/en-us/a...ub...ng-symbols.
T
tippestwolf70
01-29-2022, 02:30 AM #11

In reality, there isn't a fixed pattern, but a subtle one exists. Initially, between BSOD events, an error occurred twice—specifically, the message "Initialization failed due to the inability to create a driver device." To pinpoint the faulty interface, the provided string is used: "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000". This indicates which interface didn't initialize properly. If neither MAC address nor GUID is available, the error refers to the device name in the cluster.

Additionally, similar issues appear in sequences like "When updating secure boot, the secure boot variable could not be updated. Mistake: Secure Boot is not enabled on this computer.. For more information, see on the page https://go.microsoft.com/fwlink/?linkid=2169931". Other warnings include: "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."

There are also references to registration failures such as "Registration of the {server name} DCOM server failed during the allotted waiting time." and "The TCP/IP IPv6 interface with index 10 could not bind to the provider." These clues suggest possible network or service configuration problems.

Other entries mention driver updates preceding BSODs, differing each time, and logs vanishing for certain reasons. A screenshot of one BSOD is available: https://learn.microsoft.com/en-us/a...ub...ng-symbols.

_
_Nylo_
Junior Member
16
01-30-2022, 09:07 AM
#12
Maybe there are some faulty or damaged files.
Try using the built-in Windows troubleshooters; they might identify and resolve issues.
Execute "dism" and "sfc /scannow" from the command line.
Follow the links provided for guidance:
https://www.windowscentral.com/how-use-d...s-10-image
https://www.lifewire.com/how-to-use-sfc-...es-2626161
Also note there appear to be network-related problems.
Disable IPv6 and run "ipconfig /all" through the Command Prompt, then share the complete output here.
_
_Nylo_
01-30-2022, 09:07 AM #12

Maybe there are some faulty or damaged files.
Try using the built-in Windows troubleshooters; they might identify and resolve issues.
Execute "dism" and "sfc /scannow" from the command line.
Follow the links provided for guidance:
https://www.windowscentral.com/how-use-d...s-10-image
https://www.lifewire.com/how-to-use-sfc-...es-2626161
Also note there appear to be network-related problems.
Disable IPv6 and run "ipconfig /all" through the Command Prompt, then share the complete output here.

I
iskall99
Member
99
01-31-2022, 04:56 PM
#13
I checked the computer using sfc/scannow and DISM, neither of which found anything and writes that everything is fine. As for ip/v6, I use nekobox(nekoray) with custom settings that I made myself, since there are not many instructions where they would explain what is responsible for what. There I had ip/v6 only in the settings and ip/v6 prefer in some settings. I switched everything to ip/v4. As for ipconfig/all, I understand that this is stupid and you're just trying to help me, but I don't really want to throw this information off because this is a public forum. Perhaps there is an option, should I find the problem myself? In the sense that I need to look at a certain point or line and see discrepancies with the norm?
I
iskall99
01-31-2022, 04:56 PM #13

I checked the computer using sfc/scannow and DISM, neither of which found anything and writes that everything is fine. As for ip/v6, I use nekobox(nekoray) with custom settings that I made myself, since there are not many instructions where they would explain what is responsible for what. There I had ip/v6 only in the settings and ip/v6 prefer in some settings. I switched everything to ip/v4. As for ipconfig/all, I understand that this is stupid and you're just trying to help me, but I don't really want to throw this information off because this is a public forum. Perhaps there is an option, should I find the problem myself? In the sense that I need to look at a certain point or line and see discrepancies with the norm?

B
Benjikins
Junior Member
11
02-03-2022, 10:18 AM
#14
This command is frequently employed for diagnostics. Below is the output from my machine using Windows PowerShell:

Windows PowerShell
Copyright © Microsoft Corporation. All rights reserved.
Upgrade to the newest PowerShell version for additional features and enhancements!
https://aka.ms/PSWindows

On PS C:\Users\XXXXX> ipconfig /all
IP Configuration Status
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

Additional notes:
- Information about IP addresses can be found at the provided links.
- For more detailed guidance, you may explore further resources and tutorials.
B
Benjikins
02-03-2022, 10:18 AM #14

This command is frequently employed for diagnostics. Below is the output from my machine using Windows PowerShell:

Windows PowerShell
Copyright © Microsoft Corporation. All rights reserved.
Upgrade to the newest PowerShell version for additional features and enhancements!
https://aka.ms/PSWindows

On PS C:\Users\XXXXX> ipconfig /all
IP Configuration Status
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

Additional notes:
- Information about IP addresses can be found at the provided links.
- For more detailed guidance, you may explore further resources and tutorials.

K
kjeld_skater
Member
52
02-09-2022, 05:38 PM
#15
Setting up the IP protocol for Windows
Computer name . . . . . . . . . : XXX
The main DNS suffix . . . . . : Hybrid
Network configuration is active. . . . : No
The WINS proxy is turned on. . . . : No
Unknown nekoray-tun adapter:
DNS connection suffix . . . . : sing-tun Tunnel
Physical location. . . . : DHCP is active. . . . : No
Auto-tuning function is enabled. . . . : Yes
Local IPv6 address for the channel. . . : fe80::8c3d:c7be:8a31:bfd9%10 (Primary)
IPv4 address. . . . . : 173.16.0.1 (Main)
Subnet mask. . . . : 255.255.255.240
Main gateway. . . . : 0.0.0.0
DNS servers. . . . : 173.19.1.2
NetBIOS over TCP/IP. . . . : Active
Ethernet adapter:
Environment status. . . . . . . . : The transmission medium is not reachable.
DNS connection suffix. . . . : Realtek PCIe GbE Family Controller
Physical location. . . : 04-8B-16-13-42-75
DHCP is enabled. . . . : Yes
Auto-tuning is active. . . . : Yes
Ethernet adapter Ethernet 2:
DNS connection suffix. . . . : Remote NDIS Compatible Device
Physical location. . . : 02-0A-9C-53-35-36
DHCP is enabled. . . . : Yes
Auto-tuning is active. . . . : Yes
Local IPv6 address for the channel. . . : fe80::4505:5246:34ad:2209%15 (Primary)
IPv4 address. . . . : 192.165.42.210 (Main)
Subnet mask. . . . : 255.255.255.0
Lease information received. . . . . . . . . . . . . . . . Lease expires on 7 January 2025 at 17:58:20
Lease ne will expire until 18:58:20 on 7 January 2025
Main gateway. . . . : 192.179.42.153
DHCP server. . . . : 192.179.42.153
IPAID DHCPv6. . . . : 302123610
DHCPv6 client DUID. . . . : 00-01-00-01-5B-0C-8A-2A-04-7C-16-13-48-75
DNS servers. . . . : 192.179.42.153
NetBIOS over TCP/IP. . . . : Active
There might be minor discrepancies due to language differences; my translation was made to ensure clarity, please accept.
K
kjeld_skater
02-09-2022, 05:38 PM #15

Setting up the IP protocol for Windows
Computer name . . . . . . . . . : XXX
The main DNS suffix . . . . . : Hybrid
Network configuration is active. . . . : No
The WINS proxy is turned on. . . . : No
Unknown nekoray-tun adapter:
DNS connection suffix . . . . : sing-tun Tunnel
Physical location. . . . : DHCP is active. . . . : No
Auto-tuning function is enabled. . . . : Yes
Local IPv6 address for the channel. . . : fe80::8c3d:c7be:8a31:bfd9%10 (Primary)
IPv4 address. . . . . : 173.16.0.1 (Main)
Subnet mask. . . . : 255.255.255.240
Main gateway. . . . : 0.0.0.0
DNS servers. . . . : 173.19.1.2
NetBIOS over TCP/IP. . . . : Active
Ethernet adapter:
Environment status. . . . . . . . : The transmission medium is not reachable.
DNS connection suffix. . . . : Realtek PCIe GbE Family Controller
Physical location. . . : 04-8B-16-13-42-75
DHCP is enabled. . . . : Yes
Auto-tuning is active. . . . : Yes
Ethernet adapter Ethernet 2:
DNS connection suffix. . . . : Remote NDIS Compatible Device
Physical location. . . : 02-0A-9C-53-35-36
DHCP is enabled. . . . : Yes
Auto-tuning is active. . . . : Yes
Local IPv6 address for the channel. . . : fe80::4505:5246:34ad:2209%15 (Primary)
IPv4 address. . . . : 192.165.42.210 (Main)
Subnet mask. . . . : 255.255.255.0
Lease information received. . . . . . . . . . . . . . . . Lease expires on 7 January 2025 at 17:58:20
Lease ne will expire until 18:58:20 on 7 January 2025
Main gateway. . . . : 192.179.42.153
DHCP server. . . . : 192.179.42.153
IPAID DHCPv6. . . . : 302123610
DHCPv6 client DUID. . . . : 00-01-00-01-5B-0C-8A-2A-04-7C-16-13-48-75
DNS servers. . . . : 192.179.42.153
NetBIOS over TCP/IP. . . . : Active
There might be minor discrepancies due to language differences; my translation was made to ensure clarity, please accept.

N
Noblika
Member
52
02-09-2022, 10:31 PM
#16
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
)"
N
Noblika
02-09-2022, 10:31 PM #16

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
)"

P
PijugoElNoble
Junior Member
17
02-10-2022, 04:01 AM
#17
IPv6 is still active.
Have you altered or modified MAC addresses for any device—real or virtual?
Or changed IP addresses?
The router/gateway lease duration is only one hour, which may be an issue.
= = = =
Unknown nekoray-tun adapter:
DNS connection suffix . . . . . :
Description. . . . . . . . . . . . : sing-tun Tunnel
Physical address. . . . . . . . . :
DHCP is active. . . . . . : No
Auto-tuning is turned on. . . . . : Yes
Local IPv6 address of the channel. . . : fe80::8c3d:c7be:8a31:bfd9%10 (Primary)
IPv4 address. . . . . . . . . . : 173.16.0.1( Main)
Subnet mask . . . . . . . . . . : 255.255.255.240
Main gateway. . . . . . . . . : 0.0.0.0
DNS servers. . . . . . . . . : 173.19.1.2
NetBIOS over TCP/IP . . . . . . . . : Enabled
= = =
Not familiar with Nekoray and should defer this to those who are experienced with it and have the correct VPN setup.
P
PijugoElNoble
02-10-2022, 04:01 AM #17

IPv6 is still active.
Have you altered or modified MAC addresses for any device—real or virtual?
Or changed IP addresses?
The router/gateway lease duration is only one hour, which may be an issue.
= = = =
Unknown nekoray-tun adapter:
DNS connection suffix . . . . . :
Description. . . . . . . . . . . . : sing-tun Tunnel
Physical address. . . . . . . . . :
DHCP is active. . . . . . : No
Auto-tuning is turned on. . . . . : Yes
Local IPv6 address of the channel. . . : fe80::8c3d:c7be:8a31:bfd9%10 (Primary)
IPv4 address. . . . . . . . . . : 173.16.0.1( Main)
Subnet mask . . . . . . . . . . : 255.255.255.240
Main gateway. . . . . . . . . : 0.0.0.0
DNS servers. . . . . . . . . : 173.19.1.2
NetBIOS over TCP/IP . . . . . . . . : Enabled
= = =
Not familiar with Nekoray and should defer this to those who are experienced with it and have the correct VPN setup.

I
ItzCh3nTi_YT
Member
96
02-11-2022, 07:29 PM
#18
I did not carry out any adjustments to the network or its related parts beyond allowing nekoray.
I
ItzCh3nTi_YT
02-11-2022, 07:29 PM #18

I did not carry out any adjustments to the network or its related parts beyond allowing nekoray.

L
legonalas
Junior Member
10
02-14-2022, 03:43 AM
#19
It seems to me that only those who grasp this will notice this message. I’ve developed some new doubts. I observed a recurring issue—the BSOD occurs when I launch a browser or open a new tab while playing (whether PUBG or Hunt:Showdown, though it seems irrelevant which game). At that exact moment, the BSOD appears. There’s also a registry entry indicating "gameflt file system filter (version 10.0, 2009-11-22T22:11:52.000000000Z) successfully loaded and registered with the filter manager." I don’t fully understand what registry entries mean, but I suspect there might be a connection, possibly linked to both the game and browser activity. Both opening the game and the browser at the same time seem to trigger this problem. Still, I lack enough knowledge to confirm any direct link.
L
legonalas
02-14-2022, 03:43 AM #19

It seems to me that only those who grasp this will notice this message. I’ve developed some new doubts. I observed a recurring issue—the BSOD occurs when I launch a browser or open a new tab while playing (whether PUBG or Hunt:Showdown, though it seems irrelevant which game). At that exact moment, the BSOD appears. There’s also a registry entry indicating "gameflt file system filter (version 10.0, 2009-11-22T22:11:52.000000000Z) successfully loaded and registered with the filter manager." I don’t fully understand what registry entries mean, but I suspect there might be a connection, possibly linked to both the game and browser activity. Both opening the game and the browser at the same time seem to trigger this problem. Still, I lack enough knowledge to confirm any direct link.

D
DexterReal
Junior Member
6
02-14-2022, 12:33 PM
#20
I've already shared the content from the registry prior to and following the BSOD. It was in #17, where I repeatedly copied and pasted multiple tasks before and after the BSOD, placing the necessary details in the same location where Windows offers them.
D
DexterReal
02-14-2022, 12:33 PM #20

I've already shared the content from the registry prior to and following the BSOD. It was in #17, where I repeatedly copied and pasted multiple tasks before and after the BSOD, placing the necessary details in the same location where Windows offers them.

Pages (3): Previous 1 2 3 Next