Windows 7 sometimes hangs during starting because the second drive is manually BitLocked. 1st Drive: SSD (Unencrypted)2nd Drive: Raid10 (Encrypted with BitLocker)If the computer has been off during the night, upon start up Windows shows the logo animation, then the screen goes black prior to displaying the welcome logon screen. However it never shows this and remains black with the HDD light blinking now and again. It stays like this forever. I have a feeling if I left it on for several hours, it will probably go to the welcome logon screen. My only recourse of action is to remove the computer cover and unplug all the RAID10 STAT cables from my Hard Drives. (Raid10 using Intel ICH10R).My guess is "Windows 7" is attempting some sort of Scan Disc or Disc Defragmentation but cannot access the encrypted volume. Instead of instantly giving it, it hangs the system???FYI: It's the second time its done this (in between reformats). The first time I thought it was the AntiVirus root kit scan causing this. However the second time I booted in safe mode and uninstalled it, and the problem still continued until I remove the STAT cables which tells me it's a Windows 7 related problem.So what gives? Is such a scan scheduled to run after prolonged shutdowns, will this be fixed in Service Pack 1 and is there a workaround to prevent this? Thanks!

Hello,This problem may be also caused by the BIOS and the chipset drivers. Try to update the BIOS and chipset drivers. If the issue persists, try to disable AHCI mode in bios. Thomas77

It did it again this morning. The computer was off for a few hours last night.When it was booting into Windows in between Low-Res display and the welcome screen, the screen remained black with no mouse pointer... however the USB mouse and keyboard both powered up.Windows would only boot up in Safe-Mode.I can't disable RAID, otherwise it will corrupt my RAID10 volume.In safe mode, I did uninstall and load an old driver for the "Intel(R) ICH8R/ICH9R/ICH10R/DO STAT RAID Controller" , v8.6.2.1012 to no effect.I also tried changing the Bios clock back to the time the system was shutdown to no effect.As an experiment I booted the computer (only as far as the Windows Recovery Menu, one that says Start Recovery Console or Start Windows Normally) with the STAT cables removed and turned off the system and re-inserted them. Then the computer booted straight into windows.So yes, I think it is something in the bios that triggers this event... however it's not the cause why Windows is hanging, since it's able to load safe mode fine with the Intel RAID controller driver running. The motherboard is a P6TD Deluxe and it was updated with the latest bios several weeks ago.I'll see if there's a driver update for the chipset. If there isn't one, the next time this happens I'll try removing the driver and see if the system boots up.

A new Bios ROM (released yesterday) and updated Intel Chipset driver appears to have fixed the problem.Thank you for your suggestion.