Solved Library PC which should be left all day has BSOD 2 days running!

[GrazyD]

Hi,

We have a networked PC here which used for checking books in and out of our library and it has blue screened 2 days in a row, nobody has been using this pc when it has blue screened. I have downloaded SF diag tool but everytime I try to run it and each individual component it gives me the error that is at the bottom of the instruction. I do have some mini dump files can you please have a look as I don't have the tools or knowledge. I have attached them.

Many Thanks

 

[koolkat77]

Welcome to the forum.

Please follow http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html and upload all necessary files.

 

[GrazyD]

Hi thanks for the reply, I have tried running the diag tool but I cannot get it to run, it keeps giving me the error and I don't understand how to fix it, this is why I attached the dmp files in my original post.

Thanks

 

[Arc]

OK, at least upload your MSINFO32.nfo file.

1. Click on the start button
2. Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
3. File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
4. Give the time for processing, it will save a .nfo file on your desktop.
5. Zip it, and upload it following the instruction.

 

[ICIT2LOL]

Arc do you think a safe mode sfc and chkdsk would be of any help??

 

[x BlueRobot]

What is the error message?

I suspect a problem with the network card driver or any internet security suite.

0: kd> [COLOR="SeaGreen"]lmvm b57nd60x[/COLOR]
start    end        module name
8e518000 8e55d000   b57nd60x   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\b57nd60x.sys
    Image name: b57nd60x.sys
    Timestamp:        [COLOR="Red"]Sun Oct 11 09:34:22 2009[/COLOR] (4AD1988E)
    CheckSum:         0004D58E
    ImageSize:        00045000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Your Broadcom NetXtreme Gigabit Ethernet NDIS6.0 Driver is very old and outdated, please update the driver from here - Ethernet NIC Driver Downloads | Broadcom

[COLOR=Red]BugCheck 9F[/COLOR], {[COLOR="Blue"]3[/COLOR], 84a7e5a0, 82b78ae0, [COLOR=SeaGreen]84d3b728[/COLOR]}

Probably caused by : ntkrpamp

0: kd> [COLOR=SeaGreen]!irp 84d3b728[/COLOR]
Irp is active with 3 stacks 2 is current (= 0x84d3b7bc)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
     cmd  flg cl Device   File     Completion-Context
 [ 16, 0]   0  0 84a7e5a0 00000000 88ccd377-8589a0e0    
           \Driver\PnpManager    ndis!ndisSetDevicePowerDownComplete
            Args: 00000000 00000000 00000000 00000003
[COLOR=Red]>[ 16, 2]   0 e1 8589a028 00000000 00000000-00000000    pending
           \Driver\tunnel[/COLOR]
            Args: 00015400 00000001 00000004 00000003
 [  0, 0]   0  0 00000000 00000000 00000000-84ccc538    

            Args: 00000000 00000000 00000000 00000000

For the IRP, these links will be worth checking out - IRP_MJ_POWER (Windows Drivers) and IRP_MN_SET_POWER (Windows Drivers)

0: kd> [COLOR="SeaGreen"]!devobj 84a7e5a0[/COLOR]
Device object (84a7e5a0) is for:
 Cannot read info offset from nt!ObpInfoMaskToOffset
 \Driver\PnpManager DriverObject 84a9cbb8
Current Irp 00000000 RefCount 0 Type 00000004 Flags 00001040
DevExt 84a7e658 DevObjExt 84a7e660 DevNode 84a97488 
ExtensionFlags (0x00000800)  [COLOR="Red"]DOE_DEFAULT_SD_PRESENT[/COLOR]
Characteristics (0x00000180)  [COLOR=Red]FILE_AUTOGENERATED_DEVICE_NAME[/COLOR], [COLOR="Red"]FILE_DEVICE_SECURE_OPEN[/COLOR]
AttachedDevice (Upper) 8589a028 \Driver\tunnel
Device queue is not busy.

0: kd> [COLOR="SeaGreen"]!devstack 84a7e5a0[/COLOR]
  !DevObj   !DrvObj            !DevExt   ObjectName
  8589a028  \Driver\tunnel     8589a0e0  InfoMask field not found for _OBJECT_HEADER at 8589a010

> 84a7e5a0  \Driver\PnpManager 84a7e658  Cannot read info offset from nt!ObpInfoMaskToOffset

!DevNode 84a97488 :
  DeviceInst is "Root\*TEREDO\0000"
  ServiceName is "tunnel"

FILE_AUTOGENERATED_DEVICE_NAME indicates the I/O Manager to give a device object a name, instead of the caller specifying a name itself.

FILE_DEVICE_SECURE_OPEN indicates the I/O Manager to apply the security descriptor to any device opens on this particular device object, and this prevents any unauthorised access to the driver's namespace which belongs to that device object.

DOE_DEFAULT_SD_PRESENT most likely simply provides a default security descriptor with the standard security settings.

0: kd> [COLOR="SeaGreen"]k[/COLOR]
ChildEBP RetAddr  
82b78a94 82b18377 nt!KeBugCheckEx+0x1e
82b78b00 82b183f0 [COLOR="Red"]nt!PopCheckIrpWatchdog[/COLOR]+0x1f5
82b78b38 82aca4d9[COLOR="Red"] nt!PopCheckForIdleness[/COLOR]+0x73 <-- Timer Object
82b78b7c 82aca47d nt!KiProcessTimerDpcTable+0x50
82b78c68 82aca33a nt!KiProcessExpiredTimerList+0x101
82b78cdc 82ac84ce nt!KiTimerExpiration+0x25c
82b78d20 82ac82f8 nt!KiRetireDpcList+0xcb
82b78d24 00000000 nt!KiIdleLoop+0x38

nt!PopCheckIrpWatchdog is used to call the nt!KeBugCheckEx, when the Power IRP has been pending for 10 minutes or more.

 

[Arc]

Arc do you think a safe mode sfc and chkdsk would be of any help??

I really dont think so, John

Why? I can explain the reason. The minor reason is, SFC checks for system files only. I have never seen any BSOD caused by system files malfunctioning and resolved by running SFC scannow command. This command is very useful and helpful, but if the BSOD is driver/software caused, it is always third party items which is the culprit. And about chkdsk, it is helpful for HDD/file system related issue, and the present issue is not a HDD/File System related issue.

So what is the present issue? It is hibernate/sleep related. And it is the major reason why I dont think those will not help. The suggestions are be be issue specific. The first necessary notion of the hibernate/sleep relared issue is from the original post .....

nobody has been using this pc when it has blue screened.

The sufficient reason to believe that it is a hibernate/sleep related issue is the bugcheck code .....

BugCheck 9F : DRIVER_POWER_STATE_FAILURE

Driver power state failure means, a particular driver is failing to response properly within the time frame during power transition (from active to sleep and/or vice-versa) and causing the BSOD. So, we need to search for the driver that is failing the power state.

We have the driver, that is b57nd60x.sys. And the driver is very old, of 2009. So we need to update it. Usually the driver is used by Broadcom NetXtreme.... but we need to be 100% sure before suggesting it to the OP. So we need to see the MSINFO32.nfo file.

Also, we need to check the graphics environment, as there is smoe hint of intel display failure, too; and the USB environment, too. Specially if the USER is using any USB network adapter (I guess NetXtreme is a PCIe card). And, all those will be available in the MSINFO32,nfo.

I hope you can understand my point and so I request you to kindly not take my post otherwise. I am just trying to explain what I am thinking based on my finding from the data the user already uploaded.

EDIT: A stop 0x9F is a failing PnP device driver, and not anything else. It it is induced by anything else (Internet Security or VPN or anything), the code shows as 0x100009F.

 

[ICIT2LOL]

Arc do you think a safe mode sfc and chkdsk would be of any help??

I really dont think so, John

Why? I can explain the reason. The minor reason is, SFC checks for system files only. I have never seen any BSOD caused by system files malfunctioning and resolved by running SFC scannow command. This command is very useful and helpful, but if the BSOD is driver/software caused, it is always third party items which is the culprit. And about chkdsk, it is helpful for HDD/file system related issue, and the present issue is not a HDD/File System related issue.

So what is the present issue? It is hibernate/sleep related. And it is the major reason why I dont think those will not help. The suggestions are be be issue specific. The first necessary notion of the hibernate/sleep relared issue is from the original post .....

nobody has been using this pc when it has blue screened.

The sufficient reason to believe that it is a hibernate/sleep related issue is the bugcheck code .....

BugCheck 9F : DRIVER_POWER_STATE_FAILURE

Driver power state failure means, a particular driver is failing to response properly within the time frame during power transition (from active to sleep and/or vice-versa) and causing the BSOD. So, we need to search for the driver that is failing the power state.

We have the driver, that is b57nd60x.sys. And the driver is very old, of 2009. So we need to update it. Usually the driver is used by Broadcom NetXtreme.... but we need to be 100% sure before suggesting it to the OP. So we need to see the MSINFO32.nfo file.

Also, we need to check the graphics environment, as there is smoe hint of intel display failure, too; and the USB environment, too. Specially if the USER is using any USB network adapter (I guess NetXtreme is a PCIe card). And, all those will be available in the MSINFO32,nfo.

I hope you can understand my point and so I request you to kindly not take my post otherwise. I am just trying to explain what I am thinking based on my finding from the data the user already uploaded.

EDIT: A stop 0x9F is a failing PnP device driver, and not anything else. It it is induced by anything else (Internet Security or VPN or anything), the code shows as 0x100009F.

Thanks Arc no mate that was really helpful and one I am saving for reference info

 

[GrazyD]

msinfo32 file

Hi Guys, and many thanks for looking into this, I'm sorry I haven't replied sooner but I have had a death in the family.
Please find attached the msinfo32 file as instructed.

Thanks

GrazyD

 

[Arc]

Unfortunately the .nfo file is corrupted. Try to upload a text version?

1. Click on the start button
2. Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
3. File>Export. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
4. Give the time for processing, it will save a .nfo file on your desktop.
5. Zip it, and upload it following the instruction.

 

[GrazyD]

msinfo32 re attached

Thanks
GrazyD

 

[Arc]

Yes, it is Broadcom NetXtreme Gigabit Ethernet that you need to update. So get it from the link that x BlueRobot suggested earlier ..... Ethernet NIC Driver Downloads | Broadcom

Also install Intel® Graphics Media Accelerator Driver.

Let us know the results.

 

[GrazyD]

Yes, it is Broadcom NetXtreme Gigabit Ethernet that you need to update. So get it from the link that x BlueRobot suggested earlier ..... Ethernet NIC Driver Downloads | Broadcom

Also install Intel® Graphics Media Accelerator Driver.

Let us know the results.

Hi Arc,

Many thanks for this, I have updated the NIC driver and this is now showing the latest driver. I was going to install the other driver but this is for a 64bit system, but the machine with the problem is a 32bit system (unless I'm missing something)

So far so good.

Thanks again

GrazyD

 

[Arc]

Then try it: Intel® Graphics Media Accelerator Driver,Windows 7

 

[GrazyD]

Thanks guys, all drivers installed as advised I guess I just keep an on it.

Much Appreciated

GrazyD

 

[x BlueRobot]

Please post a update if any problems arise again, or everything is okay.

 

[GrazyD]

All is Good!

Well guys all seems to be OK, pc hasn't had a BSOD since I have updated drivers as advised, so thanks ever so much for all your time and effort.

Thanks to all who contributed.

GrazyD

 

[x BlueRobot]

Welcome, glad to be able to help