Memory module size


  1. Posts : 22
    Windows 7
       #1

    Memory module size


    I have read some data that says that Windows Seven has problems with mixed sizes of memory modules. In my system I have three 2 Gig modules and one 1 Gig module. Can this cause any problems. The memory came preinstalled in my system so I assume it is of same type and manufacturer. Still trying to chase a problem with desktop heap allocation failure at boot up.
      My Computer


  2. Posts : 28,845
    Win 8 Release candidate 8400
       #2

    arliedog said:
    I have read some data that says that Windows Seven has problems with mixed sizes of memory modules. In my system I have three 2 Gig modules and one 1 Gig module. Can this cause any problems. The memory came preinstalled in my system so I assume it is of same type and manufacturer. Still trying to chase a problem with desktop heap allocation failure at boot up.
    The size of the module shouldn't matter as long as they are exactly the same specs. If you think the heap problem is caused by memory download and run memtestx86 for several hours at least.

    You can also check in event viewer (type event vwr in search) for log entries. Go to windows logs>application tab (and system)and look for errors (red in the left hand colum) relating to the problem. When found note the event ID and source codes and relay them to us

    Let us know if you need help

    Ken J+
      My Computer


  3. Posts : 5,705
    Win7 x64 + x86
       #3

    What points to "desktop heap allocation failure" during the boot? Where does this error come from?
      My Computer


  4. Posts : 22
    Windows 7
    Thread Starter
       #4

    Event id 243 desktop heap allocation failure


    This
    zigzag3143 said:
    arliedog said:
    I have read some data that says that Windows Seven has problems with mixed sizes of memory modules. In my system I have three 2 Gig modules and one 1 Gig module. Can this cause any problems. The memory came preinstalled in my system so I assume it is of same typeThis and manufacturer. Still trying to chase a problem with desktop heap allocation failure at boot up.
    The size of the module shouldn't matter as long as they are exactly the same specs. If you think the heap problem is caused by memory download and run memtestx86 for several hours at least.

    You can also check in event viewer (type event vwr in search) for log entries. Go to windows logs>application tab (and system)and look for errors (red in the left hand colum) relating to the problem. When found note the event ID and source codes and relay them to us

    Let us know if you need help

    Ken J+
    Here is the event log data for the desktop heap failure. This happens when there are no windows open other than the desktop which consists of 14 shortcut icons and nothing open on the task bar.
    Here is the data:
    Log Name: System
    Source: Win32k
    Date: 11/23/2009 9:03:32 PM
    Event ID: 243
    Task Category: None
    Level: Warning
    Keywords: Classic
    User: N/A
    Computer: dlhert-PC
    Description:
    A desktop heap allocation failed.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
    <Provider Name="Win32k" />
    <EventID Qualifiers="32768">243</EventID>
    <Level>3</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2009-11-24T03:03:32.528200000Z" />
    <EventRecordID>8427</EventRecordID>
    <Channel>System</Channel>
    <Computer>dlhert-PC</Computer>
    <Security />
    </System>
    <EventData>
    <Data>
    </Data>
    <Binary>000000000100000000000000F3000080000000000000000000000000000000000000000000000000</Binary>
    </EventData>
    </Event>
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 07:02.
Find Us