BSOD when restarting windows after exteneded user session.

I am not sure what to make of that. I think it is another case of the upgrade advisor being senile again. I am using the latest Bluetooth drivers that are for my laptop; version 9.10.00T

I would be willing to bet that if I went back to the Bluetooth drivers that came with my laptop, the upgrade advisor would not have a problem with those drivers v7.10.00(T)

will autoruns work for x64? I remember that when I first got my laptop, when I went to use some of the software from sysinternals, that I found out that a fair portion of them were not 64-bit friendly

UPDATE:

Ok, I see that this particular piece of software has been fairly recently updated. I will run it as instructed and post the link in a bit

heres the link

--> http://1drv.ms/1habWFX  <--

What have you done about these devices in your Windows Upgrade Advisor report

Devices Status Details

 Bluetooth RFBUS

TOSHIBA Not compatible The driver installed for this device is not compatible with Windows 7.

 Bluetooth RFHID

TOSHIBA Not compatible The driver installed for this device is not compatible with Windows 7.

 BT Port

TOSHIBA Not compatible The driver installed for this device is not compatible with Windows 7.

To identify what loads when you boot use Autoruns (freeware from Microsoft).

http://technet.microsoft.com/en-us/sysinternals/bb963902

Select File, Save, change the “Save as type” to Text file type using the Scroll to the right and click Save. Please upload the file to your OneDrive as a shared file and post as a link here.

it is still disabled

Microsoft  uses a "lite" version of diskkeeper in windows disk defragmenter, so I still don't see how the full feature version could be the problem.

http://support.microsoft.com/kb/130539

besides that, I have googled my brains out and the last version of Diskeeper that I could find caused BSOD's was Diskeeper 2010, that is two or three version older than what I have. I have found no BSOD issues involving Diskeeper 12 Professional that has been reported online.

there are some conflicts with Diskeeper and other software, none of which I have installed.

I did do  a manual defrag last week using diskkeeper, but ifaast, intelliwrite, and automatic defrag remain disabled.

Patrick Barker made this suggestion on 30 January 2014 Diskeeper is known to cause crashes, please remove it for troubleshooting purposes.

Did you not remove it or did you remove it and put it back on your system?

there have been no updates released by Toshiba for my laptop in a long time (years). I have all the latest drivers they have made available. I use Microsft Security Essentials for my AV needs, and I have yet to see any sort of conflicts from it. as for verifier, activating it causes my system to bsod on me at boot, if you see my previous post on what happened last time I activated it, you will see what happens. I'm not in any sort of mood right now to mess with safe mode unless I absolutely have too. I don't know what this "DRIVER_POWER_STATE_FAILURE " is, but it is annoying that it happens so inconstantly, which makes it hard to diagnose. I did notice the crash address is different than last time, this time it is listed as "ntoskrnl.exe+75bc0"

there hasn't been any real changes to my system's setup aside from some new games and updates from Microsoft. Maybe windows is not designed to run continuously for such long periods of time?

Update....

Boy do I feel stupid...... apparently my system not only made a kernel dump of the event, but a minidump of it as well..... I am uploading it as we speak as well as copies of my application and system event logs.

here is an updated link to (hopefully) all the necessary files for troubleshooting

--> http://1drv.ms/1cM07ZJ  <--