<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic NPCAP 1.79 - OneAgent - Blue Screen Crash in Open Q&amp;A</title>
    <link>https://community.dynatrace.com/t5/Open-Q-A/NPCAP-1-79-OneAgent-Blue-Screen-Crash/m-p/277948#M36605</link>
    <description>&lt;P&gt;The Dynatrace&amp;nbsp;OneAgent has been running in Infrastructure Monitoring mode for about a month, without problems so far.&lt;/P&gt;
&lt;P&gt;However, during a period of runtime of a database server, found to be of high&amp;nbsp;RAM congestion, reaching 92%, the server stopped and restarted, with blue&amp;nbsp;display, saying that the NPCAP.SYS element was what caused it.&lt;/P&gt;
&lt;P&gt;After&amp;nbsp;checking the technical documentation, it seems that WinPcap as well as Npcap&amp;nbsp;must be removed if both technologies (WinPcap and Npcap) reside on the same&amp;nbsp;machine. Following that, the OneAgent would also have to be uninstalled, and&amp;nbsp;then a clean installation will have to be performed, only then it can be&amp;nbsp;guaranteed that it functions properly.&lt;/P&gt;
&lt;P&gt;Anybody&amp;nbsp;else experienced it, and what additional steps did you take to solve it?&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Operating System Version: Windows Server 2016 Standard 1607, 10.0.14393&lt;/LI&gt;
&lt;LI&gt;OneAgent Mode: Infrastructure&lt;/LI&gt;
&lt;LI&gt;Virtualization: VMWare&lt;/LI&gt;
&lt;/UL&gt;</description>
    <pubDate>Mon, 26 May 2025 06:32:19 GMT</pubDate>
    <dc:creator>legajius</dc:creator>
    <dc:date>2025-05-26T06:32:19Z</dc:date>
    <item>
      <title>NPCAP 1.79 - OneAgent - Blue Screen Crash</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/NPCAP-1-79-OneAgent-Blue-Screen-Crash/m-p/277948#M36605</link>
      <description>&lt;P&gt;The Dynatrace&amp;nbsp;OneAgent has been running in Infrastructure Monitoring mode for about a month, without problems so far.&lt;/P&gt;
&lt;P&gt;However, during a period of runtime of a database server, found to be of high&amp;nbsp;RAM congestion, reaching 92%, the server stopped and restarted, with blue&amp;nbsp;display, saying that the NPCAP.SYS element was what caused it.&lt;/P&gt;
&lt;P&gt;After&amp;nbsp;checking the technical documentation, it seems that WinPcap as well as Npcap&amp;nbsp;must be removed if both technologies (WinPcap and Npcap) reside on the same&amp;nbsp;machine. Following that, the OneAgent would also have to be uninstalled, and&amp;nbsp;then a clean installation will have to be performed, only then it can be&amp;nbsp;guaranteed that it functions properly.&lt;/P&gt;
&lt;P&gt;Anybody&amp;nbsp;else experienced it, and what additional steps did you take to solve it?&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Operating System Version: Windows Server 2016 Standard 1607, 10.0.14393&lt;/LI&gt;
&lt;LI&gt;OneAgent Mode: Infrastructure&lt;/LI&gt;
&lt;LI&gt;Virtualization: VMWare&lt;/LI&gt;
&lt;/UL&gt;</description>
      <pubDate>Mon, 26 May 2025 06:32:19 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/NPCAP-1-79-OneAgent-Blue-Screen-Crash/m-p/277948#M36605</guid>
      <dc:creator>legajius</dc:creator>
      <dc:date>2025-05-26T06:32:19Z</dc:date>
    </item>
    <item>
      <title>Re: NPCAP 1.79 - OneAgent - Blue Screen Crash</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/NPCAP-1-79-OneAgent-Blue-Screen-Crash/m-p/292300#M38355</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/85889"&gt;@legajius&lt;/a&gt;, does this issue still occur? Did you manage to solve it?&lt;/P&gt;</description>
      <pubDate>Tue, 30 Dec 2025 15:25:39 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/NPCAP-1-79-OneAgent-Blue-Screen-Crash/m-p/292300#M38355</guid>
      <dc:creator>GosiaMurawska</dc:creator>
      <dc:date>2025-12-30T15:25:39Z</dc:date>
    </item>
  </channel>
</rss>

