/3GB SP2 BSOD!

I recently upgraded to 2.5GB of RAM and tried the " /3GB switch", but I keep
getting BSOD's stating "BAD_SYSTEM_CONFIG_INFO"
BEFORE the black Windows logo screen even loads.
It will not load into safe mode either.

Here is my boot.ini file:

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOW S
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Micro soft Windows XP
Professional" /fastdetect
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Micro soft Windows XP
Professional" /3GB /fastdetect

I am running XP Pro SP2 with all the latest updates.
I have run every memory test known to man, they all come up fine.
I have tested all of the 5 RAM modules I own and they are all good.
I have tried booting with each RAM module individually with the same results.
I have re-installed the KB826939 rollup.
I have tried the /USERVA command with various following numbers without
success.
I have tried it with only one boot line (which forced me to boot from the
windows cd and rebuild my boot file).
I have tried putting the /3GB after /fastdetect and taking out /fastdetect
alltogether, as I've seen recommended.
Nothing seems to work, something's holding me back.
I have only one PCI card (an an RME 9636 sound card), and an ATI Radeon 7000
64MB AGP (Not a FireGL) card in this machine.
Any ideas? Noone has been able to answer this for me.
Thanks in advance for even thinking about helping!
_________________
jeswa
schematic.net
j(r e m o v e t h i
_________________
AMD Athlon 64 3400+ . Asus KV8 Deluxe . 2.5gb Mushkin DDR LII V2

jeswa,
for a start, if you didn't know, /3gb parameter only works on 32-bit version
of WinNT family OSes. On 64-bit, this parameter is ignored as far as I know.
/3gb deals with virtual memory, it affects the way how virtual memory is
split between kernel and user mode and has no effect on physical memory
installed (RAM).
only processes that have LARGEADDRESSAWARE bit can benefit from /3gb

KB826939 rollup should not be installed over SP2

that said, the error message you receive usually comes from:
bad RAM (you indicated that you did testing)
wrong permissions on registry hive(s) or corrupt registry

I don't know if /3gb parameter can cause the error message you are getting
(my guess is no)

a question: does your computer boot if you remove /3gb from boot.ini?

"jeswa" wrote in message
...
I recently upgraded to 2.5GB of RAM and tried the " /3GB switch", but I
keep
getting BSOD's stating "BAD_SYSTEM_CONFIG_INFO"
BEFORE the black Windows logo screen even loads.
It will not load into safe mode either.

Here is my boot.ini file:

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOW S
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Micro soft Windows XP
Professional" /fastdetect
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Micro soft Windows XP
Professional" /3GB /fastdetect

I am running XP Pro SP2 with all the latest updates.
I have run every memory test known to man, they all come up fine.
I have tested all of the 5 RAM modules I own and they are all good.
I have tried booting with each RAM module individually with the same
results.
I have re-installed the KB826939 rollup.
I have tried the /USERVA command with various following numbers without
success.
I have tried it with only one boot line (which forced me to boot from the
windows cd and rebuild my boot file).
I have tried putting the /3GB after /fastdetect and taking out /fastdetect
alltogether, as I've seen recommended.
Nothing seems to work, something's holding me back.
I have only one PCI card (an an RME 9636 sound card), and an ATI Radeon
7000
64MB AGP (Not a FireGL) card in this machine.
Any ideas? Noone has been able to answer this for me.
Thanks in advance for even thinking about helping!
_________________
jeswa
schematic.net
j(r e m o v e t h i
_________________
AMD Athlon 64 3400+ . Asus KV8 Deluxe . 2.5gb Mushkin DDR LII V2

I am still facing the same problem, how i can rid on this problem

In August 2006, Microsoft released updated installation media for Windows XP SP2 and Windows Server 2003 SP1 to contain a patch that requires ActiveX controls to require manual activation in accordance with a patent held by Eolas. Since then, the technology was licensed by Microsoft, and Service Pack 3 and later versions do not include this update.