[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 306
  • Last Modified:

Servers won't boot with 4GB memory with Server 2003

I have a client that has 3 DL140 2x3.2GHz none of them will boot with 4 GB of memory.  They all boot with 3 and he has tested the difference slots.  When he boots 4 GB windows will not load.  Does anyone have any idea's.

Thanks
0
Nancy Villa
Asked:
Nancy Villa
  • 5
  • 2
  • 2
  • +6
2 Solutions
 
MSE-dwellsCommented:
Please provide more information regarding the error.
0
 
KCTSCommented:
just to clarify is the problem that even with 4Gb it only shows 3Gb? If so this is normal for a 32bit OS as it can't utilize all of the memory.
0
 
Bradley HaynesCommented:
Check the Boot.ini file.

This article describes Physical Address Extension (PAE) and Address Windowing Extensions (AWE) and explains how they work together. This article also discusses the limitations of using memory beyond the 4-gigabyte (GB) range that is inherent to 32-bit operating systems.

http://support.microsoft.com/kb/283037
0
[Webinar] Improve your customer journey

A positive customer journey is important in attracting and retaining business. To improve this experience, you can use Google Maps APIs to increase checkout conversions, boost user engagement, and optimize order fulfillment. Learn how in this webinar presented by Dito.

 
Nancy VillaDirector of ITAuthor Commented:
It won't even boot with 4 GB it hangs on the Windows screen and never comes up.  I don't get any errors, but all 4 GBs are showing in the bios.
0
 
oBdACommented:
Check the boot.ini and make sure the /pae switch is NOT included in the line for the regular W2k3 start.
I've seen systems not boot because of it (while still recognizing most of the 4GB).
0
 
ocon827679Commented:
Check to see that you have the latest BIOS for the server.
0
 
Nancy VillaDirector of ITAuthor Commented:
We do have the latest bios, but we also have the /pae switch.  I am going to have it removed and see if that solves the problem.
0
 
Nancy VillaDirector of ITAuthor Commented:
I took the /pae switch off and the same thing is happening.
Windows trys to boot and shuts down then triggers a fredl light ault on the server

0
 
StuFox100Commented:
Hi

1. Are there any errors in the event log?
2. Can you boot in to safe mode?
3. Check your pagefile allocation - do you have enough disk to support the dynamic pagefile?

Cheers
Stu
0
 
ChiefITCommented:
I think I have seen this issue before. Let me see if I can dig it up.

Yes, here it is> The 3Gb barrier.

http://www.dansdata.com/askdan00015.htm

I hope this helps.
0
 
Nancy VillaDirector of ITAuthor Commented:
We do not get any errors in the event log, because windows does not get that far when booting with the 4 GB.  Again 3 GB is comes right up.
0
 
ocon827679Commented:
Have you called the vendor about this yet?  This just sounds like a BIOS issue.
0
 
StuFox100Commented:
There is a BIOS fix.

The latest is
Systems ROMPaq Firmware Upgrade for HP ProLiant DL140 G3 Servers
version 1.14 (2007.08.13) A   (17 Aug 07)

But the previous one mentions something about a max mem issue:
Systems ROMPaq Firmware Upgrade for HP ProLiant DL140 G3 Servers
version 1.13 (2007.05.18) A   (23 May 07)

Try installing the latest and see how it goes.
Cheers
Stu
0
 
Nancy VillaDirector of ITAuthor Commented:
We ended up never getting this fixed.  I think it has to do the Bios so I will award Stu the points
0
 
Dudester68Commented:
I have the same problem.  I upgraded my RAM from 2GB to 4GB but the machine just hanged  (it got me to the screen for logging in, but when i press Ctrl+Alt+Delete, nothing happens):

I have 32-bit  Windows 2003 Enterprise Server installed with Gigabyte P965-DQ6 motherboard.  This is the original boot.ini configuration:

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003, Enterprise" /PAE /2GB /fastdetect /NoExecute=OptOut

After reading from another thread on this website, I updated the boot.ini to the following, but the computer still hanged:

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003, Enterprise" /fastdetect /NoExecute=OptOut /PAE

From this thread, I updated the boot.ini again (removed the /PAE switch) but still the problem remains.

When I reduce to 3GB RAM only the machine runs without any problems.  What could be the problem here?

Thanks so much.







0

Featured Post

Receive 1:1 tech help

Solve your biggest tech problems alongside global tech experts with 1:1 help.

  • 5
  • 2
  • 2
  • +6
Tackle projects and never again get stuck behind a technical roadblock.
Join Now