Solved Frequent BSOD at Idle, error 0x0000009f

[dannytill]

My custom build is getting random BSODs mostly at idle. Happens occasionally when I'm doing something but this is mainly my media server so I don't log onto it very often. I did a grab all. Pretty sure it's a driver. Hopefully one of you guys can point me in the right direction. Thanks.

 

[ICIT2LOL]

Danny give these a run first delete any rubbish the malware scans come up with the ADWe the Clean button

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

http://www.sevenforums.com/tutorials/433-disk-check.html< DO NOT runon a SSD

http://www.superantispyware.com/

http://www.malwarebytes.org/products/malwarebytes_free/

http://www.bleepingcomputer.com/download/adwcleaner/

download from bleeping computer

 

[Arc]

Also pay attention to ATTO ExpressSAS R348 RAID Adapter
(c:\windows\system32\drivers\esasraid.sys).

No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
     cmd  flg cl Device   File     Completion-Context
 [ 16, 0]   0  0 fffffa800cecd9c0 00000000 fffff88001814d30-fffffa800cf90cd0    
           [COLOR=Red]\Driver\ESASRAID    CLASSPNP!ClasspPowerUpCompletion[/COLOR]
            Args: 00000000 00000000 00000000 00000002
>[ 16, 2]   0 e1 fffffa800cf90790 00000000 fffff88000e45f50-00000000 Success Error Cancel pending
           \Driver\Disk    partmgr!PmPowerCompletion
            Args: 00041100 00000001 00000001 00000002
 [ 16, 2]   0 e1 fffffa800cef5b90 00000000 00000000-00000000    pending
           \Driver\partmgr
            Args: 00041100 00000001 00000001 00000002
----------------------------------------------------------------------------------------------------------------------
[COLOR=Red]BugCheck 9F[/COLOR], {3, fffffa800cecd9c0, fffff80000b9c3d8, fffffa80127d7b00}

*** WARNING: Unable to verify timestamp for esasraid.sys
*** ERROR: Module load completed but symbols could not be loaded for esasraid.sys
[B][COLOR=Red]Probably caused by : esasraid.sys[/COLOR][/B]

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

And the driver is old.

fffff880`01174000 fffff880`01189000   esasraid T (no symbols)           
    Loaded symbol image file: esasraid.sys
    Image path: \SystemRoot\system32\DRIVERS\esasraid.sys
[COLOR=Red]    Image name: esasraid.sys
    Timestamp:        Mon May 09 19:18:00 2011[/COLOR] (4DC7F090)
    CheckSum:         0001B37F
    ImageSize:        00015000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

RAID is always problematic; and so we usually suggest to not use RAID. But it appears to be very essential for you. It seems that a number of HDDs are in the array.

Model    ATTO Raid500 SCSI Disk Device
Size    [COLOR=Red][B]8.19 TB[/B][/COLOR] (9,001,614,827,520 bytes)

Try to update the driver first. It seems that you need to registration here to search for drivers: SAS/SATA RAID Adapters | ATTO

Let us know whether there is any feasible update or not; and if updates are available, the situation after that update.

 

[dannytill]

I used to work there and the raid card is just old but it was one of their most popular products. It's discontinued but I have the most recent driver. And yes I do need the raid. I have 4 3TB drives in a raid 5. There were a lot of dump files did they they all point the raid?

 

[Arc]

I used to work there and the raid card is just old but it was one of their most popular products. It's discontinued but I have the most recent driver. And yes I do need the raid. I have 4 3TB drives in a raid 5. There were a lot of dump files did they they all point the raid?

All that I checked.

 

[dannytill]

OK maybe I will uninstall the driver,, re-seat the card and the reinstall the driver. See if that helps. Let me know if you have any other ideas. I saw some errors I thought were pointing to the wifi but maybe I'm wrong.

 

[Arc]

First, BlueScreen View is a poor inferior tool compared to what we use.

Second, if you dont have trust on the suggestions and the person who is suggesting, you will never be able to follow the instructions and get the desired result thereby.

Still, checked latest 23 crash dumps for your satisfaction only, once again. All are the same, what I posted in my first post in this thread.

Plus, checked for athrx.sys, for your satisfaction, too. It is old, and needs update for sure. Get it: Drivers for Atheros AR9485 and Windows 7
Follow http://www.sevenforums.com/tutorials/97061-driver-install-device-manager.html to install it.

But, the network driver is not the uppermost issue, it is RAID.

EDIT: Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept then restart.

This startup entry .... you should not keep it there in the present situation. It will make the situation worse.

LenovoEMC Storage Manager    c:\progra~2\lenovo~1\lenovo~2.exe -s    Public    Common Startup

 

[dannytill]

Sorry, I believe you plus like you said 23 of the logs all pointed to the same thing. You guys have nothing but helpful. I wasn't trying to imply you were wrong I just wanted to cover all my bases. I'll see if there is anything I can do with the raid. I have the ATTO config tool in the startup too. I don't think it has to be there either. I'm working on your suggestions and I'll get back to you with the results. Thanks again.

 

[dannytill]

I am not sure why but I think qtorrent was causing my BSODs. Ever since I stopped using it I have not received another BSOD. Maybe the way qtorrent was interacting with the raid caused it. Regardless I have to assume that qtorrent was the cause as I have not made any other changes. Thanks for the help.