BSOD when restarting windows after exteneded user session.

no, all BSOD's have occurred after having the windows session going for a week or more (I use sleep or hibernate when I wasn't using the laptop) none of the BSOD's occur during or shortly after a boot was initiated. before the BSOD's happen, windows will always start acting weird like the taskbar clock will stop updating (lastime right before crash it still read 11:27 PM /9/2014) or the web browsing and any file intensive operations will become sluggish. games will start acting like the computer is unable to process the data fast enough, resulting in a "this program has stopped responding" scenario. I always keep a close eye on my temps, and they always stay at or below 69% and the fans never ramp up past 50%, so I know the processor is not ramping the speed down because of high temps or anything like that. I have watched the clock speed before restarting, and it is with in normal ranges (1500Mhz to 2800Mhz) for all cores. oddly when windows starts acting wonky (which means I get a BSOD when I tell windows to restart) the load on all 8 cores Is not higher than it usually is normally.

I really don't know what to make of this all....

Maybe Windows wasn't designed to run with such a long user session. maybe if I had win7 enterprise I would not run into this issue since servers are designed to run 24/7 without restarts and the like.

I looked in my c:\windows\system32\driverstore\FileRepository\ and C:.\system32\drivers for the missing Microsoft driver files. while they did exist in .\filerepository, the did not exist in they or were missing in ..\drivers. I went ahead and copied the sys files to .\drivers and since checksur did not catch them. the yellow marks for those drivers have disappeared. as for the others, I deleted them.

The problem you have is that it may be another month before you get another BSOD error. This makes it difficult to know whether anything you do has resolved the problem.

When you wrote the subject for your thread you mentioned restarting windows. Have all BSOD errors occurred shortly after a boot was initiated?

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.