Lefy8880

My budget is around 100 to 150 max euros. For some components I'll try to RMA them. But is going to be very difficult and it will take time.

Already done that. I have mentioned it before. I have put manual timings and tested them with memtest86. No errors. I'm going to buy(upgrade?) mobo first (I dont have some much money just to buy new pc... This is 4 months old) Can you suggest one better than this? Maybe x570? I think it has more support than older motherboards.

When I analyze the dmp file for WHEA Logger it shows this...... ******************************************************************************* * * * 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 WHEA_ERROR_RECORD structure that describes the error conditon. Arguments: Arg1: 0000000000000000, Machine Check Exception Arg2: ffffd88f2dcbec00, Address of the WHEA_ERROR_RECORD structure. Arg3: 00000000bea00000, High order 32-bits of the MCi_STATUS value. Arg4: 0000000000000108, Low order 32-bits of the MCi_STATUS value. Debugging Details: ------------------ fffff8041640f2a8: Unable to get Flags value from nt!KdVersionBlock fffff8041640f2a8: Unable to get Flags value from nt!KdVersionBlock ************************************************************************* *** *** *** *** *** 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 *** *** *** ************************************************************************* fffff8041640f2a8: Unable to get Flags value from nt!KdVersionBlock ************************************************************************* *** *** *** *** *** 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 *** *** *** ************************************************************************* KEY_VALUES_STRING: 1 Key : Analysis.CPU.Sec Value: 2 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on DESKTOP-5L769R4 Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.Sec Value: 3 Key : Analysis.Memory.CommitPeak.Mb Value: 73 Key : Analysis.System Value: CreateObject Key : WHEA.MCiStatus.Code Value: 0xbea0000000000108 Key : WHEA.MCiStatus.McaError Value: 0x0108 Key : WHEA.MCiStatus.ModelError Value: 0x0000 Key : WHEA.MCiStatus.Reserved Value: 0x00a00000 ADDITIONAL_XML: 1 DUMP_FILE_ATTRIBUTES: 0x18 Kernel Generated Triage Dump Live Generated Dump BUGCHECK_CODE: 124 BUGCHECK_P1: 0 BUGCHECK_P2: ffffd88f2dcbec00 BUGCHECK_P3: bea00000 BUGCHECK_P4: 108 PROCESS_NAME: smss.exe STACK_TEXT: ffff8105`55a53080 fffff804`1616a40f : ffffd88f`2dcbebe0 00000000`00000000 ffffd88f`2dcbec00 000000fc`6bd9f5c0 : nt!LkmdTelCreateReport+0x13e ffff8105`55a535c0 fffff804`1616a306 : ffffd88f`2dcbebe0 fffff804`00000000 00000000`00000000 00000000`00000022 : nt!WheapReportLiveDump+0x7b ffff8105`55a53600 fffff804`15fc1fed : 00000000`00000001 ffff8105`55a53b80 00000000`00000022 00000000`000001a8 : nt!WheapReportDeferredLiveDumps+0x7a ffff8105`55a53630 fffff804`15e381a8 : 00000000`00000000 ffffd88f`325db000 00000000`00000000 00000000`00000000 : nt!WheaCrashDumpInitializationComplete+0x59 ffff8105`55a53660 fffff804`15bef378 : ffffd88f`320d0000 ffffd88f`320dd400 ffff8105`55a53b80 ffffd88f`00000000 : nt!NtSetSystemInformation+0x928 ffff8105`55a53b00 00007ff8`5aece2c4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28 000000fc`6bd9f568 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`5aece2c4 MODULE_NAME: AuthenticAMD IMAGE_NAME: AuthenticAMD.sys STACK_COMMAND: .thread ; .cxr ; kb FAILURE_BUCKET_ID: LKD_0x124_0_AuthenticAMD_BANK0_MSCOD0000_MCACOD0108_PCC_UC_IMAGE_AuthenticAMD.sys OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {509acb9c-038f-dfdb-adc2-7917670271d1} Followup: MachineOwner --------- What does that means?

Update. Still getting random reboots and event viewer shows "WHEA-Logger Event ID-18" Even when I'm in discord or browsing internet. What do you suggest to try? New mobo? New PSU?

Update. CPU Cooler has been installed. ASUS BIOS 5406 moded profile has been set to correct wrong cpu clock speed (3.59 and not 3.60ghz) - by deactivating CPU Spread Spectrum. I seted manually ram timings. To correct them by using ram calculator and ran ram testing with memtest(no errors). Just to be sure there is no problems with my rams. Temps are perfect. Max cpu temp 72 Cº. Same with gpu. Max temp 70-75 Cº with custom fan curve. No reboots-hardcrash second day by only doing some benchmarks. Haven't tried games so far. I'll report back if anything happens.

I got news guys. (I'm still waiting for my new cpu cooler.) I did a bios downgrade and update. went to 5007 and then back to 5406 at ASUS BIOS. then reinstalled windows with all latests drivers. AMD chipset and Radeon Drivers. I still have the same reboots and hard crashes. but this time I also get a WHEA Logger Event ID:18 A fatal hardware error has occurred. Reported by component: Processor Core Error Source: Machine Check Exception Error Type: Cache Hierarchy Error Processor APIC ID: 0 (Sometimes Processor APIC ID is 2,3,4,5-9) Tried some fixes that I found on web. Like: -Disabling AMD External Events Utility. -Do some changes in the Power Plan. Set almost everything to Max Performance. -Reinstalled CPU and Cooler again Still the problem hasn't gone away. If anyone knows more about this Event or what it might be causing it please help us.

I reinstall again my cpu and the cpu cooler, no difference. AMD drivers enterprise didn't make any change. I changed drivers back to 20.4.2 again. New cpu cooler is on the way. Arctic Freezer II 360. Which can cool down also the vrms. To see if there is any difference. I hope it will. If it doesn't I will get a bigger PSU. Somewhere at 750-850 watts. It's time to spend some more money.

Hey. So is this a problem? Heatsink is too close to those capasitors. Maybe when cpu heats up is causing the reboots?

Ok. I'll try 1803 version thnx. As I said before from my last testing with another computer my rx 5700xt is working fine. And also no drivers issues anymore since last drivers. The problem is when i out this gpu in my rig. Im not getting bsod (blue or black) and no drivers glitch efc. I'm getting a hard crash and then reboot at certain games.

I have already tried the CPU cooler reinstall. But I can give it a go one more time. Also I wasn't able to find any version before the 1909 to download. I you know any way tell me. But how you explain that my pc with the other gpu(rx 570) works just fine?

So. Today I went to my brothers house and put my rx 5700 xt at his Intel PC. Intalled 20.4.2 drivers and everything worked just fine(2k most games and high settings to streed it). no crashes. no reboots. no bsod. Then I tried his GPU (RX570) in my pc and the same. No problems. No reboots neither bsods. Then I swapped PSU's (He has the same model with mine but cx550m) and puted in my pc with the rx 5700 xt to see if the PSu is the problem but reboots came back again. -Also tried it with XMP disabled and enabled. -Also changed cables for GPU. -Went back to 1909 version of windows because at moment I had 2004. What I have noticed is that my bros computer, exept that he has Intel Build, he also has old version of Windows(1903). I remember reading that windows updates can cause problems to drivers etc. I will try go back to the exact windows version to see if it makes a difference. What do all of you think about those results of my testing? EDIT: Or I just need a bigger psu. Sadly I dont have any more than 650watts to test it. Only if I buy one. But at this time I'm trying to solve it without spending more money that I already have. Also I cant downgrade my windows to 1903. So I'll update it to 2004 and also the drivers to 20.5.1. I saw somewhere in the web for some is the most stable of all time. I'll report back.

nice program. I tried it. All temps are good. GPU max was at 70-80 same for CPU. But it doesnt show vrms temps. I was able to play for a little time AC Unity(The game before was boosting my gpu to max even in the menu for no reason and then gave me a hard crash). What I did was use ddu again and install drivers version 20.4.2. Then changed again Clock speed to 1905mhz and set to 999mv. Nothing else. I'll post screenshots here of my temps etc at the moment of crash. but they seems normal to me. Again no Minidump file. See the pictures and tell me. I will continue testing but in the end I'll go to the shop to test it with bigger PSU.

No minidump files. For days now. Since the new drivers. I checked my VRM temps. They seems fine. I'll run again the games that hard crash and see the temps and usage for everything. Do you know any good program that keeps log file of those?

The third one. Link: PowerColor Radeon™ RX 5700 XT 8GB GDDR6 (600w minimum) Reporting back after few days without reboots. (Using right now 20.5.1 drivers). Problem came back. Still havent changed my PSU. Finished two games - Assasins Creed Black Flag and the Rogue. Also played for 2-3 days GTA V. Then I open Unity and here we go again. Same with Syndicate. I played for about 15 min and had a hard Crash. Tried 3 different tunings and dif powerplans still the same. When i open Unity my GPU sounds like turboing to max for no reason while I'm in the menu. Don't know why. Seems like reboots happen to certain games only now. Tried everything. One thing that seems to solved my problem for this few days was after I was turning off my pc I also set to OFF my PSU. any ideas?

The minidump file is very old. I dont have that type of issue anymore. I mean drivers isn't a problem now. This 3 days was my best days since I build my pc. Playing 1440p high settings without a problem. I dont know exactly what fixed it. All I did was change some settings in adrenaline. Also I dont think that rx5700xt is a bad gpu. Its good. Very good. I was lucky and got it for only 250euros. When the price was at 580euros. So yes. It was the best option at the moment. For that reason I cant change it . I test it for a week to see if problem with the reboots will come back. I post back here for news. ( I Still believe that PSU is the problem here )