BSOD all the time!

[necrodragon]

I used to get the BSOD all the time randomly and then I installed Bluescreenview hoping to see what caused the problem. All the dump files had ntoskrnl.exe listed and so I did a system recovery hoping to fix the problem but it crashed again today. I have uploaded today's crash file also with this post.

 

[zigzag3143]

I used to get the BSOD all the time randomly and then I installed Bluescreenview hoping to see what caused the problem. All the dump files had ntoskrnl.exe listed and so I did a system recovery hoping to fix the problem but it crashed again today. I have uploaded today's crash file also with this post.

related to your NETw5s64.sys network driver re-install using most recent. You also have 5 year old drivers that need updating.

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\060411-22495-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00b9c500?
Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Machine Name:
Kernel base = 0xfffff800`0324b000 PsLoadedModuleList = 0xfffff800`03488e50
Debug session time: Sat Jun  4 22:09:00.612 2011 (GMT-4)
System Uptime: 0 days 11:05:39.220
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...........
Loading User Symbols
Loading unloaded module list
......................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa8004902060, fffff80000b9c518, fffffa800b5d55a0}

*** WARNING: Unable to verify timestamp for NETw5s64.sys
*** ERROR: Module load completed but symbols could not be loaded for NETw5s64.sys
Probably caused by : NETw5s64.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: fffffa8004902060, Physical Device Object of the stack
Arg3: fffff80000b9c518, Functional Device Object of the stack
Arg4: fffffa800b5d55a0, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IRP_ADDRESS:  fffffa800b5d55a0

DEVICE_OBJECT: fffffa8005d36050

DRIVER_OBJECT: fffffa8005c24800

IMAGE_NAME:  NETw5s64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4b4df6b9

MODULE_NAME: NETw5s64

FAULTING_MODULE: fffff88006093000 NETw5s64

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff8000332a383 to fffff800032bb700

STACK_TEXT:  
fffff800`00b9c4c8 fffff800`0332a383 : 00000000`0000009f 00000000`00000003 fffffa80`04902060 fffff800`00b9c518 : nt!KeBugCheckEx
fffff800`00b9c4d0 fffff800`032c72ae : fffff800`00b9c600 fffff800`00b9c600 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x29270
fffff800`00b9c570 fffff800`032c6de6 : fffffa80`07c4c168 fffffa80`07c4c168 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5e0 fffff800`032c74ce : 0000005c`fda15941 fffff800`00b9cc58 00000000`002710be fffff800`03439a48 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`032c6cc7 : 00000013`53b20ec2 00000013`002710be 00000013`53b20ef4 00000000`000000be : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`032c3eea : fffff800`03435e80 fffff800`03443c40 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_IMAGE_NETw5s64.sys

BUCKET_ID:  X64_0x9F_IMAGE_NETw5s64.sys

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

Old drivers

iirsp.sys    12/13/2005 5:47:54 PM        fffff880`01742000    fffff880`01753000    0x00011000    0x439f418a                        
nfrd960.sys    6/6/2006 5:11:48 PM        fffff880`016a4000    fffff880`016b4000    0x00010000    0x4485ef94                        
adpu320.sys    2/27/2007 8:04:15 PM        fffff880`01200000    fffff880`0122f000    0x0002f000    0x45e4c6ff                        
adpahci.sys    5/1/2007 1:30:09 PM        fffff880`0118e000    fffff880`011e4000    0x00056000    0x46377921                        
arc.sys    5/24/2007 5:27:55 PM        fffff880`011e4000    fffff880`011fd000    0x00019000    0x4656035b                        
SiSRaid2.sys    9/24/2008 2:28:20 PM        fffff880`01b4e000    fffff880`01b5c000    0x0000e000    0x48da86c4                        
sisraid4.sys    10/1/2008 5:56:04 PM        fffff880`01b5c000    fffff880`01b74000    0x00018000    0x48e3f1f4                        
adp94xx.sys    12/5/2008 7:54:42 PM        fffff880`0135c000    fffff880`013d7000    0x0007b000    0x4939bf42                        
lsi_fc.sys    12/9/2008 6:46:09 PM        fffff880`01753000    fffff880`01772000    0x0001f000    0x493ef531                        
arcsas.sys    1/14/2009 3:27:37 PM        fffff880`00e72000    fffff880`00e8d000    0x0001b000    0x496e3ca9                        
ql2300.sys    1/22/2009 7:05:06 PM        fffff880`01859000    fffff880`019fd000    0x001a4000    0x4978fba2                        
vsmraid.sys    1/30/2009 9:18:57 PM        fffff880`01b7e000    fffff880`01ba8000    0x0002a000    0x4983a701                        
elxstor.sys    2/3/2009 6:52:11 PM        fffff880`016bb000    fffff880`01742000    0x00087000    0x4988ca9b                        
stexstor.sys    2/17/2009 7:03:36 PM        fffff880`01b74000    fffff880`01b7e000    0x0000a000    0x499b4248                        
hamachi.sys    2/19/2009 6:36:41 AM        fffff880`04d4f000    fffff880`04d5a000    0x0000b000    0x499d3639                        
amdsbs.sys    3/20/2009 2:36:03 PM        fffff880`01000000    fffff880`01047000    0x00047000    0x49c3e213                        
iaStorV.sys    4/8/2009 12:57:17 PM        fffff880`0123e000    fffff880`0135c000    0x0011e000    0x49dcd76d                        
lsi_scsi.sys    4/16/2009 6:13:50 PM        fffff880`01785000    fffff880`017a4000    0x0001f000    0x49e7ad9e                        
HpqKbFiltr.sys    4/29/2009 9:48:30 AM        fffff880`06079000    fffff880`06085000    0x0000c000    0x49f85aae                        
spldr.sys    5/11/2009 12:56:27 PM        fffff880`0207d000    fffff880`02085000    0x00008000    0x4a0858bb                        
GEARAspiWDM.sys    5/18/2009 8:17:04 AM        fffff880`059f1000    fffff880`059fe000    0x0000d000    0x4a1151c0                        
HpSAMD.sys    5/18/2009 7:43:49 PM        fffff880`0146d000    fffff880`01484000    0x00017000    0x4a11f2b5                        
lsi_sas.sys    5/18/2009 8:20:23 PM        fffff880`015df000    fffff880`015fc000    0x0001d000    0x4a11fb47                        
lsi_sas2.sys    5/18/2009 8:31:48 PM        fffff880`01772000    fffff880`01785000    0x00013000    0x4a11fdf4                        
megasas.sys    5/18/2009 9:09:46 PM        fffff880`017a4000    fffff880`017b0000    0x0000c000    0x4a1206da                        
ql40xx.sys    5/18/2009 9:18:11 PM        fffff880`01aef000    fffff880`01b4e000    0x0005f000    0x4a1208d3                        
MegaSR.sys    5/18/2009 9:25:54 PM        fffff880`01600000    fffff880`016a4000    0x000a4000    0x4a120aa2                        
amdsata.sys    5/19/2009 1:53:21 PM        fffff880`013d7000    fffff880`013f5000    0x0001e000    0x4a12f211                        
amdxata.sys    5/19/2009 1:56:59 PM        fffff880`01484000    fffff880`0148f000    0x0000b000    0x4a12f2eb                        
nvraid.sys    5/20/2009 2:39:40 AM        fffff880`01126000    fffff880`0114f000    0x00029000    0x4a13a5ac                        
nvstor.sys    5/20/2009 2:45:37 AM        fffff880`017b0000    fffff880`017db000    0x0002b000    0x4a13a711                        
LHidFilt.Sys    6/17/2009 12:49:39 PM        fffff880`07fc3000    fffff880`07fd6000    0x00013000    0x4a391ea3                        
LMouFilt.Sys    6/17/2009 12:49:43 PM        fffff880`07fd6000    fffff880`07fea000    0x00014000    0x4a391ea7                        
LEqdUsb.Sys    6/17/2009 12:49:54 PM        fffff880`07eb7000    fffff880`07ece000    0x00017000    0x4a391eb2                        
LHidEqd.Sys    6/17/2009 12:49:56 PM        fffff880`07ece000    fffff880`07ed6000    0x00008000    0x4a391eb4                        
enecir.sys    6/28/2009 10:17:30 PM        fffff880`0603e000    fffff880`0605b000    0x0001d000    0x4a48243a

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

 

[necrodragon]

I am having trouble finding out what each of these drivers listed actually are and therefore don;t know if I am installing the correct files to fix them. COuld you please tell me what each of these things are?

 

[usasma]

Include this webpage in your searches when trying to ID drivers: Driver Reference

 

[necrodragon]

OK, look at "stexstor.sys", it says that that is Promise SuperTrak EX Series Driver but when i go to find drivers there are different models of the product in the series such as:

SuperTrak EX12350
SuperTrak EX16300
SuperTrak EX16350
etc.

How do I find out which model I have because this is an issue with a lot of the items mentioned in the list above?

 

[usasma]

Use this free program: Speccy - System Information - Free Download

Also, you can try to locate it using MSINFO32.exe
Or you can look in Device Manager for it
Or you can check the specifications of your system. Since this is an HP system, there's a strong possibility that the driver is loading, but there is no such device on your system.

There's likely to be only 1 set of storage drivers that you are actually using - so work your way through the list of drivers. Check the drivers in Device Manager for the IDE ATA/ATAPI Controllers - that'll tell you which one you have. Don't worry about the other storage drivers yet (but they may have an impact on BSOD's - so don't just dismiss them).

 

[necrodragon]

I looked at the IDE ATA/ATAPI Controllers in Device Manager and found only one listed: Intel(R) PCHM SATA AHCI Controller 4 Port. I looked for drivers but I think it is up to date. Also, I downloaded Speccy, but am not sure how to use it and how it helps me identify the specific programs/models.

 

[necrodragon]

Use this free program: Speccy - System Information - Free Download

Also, you can try to locate it using MSINFO32.exe
Or you can look in Device Manager for it
Or you can check the specifications of your system. Since this is an HP system, there's a strong possibility that the driver is loading, but there is no such device on your system.

There's likely to be only 1 set of storage drivers that you are actually using - so work your way through the list of drivers. Check the drivers in Device Manager for the IDE ATA/ATAPI Controllers - that'll tell you which one you have. Don't worry about the other storage drivers yet (but they may have an impact on BSOD's - so don't just dismiss them).

I looked at the IDE ATA/ATAPI Controllers in Device Manager and found only one listed: Intel(R) PCHM SATA AHCI Controller 4 Port. I looked for drivers but I think it is up to date. Also, I downloaded Speccy, but am not sure how to use it and how it helps me identify the specific programs/models.

 

[usasma]

Haven't used speccy myself - have just recently seen it used on another forum.

The Intel drivers are the one's that start with IaStor...
The one that I saw above dated from 2009 and should be updated.

But zigzag3143 suggested that you update your Intel wifi drivers - have you done that? Are you still experiencing BSOD's?

 

[necrodragon]

Haven't used speccy myself - have just recently seen it used on another forum.

The Intel drivers are the one's that start with IaStor...
The one that I saw above dated from 2009 and should be updated.

But zigzag3143 suggested that you update your Intel wifi drivers - have you done that? Are you still experiencing BSOD's?

Yes, I updated the wifi drivers, and I never know when I am going to get the BSOD, sometimes it could happen the next day or within the next week or few weeks, it's unpredictable. I'll look into the aforementioned Intel Driver from 2009.