Application: LEDKeeper2.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.NullReferenceException
at MSI_LED.CSDK_Handler..ctor()
at MSI_LED.App.Application_Startup(System.Object, System.Windows.StartupEventArgs)
at System.Windows.Application.OnStartup(System.Windows.StartupEventArgs)
at System.Windows.Application.<.ctor>b__1_0(System.Object)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.DispatcherOperation.InvokeImpl()
at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Windows.Threading.DispatcherOperation.Invoke()
at System.Windows.Threading.Dispatcher.ProcessQueue()
at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
at System.Windows.Threading.Dispatcher.PushFrame(System.Windows.Threading.DispatcherFrame)
at System.Windows.Application.RunDispatcher(System.Object)
at System.Windows.Application.RunInternal(System.Windows.Window)
at System.Windows.Application.Run(System.Windows.Window)
at System.Windows.Application.Run()
at MSI_LED.App.Main()
-
- Nov 4, 2012
-
- 9,812
-
- 153
-
- 55,890
- 2,199
-
#2
looks like it is in C:Program Files (x86)MSIMysticLight directory.
you should look for a update the these drivers.
——-
first bugcheck
LEDKeeper.exe
called to a driver that used a memory address it no longer owned. this resulted in a bugcheck.
(most likely a program bug)
————-
Other issues you have some old drivers:
SystemRootsystem32driversSiLib.sys Thu Jul 15 15:08:26 2010
SystemRootsystem32driversSiUSBXp.sys Thu Jul 15 15:27:13 2010
(this is likely to cause issues with your usb subsystem, you should remove these drivers)
and a overclocking driver installed:
C:Program Files (x86)MSIMysticLightLibNTIOLib_X64.sys Sun Jul 9 19:13:57 2017
remove this old overclock driver and install a current version for your newer CPU (if you really must have the overclocking)
————
Machine ID Information [From Smbios 2.8, DMIVersion 0, Size=4807]
BiosMajorRelease = 5
BiosMinorRelease = 13
BiosVendor = American Megatrends Inc.
BiosVersion = 1.60
BiosReleaseDate = 08/08/2019
SystemManufacturer = Micro-Star International Co., Ltd.
SystemProductName = MS-7B17
SystemFamily = Default string
SystemVersion = 1.0
SystemSKU = Default string
BaseBoardManufacturer = Micro-Star International Co., Ltd.
BaseBoardProduct = MPG Z390 GAMING PRO CARBON (MS-7B17)
BaseBoardVersion = 1.0
[CPU Information]
~MHz = REG_DWORD 4008
Component Information = REG_BINARY 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
Configuration Data = REG_FULL_RESOURCE_DESCRIPTOR ff,ff,ff,ff,ff,ff,ff,ff,0,0,0,0,0,0,0,0
Identifier = REG_SZ Intel64 Family 6 Model 158 Stepping 13
ProcessorNameString = REG_SZ Intel(R) Core(TM) i9-9900KS CPU @ 4.00GHz
Update Status = REG_DWORD 2
VendorIdentifier = REG_SZ GenuineIntel
MSR8B = REG_QWORD be00000000
-
- Nov 4, 2012
-
- 9,812
-
- 153
-
- 55,890
- 2,199
-
#2
looks like it is in C:Program Files (x86)MSIMysticLight directory.
you should look for a update the these drivers.
——-
first bugcheck
LEDKeeper.exe
called to a driver that used a memory address it no longer owned. this resulted in a bugcheck.
(most likely a program bug)
————-
Other issues you have some old drivers:
SystemRootsystem32driversSiLib.sys Thu Jul 15 15:08:26 2010
SystemRootsystem32driversSiUSBXp.sys Thu Jul 15 15:27:13 2010
(this is likely to cause issues with your usb subsystem, you should remove these drivers)
and a overclocking driver installed:
C:Program Files (x86)MSIMysticLightLibNTIOLib_X64.sys Sun Jul 9 19:13:57 2017
remove this old overclock driver and install a current version for your newer CPU (if you really must have the overclocking)
————
Machine ID Information [From Smbios 2.8, DMIVersion 0, Size=4807]
BiosMajorRelease = 5
BiosMinorRelease = 13
BiosVendor = American Megatrends Inc.
BiosVersion = 1.60
BiosReleaseDate = 08/08/2019
SystemManufacturer = Micro-Star International Co., Ltd.
SystemProductName = MS-7B17
SystemFamily = Default string
SystemVersion = 1.0
SystemSKU = Default string
BaseBoardManufacturer = Micro-Star International Co., Ltd.
BaseBoardProduct = MPG Z390 GAMING PRO CARBON (MS-7B17)
BaseBoardVersion = 1.0
[CPU Information]
~MHz = REG_DWORD 4008
Component Information = REG_BINARY 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
Configuration Data = REG_FULL_RESOURCE_DESCRIPTOR ff,ff,ff,ff,ff,ff,ff,ff,0,0,0,0,0,0,0,0
Identifier = REG_SZ Intel64 Family 6 Model 158 Stepping 13
ProcessorNameString = REG_SZ Intel(R) Core(TM) i9-9900KS CPU @ 4.00GHz
Update Status = REG_DWORD 2
VendorIdentifier = REG_SZ GenuineIntel
MSR8B = REG_QWORD be00000000
| Thread starter | Similar threads | Forum | Replies | Date |
|---|---|---|---|---|
|
K
|
Question Are python.exe and python3.exe present under «App Execution aliases» By default ? | Windows 10 | 2 | Jan 17, 2023 |
|
|
[SOLVED] My anti virus took my visual studio output EXE because it is a trojan horse? lol | Windows 10 | 7 | Jan 1, 2023 |
|
|
Question BSOD Everyday for 3 Months NTOSKRNL.exe | Windows 10 | 3 | Oct 15, 2022 |
|
B
|
Question Can’t run most .exe files after game crash | Windows 10 | 1 | Sep 22, 2022 |
|
L
|
Question BSODs on wake from sleep, or randomly | Windows 10 | 2 | Aug 29, 2022 |
|
C
|
Question BSOD IRQL_NOT_LESS_OR_EQUAL | Windows 10 | 3 | Jul 15, 2022 |
|
L
|
Question IRQL_NOT_LESS_OR_EQUAL | Windows 10 | 1 | May 18, 2022 |
|
A
|
Question Weird warning window | Windows 10 | 8 | May 4, 2022 |
|
V
|
[SOLVED] IRQL_not_less_or_equal BSOD when trying to install Windows 10 | Windows 10 | 8 | Mar 11, 2022 |
|
|
[SOLVED] multiple bsod (ntoskrnl, ntoskrnl) — lenovo thinkpad yoga15 | Windows 10 | 9 | Jan 29, 2022 |
- Advertising
- Cookies Policies
- Privacy
- Term & Conditions
- Topics
-
- Nov 4, 2012
-
- 9,812
-
- 153
-
- 55,890
- 2,199
-
#2
looks like it is in C:Program Files (x86)MSIMysticLight directory.
you should look for a update the these drivers.
——-
first bugcheck
LEDKeeper.exe
called to a driver that used a memory address it no longer owned. this resulted in a bugcheck.
(most likely a program bug)
————-
Other issues you have some old drivers:
SystemRootsystem32driversSiLib.sys Thu Jul 15 15:08:26 2010
SystemRootsystem32driversSiUSBXp.sys Thu Jul 15 15:27:13 2010
(this is likely to cause issues with your usb subsystem, you should remove these drivers)
and a overclocking driver installed:
C:Program Files (x86)MSIMysticLightLibNTIOLib_X64.sys Sun Jul 9 19:13:57 2017
remove this old overclock driver and install a current version for your newer CPU (if you really must have the overclocking)
————
Machine ID Information [From Smbios 2.8, DMIVersion 0, Size=4807]
BiosMajorRelease = 5
BiosMinorRelease = 13
BiosVendor = American Megatrends Inc.
BiosVersion = 1.60
BiosReleaseDate = 08/08/2019
SystemManufacturer = Micro-Star International Co., Ltd.
SystemProductName = MS-7B17
SystemFamily = Default string
SystemVersion = 1.0
SystemSKU = Default string
BaseBoardManufacturer = Micro-Star International Co., Ltd.
BaseBoardProduct = MPG Z390 GAMING PRO CARBON (MS-7B17)
BaseBoardVersion = 1.0
[CPU Information]
~MHz = REG_DWORD 4008
Component Information = REG_BINARY 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
Configuration Data = REG_FULL_RESOURCE_DESCRIPTOR ff,ff,ff,ff,ff,ff,ff,ff,0,0,0,0,0,0,0,0
Identifier = REG_SZ Intel64 Family 6 Model 158 Stepping 13
ProcessorNameString = REG_SZ Intel(R) Core(TM) i9-9900KS CPU @ 4.00GHz
Update Status = REG_DWORD 2
VendorIdentifier = REG_SZ GenuineIntel
MSR8B = REG_QWORD be00000000
-
- Nov 4, 2012
-
- 9,812
-
- 153
-
- 55,890
-
- 2,199
-
#2
looks like it is in C:Program Files (x86)MSIMysticLight directory.
you should look for a update the these drivers.
——-
first bugcheck
LEDKeeper.exe
called to a driver that used a memory address it no longer owned. this resulted in a bugcheck.
(most likely a program bug)
————-
Other issues you have some old drivers:
SystemRootsystem32driversSiLib.sys Thu Jul 15 15:08:26 2010
SystemRootsystem32driversSiUSBXp.sys Thu Jul 15 15:27:13 2010
(this is likely to cause issues with your usb subsystem, you should remove these drivers)
and a overclocking driver installed:
C:Program Files (x86)MSIMysticLightLibNTIOLib_X64.sys Sun Jul 9 19:13:57 2017
remove this old overclock driver and install a current version for your newer CPU (if you really must have the overclocking)
————
Machine ID Information [From Smbios 2.8, DMIVersion 0, Size=4807]
BiosMajorRelease = 5
BiosMinorRelease = 13
BiosVendor = American Megatrends Inc.
BiosVersion = 1.60
BiosReleaseDate = 08/08/2019
SystemManufacturer = Micro-Star International Co., Ltd.
SystemProductName = MS-7B17
SystemFamily = Default string
SystemVersion = 1.0
SystemSKU = Default string
BaseBoardManufacturer = Micro-Star International Co., Ltd.
BaseBoardProduct = MPG Z390 GAMING PRO CARBON (MS-7B17)
BaseBoardVersion = 1.0
[CPU Information]
~MHz = REG_DWORD 4008
Component Information = REG_BINARY 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
Configuration Data = REG_FULL_RESOURCE_DESCRIPTOR ff,ff,ff,ff,ff,ff,ff,ff,0,0,0,0,0,0,0,0
Identifier = REG_SZ Intel64 Family 6 Model 158 Stepping 13
ProcessorNameString = REG_SZ Intel(R) Core(TM) i9-9900KS CPU @ 4.00GHz
Update Status = REG_DWORD 2
VendorIdentifier = REG_SZ GenuineIntel
MSR8B = REG_QWORD be00000000
| Thread starter | Similar threads | Forum | Replies | Date |
|---|---|---|---|---|
|
K
|
Question Are python.exe and python3.exe present under «App Execution aliases» By default ? | Windows 10 | 2 | Jan 17, 2023 |
|
|
[SOLVED] My anti virus took my visual studio output EXE because it is a trojan horse? lol | Windows 10 | 7 | Jan 1, 2023 |
|
|
Question BSOD Everyday for 3 Months NTOSKRNL.exe | Windows 10 | 3 | Oct 15, 2022 |
|
B
|
Question Can’t run most .exe files after game crash | Windows 10 | 1 | Sep 22, 2022 |
|
L
|
Question BSODs on wake from sleep, or randomly | Windows 10 | 2 | Aug 29, 2022 |
|
C
|
Question BSOD IRQL_NOT_LESS_OR_EQUAL | Windows 10 | 3 | Jul 15, 2022 |
|
L
|
Question IRQL_NOT_LESS_OR_EQUAL | Windows 10 | 1 | May 18, 2022 |
|
A
|
Question Weird warning window | Windows 10 | 8 | May 4, 2022 |
|
V
|
[SOLVED] IRQL_not_less_or_equal BSOD when trying to install Windows 10 | Windows 10 | 8 | Mar 11, 2022 |
|
|
[SOLVED] multiple bsod (ntoskrnl, ntoskrnl) — lenovo thinkpad yoga15 | Windows 10 | 9 | Jan 29, 2022 |
- Advertising
- Cookies Policies
- Privacy
- Term & Conditions
- Topics