BSOD - 0xd1 - storport.sys

[Varstaz]

Hi Everyone! thanks for having a look at it

-almost since having this new pc, it's been BSOD-ing:
*Bugcheck: 0xd1 ( DRIVER_IRQ_NOT_LESS_OR_EQUAL )
*Probably causing: storport.sys

-when trying to play certain games, BSOD is more frequent
(visiting 20secs into the game)
-BSOD only appears when playing games, haven't encountered it any other time

-having a basically clean install of Windows 7 x64


Have:
-tried updating drivers
-run memtest86 up to 3 passes, no errors found
-run on previous install of OS: Windows partition error checking, which then caused the system to freeze on startup until have reinstalled it(the OS)

System specs:
-CPU: AMD Phenom(tm) II X6 1055T
-Mainboard: ECS MCP61M-M3 (BIOS: AMI 080015 11/03/2010)
-RAM: 8GB DIMM DDR3 (2*4GB)
-Video Card: AMD Radeon HD 6870
-Network Adapter: NVIDIA nForce 10/100 Mbps Ethernet
-Windows System: Microsoft Windows 7 Ultimate 6.01.7600 x64

I haven't overclocked or otherwise altered the working of any piece of hardware

Minidumps, Event log and further System Specifics are included beneath!

Please share any ideas on resolving this...thank you! 😍

Minidumps.rar
EventLog.rar
SystemSpecs.nfo

 

[pjmelect]

Have you looked here?

http://support.microsoft.com/kb/983554

 

[Varstaz]

Thank you pjmelect for your help! My install of windows was so clean, that this time I've forgotten about the updates.
After installing the hotfix, the issue seemed to be partially mended though not completely fixed. Trying it at a game, instead of BSOD-ing, it's frozen for minutes. After it however I could continue.
Hoping that the windows updates could eliminate the remaining problems, I installed the first Service Pack through the automatic update system. Since then, it's BSOD-ing as before.

When only the freezing was the issue, Widows logged the following error a lot of times:

[fixed]<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="nvstor64" />
<EventID Qualifiers="49374">9</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2011-12-27T20:36:48.913400000Z" />
<EventRecordID>3665</EventRecordID>
<Channel>System</Channel>
<Computer>FL143nD57</Computer>
<Security />
</System>
<EventData>
<Data>\Device\RaidPort0</Data>
<Data>WDC WD10EARS-00MVWB0</Data>
<Data>51.0</Data>
<Data>WD-WMAZA4775488</Data>
<Data>0</Data>
<Binary>0000000005002800000000000900DEC0000000000000000000000000000000000000000000000000</Binary>
</EventData>
</Event>[/fixed]

I have uploaded an updated version of my EventLog beneath.

Any suggestion is greatly appreciated!

EventLog2.7z

 

[pjmelect]

It seems that it is the RAID driver that is causing your problems, do you have a RAID? if not try disabling it in the BIOS.

 

[Varstaz]

In my BIOS there's a "Sata configuration" option that can be either SATA or RAID Mode. It's been SATA ever since.

I've run the hdd's extended test which passed.

I tried updating everything possible through the Windows Device Manager.
Under "IDE ATA/ATAPI controllers" it installed updates for 2 "NVIDIA nForce Serial ATA Controller" entries.
The entries then moved under "Storage Controllers".
This resulted in the game's screen freezing and the pc being unresponsive save toggling Num Lock. As if a pointer was lost the the hdd. No BSOD this time.
Reinstalling the mobo's diver reversed this.

In BIOS APIC Mode is enabled. I've read that it extends the number of IRQ levels, and has some other benefits for multi CPU systems. It caused problems for others. (Disabling that and reinstalling windows might solve my issue.)

Changing game settings to the absolute minimum also seems to help.
I remember reading something about Windows incorrectly assuming a PCI device instead of a ?PCI-e? in some cases, which can lead to handling the device incorrectly. ?Maybe when I was reading on APIC?
Cannot find anything on this anymore.

As always, any suggestion is greatly appreciated!