BSOD 6x4GB 1333 DIMM's @1.5v occasionally x58 Sabertooth i7-970

Memory test seems to work fine. I have 6 DIMMS of GSKILL ripjaw F3-10666CL9D-8GBRL RAM set at 1.5v. The system seemed stable with only 3 DIMM's in (no BSOD's the entire day). Last night when I had 6 DIMM's in it BSOD'd often and this evening I put the other 3 DIMM's back in and the BSOD's resumed. memtest86+ seems to run fine but I'm going to leave it over night to be sure.

Is there a good method to diagnose the problem?

I've upped my voltages too to try and see if that would help:
uncore - 1.25v
ICH - 1.2v
DRAM BUS - 1.5v
CPU - 1.25

Factory clock settings etc. This happened a long while back but resolved itself. The problem started again recently so I went back and clean installed windows thinking it was a driver. All drivers are up to date and the BSOD seems to be in random executables (thus I'm thinking memory issues).
2 answers Last reply
More about bsod 6x4gb 1333 dimm occasionally sabertooth
  1. You don't need to raise the other voltages, if anything you should raise the DRAM Bus Voltage to 1.550V or 1.60V.

    I am assuming you have a triple channel motherboard?

    You may need to exchange for a hex channel memory kit, which is 6 modules, tested, and guaranteed to work together in the same system.

    For memtest86+, you need to test one module at a time. Errors can be hidden if you have multiples installed.

    Keep us posted on the result.

    Thank you
  2. I have the DRAM bus voltage raised to 1.550v. Yes, I have triple channel and this system was table for several years, only recently has it become unstable.

    I will attempt to test modules one at a time.

    New BSOD today:
    crash dump file: C:\Windows\Minidump\081412-17534-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
    Bugcheck code: 0xA (0xD1, 0x2, 0x0, 0xFFFFF80002CB5B44)
    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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
Ask a new question

Read More

G.SKILL Blue Screen DIMM Memory