Little update:

I've just downloaded MS debugging tools. I'm new to all this but it looks like the problem is probably due to ntkrnlpa.exe. Anyone know what this does?

Am downloading the symbol packages now as the debugger isn't using the correct symbols so isn't able to do an analysis.

 

hi try having a look in the device manager look for any yellow ! or red x if there are any go to the mfr support website for your model and download the latest drivers you may need to turn off your antivirus briefly to install them

 

Thanks for the reply.

I've looked at my device manager but there aren't any yellow ! or red x.

Installed the symbols for the debugger but either have the wrong ones or not doing things correctly as it's still telling me they're wrong. Can't find the kernal for the file I mentioned above.

I've also looked at my event logs and found quite a few warnings, errors and criticals under diagnostics-performance and a couple of errors under diagnostics-dps. Everything seems to point to errors from resuming from standby (hibernate) and diagnotics performance and diagperf.dll. Tried the event log online help but it doesn't come up with any results for the queries.

Bit stumped as what to do now...

 

hi maybe this can help http://forums.majorgeeks.com/showthread.php?t=35246

 

Thanks for the link. Seems like I've been doing things like in that guide but still not getting the correct symbols.

Looking at the MS website again it looks like I need to download more symbols. Got the SP1 symbols but not the original RTM ones yet, so am downloading them now.

Will give that a go and will see. Resolved or unresolved, I'll be back!

Just incase this may help, this is what I get when I debug at the moment:

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 00000003, A device object has been blocking an Irp for too long a time
Arg2: 85a07708, Physical Device Object of the stack
Arg3: 816c15d8, Functional Device Object of the stack
Arg4: 84aae220, The blocked IRP

Debugging Details:
------------------

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

 

hi i think you may be as well to update all the drivers if you cannot get the specific one pinpointed as it seems from what little you can get this is the problem get them from the mfr

 

Yeah, I updated all my system drivers (ones that I could find) over the weekend, wanting to see if any of them were causing the problem but another bsod occured this morning.

Have just installed the latest driver for my ext hdd, which according to Buffalo, is an important update for powersacing function. Hope this solves it.

One thing that is still bugging me is that the original MS support article said it was a firewire error when I've never used firewire. If this update doesn't fix things then maybe I'll try disabling it.

 

Does the problem continue if you disconnect the external drive?

You haven't actually uploaded the minidump -- sometimes the stack trace or other data can shed further clues.

Let's see if I get the same message, usually it's best to use the symbol path SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols rather than download the whole bunch for a specific version (if you have a fast connection)

 

Hi Rollin' Rog. I think I've located the problem. I tried to upload the minidump file in the zip but it woiuldn't let me for some reason.

Last night I re-read that article that joeten linked to and put the symbol path as it and you suggested. It suggests the error is probably in bautopw.sys. No symbols could be loaded for it in the debugging but this file is causing the driver fault.

A google search reveals that it is a Buffalo eco manager filter driver. So it is the ext hard drive that is causing the problem!

Only thing is, this .sys file wasn't updated when I installed the new drivers yesterday. And another bsod occured just now as I resumed from hibernation. What shall I do? Uninstall the eco manager and delete this driver (if it's not removed by uninstalling)?

The problem seems to occur if I hibernate with the ext hdd connected to my laptop, and then resume with it unplugged. Suppose the easiest thing to do is disconnect before hibernating, or resume then disconnect. But sometimes it's just that I move my laptop around and don't think about disconnecting my ext hdd before hibernating...

 

Good work, I would remove any application whose driver is showing as the faulting module in the debugger. Then test with it removed. If reinstalling brings back the same problem -- you might contact the manufacturer to see what they have to say, or just see if the device will work without any additional drivers or software from the vendor. Most actually will, just without some bells and whistles.

 

Ok thanks, I'll give that ago and see how I get on.

 

Good luck, will look for your update when you have tested fully.

 

It does seem that the eco manager that came with the Buffalo ext hdd was behind the bsod after I resumed from hibernation on my laptop, with the bautopw.sys driver causing the problem. Once I uninstalled the software bautopw.sys was deleted and I have not had a bsod since.

Will have to see if the built in Vista power management will spin down/stand by an ext hdd after some activity now but will mark this thread as solved.

Good thing that I seem to have got it sorted! Thanks for all your help :up:

Long description below:

I uninstalled the eco manager (which deleted the bautopw.sys driver) and tried restarting, then hibernating with the drive plugged in. When I resumed with the drive unplugged I didn't get a driver power state failure bsod.

I then tried reinstalling the eco software and hibernated with the drive attached. When I resumed with the ext hdd disconnected I got a 9f error bsod after a few minutes. Debugging the minidump file again said that bautopw.sys was most probably the cause.

Uninstalled the eco software again (getting rid of bautopw.sys) and have since not had a bsod when resuming from hibernation.

 

hi ive been watching your thread as rollin rog came in and is better on the bsod thing than me but it does seem you have found the culprit glad you got it sorted

 

I'd give the vendor a toot on the phone Ribena -- at least just to let them know there are issues even if they don't have an answer for you. I'm sure the drive is under warranty.

There may be a registry hack or something they know of that needs a modification.

Anyway glad to hear the problem is definitely identified.

 

Thanks again guys.

Glad to have got it sorted as I'm away for a while now. Will try to give them a ring when I get back and if they let me know anything then I'll update the thread.