<?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: CPU Tried to Re-Acquire Lock / various BSOD message in VMware vSphere™ Discussions</title>
    <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/CPU-Tried-to-Re-Acquire-Lock-various-BSOD-message/m-p/2984844#M45992</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I've been getting the same problems since the begining of May. various CPU Lock messages or panic requested by another PCPU.&lt;/P&gt;&lt;P&gt;Running Ryzen 5 3600 with a AsRock Rack X470D4U.&lt;/P&gt;&lt;P&gt;Have also reinstalled, moved SSD. tried varoius 7-8 updates, removed unneedded packages. average uptime is 1 day, but seen it last 5 days, and as little as 1 hour.&lt;/P&gt;&lt;P&gt;Run out of ideas as well, and my next move would be to move off ESXi.&lt;/P&gt;&lt;P&gt;Any chance you managed to work it out?&lt;/P&gt;</description>
    <pubDate>Thu, 31 Aug 2023 12:16:01 GMT</pubDate>
    <dc:creator>stknt00</dc:creator>
    <dc:date>2023-08-31T12:16:01Z</dc:date>
    <item>
      <title>CPU Tried to Re-Acquire Lock / various BSOD message</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/CPU-Tried-to-Re-Acquire-Lock-various-BSOD-message/m-p/2969648#M45279</link>
      <description>&lt;P&gt;I'm having issue with ESXi random crashing recently.&lt;/P&gt;&lt;P&gt;My setup (Not in WQHL, I know, but it's been running fine for 2 years up until now):&lt;/P&gt;&lt;P&gt;- AMD Ryzen Threadripper 3970x&lt;/P&gt;&lt;P&gt;- Asrock Rack TRX40&lt;/P&gt;&lt;P&gt;- Gskill Ripjaws V DDR4 32GBx4&lt;/P&gt;&lt;P&gt;- Samsung 970 EVO Plus 2TB&lt;/P&gt;&lt;P&gt;- Intel SSD&lt;/P&gt;&lt;P&gt;- WD Red / Gold 12TB&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;ESXi crashing sometimes as soon as VM started, up to 12 hours uptime. It's just random.&lt;/P&gt;&lt;P&gt;First occurrence happened right after my UPS battery restarted, which made the server went down.&lt;/P&gt;&lt;P&gt;When I booted it again,&amp;nbsp;BSOD started to appear, with various messages when it happened:&lt;/P&gt;&lt;P&gt;- CPU Tried to Re-Acquire Lock&lt;/P&gt;&lt;P&gt;- Verify bora/vmkernel/sched/cpusched.c /&lt;/P&gt;&lt;P&gt;- #PF Exception 14 in world xxxx:vmm5:&amp;lt;random_VM_name&amp;gt; IP xxxx&lt;/P&gt;&lt;P&gt;- Spin count exceeded - possible deadlock&lt;/P&gt;&lt;P&gt;- Error closing the volume: . Eviction fails: Failure&lt;/P&gt;&lt;P&gt;- NMP: nmp_ResetDeviceLogThrottling:3839: Error status H:0x0 xxxx&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What I did:&lt;/P&gt;&lt;P&gt;- Switched ESXi to different SSD and slot (by reinstalling)&lt;/P&gt;&lt;P&gt;- Cleaned up the case, re-applied CPU thermal paste&lt;/P&gt;&lt;P&gt;- Switched RAM slot and run only 1 single stick&amp;nbsp;&lt;/P&gt;&lt;P&gt;- Re-installed ESXi using version 7.02 - 8.01&lt;/P&gt;&lt;P&gt;- Unplugged every PCIe device, including Intel NIC and Avago HBA&lt;/P&gt;&lt;P&gt;- Replaced CMOS battery and adjusted date/time&lt;/P&gt;&lt;P&gt;- Reinstalled every VM OS&lt;/P&gt;&lt;P&gt;- Switched on only one VM at a time&lt;/P&gt;&lt;P&gt;- Switched LAN cable to other port&lt;/P&gt;&lt;P&gt;Attaching various message when it happened.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please can you help me. I'm running out of ideas.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 22 May 2023 14:32:57 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/CPU-Tried-to-Re-Acquire-Lock-various-BSOD-message/m-p/2969648#M45279</guid>
      <dc:creator>gailheyil</dc:creator>
      <dc:date>2023-05-22T14:32:57Z</dc:date>
    </item>
    <item>
      <title>Re: CPU Tried to Re-Acquire Lock / various BSOD message</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/CPU-Tried-to-Re-Acquire-Lock-various-BSOD-message/m-p/2984844#M45992</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I've been getting the same problems since the begining of May. various CPU Lock messages or panic requested by another PCPU.&lt;/P&gt;&lt;P&gt;Running Ryzen 5 3600 with a AsRock Rack X470D4U.&lt;/P&gt;&lt;P&gt;Have also reinstalled, moved SSD. tried varoius 7-8 updates, removed unneedded packages. average uptime is 1 day, but seen it last 5 days, and as little as 1 hour.&lt;/P&gt;&lt;P&gt;Run out of ideas as well, and my next move would be to move off ESXi.&lt;/P&gt;&lt;P&gt;Any chance you managed to work it out?&lt;/P&gt;</description>
      <pubDate>Thu, 31 Aug 2023 12:16:01 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/CPU-Tried-to-Re-Acquire-Lock-various-BSOD-message/m-p/2984844#M45992</guid>
      <dc:creator>stknt00</dc:creator>
      <dc:date>2023-08-31T12:16:01Z</dc:date>
    </item>
    <item>
      <title>Re: CPU Tried to Re-Acquire Lock / various BSOD message</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/CPU-Tried-to-Re-Acquire-Lock-various-BSOD-message/m-p/2984897#M45995</link>
      <description>&lt;P&gt;I ended up upgrading to TR Pro. Means replacing motherboard and CPU.&lt;/P&gt;&lt;P&gt;You can try to RMA the motherboard, as CPU is the last component to fail.&lt;/P&gt;&lt;P&gt;AsRock is not very durable. Even though it's working now with the new Asrock motherboard, one of the DIMM slot is faulty and not able to detect the RAM.&lt;/P&gt;</description>
      <pubDate>Thu, 31 Aug 2023 16:53:23 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/CPU-Tried-to-Re-Acquire-Lock-various-BSOD-message/m-p/2984897#M45995</guid>
      <dc:creator>gailheyil</dc:creator>
      <dc:date>2023-08-31T16:53:23Z</dc:date>
    </item>
  </channel>
</rss>

