Jump to content

StupidForumReg

Members
  • Posts

    1
  • Joined

Reputation

10 Good
  1. I just updated and now I cant seem to configure the "hardware lighting" setting without crashing the software each time. I can LOOK at it, but as soon as i access the drop-down to configure any new settings or try and change colors the whole program freezes and crashes. some of the settings stick so it seems like the changes stick until you powercycle your PC and nothing is different. im looking around to try and find a crash log but im coming up dry in the program folder. as far as microsoft can see: - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> - <System> <Provider Name="Windows Error Reporting" /> <EventID Qualifiers="0">1001</EventID> <Level>4</Level> <Task>0</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2019-06-19T00:17:31.737988800Z" /> <EventRecordID>1132</EventRecordID> <Channel>Application</Channel> <Computer>PersonalGear-3</Computer> <Security /> </System> - <EventData> <Data>1768803946511473381</Data> <Data>1</Data> <Data>APPCRASH</Data> <Data>Not available</Data> <Data>0</Data> <Data>iCUE.exe</Data> <Data>3.16.56.0</Data> <Data>5cd2f74b</Data> <Data>iCUE.exe</Data> <Data>3.16.56.0</Data> <Data>5cd2f74b</Data> <Data>c0000005</Data> <Data>0139e2f0</Data> <Data /> <Data /> <Data>\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5E84.tmp.dmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6059.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER606A.tmp.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER606E.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER609E.tmp.txt</Data> <Data>\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_iCUE.exe_57ea8fa65180aa2819dddbc618d8d5811eba196_e88d88f1_ce80d139-865a-485f-a722-7adcefaaa35c</Data> <Data /> <Data>0</Data> <Data>253bf0b9-ab4e-4ddc-9171-0c636ea587d7</Data> <Data>268435456</Data> <Data>8e44928826419678888c0dd15d201ae5</Data> <Data>0</Data> </EventData> </Event> so its generally unhelpful because some of these hex values kind of only make sense to microsoft. the only thing i could really find that seems like it might be of some help is a fault offset: Faulting application name: iCUE.exe, version: 3.16.56.0, time stamp: 0x5cd2f74b Faulting module name: iCUE.exe, version: 3.16.56.0, time stamp: 0x5cd2f74b Exception code: 0xc0000005 Fault offset: 0x0139e2f0 Faulting process id: 0x262c Faulting application start time: 0x01d526342906b1ca Faulting application path: C:\Program Files (x86)\Corsair\CORSAIR iCUE Software\iCUE.exe Faulting module path: C:\Program Files (x86)\Corsair\CORSAIR iCUE Software\iCUE.exe Report Id: 9c916cac-c61a-4976-a7fe-1ffd59627be6 Faulting package full name: Faulting package-relative application ID: when looking at the fault offset it says crashing might happen when you input a procedure that has more than 4000 characters. now the values may be arbitrary and not relevant since the context of that discovery was for SQL for windows server, but given how many config values this program handles it may have seen yet another configuration and pushed it past its "threshold." but then again i know nothing about programming. hence why im here asking all you guys thanks for any help
×
×
  • Create New...