PFN_REFERENCE_COUNT BSOD after long time packet capture
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 3.6k
- Forks
- 592
- PR merge metrics
- No merged PRs in 30d
Description
This bsod happened about 14 hours after running. Have tried both npcap 1.79 and latest 1.84. The call stack looks almost identical. Any help would be greatly appreciated!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Begin by examining the attached 103025-5203-01.dmp and 103125-5328-01.dmp files, then compare their call stacks and the reported PFN_REFERENCE_COUNT BSOD after long packet capture. Reproduce the extended capture scenario if possible and determine a confirmed root cause; completion requires a maintainer-validated fix or diagnosis.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- networking, operating-systems
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100