<?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 Re: I can replicate Freezing problem in Archive</title>
    <link>https://community.solidigm.com/t5/archive/i-can-replicate-freezing-problem/m-p/19566#M11642</link>
    <description>&lt;P&gt;You mean for example if 1st sector is read and then next (2nd sector) is written to, the freezing occurs?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The solution is increasing delay and could be as well for skipping the next sector to write data too.&lt;/P&gt;</description>
    <pubDate>Fri, 28 Sep 2012 19:54:47 GMT</pubDate>
    <dc:creator>idata</dc:creator>
    <dc:date>2012-09-28T19:54:47Z</dc:date>
    <item>
      <title>I can replicate Freezing problem</title>
      <link>https://community.solidigm.com/t5/archive/i-can-replicate-freezing-problem/m-p/19564#M11640</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Not sure how to get Intel to listen, but the freezing problem is caused by a read immediately followed by a write.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I wrote a rough and dirty program that Seeks to a random spot in an existing file, then writes to the same file in the next indexed spot. Crash! every time it locks up.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The index is the size of the buffer used to read/write. Using a 512 Byte Buffer, I Seek to random spot and read the BufferLen, then move the file pointer 512 (BufferLen) Bytes ahead and write the buffer back.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If I add at least a 10 millisecond delay between the read and write it all runs fine.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I tried differing BufferLen but it still crashes. The only thing that stops the freeze is inserting the delay. And, that delay needs to be about 8 to 10 mS minimum. Less than 8 it still freezes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 12 Sep 2012 00:01:59 GMT</pubDate>
      <guid>https://community.solidigm.com/t5/archive/i-can-replicate-freezing-problem/m-p/19564#M11640</guid>
      <dc:creator>idata</dc:creator>
      <dc:date>2012-09-12T00:01:59Z</dc:date>
    </item>
    <item>
      <title>Re: I can replicate Freezing problem</title>
      <link>https://community.solidigm.com/t5/archive/i-can-replicate-freezing-problem/m-p/19565#M11641</link>
      <description>&lt;P&gt;Interesting.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Have you also tried the routine with another SSD (perhaps a non-Sandforce based) on the same machine to confirm that the outcome is linked to the drive and not the platform?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What chipset/SATA controller does your test machine have?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Do you think it would be possible to make a version of the test program that is safe for general consumption? Perhaps with a bundled dummy test file and the source code included.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have various Intel* and Samsung SSDs I could run the test on. However, none of my drives (or combinations of drives and mainboard chipsets) suffer from any freezes in daily operation.&lt;/P&gt;&lt;P&gt;*Only one is Sandforce-based, though. A 60GB 520 series.&lt;/P&gt;</description>
      <pubDate>Fri, 14 Sep 2012 20:32:54 GMT</pubDate>
      <guid>https://community.solidigm.com/t5/archive/i-can-replicate-freezing-problem/m-p/19565#M11641</guid>
      <dc:creator>UHans</dc:creator>
      <dc:date>2012-09-14T20:32:54Z</dc:date>
    </item>
    <item>
      <title>Re: I can replicate Freezing problem</title>
      <link>https://community.solidigm.com/t5/archive/i-can-replicate-freezing-problem/m-p/19566#M11642</link>
      <description>&lt;P&gt;You mean for example if 1st sector is read and then next (2nd sector) is written to, the freezing occurs?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The solution is increasing delay and could be as well for skipping the next sector to write data too.&lt;/P&gt;</description>
      <pubDate>Fri, 28 Sep 2012 19:54:47 GMT</pubDate>
      <guid>https://community.solidigm.com/t5/archive/i-can-replicate-freezing-problem/m-p/19566#M11642</guid>
      <dc:creator>idata</dc:creator>
      <dc:date>2012-09-28T19:54:47Z</dc:date>
    </item>
    <item>
      <title>Re: I can replicate Freezing problem</title>
      <link>https://community.solidigm.com/t5/archive/i-can-replicate-freezing-problem/m-p/19567#M11643</link>
      <description>&lt;P&gt;I can consistently reproduce the freeze/hang at will using CrystalDiskMark3_0_1c x64 too.&lt;/P&gt;&lt;P&gt;Run random 512K block size test with the tool, test size does't matter. &lt;/P&gt;&lt;P&gt;Reads are all good with ~450MB/s.&lt;/P&gt;&lt;P&gt;For Write, sometimes it can finish 1 or 2 loop with ~150MB/s, and then the hdd led goes off and freeze!!&lt;/P&gt;&lt;P&gt;I have to do hard reset.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Tried everything but no luck....  &lt;/P&gt;&lt;P&gt;1. installed latest IRST (before i've done this, random BSOD)&lt;/P&gt;&lt;P&gt;2. disable all CPU C-state in bios&lt;/P&gt;&lt;P&gt;3. enable hot plug of the SATA device in bios&lt;/P&gt;&lt;P&gt;4. registry edit trick&lt;/P&gt;&lt;P&gt;5. disable trim&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Would you bother to try my CrystalDiskMark test case also?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Tue, 16 Oct 2012 15:27:47 GMT</pubDate>
      <guid>https://community.solidigm.com/t5/archive/i-can-replicate-freezing-problem/m-p/19567#M11643</guid>
      <dc:creator>idata</dc:creator>
      <dc:date>2012-10-16T15:27:47Z</dc:date>
    </item>
    <item>
      <title>Re: I can replicate Freezing problem</title>
      <link>https://community.solidigm.com/t5/archive/i-can-replicate-freezing-problem/m-p/19568#M11644</link>
      <description>&lt;P&gt;The test goes well for me and turning off Windows write-cache buffer flushing did not do anything. I could also try turning off write-caching but I doubt it will do anything.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What registry edit did you perform? Was it about disabling DPMI?&lt;/P&gt;</description>
      <pubDate>Thu, 25 Oct 2012 21:41:26 GMT</pubDate>
      <guid>https://community.solidigm.com/t5/archive/i-can-replicate-freezing-problem/m-p/19568#M11644</guid>
      <dc:creator>idata</dc:creator>
      <dc:date>2012-10-25T21:41:26Z</dc:date>
    </item>
    <item>
      <title>Re: I can replicate Freezing problem</title>
      <link>https://community.solidigm.com/t5/archive/i-can-replicate-freezing-problem/m-p/19569#M11645</link>
      <description>&lt;P&gt;Hi Lun,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We've tried recreating your report of freezing with CrystalDiskMark but it runs OK for us.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you are still having problems I suggest you contact Customer Support.  You can find contact information at:&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.intel.com/p/en_US/support/contactsupport" rel="nofollow noopener noreferrer"&gt;http://www.intel.com/p/en_US/support/contactsupport&lt;/A&gt; &lt;A href="http://www.intel.com/p/en_US/support/contactsupport" rel="nofollow noopener noreferrer"&gt;http://www.intel.com/p/en_US/support/contactsupport&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Fri, 15 Feb 2013 19:28:43 GMT</pubDate>
      <guid>https://community.solidigm.com/t5/archive/i-can-replicate-freezing-problem/m-p/19569#M11645</guid>
      <dc:creator>KenF_Intel</dc:creator>
      <dc:date>2013-02-15T19:28:43Z</dc:date>
    </item>
  </channel>
</rss>

