BSOD while idle, error 09f

[Exiael]

I have Windows Home Premium x64. It is the original version installed on my computer, and it is OEM. My hardware and OS are around a year old.

While idling or trying to shut down my system encounters this error. I've never had the error while actively using my system.

 

[zigzag3143]

Two items need addressing before we can even begin to investigate.

1-Aicharger.sys is a known cause of BSOD's and needs to be removed.

2-USBHUB.sys seems to be involved please read here for some generic USB help

http://www.sevenforums.com/tutorials/165554-usb-driver-general-fix-problems.html?filter

 

[Vir Gnarus]

Zigzag is right, Aicharger is being blamed on all of the crashes in that it's holding things up. While it could be holding things up because it's waiting on something else that's holding things up, that may very well not be the case here given Aicharger's notorious reputation. It's best to remove it. Even if we wanted to dive further to find exact cause, we can't without at least a kernel dump (MEMORY.DMP in Windows directory).

Go ahead and remove Aicharger, then see how things go. If the problem persists, turn on Driver Verifier. Do not select the following checks: Force Pending I/O Requests, IRP Logging, and Low Resource Sim. Make sure to restart system after you finish setup. If you experience a boot loop afterwards, go into Safe Mode by pressing F8 prior to Windows logo and disable DV there. Provide us any new crashdumps.

 

[Exiael]

Thanks for the help. I remove aicharger and followed the link for usb devices, but the problem was still there. I'm attaching the information again with the newest dump file as well.

 

[Vir Gnarus]

Can you please turn on DV? We can't do much without it. Remember to follow my recommendations for what checks not to select. Provide us any crashdumps that may occur when DV is active.

 

[Exiael]

Sorry about that. After enabling drive verifier I was unable to even log in without a blue screen popping up. Only one of the attempts created the dump file but I'm including that.

 

[Vir Gnarus]

I may not be able to definitively discern what happened here, given that this is just from a lil ole minidump, but I can tell that at least in this case Daemon Tools was involved. It does look relatively aged (Oct 2011) so you will want to update both it and the SPTD driver that comes with it. Your best means of doing so is uninstalling Daemon Tools then deleting \Windows\System32\drivers\sptd.sys (should it exist). Then download and install the latest version of DT. Note that Daemon Tools can and has harbored bugs before, so use it with discretion regardless what version it may be.

This may however be a false positive. Your best bet is probably to uninstall Daemon Tools (and the SPTD driver) and then running Driver Verifier again as previously instructed until you get another crashdump.