Fresh Build - Constant BSOD - Multiple Codes - 3b, 50, a

LP81 · 10 May 2012

Up to 5 successful passes on Memtest86+

here's a small snippet from the Motherboards manual: Gigabyte GA-Z68AP-D3 | Manual - Page 37

Extreme Memory Profile (X.M.P.), System Memory Multiplier (SPD), Memory Frequency(Mhz)
The settings under the three items above are synchronous to those under the same items on the Advanced Frequency Settings menu.

Performance Enhance
Allows the system to operate at three different performance levels.
Standard -- Lets the system operate at its basic performance level.
Turbo -- Lets the system operate at its good performance level. (Default)
Extreme -- Lets the system operate at its best performance level.

DRAM Timing Selectable (SPD)
Quick and Expert allows the Channel Interleaving, Rank Interleaving, Channel A Timing Settings, and Channel B Timing Settings items to be configurable. Options are: Auto (default), Quick, Expert.

Profile DDR Voltage
When using a non-XMP memory module or Extreme Memory Profile (X.M.P.) is set to Disabled, this item will display as 1.5V. When Extreme Memory Profile (X.M.P.) is set to Profle1 or Profle2, this item will display the value based on the SPD data on the XMP memory.

So it sounds like the XMP is on by default but I will verify setting after the 7th RAM testing pass

LP81 · 10 May 2012

7 Passes, no errors

Went into the BIOS and checked out the Memory Frequency Tab:
X.M.P. is currently disabled - screenshot below

Also I downloaded and ran CPUz. Grabbed multiple screenshots. Computer BSODed in the middle of me saving them, this time was a d1 Error

Tab1:

Tab4:

Tab5: (all 4 sticks in the sub menu had the same info)

James7679 · 10 May 2012

Try enabling XMP. Also, are you able to run Prime95 without crashing? Or Intel Burn Test?

Lastly, don't suppose you have any other hardware laying around that you can use for testing? Another 1155, or MoBo, or PSU?

LP81 · 10 May 2012

Downloaded Prime95, ran the Small FFTs test and I got a BSOD after about 20 min - 3b error

PSU I know isn't the cause. I originally had a OCZ ZS Series 550W 80PLUS Bronze High Performance Power Supply on it with the same BSOD issues.

I am not 100% what caused my previous Rig to die so trying to swap in its old guts might now be advisable
Mobo - EVGA 122-CK-NF67-T1 LGA 775 NVIDIA nForce 680i
CPU - Intel Core 2 Quad Q6600 Kentsfield 2.4GHz

I will try enabling the XMP as a next step and see what happens

LP81 · 10 May 2012

Turned on XMP in BIOS, it defaulted to "Turbo"
Save & Exit
The computer shut itself down, rebooted and said "The system has experienced boot failures because of overclocking or changes of voltages. Last settings will be used"

Went back in, turned XMP on again but changed it to "standard"
Save & Exit
Windows started to boot, then reset itself, and ended up on a Windows Error Recovery screen
Chose "Launch Startup Repair" and got a BSOD 7E error

Disabled XMP in the BIOS and after a lot of hullabaloo, finally got windows to start up again.

I think the problem with this step is I sent the shutdown signal, and it started to do updates then died in the middle of them causing the previous error.

I will try to re-enable XMP in "Standard" mode again and see what happens.

LP81 · 10 May 2012

So with XMP turned on, and set as "standard", I can't even get to the Win7 login screen before a BSOD. This time it's a 1000007e ndis.sys BSOD dump.

I'm about to run the jcgriff again so you can get an updated list of the 14 dumps on file.

Attachment to follow

James7679 · 11 May 2012

All of these codes you are getting, when placed together definitely indicate that you have voltage issues. Now, since the memory controller is no longer on the north bridge, and you are having cpu errors, as Vir Gnarus kindly pointed out, my best guess is that you have a bad processor. This is not common, but I have seen it a few times lately. It could be your MoBo, and less likely, your memory.

There is one more thing you can try. Looking at your CPUz, your idle voltage looks pretty low, this can cause instability. It's possible that you could bump your VCore offset up and it might stabilize. Try bumping the offset by .020(can't remember if that is the differential on the offset menu), or whatever the next bump up is. Reboot, and if it seems a little better, but still crashes, bump it up a little more. Oh, and leave XMP enabled when doing so. Your settings should look like this;

Note that the Performance enhance shows "Turbo" and the XMP profile should be marked "Profile 1".

Post back results.

LP81 · 11 May 2012

I can edit the VCore frequency in increments of 0.005 on this mobo.

The BIOS originally read 1.240 at the time so I upped it to 1.260 as well as changed the XMP back on to Turbo

Save and Exit - Immediate dump while loading Windows (too fast to see actual dump info)

Back into BIOS, now the CPU Vcore says 1.320V as the "Normal" so I tried 1.340V

Save and Exit - Immediate dump while loading Windows (too fast to see actual dump info)

Tried going back to "Standard" on XMP with 1.64 - same thing - quick dump

On a side note, looking at the "Advanced Memory Settings" I do see that is says the System Memory Multiplier says 1333Mhz, however the RAM i have is Corsair PC3-12800 1600MHz 240-pin DDR3 Timing: 9-9-9-24 1.65v

Could that be the issue at all? (just throwing out Ideas)

James7679 · 11 May 2012

No, that's fine.

Well, I will see if anyone else has further suggestions, but my best guess is to second the opinion of Vir Gnarus and advise an RMA of your CPU.

Dwarf · 11 May 2012

We've ascertained by what you have posted that there is nothing wrong with your hardware as far as a 32-bit OS is concerned (XP running without problems). We also know that you are having problems with w7 64-bit, but can you try the 32-bit version instead? W7 contains far more drivers and is compatible straight out of the box than earlier OSes (including XP), so I don't think that it is a driver issue.

If a clean install of 32-bit works without problems, but the 64-bit version causes random BSODs, then the cause of the problem must be something to do with the architecture. We can rule out most of the hardware here, as it functions identically under both bit versions. The only component that can have a bearing on this is the CPU. It is perfectly feasible to have a CPU that functions OK with 32-bit but has problems when trying to use 64-bit.

Note that when carrying out testing such as this, you should set your BIOS to its defaults, and should stop over/under clocking. You should also ensure that you deselect the option to automatically activate when online.