Windows 10: Graphics driver failure followed by unbootable system

Hi
Windows 10 has been installed on my old Toshiba Tecra laptop for some weeks now and running fine.
Last night the machine rebooted, I think after a MS Office 365 update.
The whole drive is encrypted with Truecrypt. I was able to get back in and found the intel graphics adapter had been identified as a Microsoft Basic Graphics Adapter (with resulting incorrect resolution setting) and the monitor profile had been lost.
I eventually sorted the graphics adapter issue by running windows update and reinstalling the intel driver. I also installed the .inf file for my monitor so that this was correctly identified in device manager.
All seemed ok.
The this morning I found the machine had again rebooted during the night. The machine ran through a reset procedure up until rebooting when it gave the 'UNMOUNTABLE_BOOT_VOLUME' message.

I have tried the truecrypt rescue disc but I think I have the incorrect one with me, but I don't think Truecrypt is the issue here as the bootloader indicates the correct password has been entered by displaying the 'booting' message.

So am stuck and wondering if anyone can shed any light.

UPDATE
Should have added that I enter the Truecrypt boot password and the machine indicates that this is correct as it declares 'booting'.
Then preparing system repair with options to Troubleshoot or Turn off your PC. Choosing Troubleshoot gives options to Reset this PC or advanced options. Reset PC originally ran into 'unbootable system drive' message. On 3rd attempt just now, got a series of other options including one to repair system drive. Eventual outcome is that 'StartUp Repair could not repair your PC.

I am trying to work out of this is a Windows Update issue, a hardware issue (failing hard drive or somesuch,), a truecrypt issue, some combination of all these or something else.

Will see if I have the updated truecrypt rescue disc created after I clean installed windows 10. But can't do that until Tuesday.

Thanks in advance for any pointers and advice.

:)

 

Windows 10 0x0000009f

Hi,

0x0000009F is a Driver Power State Failure code.

The main cause of this error is a device driver that is outdated or misconfigured. This may happen after a system update, a disk read/write error, or a Windows update or reinstall.

Graphics (Display) drivers and audio drivers are a common cause of this error however, any driver on the system could be responsible.

For more info and diagnostic guidance you can follow the link below:

0x0000009F (DRIVER POWER STATE FAILURE)

Good Luck and let us know how it goes.

-Richard

 

Every time I try to use silverlight players I get BSOD

Intel's driver helper tool is not always accurate.

Try the following graphics driver from Intel just to make sure you have the latest :

https://downloadcenter.intel.com/download/27484...

Post back if the error persists.

Also, check for a BIOS update as one may be available and may help with system stability.

If updating the BIOS as a general precaution back up critical files beforehand as the rare chance of a failed BIOS update may result in system failure.

 

Will Advanced Options offer you the option of a command line?
If so, do you know if it's possible to type in a command which will cause Truecrypt to decrypt the drive?

 

Which Tecra are you talking about? please be specific on the model and name

EDIT: That is just too old to run on Windows 10.

 

Yes thanks I think that I possible. I have not yet worked out the correct syntax though as it is not working for me. Obviously got something wrong.

Once I get back home I should have the correct truecrypt rescue disc. I'll give that a try as I think it is the boot into windows that is the problem. Wil post back when I have given that a try.

 

Thanks. Could you expand on how it may be too old when it has been running happily for at least four weeks? I'm intrigued as to what you think the problem may be.

 

I did some experimentation with Truecrypt - I installed it on a Virtual Machine, and encrypted the system drive. (Only a very basic drive/partition layout.)

I couldn't get it to boot to a Command Prompt as I suggested earlier - I think it tries to reboot from its own Windows PE boot loader and without the Truecrypt step, it can't read the partitions.

However I could get into Safe Mode - if you could get it to boot into Safe Mode that might help.

I also tried booting from an old Truecrypt rescue disk from an old system which has long since been over-written.
This old Truecrypt rescue disk could decrypt my VM which I only encrypted last night, even though they had different passwords/keys etc. I just needed to type in the new password.

So my suggestion would be to see if you can boot into the old rescue disk, then select the option to decrypt the system disk. (I'm afraid it won't be a quick process .) Then on an un-encrypted disk, there's more chance of getting windows going again or at least recovering your files. If you have Windows 10 Pro, you could use Bitlocker in any case (even on old hardware) which will play more nicely with boot problems of this sort.

 

I just saw this. Although I think the old rescue disk might still be able to decrypt it, it took ages for me, so if you're travelling home soon, then it might be better to wait until you're somewhere you can leave it for a few hours/overnight, rather than start the decrypt process and have to interrupt it to travel.

 

Thanks David. Just tried to use the rescue disk to boot and same windows error message about something going wrong. Just checking out the various truecrypt options and will almost certainly decrypt the drive. Will post back with results.

EDIT: decrypting now. Fingers crossed for the morning!

 

Truecrypt rescue decrypted successfully. Once I got around the truecrypt pre-boot authentication window (ESC) and mounted my data partition I am up and running again.

Now need to work out where to go from here. I am still thinking this was to do with a Windows 10 update or version upgrade that maybe also screwed graphics driver.

I have found this which suggests that this may happen every time a windows version upgrade is pushed out. See last paragraph in first section...
https://www.winhelp.us/truecrypt-sys...ncryption.html

I think I could carry on using Truecrypt on the data partition having decrypted the system partition as long as I am prepared to mount the data partition manually each time I log on. Does that sound like it should work? Presumably any upgrade failure only applies to the system partition/files?

Or I need to go to BitLocker.... but I really do not trust that this has not been 'back doored'.

 

I found that, aftar using the Rescue Disk to decrypt, I could run TrueCrypt within Windows itself, and select the option to Permanently Decrypt the System Drive. Although you have already done this, it did seem to get rid of the Boot Loader which might be left behind. Or there may be an option on the Rescue Disk to get rid of the Boot Loader?

I wouldn't be at all surprised. I don't think TrueCrypt is compatible with the sort of things Windows 8/10 try to do at boot time, especially when Windows decides it wants to auto-repair etc.

If you have the default Fast Startup enabled in Power Options, that probably won't help either, as it means a 'Shut Down' is only really a form of Hibernate and the machine rarely does a 'proper' boot-up.

I think using Truecrypt on a Data partition should be less likely to lock you out, although there's no guarantee.

Has Bitlocker itself been 'back-doored' though? And even if it has, is it any worse that Truecrypt whose own creators have said it's not secure (albeit for no apparent reason as far as I know)?

 

Hi David

Thanks for that. I think the rescue disk will probably restore the original bootloader. I think I will carry on using Truecrypt for now on my data drives (with some more frequent external backups!) until it does not work.

I don't really have anything to hide just want to make sure if machines are stolen data is secure.

I still don't trust that Truecrypt development was not knobbled by NSA and that all the stuff we are seeing, Veracrypt, TCNext, isn't all part of the same drive to get people to stop using Truecrypt.

Thanks for your assistance.

 

Having successfully decrypted the system partition setting the data partition (still encrypted) as a truecrypt favourite volume (rather than system favourite) AND leaving the truecrypt bootloader in place, using it to log on as before, means that the data partition is still mounted at boot up and ALSO that folders shared to homegroup remain shared.

Can avoid the MS tyranny for a little longer *Biggrin

 

Glad you got it sorted the way you want it. *Smile