Driver power state failure

I looked at a second bugcheck, also a USB hub bugcheck caused when attempting to power down a blue tooth device
the system uptime was also 53 days so I think the data in the debugger is incorrect or corrupted.
- debugger does not like your copy of win32k.sys.

anyway, I would be looking for updated bluetooth software.


6: kd> lmvm btfilter
start end module name
fffff800`01600000 fffff800`016a6000 btfilter (deferred)
Image path: \SystemRoot\system32\DRIVERS\btfilter.sys
Image name: btfilter.sys
Timestamp: Tue Sep 03 03:02:07 2013 (5225B39F)
CheckSum: 000A1072
ImageSize: 000A6000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
6: kd> !irp ffffe0000bbb5bd0


=======
The system attempted to power down a device attached to a usb port and the device did not respond within the required timeout value so the system bugchecked.
System Uptime: 53 days 6:47:19.985
BIOS Release Date 06/26/2013
Manufacturer Notebook
Product Name P15SM
Processor Version Intel(R) Core(TM) i7-4900MQ CPU @ 2.80GHz
Processor Voltage 8ch - 1.2V
External Clock 100MHz
Max Speed 3800MHz
Current Speed 2800MHz

Based on the system uptime of 53 days I would say you found a real bug that will be very difficult to pin down (assumeing the 53 days time reported it correct) You will want to do a shutdown on your machine and restart it sometimes to get all the various updates installed (rather than just letting your system go to sleep everytime after you use it)

Also: your system appears to be running a rootkit virus rikvm_38F51D56.sys
edit: some indications that this is a valid cyperlink powerISO file but you might want to check
6: kd> lmvm rikvm_38F51D56
start end module name
fffff800`04666000 fffff800`04caf000 rikvm_38F51D56 (deferred)
Image path: \??\C:\WINDOWS\system32\Drivers\rikvm_38F51D56.sys
Image name: rikvm_38F51D56.sys
Timestamp: Mon May 14 00:49:40 2012 (4FB0B914)
CheckSum: 00033650
ImageSize: 00649000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4


you might want to look into that
The debugger could not check your win32k.sys file also. This is a standard windows file and it appears to have been modified.