BSOD windows seven wake from sleep

Welcome To SevenForums.

McAfee is a frequent cause of BSOD-s (specially in the situation you describe). Consider uninstalling it with the McAfee Removal Tool and replace with Microsoft Security Essentials (To test)

• How to uninstall or reinstall supported McAfee products using the Consumer Products Removal tool (MCPR)
  
  • McAfee Removal Tool - McAfee Uninstaller

Microsoft Security Essentials.

Recommended from a strict BSOD perspective, compatibility & stability compared to other antiviruses/internet security software. It is free and lightweight:-

• Microsoft Security Essentials - Free Antivirus for Windows
  
  • Malwarebytes : Malwarebytes Anti-Malware removes malware including viruses, spyware, worms and trojans, plus it protects your computer
    
    • Good and Free system security combination.

   Warning

Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.

Run a full scan with both (separately) once downloaded, installed and updated.

Perform a System File Check:

1. Click on the start
2. Type CMD on Search
3. Left click and Run as Administrator
4. Type SFC /scannow

Full tutorial here:

• SFC /SCANNOW Command - System File Checker

Disk Check on your hard drive for file system errors and bad sectors on it:

• Disk Check

Reduce items at start-up. Nothing except anti-virus is required:

• Startup Programs - Change
• Troubleshoot Application Conflicts by Performing a Clean Startup

e1c62x64.sys Intel(R) 82579V Gigabit Network Connection driver which you can update from here: Driver Reference Table - e1c62x64.sys

Go to this link: Intel® Driver Update Utility. Check the system for latest updates. Download & install them one by one.

Let us know the results and further BSOD reports.

SUMMARY:

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 19, {20, fffffa800a9b61c0, fffffa800a9b62e0, 412000d}

*** WARNING: Unable to verify timestamp for e1c62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for e1c62x64.sys
Probably caused by : e1c62x64.sys ( e1c62x64+1bec2 )

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

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

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 0000000000000020, a pool block header size is corrupt.
Arg2: fffffa800a9b61c0, The pool entry we were looking for within the page.
Arg3: fffffa800a9b62e0, The next pool entry.
Arg4: 000000000412000d, (reserved)

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


BUGCHECK_STR:  0x19_20

POOL_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cca100
GetUlongFromAddress: unable to read from fffff80002cca1c0
 fffffa800a9b61c0 Nonpaged pool

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002bc5cae to fffff80002a9afc0

STACK_TEXT:  
fffff880`03570e98 fffff800`02bc5cae : 00000000`00000019 00000000`00000020 fffffa80`0a9b61c0 fffffa80`0a9b62e0 : nt!KeBugCheckEx
fffff880`03570ea0 fffff880`01654845 : 00000000`fffeffff fffffa80`0b5b7870 fffff880`51314549 fffff880`0164dbc4 : nt!ExDeferredFreePool+0x12da
fffff880`03570f50 fffff880`04775ec2 : 00000000`00000000 fffff880`016c75ff fffffa80`06d24dd0 fffffa80`08ef5110 : ndis!NdisFreeMemory+0x15
fffff880`03570f80 00000000`00000000 : fffff880`016c75ff fffffa80`06d24dd0 fffffa80`08ef5110 00000000`00000000 : e1c62x64+0x1bec2


STACK_COMMAND:  kb

FOLLOWUP_IP: 
e1c62x64+1bec2
fffff880`04775ec2 ??              ???

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  e1c62x64+1bec2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: e1c62x64

IMAGE_NAME:  e1c62x64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  50258ebf

FAILURE_BUCKET_ID:  X64_0x19_20_e1c62x64+1bec2

BUCKET_ID:  X64_0x19_20_e1c62x64+1bec2

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

3: kd> lmvm e1c62x64
start             end                 module name
fffff880`0475a000 fffff880`047d3000   e1c62x64 T (no symbols)           
    Loaded symbol image file: e1c62x64.sys
    Image path: \SystemRoot\system32\DRIVERS\e1c62x64.sys
    Image name: e1c62x64.sys
    Timestamp:        Sat Aug 11 04:44:15 2012 (50258EBF)
    CheckSum:         000829CE
    ImageSize:        00079000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Any updates?

OK, give it another week.

If you're unable to recreate the BSOD it's likely solved.

   Tip

• If your problem is solved please use the Mark this thread as solved link at the top of your thread or down on the left corner