obsidian1200

I'd go with the xeon in this case.

I've only done it for new OSes or if an OS is being very buggy and I'm unable to fix it/tired of dealing with it.

Sounds like it could be a bad GPU, I'm assuming the system booted just fine prior to installing the nvidia drivers which means it was working alright with the Microsoft Basic Display Adapter driver. I'd suggest trying the safemode route comic sans mentioned to try different drivers, as well as the alternate OS route Ryan_Vickers mentioned, but just be sure you also install the drivers for it in that OS for accurate testing. I'll also suggest, if possible, trying the GPU in a different system and seeing if that system also starts to BSOD after installing the card. If it does, I'd say that's strong evidence of a bad GPU.

You're welcome, have fun with the new drive!

If you're 100% sure disk 0 is the one you need to format/erase, you can use diskpart in an elevated command prompt to do that. Simply open a command prompt as an admin and type in "diskpart" to launch the command line utility. Diskpart is a utility included with Windows. Next, type "list disk" to produce a list of disks. In this case, you seem sure disk 0 is your target disk, but it never hurts to double check before a format. Type "select disk 0" and hit enter to select the disk. Then type "clean", which will clear the current partition table on disk 0. After the cleaning completes, assuming it does, type "Create partition primary" to create a new partition. Then, type "format quick fs=[insert filesystem fat32, ntfs, or exfat here] label=[name of drive]" and hit enter. After that, type "assign letter=[drive letter]" and ht enter. The drive should now show up in explorer with the label and letter you assigned.

I found the same to be true, I just did a test with this pack in a VM. After installing the prerequisite update and this new pack, I manually upgraded IE via the Microsoft site. Then I let the Windows update agent do its thing, and through a few reboots, Windows Update showed zero remaining updates after installing ~70 updates. On a similar note, Microsoft added this page to their support site, https://support.microsoft.com/en-us/kb/3125574 which lists various things not included as well as some known issues with the rollup and how to fix them. Edit: Well the VM just chimed for additional updates, with plenty "security" updates from 2014 and 2015 popping in. I'll update with a final tally after they've all finished. Edit 2: Looks like it finished after doing another round of updates. I'd say about 10, so let's say there's a total of 80 updates after this pack. Still, better than what the total was before this rollup, but not as amazing as I had hoped.

I never said Vista only took hours to upgrade nor did I say Vista ever ran better, re-read the post. I only said 7 takes a few hours for updates, and it wasn't a complaint. I only said Vista takes a long time to update from a fresh SP2 installation. Again, there's a reason I want a 3rd service pack for vista. It's currently a pain to update.

Still waiting on an SP3 for Vista, personally. At least with 7 it only takes a few hours to update (depending on network speed), but Vista takes so long from a fresh SP2 install, even with a fully updated Windows Update Agent. I guess this is still nice for those who don't know how to speed up Windows 7 updates, though. It'll make things a tad bit easier for those who need to reinstall Windows 7, occasionally or frequently.

Next step after an SFC scan imho is running dism. In an elevated command prompt, try dism /online /cleanup-image /restorehealth If there's a particular update that's looping, providing the KB number would probably help. It might be a case where you'll need to clear the Windows update cache.

I don't have recommendations for where to get updated ISOs, but I'd ere on the side of caution. With a modified ISO that doesn't match a checksum of the stock ISO, you really don't know for certain what else could be embedded in that ISO. I'd say this is a great opportunity for you to learn how to make one yourself. It's not that difficult and you'll know it's a safe ISO.

That's a rare case (I've only seen it a small handful of times in my work experience), but a good point. Given OP's current dilemma with windows BSODing due to an inaccessible boot device (which was occuring prior to unplugging the secondary drive), I'd say that's more reason to redo the windows install from scratch without additional drives plugged in so the BCD and bootmgr files will all be loaded into their proper place on the SSD. Then, once that's done, removing any unneeded boot files from the secondary drive can be done within Windows.

That's interesting, the "no bootable device" message should only appear if you don't have a bootable drive installed, which shouldn't be the case assuming that the SSD is still plugged in and detected in the UEFI/BIOS. Disconnecting a secondary drive should have no bearing on the bootable state of the system to a different drive.

Disconnecting the secondary HDD won't cause that message unless windows is on it, that may indicate a problem with the remaining storage devices. Are you trying to reinstall Windows via the recovery partition or a USB stick/DVD?

For the small amount extra, I'd rather go with the Dell P2415Q. Way better stand and IPS panel.

It shouldn't, but why risk it? I'd disconnect the 2nd drive from the system prior to doing the restore just to be safe.