cancel
Showing results for 
Search instead for 
Did you mean: 

Graphics

landolf
Adept I

Re: RX 5700 XT PC reboots on APEX

I had a similar problem with a new build, sometimes there was still sound, but mostly it was just both screens turning black and an instant reboot.

After changing GPU for another custom 5700 xt, changing PSU to a 750 platinum and every tweak I could find (2 different PCIe-cables for GPU, set PCIe-slot to 3rd gen, since I use a x570 board, updated Windows, GPU drivers, reinstall drivers without setting any profile when installing, installing 5 different older GPU drivers and many more), I contacted AMD and told them what my problem was. 

For me, the solution was to change my memory. I have the 3800 xt which safely supports up to 3200 MHz, I was using 3600 MHz memory. After changing it in my bios to 3200 MHz, it was stable and the crashes were gone. I then changed to a 2x8 GB cl14 G.Skill Flare X, single rank (F4-3200C14D-16GFX) kit, got the timings a little tighter 14-14-13-28, so it was still safe according to DRAM Calculator for Ryzen. I even overclocked the GPU a little now, haven't had any problems since.

I hope that helps!

0 Likes
marcelma95
Adept II

Re: RX 5700 XT PC reboots on APEX

Were you experiencing startup issues as well? For me I am having very similar problems with my 5600 XT but for me the larger issue isn't crashing during games but crashing at startup. I have identical error messages but I am unable to see any specific program that has issues other than the LEDKeeper2 and other mystic light program.

0 Likes
marcelma95
Adept II

Re: RX 5700 XT PC reboots on APEX

Below are the logs from the event viewer that i experienced. :

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.CControl.ResetItem(Int32)
at MSI_LED.App.CloseAPP()
at MSI_LED.WindowToGetHandle.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at System.Windows.Interop.HwndSource.PublicHooksFilterMessage(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)

Faulting application name: LEDKeeper2.exe, version: 1.0.0.67, time stamp: 0x5ed5f5db
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc000041d
Fault offset: 0x07382d9b
Faulting process id: 0x21ac
Faulting application start time: 0x01d64aaa578eb16e
Faulting application path: C:\Program Files (x86)\MSI\One Dragon Center\Mystic_Light\LEDKeeper2.exe
Faulting module path: unknown
Report Id: 84bddcbf-08b6-4a68-acd6-9b84a1e95b1b
Faulting package full name:
Faulting package-relative application ID:

Faulting application name: LEDKeeper2.exe, version: 1.0.0.67, time stamp: 0x5ed5f5db
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x07382d9b
Faulting process id: 0x21ac
Faulting application start time: 0x01d64aaa578eb16e
Faulting application path: C:\Program Files (x86)\MSI\One Dragon Center\Mystic_Light\LEDKeeper2.exe
Faulting module path: unknown
Report Id: 652ed6d6-2743-4335-998e-540671712481
Faulting package full name:
Faulting package-relative application ID:

0 Likes