Solved BSOD on Windows Startup After Ubuntu USB Trial

[dakattack]

Lenovo T410
Windows 7 64

Ran Ubuntu from thumb drive as a trial. After testing, went to load Windows without thumbdrive connected, get BSOD a few seconds after Windows begins loading:

BSOD: 0x0000007b (0xB0786a58, 0xC0000034, 0x0000000, 0x0000000)

Same result for safe mode.

Tried running Ubuntu through USB again, loads fine and functions fine.

Startup Repair:

    Startup Repair:  Root cause found:  A recent driver installation or upgrade may be preventing the system from starting.
    
    Repair Action:  System files integrity check and repair
    Result:  Failed.  Error Code:  0x4005

System Restore to point before Ubuntu, still get BSOD on Windows loading.

Memory Diagnostic passes.

Chkdsk /r finds no issues.

Repairing MBR from command prompt has no effect.

 

[Arc]

Stop 0x7B means INACCESSIBLE_BOOT_DEVICE.

What you are saying, it appears that the boot parameters got changed.

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.

If it is that issue that I am thinking, it will not be hard to fix. Otherwise, you may need to test your HDD.

 

[dakattack]

Had to take a pic with my phone:

 

[Arc]

So the windows partition is active. Try to Rebuild MBR on Disk1 and see if windows 7 boots or not.

If still it does not boot, better you test the HDD using a bootable disc check tool. Seatools for DOS will be a good choice.

Let us know the results.

 

[dakattack]

Did MBR rebuild on Drive 1, still get BSOD on Windows boot.

Seem to be having some trouble with Seatools starting. After creating a bootable USB drive, the program seems like it wants to start but then I am stuck at a black screen with FreeDOS in the upper left corner. It doesn't go past this point.

I changed my SATA controller mode from 'AHCI' to 'Compatibility'. That was my only option in that menu.

 

[Arc]

Can you burn Seatools for DOS in a bootable CD and try again?

 

[dakattack]

Short test passed.

Running long test now.

 

[dakattack]

Long test passed without issue.

 

[Arc]

So the HDD is working fine. It is just the boot files got corrupt.

Follow it: Troubleshooting Windows 7 Failure to Start

If it also failed to do it any better, please understand that the corruption is beyond repair and you need a clean reinstall.

If you need to back up any data from the HDD and you dont know how can you do it, you may follow this guide: http://www.sevenforums.com/tutorials/93347-copy-paste-windows-recovery-console.html

 

[dakattack]

It seems like switching from AHCI to Compatibility allowed it to boot properly. It didn't do this last night, but allowed Windows to boot today.

Will update if it continues to be an issue, but it appears to be solved for now.

Thank you for your help Arc.

 

[Arc]

Ah ... that's a good news!

 

[dakattack]

I forgot to mention the a notification box popped up when windows loaded mentioning that it had been restored to a previous restoration point. So it seems like it may have been a combination of the restoration and switching to compatibility mode and...something else? TIme maybe? Haha.

 

[Arc]

I dont know how it happened, but what happened there is the Linux session changed the storage controller mode. Windows cannot boot when the storage controller mode is something other than that on which it was originally installed.

As as the native storage controller mode is set there again, windows booted up properly.