So you currently have three 1GB sticks in there? If yes, adding an identical 1GB stick into slot 4 will work. The only configurations using 4GB sticks are as follows -Slot 1 4GB, Slot 2 4GB = 8GB
Slot 1 4GB, Slot 2 4GB, Slot 3 2GB, Slot 4 2GB = 12GB
Slot 1 4GB, Slot 2 4GB, Slot 3 4GB, Slot 4 4GB = 16GB
(Liaison for Desktops, Alienware, Monitors)Quick link for Manuals and DriversProSupport Plus for PCs and Tablets
So I got this one -- "8GB Kit (4GBx2) DDR3 PC3-10600 • CL=9 • Unbuffered • NON-ECC • DDR3-1333 • 1.5V • 512Meg x 64 Part #: CT1029717" from www.crucial.com/.../mpartspecs.aspx ...
I removed the old three 1 GB RAMs, and then replaced with the two new Crucial RAM. They worked well, but then the last few days I got two random blue screens:
On Fri 6/10/2011 8:18:40 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\061011-21465-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70700)
Bugcheck code: 0x1A (0x5003, 0xFFFFF90000812000, 0x4D7F, 0x81B500009AEE)
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Wed 6/8/2011 7:47:14 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060811-20654-01.dmp
Bugcheck code: 0xDE (0x2, 0xFFFFF8A01935C8F0, 0xFFFFF8A01BC29909, 0x2B2BB8C0)
Bug check description: This indicates that a driver has corrupted pool memory that is used for holding pages destined for disk.
I am going to run Memtest86+ v4.20 over the weekend to see if it is indeed the bad RAM. I noticed the blue screens happen after doing heavy multitasking and then doing light works, and then crash.
Was I supposed to do anything like change CMOS settings after the RAM switch?
FYI from the latest hwinfo32 and CPU-Z tools' results if they give clues:
(will remove/update when needed).