BSOD After Resuming From Sleep/Hibernation, Error

Perform a clean install of your SynTP.sys Synaptic Touch Pad Driver Driver Reference Table - SynTP.sys

   Tip

How to clean left over drivers
Sometimes drivers remain, not completely uninstalled. Follow this tutorial for complete removal of drivers of the particular program: How to Clean Left Over Driver Files with Driver Sweeper

Click on the Start
► Control Panel
► Programs
► Uninstall a program
► Uninstall everything related to the software.

Delete remnants of its drivers/older drivers using Driver Sweeper

Code:

*******************************************************************************
*                                                                             *
*                        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: fffffa8004ee5e40, Physical Device Object of the stack
Arg3: fffff800045b1518, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: fffffa8008b61c60, The blocked IRP

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

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

DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  ACPI.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce79294

MODULE_NAME: ACPI

FAULTING_MODULE: fffff88000f28000 ACPI

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

STACK_TEXT:  
fffff800`045b14c8 fffff800`02f448c2 : 00000000`0000009f 00000000`00000003 fffffa80`04ee5e40 fffff800`045b1518 : nt!KeBugCheckEx
fffff800`045b14d0 fffff800`02edf84c : fffff800`045b1618 fffff800`045b1618 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x33af0
fffff800`045b1570 fffff800`02edf6e6 : fffffa80`08c49658 fffffa80`08c49658 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`045b15e0 fffff800`02edf5ce : 000001c7`5e840f61 fffff800`045b1c58 00000000`00bf4cf0 fffff800`03054088 : nt!KiProcessExpiredTimerList+0xc6
fffff800`045b1c30 fffff800`02edf3b7 : 0000006a`6f39d2c3 0000006a`00bf4cf0 0000006a`6f39d2bc 00000000`000000f0 : nt!KiTimerExpiration+0x1be
fffff800`045b1cd0 fffff800`02ecc90a : fffff800`0304fe80 fffff800`0305dcc0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`045b1d80 00000000`00000000 : fffff800`045b2000 fffff800`045ac000 fffff800`045b1d40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_3_SynTP_IMAGE_ACPI.sys

BUCKET_ID:  X64_0x9F_3_SynTP_IMAGE_ACPI.sys

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

Start up
Keep less stuff at the start-up. Only anti-virus, this helps avoid driver conflicts and improves time to log in to windows.

Troubleshoot a Problem by Performing a Clean Startup in Windows 7 or Vista
How to Change, Add, or Remove Startup Programs in Windows 7

SFC /scannow to check windows for corruption:

How to Repair Windows 7 System Files with System File Checker
1. Click Start
2. In the search box, type Command Prompt
3. In the list that appears, right-click on cmd.exe and choose Run as administrator
4. In the command window that opens, type sfc /scannow and hit enter.

Daemon Tools/Alcohol %

Code:

Start Menu\Programs\DAEMON Tools Pro	Public:Start Menu\Programs\DAEMON Tools Pro	Public

Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Win7 systems (mostly due to the sptd.sys driver, although we have seen dtsoftbus01.sys blamed on several occasions). Please uninstall the program, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration): DuplexSecure - FAQ

As an alternative, many people recommend the use of Total Mounter or Magic ISO

Basic checks: Please run these tests and report back the results

1. SFC /scannow to check windows for corruption - SFC /SCANNOW Command - System File Checker
2. Disk check for errors on the hard drive - How to Run Disk Check in Windows 7
3. Troubleshoot applications by a clean boot - Troubleshoot Application Conflicts by Performing a Clean Startup
4. Memtest86+ paying close attention to part 3 - RAM - Test with Memtest86+
5. Hard drive test from HDD mfg website - Hard Drive Diagnostic Procedure

You need to upload the dumps.

No dump files..

Configure dumps

First, we want to make sure the computer is saving your dump files. Go to Control Panel -> System -> Advanced System Settings -> Startup and Recovery [Settings] Make sure that "Write Debugging Information" is set to Small Memory Dump (256kb) if it is not already.

Dump Files - Configure Windows to Create on BSOD

Next, make sure that the folder C:\Windows\Minidump exists. If not, create it (allow permission if asked). Make sure any dumps you want to analyze, whether yours or others', are in this folder. You can ZIP/RAR the files and send them to someone else to analyze as well.

Still no dumps. At this point I would suggest you do a Clean Reinstall - Factory OEM Windows 7 and tell us if you continue getting BSOD's.