Feedback for recently analysed BSOD's

Good day,

Lately I have been getting some BSOD's on my computer on a certain occasion:

Whenever awakening my computer out of sleep mode, everything works fine, until I have to shut down the computer. Then it will hang at "Shutting down..." for almost 20 minutes, to be followed by a BSOD.
I have approximately 4 dump files of this already and after analysing with WinDbg, I could come to the conclusion that it has something to do with an installed Realtek driver.

This is the script of the latest analysis:

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: fffffa8005f33a10, Physical Device Object of the stack
Arg3: fffff80000b9a3d8, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: fffffa8005592010, The blocked IRP

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


DRVPOWERSTATE_SUBCODE: 3

IMAGE_NAME: pci.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7928f

MODULE_NAME: pci

FAULTING_MODULE: fffff8800100d000 pci

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

DPC_STACK_BASE: FFFFF80000BA0FB0

STACK_TEXT:
fffff800`00b9a388 fffff800`036e3510 : 00000000`0000009f 00000000`00000003 fffffa80`05f33a10 fffff800`00b9a3d8 : nt!KeBugCheckEx
fffff800`00b9a390 fffff800`0368072c : fffff800`00b9a4c0 fffff800`00b9a4c0 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x324a0
fffff800`00b9a430 fffff800`036805c6 : fffff880`0b304990 fffff880`0b304990 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`00b9a4a0 fffff800`036804ae : 00000034`1fa591f0 fffff800`00b9ab18 00000000`0015e5aa fffff800`037f77c8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9aaf0 fffff800`03680297 : 0000000e`3870a5c3 0000000e`0015e5aa 0000000e`3870a5d3 00000000`000000aa : nt!KiTimerExpiration+0x1be
fffff800`00b9ab90 fffff800`0366c5ca : fffff800`037f3e80 fffff800`03801cc0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9ac40 00000000`00000000 : fffff800`00b9b000 fffff800`00b95000 fffff800`00b9ac00 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

IMAGE_VERSION: 6.1.7601.17514

FAILURE_BUCKET_ID: X64_0x9F_3_POWER_DOWN_Rt64win7_IMAGE_pci.sys

BUCKET_ID: X64_0x9F_3_POWER_DOWN_Rt64win7_IMAGE_pci.sys

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_0x9f_3_power_down_rt64win7_image_pci.sys

FAILURE_ID_HASH: {041ba02b-99ae-ff7a-d9e6-d2dba0b936e9}

Followup: MachineOwner

At first, I thought this had something to do with the Realtek HD Audio Drivers. I had updated them once almost 2 years ago and updated them again less than a year ago, but I'm afraid that caused instability in my system, as a strange sound issue appeared, which I'm going to leave outside this topic (that's another story which I'll probably post in another section sooner or later)
I was however able to find the "default" audio drivers that were installed from the moment I bought this computer (eMachines model ET1870 ; bought in 2011). Their site had a downloads page which contained a Realtek Audio Driver that should be compatible with my motherboard.

6.0.1.7246 was the version I had installed as "latest / unstable", the version from their site was 6.0.1.6257 (probably more compatible with my system than later versions), so I downgraded it, hoping to improve the situation.
The reason I updated the audio drivers (which normally shouldn't be necessary to do?) is that it seemed to interfere with a recent video game, which caused my whole computer to freeze up, having to do a forced shutdown. This is no concern to me. (for now...)
I haven't checked if the BSOD's have been resolved by this downgrade yet, will do after further feedback from you people.



After some browsing however, I found out that km:x64_0x9f_3_power_down_rt64win7_image_pci.sys has something to do with Realtek LAN drivers, which are also installed on my computer.

Realtek Ethernet Controller Driver Version 7.41.216.2011
On the same site I got the older version audio drivers, I found version 7.36.1224.2010 for Realtek "LAN drivers", which I assume they mean my Ethernet Controller Driver.
However that seems to be an older version aswell and I have never manually updated these drivers. I think this device got updated through Windows 7 updates, but quite long ago (7.41.216.2011 update goes back to 28th of June 2011, which is a date before I purchased this computer (November 2011), so I think the ethernet controller driver weren't touched by Windows 7 afterwards at all

I'd appreciate any help on this issue and hopefully I'll be able to cure these BSOD's.



Extra: I did find some older minidumps aswell that did not spoke about Realtek drivers. I think I'll just post them here aswell if you had liked to analyse these aswell... :)

Edit: See .zip file (if the older BSOD's are actually contained inside)


As stated above, I'll appreciate your time and effort into helping me with this!

Blue Screen of Death (BSOD) Posting Instructions

There is a lot of info missing from your upload, please run the tool again and wait for a couple minutes for the files to be gathered before uploading

Have a look at someone elses BSOD upload and you will see what it should contain
If it fails to collect the correct files again please manually generate a msinfo32 file and upload with your next post

Please also run a sfc scan to check your system files
SFC /SCANNOW Command - System File Checker

OK will see if I can get our sfc guru to have a look at your scan results

OK, the stop error is 0x9F Driver Power State Failure so we can be reasonably sure the problem is driver based and RT64win7 is being highlighted in the crash dumps (along with pci.sys)
The driver is listed as Rt64win7.sys Wed Feb 16 09:03:57 2011, see if there is an update from Realtek for your network driver and after we have sfc results we may be able to eliminate windows driver problems.

I would also recommend lightening up the start up by removing all entries except AV (if only temporarily) and remove daemon tools which is a very problematic piece of software in terms of BSOD issues
After removing daemon tools run this link to ensure you do not have the sptd.sys driver on your machine, if it is not present the uninstall button will be greyed out
SPTD Uninstaller x86
SPTD Uninstaller x64

Uninstaller source page

Well, Daemon Tools was a program which I have been using regularly, just for loading .iso's in a virtual drive. If you really think it's an unstable piece of software I guess I'll have to find an alternative, unless you say the uninstallation is temporary. (or unless you know a better alternative for mounting .iso's on a virtual drive)
I'll do as you say and will give you feedback soon.
However I do not fully understand your meaning with "removing all entries". I do make sure there isn't too much stuff running on windows startup already, and the computer starts up quite fast (of course slower than 3 years ago, but I did manage to speed it up after uninstalling some things and tweaking)
Removing all the entries is temporarily, right? Just to have the sfc scannow give better results? I do not fully understand, to be honest.

Edit: Daemon Tools and the SPTD drivers from it are removed succesfully. I'm waiting for the next step(s).

For the Realtek drivers. I am not sure which one I have to download from their site (their site is pretty much a mess)
The actual name "Ethernet Controller drivers" does not seem to appear anywhere, so I'm never 100% sure which drivers I actually have to be downloading from them.
Device manager calls it the PCIe GBE Family Controller, so that is it.
However I am still not very sure if it is actually necessary or a good idea to update such drivers (same with the Realtek HD audio drivers) I have the feeling that compatibility with my system will not be guaranteed and so it might suffer from incompatibility / instability in the future.

The only error in the CBS log was from the SFC scan - and that one is the 'usual' one from KB3068708.
You can either ignore it, or uninstall the update, and hide it when it returns in Windows Update.
MS say they will fix it some day - but they don't say when (so don't hold your breath!)