BSOD after Windows & is Hibernated/ Sleep and Unexpecetd Shutdown

My laptop suffers from BSOD after selecting Hibernate/Sleep option. The computer stays on for some time then gets switched off. After the computer switched on again the computer starts from beginning stating whether I want to safe start/ safe start with command prompt/ ..../ start windows normally. After windows starts I get an error message that There was an unexpected shutdown. This happens every time I select Hibernate/Sleep.

Need help. I often need to hibernate my work and without that option working it is difficult to find any other way.
There hasn't been any recent unusual installations. My windows is updated and I don't normally fiddle with the registry.

I am using a Sony Vaio Laptop Model Number VPCEB46FG

Post it following the Blue Screen of Death (BSOD) Posting Instructions.

Here you go .....

Code:

fffff800`00b9c680  fffff880`0106e500Unable to load image \SystemRoot\System32\Drivers\sptd.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
 sptd+0x1500

Daemon Tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known BSOD causer. Uninstall Daemon Tools at first. Then download SPTD standalone installer from Disk-Tools.com, and execute the downloaded file as guided below :

• Double click to open it.
• Click this button only:
• 
• If it is grayed out, as in the picture, there is no more SPTD in your system, and you just close the window.

And again ......

Code:

fffff800`00b9c828  fffff880`01aabcbcUnable to load image \SystemRoot\system32\drivers\iaStor.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for iaStor.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStor.sys
 iaStor+0x30cbc

Get rid of intel rapid storage. First uninstall it from Control Panel > Programs and Features. Then Uninstall the driver from device manager.

1. Right click on "my computer" icon and click "manage" on the context menu.
2. It will open the "computer management" window.
3. Select "Device Manager" in the left pane, It will list all the existing devices up.
4. Expand "IDE ATA/ATAPI controllers" by clicking on the triangle in front of it.
5. Select one Intel device item under it, right click, uninstall.
6. Continue the process for all Intel items under "IDE ATA/ATAPI controllers"
7. Now restart the computer. At restart, windows will auto configure the appropriate native system driver.

Do one more thing ... Update your Atheros AR9285 Wireless Network Adapter driver from Drivers for Atheros AR9285 and Windows 7.

Tar por lid ta close koro ..... 15 minutes por open it again. Does it BSOD still? Let us know.
-------------------------------------------------------------------------------------------

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa80035eb980, fffff80000b9c518, fffffa80095dc6d0}

Probably caused by : ntkrnlmp

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

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

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time (usually 10 minutes).
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa80035eb980, Physical Device Object of the stack
Arg3: fffff80000b9c518, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: fffffa80095dc6d0, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  ntkrnlmp

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAULTING_MODULE: fffff88004bc5000 ndiswan

DEVICE_OBJECT: fffffa80073b6050

DRIVER_OBJECT: fffffa80069278e0

IRP_ADDRESS:  fffffa80095dc6d0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

TAG_NOT_DEFINED_c000000f:  FFFFF80000BA2FB0

STACK_TEXT:  
fffff800`00b9c4c8 fffff800`0452ca23 : 00000000`0000009f 00000000`00000003 fffffa80`035eb980 fffff800`00b9c518 : nt!KeBugCheckEx
fffff800`00b9c4d0 fffff800`044caa06 : fffff800`00b9c600 fffff800`00b9c600 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x288e0
fffff800`00b9c570 fffff800`044c9cc6 : fffffa80`0865b740 fffffa80`0865b740 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5e0 fffff800`044ca8fe : 00000048`212f1bff fffff800`00b9cc58 00000000`001e4d38 fffff800`0463b988 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`044ca037 : 00000012`bd2786c2 00000012`001e4d38 00000012`bd278658 00000000`00000038 : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`044c709a : fffff800`04638e80 fffff800`04646c40 00000000`00000001 fffffa80`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

MODULE_NAME: ntkrnlmp

FAILURE_BUCKET_ID:  X64_0x9F_3_POWER_DOWN_IMAGE_ntkrnlmp

BUCKET_ID:  X64_0x9F_3_POWER_DOWN_IMAGE_ntkrnlmp

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

Arpan you know it is risky to share your personal contracts in an open forum this way. It may yield some fatal results.

Do you have windows installation disc? Follow it:Startup Repair for three separate times, with restarts after every single run.
Startup Repair: Run three separate times.

If still nothing changed, Troubleshooting Windows 7 Failure to Start

One thing you should be confirmed that Hibernation or anything has nothing to do with the bootloader. What you replied makes it sense that you uninstalled Daemon tools and SPTD ..... it cannot do such a damage that you are saying, and uninstalling IRST will not do any further damage.

In windows 7, the bootloader entries are stored in a separate partition (a 100 MB hidden partition called system reserved) .... that is totally disjoint with the C drive where the other programs are installed. So it is not a fact that the damage caused by what I have suggested and what you have done. Somehow you have got the bootloader corrupted, and it is to be fixed.

Follow the links I supplied .... the bootloader issue will be recovered.

Ask for any more help..... but dont supply your personal contracts.