Solved System service exception BSOD playing Starcraft 2

[Boozad]

This is the last thing I can think of. Give this a read through and a try and if it doesn't work I'll help you with the reinstall. http://www.sevenforums.com/tutorials/20864-mbr-restore-windows-7-master-boot-record.html

 

[JTMoney66]

Ok - I'll try this in the morning and let you know the results. I'll have my new HD and stuff ready by tomorrow night (before your morning time on Wednesday). The time difference of 8 hours is pretty difficult.

 

[Boozad]

We have a tutorial for a clean install of 7, I'll link it when needed. Follow that to the letter and you won't go wrong. The cleaning up of your other drives after the install should be pretty straight forward too.

 

[JTMoney66]

Ok, I tried restoring the MBR and I got the same BSOD.

 

[Boozad]

I'm at a complete loss here I must admit. Give me one last shot, I'll ask some other BSOD bods to drop by and take a look to see if they can see anything I'm missing.

 

[essenbe]

Hi, I have just scanned real quick, so please excuse me if I ask something you have already tried. Use this tutorial on partition wizard and see if you can get a screenshot of your disks. http://www.sevenforums.com/tutorials/93322-partition-wizard-use-bootable-cd.html

Also, can you boot from the installation Disk. When you get to the first screen, do not select your language. Hold down the shift Key and press F10, you will get a command prompt. Type diskpart and press enter. It will take it a few seconds but it will reply diskpart, type list disk and press enter. it will show a list of all hard drives in your machine, each one is assigned a number on the left. Find the number for the hard drive windows is installed on and, for example if it was listed as hard drive #1, type select disk 1 and press enter. It will respond that disk #1 is the selected disk. Type list partition and it should show all partitions on the disk. Type detail disk and press enter. Please take a picture of the screen if at all possible. A cell phone picture is fine as long as we can read it. maybe that will show what is wrong. If it will make it easier on you, disconnect 1 wire from every hard drive except the one Windows is installed on. Then it will be select disk 0 instead of 1. To get out of the command prompt, type exit and press enter, you will then still be in the command prompt but at X sources, type exit and press enter again and you will be back at the select your language. Just cancel out if you want.

 

[Boozad]

Thanks Steve mate.

 

[JTMoney66]

Hi, I will send the screenshot when I can. But I do remember typing list partitions on all my disks in diskpart. They all only have 1 partition called "Primary".

 

[essenbe]

Unless you made it happen, your Windows disk should have 2 partitions. A 100MB system Reserved and a C partition. The 100 MB system reserved should be named the System partition and be marked active. That should be the only partition marked active unless you have another OS installed.

I recall reading you ran startup repair. Did you try with all other disks removed and inly the Windows disk installed? Run it 3 times and try to restart the computer between each time. It sometimes takes 3 tries for it to write/repair the boot files. It would be helpful to know, if you have a 100 MB system Reserved and is it on the Windows Drive and is it marked active. Hopefully the diskpart and the Partition Wizard screenshot will tell us that.

 

[JTMoney66]

I am not at home right now but I will take the screenshots of diskpart and post them later.

It could have been my own doing, I'm not sure. When I installed my current Windows 7, it was on a new HD and I did not manually create any partitions on the disk. I have never changed the partitions on any of my drives. I have 3 internal hard drives (you'll see later in the screenshot), 2 of which are ssd.

One thing I always noticed that I didn't think about much until now is that, whenever I emptied the recycle bin, there was a short delay and some clicking noise (sounding like a normal HDD), BUT my Windows is installed on a SSD, so I couldn't explain the noise. So perhaps, my old disk drive has some involvement in the system that they should not have?

If my Windows drive is not partitioned, or is not marked as active, maybe that would be preventing me from loading Windows?

 

[JTMoney66]

Here I have attached a photo of the detail disk results. This is for sure the only disk with a Windows 7 installation.

I have not tried startup repair with all other disks removed. I had 3 or so other external drives that I removed at the beginning of this. I could try that if needed. Hopefully the picture will provide some clues.

Please let me know your suggestions. Thank you.

 

[Arc]

Hi JTMoney66.

I am sorry that I am asking, probably you have provided the info earlier but I am missing it, but are you getting stop 0x6B during windows installation?

And, hopefully you are attempting to install windows on the 120 GB Corsair Force GT, as it was?

If the aboves are right, then ......

1. Boot into the BIOS. Check it thoroughly ... wherever it is UEFI, set it to Legacy in the BIOS. Then attempt another clean reinstall. Does it still fail?

2. Open the computer. Check the cablings. If possible, apply new SATA cables. Then attempt the installation again.

3. If it still fails, attempt to install windows on any other HDD or SSD.

Let us know at this point.

 

[JTMoney66]

Hi JTMoney66.

I am sorry that I am asking, probably you have provided the info earlier but I am missing it, but are you getting stop 0x6B during windows installation?

No problem, I already have Windows installed, but I am getting the stop error when trying to load into Windows (right after the Windows starting screen and before the login screen)

And, hopefully you are attempting to install windows on the 120 GB Corsair Force GT, as it was?

Correct it should be installed on that drive. However, I have a new drive that I would like to reinstall Windows on, so that I don't have to lose all my files from the 120GB drive.

If the aboves are right, then ......

1. Boot into the BIOS. Check it thoroughly ... wherever it is UEFI, set it to Legacy in the BIOS. Then attempt another clean reinstall. Does it still fail?

I did not see anything anywhere labeled UEFI or Legacy except on my bootable USB drive but I am not booting it as UEFI, I select the basic option. I checked the whole BIOS. It is version 1604 for the Sabertooth 990FX MB.

2. Open the computer. Check the cablings. If possible, apply new SATA cables. Then attempt the installation again.

I just received new SATA cables (with my new drive) and I'll be replacing all of them.

3. If it still fails, attempt to install windows on any other HDD or SSD.

Let us know at this point.

I think I will just install Windows on my new SSD (it is 250GB) if the new cables don't fix the problem right away.

 

[JTMoney66]

Ok, I replaced the SATA cables, installed the 250GB drive and temporarily disconnected the 90GB drive. I restarted and tried to boot from the 120GB drive and now it says BOOTMGR is missing, press Ctrl-Alt-Del to restart.

 

[essenbe]

Go into bios and make sure the 1st boot device is your 120Gb drive.

 

[JTMoney66]

The 120GB drive is set as first in the boot order in the BIOS. I also tried pressing F8 at startup and selecting it from the boot menu there. I checked and all the new SATA cables are secure and the power cable is secure. According to the motherboard, they are connected to the correct SATA3 ports.

I checked diskpart and it showed my 120GB drive and my oldest drive (a HDD) in the system both have 0 bytes of free space which should not be true. However, it showed the new 250GB drive as having 232GB of free space. Those are the 3 drives currently connected since my 90GB drive is disconnected.

A quick background of the timeline of my Windows installations is as follows:

originally had Windows Vista on my HDD --> upgraded to Win7 on 90GB SSD --> reinstalled Win7 on 120GB SSD (for more space). The old Windows installations were supposedly cleaned up and I remember using system cleanup to remove the old Windows installation to clear up some disk space.

 

[Arc]

So it is not the boot failure caused by UEFI and MBR mismatch. Nice.

It is also nice that you have changed the SATA cables. (all of them hopefully?)

Now follow post #75 by essenbe and do one more thing:

Do you have access to another computer right now? If so, download Partition wizard Bootable CD (the last one in the link). Burn it in a blank CD or in a USB flash stick.

Boot into Partition Wizards GUI following this instructions. When you are on the last screen, take a camera snap of the screen and upload the snap here.
Screenshots and Files - Upload and Post in Seven Forums

We need to see the partitions and parameters.

We need this.

Two major possibilities are still remained. The first one is a missing boot file (generally caused by two causes, either the MBR is corrupt or the right partition on the first boot disk is not marked as active; the above will tell about it.

On another way: You tried to perform a clean reinstall as it seemed. So that should wipe the boot files up. In that case, disconnect all the other discs than the 120 GB SSD (SATA and USB; must in this case), perform a clean reinstall, when done, add the other discs back.

If still the clean reinstall does not end without a BSOD, unfortunately (as for the second possibility of the origin of the issue, a corrupt/bad disc) you will need to install windows on any other disc.

 

[JTMoney66]

Hi Arc, I have not tried a clean reinstall yet. I only used my bootable USB Win7 install to try and run startup repair.

I will try the partition wizard and get back to you with a screenshot. Sorry if I missed this in the previous instructions.

I would prefer not to do a clean reinstall on the 120GB drive because it has several files I need, and it would be a hassle to copy them all via command prompt to a backup. I don't mind going ahead and doing a clean install on the 250GB drive, especially if that has a higher chance of success.

 

[Arc]

I would prefer not to do a clean reinstall on the 120GB drive because it has several files I need, and it would be a hassle to copy them all via command prompt to a backup.

Command Prompt? No.

http://www.sevenforums.com/tutorials/93347-copy-paste-windows-recovery-console.html
​

Backing up the files are not a big deal.

I don't mind going ahead and doing a clean install on the 250GB drive, especially if that has a higher chance of success.

If the attempt to install windows on the SSD (with all the other discs disconnected) fails again, then you will need to install windows on that one, because this failing attempt will confirm the biggest cause of a stop 0x6B, a failing disc.

 

[JTMoney66]

So it is not the boot failure caused by UEFI and MBR mismatch. Nice.

It is also nice that you have changed the SATA cables. (all of them hopefully?)

Yes, I only have 3 new SATA cables so that is why I disconnected the 90GB drive, so that the remaining drives that are connected would have new SATA cables (the 120GB SSD, the 250GB SSD, and the ~400GB HDD).

Now follow post #75 by essenbe and do one more thing:

Do you have access to another computer right now? If so, download Partition wizard Bootable CD (the last one in the link). Burn it in a blank CD or in a USB flash stick.

Boot into Partition Wizards GUI following this instructions. When you are on the last screen, take a camera snap of the screen and upload the snap here.
Screenshots and Files - Upload and Post in Seven Forums

We need to see the partitions and parameters.

We need this.

I will get on this asap and post the results. I do have access to my laptop, but it is Windows 8. Hopefully that won't be a problem.

Two major possibilities are still remained. The first one is a missing boot file (generally caused by two causes, either the MBR is corrupt or the right partition on the first boot disk is not marked as active; the above will tell about it.

I don't know about the MBR being corrupt (I guess that is a possibility). To the 2nd possibility: I actually already tried marking the partition on the boot disk as active in diskpart, and got the same BSOD stop 0x06B. Perhaps it was not the right partition, however.

On another way: You tried to perform a clean reinstall as it seemed. So that should wipe the boot files up. In that case, disconnect all the other discs than the 120 GB SSD (SATA and USB; must in this case), perform a clean reinstall, when done, add the other discs back.

If still the clean reinstall does not end without a BSOD, unfortunately (as for the second possibility of the origin of the issue, a corrupt/bad disc) you will need to install windows on any other disc.

I will go ahead and disconnect all the SATA cables from other drives besides the 120GB SSD.

If the attempt to install windows on the SSD (with all the other discs disconnected) fails again, then you will need to install windows on that one, because this failing attempt will confirm the biggest cause of a stop 0x6B, a failing disc.

I would be a bit shocked if the disc was failing but obviously I can't rule it out yet. It gets significant (filtered) air flow so heat shouldn't be an issue, it is only ~2 years old and it's an SSD which I wouldn't expect to fail so quickly. And I periodically use compressed air to remove dust buildup in my case. Additionally, in the command prompt I can access and cd to the 120GB drive's directories and view all of the files. So from that I assumed the drive was ok, it just couldn't boot.