Driver_Power_State_Failure (scsiport.sys) after Sleep

[tarsonis]

Hello there,

just ran into this BSOD. Looked into the minidump and the files that caused the crash are ntoskrnl.exe+81e7a and scsiport.sys+1f9b4. I don't get it. I don't have any SCSI devices. :sarc: How can I find out which device is responsible for this?

minidump ist in the attachment.

 

[Arc]

Hello tarsonis, post it following the Blue Screen of Death (BSOD) Posting Instructions.

 

[tarsonis]

Ah, ok! Didn't know. Just a sidenote. I started Driver detective about two days ago and it said everything is allright.

 

[Arc]

Your crash dumps are not showing any finite probable cause.

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

Use !analyze -v to get detailed debugging information.

BugCheck 1000009F, {4, 258, fffffa800ca86660, fffff800056bd3d0}

Implicit thread is now fffffa80`0ca86660
[COLOR=Red]Probably caused by : ntkrnlmp.exe [/COLOR]( nt!KiSwapContext+7a )

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

In such a situation, it is better to enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier. With verifier enabled, use the computer normally, surf internet and download things (specially) normally, though it may behave a bit laggy.

Let us know the results, with the subsequent crash dumps, if any.

 

[tarsonis]

Ok, first of thank you! Enabled the verifier like described. After restart I get a BSOD.

ksbus64.sys - Address FFFF88000E78000 base at FFFFF88000E6F000, Datestamp

Had to choose "last working state" to boot into windows again. I think verifier is deactivated now.

//Edit: Ok, this file belongs to TotalMounter. I was told the TotalMounter is the safest Virtual CD mounter around. Should I deinstall it?

 

[tarsonis]

Ok, I deinstalled TotalMounter. Did the verifier action again and get a new BSOD:

iaStorA.sys -Address FFFFF880012A2973 base at FFFFF88001219000, DateStamp

Well, this is the Intel AHCI driver. Can't be wrong because I downloaded it from my motherboard manufactor website. What should I do?

 

[Arc]

As far as I can say, there is no "safe" virtual drive mounter. I can recommend 7-Zip which extracts all disc images, and your work is done. Using it, at a maximum, you will miss the autorun and DVD menus, and nothing more.

iAstor is also problematic, whereas msahci.sys is not. I recommend to use it, and it is the easiest.

Get rid of intel rapid storage.

1. Right click on "my computer" icon and click "manage" on the context menu.
2. It will open the "computer management" window.
3. Select "Device Manager" in the left pane, It will list all the existing devices up.
4. Expand "Disc Drives" by clicking on the triangle in front of it.
5. Select one item under it, right click, uninstall.
6. Continue the process for all items under "Disc Drives"
7. Now restart the computer. At restart, windows will auto configure the appropriate system driver, msahci.sys.

Let us know the further results.

 

[tarsonis]

Ok, will try 7-zip. Regarding the Intel IRS driver. Well this a Z77 Board and with intel sata chip. I read that the win7 build in driver is not that good in performing and not that good in use with SSD drives.
Can't understand why this should be deinstalled when win7 got a problem. Seems to me thats more a OS bug than a controller bug. :huh:

 

[Arc]

That depends on your focus of priority

 

[tarsonis]

Sure. But its like buying a car, where the dealer says I can only drive with their tires even if they weaker than everyones else. To me its a OS bug. I don't get this BSOD in Xp (dual boot system)

So no other solution? BSOD when sleep or using driver thats not supposed to be used? :huh:

 

[Arc]

Actually, msahci is the most stable one. I haven't seen any crash due to it, and have seen a lot with rapid storage. A few of our most knowledgable members think (and I follow their opinion) that Rapid Storage is a bloatware. But it might be a point of contradiction.

As a practice, IMO safety first.

 

[tarsonis]

OK, I will test it. Since the last two or three sleeps there was no BSOD. I DIDn't change the ahci driver. Hope it stay that way. If not I will install the nsahci driver. thanks