You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What happened:
Portmaster seem to be causing KERNEL_MODE_HEAP_CORRUPTION.
What did you expect to happen?:
Not BSOD.
How did you reproduce it?:
It seems to be happening at 'random' I was testing memory to see if it was related to my ram modules and at somepoint it randomly happen (also seem to happen sometimes when waking the computer up after sleep).
Debug Information:
Version 1.6.10
Portmaster 1.6.10
built with go1.22.3 (gc -cgo) for windows/amd64
at 2024-05-15T12:03:21Z
commit 867d0bca2d71d7247039cf8e6b129580c28be7d6 (clean)
at 2024-05-15T09:08:08Z
from [email protected]:Safing/portmaster.git
Licensed under the GPLv3 license.
Platform: Microsoft Windows 10 Pro 10.0.19045 Build 19045
System: Microsoft Windows 10 Pro windows (Standalone Workstation) 10.0.19045 Build 19045
Kernel: 10.0.19045 Build 19045 x86_64
DatagramV4Callout Callout This callout is used to handle datagram data for IPv4. {a6be3096-66bf-4959-8629-1c3a4c40c31e} [no provider key] FWPM_LAYER_DATAGRAM_DATA_V4
DatagramV4Filter Filter The filter is used for handling datagram data for IPv4. {643270c6-c288-4372-826f-5888c4c72ab8} [no provider key] FWPM_LAYER_DATAGRAM_DATA_V4 {a87fb472-fc68-4805-8559-c6ae774773e0}
DatagramV6Callout Callout This callout is used to handle datagram data for IPv6. {d55cb395-29a1-4716-8cb1-65c888995f54} [no provider key] FWPM_LAYER_DATAGRAM_DATA_V6
DatagramV6Filter Filter The filter is used for handling datagram data for IPv6. {c9c3f640-3d1d-4b2a-b91c-5c9ae06fd87a} [no provider key] FWPM_LAYER_DATAGRAM_DATA_V6 {a87fb472-fc68-4805-8559-c6ae774773e0}
Edge traversal Teredo Authorization Sublayer SubLayer Edge traversal Teredo Authorization Sublayer {7b6b11f6-cbb5-433c-ae06-6a4f0076e49e}
PortmasterALEInboundV4Callout Callout This callout is used by the Portmaster to monitor outbound IPv4 traffic before the connection is established. {e36216c5-7b33-40ee-b054-fb1bc7decc19} [no provider key] FWPM_LAYER_ALE_AUTH_RECV_ACCEPT_V4
PortmasterALEInboundV4Filter Filter This filter is used by the Portmaster to monitor inbound IPv4 traffic before the connection is established. {3a4d1f9e-125c-42f5-8c75-5c2b4e62e974} [no provider key] FWPM_LAYER_ALE_AUTH_RECV_ACCEPT_V4 {a87fb472-fc68-4805-8559-c6ae774773e0}
PortmasterALEInboundV6Callout Callout This callout is used by the Portmaster to monitor outbound IPv6 traffic before the connection is established. {77ea9927-66e7-4cf8-9ea2-941edf2fae63} [no provider key] FWPM_LAYER_ALE_AUTH_RECV_ACCEPT_V6
PortmasterALEInboundV6Filter Filter This filter is used by the Portmaster to monitor inbound IPv6 traffic before the connection is established. {a20a33be-56b4-465e-a98c-075f2a2ef0c7} [no provider key] FWPM_LAYER_ALE_AUTH_RECV_ACCEPT_V6 {a87fb472-fc68-4805-8559-c6ae774773e0}
PortmasterALEOutboundV4Callout Callout This callout is used by the Portmaster to montiror outbound IPv4 traffic before the connection is established. {029819fe-97d9-4e5f-a0fb-78ef5cef8ac4} [no provider key] FWPM_LAYER_ALE_AUTH_CONNECT_V4
PortmasterALEOutboundV4Filter Filter This filter is used by the Portmaster to monitor outbound IPv4 traffic before the connection is established. {09630f39-3ef3-44db-b3c0-dcdb80c89785} [no provider key] FWPM_LAYER_ALE_AUTH_CONNECT_V4 {a87fb472-fc68-4805-8559-c6ae774773e0}
PortmasterALEOutboundV6Callout Callout This callout is used by the Portmaster to monitor outbound IPv6 traffic before the connection is established. {d6b0213a-337a-4cc6-84c0-cc60731b9e2a} [no provider key] FWPM_LAYER_ALE_AUTH_CONNECT_V6
PortmasterALEOutboundV6Filter Filter This filter is used by the Portmaster to monitor outbound IPv6 traffic before the connection is established. {08f353fa-0d41-4fbc-aaec-a9d102d932df} [no provider key] FWPM_LAYER_ALE_AUTH_CONNECT_V6 {a87fb472-fc68-4805-8559-c6ae774773e0}
PortmasterInboundV4Callout Callout This callout is used by the Portmaster to intercept inbound IPv4 traffic. {05c55149-4732-4857-8d10-f178f3a06f8c} [no provider key] FWPM_LAYER_INBOUND_IPPACKET_V4
PortmasterInboundV4Filter Filter This filter is used by the Portmaster to intercept inbound IPv4 traffic. {44c52d3c-6232-4abc-b555-56c238713d0d} [no provider key] FWPM_LAYER_INBOUND_IPPACKET_V4 {a87fb472-fc68-4805-8559-c6ae774773e0}
PortmasterInboundV6Callout Callout This callout is used by the Portmaster to intercept inbound IPv6 traffic. {ceff1df7-2baa-44c5-a6e5-73a95849bcff} [no provider key] FWPM_LAYER_INBOUND_IPPACKET_V6
PortmasterInboundV6Filter Filter This filter is used by the Portmaster to intercept inbound IPv6 traffic. {09c19418-37d0-4ad8-836d-667c42d05f17} [no provider key] FWPM_LAYER_INBOUND_IPPACKET_V6 {a87fb472-fc68-4805-8559-c6ae774773e0}
PortmasterOutboundV4Callout Callout This callout is used by the Portmaster to intercept outbound IPv4 traffic. {41162b9e-8473-4b88-a5eb-04cf1d276b06} [no provider key] FWPM_LAYER_OUTBOUND_IPPACKET_V4
PortmasterOutboundV4Filter Filter This filter is used by the Portmaster to intercept outbound IPv4 traffic. {d3ec79a3-eb75-4c30-88fa-1b195d326f8c} [no provider key] FWPM_LAYER_OUTBOUND_IPPACKET_V4 {a87fb472-fc68-4805-8559-c6ae774773e0}
PortmasterOutboundV6Callout Callout This callout is used by the Portmaster to intercept outbound IPv6 traffic. {32bad112-6af4-4109-809b-c07570ba01b4} [no provider key] FWPM_LAYER_OUTBOUND_IPPACKET_V6
PortmasterOutboundV6Filter Filter This filter is used by the Portmaster to intercept outbound IPv6 traffic. {dc62ab9b-3930-44a8-ac21-b3edf03f6c3d} [no provider key] FWPM_LAYER_OUTBOUND_IPPACKET_V6 {a87fb472-fc68-4805-8559-c6ae774773e0}
PortmasterSublayer SubLayer The Portmaster sublayer holds all it's filters. {a87fb472-fc68-4805-8559-c6ae774773e0}
StreamV4Callout Callout This callout is used to handle stream data for IPv4. {525dac52-65de-4a6f-b546-2b1f3bc226db} [no provider key] FWPM_LAYER_STREAM_V4
StreamV4Filter Filter The filter is used for handling stream data for IPv4. {c4d6d4fa-3aa0-4ae5-926d-d8e0f90187b3} [no provider key] FWPM_LAYER_STREAM_V4 {a87fb472-fc68-4805-8559-c6ae774773e0}
StreamV6Callout Callout This callout is used to handle stream data for IPv6. {4321ddf9-57b2-4391-8fc5-c5b46c655587} [no provider key] FWPM_LAYER_STREAM_V6
StreamV6Filter Filter The filter is used for handling stream data for IPv6. {36ab7728-e8ed-477e-92b7-2ee44af066c2} [no provider key] FWPM_LAYER_STREAM_V6 {a87fb472-fc68-4805-8559-c6ae774773e0}
Teredo socket option opt out block filter Filter [no description] {cdfd08f7-af7e-4208-84d7-6554553b0a2b} {cee92fc1-5059-46fc-8ad8-860283a140e1} FWPM_LAYER_ALE_AUTH_RECV_ACCEPT_V6 {7b6b11f6-cbb5-433c-ae06-6a4f0076e49e}
Greetings and welcome to our community! As this is the first issue you opened here, we wanted to share some useful infos with you:
🗣️ Our community on Discord is super helpful and active. We also have an AI-enabled support bot that knows Portmaster well and can give you immediate help.
📖 The Wiki answers all common questions and has many important details. If you can't find an answer there, let us know, so we can add anything that's missing.
Thank you for the report.
We just pushed a new version of the kernel extension in the beta channel. It includes a complete rewrite which should hopefully remove all causes of the crashes.
Similar to #1593 & #1587
Pre-Submit Checklist:
What happened:
Portmaster seem to be causing KERNEL_MODE_HEAP_CORRUPTION.
What did you expect to happen?:
Not BSOD.
How did you reproduce it?:
It seems to be happening at 'random' I was testing memory to see if it was related to my ram modules and at somepoint it randomly happen (also seem to happen sometimes when waking the computer up after sleep).
Debug Information:
Version 1.6.10
Platform: Microsoft Windows 10 Pro 10.0.19045 Build 19045
No Module Error
Status: Online
SPN: disabled (module disabled)
Resolvers: 6/6
Config: 6
Updates: stable (13/33)
Compatibility: WFP State (27)
Goroutine Stack
Windows logs:
Windows dump
The text was updated successfully, but these errors were encountered: