<?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 Incompatible with iaStor.sys in Software Archive</title>
    <link>https://community.intel.com/t5/Software-Archive/Incompatible-with-iaStor-sys/m-p/862247#M7750</link>
    <description>&lt;P&gt;Hello, experts.&lt;/P&gt;
&lt;P&gt;I work in the anti-virus company and I am engaged in driver working out. One of its possibilities is a reading of a disk on a low level. To one of versions of your driver occurs BSOD at sending on the ATA-device of command ATA_IDENTIFY_DEVICE by means of IOCTL_ATA_PASS_THROUGH_DIRECT. BSOD occurs in your driver, after sending to it of it IOCTL.&lt;/P&gt;
&lt;P&gt;1: kd&amp;gt; lmvm iastor&lt;BR /&gt;start    end        module name&lt;BR /&gt;82e6d000 82f47000   iaStor     (no symbols)           &lt;BR /&gt; Loaded symbol image file: iaStor.sys&lt;BR /&gt; Image path: \\SystemRoot\\system32\\DRIVERS\\iaStor.sys&lt;BR /&gt; Image name: iaStor.sys&lt;BR /&gt; Timestamp:        Sat Sep 13 00:31:52 2008 (48CAD1B8)&lt;BR /&gt; CheckSum:         0004FF15&lt;BR /&gt; ImageSize:        000DA000&lt;BR /&gt; Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;1: kd&amp;gt; kb&lt;BR /&gt; *** Stack trace for last set context - .thread/.cxr resets it&lt;BR /&gt;ChildEBP RetAddr  Args to Child              &lt;BR /&gt;WARNING: Stack unwind information not available. Following frames may be wrong.&lt;BR /&gt;c1bc95dc 82eacb21 861a00e0 00000000 8798cc40 iaStor+0x273f&lt;BR /&gt;c1bc95f8 82eae086 8798cc40 a25eb710 879598c8 iaStor+0x3fb21&lt;BR /&gt;c1bc961c 828779c6 861a0028 8798ccf8 ffd21024 iaStor+0x41086&lt;BR /&gt;c1bc9634 807c16c2 ffd21024 c1bc9654 807c807a nt!IofCallDriver+0x63&lt;BR /&gt;c1bc9640 807c807a 86793bd8 8798cc40 8798ccf8 acpi!ACPIDispatchForwardIrp+0x2a&lt;BR /&gt;c1bc9654 807c1f02 86793bd8 8798cc40 8798cc40 acpi!ACPIIrpDispatchDeviceControl+0xa4&lt;BR /&gt;c1bc9684 828779c6 86793bd8 86165c60 8798cd38 acpi!ACPIDispatchIrp+0x19a&lt;BR /&gt;c1bc969c 8b3bfbce fffdcc2d 8798cc40 89523ac8 nt!IofCallDriver+0x63&lt;BR /&gt;c1bc9720 8b3a9e32 89523ac8 8798cc40 8798cc40 CLASSPNP!ClassDeviceControl+0xca5&lt;BR /&gt;c1bc973c 8b3bfc6c 89523ac8 0004d030 00000000 disk!DiskDeviceControl+0x1ac&lt;BR /&gt;c1bc9758 8b3bed44 89523ac8 8798cc40 89523ac8 CLASSPNP!ClassDeviceControlDispatch+0x48&lt;BR /&gt;c1bc976c 828779c6 89523ac8 8798cc40 00000000 CLASSPNP!ClassGlobalDispatch+0x20&lt;BR /&gt;c1bc9784 805ef1de 8881a7c8 8798cc40 00000000 nt!IofCallDriver+0x63&lt;BR /&gt;c1bc97b4 805e66d1 0081a7c8 00000000 805e61b0 partmgr!PmIoctlPassThrough+0x11c&lt;BR /&gt;c1bc97d4 805e61cd 00000000 8881a8b8 8798cd1c partmgr!PmFilterDeviceControl+0xc8&lt;BR /&gt;c1bc97e8 a51910ca 8881a7c8 8798cc40 00000000 partmgr!PmGlobalDispatch+0x1d&lt;/P&gt;
&lt;P&gt;If there is a necessity, we can give kernel memory dump.&lt;/P&gt;</description>
    <pubDate>Thu, 25 Mar 2010 11:35:03 GMT</pubDate>
    <dc:creator>rkhunter</dc:creator>
    <dc:date>2010-03-25T11:35:03Z</dc:date>
    <item>
      <title>Incompatible with iaStor.sys</title>
      <link>https://community.intel.com/t5/Software-Archive/Incompatible-with-iaStor-sys/m-p/862247#M7750</link>
      <description>&lt;P&gt;Hello, experts.&lt;/P&gt;
&lt;P&gt;I work in the anti-virus company and I am engaged in driver working out. One of its possibilities is a reading of a disk on a low level. To one of versions of your driver occurs BSOD at sending on the ATA-device of command ATA_IDENTIFY_DEVICE by means of IOCTL_ATA_PASS_THROUGH_DIRECT. BSOD occurs in your driver, after sending to it of it IOCTL.&lt;/P&gt;
&lt;P&gt;1: kd&amp;gt; lmvm iastor&lt;BR /&gt;start    end        module name&lt;BR /&gt;82e6d000 82f47000   iaStor     (no symbols)           &lt;BR /&gt; Loaded symbol image file: iaStor.sys&lt;BR /&gt; Image path: \\SystemRoot\\system32\\DRIVERS\\iaStor.sys&lt;BR /&gt; Image name: iaStor.sys&lt;BR /&gt; Timestamp:        Sat Sep 13 00:31:52 2008 (48CAD1B8)&lt;BR /&gt; CheckSum:         0004FF15&lt;BR /&gt; ImageSize:        000DA000&lt;BR /&gt; Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;1: kd&amp;gt; kb&lt;BR /&gt; *** Stack trace for last set context - .thread/.cxr resets it&lt;BR /&gt;ChildEBP RetAddr  Args to Child              &lt;BR /&gt;WARNING: Stack unwind information not available. Following frames may be wrong.&lt;BR /&gt;c1bc95dc 82eacb21 861a00e0 00000000 8798cc40 iaStor+0x273f&lt;BR /&gt;c1bc95f8 82eae086 8798cc40 a25eb710 879598c8 iaStor+0x3fb21&lt;BR /&gt;c1bc961c 828779c6 861a0028 8798ccf8 ffd21024 iaStor+0x41086&lt;BR /&gt;c1bc9634 807c16c2 ffd21024 c1bc9654 807c807a nt!IofCallDriver+0x63&lt;BR /&gt;c1bc9640 807c807a 86793bd8 8798cc40 8798ccf8 acpi!ACPIDispatchForwardIrp+0x2a&lt;BR /&gt;c1bc9654 807c1f02 86793bd8 8798cc40 8798cc40 acpi!ACPIIrpDispatchDeviceControl+0xa4&lt;BR /&gt;c1bc9684 828779c6 86793bd8 86165c60 8798cd38 acpi!ACPIDispatchIrp+0x19a&lt;BR /&gt;c1bc969c 8b3bfbce fffdcc2d 8798cc40 89523ac8 nt!IofCallDriver+0x63&lt;BR /&gt;c1bc9720 8b3a9e32 89523ac8 8798cc40 8798cc40 CLASSPNP!ClassDeviceControl+0xca5&lt;BR /&gt;c1bc973c 8b3bfc6c 89523ac8 0004d030 00000000 disk!DiskDeviceControl+0x1ac&lt;BR /&gt;c1bc9758 8b3bed44 89523ac8 8798cc40 89523ac8 CLASSPNP!ClassDeviceControlDispatch+0x48&lt;BR /&gt;c1bc976c 828779c6 89523ac8 8798cc40 00000000 CLASSPNP!ClassGlobalDispatch+0x20&lt;BR /&gt;c1bc9784 805ef1de 8881a7c8 8798cc40 00000000 nt!IofCallDriver+0x63&lt;BR /&gt;c1bc97b4 805e66d1 0081a7c8 00000000 805e61b0 partmgr!PmIoctlPassThrough+0x11c&lt;BR /&gt;c1bc97d4 805e61cd 00000000 8881a8b8 8798cd1c partmgr!PmFilterDeviceControl+0xc8&lt;BR /&gt;c1bc97e8 a51910ca 8881a7c8 8798cc40 00000000 partmgr!PmGlobalDispatch+0x1d&lt;/P&gt;
&lt;P&gt;If there is a necessity, we can give kernel memory dump.&lt;/P&gt;</description>
      <pubDate>Thu, 25 Mar 2010 11:35:03 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Archive/Incompatible-with-iaStor-sys/m-p/862247#M7750</guid>
      <dc:creator>rkhunter</dc:creator>
      <dc:date>2010-03-25T11:35:03Z</dc:date>
    </item>
    <item>
      <title>Incompatible with iaStor.sys</title>
      <link>https://community.intel.com/t5/Software-Archive/Incompatible-with-iaStor-sys/m-p/862248#M7751</link>
      <description>&lt;P&gt;Hello rkhunter,&lt;BR /&gt;&lt;BR /&gt;This is somewhat outside of the scope of what we are able to supportwithin the Intel Software Network. This design inquiry would be best addressed by an Intel Product Representative.&lt;/P&gt;
&lt;P&gt;If your company has its own Intel representative, you may wish to inquire whether they are able to assist with this inquiry. Your company's Purchasing Department will normally have your Intel representative's contact information. If you have no contact, please see &lt;A href="http://www.intel.com/buy/networking/design.htm" target="_blank"&gt;http://www.intel.com/buy/networking/design.htm&lt;/A&gt; under "Design Components".&lt;/P&gt;
&lt;P&gt;If your location is not listed, please see an Intel Authorized Distributor and ask for a Field Application Engineer (FAE). Our Intel Authorized Distributor list is also linked from the URL above.&lt;BR /&gt;&lt;BR /&gt;==&lt;/P&gt;
&lt;P&gt;Lexi S.&lt;/P&gt;
&lt;P&gt;Intel Software Network Support&lt;/P&gt;
&lt;P&gt;&lt;A href="http://software.intel.com/sites/support/" target="_blank"&gt;http://software.intel.com/sites/support/&lt;/A&gt;&lt;/P&gt;
&lt;BR /&gt;</description>
      <pubDate>Thu, 25 Mar 2010 16:08:18 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Archive/Incompatible-with-iaStor-sys/m-p/862248#M7751</guid>
      <dc:creator>Intel_Software_Netw1</dc:creator>
      <dc:date>2010-03-25T16:08:18Z</dc:date>
    </item>
  </channel>
</rss>

