avp.exe causing Blue Screen

[Tekknen]

for last 2 days I'm getting all kind of blue screens, when trouble shooting i found that no Bsod happen in safe mode. was not able to point on the real problem, i format my PC and started mongering it behavior after installing my programs step by step untill i found that AVP.exe, MS EDGE, Razer Softwares and intelppm.sys conflicting leading to Bsod

I can't fix the problem as i'm getting random crashes with the lowest app installed and immediate crash after installing any razer app

windbg report sample

Quote

******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* WHEA_UNCORRECTABLE_ERROR (124) A fatal hardware error has occurred. Parameter 1 identifies the type of error source that reported the error. Parameter 2 holds the address of the nt!_WHEA_ERROR_RECORD structure that describes the error condition. Try !errrec Address of the nt!_WHEA_ERROR_RECORD structure to get more details. Arguments: Arg1: 0000000000000000, Machine Check Exception Arg2: ffffa08ad3aa6028, Address of the nt!_WHEA_ERROR_RECORD structure. Arg3: 00000000b2000000, High order 32-bits of the MCi_STATUS value. Arg4: 0000000000030005, Low order 32-bits of the MCi_STATUS value. Debugging Details: ------------------ ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION *** *** *** ************************************************************************* *** WARNING: Check Image - Checksum mismatch - Dump: 0x20f835, File: 0x20f8bd - C:\ProgramData\Dbg\sym\BTHport.sys\5DA12F75203000\BTHport.sys KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 1843 Key : Analysis.Elapsed.mSec Value: 3352 Key : Analysis.IO.Other.Mb Value: 0 Key : Analysis.IO.Read.Mb Value: 0 Key : Analysis.IO.Write.Mb Value: 0 Key : Analysis.Init.CPU.mSec Value: 437 Key : Analysis.Init.Elapsed.mSec Value: 11522 Key : Analysis.Memory.CommitPeak.Mb Value: 139 Key : Bugcheck.Code.LegacyAPI Value: 0x124 Key : Dump.Attributes.AsUlong Value: 1008 Key : Dump.Attributes.DiagDataWrittenToHeader Value: 1 Key : Dump.Attributes.ErrorCode Value: 0 Key : Dump.Attributes.KernelGeneratedTriageDump Value: 1 Key : Dump.Attributes.LastLine Value: Dump completed successfully. Key : Dump.Attributes.ProgressPercentage Value: 0 Key : Failure.Bucket Value: 0x124_0_GenuineIntel_PROCESSOR__UNKNOWN_IMAGE_GenuineIntel.sys Key : Failure.Hash Value: {5371cb52-c3d9-558e-47d4-d31c09567ca2} BUGCHECK_CODE: 124 BUGCHECK_P1: 0 BUGCHECK_P2: ffffa08ad3aa6028 BUGCHECK_P3: b2000000 BUGCHECK_P4: 30005 FILE_IN_CAB: 022224-9500-01.dmp DUMP_FILE_ATTRIBUTES: 0x1008 Kernel Generated Triage Dump BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: avp.exe STACK_TEXT: fffff805`0c7e88e8 fffff805`088fef1b : 00000000`00000124 00000000`00000000 ffffa08a`d3aa6028 00000000`b2000000 : nt!KeBugCheckEx fffff805`0c7e88f0 fffff805`054d10c0 : 00000000`00000000 fffff805`0c7e89c9 ffffa08a`d3aa6028 ffffa08a`cbf50660 : nt!HalBugCheckSystem+0xeb fffff805`0c7e8930 fffff805`08a0e4bf : 00000000`00000000 fffff805`0c7e89c9 ffffa08a`d3aa6028 00000000`00000000 : PSHED!PshedBugCheckSystem+0x10 fffff805`0c7e8960 fffff805`0890094a : ffffa08a`d3b52580 ffffa08a`d3b52580 ffffa08a`cbf506b0 fffff805`08780a1e : nt!WheaReportHwError+0x38f fffff805`0c7e8a30 fffff805`08900da0 : 00000000`00000000 ffffa08a`00000003 ffff8100`bad11000 ffff8100`bad18000 : nt!HalpMcaReportError+0xb2 fffff805`0c7e8ba0 fffff805`08900c34 : ffffa08a`cbf68720 00000000`00000001 00000000`00000000 00000000`00000000 : nt!HalpMceHandlerCore+0x138 fffff805`0c7e8c00 fffff805`08900ed9 : 00000000`00000008 00000000`00000001 00000000`00000000 00000000`00000000 : nt!HalpMceHandler+0xe0 fffff805`0c7e8c40 fffff805`08900092 : 00000000`00000000 00000000`00000000 fffff805`0c7e8ed0 00000000`00000000 : nt!HalpMceHandlerWithRendezvous+0xc9 fffff805`0c7e8c70 fffff805`0890285b : ffffa08a`cbf68720 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalpHandleMachineCheck+0x62 fffff805`0c7e8ca0 fffff805`08968f39 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalHandleMcheck+0x3b fffff805`0c7e8cd0 fffff805`08828c7e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x9 fffff805`0c7e8d00 fffff805`08828893 : 00000000`00000010 00000000`00000000 ffffffff`ffffffff fffff805`0c7e8ed0 : nt!KxMcheckAbort+0x7e fffff805`0c7e8e40 fffff805`086b725e : 00000000`00000000 ffffffff`00000000 ffffa08a`db731080 00000000`00000000 : nt!KiMcheckAbort+0x2d3 ffff8100`bad176c0 fffff805`086b6be6 : 00000000`00000000 ffff8100`00000000 ffff8100`bad17868 fffff805`00000000 : nt!MiWaitForInPageComplete+0x1ce ffff8100`bad177c0 fffff805`086621b1 : 00000000`c0033333 00000000`00000001 00000000`6b14ca9c 00000000`00000000 : nt!MiIssueHardFault+0x246 ffff8100`bad178c0 fffff805`08827a29 : ffffa08a`dc140000 00000000`0710eaf0 00000000`0710fda0 00000000`00000000 : nt!MmAccessFault+0x331 ffff8100`bad179e0 00000000`6b116553 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x369 00000000`0720c42c 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x6b116553 MODULE_NAME: GenuineIntel IMAGE_NAME: GenuineIntel.sys STACK_COMMAND: .cxr; .ecxr ; kb FAILURE_BUCKET_ID: 0x124_0_GenuineIntel_PROCESSOR__UNKNOWN_IMAGE_GenuineIntel.sys OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {5371cb52-c3d9-558e-47d4-d31c09567ca2} Followup: MachineOwner

 

[Berny]

@Tekknen Welcome.

For BSODs caused by Kaspersky please contact Kaspersky Technical Support :

https://support.kaspersky.com/b2c/