[SOLVED] Sleepmode not working anymore + BSOD 0x9F - Windows 10

F

flupke01

Member
Joined
Sep 14, 2015
Posts
17
Since about a week Windows won't get into sleepmode any more. If I try to use sleepmode, Windows seems to do so, but instead of that the system shuts down. This takes about 2-3 minutes and in the meantime the HD activity led on my system is quite busy. This happened once in a while the last months, but it just lately became a structural problem. Before it got structural, it could also happen that it took minutes to get the system in sleepmode, but it did get there, eventually.
When I start the system again after the failed sleepmode there's no error notification, only Livemail is stating it has not been shutdown properly.

Not sure if it is Windows 10 related (I've managed to get Win 10 installed about 10 days ago, with a lot of hassle and the help of this forum.), it happened in Windows 8.1 as well, but not the shutting down version... Looks like Win 10 made it worse though...

I've tried all possible combination's of my memory banks, but that did not help
I tried to learn something from the logfiles with WhoCrashed, but don't know what to do next. Analysis says this:

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Thu 8-10-2015 06:51:29 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\100815-10109-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E240)
Bugcheck code: 0x9F (0x3, 0xFFFFE0011B8F5580, 0xFFFFF800A228D990, 0xFFFFE0011D0CE010)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



Hope someone can help?
 
Hi flupke01 ^_^,

Your ZIP file contained around a dozen Dump files which means that the Blue Screen event took place around a dozen times at least. Strange that you did not notice it. Anyways, I have analysed your dump files and below has been provided an analysis of the same for informative purposes :-
Code: 
3: kd> !irp ffffe0016f573e10Irp is active with 4 stacks 3 is current (= 0xffffe0016f573f70)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
     cmd  flg cl Device   File     Completion-Context
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    


			Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    


			Args: 00000000 00000000 00000000 00000000
>[ 16, 2]   0 e1 ffffe001701b7050 00000000 fffff802f53f82d0-ffffe0016f638460 Success Error Cancel pending
	      Unable to load image rt640x64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for rt640x64.sys
*** ERROR: Module load completed but symbols could not be loaded for rt640x64.sys
 \Driver\[COLOR=#ff0000][B][U]rt640x64[/U][/B][/COLOR]	nt!PopSystemIrpCompletion
			Args: 00015400 00000000 00000005 00000003
 [  0, 0]   0  0 00000000 00000000 00000000-ffffe0016f638460    


			Args: 00000000 00000000 00000000 00000000

It seems like the Realtek Driver for Ethernet is causing the problem in your case. The driver installed on your system is outdated. Kindly download the below driver and then install it -
http://download.msi.com/dvr_exe/realtek_pcielan_w10.zip

The Driver is for your motherboard and hopefully would work without any problems.

In case of any problems, feel free to post back ^_^



-Pranav
 
Hi Pranav, thanks for helping me out here.

the update did something good for sure; the system is going in sleepmode now, kind off anyway. Still in a weird way though: the system seems to behave the same as I described before, but with 2 important differences. The system now shuts down really fast, in maybe 3-5 seconds, but it looks really to shut down: no flashing or burning leds whatsoever. But when I start the system up again it's going quite fast too, and with restoring all open programs etc.
So in the end it's like it should be, but I do wonder why I don't see my led flashing like it use to, as a sign that the system is a sleepmode?

I do have 2 remarks: I actually did not see any BSOD's for several months, I don't even think I ever saw one since updating to Windows 8.1, which is quite a long time ago... And I surely know how to recognize a BSOD, to my regret ;) So that is quite weird, I guess... And I did see in WhoCrashed there have been several error reports about this...

Also I'd like to mention that I've run MSI Live Update lately (as I do now and then); isn't it strange it did not tell me to update this driver?

Hope you have an idea about the (not) flashing led?
 
flupke01 said:
Hi Pranav, thanks for helping me out here.

the update did something good for sure; the system is going in sleepmode now, kind off anyway. Still in a weird way though: the system seems to behave the same as I described before, but with 2 important differences. The system now shuts down really fast, in maybe 3-5 seconds, but it looks really to shut down: no flashing or burning leds whatsoever. But when I start the system up again it's going quite fast too, and with restoring all open programs etc.
So in the end it's like it should be, but I do wonder why I don't see my led flashing like it use to, as a sign that the system is a sleepmode?

I do have 2 remarks: I actually did not see any BSOD's for several months, I don't even think I ever saw one since updating to Windows 8.1, which is quite a long time ago... And I surely know how to recognize a BSOD, to my regret ;) So that is quite weird, I guess... And I did see in WhoCrashed there have been several error reports about this...

Also I'd like to mention that I've run MSI Live Update lately (as I do now and then); isn't it strange it did not tell me to update this driver?

Hope you have an idea about the (not) flashing led?
Click to expand...
Hi Flupke01 ^_^,

Glad to hear that the issue is fixed. ;)

Regarding your remarks,
  1. There have been cases in which the user did not see any Blue Screen because it was very fast and yet a dump file is generated. In many cases, the user would see the Blue Screen for hours and still not have a dump file. Most systems are also set to Automatically Restart on a BSOD so it is possible that you might be away when the event occurred (Highly unlikely though). Furthermore, as newer versions of Windows are releasing, the tendency of a BSOD is decreasing.
  2. The best way to check for driver updates is to go to OEM's website and then download the driver manually. Honestly speaking, I don't trust these tools since I don't know what kind of drivers they are downloading and whether they would be compatible or not. It is just me though :p


I hope I have answered your questions. In case of any further doubts, feel free to post back ^_^.

Marked this thread as Solved.



-Pranav
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top