New
#11
Be sure to let me know.
Hi essenbe, so far a whole week without a glitch. I think it's fixed! Thanks.
If I run into a new BSOD, I'll make a new post on this forum.
That's fantastic. I am glad you have it running like you want it. If you believe it is fixed, would you please mark this thread as solved. If you have any further problems, you can post back in this thread. I am subscribed and will get an email that you have posted. Thanks very much for giving your feedback and letting us know it is working well. Thanks.
Darn, just had a BSOD again. Another power driver state failure.
My iPhone was connected by USB (just charging) at the time the BSOD occured.
What file shoud I upload? Or should I follow all steps from the posting instrcuctions (upload a complete zip-file)?
Yea, upload the whole thing. Any Apple stuff causes problems for a lot of people, me included. I had to do 2 clean installs to get rid of iTunes, which gave me a fit. Apple programs what to take over the whole computer and have to run at startup or they won't work right. I run almost nothing at startup, except what I have to have.
Thanks essenbe. New files uploaded.
Ok, this is pretty much the best I can do, right now
Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 9F, {3, fffffa8005c20710, fffff80000b9c518, fffffa8009ee1110} *** WARNING: Unable to verify timestamp for usbaapl64.sys *** ERROR: Module load completed but symbols could not be loaded for usbaapl64.sys Probably caused by : usbaapl64.sysusbaapl64 is your Apple iPod/iPhone Mobile USB device driverCode:usbaapl64 start end module name fffff880`07059000 fffff880`0706b000 usbaapl64 T (no symbols) Loaded symbol image file: usbaapl64.sys Image path: \SystemRoot\System32\Drivers\usbaapl64.sys Image name: usbaapl64.sys Timestamp: Tue Nov 27 17:38:02 2012 (50B54EDA) CheckSum: 0001669F ImageSize: 00012000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
So, basically your Apple device has blocked an I/O driver request Packet within an allotted time .Code:DRIVER_POWER_STATE_FAILURE (9f) A driver has failed to complete a power IRP within a specific time. Arguments: Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time Arg2: fffffa8005c20710, Physical Device Object of the stack Arg3: fffff80000b9c518, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack Arg4: fffffa8009ee1110, The blocked IRP
Also listed was
That is your ESET Smart SecurityCode:em008_64 start end module name fffffa80`084be000 fffffa80`085c9000 em008_64 T (no symbols) Loaded symbol image file: em008_64.dat Image path: C:\Program Files\ESET\ESET Smart Security\em008_64.dat Image name: em008_64.dat Timestamp: Wed Jul 09 07:16:02 2014 (53BD3282) CheckSum: 00000000 ImageSize: 0010B000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
So, the logical assumption is that one is blocking the other or they are most likely having a conflict. Due to the fact that it said it couldn't load the symbols or image for either one, I would assume that the Apple Device is blocking your Eset security or they are probably having a conflict because neither could be loaded, most likely other things too, which made windows crash.
Thanks essenbe.
iTunes and ESET used to work nicely next to eachother. So, probably somewhere along the line, program-updates started to cause conflicts.
I'm gonna try a driver rollback for usbaapl64.sys
I'll keep you posted,
Ok, so the driver rollback didn't work (the PC couldn't connect to the iPhone anymore).
What about this hypothesis: ESET tries to scan all attached drives, including USB sticks and mobile devices. The iPhone does not allow to be scanned ("your Apple device has blocked an I/O driver request Packet within an allotted time") and bang! BSOD.
If this may be the case, I can check if I can get ESET *not* to scan my iPhone when it's connected.
Not allowing ESET to scan the iPhone when it's connected, seems to work. (If not, I'll report back here again).
Essenbe, thanks for your analysis.