New build blue screen when starting windows

Mathil8 · Apr 25, 2017

Just finished my build yesterday and kept getting blue screened when windows began starting up. I have two drives, one a new NVMe drive and the other my old HDD with Windows already installed. When booting up either drive it blue screens at the exact same point. Any idea what the issue could be?

Build:

CPU - i5-6600k
Cooler - Cryorig H7
MoBo - Asus Z170-a
Ram - Corsair Vengeance LPX 2x8GB DDR4-3200
GPU - EVGA GTX 1060 SC 6GB
PSU - EVGA SuperNOVA G2 650W

https://ca.pcpartpicker.com/list/CY2T9W

Thanks!

BadAsAl · Apr 25, 2017

Did you install Windows from scratch on the new drive?
Try using only 1 stick of RAM and also different RAM slots.

Mathil8 · Apr 25, 2017

BadAsAl :

Going to do a fresh install of Windows on the new NVMe drive tonight. Already tried playing with the ram slots to no avail.

Thanks for the suggestions!

Mathil8 · Apr 26, 2017

BadAsAl :

Installing Windows on new drive worked fine, but I'm still having issues getting my old drive up and running; it still blue screens when starting windows. Old drive is running Windows 7. Must be a compatibility issue I guess? I've tried changing some boot settings in BIOS to no avail. Any ideas?

Thanks!

adiec · Apr 26, 2017

Mathil8 :

if you're trying to use an old o/s which was installed using a different motherboard cpu etc then you're going to run into these problems. you're getting device driver conflicts when trying to boot because the hardware isn't the same as it is expecting .

Mathil8 · Apr 26, 2017

adiec :

Mathil8 :

if you're trying to use an old o/s which was installed using a different motherboard cpu etc then you're going to run into these problems. you're getting device driver conflicts when trying to boot because the hardware isn't the same as it is expecting .

Figured as much, I'm pretty much resigned to doing a fresh install on that drive as well I guess. I know there's work arounds, in which I'd run into many other issues, but would be nice to try to get it working.

igtaba · Apr 26, 2017

Boot with the new drive, then use WesterDigital diagnostic tool or another storage diagnostics and see if the old drive past the test (at least the smarts). Maybe the old HDD is damaged and the OS is corrupted every time you try to boot up from it.

(PS: sorry for my bad english, it is not my mother tongue)

Mathil8 · Apr 26, 2017

igtaba :

Definitely possible, I'll try that later tonight. Thanks for the suggestion!

adiec · Apr 26, 2017

Mathil8 :

if you have things on there that you wish to keep you should still be able to access the drive using the new install you did on the new drive . i think if it was a windows 8 or 10 installation on the old drive it has far less of these conflicts .

just to be clear : new o/s boots with old hdd being used as storage/ old hdd doesn't boot when being used as primary boot device

Mathil8 · Apr 26, 2017

adiec :

Mathil8 :

if you have things on there that you wish to keep you should still be able to access the drive using the new install you did on the new drive . i think if it was a windows 8 or 10 installation on the old drive it has far less of these conflicts .

just to be clear : new o/s boots with old hdd being used as storage/ old hdd doesn't boot when being used as primary boot device

Correct. Although I'm having administrator issues trying to access the old hdd as storage. That should be an easy fix though.

adiec · Apr 26, 2017

what kind of admin issues ?

Mathil8 · Apr 26, 2017

adiec :

Just permissions, think I know how to fix it, going to play with it later tonight.

adiec · Apr 26, 2017

Mathil8 :

ok let us know if you have any problems

igtaba · Apr 26, 2017

If you cant open it coz admin issues try to boot ubuntu live (without intalling it) from a USB and that would do

Mathil8 · Apr 26, 2017

Will do, thanks!

Mathil8 · Apr 28, 2017

I've resigned myself to the fact that I'll have to do a fresh install on the old drive. I've been able to fix the permissions issue and have gained access to the old drive from new drive OS.

Thanks for the responses everyone!

igtaba · Apr 28, 2017

Mathil8 :

So, let's be clear?
- If you boot with only the new drive connected, ths system works fine?
- The blue screens that you have are only with the old disk now that you've done the fresh install in the new?
- If the old disk had windows install for a diferent build (other parts) you are probably gonna need a reinstall, but it should post Ok, and load up basically anyway.
-Have you read wahts code gives you the blue screen? is always on the same point?

Mathil8 · Apr 28, 2017

igtaba :

Mathil8 :

So, let's be clear?
- If you boot with only the new drive connected, ths system works fine?
Yes, only the new drive with fresh install boots, old drive does not boot.
- The blue screens that you have are only with the old disk now that you've done the fresh install in the new?
Correct.
- If the old disk had windows install for a diferent build (other parts) you are probably gonna need a reinstall, but it should post Ok, and load up basically anyway.
Old disk had windows install from a different build. Posted fine, but froze when starting windows.
-Have you read wahts code gives you the blue screen? is always on the same point?
Haven't been able to read the code as the blue screen just flashes for a split second. It blue screens at the exact same point every time when loading windows after post.

See bold.

igtaba · Apr 28, 2017

Mathil8 :

igtaba :

See bold.

Try with a new install of windows in the old drive. also use Wester Digital Diagnostics (you can run booting with the new disk and then analize the old drive.To see if the disk is corrupted or not, but I will suspect that a windows reintall will do (I don't know why you want to have windows in the both disk and not use one as storage only)

adiec · Apr 28, 2017

some people get lucky when using an old HDD with windows already installed from a different pc and some don't . what we are talking about here is a complete move away from the old build. new mobo, ram , cpu etc. if for instance you had already owned a 6th gen cpu, mobo and ddr4 ram then you might have gotten away with almost no problems .

if you're insistent upon wanting to install windows on this second HDD then i suggest you either :-

reinstall windows using the option to keep your documents etc.

transfer any files you wish to keep to the new drive and then do a clean install of windows on the old hdd. when asked where you would like to install windows , first delete the partition of your old hdd , create a new partition, format the drive and then select the newly created partition as the place to install windows. (please note this will remove everything from your old hdd and it will be a completely empty drive)

Mathil8 · Apr 28, 2017

Yeah, the harddrive is from a ~8 year old system. Not surprising it's not compatible.

Initially I wanted to use the old harddrive as a secondary boot, but I'll just use it as internal storage now.

adiec · Apr 28, 2017

Mathil8 :

storage is the way i would go too i'm sorry i couldn't fix all your issues but i am quite sure we have done all we can between us both .

Mathil8 · Apr 28, 2017

adiec :

Yup, dont think anything could be done. Even if I got it to boot I'd run into numerous other issues I'm sure. This just forces me to be quick about doing a fresh install

. A blessing in disguise. Thanks for your help.

New build blue screen when starting windows

Prominent

Distinguished

Prominent

Prominent

Honorable

Prominent

Reputable

Prominent

Honorable

Prominent

Honorable

Prominent

Honorable

Reputable

Prominent

Prominent

Reputable

Prominent

Reputable

Honorable

Prominent

Honorable

Prominent

Share this page