MSI z87-g45 BSOD when trying to install windows

[sniffit]

So I just recently built a new computer and every time I've tried to install windows 7, I get a BSOD around when the Windows logo is starting or finishing animation. I'm getting really frustrated because I've done some research and haven't found a solution.

Parts List:
Case - Corsair Carbide Series 400R Graphite Grey
Processor - Intel i5-4670k Haswell 3.4 ghz quad core LGA 1150
MOBO - MSI z87-g45 LGA 1150
RAM - G.SKILL Ripjaws Series 2x2gbs DDR3 1600 mhz SDRAM
Additional RAM - Exact same as above except 1x4
GPU - Asus Radeon R9 280 3gbz GDDR5 PCI 3.0
PSU - EVGA New Version SuperNOVA 80 PLUS BRONZE CERTIFIED 750W (Haswell Support)
HDD - WD 1 tb 7200 RPM
Cooling - Corsair Hydro Series H60

Things I've Already Attempted:
1) Replaced PSU with a used working 730W (Haswell Support)
2) Uninstalled and reinstalled all parts
3) Swapped to different HDD's
4) Swapped HDD settings from ACHI to IDE and vice versa
5) RMA'ed mobo and reinstalled new mobo
6) Ran Memtest86 for over 11 trials and came up with zero errors
7) Removed GPU in an attempt to narrow problem now
8) Tried different SATA ports
9) Reflashed bios from 1.7 to 1.9 on both MOBO
10) Tried different versions of windows and methods (USB, CD, etc and x64 and x86)

Last thing to test for possibly a defective Processor. Therefore, I might RMA mine soon. If there are any suggestions, I'd love to here from you guys. Thanks!



Edit:
So, I recently just replaced the mobo with an ASRock z97 Fatal1ty Killer and it is also having the exact same issues. Going to buy a different ram that's specifically listed on the compatibility chart and see if that's the issue. Ironically, the 1x4 G.Skill I got with the MSI z87 has a sticker on the front stating that it is compatible with z97.

Edit (9/11/14):
Just received new ram that's listed under z97 Fatal1ty Killer's compatibility chart. Ran the computer with both sticks of 2x4 with both AHCI and IDE settings and got similar results. Swapped to different HDD and attempted both settings and came up with same results. Next step is going to be trying to install with Windows 8.1 legitimate copy I just purchased using student discount. If this doesn't work, I'll RMA my processor. If that fails also, I'll just RMA everything back and change to different parts as I can't seem to figure out what the problem is.

 

[JackNaylorPE]

I was expecting RAM issues....that's a real weak RAM set compared to rest of build. Have ya tried with just the two 2 GB sticks ?

 

[sniffit]

I've tried with 2 and even just 1 to see if that was the issue but it doesn't seem to make a difference. I agree the ram is on the low end but it's just what I had in stock and what I got for free

 

[Shaun o]

Let me guess it blue screens on the windows logo just before it`s about to enter windows.
You obviously have the monitor cable connected to the 280 card.

In the bios disable any on board Igpu support if you can of a Haswell.
Make sure Xmp mode is also enabled in the bios if the memory uses it.
And check that the bios has selected the right voltage for the ram or memory modules.

As a test to see if it`s not a driver related problem, on powering the system on tap the F8 key and load windows in safe mode. If it loads to the desktop it confirms it`s a problem with a driver since safe mode only uses standard MS drivers.

 

[sniffit]

Let me guess it blue screens on the windows logo just before it`s about to enter windows.
You obviously have the monitor cable connected to the 280 card.

In the bios disable any on board Igpu support if you can of a Haswell.
Make sure Xmp mode is also enabled in the bios if the memory uses it.
And check that the bios has selected the right voltage for the ram or memory modules.

As a test to see if it`s not a driver related problem, on powering the system on tap the F8 key and load windows in safe mode. If it loads to the desktop it confirms it`s a problem with a driver since safe mode only uses standard MS drivers.

I have confirmed that multi-moniter is disabled in bios and XMP mode is enabled. Furthermore, I checked the voltage for the ram and it's registering at 1.488 but I think it is set to 1.500. When I first attempted to load in both AHCI and IDE, it failed once again. Not even sure windows will load in safe mode since it's not installed. It's just hanging in 'Please Wait' and nothing is loading any more

 

[johnbl]

what bugcheck code?

 

[sniffit]

what bugcheck code?

It seems to be inconsistent. I haven't really documented the codes themselves but it seems to change from IRQL, to DRIVER, to PAGE FAULT, ATTEMPTED TO WRITE READONLY MEMORY, and even ACPI. I can't really tell which one is the real error since they vary when I was troubleshooting. However, those are the ones I remember from the top of my head.

 

[johnbl]

all of them are real, but most often they will have one root cause. IE one driver overwriting another drivers memory.
if this happens during the install, see if you can find any memory .dmp file that you can post so it can be looked at with the windows debugger.

what bugcheck code?

It seems to be inconsistent. I haven't really documented the codes themselves but it seems to change from IRQL, to DRIVER, to PAGE FAULT, ATTEMPTED TO WRITE READONLY MEMORY, and even ACPI. I can't really tell which one is the real error since they vary when I was troubleshooting. However, those are the ones I remember from the top of my head.

 

[sniffit]

all of them are real, but most often they will have one root cause. IE one driver overwriting another drivers memory.
if this happens during the install, see if you can find any memory .dmp file that you can post so it can be looked at with the windows debugger.

what bugcheck code?

It seems to be inconsistent. I haven't really documented the codes themselves but it seems to change from IRQL, to DRIVER, to PAGE FAULT, ATTEMPTED TO WRITE READONLY MEMORY, and even ACPI. I can't really tell which one is the real error since they vary when I was troubleshooting. However, those are the ones I remember from the top of my head.

I believe it's a setting that I am overlooking, however, I'm not sure how I go about grabbing a .dmp file when I can only access the bios (since I'm trying to install windows but it's BSOD). If you know how I do this, please let me know. Thanks!

 

[sniffit]

I was expecting RAM issues....that's a real weak RAM set compared to rest of build. Have ya tried with just the two 2 GB sticks ?

To rule out your suggestion, I purchased 1866 mhz G.Skill Snipers 2x4 and had no results. I appreciate your response.

 

[pudnocker]

For what it is worth, I am having the exact same issue. I have the same MB, and Windows boots all the way to the point of saying starting Windows on the initial install. It then gets a 7B stop error. Have not been able to find a solution yet. I have a single 8 GB DIM. I thought that it was a driver issue that it did not have the intel raid adapter, but I see that loading at install. Also, this is an upgrade for me. I am able to boot into the previous Windows 7 (32 bit) instance. I just cannot install from a (64 bit) load.

 

[beats_86]

I have a very similar problem. I recently switched out my old i7 920 and alienware aurora mobo to an MSI z97 mobo and i7 4970k. Immediately upon booting into windows at the loading screen and then I get a BSOD with 7B stop code. When I try to boot into safe mode or boot into windows repair I get an error saying the source is unreachable. I've tried all the other aforementioned steps in previous posts but to no avail.

I was unable to use the windows repair cd I made prior to the install to repair my windows installation but could access the command prompt. I used that to install the drivers for my mobo but this still didn't let me boot to windows or conduct a new repair with the disc. However I've downloaded a ISO for win 7 64bit (on another computer) and can use that to re-image my boot drive from the system image saved on my external HDD prior to the switch. I still get the error post that process though.

Next I'll try to re-install windows completely using that CD rather than repair/re-image but I'm not confident this will work.