The Corsair User Forums  

Go Back   The Corsair User Forums > Corsair Product Discussion > iCUE Software

Notices

Reply
 
Thread Tools Search this Thread Rate Thread Display Modes
  #1  
Old 10-23-2019, 05:52 PM
mroselli mroselli is offline
Registered User
mroselli's PC Specs
 
Join Date: Oct 2019
Posts: 4
POST ID # = 1022168
mroselli Reputation: 10
Question iCue Drivers Causing BSOD

I tired to contact Corsair directly via product support but the response I got was to try reinstalling and that no the email could not be forwarded to software engineering.


I have been battling random BSOD ever since I put this PC together. I narrowed it down to Corsair software being the cause. When the PC crashes, it never succeeds to create a dump. I get a lot of LiveKernelEvent 144 (1003 or 3003) in the event log. I finally was able to get the Windows driver verifier to spit out some useful information when I enabled it with DDI compliance. Corsair driver immediately fails driver verifier as soon as PC boots.

The error code is with CorsairLLAccess.sys and indicates ... EDIT: <removed> - see post below. I decoded the bugcheck wrong, WinDbg shows the correct bug.

Does someone know how I can get this info to Corsair engineers ? I think the driver needs to be fixed. Do they browse this forum ?
Attached Files
File Type: zip icue_export_system_info_and_logs.zip (166.7 KB, 19 views)
File Type: zip 102119-6546-01dump.zip (30.0 KB, 14 views)

Last edited by mroselli; 10-29-2019 at 11:56 PM. Reason: Removed incorrect assertion
Reply With Quote
  #2  
Old 10-23-2019, 06:24 PM
c-attack c-attack is offline
Registered User
c-attack's PC Specs
 
Join Date: Jun 2014
Posts: 9,552
POST ID # = 1022174
c-attack c-attack Reputation: 107
Default

I imagine you tried reinstalling before starting down this road. I have passed it on to the iCUE software team, but I can't guarantee they will respond directly.

You're running a common processor on a popular motherboard. It seems unlikely this is hardware related. I don't want to tell you to go do a Windows clean install, but it seems like CUE and Windows are the two central elements. If it's not a CUE install corruption, then that leaves the other.
Reply With Quote
  #3  
Old 10-23-2019, 06:53 PM
mroselli mroselli is offline
Registered User
mroselli's PC Specs
 
Join Date: Oct 2019
Posts: 4
POST ID # = 1022178
mroselli Reputation: 10
Default

I have tried reinstalling iCue. Not Windows yet but I've done many DISM scan repair things and file system checks.

My understanding is that the driver verifier bugcheck indicates a software bug in the driver itself. Particularly the error code indicated in the dump file.

Thankfully the problem only occurs in idle loads and lately its frequency had decreased. It happened shortly after I updated iCue which is what renewed my interest in finding the root cause once more. All said I've probably spent 20 hours thus far attempting to narrow the cause.
Reply With Quote
  #4  
Old 10-23-2019, 07:57 PM
c-attack c-attack is offline
Registered User
c-attack's PC Specs
 
Join Date: Jun 2014
Posts: 9,552
POST ID # = 1022184
c-attack c-attack Reputation: 107
Default

OK, hang tight and don't pull the plug on the C: drive quite yet. Let's see if they can narrow the issue further.
Reply With Quote
  #5  
Old 10-23-2019, 08:55 PM
mroselli mroselli is offline
Registered User
mroselli's PC Specs
 
Join Date: Oct 2019
Posts: 4
POST ID # = 1022188
mroselli Reputation: 10
Default

The CorsairLLAccess64.sys on my PC is version 1.0.16.0, re-installing 3.21.88 iCue software put the same version (1.0.16.0) back on my PC. Thanks for the quick response, I appreciate it. I look forward to hearing back.
Reply With Quote
  #6  
Old 10-29-2019, 06:33 AM
Corsair James's Avatar
Corsair James Corsair James is offline
iCUE Product Manager
 
Join Date: Oct 2013
Location: Fremont, CA
Posts: 4,459
POST ID # = 1022608
Corsair James Reputation: 75
Default

I checked with our devs and analyzed your log. It looks like the problem is related to you enabling driver verifier custom settings for developers in Windows 10. Why did you do this?
__________________

iCUE - A CORSAIR Interface
https://www.corsair.com/us/en/icue
Reply With Quote
  #7  
Old 10-29-2019, 06:49 AM
deno1000 deno1000 is offline
Registered User
 
Join Date: Jul 2019
Posts: 11
POST ID # = 1022610
deno1000 Reputation: 10
Default

This is not problem of windows..a lot of people have probleam with this softwer after last firmware update.
My pc freez every 10min..I unistal ICUE and no problems...
Reply With Quote
  #8  
Old 10-29-2019, 11:55 PM
mroselli mroselli is offline
Registered User
mroselli's PC Specs
 
Join Date: Oct 2019
Posts: 4
POST ID # = 1022678
mroselli Reputation: 10
Default

Quote:
Originally Posted by Corsair James View Post
I checked with our devs and analyzed your log. It looks like the problem is related to you enabling driver verifier custom settings for developers in Windows 10. Why did you do this?
I did this because I needed evidence to support my claim that Corsair drivers are causing my computer to crash.

Enabling driver verifier on my PC allows me to test your driver for compatibility with Windows. As per my attached dump file, the driver is failing with bugcheck code 0xC4 and the following parameters (decoded using this webpage):

Code:
Parameter 1: 0x2000 - The Storport miniport driver passed a bad argument (a NULL pointer) to the StorPortInitialize routine.
Parameter 2: 0xfffff801e7121c5d - The first argument passed to the StorPortInitialize routine. This parameter is a pointer to the driver object that the operating system passed to the miniport driver in the first argument of the miniport driver's DriverEntry routine.
Parameter
Parameter 3: 0x0 (NULL) - The second argument passed to the StorPortInitialize routine. This parameter is a pointer to context information that the operating system passed to the miniport driver in the second argument of the miniport driver's DriverEntry routine.
This is odd because this driver is not a Storport miniport driver... and when I load the dump file in WinDbg, it indicates the following decode for C4:
Code:
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 0000000000002000, Code Integrity Issue: The caller specified an executable pool type. (Expected: NonPagedPoolNx)
Arg2: fffff801e7121c5d, The address in the driver's code where the error was detected.
Arg3: 0000000000000000, Pool Type.
Arg4: 000000004d4d4c43, Pool Tag (if provided).
This code integrity issue matches this web page description: https://docs.microsoft.com/en-us/win...grity-checking

Okay so I'm pretty sure this is actually a Code Integrity bugcheck fail (and a Microsoft documentation issue). It appears the driver is allocating a page with the executable bit set and it should not be doing that. Is that crash worthy? Deserving of a revision to the driver? I'll leave that to Corsair's discretion.

I'll try continuing to run Verifier on with Code Integrity disabled.

My initial comment:
Quote:
The error code is with CorsairLLAccess.sys and indicates that a Windows API function that should only be invoked while under passive IRQL level is being invoked while not in passive IRQL which leads to hangs and deadlock.
is incorrect. I was looking at the wrong bug check code (0x00020002 , the entry below the incorrect StorportInitialize() bugcheck). I'll edit the comment to reflect that.

I appreciate the developers taking a look. I'm at my wit's end trying to justify not throwing my brand new PC in the trash. I'll post back after I've ran verifier with CI disabled. Thanks again.
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -4. The time now is 03:21 PM.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2019, vBulletin Solutions, Inc.