BSOD on new build

Stingerbar

Previously I had Windows 7 installed on a normal samsung f1 harddrive, subsequently I bought an SSD and installed windows 7 on that and had both in my old pc

It would give me two options for Windows 7 on boot up, I'd always choose the top one as it was the SSD

I just built a new PC

hooked up the SSD (crucial M4) to the Sata3 connection
and the mechanical harddrive to the sata2

I have booted from both alternatively, and they both bluescreen very shortly after the Windows logo comes up

Gonna reinstall Windows 7 onto the SSD, any other suggestions?

I read somewhere it might be an ACPI configuration setting or something, I have lots of options in the ASrock UEFI

game4it70

ACPI should be set before you install again.I think its in advanced or boot section.

It would be best to unplug the mec drive too while you install 7.

BloodBath

Of course it bluescreens. All the drivers are set up for your old hardware.

You need to do a fresh install of windows with new hardware.

You could try booting in safe mode and uninstalling all of your drivers with driver sweeper but I don't know how effective that is.

raymix

ACPI is a power feature, in your case it sounds like an AHCI problem, which is a driver. You can do a registry fix to allow AHCI mode without reinstalling OS, however reinstalling would be highly recommended to keep it clean.

raymix

raymix wrote: »

ACPI is a power feature, in your case it sounds like an AHCI problem, which is a driver. You can do a registry fix to allow AHCI mode without reinstalling OS, however reinstalling would be highly recommended to keep it clean.

Exactly. You can transfer a Windows install to different hardware but it doesn't always work nicely. Also, if the install is an OEM copy then it's not allowed.

uncle_sam_ie

Karsini wrote: »

Also, if the install is an OEM copy then it's not allowed.

It's fine to replace hard drives with OEM copies of Windows. It's MB's where that's not allowed. Although, it can still be done.

uncle_sam_ie

uncle_sam_ie wrote: »

It's fine to replace hard drives with OEM copies of Windows. It's MB's where that's not allowed. Although, it can still be done.

That's correct, but the OP said they built a new PC, which wouldn't be allowed. "Not allowed" doesn't mean "can't be done" as you say, it's a licensing thing.

Stingerbar

thanks lads, I've managed to change hardware before and start up with old drives, thought i could do it this time. I unplugged the mechanical harddrive and booted from usb to install win7 on the ssd. After all that i replugged in the mechanical harddrive so now it boots from ssd everytime without wanting to give an option to boot from both or bluescreening

I went from amd x4 955 with gtx 660 --> i5 3470 with gtx 660

for a laugh i ran the old 3dmark06 on my 955 and I got 18488
just ran it now on the new processor and got 25844

I know 3dmark06 is ancient, but nice to see it register 30% increase

raymix

Do you guys think that in this case BSOD could also be caused by CPU change from AMD to Intel? I am not 100% on this. Personally I would never bother trying to get old installation to work after swapping CPU like that.
Just curious, that's all.

raymix

raymix wrote: »

Do you guys think that in this case BSOD could also be caused by CPU change from AMD to Intel? I am not 100% on this. Personally I would never bother trying to get old installation to work after swapping CPU like that.
Just curious, that's all.

It could be. I remember that XP SP3 brought to the forefront a problem where OEMs made an image on an Intel machine and deployed it to an AMD, so the Intel CPU power management driver intelppm.sys was still running on the AMD system. It was causing these systems to crash after SP3 was installed.