CorsairLink V2.2.0 Bluescreen and more

I first uninstalled V2.1.7 and after a reboot installed V2.2.0. After leaving the machine idle for about an hour (no keyboard and mouse action) the machine stops with a bluescreen:

STOP: 0x0000001E (0x0000000000000000, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000).

Then I restored my system from an image before installing V2.1.7 and did a fresh install of V2.2.0.

The result is the same, after been idle for about 1 hour, the machine chrashes with a bluescreen.

I disabled all powersaving settings.

When I was testing I wanted to use logging to get the time of failure, but no matter what interval I use in the logging section, there are about 10 lines per second written.

Can you attach your minidumps as a .zip file here?

What lines were written when you were logging?

Latest BIOS, drivers for everything?

may not have anything to do with this... but it is worth asking....

What version of Intel RSTe drivers are you running?

After installing V2.1.7 I left the machine idle for 3 hours, no problem.

Then I installed V2.2.0 and started logging, after 3 hours the machine was still running. Then I stopped the logging and the machine crashed after about 1.5 hours.

I include a minidump file and a part of the logfile.

I'm using Intel® C600 Series Chipset SATA RAID Controller driver 3.5.1.1008.

I use the latest bios and drivers.

Dmp112412-23306-01.zip

logFile.zip

Only way you will be able to get out of the blue screen, is to use a prior version of RSTe than 3.5.1 or 3.5.0.

I got the same problem here, my PC, which was insanly stable, started to blue screen all of a sudden for nothing, but only since i installed CorsairLink 2.1.7.

There is a thread here that discuss this problem with RSTe 3.5.1 drivers... think 3.5.0 does the same thing. So you have to make a choice here... Keep RSTe and get rid of CorsairLink 2.1.7 (maybe 2.2.0 is same).

Or get rid of RSTe 3.5.1 or and install something prior to 3.5.0... that sucks, i know, but it`s the only way out for now.

I will try an older RSTe version, but I don't think it is a RSTe problem but a problem with CorsairLink 2.2.0.

V2.1.7 runs fine.

I see you are running Windows 8, I'm running Windows 7.

I will give Windows 8 a try today.

I can tell you i had problem with both Windows 7 and windows 8 with the RSTe 3.5.1 and 2.1.7 software... as soon as i downgraded the RSTe... the bluescreen stopped..

I agree with you, nothing is wrong with RSTe... i am pretty darn sure the culprit is Corsair's software...

I will try an older RSTe version, but I don't think it is a RSTe problem but a problem with CorsairLink 2.2.0.

V2.1.7 runs fine.

I see you are running Windows 8, I'm running Windows 7.

I will give Windows 8 a try today.

This is my only my view.

I am running the new Corsair link 2.2.0. The moment I install Intel RSTe 3.5, I got BSOD. I have a thread that I made and alot of people are having similar problems. If I put Intel RSTe 3.0.. all is fine.

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

If I have Intel RSTe 3.5 install without the Corsair Link 2.2.0, I don't get any BSOD.

Before Corsair even says this is a big issue, they need to replicate the problem first. I am not sure if they are doing anything about it yet but time will tell. But, as I have said, more and more people are having this issue.

GOOD LUCK!!!!

We have adamantly stated Windows 8 is not supported at this time so there is nothing we can do until we have a Windows 8 compatible version of our software and proper driver support.

Can you tell us if this is being worked on currently? And maybe even a rough ETA?

We have adamantly stated Windows 8 is not supported at this time so there is nothing we can do until we have a Windows 8 compatible version of our software and proper driver support.

I am not running windows 8. I am running windows 7 and yes I already knew that since their are many threads that says this.

I did specify that in my thread that I have going on about this exact issue and in my pc specs. :biggrin:

So what I said before is still valid and the new software 2.1.7 does not work with Intel RSTe 3.5 because it is always doing the BSOD.

And if corsair does even check the forums, in the thread I made about this... their are multiple people that are having this issue.

The only person that does not have this issue is running very old software for the link.

So I will say this statement agian:

Before Corsair even says this is a big issue, they need to replicate the problem first. I am not sure if they are doing anything about it yet but time will tell.

uninstall the old RST(e) drivers and install these afterwards:

http://drivers.softpedia.com/get/Other-DRIVERS-TOOLS/INTEL/Intel-RSTe-and-AHCI-Driver-3003020.shtml

problem exists if you install any newer version of RST(e). with version 3.0.0.3020 you may install the newest LINK software without problems.

this is a known problem with LINK and RST ...

I can tell you i had problem with both Windows 7 and windows 8 with the RSTe 3.5.1 and 2.1.7 software... as soon as i downgraded the RSTe... the bluescreen stopped..

 

I agree with you, nothing is wrong with RSTe... i am pretty darn sure the culprit is Corsair's software...

Corsair Link 2.2 does make my computer to restart unplanned also with Intel RSTe 3.5 in Win 8 64it. But now the Corsair say they don't have drivers to Win 8 yet, it seems a bit odd. Do they not want to sell their product too Win 8 customers?

And whey does it seems that a lot of the Hxx/xi seriers and maybe also Hxx/x have damaged radiators (bend metal ), even if they work it doesen't look good?

Rassel:

I use your settings for the overclock (Thanx for them) that I you have written on another forum and thought that was the wrong for me, even if Prime95 worked out well, but the unplanned restart (did'ent see the BSOD) even was at the standard CPU speed with just XMP setting in bios just for the memory getting the right value and not only when it was overclocked, so then the OC was not the problem, then when I tested to restart the computer it just "hanged" and when I instead used shutdown it said tha sierra_ something failed... And that is for the Corsair link, when I have uninstalled that, the computer have been working all the night, even if my mouse stopped working last night (somehing more to look up for me)...

So I think I going to the get the OC settings back.

But the second part om Prime 95 my CPU went up to 71C and I have the H100i in Push/pull config. Put in part 1 just just went up to like 65-66C

Is that okey you think? But more questions I take on the other forum if possible.

Is it possible to find RSTe 3.0 somewhere? if I want to use the Corsair Link anyway until the get working drivers and so on for Win 8.

BR

// Patrik

But now the Corsair say they don't have drivers to Win 8 yet, it seems a bit odd.

That is odd, especially as the drivers are Microsoft's own HID drivers :bigeyes::eek::eek:

See previous post for RSTe 3.0

I get this message when I trying to go to that page:

"404 - page not found"

I can still access the page. But as always Google is your best friend.

First hit: http://www.soft-go.com/download_driver/Intel-RSTe-and-AHCI-Driver-3.0.0.3020-for-Win7x64_50703.html

We have adamantly stated Windows 8 is not supported at this time so there is nothing we can do until we have a Windows 8 compatible version of our software and proper driver support.

I am getting frequent BSOD now and searching around for the cause. I run Windows 8. I suspect the Corsair H80i Link and found several references on different forums to problems with the H80i Corsair Link.

I am surprised that you say that Corsair adamantly stated Windows 8 is not supported. Originally I looked at the H80i on the Corsair website, and on the product page for the H80i, THERE IS NO MENTION THAT WINDOWS 8 IS NOT SUPPORTED.

I feel conned because when you want to sell the H80i on the product page, you are hiding essential information.

 

I feel conned because when you want to sell the H80i on the product page, you are hiding essential information.

no offense

considering that win8 is so new id would have checked first if it were a concern to me

it does take time to redo things for a completely new OS

no offense

considering that win8 is so new id would have checked first if it were a concern to me

it does take time to redo things for a completely new OS

no offense

I am not a specialist and when I buy a product, as a non-expert user I would expect that it would work with a released OS and which was in the making for a long time.

On the other hand, Corsair is a specialist, they knew and it would have been a small thing to add a note with the H80i on their product page.

A court would consider that Corsair has a higher duty here being the specialist and having knowledge of the problem.

If MS would release a new Office suite and it would not be compatible with Win 8 and they would not inform about that on their product page or on the box they sell, you would cry murder.

i understand your point however corsair cant begin the coding for win8 until it has been released as it isnt available to them.

have you tried using the win7 compatibility mode to get it working?

i understand your point however corsair cant begin the coding for win8 until it has been released as it isnt available to them.

have you tried using the win7 compatibility mode to get it working?

I understand what you are saying, but am still of the opinion that Corsair should have mentioned the non-compatible Win 8 situation on the H80i product page.

Thanks for the suggestion with the win7 compatibility mode. But I am not a specialist. How do I do that.