Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.

Windows 7: BSOD - IDSvia64.sys

12 Apr 2012   #11

Windows 7 Home Premium 64 Bit

Loading Dump File [D:\Kingston\BSODDmpFiles\RockStar1965\Windows_NT6_BSOD_jcgriff2\041112-13572-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*
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`03214000 PsLoadedModuleList = 0xfffff800`03458650
Debug session time: Wed Apr 11 22:20:12.911 2012 (UTC - 6:00)
System Uptime: 0 days 1:36:15.739
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

Use !analyze -v to get detailed debugging information.

BugCheck 19, {3, fffffa801dfc6260, fffffa801dfc6260, ffffffffffffffff}

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 : Pool_Corruption ( nt!ExDeferredFreePool+cbb )

Followup: Pool_corruption

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

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.
Arg1: 0000000000000003, the pool freelist is corrupt.
Arg2: fffffa801dfc6260, the pool entry being checked.
Arg3: fffffa801dfc6260, the read back flink freelist value (should be the same as 2).
Arg4: ffffffffffffffff, the read back blink freelist value (should be the same as 2).

Debugging Details:






LAST_CONTROL_TRANSFER:  from fffff800033bd70f to fffff80003290c80

fffff880`0e06c698 fffff800`033bd70f : 00000000`00000019 00000000`00000003 fffffa80`1dfc6260 fffffa80`1dfc6260 : nt!KeBugCheckEx
fffff880`0e06c6a0 fffff800`033bf1a1 : 00000000`00000000 fffffa80`1e108870 00000000`00000000 fffffa80`1930e1a0 : nt!ExDeferredFreePool+0xcbb
fffff880`0e06c730 fffff880`01c208a7 : fffffa80`19c08480 00000000`0000005b fffffa80`6264444e fffff880`0fa2c569 : nt!ExFreePoolWithTag+0x411
fffff880`0e06c7e0 fffff880`0fa29c91 : 00000000`00000801 fffffa80`19ca6a30 00000000`0000004e fffff880`0fa2c723 : ndis!NdisMFreeNetBufferSGList+0xa7
fffff880`0e06c820 00000000`00000801 : fffffa80`19ca6a30 00000000`0000004e fffff880`0fa2c723 fffffa80`1deb12a0 : e1c62x64+0x29c91
fffff880`0e06c828 fffffa80`19ca6a30 : 00000000`0000004e fffff880`0fa2c723 fffffa80`1deb12a0 fffffa80`19d43d50 : 0x801
fffff880`0e06c830 00000000`0000004e : fffff880`0fa2c723 fffffa80`1deb12a0 fffffa80`19d43d50 fffffa80`0000001b : 0xfffffa80`19ca6a30
fffff880`0e06c838 fffff880`0fa2c723 : fffffa80`1deb12a0 fffffa80`19d43d50 fffffa80`0000001b 00000000`00000003 : 0x4e
fffff880`0e06c840 fffffa80`1deb12a0 : fffffa80`19d43d50 fffffa80`0000001b 00000000`00000003 fffffa80`00000000 : e1c62x64+0x2c723
fffff880`0e06c848 fffffa80`19d43d50 : fffffa80`0000001b 00000000`00000003 fffffa80`00000000 00000000`00000000 : 0xfffffa80`1deb12a0
fffff880`0e06c850 fffffa80`0000001b : 00000000`00000003 fffffa80`00000000 00000000`00000000 0000000a`00000001 : 0xfffffa80`19d43d50
fffff880`0e06c858 00000000`00000003 : fffffa80`00000000 00000000`00000000 0000000a`00000001 fffffa80`19bf6000 : 0xfffffa80`0000001b
fffff880`0e06c860 fffffa80`00000000 : 00000000`00000000 0000000a`00000001 fffffa80`19bf6000 00000000`00000000 : 0x3
fffff880`0e06c868 00000000`00000000 : 0000000a`00000001 fffffa80`19bf6000 00000000`00000000 00000000`00000000 : 0xfffffa80`00000000


fffff800`033bd70f cc              int     3


SYMBOL_NAME:  nt!ExDeferredFreePool+cbb

FOLLOWUP_NAME:  Pool_corruption

IMAGE_NAME:  Pool_Corruption


MODULE_NAME: Pool_Corruption

FAILURE_BUCKET_ID:  X64_0x19_3_nt!ExDeferredFreePool+cbb

BUCKET_ID:  X64_0x19_3_nt!ExDeferredFreePool+cbb

Followup: Pool_corruption
The latest crash appears to be caused by your Intel(R) 82579V Gigabit Network Connection driver. When you re-installed the old one, did you follow these steps:
  1. First, download the mfg driver. Then do the next steps.
  2. Click Start Menu
  3. Right Click My Computer/Computer
  4. Click Manage
  5. Click Device Manager from the list on the left
  6. Expand Network adapters
  7. Right click the Intel Ethernet device
  8. Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
  9. Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
  10. Restart your computer only if Windows asks you to.
  11. Install the mfg driver for the device.

  1. Login as an adminstrative user.
  2. First, download the mfg driver. Then do the next steps.
  3. Click Start Menu
  4. Click Control Panel
  5. Click Hardware and Sound
  6. Click Device Manager (the last link under Devices and Printers)
  7. Expand Network adapters
  8. Right click the Intel Ethernet device
  9. Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
  10. Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
  11. Restart your computer only if Windows asks you to.
  12. Install the mfg driver for the device.

My System SpecsSystem Spec

 BSOD - IDSvia64.sys

Thread Tools

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 13:50.
Twitter Facebook Google+