Limitation of physical ESX (memory)

Similar Questions

• Distribution of load among the groups, only one thread limited to physical CPU (& memory)?

  I was not able to discern, documentation, I read so well how the load of a virtual machine is distributed should the load exceeds the limits of one CPU heart.

  At what level is the distributed load between the physical processors cores and especially between physical servers?

  At the level of the Virtual Machines,

  At the level of the process.

  At the level of the threads, or

  Somehow secondary thread?

  I'll ask another way; the ESX provides virtual processors that exceed the capacity of the hearts of single-processor or single servers, which also has the ability to run a single thread that consumes the entire capacity of the virtual processor?

  Can someone point me in the right direction?

  There is good documentation for this issue?

  AiwarikiaR-

  I don't think that it is wrong, unless you only have 1 VM.

  If you have more 1VM, with the processors maintain will almost always help them performance.

  best place to like this doco is VMWorld transcripts and VMware classes.

  -Matt

• How to check the ESX memory for errors?

  Hi all

  I faced with the strange behavior of ESX:

  Some linux VMs (RHEL) were stopped. No error messages in the vCenter nor LabManager, I even thought that someone just connected and Runic stop.

  Below you will find information of ESX server logs:

  (1) the vmkernel newspaper:

  #grep - color = always-i ' 1922 [^ 0-9] "... /VMkernel *"

  .. (/ VMkernel.8:Dec 8 22:22:40 WKK1EC02 vmkernel: 290:11:51:47.230 cpu14:23084) UserDump: 1441: Dumping cartel 23079 (of the world 23084) to file the vmfs/volumes/4a4ce277-4a35505c-8828-0024817b058c/labmanager/1922/vmware-vmx-zdump.000...

  (2) the journal of the VM:

  # grep ' 08 Dec' /vmfs/volumes/4a4ce277-4a35505c-8828-0024817b058c/labmanager/1922/vmware-1.log '.

  16:53:49.164 Dec 08: vmx | GuestRpcSendTimedOut: message to the Toolbox has expired.
  16:54:14.972 Dec 08: vmx | GuestRpcSendTimedOut: message to the Toolbox has expired.
  21:59:05.262 Dec 08: mks | Cannot write the temporary image THUMB
  21:59:15.264 Dec 08: mks | Cannot write the temporary image THUMB
  21:59:30.270 Dec 08: mks | Cannot write the temporary image THUMB
  21:59:35.271 Dec 08: mks | Cannot write the temporary image THUMB
  21:59:45.275 Dec 08: mks | Cannot write the temporary image THUMB
  21:59:50.285 Dec 08: mks | Cannot write the temporary image THUMB
  22:00:00.274 Dec 08: mks | Cannot write the temporary image THUMB
  22:00:05.276 Dec 08: mks | Cannot write the temporary image THUMB
  22:01:15.410 Dec 08: mks | Cannot write the temporary image THUMB
  22:03:25.312 Dec 08: mks | Cannot write the temporary image THUMB
  22:05:00.324 Dec 08: mks | Cannot write the temporary image THUMB
  22:05:05.340 Dec 08: mks | Cannot write the temporary image THUMB
  22:05:15.331 Dec 08: mks | Cannot write the temporary image THUMB
  22:05:20.341 Dec 08: mks | Cannot write the temporary image THUMB
  22:05:30.344 Dec 08: mks | Cannot write the temporary image THUMB
  22:05:35.353 Dec 08: mks | Cannot write the temporary image THUMB
  22:05:40.354 Dec 08: mks | Cannot write the temporary image THUMB
  22:05:45.366 Dec 08: mks | Cannot write the temporary image THUMB
  22:05:50.357 Dec 08: mks | Cannot write the temporary image THUMB
  22:05:55.361 Dec 08: mks | Cannot write the temporary image THUMB
  22:06:00.365 Dec 08: mks | Cannot write the temporary image THUMB
  22:06:05.371 Dec 08: mks | Cannot write the temporary image THUMB
  22:06:10.395 Dec 08: mks | Cannot write the temporary image THUMB
  22:06:15.379 Dec 08: mks | Cannot write the temporary image THUMB
  22:06:20.381 Dec 08: mks | Cannot write the temporary image THUMB
  22:06:30.397 Dec 08: mks | Cannot write the temporary image THUMB
  22:06:40.403 Dec 08: mks | Cannot write the temporary image THUMB
  22:20:45.541 Dec 08: mks | Cannot write the temporary image THUMB
  22:21:10.580 Dec 08: mks | Cannot write the temporary image THUMB
  22:21:15.538 Dec 08: mks | Cannot write the temporary image THUMB
  22:21:20.554 Dec 08: mks | Cannot write the temporary image THUMB
  22:21:25.545 Dec 08: mks | Cannot write the temporary image THUMB
  22:21:30.580 Dec 08: mks | Cannot write the temporary image THUMB
  22:21:35.591 Dec 08: mks | Cannot write the temporary image THUMB
  22:21:40.537 Dec 08: mks | Cannot write the temporary image THUMB
  22:21:45.629 Dec 08: mks | Cannot write the temporary image THUMB
  22:21:50.583 Dec 08: mks | Cannot write the temporary image THUMB
  22:21:55.616 Dec 08: mks | Cannot write the temporary image THUMB
  22:22:00.590 Dec 08: mks | Cannot write the temporary image THUMB
  22:22:05.638 Dec 08: mks | Cannot write the temporary image THUMB
  22:22:10.595 Dec 08: mks | Cannot write the temporary image THUMB
  22:22:15.582 Dec 08: mks | Cannot write the temporary image THUMB
  22:22:20.622 Dec 08: mks | Cannot write the temporary image THUMB
  22:22:25.583 Dec 08: mks | Cannot write the temporary image THUMB
  22:22:30.627 Dec 08: mks | Cannot write the temporary image THUMB
  22:22:35.673 Dec 08: mks | Cannot write the temporary image THUMB
  22:22:40.588 Dec 08: mks | Panic: file lock (was the bug 49968)
  22:22:40.589 Dec 08: mks | Bora/lib/image/imageUtilPng.c:462 unrecoverable memory allocation failure
  22:23:21.438 Dec 08: mks | Backtrace:
  22:23:21.440 Dec 08: mks | Backtrace [0] 0x3ccf63d8 eip 0xa3f88cd
  22:23:21.442 Dec 08: mks | Backtrace [1] 0x3ccf6818 eip 0x9ff705c
  22:23:21.443 Dec 08: mks | Backtrace [2] eip 0xa2803bc 0x3ccf6b88
  22:23:21.443 Dec 08: mks | Backtrace [3] eip 0xa2803f6 0x3ccf6bb8
  22:23:21.444 Dec 08: mks | Backtrace [4] eip 0xa27fcc3 0x3ccf6bd8
  22:23:21.444 Dec 08: mks | Backtrace [5] eip 0xa27fd28 0x3ccf6c28
  22:23:21.445 Dec 08: mks | Backtrace [6] eip 0xa115582 0x3ccf7128
  22:23:21.445 Dec 08: mks | Backtrace [7] eip 0xa115717 0x3ccf7138
  22:23:21.445 Dec 08: mks | Backtrace [8] eip 0xa00d0a9 0x3ccf7168
  22:23:21.446 Dec 08: mks | Backtrace [9] 0x3ccf9278 0xa00dbef eip
  22:23:21.447 Dec 08: mks | Backtrace [10] eip 0x3ccf9298 0xa298217
  22:23:21.447 Dec 08: mks | Backtrace [11] eip 0x3ccf92b8 0xa298255
  22:23:21.448 Dec 08: mks | Backtrace [12] eip 0x3ccf92e8 0xa10bfe9
  22:23:21.448 Dec 08: mks | Backtrace [13] eip 0xa0f2e81 0x3ccf93c8
  22:23:21.504 Dec 08: mks | Backtrace [14] eip 0x160534fb 0x3ccf94b8
  22:23:21.505 Dec 08: mks | Backtrace [15] eip 00000000 0x1613ae3e
  22:23:21.507 Dec 08: mks | SymBacktrace [0] 0x3ccf63d8 eip in function 0xa3f88cd in/usr/lib/vmware/bin/vmware-vmx of the object in the 0x9f98000 (zero)
  22:23:21.508 Dec 08: mks | SymBacktrace [1] 0x3ccf6818 eip 0x9ff705c panic function in/usr/lib/vmware/bin/vmware-vmx of the object loaded on the 0x9f98000
  22:23:21.508 Dec 08: mks | SymBacktrace [2] 0x3ccf6b88 eip in function 0xa2803bc in/usr/lib/vmware/bin/vmware-vmx of the object in the 0x9f98000 (zero)
  22:23:21.511 Dec 08: mks | SymBacktrace [3] 0x3ccf6bb8 eip in function 0xa2803f6 in/usr/lib/vmware/bin/vmware-vmx of the object in the 0x9f98000 (zero)
  22:23:21.511 Dec 08: mks | SymBacktrace [4] 0x3ccf6bd8 eip in function 0xa27fcc3 in/usr/lib/vmware/bin/vmware-vmx of the object in the 0x9f98000 (zero)
  22:23:21.512 Dec 08: mks | SymBacktrace [5] 0x3ccf6c28 eip in function 0xa27fd28 in/usr/lib/vmware/bin/vmware-vmx of the object in the 0x9f98000 (zero)
  22:23:21.513 Dec 08: mks | SymBacktrace [6] 0x3ccf7128 eip in function 0xa115582 in/usr/lib/vmware/bin/vmware-vmx of the object in the 0x9f98000 (zero)
  22:23:21.514 Dec 08: mks | SymBacktrace [7] 0x3ccf7138 eip in function 0xa115717 in/usr/lib/vmware/bin/vmware-vmx of the object in the 0x9f98000 (zero)
  22:23:21.515 Dec 08: mks | SymBacktrace [8] 0x3ccf7168 eip in function 0xa00d0a9 in/usr/lib/vmware/bin/vmware-vmx of the object in the 0x9f98000 (zero)
  22:23:21.515 Dec 08: mks | SymBacktrace [9] 0x3ccf9278 eip in function 0xa00dbef in/usr/lib/vmware/bin/vmware-vmx of the object in the 0x9f98000 (zero)
  22:23:21.516 Dec 08: mks | SymBacktrace [10] 0x3ccf9298 eip in function 0xa298217 in/usr/lib/vmware/bin/vmware-vmx of the object in the 0x9f98000 (zero)
  22:23:21.517 Dec 08: mks | SymBacktrace [11] 0x3ccf92b8 eip in function 0xa298255 in/usr/lib/vmware/bin/vmware-vmx of the object in the 0x9f98000 (zero)
  22:23:21.518 Dec 08: mks | SymBacktrace [12] 0x3ccf92e8 eip in function 0xa10bfe9 in/usr/lib/vmware/bin/vmware-vmx of the object in the 0x9f98000 (zero)
  22:23:21.519 Dec 08: mks | SymBacktrace [13] 0x3ccf93c8 eip in function 0xa0f2e81 in/usr/lib/vmware/bin/vmware-vmx of the object in the 0x9f98000 (zero)
  22:23:21.519 Dec 08: mks | SymBacktrace [14] 0x3ccf94b8 eip 0x160534fb in function (zero) in the object /usr/lib/vmware/lib/libpthread.so.0 to the 0x1604e000
  22:23:21.520 Dec 08: mks | SymBacktrace [15] eip 00000000 0x1613ae3e based on cloning in object /usr/lib/vmware/lib/libc.so.6 loaded in 0 x 16069000
  22:23:21.520 Dec 08: mks | Msg_Post: error
  22:23:21.521 Dec 08: mks | [msg.log.error.unrecoverable] fatal error VMware ESX: (mks)
  22:23:21.521 Dec 08: mks | Bora/lib/image/imageUtilPng.c:462 unrecoverable memory allocation failure
  22:23:21.521 Dec 08: mks | [msg.panic.haveLog] a log file is available in "/ vmfs/volumes/4a4ce277-4a35505c-8828-0024817b058c/labmanager/1922/vmware.log".  [msg.panic.haveCore] a base file is available in "/ vmfs/volumes/4a4ce277-4a35505c-8828-0024817b058c/labmanager/1922/vmware-vmx-zdump.000".  [msg.panic.requestSupport.withLogAndCore] please request support and include the contents of the log file and the base file.  [msg.panic.requestSupport.vmSupport.vmx86]
  22:23:21.523 Dec 08: mks | To collect the data to submit to the VMware support, run 'vm-support.
  22:23:21.524 Dec 08: mks | [msg.panic.response] we will respond on the basis of your entitlement to support.
  22:23:21.525 Dec 08: mks | ----------------------------------------
  22:23:21.739 Dec 08: vmx | Watched VTHREAD thread 1 "mks" is dead
  22:23:22.651 Dec 08: 1 vcpu. Watched VTHREAD thread 0 "vmx" is dead
  22:23:22.740 Dec 08: vcpu-3 | Watched VTHREAD thread 0 "vmx" is dead
  22:23:22.741 Dec 08: vcpu-2 | Watched VTHREAD thread 0 "vmx" is dead
  22:23:22.743 Dec 08: vcpu-0 | Watched VTHREAD thread 0 "vmx" is dead

  I found the suggestion to check the ESX memory for problems.

  I found the information that ESX 3.0 was ramcheck service which could check the memory, but there is no such service in future versions of ESX.

  Could someone help me find how to check the memory without stopping the ESX Server (I could not migrate virtual machines per host)?

  The only way you will get a true test of the memory of the HOST must stop it and run the test directly. Any tool running in the ESX console will only have indirect access RAM. The vmkernel controls access to physical RAM.

• Need to know how to describe something to confirm the physical ESX servers have 2 good trails in the SAN

  Hello

  I wanted to know "how to do something to confirm the physical ESX servers have 2 good trails in the SAN script" via power Cli script.

  Kindly help me for the script

  Thank you

  KR

  Try the following lines

  Get-VMHost | Get-ScsiLun |
      Select @{N="Hostname";E={$_.VMHost.Name}},
      CanonicalName,
      @{N="Active Paths";E={($_ | Get-ScsiLunPath | where {$_.State -ne "dead"}).Count}}
  

  It will show the number of deaths per LUN non-chemins

• Dv6500 Limitation of physical memory to 3 GB

  Hi all

  My DV6500 Entertainment PC supplied with Windows Vista 32 bit pre-installed which limited my use of 4 GB memory to 3 GB. I have recently upgraded to Windows Home Premium 32-bit, which I believe has a limitation of 4 GB physical memory (http://msdn.microsoft.com/en-us/library/windows/desktop/aa366778%28v=vs.85%29.aspx#physical_memory_l... but after inspection always my windows shows 3 GB of memory usable.) Is there something I need to tweek in windows or bios to use fully all the 4 GB as installed on my laptop? Thanks in advance.

  Hello:

  That's what this forum is dedicated... to ask and answer questions.

  So, there is absolutely nothing for you to be sorry for.

  Unfortunately, there is no way you can remap or re - dedicate memory configuration. It is what it is.

  However, the BIOS of your PC may have a more dedicated graphic memory setting to use.

  I was very surprised to see that there is a video memory setting in my BIOS dv6810us. The default value is 64 MB.  However, I could change the setting to 128 MB or 32 MB.

  Then, I changed it to 128 MB.

  Paul

• __ERROR PHYSICAL DUMP MEMORY __STOP 0X0000008E (0XC0000005, 0XBF05D7EE, 0XECE00BC0, 0X00000000)

  WHEN I OPENED MORE THAN 2 TABS WATCHING YOUTUBE OR VIDEO SITES, A SCREEN BLUE WILL SHOW SAYING THAT PHYSICAL MEMORY DUMP... STOP STOP 0X0000008E (0XC0000005, 0XBF05D7EE, 0XECE00BC0, 0X00000000)

  Hi ferds11ab2001,

  Follow the methods below:

  Method 1:

  Disconnect all external devices (printers, scanner, USB (universal serial bus) drives, etc...) Except the keyboard and mouse and then start.

  If this solves the problem, then add back devices at a time until you discover the piece of hardware causing the issue.  Then get any drivers\software update for the device.

  Method 2:

  Follow the steps mentioned in the articles below which deals with a similar question

  1. General troubleshooting for an error message that you receive randomly in Windows XP: "Stop 0x0000008E"http://support.microsoft.com/kb/945658

  2. you receive a random "0x0000008E" error message on a blue screen in Windows XP

  http://support.Microsoft.com/kb/827663

  With regard to:

  Samhrutha G S - Microsoft technical support.

  Visit our Microsoft answers feedback Forum and let us know what you think.

• Installed physical (RAM) memory is not equal to the total amount of physical memory

  Hello world

  I have a Windows 2 K 8 Server with SP2 to run the service of Hyper-V, the machine has 16 GB of memory installed, windows has detected and windows displays its total memory is only 12 GB and causing some of my virtual machine cannot start (due to a lack of memory)

  can - what someone knows how to change that? Thank you very much

  the next section shows my machine Info:

  Name of the Microsoft® Windows Server® 2008 Enterprise operating system
  Version 6.0.6002 Service Pack 2 Build 6002
  Another Description of the OS is not available
  Manufacturer of operating system Microsoft Corporation
  The HP system manufacturer
  ProLiant DL360 G5 model system
  System Type x 64-based PC
  Processor Intel Xeon E5335 CPU @ 2.00 GHz, 2000 Mhz, 4 Lossnay, 4 logical processors
  Processor Intel Xeon E5335 CPU @ 2.00 GHz, 2000 Mhz, 4 Lossnay, 4 logical processors
  BIOS Version/Date HP P58, 24/01/2008
  SMBIOS Version 2.4
  Windows directory C:\Windows
  System directory C:\Windows\system32
  Boot Device \Device\HarddiskVolume1
  The local United States
  Hardware Abstraction Layer Version = "6.0.6002.18005".
  Time zone Pacific Daylight Time
  Physical memory (RAM) installed 16.0 GB
  12.0 GB total physical memory
  1.03 GB available physical memory
  24.2 GB total virtual memory
  12.3 GB available virtual memory
  Page file space 12.3 GB
  Paging file C:\pagefile.sys

  Hello

  Check with the Experts in the Forums Technet Windows 2008 Server.

  TechNet - Windows Server 2008 Forums
  http://social.technet.Microsoft.com/forums/en/category/WindowsServer

  I hope this helps.

  Rob Brown - MS MVP - Windows Desktop Experience: Bike - Mark Twain said it right.

• False alarm on ESX memory

  Hello

  I have recently updated our ESX to vSphere 5.1. After the upgrade, I receive alarm 'Memory of the host State' on some hosts even if there is no virtual machine running on them. Clear the alarm, but he comes back again.

  I checked on the ILO and the OA for all related memory errors or problems, but there is nothing in there. Everything is green.

  No one knows what is the cause.

  Thank you

  Nick

  in any case, this has been fixed after the connection of the host...

• How a VMGuest can see a number of physical ESX host processor

  Hello

  Not sure if this is expected behavior or not, but I have some application that runs from a linux machine to vmguest in my cluster Vsphere 4.0 U1 that is able to see the number of sockets processor busy on the ESX host that it is currently at. I never saw that happen up to now on another system in our environment. On Linux operating plan, when you run the "cpuinfo", the show only reviews the number of virtual processors assigned to it. I don't know how this program is able to see all the way down beyond the virtualization layer to the actual physical hardware layer on the esx host.

  My first thought was that this was triggered after the installation of the VM Tools on the guest operating system, but even after turning off the service tools you can still see the real taken account on the host computer.

  Can someone explain to me how this is possible?

  Thanks for any info you can provide

  Regardless of the tool that allows you to watch the CPU I have a strong suspicion about what is happening here.
  The exact CPU type in/proc/cpuinfo is listed: "AMD Opteron Processor 6164 HE.
  I guess that the tool you are using has some knowledge (using an internal list of program or by retrieving this information somewhere on the internet) that this CPU has really 12 hearts and he only relies on it and reported that the machine has 12 cores, instead of looking at what is really reported by the operating system.
  So, he just does not have the right to work and is not aware of virtualization.
  In any case, it is not really able to look directly into the hypervisor.
  Andreas
  -Visit my Blog experience front of VMware

• Limits of Disco e Memoria vSphere

  OLA.

  MEU ambiente possui as seguintes configuracoes:

  6 clubs 3 TB e 64 GB of memory RAM.

  Na versão 4.1 hypervisor nao estava reconhecendo discos 3TO acima. UM disco em 3 TB, reconheceu 700 GB.

  JA na versão 5.1 mourned memoria RAM 32 GB acima nao na versão gratuita.

  Por case alguem sabe me say is a versão 4.1 Update 3 or a versão 5.1 update 1 where o problema?

  Alguem por case that has um ambiente com discos acima 2 TB com o vSphere Hypervisor (Gratuito) was using 100% back discos?

  Muito Obrigado.

  Oi...

  Voce utlizar acima disco 2 TB so sendo RAW DEVICE.

  VMFS tem has ate 2 TB ( http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003565 ) limitacao

  O Quebec voce pode fazer e through try of da controladora do disco as voce tem no seria criar servidor no discos logicos com size 2 TB get use todo Espaço existente para menor no disco.

• Execute 4vCPUs virtual machines on an 8 core physical ESX host?

  I have to run 4 * 4 vCPUs on my ESX Server. I only ESX Server with 2 processors and each has 4 cores = 8 cores in total.

  Is that enough or what is best practical value if I have to run 4vCPUs?

  If you more search 100% CPU. It's ok if half of your vCPU do no actual work at any given instant, in fact quite common. If they do a real job, you will have a problem of great claim and you will see big time of loan that predict you. There will be no difference in the movement of 2 cpu invited if this is the case, because you always need the number of cores to support threads you have (assuming the same bitrate).

  In case the vCPU is not all busy or they are all busy together then you should be fine but it costs a treatment in order to keep the guest SMP in a valid state of ESX - threads must even if progress, they are not "occupied". If ESX is working hard to achieve this, then you will see CSTP esxtop elevation %. This means basically that ESX is having to stop/reschedule the son in the virtual machine just to keep active when the real work he would do otherwise. So at this point, you can better with smaller virtual machines. Order our planning on the blog document VROOM.

• is daq bit resolution applied to the area defined in the daq assistant or well to the limits of physical blood of the daq hardware.

  Hello, this is my first post here,

  I've been wondering about this:

  When you configure a new daq with the daq Assistant, is the resolution applied to the voltage / number of entries you define, or is it a fixed value per volt by channel.

  For example:

  I have a 6015 usb data acquisition, it has 16 inputs analog, 16-bit resolution 250 kech. / s 09:50 volts.

  so is this as (2 ^ 16) / (16 * (-10-10)) = my resolution through volt?

  or that this has nothing to do with the amount of channels,

  If I want to measure more than 0 to 5 volts, my 16-bit apply from 0 to 5, or even more scale of data acquisition (which is 09:50 volts)

  Thank you

  Marco

  You will get full-resolution 16 bits on each channel regardless of the number of channels is configured.  Renault most are multi-plexed if your specification of sampling RATE in usually a global significance that you can only scan channels with a sampling frequency = MAX RATE / number of CHANNELS.  Also, most NI Renault have a Programmable Gain amplifier on the front-end server, so if you specify a range of voltage smaller in your task configuration the amplifier will automatically increase the gain to use most of the possible BIT ADC.  You see care device and for more details...

• ESX host has a virtual machine that must be behind a physical firewall

  We have several hosts of ESXi.  Some are standard ver3.5, while others are standard ver4.1.  All guests of stand alone.

  A host ESX ver3.5 has 6 virtual computers assigned to the network port of the single on a vSwitch stand-alone virtual computer group.   This switch has 3 uplinks.

  One of the virtual machines must place the physical while the rest remains in front of the firewall as well as the ESX host firewall.   I am told that this can be done by assigning one of of the uplinks to a subnet that is behind the firewall.  And this is the best way to manage it.   My question is: is it possible?   My experience limited with physical firewall and what knowledge I have of VI3, we would need to create a separate vSwitch to do this and assign the VM to these switches... and that's if the uplink can be assigned to a physical switch that connects to another switch behind the firewall (I think).

  Something doesn't seem quite in here... I'm not sure it will work.

  Sounds good to me. If it is a separate physical switch to connect, then you will need an additional vSwitch. If it's just a separate VLAN you could - depending on your current configuration (VST) - just create a new port with the appropriate VLAN ID configured Group.

  André

• 1000008e physical memory error blue screen

  BSOD AT CERTAIN TIMES ON DEPRECIATION OF PHYSICAL MEMORY. ERROR CODE BCCode: 1000008e BCP1: C0000005 BCP2: BD308FDE BCP3: 8D02D8E8 BCP4: 00000000.

  Hi all

  I have a hp dx 7380mt pc, where I work in the xp operating system (OSVer: 5_1_2600 SP: 2_0) since 3 years.all works fine but recent 4/5 months, I am facing this problem of bsod on physical depreciation memory.some time at the start of computer time may not work and display is off, although the glow of electric light and processor fan rotate.i thinks he can occur due to dust store in the location of the ram. so, I clean these slots. but after three four days the period of work, he suddenly takes restarting and bsod came.i do not understand is this related problem of ram or just upgrade mother board related.i my pc with 1.5 GB of ram (512 MB previous) and nvidia gt240 graphics card (agrees with my 300 watt smps) windows far.the on this bsod error message is follow

  BCCode: 1000008e BCP1: C0000005 BCP2: BD308FDE BCP3: 8D02D8E8
  BCP4: 00000000 OSVer: 5_1_2600 SP: 2_0 product: 256_1

  Anyone know exactly what is the cause?

  Hi, PIMS,.

  Thanks for the details of the event log. We recommend that you download the Windows Memory Diagnostic tool and successfully run to see if the stick of memory is causing the problem.

  For more details on this, please visit the following website and follow the instructions carefully:http://oca.microsoft.com/en/windiag.asp

  Visit our Microsoft answers feedback Forum and let us know what you think.

• Physical RAM of vSphere 5.1 Limitation

  Hi guys,.

  I heard that vmware has now removed the limit of VRAM in Vsphere 5.1. but I have no idea with the limitation of physical RAM. I'll buy the standard license. but before that I want to know about it. because I have 2 guests with 2 processors each with 80 GB of ram each. then the total CPU is 4 and RAM is 160 GB. Please advise me.

  Thank you

  You can put up to 2 TB of RAM in a single ESXi host.

  For more information have a look at the maximum rates of configuration: http://www.vmware.com/pdf/vsphere5/r51/vsphere-51-configuration-maximums.pdf

  Kind regards

  Mario