Windows 7: Blue Screen Crash. New install on new system

I recently built a computer, Everything went fine and seems to check out I installed windows 7 and it will crash with the ever so popular Blue Screen of Death 1033 3D.




Now one very very important thing to state here is that I can run windows 7 (with the disk still in the drive) Perfectly fine. I have played games on steam and I have been using my computer just fine for about 2 weeks now. But as soon as you take the disk out it will crash into the blue screen. Any suggestions and help is greatly appreciated.

Hi Slayner117 welcome to SF

""(with the disk still in the drive) ""

Which disk exactly? The windows dvd or the game dvd?

Oh Sorry for the delayed reply. The Windows 7 disk.

So if i understand well the pc works just fine when the windows dvd is IN the dvd drive?

But if you remove the windows dvd from the dvd drive the system crash?

Can you boot your PC without anything in the DVD drive? If you do that, what happens?

Corazon OP already posted this.

Now one very very important thing to state here is that I can run windows 7 (with the disk still in the drive) Perfectly fine. I have played games on steam and I have been using my computer just fine for about 2 weeks now. But as soon as you take the disk out it will crash into the blue screen. Any suggestions and help is greatly appreciated.

That's exactly correct.

If I try booting without the Windows 7 disk in the Drive. It will load briefly until it crashes to the BSOD almost immediately

Follow these simple steps.
http://www.sevenforums.com/crashes-d...tructions.html

We see cases irregularly where the DVD or Repair CD needs to be in the drive for the PC to boot. It appears the PC is booting off the disk since it cannot boot without it. The fix so far has been to confirm the System Reserved partition (preferred) or Windows 7 partition is marked Active then run Startup Repair up to 3 separate times with reboots to correctly write the System boot files to it.
Partition - Mark as Active
Startup Repair - Run 3 Separate Times

Likely the System boot files were either not written or corrupted, perhaps because installer failed to mark it Active or it's Active flag slipped. As SIW2 would often remind us early on, the target partition MUST be marked Active for System Boot files to be written to it.

This is the first time I've seen a BSOD associated with this, so perhaps minidump analysis should come first.

If the analysis or the known fix for disk-only booting doesn't help, then I'd wipe the HD to clean reinstall following these steps to get a perfect baseline install then see if problems recur which would point to hardware issues: Perfect Reinstall