Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Windows › E-Peen, would appreciate your help with a Bluscreen
New Posts  All Forums:Forum Nav:

E-Peen, would appreciate your help with a Bluscreen

post #1 of 6
Thread Starter 
Hey,

Every time I try to install windows updates after a clean install of win7 64bit I get a blue screen on the set of updates after the service pack. I have attached the minidump and would appreciate it if you could analyze it and tell me what's causing this BSOD.

Thanks! 042812-7706-01.zip 24k .zip file
post #2 of 6
Driver issue, caused by e1c62x64.sys driver. http://systemexplorer.net/db/e1c62x64.sys.html
Fräulein
(8 items)
 
  
CPUGraphicsRAMHard Drive
Intel Core i5 3337U AMD Radeon HD 7670M Hynix 4GB DDR3 1600MHz Samsung 830 128GB 
Hard DriveOSMouseMouse Pad
Seagate Momentus Thin 500GB 5400RPM Windows 8 Pro 64-bit Steelseries Sensei Fnatic Edition Razer Destructor 
  hide details  
Reply
Fräulein
(8 items)
 
  
CPUGraphicsRAMHard Drive
Intel Core i5 3337U AMD Radeon HD 7670M Hynix 4GB DDR3 1600MHz Samsung 830 128GB 
Hard DriveOSMouseMouse Pad
Seagate Momentus Thin 500GB 5400RPM Windows 8 Pro 64-bit Steelseries Sensei Fnatic Edition Razer Destructor 
  hide details  
Reply
post #3 of 6
As strych has said, the culprit is e1c62x64 (Intel(R) 82579V Gigabit Network Connection driver). Download the latest network drivers here, and then uninstall and reinstall the latest drivers you've downloaded.

Dump for reference:
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\BSOD\Downloads\042812-7706-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\MS Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0xfffff800`02e4e000 PsLoadedModuleList = 0xfffff800`03092650
Debug session time: Sat Apr 28 16:51:48.771 2012 (UTC - 4:00)
System Uptime: 0 days 0:02:57.473
Loading Kernel Symbols
...............................................................
................................................................
.............
Loading User Symbols
Loading unloaded module list
......................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {20, fffffa800ace5190, fffffa800ace52b0, 4120009}

Unable to load image \SystemRoot\system32\DRIVERS\e1c62x64.sys, Win32 error 0n2
*** 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: fffffa800ace5190, The pool entry we were looking for within the page.
Arg3: fffffa800ace52b0, The next pool entry.
Arg4: 0000000004120009, (reserved)

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


BUGCHECK_STR:  0x19_20

POOL_ADDRESS: GetPointerFromAddress: unable to read from fffff800030fc100
 fffffa800ace5190 

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002ff7cae to fffff80002ecac80

STACK_TEXT:  
fffff880`0375aac8 fffff800`02ff7cae : 00000000`00000019 00000000`00000020 fffffa80`0ace5190 fffffa80`0ace52b0 : nt!KeBugCheckEx
fffff880`0375aad0 fffff880`018e3195 : 00000000`00000000 fffff880`018dd6ae fffffa80`51314549 00000000`00000000 : nt!ExDeferredFreePool+0x12da
fffff880`0375ab80 fffff880`0f41fb23 : fffffa80`0a6125b0 fffff880`019575ff 00000000`00000000 fffffa80`0a6012e0 : ndis!NdisFreeMemory+0x15
fffff880`0375abb0 fffffa80`0a6125b0 : fffff880`019575ff 00000000`00000000 fffffa80`0a6012e0 00000000`00000000 : e1c62x64+0x1fb23
fffff880`0375abb8 fffff880`019575ff : 00000000`00000000 fffffa80`0a6012e0 00000000`00000000 00000000`00000000 : 0xfffffa80`0a6125b0
fffff880`0375abc0 00000000`fd01010b : fffffa80`0a468000 fffff880`0f43297f 00000000`00000000 fffff880`018dd8ef : ndis!ndisMiniportPreRemoveWOLPattern+0xf
fffff880`0375abf0 fffffa80`0a468000 : fffff880`0f43297f 00000000`00000000 fffff880`018dd8ef 00000000`00000000 : 0xfd01010b
fffff880`0375abf8 fffff880`0f43297f : 00000000`00000000 fffff880`018dd8ef 00000000`00000000 fffffa80`0a612d20 : 0xfffffa80`0a468000
fffff880`0375ac00 00000000`00000000 : fffff880`018dd8ef 00000000`00000000 fffffa80`0a612d20 00000000`00000011 : e1c62x64+0x3297f


STACK_COMMAND:  kb

FOLLOWUP_IP: 
e1c62x64+1fb23
fffff880`0f41fb23 ??              ???

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

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

post #4 of 6
Thread Starter 
Alright guys, thanks for the feedback. I was using the latest network driver when this happened. I installed an older driver that is on Asus' page and it didn't BSOD. I think it's a problem with the Energy efficient ethernet feature as I had that disabled many times in the past and there were no BSODs. I'll keep getting the latest driver and hopefully Intel fixes it (i'll make sure to report it to them). And the Intel drivers page isn't working at the moment so I can't check if there is a new driver available for the NIC card.
post #5 of 6
also when you update ms stuff let window decide(yes they do)once the uppdater stop selecting automaticly stuff to download(after each restart)then you can click on the rest!
post #6 of 6
Thread Starter 
It was definitely the Energy Efficient Ethernet feature on the NIC that was causing the BSOD. I installed windows twice to test this and when the feature is enabled it BSODs with it disabled, it doesn't BSOD. So at least I know what's causing the problem. Time to report it to Intel.

Anyway, thanks for your help guys! I'll refer Intel to this thread.
Edited by mrwalker - 4/29/12 at 11:35am
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Windows
Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Windows › E-Peen, would appreciate your help with a Bluscreen