Windows 7: Blue screens

alee · 19 Oct 2010

I've got an HP dv6t quad edition that I got in December 2009. It's been working very well, but occasionally it will either freeze (display still on, but nothing responsive), or spontaneously restart, or spontaneously shut down. It sometimes hangs when going into standby, also - it will do everything as if it's going into standby but won't power down, and it will be non-responsive.

I'm running the factory-installed Windows 7 Home Premium 64-bit.

I managed to look at the .dmp file from today's blue-screen - I returned home to find my computer off; it shut down by itself. I've got the results below, but I don't know how to interpret them. Full collection info is attached too. Thanks! It would be great not to be constantly wondering when the next crash or BSOD will come.

--

Quote:

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

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa8004acfa20, fffff80000b9c518, fffffa8009477e10}

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 time
Arg2: fffffa8004acfa20, Physical Device Object of the stack
Arg3: fffff80000b9c518, Functional Device Object of the stack
Arg4: fffffa8009477e10, The blocked IRP

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

DRVPOWERSTATE_SUBCODE: 3

IMAGE_NAME: pci.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc117

MODULE_NAME: pci

FAULTING_MODULE: fffff88000e00000 pci

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

STACK_TEXT:
fffff800`00b9c4c8 fffff800`03534273 : 00000000`0000009f 00000000`00000003 fffffa80`04acfa20 fffff800`00b9c518 : nt!KeBugCheckEx
fffff800`00b9c4d0 fffff800`034d129e : fffff800`00b9c600 fffff800`00b9c600 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x292b0
fffff800`00b9c570 fffff800`034d0dd6 : fffff800`03675700 00000000`00d3b5d7 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5e0 fffff800`034d14be : 000001f7`f3ce00e0 fffff800`00b9cc58 00000000`00d3b5d7 fffff800`03643d68 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`034d0cb7 : 0000004e`8bbca0c1 0000004e`00d3b5d7 0000004e`8bbca027 00000000`000000d7 : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`034cdeea : fffff800`0363fe80 fffff800`0364dc40 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a

STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: X64_0x9F_3_NETw5s64_IMAGE_pci.sys

BUCKET_ID: X64_0x9F_3_NETw5s64_IMAGE_pci.sys

Followup: MachineOwner

0: kd> lmvm pci
start end module name
fffff880`00e00000 fffff880`00e33000 pci (pdb symbols) c:\portables\symcache\pci.pdb\F98D68109228430DADC2FD033EBF5C471\pci.pdb
Loaded symbol image file: pci.sys
Mapped memory image file: c:\portables\symcache\pci.sys\4A5BC11733000\pci.sys
Image path: \SystemRoot\system32\DRIVERS\pci.sys
Image name: pci.sys
Timestamp: Mon Jul 13 18:19:51 2009 (4A5BC117)
CheckSum: 0002E579
ImageSize: 00033000
File version: 6.1.7600.16385
Product version: 6.1.7600.16385
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 2.0 Dll
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: pci.sys
OriginalFilename: pci.sys
ProductVersion: 6.1.7600.16385
FileVersion: 6.1.7600.16385 (win7_rtm.090713-1255)
FileDescription: NT Plug and Play PCI Enumerator
LegalCopyright: © Microsoft Corporation. All rights reserved.

usasma · 21 Oct 2010

Quote:

FAILURE_BUCKET_ID: X64_0x9F_3_NETw5s64_IMAGE_pci.sys

Looks like your Intel WiFi driver (NETw5s64.sys).

Please:
- download a fresh copy of the driver from the Intel Download Center ( http://downloadcenter.intel.com )
- uninstall the current driver/software
- install the freshly downloaded driver
- monitor for further BSOD's

These BSOD's appear in the MSINFO32 report:

Quote:

8/16/2010 1:33 PM Windows Error Reporting Fault bucket X64_0x116_TdrBCR:2_Tdr:2_IMAGE_nvlddmkm.sys

6/9/2010 1:02 PM Windows Error Reporting Fault bucket X64_0x116_TdrBCR:2_Tdr:2_IMAGE_nvlddmkm.sys

8/16/2010 1:35 PM Windows Error Reporting Fault bucket X64_0x117_Tdr:2_IMAGE_nvlddmkm.sys

10/17/2010 1:20 AM Windows Error Reporting Fault bucket X64_0x9087_iaStor+4aa7b

8/6/2010 1:46 AM Windows Error Reporting Fault bucket X64_0x9F_3_SETPOWER_IMAGE_NETw5s64.sys

8/16/2010 1:36 PM Windows Error Reporting Fault bucket X64_0x9F_3_SETPOWER_IMAGE_NETw5s64.sys

10/19/2010 6:36 PM Windows Error Reporting Fault bucket X64_0x9F_3_SETPOWER_IMAGE_NETw5s64.sys

8/16/2010 1:33 PM Windows Error Reporting Fault bucket X64_0xA_nt!MiResolveMappedFileFault+8b

12/23/2009 4:50 PM Windows Error Reporting Fault bucket X64_0xA_nt!MiResolveMappedFileFault+8b

They present a series of errors that may mean that you have a hardware problem (numerous different BSOD errors normally mean a hardware issue is present). We'll try and fix the most recent errors first and will see if this fixes things. Since it's nearing the one year mark, you may want to have it checked at the service center for hardware issues before your warranty expires.

If the BSOD's continue after updating the WiFi drivers, please post back with the dump files and we'll see what else we can find.

BSOD BUGCHECK SUMMARY

Code:


Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Oct 19 09:26:13.179 2010 (UTC - 4:00)
System Uptime: 2 days 12:07:25.891
Probably caused by : pci.sys
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
Bugcheck code 0000009F
Arguments 00000000`00000003 fffffa80`04acfa20 fffff800`00b9c518 fffffa80`09477e10
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Oct 16 21:17:40.386 2010 (UTC - 4:00)
System Uptime: 0 days 20:35:23.588
*** WARNING: Unable to verify timestamp for iaStor.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStor.sys
Probably caused by : iaStor.sys ( iaStor+4aa7b )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x9087
PROCESS_NAME:  IAANTmon.exe
Bugcheck code 00009087
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Aug  5 21:06:29.426 2010 (UTC - 4:00)
System Uptime: 3 days 1:27:08.628
Probably caused by : pci.sys
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
Bugcheck code 0000009F
Arguments 00000000`00000003 fffffa80`04acf060 fffff800`00b9c518 fffffa80`04225230
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Jun  9 08:50:20.401 2010 (UTC - 4:00)
System Uptime: 1 days 8:04:19.603
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+10d230 )
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
Bugcheck code 00000116
Arguments fffffa80`05a95010 fffff880`10766230 00000000`00000000 00000000`00000002
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Dec 23 12:48:40.177 2009 (UTC - 4:00)
System Uptime: 0 days 15:29:55.379
Probably caused by : memory_corruption ( nt!MiResolveMappedFileFault+8b )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  CLMLSvc.exe
Bugcheck code 0000000A
Arguments fffffa80`4de05990 00000000`00000002 00000000`00000000 fffff800`0307beeb
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

alee · 21 Oct 2010

Thanks so much for your help! I just updated the WiFi drivers to the latest. We'll see if that helps. It's both good and bad that the BSODs aren't happening so often, and so I won't really know if it's working/helping for some time.

I noticed the other older BSODs are from nvlddmkm.sys which is related to nVidia. Should I update my graphics card drivers too?

usasma · 22 Oct 2010

If you're comfortable updating these drivers - yes update your video drivers
Also update your chipset/storage drivers.

These were the drivers involved in the crash. If they're updated and the system still crashes, then we'll have to presume that it's a hardware error.

Windows 7: Blue screens

Blue screens problems?