7805u and DRIVER_POWER_STATE_FAILURE BSODs

So I think my 7805u is dying, or at least part of it is really sick.

Two days ago I had three bluescreens in one day, so I figured "Oh it must be time to reinstall Windows" and did that. Just now, I was playing Global Agenda (which isn't very good, by the way) and it locked. I could get to the task manager, but it wouldn't let me kill the process so I spent a half hour trying different ways to do it and none of them worked. Then, I read something about someone's virus blocker being the culprit and when I went to kill the Microsoft Security Essentials process, another blue screen. Interestingly enough, I had a couple other things (Winamp in particular, though VS2008 did once but KillProcess worked on it) lock and not let me kill them the day I was getting the bluescreens. I've never had either of these problems before (at least not the locking, I've had a few BSODs but nowhere near this frequent).

So, I don't know what the hell is going on. On one hand, last last time I reinstalled Windows chkdsk seemed to be spitting out a bunch of warnings about my hard drive being totally screwed, but everything on that front has seemed fine since the reinstall. On the other, it was pretty odd that the BSOD coincided perfectly with me killing MSE, though that could be for multiple unrelated reasons I suppose. And on the third (giggity), DRIVER_POWER_STATE_FAILURE (the BSOD message) seems to indicate a driver is screwing up, which I had attributed to switching to the legacy drivers for the 1394 port to circumvent the nasty sleep freeze error 7805u's seem to have. Basically, I'm totally stumped. Any thoughts before I take it to the shooting range and destroy it so I can use my "Covers Everything" warranty to get a new one (it is still under warranty so keep that in mind if you suggest for me to open it up, I'd hate to waste that +$200 from accidentally peeling off some sticker)?

Thanks in advance, every time I have a problem Google seems to point me to you guys having helped someone else with the issue so I think I'm in good hands. And apologies if this was resolved elsewhere, I couldn't find anything that seemed related.

e: Now with 100% more HijackThis logs!
This is after I restarted, I'll try to do it again next time it seems a problem is imminent.
e2: I forgot about Crystal Disk Info so I downloaded it and ran it. Doesn't look too good.

 

HDD errors can either be a bad HDD or your system, usually CPU, is getting flakey. if the cpu is reading/writing erroneous data this can be an issue too.

what can happen with a bad hdd is when you format and reinstall you put the data back into good sectors but as you use it it then start to use bad sectors again. usually if the CPU is the culprit it goes down hill fast, I mean like really fast.

If you have another drive around that is a know good drive try that first as driver power state failure could be the drive too.......

 

I don't have another SATA drive laying around, but can you boot through eSATA? I might be able to see if Best Buy has an IDE->eSATA converter and borrow an hd from another computer in the house.

Man I really hope it's the processor, I'd love a reason to get a T9900 in this.

 

Another culprit can be memory too. since you have a spare drive bay a better investment may be a HDD as you could also always use it as a spare drive. As pointed out by others if you can do an ES cpu the x9100's are a better buy with E0 stepping and then overclockable now.

The drive replacement should not be an issue with the warrenty but the CPU can be........

Edit; you can do the normal free things.
1.) blow out the GPU and CPU fans with air to be sure cooling.
2.) reseat the drive and memory.
3.) monitor your temps to be sure the fans are working

Etc............

 

Mr. Hotkeys, where did you find the legacy drivers for the 1394 port? I just have it disabled right now?

 

If you go to change the driver and list compatible drivers the legacy one should populate from Windows 7................

 

Oh yeah, I forgot about that, thank you. I think I may have tried that already. Heck I did even remember the issue, was it the system will not wake from sleep?

 

I found with 9c.23.00 I don't need the legacy drivers, see the post in the BIOS section........

 

Sweet, I will test it out, it was a sleep issue right?
+rep

 

Restart from hibernate............

 

Alright, so an update. Bought a new hard drive, but that didn't help with the BSODs (my old one was dying anyways, plus I've got a cool new toy). I've also been meaning to a RAM test but haven't because of lazy.

I did, however, some more digging after I got another BSOD a few hours ago and found out that not only does Windows make logs for BSODs, they actually contain useful information (wowie!). So I rolled up my sleeves and busted them open, then went through the frankly awful task of installing and configuring the Debugging Tools for Windows to read their contents.

The most recent dump file and its Bugcheck Analysis:

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa8006498050, fffff80000b9c518, fffffa8004484a90}

*** WARNING: Unable to verify timestamp for o2sdx64.sys
*** ERROR: Module load completed but symbols could not be loaded for o2sdx64.sys
Probably caused by : o2sdx64.sys

Followup: MachineOwner
---------

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

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8006498050, Physical Device Object of the stack
Arg3: fffff80000b9c518, Functional Device Object of the stack
Arg4: fffffa8004484a90, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  o2sdx64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a023fc2

MODULE_NAME: o2sdx64

FAULTING_MODULE: fffff88004561000 o2sdx64

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

STACK_TEXT:  
fffff800`00b9c4c8 fffff800`02ae5273 : 00000000`0000009f 00000000`00000003 fffffa80`06498050 fffff800`00b9c518 : nt!KeBugCheckEx
fffff800`00b9c4d0 fffff800`02a8229e : fffff800`00b9c600 fffff800`00b9c600 00000000`00000002 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x292b0
fffff800`00b9c570 fffff800`02a81dd6 : fffff800`02c18290 00000000`0004ee8a 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5e0 fffff800`02a824be : 0000000b`bd55b2e0 fffff800`00b9cc58 00000000`0004ee8a fffff800`02bf43c8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`02a81cb7 : 00000002`97a9dbc2 00000002`0004ee8a 00000002`97a9db52 00000000`0000008a : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`02a7eeea : fffff800`02bf0e80 fffff800`02bfec40 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_3_disk_IMAGE_o2sdx64.sys

BUCKET_ID:  X64_0x9F_3_disk_IMAGE_o2sdx64.sys

Followup: MachineOwner
---------

The other and its Bugcheck Analysis.

Both seem to point to o2sdx64.sys, which Google has told me is the driver for my SD port (which makes sense that the errors have been recent, I just started using it much more often when I got an SD drive for Christmas that I've been leaving in it around the clock) as well as that other people have been having the exact same problem with it.

I need some sleep, but I'll try finding the new drivers for it and see if that fixes it, if not at least I can disable them and use my USB SD card reader and hopefully that at least prevents me from having further problems with BSODs.

Problem is, I used the drivers posted on Gateway's site. When I only used my SD drive periodically to get pictures off my phone, I was using the same drivers and never had a problem. Now that I've got a card plugged in all the time, this has been cropping up. Has anyone had any similar problems with the SD slot drivers? And if not, you might want to upgrade (if you haven't already) to avoid the problems I had. I know they're old and likely out of date, but damn.

For me, my computer will just hang forever and not do anything occasionally when I try to set it to sleep. I've read a lot of little fixes here and there for it, but even after using the legacy drivers and unplugging my wireless mouse (read somewhere that Logitech mice or whatever can cause the problem), I still get the hang occasionally. Much less often but it's still pretty annoying.