BSOD when restarting windows after exteneded user session.

interesting that 4 of the entries were left over from a SkyDrive uninstall (probably when the next version got installed)

I would think that M$ would have done a better job with their uninstall routines.

those not found entries are part of a dos command that uses the RMDIR command "C:\windows\system32\cmd.exe /q /c rmdir /s /q "C:\Users\Chris Solomon\AppData\Local\Microsoft\SkyDrive\16.4.6013.0910"

I know that since they refer to Skydrive that they are safe to delete, but I am wondering if they fixed this problem in the latest OneDrive version of the same software.....

one of the yellow marks is for synth3dvsc.sys which is Microsoft Virtual 3D Video Transport Driver. Now, I don't know what happened to the file, but SFC is not restoring it. before I delete the entry, I am going to run checksur again. I frequently use Windows XP mode as well as remote desktop (which is used by XP mode as well), and I really don't want to screw up those two functions of windows.

tusbhub is a USB driver for remote desktop, again I don't know why it is missing, but I will see what a checksur does

VGPU.sys is a virtual GPU driver, same as last two

I am finding it difficult to keep up with two people trying to help me solve the same problem from different angles. Is it alright if I stick to Gerry for now and see what happens? if I still need help, I will be more than happy to give you my undivided attention.

Please use Autoruns to delete 14 entries where the words “File not found” appear. With Autoruns you can uncheck an item, which disables it from starting, or you can right click an item and then delete it. Click the Everything tab and look for the rows highlighted in yellow.

Correct do not run Driver Verifier all the time as it can cause instability when there

would otherwise be none. Run it a couple of times at most. It will not find all issues.

Please use the troubleshooter I posted on page one skipping nothing.

Rob - SpiritX

ugh.... that will mean having to uninstall powerdvd before I activate driver verifier I don't know why a file which is not even a driver cause verifier to bsod my system, but what ever.

my drivers except for maybe my video drivers (they are recent though) are as up to date as they can be. apparently Toshiba has a bad habit of releasing a laptop/pc and then supporting it for a few months or so and then dropping support for it like a hot potato.

Is it all right if I only do a boot with the Toshiba stuff loaded instead of a clean boot? because I have done a clean boot I the past (only ms loaded stuff) and the Toshiba stuff always gave me grief afterwards when go to renable it. essentially I just want to boot the stuff that came with it from the factory.

I have been advised not to keep my system running long term with verifier enabled, but this issue is chronically erratic as to when it will happen. but it occurs after having a windows session that lasts for 1 or more weeks. as for all the other stuff you listed, I am obviously not totally helpless when it comes to computers, so much of that stuff has either been tried or is not an option.

will setting up verifier to run for an hour or so and then sending in any logs be sufficient? this is my primary PC, and I depend on it heavily. so having it setup to run verifier for a couple of weeks is out of the question (and not recommended). same goes for the clean or lighter boot scenario that I suggested.

another reason I suggested the lighter boot scenario is the fuss that the laptop makes when I try and clean boot is caused by either one or both of these hardware devices; there listing in device manager is:

TOSHIBA x64 ACPI-Compliant Value Added Logical and General Purpose Device

controls Toshiba specific hardware functions including health sensors, interacts with TOSHIBA HDD Protection - Shock Sensor Driver device, ECO and other power management features, etc

TosSec Class

   |  

   ---  TOSHIBA tos_sps64 Driver

I don't know what this is for and because it appears to a Toshiba security feature, I leave it the **** alone.

Update: just did some research into "TOSHIBA tos_sps64 Driver" and it appears to be a hardware driver related to hardware functions, and furthermore if it becomes damaged or goes missing, it will totally prevent the system from booting successfully even to safemode (yet another reason to leave it the **** alone.).