Razer Synapse Conflicting with rewasd 7.1 Causing Bsod

[Tekknen]

I have a razer ornata v2 Keyboard i'm using Synapse 3 just for RPG LED Configuration, i had no problem with both Razer Synapes 3 working along rewasd until i updated rewasd from 7.0 to 7.1 last update. that when i stared to get all kind of blue Screen

• IRQL_NOT_LESS_OR_EQUAL
• PAGE_FAULT_IN_NONPAGED_AREA
• SYSTEM_SERVICE_EXCEPTION
• DPC_WATCHDOG_VIOLATION
• MACHINE_CHECK_EXCEPTION

not only that loging into win11 safe mode give annoying warning
"The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application."
which is caused by rewasd. i know this because i did a reformate to my pc, getting a clean boot windows. the message only reappeared after installing rewasd

is there a way to fix the conflict between the two app

[1ncorrect]

1. What steps lead to a BSOD?
2. Have you tried to go through the basic steps of troubleshooting this BSOD from the Internet? This BSOD may be caused by driver issues.
3. Do you have dump file of the BSOD? You should be able to locate it via this path %SystemRoot%memory.dmp (i.e. C:\Windows\memory.dmp by default).
Please, check it and send us dump file to find the BSOD reason.

[Tekknen]

1. What steps lead to a BSOD?

As soon as system start and razer synapse start to load.

2. Have you tried to go through the basic steps of troubleshooting this BSOD from the Internet? This BSOD may be caused by driver issues.

blue screen vary so i diced to reformat which system is stable now except for a single MACHINE_CHECK_EXCEPTION Bsod afters hours of running while watching media from firefox browser. but as soon I try installing Razer software crashes return

;n2419073. Do you have dump file of the BSOD? You should be able to locate it via this path %SystemRoot%memory.dmp (i.e. C:\Windows\memory.dmp by default).
Please, check it and send us dump file to find the BSOD reason.

PROCESS_NAME: System

STACK_TEXT:
ffff9701`81b8fac8 fffff803`50d009ec : 00000000`0000009c 00000000`80000001 ffff9701`81b8fb00 00000000`00000000 : nt!KeBugCheckEx
ffff9701`81b8fad0 fffff803`50d00f2c : 00000000`00000008 ffff9701`81b8fe50 00000000`00000000 394e5546`0170384e : nt!HalpMcaReportError+0x154
ffff9701`81b8fc40 fffff803`50d00092 : 00000000`00000000 00000000`80000001 ffff9701`81b8fed0 064da00f`4ba15354 : nt!HalpMceHandlerWithRendezvous+0x11c
ffff9701`81b8fc70 fffff803`50d0285b : ffffe40b`ee5688a0 000a0a4c`534d4c7a 5652544c`8800070a 4c534d4c`7b700000 : nt!HalpHandleMachineCheck+0x62
ffff9701`81b8fca0 fffff803`50d68f39 : 00070a00`0a0a4c53 00020a56`52544c88 ff0b4c53`4e4c7b70 0a565254`4c880003 : nt!HalHandleMcheck+0x3b
ffff9701`81b8fcd0 fffff803`50c28c7e : a0080a30`5f545f93 00315243`45125b19 01315243`459310a0 a4030a69`959208a0 : nt!KiHandleMcheck+0x9
ffff9701`81b8fd00 fffff803`50c28893 : 00000000`00000010 00000000`00000000 00000000`00000000 ffff9701`81b8fed0 : nt!KxMcheckAbort+0x7e
ffff9701`81b8fe40 fffff803`6be3156f : fffff803`6be315c4 00000000`00000000 00000000`00000000 ffffa5f5`6f35ca6f : nt!KiMcheckAbort+0x2d3
ffffa90d`92e5f4d8 fffff803`6be315c4 : 00000000`00000000 00000000`00000000 ffffa5f5`6f35ca6f 00000000`00000000 : intelppm!MWaitIdle+0x1f
ffffa90d`92e5f4e0 fffff803`50a1125f : 00000000`00000000 00000000`0000007f 00000000`ffffffff 00000011`00aa92d5 : intelppm!AcpiCStateIdleExecute+0x24
ffffa90d`92e5f510 fffff803`50a10c11 : ffffe40b`f84e5718 ffff9701`81b60100 ffffe40b`ffffffff ffffa90d`92e5f9b0 : nt!PpmIdleExecuteTransition+0x41f
ffffa90d`92e5f950 fffff803`50c1bb14 : 00000000`00000000 00000000`00000000 ffffe40b`ee5c3080 ffffe40c`02033080 : nt!PoIdle+0x361
ffffa90d`92e5fb40 00000000`00000000 : ffffa90d`92e60000 ffffa90d`92e59000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x54


SYMBOL_NAME: intelppm!MWaitIdle+1f

MODULE_NAME: intelppm

IMAGE_NAME: intelppm.sys

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 1f

FAILURE_BUCKET_ID: 0x9C_SPURIOUS_GenuineIntel_intelppm!MWaitIdle

OS_VERSION: 10.0.22621.1

BUILDLAB_STR: ni_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {1132fd1e-b4e3-34d7-1215-2712eb51da30}

Followup: MachineOwner
---------

2: kd> .f+
01 ffff9701`81b8fad0 fffff803`50d00f2c nt!HalpMcaReportError+0x154

[strokel]

Hi. Could you please go to Preferences, disable the LED in the LED settings section, and check if this issue persists?