BSOD after "wake up"

Hello and welcome circler mate looking at those files I would do these straight away as a matter of interest why did you run GMER?


http://www.superantispyware.com/

http://www.malwarebytes.org/products/malwarebytes_free/
http://www.bleepingcomputer.com/download/adwcleaner/

download from bleeping computer and this Free Malware Removal Tools
go down to the TDSS Killer and run it too delete any rubbish that comes up

After you have done those run these SFC /SCANNOW Command - System File Checker
and
Disk Check

Hi circler666.

Install Service pack 1 and all other windows updates. Otherwise the system will remain vulnerable to threats.

Code:

Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503

Learn how to install Windows 7 Service Pack 1 (SP1)
Service Pack Center - Microsoft Windows

The crash dump is not producing enough evidence to blame something to cause the BSOD, but you should try these, as least for test.

• Marvell Yukon 88E8057 PCI-E Gigabit Ethernet Controller: Update from Marvell - Support - Driver Downloads
• Atheros AR9287 Wireless Network Adapter: Update from Drivers for Atheros AR9287 and Windows 7
• NetLimiter: Uninstall
• TAP-Win32 Adapter V9: uninstall OpenVPN
• VMWare: Update version

It seems that you have experimented a lot with network connections.

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.

You have 31 programs at startup . Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept then restart.

Let us know the results.

Edit: ICit2lol did it faster :). Please follow him first. If still issues are present there, continue with the further suggestions.
__________________________________________________________________________

Code:

Loading User Symbols
Missing image name, possible paged-out or corrupt data.
Loading unloaded module list
..Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
..Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
...Missing image name, possible paged-out or corrupt data.
....Missing image name, possible paged-out or corrupt data.
..Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
..Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
..Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
..Missing image name, possible paged-out or corrupt data.
..
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa80069f7c20, fffff80000b9c518, fffffa8009ca4550}

*** WARNING: Unable to verify timestamp for ACPI.sys
*** ERROR: Module load completed but symbols could not be loaded for ACPI.sys
Probably caused by : ACPI.sys

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

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


DRVPOWERSTATE_SUBCODE:  3

DEVICE_OBJECT: fffffa80069f7c20

DRIVER_OBJECT: fffffa80069c7b00

IMAGE_NAME:  ACPI.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: ACPI

FAULTING_MODULE: fffff88000f87000 ACPI

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x9F

CURRENT_IRQL:  2

TAG_NOT_DEFINED_c000000f:  FFFFF80000BA2FB0

LAST_CONTROL_TRANSFER:  from fffff80003af31d3 to fffff80003a845c0

STACK_TEXT:  
fffff800`00b9c4c8 fffff800`03af31d3 : 00000000`0000009f 00000000`00000003 fffffa80`069f7c20 fffff800`00b9c518 : nt!KeBugCheckEx
fffff800`00b9c4d0 fffff800`03a9012e : fffff800`00b9c600 fffff800`00b9c600 00000000`00000002 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x29270
fffff800`00b9c570 fffff800`03a8fc76 : fffffa80`0cc401d0 00000000`0016203a 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5e0 fffff800`03a9034e : 00000034`ab0cf875 fffff800`00b9cc58 00000000`0016203a fffff800`03c019c8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`03a8fb57 : 00000009`93c561c2 00000009`0016203a 00000009`93c561fe 00000000`0000003a : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`03a8cd8a : fffff800`03bfee80 fffff800`03c0cc40 00000000`00000001 fffff880`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

FAILURE_BUCKET_ID:  X64_0x9F_3_IMAGE_ACPI.sys

BUCKET_ID:  X64_0x9F_3_IMAGE_ACPI.sys

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