Hello everyone, first post on this forum.
My problem is this:
I recently bought (2x) 2GB [4GB] Kingston HyperX DDR2 PC5300 667MHz Performance Modules for my notebook computer, I have EVERYTHING updated (I am a "update" freak). I took out the preinstalled Hyundai (2x) 512MB [1GB] modules and pop in both Kingston modules without a problem, I turn on my computer and the main BIOS boot doesn't show...I restart it the 2nd time, and everything boots up normally until I get to the "Aurora" boot screen (I have the standard "Microsoft Corporation" boot disabled). I notice that the bottem-half of the screen becomes pixalated with weird colors and "scroll" down to bottem. It then proceeds to boot into the log-on screen without further problems until I sit to wait for something else weird to happen...which indeed does happen, a section of a square hovering over the blue "arrow" button becomes pixalated with weird colors and "scroll" down like on the boot screen. I sign in and then for probably about 15 seconds the screen becomes "50-50" pixalated with weird colors and the normal Vista desktop with no fugginess. I then get the BSOD shortly after that which never gives me a chance to read it since it quickly reboots.
Here are the things I have tried already:
1) Insert 2GB stick in and go to MSCONFIG Boot options and set Maximum Memory to 2048 and restart the computer then shut down again and insert the 2nd 2GB stick and boot up. I then get bunch of weird mixed results in both Safe Mode and Normal Mode as if I can barely get into "Normal Mode" without the "Glowing Orb" freezing or signing in and then quickly getting BSOD. I get into Safe Mode and then get the "50-50" deal on me but can see through half the "good side" of Vista and manage to get into MSCONFIG to set Maximum Memory to 3072MB and then restart the computer, but when its "Shutting Down" the orb stops and it just hangs. (I have the quickly go through all that before the computer freezes but never enough time to make "Shutting Down" 100% complete)
2) I have 2GB stick in and I download this program called Vista Boot Pro 3.3, I go to Advanced settings and set the Physical Memory level 3900MB [I have read people having success with this on the Microsoft TechNet Forums] and then shut computer off and insert 2nd 2GB stick, I manage to boot up perfectly fine, but then realize Vista is detecting all 4GB RAM in both System Properties and System Information but only using 1GB (895 Used/211MB Free). I restart the computer and then Vista stops booting in all the way. I am forced to reinstall Vista with 2GB installed.
3) I have read that if you reinstall KB929777, it'll fix the 4GB issue. But seeing as I am using Vista x64 with SP1 x64 slipstreamed, SP1 already has the fix integrated so there is NO WAY to "reinstall" the fix. I have thought about using my standard Vista x64 RTM DVD and reinstall but I can NEVER get SP1 to download completely or install, both Windows Update and Standalone Installer. Both 32 and 64 bits. I have NO clue why. I always get errors.
My notebook specifications are as followed:
2008 HP Compaq Presario C762NR
Microsoft Windows Vista Home Premium x64
Intel Mobile Pentium Dual-Core T2370 (1.73GHz/533MHz/x64 EM64T Processor)
Intel GMA X3100 (128MB-512MB- RAM/256MB-1GB RAM/384MB-2GB+ RAM)
Intel Mobile GM965 Express Chipset
HP InsydeH20 BIOS F.34 (September 2008)
Hitachi 5400RPM 160GB HD
Atheros AR5007B/G WiFi
Kingston HyperX DDR2 PC5300 2GB 667MHz (4GB Dual-Channel Kit)
YES YES I know! Hewlett-Packard says that my model "only" supports 2GB RAM...WRONG! it supports MORE! People have been getting 2.5GB and 3GB RAM working on here, but HP released BIOS F.31 which claims to have fixed the 3GB/4GB issue for both 32 and 64-bit Vistas respectively.
My BIOS detects both 2GB sticks in with 4096MB and my VRAM increases from 256MB to 384MB at same time.
If I'm able to boot this far into Vista with 4GB in certain scenarios then there MUST be a way to fix this problem as I am running Vista x64.
[Edit]: I do NOT have any options in my BIOS to adjust RAM stuff. BOTH modules work when inserted by themselves in BOTH RAM slots, so my RAM is not faulty.