Corsair iCUE Lighting Software Crashed My System.

[eidairaman1]

admittedly I didn't read every line. waaay to long. just skimmed and found that.

Yeah 4x 3600 on Zen2, not gonna happpen. Probably will top out at 2933.

3200 at most depends on what mobo maker specifies

 

[Mussels]

3200 at most depends on what mobo maker specifies

It's more about what the CPU can handle than the board these days, some boards (like my ITX one) do have their own limits, but those limits apply regardless of the CPU

We all know higher SoC will raise that limit, we just don't know how high since not many people try 8 ranks

 

[Forum_Posts23]

It's more about what the CPU can handle than the board these days, some boards (like my ITX one) do have their own limits, but those limits apply regardless of the CPU

We all know higher SoC will raise that limit, we just don't know how high since not many people try 8 ranks

Thank you for the help on this I'll give SoC a try. Honestly, though I'm confused by this since the system has worked without issues until I added the Lian Li SL Infinity fans with the L-Connect3. Literally not even a system hang. Same memory and timings just different kits I changed from 2 kits of 2x16 to an identical spec only 1 kit of 4x16 instead. The Memory is on the QVL for both G.Skill and ASUS related to the board. I do not have any extra device hubs other than the Lian Li SL Inf controller and since the only things, Corsair is the keyboard, mouse, and headset I don't see how this applies. I've been running this same setup for 3+ years without any issues until now. In fact, at this very moment I've been successfully running the system without issue for about a week so long as iCue is not installed. I know it's a really long post and I'm sorry but you don't know what you don't know. I have put a lot of money and work into this so I want to be as thorough as possible to save all parties time and frustration. I really truly appreciate the feedback.

Please do not write this off as resolved this is not yet corrected. The REAL problem here is that I NEED iCue. I'm 75% blind and use a software called ZoomText which uses muli-key commands such as "ALT+SHIFT+PageUp" to increase the Zoom level so I can see the screen. I bought the Corsair K95 keyboard for dedicated macro keys which I can't program without iCue. So you see I need to have L-Connect3 for the SL infinity fans due to the proprietary control and I need iCue for macro use. Otherwise, I couldn't care any less about RGB crap other than backlighting to assist in finding the keys on the keyboard.

 

[Mussels]

Icue is a pain in the asss

Remember that SoC problems are related to all PCI-E, USB and memory controller issues - you can simply have connected another USB device causing the voltages to drop on the USB part of the SoC and bam, the issues start because now the rams controllers not receiving the power it should be


You can replace the Lian li software with openRGB, just untick the corsair boxes so it doesnt conflict with them

"2x16 to an identical spec only 1 kit of 4x16 instead."

That's exactly the issue. You've doubled the amount of work the memory controller has to do, and you cannot run the same clock speeds doing so. Heres my favourite images i keep on my desktop since i explain this so often.

Those "OC upto" are with voltage increases and by de-syncing the IF and memory controller which badly hurts performance

4x2 rank? Look at that, you're only "safe" for 2933, 3600 with voltage increases

 

[ir_cow]

Those "OC upto" are with voltage increases and by de-syncing the IF and memory controller which badly hurts performance

4x2 rank? Look at that, you're only "safe" for 2933, 3600 with voltage increases

I pretend Gear 2 (2:1 FCLK) doesn't exist for Ryzen (DDR4). Unless you need the memory, it really does hurt perf.

 

[Forum_Posts23]

Icue is a pain in the asss

Remember that SoC problems are related to all PCI-E, USB and memory controller issues - you can simply have connected another USB device causing the voltages to drop on the USB part of the SoC and bam, the issues start because now the rams controllers not receiving the power it should be


You can replace the Lian li software with openRGB, just untick the corsair boxes so it doesnt conflict with them

"2x16 to an identical spec only 1 kit of 4x16 instead."

That's exactly the issue. You've doubled the amount of work the memory controller has to do, and you cannot run the same clock speeds doing so. Heres my favourite images i keep on my desktop since i explain this so often.

Those "OC upto" are with voltage increases and by de-syncing the IF and memory controller which badly hurts performance

4x2 rank? Look at that, you're only "safe" for 2933, 3600 with voltage increases

So to fully understand and explain this last part so I can complete the new testing in one shot I'll up the SoC to 1.18 (between your recommended 1.15 and 1.2) and I'll reinstall iCue and see how things fair.

I have had 64GB of memory since day 1. I only changed from 2 kits of 2x16 to 1 kit of 4x16.

So literally the only change was to swap fans from board-controlled PWM to the proprietary connector SL Infinity fans that require the L-Connect3 software to control the fan speed. the board knows there are fans but without the L-Connect3 software passthrough to Armoury Cate for control or using the L-Connect3 directly for fan control the fans will not change speeds. If Open RGB will control the Lian Li controller from fan speed then I'm all for it, I just require iCue from the keyboard no matter what and it was working fine before the new fans.

 

[eidairaman1]

So to fully understand and explain this last part so I can complete the new testing in one shot I'll up the SoC to 1.18 (between your recommended 1.15 and 1.2) and I'll reinstall iCue and see how things fair.

I have had 64GB of memory since day 1. I only changed from 2 kits of 2x16 to 1 kit of 4x16.

So literally the only change was to swap fans from board-controlled PWM to the proprietary connector SL Infinity fans that require the L-Connect3 software to control the fan speed. the board knows there are fans but without the L-Connect3 software passthrough to Armoury Cate for control or using the L-Connect3 directly for fan control the fans will not change speeds. If Open RGB will control the Lian Li controller from fan speed then I'm all for it, I just require iCue from the keyboard no matter what and it was working fine before the new fans.

Contact corsair for assistance

 

[Forum_Posts23]

after changing the SoC now I'm getting BSoD errors within 10-15 minutes of power-on and I haven't made another change of any kind.

 

[AMF]

It's been 3 years since the post was created but there are still issues with this at least for me. Any additional help would be great.

First and foremost my machine has been functional for over 3 years without fail until now. Here is what has been done so far.

Since 12/12/2022, I have updated all drivers to the latest versions for everything be it the Fan controller, AMD drivers, Nvidia drivers, BIOS, Armoury Crate, Corsair iCue, L-Connect3, and all software on the machine. I also purchased and replaced the power supply (Again) on 12/16/2022 to EVGA 1300 GT (1300 Watts) from the EVGA 1300 G+ (1300 Watts) and I’m still having the same problem. At this point between the warranty exchanges and new purchases, I almost have enough parts to build a new PC. I need this fixed I'm 75% blind and this machine is my only means of working since I use software for magnifying everything.

At this point in my journey:
Current configuration:
CPU: AMD Ryzen 9 3950X
Motherboard – ASUS ROG Crosshair VIII Hero (WI-FI)
Memory - G.Skill Trident Z neo
F4-3600C16Q-64GTZNC
DDR4-3600 CL16-19-19-39 1.35V
64GB (4x16GB)
GPU: ASUS ROG-STRIX-RTX3090-O24G-WHITE
CPU Cooler: ASUS ROG RYUJIN II 360
Power Supply: EVGA Supernova 1300 GT
Case Fans: Lian Li SL120 Infinity (x9)
Add-In: Asus TPM-M R2.0 14-1 Pin TPM Module
NVMe: x2 Samsung 980 PRO SSD 2TB NVMe Gen 4 M.2
SSD: x3 Samsung 870 EVO 2TB 2.5 Inch SATA III
Keyboard/Mouse/Headset:
Corsair K95 RGB Platinum XT Mechanical Gaming Keyboard
Corsair Dark Core RGB Pro SE, Wireless FPS/MOBA Gaming Mouse
Corsair VIRTUOSO RGB WIRELESS XT High-Fidelity Gaming Headset

Issue:

• For approximately 5 months my PC will hard stop for seemingly no reason at very random times without any similarities to previous crashes. Sometimes it will crash while playing a game, other times I could be in the middle of a VMWare work session, looking at an MS Word document, or even just leaving the computer completely idle with all work processes closed overnight without anything being touched. Additionally, prior to replacing motherboard, I would also periodically get a boot error indicating BIOS corruption and needing to restore using “USB Flashback”.

When this occurs:

• The monitor display either freezes to the current image or goes black/blank.
• There is no change in QCODE.
  • Typical boot from a cold state QCODE is either CPU temp or AA, which is normal.
• The DRAM LED (amber color) comes on.
• At this point, there is no function from the motherboard.
  • Case power button whether held for up to a minute or not.
  • The case reset button will not work.
  • Onboard “Start” and “Reset/AUX” keys do not function.
  • All case fans still rotate and LEDs stay on as well as the GPU stays lit.
• The only way to get back to a working state is to:
  • Toggle the power switch on the PSU
  • Use the onboard “SAFE _BOOT” or “RETRY_BUTTON” from the motherboard.

What has been done thus far:

• Ran both Memtest86 and Windows Memory Diagnostics (both failed with errors in one way or another.)
• Set UEFI back to defaults and retested with same results.
• Swapped memory:
  • Original: G.Skill Trident Z neo
    • F4-3600C16D-32GTZNC
    • DDR4-3600 CL16-19-19-39 1.35V
    • 32GB (2x16GB)
      • **2 kits 4 sticks total
  • New replacement: G.Skill Trident Z neo
    • F4-3600C16Q-64GTZNC
    • DDR4-3600 CL16-19-19-39 1.35V
    • 64GB (4x16GB)
• Tested new memory and passed in default and D.O.C.P. configuration. (left in D.O.C.P.)
• Still having same original issue for about a week.
• Swapped GPU:
  • Original: ROG-STRIX-RTX2080TI-O11G-GAMING
    • **RMA swap to TUF-RTX3080TI-O12G-GAMING
  • 1ST replacement: TUF-RTX3080TI-O12G-GAMING
  • 2nd replacement: ROG-STRIX-RTX3080TI-O12G-GAMING
    • *New purchase
  • 3nd replacement: ROG-STRIX-RTX3090-O24G-WHITE
    • *New purchase
  • 4th MSI Gaming 1660 Super
    • *New purchase
• Used each GPU for about 2-3 weeks before swapping to the next to no avail. The current GFPU in use is the 3090.
• Rolled back UEFI BIOS to Version 2204 (2020/08/14) then back forward to Version 4201 (2022/04/29).
• Swapped PSU
  • Original: SilverStone Technology 800W SFX-L, 80 Plus Titanium
  • Current: EVGA Supernova 1300 G
• Still same issues
• Nuked Windows 10 Pro and removed all NVMe/SSD drives except for the boot NVMe drive.
• Reinstalled Windows 10 PRO (fully activated retail copy).
• Reinstalled all required software.
• No change system is still crashing to Amber DRAM light.
• Swapped CPU Cooler:
  • Original: Lian Li GA-240A Galahad AIO 240
  • New: ASUS ROG RYUJIN II 360
• There are no extension cables being used inside or outside of the computer chassis other than a surge protector.
• The system still continues to randomly crash.
• Replaced the motherboard via RMA to the same product that was changed 11/29/2022.
• Since 12/12/2022, I have updated all drivers to the latest versions for everything be it Fan controller, AMD drivers, Nvidia drivers, BIOS, Armoury Crate, Corsair iCue, and all software on the machine. I also purchased and replaced the power supply (Again) 12/16/2022 to EVGA 1300 GT (1300 Watts) from the EVGA 1300 G+ (1300 Watts).
• The most recent change made to single out the issues was to reinstall each software driver one-by-one. Everything is now working flawlessly with everything reinstalling EXCEPT iCue. I have tested both versions of iCue (v4.31.168 and v3.38.88 (For Legacy Devices)) and the same for L-Connect3 (Current version: v1.5.18 Posted: 12/20/2022 and "For UNI FAN SL-INF users, please keep using"V1.3.16.)
  • Just to clarify I do not currently have iCue installed period and L-Connect3 v1.3.16 is installed.
• All that having been said I have not ever had issues with iCue and ASUS Aura working together and I have not had issues with L-Connect3 and ASUS Aura working together. It seems though that iCue and L-Connect3 with or without ASUS Aura consistently conflict.

If not for a literal life need (75% blind) I wouldn't need or care if iCue was ever installed but unfortunately I need it to configure the macro keys on the K95 keyboard (which is the most important regardless of RGB) since that's first why I bought the keyboard and the macros are used to facilitate the magnifier multi-key functions. Additionally, since the Lian-Li fans are the SL-INF 3=packs I have to have the controller due to proprietary fan connections rather than direct to motherboard cables. Without L-Connect3 I can't control the fans even by passthrough. I really need someone's help to figure this out.

Thank you so so much in advance for any help.

PS: There are no BSOD logs due to being a hard stop. I do have crash dump reports from GPU-z which is packaged into the L-Connect3 software and is used by L-Connect3 to monitor the system for fan control.

try changing mem timings to 16 20 20 20 38 51 mem voltage to 1.375 to check for stability issues swap your mem sticks in thier slots make sure they are in correct slots also try using just 2 sticks in dual channel slots maybe update bios ? stability issues i had same thing happen to me i updated and fixed it load optimized defaults restart see what happens

 

[Gmr_Chick]

I use iCue on all my various systems and dont have these issues

Some Asus boards are having problems detecting corsair RAM on the latest version, but nothing like what you're describing.

Update your BIOS and see how it goes, you likely have some other RGB software conflicting (asus aura? or wahtever they call it)

Wait....so you're actively using iCUE now? I thought you hated it? You made a whole thread about it and everything

 

[A Computer Guy]

Wait....so you're actively using iCUE now? I thought you hated it? You made a whole thread about it and everything

Yea this is interesting. I reinstalled my system not too long ago and have been contemplating if I should try the newest iCue 4 (install is twice as big as v3) or just install an older version iCue 3 I knew worked for me but uncertain if it will have issues with the newer Windows 10 21H2 or newer. I'm deadlocked on the decision and haven't reinstalled any version.

 

[Mussels]

So to fully understand and explain this last part so I can complete the new testing in one shot I'll up the SoC to 1.18 (between your recommended 1.15 and 1.2) and I'll reinstall iCue and see how things fair.

I have had 64GB of memory since day 1. I only changed from 2 kits of 2x16 to 1 kit of 4x16.

So literally the only change was to swap fans from board-controlled PWM to the proprietary connector SL Infinity fans that require the L-Connect3 software to control the fan speed. the board knows there are fans but without the L-Connect3 software passthrough to Armoury Cate for control or using the L-Connect3 directly for fan control the fans will not change speeds. If Open RGB will control the Lian Li controller from fan speed then I'm all for it, I just require iCue from the keyboard no matter what and it was working fine before the new fans.

Armoury crate too?
Yeah these softwares do NOT play well together.
You need to ditch anything you do not 100% NEED and move to lightweight alternatives

Example: Icue may be needed for drivers for certain things, but do you need it running in the tray? If not, disable auto start with windows


F off armoury crate and lian lis software, and go through the nightmare of actually removing it - you need debloating tools and manually disabling services and deleting hidden files they leave behind.

When they're gone, use third party programs like openRGB and FanControl, disabling support for corsair things still ran by icue to prevent issues
The key to these programs is they're set and forget, you can have them run the settings you want and then quit them - openRGB has a "load X profile on exit" option that is amazing for this very purpose


Get rid of the software conflicts and wasted resources, and your PC is going to run a whole lot better

after changing the SoC now I'm getting BSoD errors within 10-15 minutes of power-on and I haven't made another change of any kind.

You did jump right up to high voltages, you should start at 1.10v and then 1.125v, 1.15v etc
higher isnt always more stable

Can you post Zentimings screenshots of what it looks like?

 

[Forum_Posts23]

Armoury crate too?
Yeah these softwares do NOT play well together.
You need to ditch anything you do not 100% NEED and move to lightweight alternatives

Example: Icue may be needed for drivers for certain things, but do you need it running in the tray? If not, disable auto start with windows


F off armoury crate and lian lis software, and go through the nightmare of actually removing it - you need debloating tools and manually disabling services and deleting hidden files they leave behind.

When they're gone, use third party programs like openRGB and FanControl, disabling support for corsair things still ran by icue to prevent issues
The key to these programs is they're set and forget, you can have them run the settings you want and then quit them - openRGB has a "load X profile on exit" option that is amazing for this very purpose


Get rid of the software conflicts and wasted resources, and your PC is going to run a whole lot better


You did jump right up to high voltages, you should start at 1.10v and then 1.125v, 1.15v etc
higher isnt always more stable

Can you post Zentimings screenshots of what it looks like?
View attachment 277288

I'm already down to bear necessities as far as I can tell. This is not a gaming rig. Yes, I occasionally play something from time to time but this is mainly a lab machine running VMWare with servers and multiple machines running 85% of its active time. Sure I have enthusiast parts and whatnot but they have a purpose.

Yes, I can nuke Armoury Crate (AC) but I get my screen readout from it on the ASUS ROG RYUJIN II 360 display.
iCue is actively needed for keyboard macro buttons to function.
As I've said though the fans will not register PWM control without L-Connect3 (LC), I know this because before I ever installed AC I had FanControl (FC), and not only did it not find the Lian Li Hub plugged into the CPU Fan header but it only found 2 out of 3 fans on the GPU. So I left it installed and installed AC. Still no luck with FC, so here I am with AC and LC installed. Still doesn't resolve the iCue issue but we're working on it.

I didn't crank the SoC exactly as stated. I actually set it to 1.08v (+.12v) so that it could flex.

 

[Mussels]

You're likely going to have a real bad time with armoury crate and icue together, definitely look into alternate ways to run that display


Keep working on the SoC voltage, and if it gets too high that it's unsafe (1.2v+) or causing too much CPU heat, then lower the DRAM frequency and IF clocks instead

 

[Forum_Posts23]

You're likely going to have a real bad time with armoury crate and icue together, definitely look into alternate ways to run that display


Keep working on the SoC voltage, and if it gets too high that it's unsafe (1.2v+) or causing too much CPU heat, then lower the DRAM frequency and IF clocks instead

I really don't want to count chickens before they hatch but looks like for now at least I'm stable. I have the SoC voltage set to 1.19375v and have found that my keyboard does have hardware-driven storage so I was able to set the corsair iCue functions with profiles, then nuked iCue. Fingers crossed. Although the SoC may have helped, I'm of the mind at this point it's LC3 that's the real problem here. I ran Windows Driver Verifier for about 10 hours today and more than once I hit IRQL less than and overrun buffers.

It would seem that anything monitoring hardware other than the LC3's GPU-Z version causes the system to crap itself. At least for me.

I'll share dumps if you care to review them, I'm still not the best at reading them.

Microsoft (R) Windows Debugger Version 10.0.25200.1003 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
*** wait with pending attach
************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
ModLoad: 00007ff6`595b0000 00007ff6`595f6000 C:\Users\garyw\AppData\Local\Programs\L-Connect 3\resources\gpuz.exe
ModLoad: 00007ffd`29f50000 00007ffd`2a148000 C:\Windows\SYSTEM32\ntdll.dll
ModLoad: 00007ffd`299b0000 00007ffd`29a6f000 C:\Windows\System32\KERNEL32.DLL
ModLoad: 00007ffd`27bc0000 00007ffd`27e92000 C:\Windows\System32\KERNELBASE.dll
ModLoad: 00007ffc`bf8f0000 00007ffc`bfc75000 C:\Users\garyw\AppData\Local\Programs\L-Connect 3\resources\GPU-Z64.dll
ModLoad: 00007ffd`28200000 00007ffd`282ae000 C:\Windows\System32\ADVAPI32.dll
ModLoad: 00007ffd`28c50000 00007ffd`28cee000 C:\Windows\System32\msvcrt.dll
ModLoad: 00007ffd`28d50000 00007ffd`28dec000 C:\Windows\System32\sechost.dll
ModLoad: 00007ffd`28df0000 00007ffd`28f15000 C:\Windows\System32\RPCRT4.dll
ModLoad: 00007ffd`27610000 00007ffd`27766000 C:\Windows\System32\CRYPT32.dll
ModLoad: 00007ffd`27ac0000 00007ffd`27bc0000 C:\Windows\System32\ucrtbase.dll
ModLoad: 00007ffd`29140000 00007ffd`2916b000 C:\Windows\System32\GDI32.dll
ModLoad: 00007ffd`27940000 00007ffd`27962000 C:\Windows\System32\win32u.dll
ModLoad: 00007ffd`22c90000 00007ffd`22ef3000 C:\Windows\SYSTEM32\d3d11.dll
ModLoad: 00007ffd`27830000 00007ffd`2793f000 C:\Windows\System32\gdi32full.dll
ModLoad: 00007ffd`25ed0000 00007ffd`25fc3000 C:\Windows\SYSTEM32\dxgi.dll
ModLoad: 00007ffd`27970000 00007ffd`27a0d000 C:\Windows\System32\msvcp_win.dll
ModLoad: 00007ffd`1db50000 00007ffd`1dd1e000 C:\Windows\SYSTEM32\d3d9.dll
ModLoad: 00007ffd`27f70000 00007ffd`28111000 C:\Windows\System32\USER32.dll
ModLoad: 00007ffd`29360000 00007ffd`2948a000 C:\Windows\System32\ole32.dll
ModLoad: 00007ffd`29490000 00007ffd`297e5000 C:\Windows\System32\combase.dll
ModLoad: 00007ffd`254f0000 00007ffd`25502000 C:\Windows\SYSTEM32\kernel.appcore.dll
ModLoad: 00007ffd`29290000 00007ffd`2935d000 C:\Windows\System32\OLEAUT32.dll
ModLoad: 00007ffd`29a70000 00007ffd`29ed8000 C:\Windows\System32\SETUPAPI.dll
ModLoad: 00007ffd`27770000 00007ffd`277be000 C:\Windows\System32\cfgmgr32.dll
ModLoad: 00007ffd`256f0000 00007ffd`25e82000 C:\Windows\SYSTEM32\windows.storage.dll
ModLoad: 00007ffd`27f30000 00007ffd`27f57000 C:\Windows\System32\bcrypt.dll
ModLoad: 00007ffd`25200000 00007ffd`2522f000 C:\Windows\SYSTEM32\dwmapi.dll
ModLoad: 00007ffd`1b2f0000 00007ffd`1b356000 C:\Windows\SYSTEM32\OLEACC.dll
ModLoad: 00007ffd`283b0000 00007ffd`28af4000 C:\Windows\System32\SHELL32.dll
ModLoad: 00007ffd`28f20000 00007ffd`28f75000 C:\Windows\System32\SHLWAPI.dll
ModLoad: 00007ffd`277c0000 00007ffd`27829000 C:\Windows\System32\WINTRUST.dll
ModLoad: 00007ffd`27070000 00007ffd`270a0000 C:\Windows\SYSTEM32\Wldp.dll
ModLoad: 00007ffd`204f0000 00007ffd`204fa000 C:\Windows\SYSTEM32\VERSION.dll
ModLoad: 00007ffd`1e8e0000 00007ffd`1e907000 C:\Windows\SYSTEM32\WINMM.dll
ModLoad: 00007ffd`1b360000 00007ffd`1b3f8000 C:\Windows\SYSTEM32\WINSPOOL.DRV
ModLoad: 00007ffd`290a0000 00007ffd`290d2000 C:\Windows\System32\IMM32.DLL
ModLoad: 00007ffd`27200000 00007ffd`27212000 C:\Windows\SYSTEM32\MSASN1.dll
ModLoad: 00007ffd`1b400000 00007ffd`1b69a000 C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.19041.1110_none_60b5254171f9507e\Comctl32.dll
ModLoad: 00007ffd`0e010000 00007ffd`0e053000 C:\Windows\SYSTEM32\feclient.dll
ModLoad: 00007ffd`21e90000 00007ffd`22141000 C:\Windows\SYSTEM32\iertutil.dll
ModLoad: 00007ffd`28ff0000 00007ffd`2909d000 C:\Windows\System32\shcore.dll
ModLoad: 00007ffd`273c0000 00007ffd`273ec000 C:\Windows\SYSTEM32\DEVOBJ.dll
ModLoad: 00007ffd`19d60000 00007ffd`1a4cf000 C:\Windows\SYSTEM32\nvapi64.dll
ModLoad: 00007ffd`1ff10000 00007ffd`1ff41000 C:\Windows\SYSTEM32\cryptnet.dll
ModLoad: 00007ffd`1fc70000 00007ffd`1fdb8000 C:\Windows\SYSTEM32\drvstore.dll
ModLoad: 00007ffd`26fc0000 00007ffd`26fcc000 C:\Windows\SYSTEM32\cryptbase.dll
ModLoad: 00007ffd`28390000 00007ffd`283ad000 C:\Windows\System32\imagehlp.dll
ModLoad: 00007ffd`26fd0000 00007ffd`26fe8000 C:\Windows\SYSTEM32\CRYPTSP.dll
ModLoad: 00007ffd`26680000 00007ffd`266b4000 C:\Windows\system32\rsaenh.dll
ModLoad: 00007ffd`27ea0000 00007ffd`27f22000 C:\Windows\System32\bcryptPrimitives.dll
ModLoad: 00007ffd`24f80000 00007ffd`2501e000 C:\Windows\system32\uxtheme.dll
ModLoad: 00007ffd`1e860000 00007ffd`1e89b000 C:\Windows\SYSTEM32\dxcore.dll
(5f8c.5f90): Security check failure or stack buffer overrun - code c0000409 (!!! second chance !!!)

 

[Mussels]

IRQL less than and overrun buffers.

IRQL errors are usually plain memory errors - too high clocked or too high timings, as opposed to the WHEA errors from the memory controller

 

[eidairaman1]

IRQL errors are usually plain memory errors - too high clocked or too high timings, as opposed to the WHEA errors from the memory controller

Sounds to me there is more problems than just the software

 

[Forum_Posts23]

I think I'll make this my final message, I hope!!!

Since Wed 1/3/23 (Happy New Year!), I can happily report after making the SoC changes, a Windows rollback, and reinstalling AC, LC3, and even iCUE I have not had any stability issues as of yet. LC3 has a newer version as of 1/4/23 which I believe is a considerable credit to the success just as much as anything else since it no longer relies on GPU-Z from what I can tell anyway.

Thank you all for your thoughts and help with this critical issue.

 

[RJARRRPCGP]

IRQL errors are usually plain memory errors - too high clocked or too high timings, as opposed to the WHEA errors from the memory controller

0x0000000a is likely not enough Vcore/core frequency too high. You may get that error during a Linpack failure. That error code is to me, often the meme of losing the CPU core lottery/bronze CPU sample.

I got that on a super-dud Pentium E2180.

You won't always get a WHEA for unstable core and you may get an application access-violation error report instead.