Bluescreen after memory change

[Latheras]

Hi!

After I changed to a new set of RAM, I've had a bunch of errors on my computer, and it won't boot past BIOS without crashing or going on forever. Neither I or my friends have been able to fix it, so now you guys are my last hope.

Set-up:
MSI Z87-GD65 Gaming
Intel Core i7-477K
Old RAM: Corsair Vengeance Pro DDR3 1600MHz 8GB (2x4GB CL9 XMP 1,5V)
New RAM: Corsair Vengeance Pro DDR3 2400MHz 16GB (2x8GB CL11 XMP 1,65V)

• 
  * I replaced the new RAM with the old, and put them in the same slots the old ones were in. (I wore static protection.)
  * PC booted up without any problem.
  * Used Intel XTU to test the RAM.
  * Before completion it crashed and rebooted. After logging on, it worked as normal again.
  * Crashed again after trying to run a game. Now it won't boot to desktop.

Now it either tries to

• 
  * Scan and repair the D: drive, and get stuck at 100%
  * Automatic repair, and crash with error: POOL_CORRUPTION_IN_FILE_AREA
  * Get stuck at forever diagnosing the computer
  * Get stuck showing the Windows-logo, and the never ending loading-"dot-circle"

Solutions tried:

• 
  * Checking RAM-slots for damage
  * Checking if RAM is inserted correctly.
  * Using only either one of the sticks, and in the different slots.
  * Using RAM in another computer (The computer worked)
  * Using another RAM in my computer (Kingston 1333MHz 2x8GB 1.5V) (It did not work... Same issue.)

Due to that, it seems the problem isn't the RAM, which is strange. The computer worked perfectly before the RAM-change. Perhaps you can see something here that I can't?

In either way, it won't boot to desktop. Some other blue screen errors are:

• 
  ATTEMPTED_WRITE_TO_READONLY_MEMORY
  KERNEL_SECURITY_CHECK_FAILURE
  BAD_POOL_HEADER
  MEMORY_MANAGEMENT
  PAGE_FAULT_IN_NONEPAGED_AREA
  SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
  KMODE_EXCEPTION_NOT_HANDLED

Is this all a driver issue?


Hope that wasn't too much of a read. I'll be sitting here trying to find a solution while waiting for possible answers. All help is appreciated!

 

[Mac070]

AT THIS POINT STOP OVERCLOCKING , IF YOU DONT KNOW IF YOU ARE THEN YOU PROBABLY ARENT.
Yes my advice would be to try updating and making sure your bios is up to date. Also as Intel is stating that that i7 processor doesn't support that higher frequency ram. Only 1333 and 1600 at 1.5 volts. Your new ram runs at 1.65 ?

 

[Latheras]

AT THIS POINT STOP OVERCLOCKING , IF YOU DONT KNOW IF YOU ARE THEN YOU PROBABLY ARENT.
Yes my advice would be to try updating and making sure your bios is up to date. Also as Intel is stating that that i7 processor doesn't support that higher frequency ram. Only 1333 and 1600 at 1.5 volts. Your new ram runs at 1.65 ?

I'm not overclocking at the moment. I was finally able to get into repair options, by the way. Booting now causes the 0xc000021a error.

I didn't know i7 didn't support higher than 1600MHz. The old one was that, and yes, ran at 1.5V. So this means the new ram won't work on the computer?

That doesn't solve the problem though, as even the Kingston RAM mentioned won't work.

EDIT: I checked into what you said, here: http://www.tomshardware.co.uk/answers/id-1698560/65v-ram-haswell.html

• 
  Intel's approved i7 Compatibilty List for the 4770k (May 2013) includes:
  
  12 1.65 volt modules
  02 1.60 volt modules
  09 1.50 volt modules

Which means 1.65V should be supported.

 

[Tradesman1]

You will probably need a slight CPU OC to run at 2400 (say 4-4.2 GHz, then simply enable XMP and select profile 1

 

[Latheras]

You will probably need a slight CPU OC to run at 2400 (say 4-4.2 GHz, then simply enable XMP and select profile 1

I might try that when I'm able to boot to desktop. As of now, even lower voltage RAM won't work anymore.

 

[Tradesman1]

Try clearing CMOS (with no DRAM installed) then install the 2 2400 sticks

 

[Latheras]

Try clearing CMOS (with no DRAM installed) then install the 2 2400 sticks

Tried this now. Got the POOL_CORRUPTION_IN_FILE_AREA error.

 

[Tradesman1]

Could be a few thing

This,

Causes of POOL_CORRUPTION_IN_FILE_AREA Blue Screen Errors

Incorrectly configured, old, or corrupted device drivers. (very common)
Corruption in Windows registry from a recent software change (install or uninstall).
Virus or malware infection that has corrupted Windows system files or Windows Operating System-related program files.
Driver conflict after installing new hardware.
Damaged or removed system files after you’ve installed software or drivers related to Windows Operating System.
Error 0xDE blue screen caused by a damaged hard disk.
POOL_CORRUPTION_IN_FILE_AREA STOP error due to memory (RAM) corruption.

POOL_CORRUPTION_IN_FILE_AREA blue screen errors can be caused by a variety of hardware, firmware, driver, or software issues.

from

http://www.solvusoft.com/en/errors/blue-screen-errors/microsoft-corporation/windows-operating-system/bug-check-0xde-pool-corruption-in-file-area/

 

[Latheras]

Incorrectly configured, old, or corrupted device drivers.
Driver conflict after installing new hardware.
Error 0xDE blue screen caused by a damaged hard disk.
POOL_CORRUPTION_IN_FILE_AREA STOP error due to memory (RAM) corruption.

POOL_CORRUPTION_IN_FILE_AREA blue screen errors can be caused by a variety of hardware, firmware, driver, or software issues.

My guess is on driver issue. The HDD and my previous RAM worked before the installation of new RAM. Doesn't explain why it won't run on my friend's older RAM, but I'll run this through tech-support in the morning, and see what they say. If they give me any solutions, I'll let you know.

Thanks for the help, so far!

 

[Tradesman1]

Will look for you tomorrow 😉

 

[Latheras]

Will look for you tomorrow 😉

G'day!
Customer service didn't seem to know much, or ask much about the errors, but told me to send the motherboard, processor and RAM to them, so they could check. (Although without the HDD they won't be able to fix driver issues...)

Do you have any ideas of how I could give it a last shot before sending it in? How can I solve the driver issues without booting to desktop? (Restoring to a previous update didn't work)

Might this all be a conflict between the RAM and the motherboard?

 

[Tradesman1]

Have you tried running SFC /SCANNOW from the command prompt? It's the system file checker (and may want to try running from SAFE MODE