More fun experiments with malware part 2
-
<p><strong>Virtual PC:</strong></p>
<p><strong>VMWare Workstation 15 Player</strong></p>
<p><strong>Windows 7 x64</strong></p>
<p><strong>KIS 20.0.1.780 de app + drv verifier enabled</strong></p>
<p><strong>Reproduction steps:</strong></p>
<p><span>This dump got created after KIS was able to start again, i think something was still wrong but i am not sure about the cause.</span></p>
<p><strong></strong></p>
<p><span></span></p> -
<p><strong>Virtual PC:</strong></p>
<p><strong>VMWare Workstation 15 Player</strong></p>
<p><strong>Windows 7 x64</strong></p>
<p><strong>KIS 20.0.1.780 de app + drv verifier enabled</strong></p>
<p><strong>Reproduction steps:</strong></p>
<p><span>This dump got created after KIS was able to start again, i think something was still wrong but i am not sure about the cause.</span></p>
<p><strong></strong></p>
<p><span></span></p><p>@helios_07 Hello! </p>
<p>Is there any chance to reproduce it again with some <span>conditions? </span></p>
<p>Conditions:</p>
<p>1) install KTS</p>
<p>2) Start procmon </p>
<p>3) enable traces in KTS</p>
<p>4) restart KTS (at this moment KTS will get process ID's from procmon and it'll be much more easy to understand what had happened) </p>
<p>5) try reproduce dump</p> -
<p>@helios_07 Hello! </p>
<p>Is there any chance to reproduce it again with some <span>conditions? </span></p>
<p>Conditions:</p>
<p>1) install KTS</p>
<p>2) Start procmon </p>
<p>3) enable traces in KTS</p>
<p>4) restart KTS (at this moment KTS will get process ID's from procmon and it'll be much more easy to understand what had happened) </p>
<p>5) try reproduce dump</p>
