Jump to content
Corsair Community

BSODs caused by Link 2.20 and iastorA.sys


tyrannosaurus

Recommended Posts

BSODs caused by Link 2.2.0 in connection with IRST and WINDOWS 7 64.

 

 

Posted this under PSU already, but I think it should be here as well.

 

The only reason I need Link is to start the fan for my AX1200i, because this PSU is running pretty warm before the fan is willing to start.

 

 

My IRST driver:

Intel® Rapid Storage Technology enterprise Driver Software V3.5.0.1092 for Windows Vista/7 32bit & 64bit.(WHQL)

 

Within 5 minutes after installing Link 2.2.0 system crashed. Before my system worked bugfree.

 

 

Probably a conflict between Link driver and Intel Rapid Storage Driver:

 

 

 

 

 

Microsoft ® Windows Debugger Version 6.12.0002.633 AMD64

Copyright © Microsoft Corporation. All rights reserved.

 

 

Loading Dump File [C:\Windows\Minidump\010313-10249-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

 

Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols;C:\Symbols

Executable search path is:

Windows 7 Kernel Version 7601 (Service Pack 1) MP (12 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333

Machine Name:

Kernel base = 0xfffff800`0385e000 PsLoadedModuleList = 0xfffff800`03aa2670

Debug session time: Thu Jan 3 13:08:46.870 2013 (UTC + 1:00)

System Uptime: 0 days 0:07:04.070

Loading Kernel Symbols

...............................................................

................................................................

..........................................

Loading User Symbols

Loading unloaded module list

.....

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

 

Use !analyze -v to get detailed debugging information.

 

BugCheck 1E, {0, 0, 0, 0}

 

*** WARNING: Unable to verify timestamp for iaStorA.sys

*** ERROR: Module load completed but symbols could not be loaded for iaStorA.sys

Probably caused by : storport.sys ( storport!StorPortNotification+22 )

 

Followup: MachineOwner

---------

 

2: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

 

KMODE_EXCEPTION_NOT_HANDLED (1e)

This is a very common bugcheck. Usually the exception address pinpoints

the driver/function that caused the problem. Always note this address

as well as the link date of the driver/image that contains this address.

Arguments:

Arg1: 0000000000000000, The exception code that was not handled

Arg2: 0000000000000000, The address that the exception occurred at

Arg3: 0000000000000000, Parameter 0 of the exception

Arg4: 0000000000000000, Parameter 1 of the exception

 

Debugging Details:

------------------

 

 

EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

 

FAULTING_IP:

+3937613263326636

00000000`00000000 ?? ???

 

EXCEPTION_PARAMETER1: 0000000000000000

 

EXCEPTION_PARAMETER2: 0000000000000000

 

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

 

BUGCHECK_STR: 0x1E_0

 

CUSTOMER_CRASH_COUNT: 1

 

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

 

PROCESS_NAME: System

 

CURRENT_IRQL: 2

 

EXCEPTION_RECORD: fffff8800396a808 -- (.exr 0xfffff8800396a808)

ExceptionAddress: fffff8800190b0d2 (storport!StorPortNotification+0x0000000000000022)

ExceptionCode: c0000005 (Access violation)

ExceptionFlags: 00000000

NumberParameters: 2

Parameter[0]: 0000000000000000

Parameter[1]: ffffffffffffffff

Attempt to read from address ffffffffffffffff

 

TRAP_FRAME: fffff8800396a8b0 -- (.trap 0xfffff8800396a8b0)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=0073da650073da65 rbx=0000000000000000 rcx=0000000000001003

rdx=fffffa801804c000 rsi=0000000000000000 rdi=0000000000000000

rip=fffff8800190b0d2 rsp=fffff8800396aa40 rbp=fffffa800d5e11d0

r8=0000000000000002 r9=0000000000000000 r10=fffffa801804c000

r11=fffff88003942100 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0 nv up ei ng nz na po nc

storport!StorPortNotification+0x22:

fffff880`0190b0d2 488b18 mov rbx,qword ptr [rax] ds:0073da65`0073da65=????????????????

Resetting default scope

 

LAST_CONTROL_TRANSFER: from fffff800038d49be to fffff800038dcf90

 

STACK_TEXT:

fffff880`039698e8 fffff800`038d49be : 00000000`00000000 fffff800`0381962f fffff880`0396a060 fffff800`03907e20 : nt!KeBugCheck

fffff880`039698f0 fffff800`03907aed : fffff800`03ae36f8 fffff800`03a201b0 fffff800`0385e000 fffff880`0396a808 : nt!KiKernelCalloutExceptionHandler+0xe

fffff880`03969920 fffff800`039068c5 : fffff800`03a23fac fffff880`03969998 fffff880`0396a808 fffff800`0385e000 : nt!RtlpExecuteHandlerForException+0xd

fffff880`03969950 fffff800`03917851 : fffff880`0396a808 fffff880`0396a060 fffff880`00000000 fffffa80`0d69bad8 : nt!RtlDispatchException+0x415

fffff880`0396a030 fffff800`038dc642 : fffff880`0396a808 00000000`00000000 fffff880`0396a8b0 00000000`00000000 : nt!KiDispatchException+0x135

fffff880`0396a6d0 fffff800`038daf4a : 00000000`00000001 fffffa80`146bd7f0 fffffa80`15f95130 00000000`00000030 : nt!KiExceptionDispatch+0xc2

fffff880`0396a8b0 fffff880`0190b0d2 : fffffa80`0d6b51db fffff880`012e90de 00000000`00000000 fffffa80`0d69bad8 : nt!KiGeneralProtectionFault+0x10a

fffff880`0396aa40 fffff880`012e7aa8 : fffffa80`0d8eae40 fffffa80`1804c000 00000000`00000002 00000000`00000000 : storport!StorPortNotification+0x22

fffff880`0396aac0 fffffa80`0d8eae40 : fffffa80`1804c000 00000000`00000002 00000000`00000000 fffff880`0396ab38 : iaStorA+0x63aa8

fffff880`0396aac8 fffffa80`1804c000 : 00000000`00000002 00000000`00000000 fffff880`0396ab38 00000000`00000002 : 0xfffffa80`0d8eae40

fffff880`0396aad0 00000000`00000002 : 00000000`00000000 fffff880`0396ab38 00000000`00000002 00000000`0001b596 : 0xfffffa80`1804c000

fffff880`0396aad8 00000000`00000000 : fffff880`0396ab38 00000000`00000002 00000000`0001b596 fffff880`012eebec : 0x2

 

 

STACK_COMMAND: kb

 

FOLLOWUP_IP:

storport!StorPortNotification+22

fffff880`0190b0d2 488b18 mov rbx,qword ptr [rax]

 

SYMBOL_STACK_INDEX: 7

 

SYMBOL_NAME: storport!StorPortNotification+22

 

FOLLOWUP_NAME: MachineOwner

 

MODULE_NAME: storport

 

IMAGE_NAME: storport.sys

 

DEBUG_FLR_IMAGE_TIMESTAMP: 4d79a55f

 

FAILURE_BUCKET_ID: X64_0x1E_0_storport!StorPortNotification+22

 

BUCKET_ID: X64_0x1E_0_storport!StorPortNotification+22

 

Followup: MachineOwner

---------

minidump 010313.zip

Link to comment
Share on other sites

  • Replies 68
  • Created
  • Last Reply

Thank you, Jan54. I knew, there was somewhere a thread about IRST and Link, but coudn't refind it.

 

Still I think, Corsair should offer a solution to that problem, which is really annoying.

AX1200i eventually is an expensive toy.

 

 

So: what version of IRST and Link do you use sucessfully?

Link to comment
Share on other sites

Thank you, Jan54. I knew, there was somewhere a thread about IRST and Link, but coudn't refind it.

 

Still I think, Corsair should offer a solution to that problem, which is really annoying.

AX1200i eventually is an expensive toy.

 

 

So: what version of IRST and Link do you use sucessfully?

 

I use iRST 3.0.0.2003 (came with my mb) and Link v2.2.0

Link to comment
Share on other sites

IRST 3.0.2003, dated 2011.12.02, is the first driver for my MB that Asus released.

 

IRST Enterprise, Version 3.5.0.1092 & 3.5.0.109, dated 2012.10.22 are the most recent from Asus MB support.

 

This is really ridiculous, that we have to use outdated driver to support oldfashioned Corsair driver.

 

After uninstalling Link 2.2.0 9 hours ago, I had not a single BSOD.

 

Don't know, how I will decide right now. Maybe I'll kick Link Driver and leave my AX1200i unsupported. I've little hope that Corsair will fix this.

Link to comment
Share on other sites

UPDATE:

 

Confirmed: IRST 3.0.2003 and Link 2.2.0 work together.

 

So this may be conceived as an interim solution.

 

 

On the other hand: How about Corsair would inform trillions of IntelRapidStorageDriver-User which version is compatible with their exotic driver?

 

 

After all I've spent days tracking down the cause of this troublemaker and reinstalling my whole system.

Link to comment
Share on other sites

I spent numerous days looking for the cause of the BSOD's on my Win8 64 pro system, not suspecting Link 2.2 as lack of Win8 support was nowhere stated. As it seems the issue also occurs with win7.

As soon as I installed Intel RSTe 3.5.1096, it crashed almost every hour sharp.

uninstalled corsair link and the BSODs are gone.

@t53186: I also have the X79 setup, but an Asus Sabertooth board. Are you running Win8 pro 64? It might be worth the trouble for me downgrading to 1092, although I don't want to risk my Raid5 array with Terabytes of data....

 

btw really awkward that such expensive tools, as it did come with my AX750i and linked to the H100i, is not supported on Win8. Manufacturers receive Win8 pre-releases way up front and it is not exactly new anymore.... couple of months old. Not giving it a priority is of course another story.....

way to go Corsair:evil:

Link to comment
Share on other sites

Sorry to say running WIN7 x64 pro. I have a SSD boot drive/applications and 4 500GB drives in raid10.

 

Not arguing with your assertion about pre-consumer release of win8 to vendors. However I hesitate to pass judgement on Corsair's ability to get it right for win 8 when released for a couple of reasons. Not that I am letting them off the hook mind you.

 

1. R&D, or whatever has been pretty busy trying to get it right for the OS that is advertised as supported along with the new products they have released. Don't know what relationship Corsair has with Microsoft.

 

2. In my 30+ years of computer experience, early adopters of new operating systems are going out on a limb hoping everything will work. Again, not making excuses. In my occupation dealing with PC, server, and mainframe hardware we never implement new changes as fast as they are available. Keeping in mind what we support is mission critical stuff.

 

3. I love to tinker on my own hardware which is critical for my hobbies, games, everyday use, and personal business as a graphic designer. I take a lot of chances, more than I should with the knowledge and experience I have, but I still don't venture in to the land of unknown when it comes to new operating systems, especially Microsoft Windows which is driven more by marketing hype and desire to make a profit than it is by the end user.

 

I apologize for my ranting and hope no one thinks I am saying it is our fault that the link does not work as we expect it. Just offering an alternative point of view/opinion.

Link to comment
Share on other sites

I hear you, coming from a mainframe business too, I agree. But Corsair aiming for consumer business and not explicitly stating required OS's at their product pages, should do better. I thought for once taking the leap, having looked at various support for my components, so this is disappointing.

Let's say that I hope Corsair will get their stuff together soon and work hard at support for Win 8. :)

Link to comment
Share on other sites

  • 2 weeks later...
Guys I am sorry but we are looking into this now and I expect a newer version that will have better support for Windows 8.

But I will have more information in about two weeks.

 

that's good news Ram Guy! thanks for the update!:headbang2

good to know that the support will take off for Win8, I have an Obsidian, Hydro and AX PSU from corsair, but cannot control any fan/noise settings at all :[pouts:

Link to comment
Share on other sites

Guys I am sorry but we are looking into this now and I expect a newer version that will have better support for Windows 8.

But I will have more information in about two weeks.

 

And how about Windows 7 64 bit, will there be a fix too?

I would be happy, if you could pass my attached minidump file (see post #1) to your software guy and post some results.

I mean besides this Link-bug Ax1200i is working fine.

Link to comment
Share on other sites

Thx RamGuy, good news...

 

Now, to anyone that want to use TRIM in a raid array on let's say x79 chipset, as most major manufacturers now are providing new bios upgrade with TRIM support, mostly, like me using a Rampage IV Extreme, i was pissed that i had to do a choice of BSOD or backtrack drivers to RSTe 3.0...

 

Well, instead, i used a modified bios that uses 11.6 based OROM instead of RST 3.5 OROM, and use Intel 11.7 Drivers instead of RSTe 3.5... and i get no BSOD, until corsair fixes their problems with the software... and mostly, Windows 8 x64 problems...

 

I am using 2 computers, one Rampage III Extreme on x58 chipset and a modded 11.6 OROM, and also a Rampage IV Extreme on x79 chipset with also a modded 11.6 OROM and both of them are running 11.7 Intel Raid drivers and i get no BSOD with the Corsair 2.2.0 software.

Link to comment
Share on other sites

win8 has only been released for a couple months now and corsair couldnt begin working on software until it was released

That's funny. I bought an Asus P8Z77-V motherboard 2 months ago, and they did not say they could only begin working on the software until Win8 was released. They said it was Win8 ready and there was a Win8 installation DVD included, and it works. I suppose a motherboard is more complicated than a stupid pump (I have a H80i cooler).

 

I reported a BSOD crash Link related a while ago, but there was no reply.

http://forum.corsair.com/v3/showthread.php?t=113585

 

When a company has quality related issues like with Link, then you start wondering about the quality side of the other products too.

Link to comment
Share on other sites

you're comparing apples to oranges

a m/b is a core part to a build so correlation is productive on all sides

you wouldnt start selling a car motor and THEN make arrangements for a chassis to put it in,would you?

 

You and I had this conversation before.

In the old days, we would meet on a dusty main street at high noon and shoot it out.

 

My point is, if Link is not fully optimal under Win8, that is fine.

But if it causes crashes, then it becomes like a core component. And if it is known that it is not compatible with Win8, then Corsair should state that on the product site of the products that use Link.

And there are plenty of other non core products that are Win8 ready. Cant see why Corsair couldn't get it done in time.

Link to comment
Share on other sites

You and I had this conversation before.

.

uh huh,and like last time i was responding to someones question when you popped in with your disgruntled expertise once again comparing apples to oranges.

when a new os is being developed,they work in conjunction with core parts,a aftermarket cooler is NOT a core part so manufacturers of these parts do their coding AFTER the OS release

 

you know theres 3 types of people that visit this board

 

1. those who come seeking help

2. those who spend their time here trying to help

3. those that come here to undermine,antagonize with the purpose of being argumentative

 

how do you view yourself?

try to be more supportive of others and youll more apt to be respected

Link to comment
Share on other sites

you know theres 3 types of people that visit this board

 

1. those who come seeking help

2. those who spend their time here trying to help

3. those that come here to undermine,antagonize with the purpose of being argumentative

how do you view yourself?

 

 

I think there are more types:

4. those that make a valid argument

5. those that defend undefendable Corsair problems.

 

I see myself in category 1, 2 and 4:

1. I reported a problem in a neutral way in an earlier post on BSOD but did not get a reply.

2. In that earlier post, reference was made to why Link could cause a problem. That could help Corsair development.

4. My argument is that software that causes BSOD is core to the use of a PC. And if the software is known to be non-compatible with an operating system, then it should be mentioned on the product site of that product.

 

You Sir, on the other hand, you look like in category 5, and on top of that, get personal when you don't like people's argument.

With that comment, I have become category 5 myself.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.


×
×
  • Create New...