dgingeri Posted February 16, 2016 Share Posted February 16, 2016 I recently got a H110i GT cooler, and the cooler itself works great, but as soon as I installed the software, everything went south. When I rebooted after the install, I got a WHEN_uncorrectable_error bluescreen. I found that if I unplugged the USB cable from the cooler, it would boot, but then many of my programs would start throwing up errors. After about 3-5 minutes after login, it would bluescreen with a "Page_Fault_in_nonpaged_area" and reboot. The uninstaller also would not remove the software. It would hang at 40%. I tried uninstalling the USB drivers first, and that just rendered my system entirely unbootable. Before the H110i GT install, everything was perfectly stable. After using system restore back to the pre-corsair link config, I was able to get back to perfect working order. The cooler still works great, but I cannot get Corsair Link to work at all. Three hours of panic and headaches is not nice. I just reinstalled the OS on this machine a couple weeks ago, and I near panicked at the thought of having to do it again. System specs: Windows 10 Pro with all the latest patches and every version of .net framework available for Windows 10 Core i7 4930k on an Asus P9X79-E WS & 32GB DDR3-1600 Samsung 850 Pro 512GB boot drive (Magician 4.9.5 installed with Rapid mode enabled) Geforce GTX980 Ti and GTX680 (EVGA PrecisionX installed) Dell PERC H710 for file storage (drive config irrelevant) Eset Smart Security antivirus Battle.net client, Arc Client, several games through both, Office 365 Home, many other programs that I could list upon request, if needed. Link to comment Share on other sites More sharing options...
Toasted Posted February 17, 2016 Share Posted February 17, 2016 So installing the LINK software will cause the system to BSOD to a "PAGE_FAULT_IN_NONPAGED_AREA" message? I don't think i've seen that ever come from software as the message is mostly related to RAM. If you want to give the LINK software a go, i'd try the v3.X.X software, else use System Information Viewer (SIV) a third party software created by red-ray which should work with the cooler as well. You can find SIV here; http://forum.corsair.com/v3/showthread.php?t=140665 Link to comment Share on other sites More sharing options...
dgingeri Posted February 17, 2016 Author Share Posted February 17, 2016 Does the 3.2 version support Windows 10? I didn't think it would. Link to comment Share on other sites More sharing options...
Toasted Posted February 18, 2016 Share Posted February 18, 2016 3.2.5676 onwards supports Windows 10. See this thread for the list of previous LINK releases; http://forum.corsair.com/v3/showthread.php?t=125350 Link to comment Share on other sites More sharing options...
dgingeri Posted February 21, 2016 Author Share Posted February 21, 2016 Well, it sort of worked. The system doesn't bluescreen on startup, and Corsair Link starts, but it complains that it has discovered new devices and requires a reboot on every boot. This may be the H110i GT, because it doesn't list that device on the interface, only my motherboard and video cards. Link to comment Share on other sites More sharing options...
red-ray Posted February 21, 2016 Share Posted February 21, 2016 it complains that it has discovered new devices and requires a reboot on every boot. http://forum.corsair.com/forums/showthread.php?t=153706 is how I dealt with the silly reboot popups Link to comment Share on other sites More sharing options...
dgingeri Posted February 22, 2016 Author Share Posted February 22, 2016 Thanks! I'll try it tonight, if I get the time. Link to comment Share on other sites More sharing options...
dgingeri Posted February 23, 2016 Author Share Posted February 23, 2016 That did it! Thanks a bunch. It's too bad 4.2 behaved so badly. 3.2 works, though, with a little hack. Link to comment Share on other sites More sharing options...
red-ray Posted February 23, 2016 Share Posted February 23, 2016 That did it! Thanks a bunch. It's too bad 4.2 behaved so badly. 3.2 works, though, with a little hack. Good, I suspect it would "bluescreen with a Page_Fault_in_nonpaged_area" To me you initial issue report about CL 4.1.0.162 does not seem likely. CL4 has more than it's fair share of issues, but yours if the only BSOD report I have noted. I would analyse the dump files in C:\Windows\Minidump using WINDBG to check what caused the issue, see http://forum.corsair.com/forums/showthread.php?p=760776. Link to comment Share on other sites More sharing options...
dgingeri Posted February 28, 2016 Author Share Posted February 28, 2016 Even 3.2 with that fix didn't work after all. I found my USB detection quit working while CL was running, plus after I added an HX1000i, the WHEA_uncorrectable_error came back on boot. Oh, and Red-ray, the bluescreen I got when 4.2 was installed but the H110i GT was unplugged pointed to a cpuz138.sys file, which does not point to CL, but my system was perfectly stable before the install of 4.2, and returned to stable after I did a system restore. The only thing that changed was the CL install. Sure, I have a ton of stuff running on my system, but all those programs run with each other with no issues. The only program I have installed in the last several years that caused instability has been Corsair Link, in any version going all the way back to 2.0. (I owned an H100i before I bought the H110i GT. That cooler went to my server.) To say I've been disappointed with Corsair Link over the years would be a vast understatement. Link to comment Share on other sites More sharing options...
red-ray Posted February 28, 2016 Share Posted February 28, 2016 Oh, and Red-ray, the bluescreen I got when 4.2 was installed but the H110i GT was unplugged pointed to a cpuz138.sys file, which does not point to CL You may think that but... You should also add you PC specs to you profile as issues such as this typically only happen on a few systems, so the exact system information is needed. cpuz138.sys is part of the CPUID SDK which both CL3 + CL4 use to report the motherboard sensors, DIMM temperatures and all the other none CL hardware. Report the bug via https://corsair.secure.force.com/home/home.jsp, ZIP then upload the crash dump file and request they fix it. Link to comment Share on other sites More sharing options...
dgingeri Posted February 29, 2016 Author Share Posted February 29, 2016 Interesting info. I had thought it was just part of CPU-z that I keep running on my secondary screen for monitoring, but I use a newer version than 1.38. I have updated my systems specs in my profile, but I was not able to locate the core dump from those previous bluescreens, probably because I didn't let them finish saving before I hit the reset button. Link to comment Share on other sites More sharing options...
red-ray Posted February 29, 2016 Share Posted February 29, 2016 I had thought it was just part of CPU-z that I keep running on my secondary screen for monitoring, but I use a newer version than 1.38. They should be in C:\Windows\Minidump. For W10 specifying the build would be good as TH1, TH2 and all the RS1s are rather different. On my system CPUZ 1.75.0.x64 uses the cpuz139_x64.sys driver. Maybe having both drivers active at the same time on your system triggers the issue. Were the issue with any of kernel mode drivers I have developed I suspect I could easily fix it once I had the crash dump file, so would expect (hope?) the same to be the case for the cpuz driver developer. Link to comment Share on other sites More sharing options...
dgingeri Posted March 11, 2016 Author Share Posted March 11, 2016 OK, I'm happy now. I put in the new 4.2.1, and it is running perfectly. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.