Tech Support Forum banner
Status
Not open for further replies.
1 - 8 of 8 Posts

· Registered
Joined
·
81 Posts
Discussion Starter · #1 ·
Hey guys I recently bought a new system and am having some bluescreen errors specifically when the computer is sleeping or coming out of sleep.

· OS -Windows 7
· x64
· Windows 7
· OEM Version
· Brand New (except CD drive and Case)
· 1 week

· i7 3770k
· GTX 670
· Asus P8Z77-V
· Corsair TX850
 

Attachments

· TSF - Enthusiast
Joined
·
15,333 Posts
Re: BSOD again....

Hello,

The one dump file loaded indicates a possible problem with the NIC driver.

Please check the ASUS Support site for an updated driver.

Code:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Machine Name:
Kernel base = 0xfffff800`02c4a000 PsLoadedModuleList = 0xfffff800`02e8e670
Debug session time: Fri Jan 18 01:13:47.029 2013 (UTC - 5:00)
System Uptime: 0 days 6:20:49.841
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {20, fffffa80089935c0, fffffa80089936e0, 4120003}

*** 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+1fb23 )

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

0: 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: fffffa80089935c0, The pool entry we were looking for within the page.
Arg3: fffffa80089936e0, The next pool entry.
Arg4: 0000000004120003, (reserved)

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


BUGCHECK_STR:  0x19_20

POOL_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ef8100
GetUlongFromAddress: unable to read from fffff80002ef81c0
 fffffa80089935c0 Nonpaged pool

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002df3cae to fffff80002cc8fc0

STACK_TEXT:  
fffff880`035e0e98 fffff800`02df3cae : 00000000`00000019 00000000`00000020 fffffa80`089935c0 fffffa80`089936e0 : nt!KeBugCheckEx
fffff880`035e0ea0 fffff880`01708845 : 00000000`00000000 fffffa80`092ff900 fffff880`51314549 fffff880`01701bc4 : nt!ExDeferredFreePool+0x12da
fffff880`035e0f50 fffff880`05589b23 : 00000000`00000000 fffff880`0177b5ff fffffa80`09132d70 fffffa80`07ce4b00 : ndis!NdisFreeMemory+0x15
fffff880`035e0f80 00000000`00000000 : fffff880`0177b5ff fffffa80`09132d70 fffffa80`07ce4b00 00000000`00000000 : e1c62x64+0x1fb23


STACK_COMMAND:  kb

FOLLOWUP_IP: 
e1c62x64+1fb23
fffff880`05589b23 ??              ???

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  e1c62x64+1fb23

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: e1c62x64

IMAGE_NAME:  e1c62x64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4f62ba28

FAILURE_BUCKET_ID:  X64_0x19_20_e1c62x64+1fb23

BUCKET_ID:  X64_0x19_20_e1c62x64+1fb23
 

· Registered
Joined
·
2 Posts
Re: BSOD again....

I updated the driver to the most recent version available on Intel's website, but still got a BSOD this morning with the same message.

"The driver is attempting to access memory beyond the end of the allocation"
e1c62x64.sys

What would be my next step here.
(Posting from a different account, Same guy though E-mail/password issues)
 

· Registered
Joined
·
3,037 Posts
1 - 8 of 8 Posts
Status
Not open for further replies.
Top