Intel 82579 Ethernet Controller And Bugcheck 9F Crash

[idata]

I'm getting a crash when putting the computer to sleep. I'm using the latest drivers (16.2). Anyone else having this poblem or know of a solution? System details and memory dump details below:

Asus P8P67 Deluxe (Bios 1503)

Intel i7 2600k

Windows 7 x64 SP1

--

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64

Copyright (c) Microsoft Corporation. All rights reserved.Loading Dump File [C:\Windows\Minidump\051911-17721-01.dmp]Mini Kernel Dump File: Only registers and stack trace are available

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?00000000`00000000?

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`041b13c0?WARNING: Whitespace at end of path elementSymbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631Machine Name:Kernel base = 0xfffff800`02a1d000 PsLoadedModuleList = 0xfffff800`02c62650Debug session time: Thu May 19 08:00:12.897 2011 (UTC - 5:00)System Uptime: 6 days 16:01:36.553Loading Kernel Symbols.........................................................................................................................................................................Loading User SymbolsLoading unloaded module list.......................................******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa8006cbe060, fffff800041b13d8, fffffa8007160910}

Probably caused by : pci.sys

Followup: MachineOwner

---------

0: kd> !analyze -v

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

DRIVER_POWER_STATE_FAILURE (9f)

A driver is causing an inconsistent power state.Arguments:Arg1: 0000000000000003, A device object has been blocking an Irp for too long a timeArg2: fffffa8006cbe060, Physical Device Object of the stackArg3: fffff800041b13d8, Functional Device Object of the stackArg4: fffffa8007160910, The blocked IRP

Debugging Details:

------------------OVERLAPPED_MODULE: Address regions for 'hiber_iaStor' and 'hiber_iaStor' overlap

DRVPOWERSTATE_SUBCODE: 3

IMAGE_NAME: pci.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7928f

MODULE_NAME: pci

FAULTING_MODULE: fffff88000e0a000 pci

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

STACK_TEXT:

fffff800`041b1388 fffff800`02b099c2 : 00000000`0000009f 00000000`00000003 fffffa80`06cbe060 fffff800`041b13d8 : nt!KeBugCheckExfffff800`041b1390 fffff800`02aa8652 : fffff800`041b14c0 fffff800`041b14c0 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x34a90fffff800`041b1430 fffff800`02aa84f6 : fffff800`02c44f00 00000000`02337e05 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66fffff800`041b14a0 fffff800`02aa83de : 0000053d`544dea48 fffff800`041b1b18 00000000`02337e05 fffff800`02c12328 : nt!KiProcessExpiredTimerList+0xc6fffff800`041b1af0 fffff800`02aa81c7 : 000001be`d04b10c1 000001be`02337e05 000001be`d04b1039 00000000`00000005 : nt!KiTimerExpiration+0x1befffff800`041b1b90 fffff800`02a94a2a : fffff800`02c0fe80 fffff800`02c1dcc0 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277fffff800`041b1c40 00000000`00000000 : fffff800`041b2000 fffff800`041ac000 fffff800`041b1c00 00000000`00000000 : nt!KiIdleLoop+0x5aSTACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: X64_0x9F_3_e1c62x64_IMAGE_pci.sys

BUCKET_ID: X64_0x9F_3_e1c62x64_IMAGE_pci.sys

Followup: MachineOwner

---------

[Gaurav_E_Intel]

It sounds like your system is not entering hibernate properly. It could be calling the driver to shutdown, but the driver may also be expecting the OS to call its sleep routine. There are a few tests to try:

1. Update the driver to 16.3...located here.. http://downloadcenter.intel.com/detail_desc.aspx?agr=Y&DwnldID=18713 http://downloadcenter.intel.com/detail_desc.aspx?agr=Y&DwnldID=18713

2. Disable the LAN device and try to sleep.

3a. Setup your computer to disable hybrid sleep. You can follow this guide...http://maximumpcguides.com/windows-7/turn-off-hybrid-sleep-in-windows-7/ http://maximumpcguides.com/windows-7/turn-off-hybrid-sleep-in-windows-7/

3b. Then see if both Standby and Hibernate cause your system to BSOD, or just one of them.

4. Repair/Re-install your OS. Your pci.sys driver might be corrupted causing the OS to stall.