I had the same problem with my GA-7VRXP when I bought it over 2 years ago.

I had started off with1 module of 512MB generic PC2700. A few months later
I decided to add another 512MB PC2700 module, also generic but different
manufacturer. I began having the same problems that you are currently
having. Each module would work fine by itself, but as soon as the second
module was added, even using the most conservative BIOS memory settings, the
problems started.

Running memtest86 with each module by itself confirmed that there were no
problems with either of the individual modules. After adding the second
module and rerunning memtest86 confirmed that there were memory errors when
both modules are used together.

The solution was to bring both modules back to my vendor and exchange them,
at no extra cost to me, for a pair of modules from the same manufacturer and
same production lot. With the 2 new 512MB PC2700 modules together, running
memtest86 for several cycles confirms that there are no more errors.

This motherboard seems to be very sensitive to any mismatches in memory
modules.

"Simon Elliott" wrote in message
. ..

I'm having problems adding an extra 512MB of memory to my 256MB
GA-7VRXP W2K/W95 dual boot system and would appreciate some advice.

I've tried three different types of memory, two lots of PC2700 and now a
strip of PC2100 (Kingston branded). In each case the symptoms are the
same; The BIOS recognises the memory and POSTs, Windows starts loading,
crashes partway through the process and the machine restarts. This boot
loop would apparently continue forever if I don't interrupt it.

At first I suspected a HAL issue but W95 (which doesn't have one)
experiences the same symptoms. I've tried using the BIOS 'Failsafe
defaults'; I've tried using different slots - with and without the
original memory and I've tried upgrading the BIOS (F12 - very
unreliable, lots of blue screens, so backed out). In every case the
symptoms are pretty much the same. Either the CHKDSK crashes while
still counting down (always in the same place, 10, 9, 8, 7, 6, bang!) or
occasionally, a BSOD ("PFN_list_corrupt",
"Driver_IRQL_not_less_or_equal", "KMODE_exception_not_handled" amongst a
selection) depending on the BIOS I'm using at the time.

On a couple of occasions I got the blue desktop background of a Windows
system starting up, but nothing happened (no "Loading Network Settings"
or "Security Settings" messages, keyboard and mouse apparently not
recognised) and I had to reboot.

I'm currently looking for a copy of the same brand as the original
memory (VData - found some on eBay); in the meantime, can anyone suggest
what might be going wrong? I'm puzzled because the board has been
thoroughly reliable since I originally built it.

--

Simon Elliott