Windows 8.1 fail to resume from hibernate or "fast start".

Dashwood

New Member
Messages
2
I recently installed a clean installation of windows 8.1 x64 on my aging laptop, but for whatever reason the system fails to "fast start" or resume from hibernation as it will reach the window's boot logo with the spiraling dots albeit spiraling "very slowly" with the cpu fan spooling up audibly in the back ground, HDD activity light stays lit although little or no audible activity is presented. I can only get around this by doing a hard restart via forcing a shut down by holding the power button. Then it would proceed to boot normally.

The Event viewer shows nothing out of the ordinary.

Disabling hibernation function via cmd "powercfg -h off" does seem to remedy this but this is more of inconvenience and hassle for me since I'm on a laptop with somewhat less than stellar performance as it does not do much more beyond watching HD videos online and offline. I find these boot time saving features and hibernation rather paramount for this laptop's continued usage.

My system spec is as follows:

Acer Aspire 3100 with "Nevarro" mainboard
ATI Radeon Xpress 1100 with up to either configurable BIOS option of up to 32, 64, 128, 256 Megabytes of Shared Memory.
2GB DDR2 RAM
Turion 64 X2 TL-60 2.00Ghz Dual Core
 

My Computer

System One

  • OS
    Windows 8.1
    Computer type
    Laptop
    System Manufacturer/Model
    Aspire 3100
    CPU
    Turion 64 X2 TL-60 2.0Ghz
    Motherboard
    Navarro
    Memory
    2.0GB DDR2 Hynix
    Graphics Card(s)
    ATI Radeon Xpress 1100
This may help (?)
Some older Dell models had this problem. No remedy seemed to be available. Only recently, Dell have come up with a solution. There is now a Bios update for the particular model (Latitude E6510). After applying the update, the bios has to be set back to factory default, rebooted and set up again to your own requirements. This worked for me, with that particualr model.

In your case, forget the update for the moment. Try the Bios factory reset and setup only.
 

My Computer

System One

  • OS
    Windows 8.1
    Computer type
    PC/Desktop
    Other Info
    Use several different computers during a day, so specs are irrelevant.
If you mean the optimized defaults, I have since tried that. Also my BIOS is the latest version at 3.13.

UPDATE:

I did notice that every attempt to fast boot leaves a minidump:

ATTEMPTED_SWITCH_FROM_DPC (b8)
A wait operation, attach process, or yield was attempted from a DPC routine.
This is an illegal operation and the stack track will lead to the offending
code and original DPC routine.
Arguments:
Arg1: fffff801f35d6a00, Original thread which is the cause of the failure
Arg2: ffffe00042c9d280, New thread
Arg3: 0000000000000000, Stack address of the original thread
Arg4: 0000000000000000

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

FAULTING_THREAD: fffff801f35d6a00

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0xB8

PROCESS_NAME: System

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from fffff801f32fd88e to fffff801f33cf036

STACK_TEXT:
fffff801`f4be25a0 fffff801`f32fd88e : ffffe000`00000004 fffff801`f35d6a00 00000000`e0620000 00000000`00000000 : nt!KiSwapContext+0x76
fffff801`f4be26e0 fffff801`f32fd339 : fffff801`f35d6a00 fffff801`f4be29b8 00000014`2adee836 00000000`00000000 : nt!KiSwapThread+0x14e
fffff801`f4be2780 fffff801`f3331d64 : fffff801`f35d6a00 00000000`00000000 00000000`000000b9 00000000`00000000 : nt!KiCommitThreadWait+0x129
fffff801`f4be2800 fffff801`b6edd8e6 : ffffe000`42959960 ffffe000`42959901 00000000`00000002 ffffe000`435c5900 : nt!KeDelayExecutionThread+0x644
fffff801`f4be28a0 ffffe000`42959960 : ffffe000`42959901 00000000`00000002 ffffe000`435c5900 ffffffff`fff85ee0 : EMS7SK+0x88e6
fffff801`f4be28a8 ffffe000`42959901 : 00000000`00000002 ffffe000`435c5900 ffffffff`fff85ee0 00000000`00000000 : 0xffffe000`42959960
fffff801`f4be28b0 00000000`00000002 : ffffe000`435c5900 ffffffff`fff85ee0 00000000`00000000 00000000`00000282 : 0xffffe000`42959901
fffff801`f4be28b8 ffffe000`435c5900 : ffffffff`fff85ee0 00000000`00000000 00000000`00000282 fffff801`b6edd747 : 0x2
fffff801`f4be28c0 ffffffff`fff85ee0 : 00000000`00000000 00000000`00000282 fffff801`b6edd747 00000000`0000c350 : 0xffffe000`435c5900
fffff801`f4be28c8 00000000`00000000 : 00000000`00000282 fffff801`b6edd747 00000000`0000c350 ffffe000`42959960 : 0xffffffff`fff85ee0


STACK_COMMAND: .thread 0xfffff801f35d6a00 ; kb

FOLLOWUP_IP:
EMS7SK+88e6
fffff801`b6edd8e6 ?? ???

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: EMS7SK+88e6

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: EMS7SK

IMAGE_NAME: EMS7SK.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 461c9c8e

FAILURE_BUCKET_ID: X64_0xB8_EMS7SK+88e6

BUCKET_ID: X64_0xB8_EMS7SK+88e6

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

I hope this helps.
 
Last edited:

My Computer

System One

  • OS
    Windows 8.1
    Computer type
    Laptop
    System Manufacturer/Model
    Aspire 3100
    CPU
    Turion 64 X2 TL-60 2.0Ghz
    Motherboard
    Navarro
    Memory
    2.0GB DDR2 Hynix
    Graphics Card(s)
    ATI Radeon Xpress 1100
Not a lot of help (to me!). But, the message and problem is usually triggered by an incompatible, or out of date, software item. Acronis is often a guilty party in this??
 

My Computer

System One

  • OS
    Windows 8.1
    Computer type
    PC/Desktop
    Other Info
    Use several different computers during a day, so specs are irrelevant.
Back
Top