Dual Channel causing BSOD

Associate
Joined
3 Jun 2009
Posts
52
Hi guys. Recently bought a new computer and the past couple of days I've been getting BSODs as soon as Windows started to load. I tried everything I could think of (format drives, re-install Windows etc) and nothing worked until I took out one of the RAM sticks. Now it starts perfectly every time and it seems to be ok. I've swapped the sticks around to see if one of them was faulty but they both work fine (independently).

As soon as I put both sticks back in though the BSOD reappears so I'm certain it's an issue with dual channel.

Specs are:

i5 2500k
ASRock Z68 Extreme4
8GB Corsair XMS3 (2x4gb)
GTX 570
Windows 7 64-bit Home Premium

Nothing is overclocked, everything is at stock. Is there a setting in the BIOS I need to change? I poked around but to be honest I didn't have a clue what I was supposed to be looking for.

Thanks for the help.
 
What voltage and frequency are you running these at? i.e. have you the XMP enabled? My guess is that if you've not changed these then you'll be running at the JDEC 1333MHz at 1.5v. Try increasing the voltage to 1.55v or even 1.6v, see what happens.

Run CPU-Z and post up the memory screen shots.
 
XMP is set to 'auto'. There are a bunch of other options but I really don't know what's what.

Anyway here's the CPU-Z result:

qsl2bn.jpg




According to the ASRock extreme tuning utility the DRAM voltage is 1.650v.

52nrcz.png
 
Last edited:
Further testing shows that it's not just Dual Channel that causes the problem. Simply having another stick installed in a seperate channel causes a BSOD as well. For some reason I am limited to one stick or it just doesn't work.

The BSOD code is PAGE_FAULT_IN_NONPAGED_AREA and it only appears as soon as the black Windows loading screen appears.
 
Last edited:
As my mate Huddy correctly predicted your memory isn't running at the correct speed/frequency.

And although your timings are correct the Command rate is set at 1T, rather than 2T, which 'may' be causing a problem.

You need to enter the BIOS and set the frequency, timings, voltage and the command rate manually.

Enter these values:

  • 1600Mhz (your frequency at present is reading as 1330MHz i.e. 2 x 665)
  • CL - 9
  • tRCD - 9
  • tRP -9
  • tRAS -24
  • Command Rate -2T (this is reading as 1T in your image)
  • 1.65V (max voltage - this can be lowered once you're stable)

Hopefully, this may resolve your issues - but if it doesn't try resetting the CMOS and then loading optimised defaults (or similar) save and exit.

Then re-enter the BIOS and input the above values again - save and exit and test again.
 
Last edited:
Try running the PLL at a full 1.9v but no more.

I'm also concerned about the VTT and wondering if this is a bit low.. The VTT is linked directly with the Memory Controller i believe, which for 2500K is on chip, hence a separate discreet voltage setting. It may be worth trying small increments to help it's stability.. Try 1.1, 1.15, 1.2 but don't go beyond that..

Plec or someone else may confirm this.

However, changing to XMP may set these up for you...
 
Changed the command rate to 2T, upped the PLL to 1.9v and the VTT to 1.1v and it works! I won't get too carried away right now because I want to give it a few days to make sure it's all stable and such but thank you both.

Edit: Lasted for about half an hour before the BSODs started again. I'm beginning to think there's something corrupted in the Windows installation somewhere.

Edit 2: New Windows installation, still BSOD. I give up.
 
Last edited:
I suggest you memtest on each stick from a bootable iso - link.

EDIT: have you tried running one stick in different memory slots?

If you've tried the above run memtest on the two slots, separately, with a single stick - as it may be a DIMM/MB/CPU issue.
 
Last edited:
Yes completely eliminate the actual Memory modules..

If that isn't the cause then it's looking more like a IMC problem which is of course is located on the CPU itself.

You couldn't have had the CPU long. Have you spoken to the vendors? It might be worth mentioning this to them and ask them to test the CPU/Mobo combo.. If it fails with them, then it'll be a straight forward RMA. If it doesn't then there may be a small testing charge but at least you'll know for sure.
 
How did you go with this? I'm actually getting the same issue, and currently eliminating memory modules. However, one pair is stating v2.12 and another v5.11, but the latter seems to be running better. Do you want to check your memory modules?

I'm using an i7 2600k CPU. But I get bouts of where the entire PC doesn't even post, fans come on and that's it. After countless reboots, it then boots up but then BSOD's, all I caught at the bottom of the message was a memory dump before rebooting
 
Back
Top Bottom