BSOD when installing new ram

[superking]

[FONT=&quot]I spent yesterday trying to get my new ram to work, but to no avail. It is 4 2gb sticks of Kingston KVR16N11S6/2. They meet the requirements according to the motherboard manual.
I am running 64 bit windows 7. I initially installed all 4 sticks at once; windows said 1gb available 7gb hardware reserved, and runs super slow. BIOS only registered 1024mb. I reset BIOS and CMOS with no difference. When I installed them one at a time in DIMM slot 1 BIOS registered the 2gb but windows would blue screen crash after verifying DMI pool at start up on all 4 sticks. I tried booting with a 1gb stick of my old ram and it boots just fine.
I ran Memtest86+ on each stick twice and they are all error free. I updated my BIOS, made sure Maximum Memory is unchecked in MSCONFIG.
According to WinDbgx64 "Probably caused by : ntoskrnl.exe ( nt+748c0 )". Did some searching on google and the only thing I can find is that it could be defective ram, but mine passed Memtest86+.

Windows 7 Home Premium 64-bit
Motherboard: Gigabyte X48T-DQ6
CPU: Intel Core2 Quad Q9300 @ 2.5ghz
Ram: [/FONT][FONT=&quot]Kingston KVR16N11S6/2
Video Card: EVGA GT 740

Thanks for helping!

[/FONT]

 

[Boozad]

A couple of questions. How long did you run MemTest86+ for? It needs to run for at least 8 passes to be anywhere near conclusive. Have you edited your registry at all? All three of your dumps indicate the following.

BAD_SYSTEM_CONFIG_INFO (74)
Can indicate that the SYSTEM hive loaded by the osloader/NTLDR
was corrupt.  This is unlikely, since the osloader will check
a hive to make sure it isn't corrupt after loading it.
It can also indicate that some critical registry keys and values
are not present.  (i.e. somebody used regedt32 to delete something
that they shouldn't have)  Booting from LastKnownGood may fix
the problem, but if someone is persistent enough in mucking with
the registry they will need to reinstall or use the Emergency
Repair Disk.
Arguments:
Arg1: 0000000000000002, (reserved)
Arg2: fffff88006685b20, (reserved)
Arg3: 0000000000000002, (reserved)
Arg4: ffffffffc000009a, usually the NT status code. [COLOR=Red]---> STATUS_INSUFFICIENT_RESOURCES[/COLOR]

Two steps to follow, maybe more depending on the answers to the previous questions.

1: Uninstall DAEMONTools, a proven cause of BSODs.

1. Uninstall DAEMONTools via Add/Remove Programs.
2. Download the SPTD standalone installer and perform the following steps.
3. Double click the executable to open it.
4. Click the button shown below.

   Information

If the button it is grayed out as shown in the image, there is no more SPTD installation on your system and you can just close the window.

2: Open an elevated command prompt and type in or copy and paste sfc /scannow and hit enter.

 

[superking]

I have not done any modifications to the Registry. While trouble shooting a suggestion was to use MSCONFIG and check number of processors to 4 and Maximum Memory to 8gb. I did that, but it did nothing so I unchecked them both and set Start up selection back to Normal Start Up.
I uninstalled Daemon Tools.
Downloaded the Standalone installer, it did not ask me to uninstall, so I closed it.
Ran Command Prompt as Admin and ran the scan.
"Windows Resource Protection found corrupt files but was unable to fix some of them"
I have attached the CBS.log file.

 

[Boozad]

I've requested someone take a look at your CBS files, once that's done we'll continue.

 

[NoelDP]

The erros found are from the KB3022345 update...

MS have updated their advice on the SFC issue.
It seems that this is an error in the 'logic' rather than an actual problem.
There is no point in attempting to correct the apparent errors, since they will reappear as soon as another diagnostic is run (possibly without user intervention!).

Therefore, as far as these errors are concerned the current options are

• ignore the errors, and wait for MS to release the promised update to correct the SFC detections

• uninstall KB3022345 and hide the offered update until its either updated or replaced.

Take your pick!

There are no other errors in the SFC scan that need attention.

 

[GokAy]

For the sake of diagnosing, would you:
- downclock the RAMs (reduce multiplier)
- loosen the timings of RAMs
- apply some voltage to RAMs
- try ganged/unganged modes if applicable

Screenshot from spd tab of CPU-z?

https://support.microsoft.com/en-us/kb/978610

Can be incompatible RAMs, faulty motherboard

 

[superking]

Uninstalled KB3022345

I will now install the 1 stick of ram and use BIOS to make adjustments to the ram. My BIOS does not offer ganged/unganged mode.

View attachment 360552

 

[Boozad]

You never answered this question:

How long did you run MemTest86+ for?

If you're going to start messing with RAM settings before we've ascertained whether your RAM is actually good or not I'll bow out and leave you to GokAy.

 

[superking]

I ran MemTest86+ on each stick twice. It took approximately 10 minutes for each stick. They passed the test each time. It took about 40 minutes to test all 4 sticks. Should I test them longer or all 4 sticks at once?
It does not make sense, if I put in all 4 sticks Windows boots just fine, but one stick crashes.

I just finished trying different settings on 1 stick of ram:
First I changed DDR3 Overvoltage control +0.05 - Still BSOD at start up
Then I changed that back and changed CAS Latency time from 10 to 9, DRAM RAS# to CAS# Delay from 11 to 9, DRAM RAS# Precharge from 11 to 9, Precharge Delay (tRAS) was left at 28 - Still BSOD at start up
Then I changed it to 11, 11, 11, 35 - Still BSOD at start up
Then I kept those settings and changed DDR3 Overvoltage control +0.05 and then +0.1 - Still BSOD at start up

[EDIT]

Forgot to upload screen cap of CPUZ with the 4 sticks of troublesome RAM
View attachment 360560

 

[Boozad]

I ran MemTest86+ on each stick twice. It took approximately 10 minutes for each stick. They passed the test each time. It took about 40 minutes to test all 4 sticks. Should I test them longer or all 4 sticks at once?
It does not make sense, if I put in all 4 sticks Windows boots just fine, but one stick crashes.

That's nowhere near long enough. MemTest86+ needs to run for at least 8 full passes to be considered anywhere near conclusive, you wouldn't have even completed a quarter of a pass on either stick. When using MemTest86+ you're testing the RAM slots as well as the sticks of RAM. Before you go messing about with timings and voltages I'd suggest running MemTest86+ properly.

Download and run MemTest86+ to test your RAM. http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

   Note

Run MemTest86+ for at least 8 passes. Ideally set it off before you go to bed and leave it overnight, we're looking for zero errors here. A single error will show something's going bad with your RAM.

 

[superking]

Should I run Memtest86+ with all 4 sticks installed? If that is the case, I will do it tonight and let it run overnight.

 

[Boozad]

I would, if there are any failures you'll then need to start pinpointing which stick/slot is at fault.

 

[superking]

I will do that, thank you for your advice and help.

 

[Boozad]

No problem, keep us posted.

 

[GokAy]

Good catch Boozad, I had assumed a proper memtest was performed.

By the way, changing timings from 10 to, say, 9 is not loosening them You are actually overclocking the RAMs that way (called tightening), increasing the likelihood of problems.

Just made a suggestion there, I would need help myself if I ever had a BSOD!

 

[Layback Bear]

Just to be certain please have the settings like this and reboot and check again to make sure the setting stay set.

View attachment 360581

 

[superking]

Almost 9 hours of Memtest86+ and no errors.
What is next?

View attachment 360768

 

[Boozad]

Install one stick of RAM in each of these slots then test please.

View attachment 360770​

 

[superking]

Over night again?

 

[Boozad]

No, don't run MemTest just use your system as normal.