cancel
Showing results for 
Search instead for 
Did you mean: 

Processors

sniperzee
Adept II

WHEA Logger Event ID 18

Computer Type: Desktop

GPU: Radeon RX 5700XT

CPU: Ryzen 5 3600

Motherboard: MSI B450 A Pro Max

RAM: GSkill Ripjaws 8GB X2 (16GB in total)

PSU: Thermaltake Smart RGB 700W

Case: Midtower with 1 stock fan

Operating System & Version: Windows 10 Pro Version 10.0.19041

GPU Drivers: Radeon Software (Adrenaline) 20.4.2

Chipset Drivers: AMD Chipset Software 2.5.4.352

Hard Disk: SSD - Crucial 1TB M2 Nvme

Background Applications: Happens irrespective of what applications running

Description of Original Problem: My newly built PC keeps on restarting randomly. Sometimes, it will run for 6-10 hours without any issue. Then other times it will simply restart when I open an application (browser, tabs, etc.) or games and sometimes it just restarts at its will. Every time it restarts, the event logger logs the below errror:

"A fatal hardware error has occurred.

Reported by component: Processor Core Error Source: Machine Check Exception Error Type: Cache Hierarchy Error Processor APIC ID: 11

The details view of this entry contains further information."

Troubleshooting: I have updated all the drivers. Deleted and reinstalled and updated all the drivers. Checked if the CPU fan is properly attached to the CPU, if GPU is properly attached, if RAMs are properly attached, and everything else. All of them seem perfectly fitted. Used various software to test CPU, GPU, RAM, etc. All came back with good results. Did memory test and DISM test. Both were successful without any error.

245 Replies

Setting look correct.

It should blue screen and then stay on the bluescreen until you press the power button.

0 Likes

But that is the catch, i did not get any BSOD and i did not press the power button.

It automatically stopped and automatically started without any intervention.

I was trying to run GTA V Benchmark when this restart happened and event viewer says the same WHEA logger with Event ID 18.

May be i am doing something wrong.

0 Likes

Non blue screen restarts are usually heat or power related.

0 Likes

Yes, this is usually the case, but the rx5700 is an exception. Me and hundreds of other people in other threads, monitored temperatures, checked memory for errors, changed power supplies over and over again to no avail. Temperatures are ok, memory is ok, new expensive PSU's, everything is useless. PC is unstable without a clear reason (for me the reason is clear, it is navi gpu's) A couple of days ago I upgraded to insider build 20H2 and the whea-logger errors seem to be gone. But everything else is in place, including freezes, black screens, and so on. The only thing is that they seem to be happening less often, but I'm not sure yet.

0 Likes

I too did not face any problem when i had a GTX 970.

Then i got this ASUS RX 5700XT and not a single day has passed without these Black screen, Freezes and what not.

 

But i have played few old games released before 2015 like Heavy Rain, Beyond Two Souls, Crysis 3 and i did not face any issue with them.

 

I do not know what is wrong with the GPU

0 Likes

What is your gpu model? If not a reference, you can try your luck by updating vbios from the asus website. This helped some reddit users get a stable system.

0 Likes

This is ASUS TUF 5700XT..I have updated the VBIOS every time they released a new one on their website.

Nothing changed till now.

0 Likes

Hi fyrel,

I just got a sudden restart today.

I can see from the event viewer, there are multiple ERROR and CRITICAL incidents.

Uploaded details on Google Drive.

I would request you, if you can have a look whenever possible.

Thanks in advance.

Drive Folder

0 Likes

Unfortunately not able to help much.

The !thread is pretty much devoid of data so can't identify the driver.

Forcing the !irp shows that a driver made a IOCTL call which fails creating 73 more failed IRP calls before crashing.

Decoding the IOCTL call gives

Unknown IOCTL : 0x335f058b

Device Type : 0x335f
Method : 0x3 METHOD_NEITHER
Access : FILE_ANY_ACCESS
Function : 0x162

But since the driver creator hasn't named the device type I don't know where to proceed from there.

Still learning all this stuff, sorry I can't help more. 

0 Likes

Hi Fyrel

sorry to ping you, but i came accross this thread and having the same issue driving me insane i though to read and post

I have a brand new PC, and keeps rebooting. The retailer has sent me a new PSU, but i always get random reboots, these are both WHEA-logger event id 18 errors like everyone else here, but most seems to be Kernel-power event id 41 task category (63)

The PC reboots randomly, i have all stock with no OC or underclock of any sort.

here attached the WHEA dump file from the last reboot - i had Logitech Options installed, and i just got rid of it, but as well got a new reboot

I have also done 2 runs of 30 mins each of OCCT 7.2.0 - 1 general run and 1 specific for power - no errors found.

Also done a Memtest86 from a bootable drive and no issues at all with the ram sticks

My configuration is:

  • AMD Ryzen 5950x
  • 32gb Crucial Ballistix RGB 2x16gb 3600 mhz
  • WD Black 1TB SN850
  • MSI RTX3080 GamingX Trio
  • MSI X570 Gaming Plus motherboard
  • Corsair RM850x PSU (already swapped - seems made no difference)

Could you please have a look at the file in your own time and let me know if you can identify anything that could help?

thanks a lot

 

0 Likes

I have tried it all too.

My System:

Mobo: Asrock Taichi X570

GPU: Gigabyte 5700xt Gaming OC rev1.00

CPU: AMD 3900x

Old Case: NZXT 500P

New Case (Thinking it was Air-Flow): Coolermaster P500M Mesh Master Case

Old CPU Cooler: Ryzen Wraith

New Cooler: NH-D15 with both fans installed

RAM: Gskill 3200 Ripjaws - 64Gb

HDD: NVME M.2 Samsung Evo 970 1Tb

Power supply: Corsair RM850x Gold

I have tried everything including drivers voltages etc... I just contacted support for Gigabyte via their online web form.  I am hating every moment with this card ever since I put this system together in March.  Even using MS word or running chrome this **bleep** thing goes black screen and reboots.  I have tried under-volting, voltage bumps, and my fans are always at 100% keeping both card and CPU at 35 deg C idle and at 70 Deg under full load playing CP2077.  Just a bad experience with this 5700xt.  If you look at the specs, for the time, I thought I was putting together a **bleep** good PC, until it keeps failing every day... even when idle with the screen saver it just reboots on its on with error mentioned throughout this forum.

0 Likes

Try to play with Infinity Fabric Clock, it seems to be solved my issue so far. I've lowered it to half of my Ram speed. 

0 Likes

*EDIT*

Just realized you aren't running an Nvidia card... Maybe you can look for separate drivers for your card as well? Sorry...

 

I was having the same problem as you when launching games. I just fixed it.

Are you connected through with DisplayPort? If you are, Nvidia ships a tool separately that checks for displayport drivers. 

https://www.nvidia.com/en-us/drivers/nv-uefi-update-x64/

Download that and run it, it has fixed my problem completely. No more WHEA 18 events.

0 Likes

This is a very common problem and seems (tentatively) to be fixed in AGESA 1.1.9.0. Try to find a beta BIOS for your motherboard.

0 Likes

So my friend.

I'm experiencing the same headache here.
And with the new AGESA, it was nothing.

I'm testing an option, but I still can't say that it completely solved it. I disabled Windows 10 Fast Boot.

[ AMD Ryzen 7 5700X (step B2) | CM MASTERLIQUID PL360 FLUX | MSI MPG B550 GAMING EDGE WIFI - 7C91v1D | 32GB DDR4 3600MHz XPG SPECTRIX | ASUS Dual GeForce RTX 3060 OC Ed 12GB GDDR6 ]
0 Likes

Esteemed,

After 2 days without the problem occurring here, I took a black screen.

What is really happening is this new AGESA bios in BETA that is causing conflicts with CPU and GPU resources. I decided to downgrade the BIOS and run more tests.

I do not recommend AGESA 1.1.9.0 for the moment.

[ AMD Ryzen 7 5700X (step B2) | CM MASTERLIQUID PL360 FLUX | MSI MPG B550 GAMING EDGE WIFI - 7C91v1D | 32GB DDR4 3600MHz XPG SPECTRIX | ASUS Dual GeForce RTX 3060 OC Ed 12GB GDDR6 ]
0 Likes

That's annoying. The new AGESA helped me quite a lot. I wish AMD would publish errata or really communicate with its customers in any way so we don't have to guess and keep throwing crap at the wall to figure out what works.

0 Likes

English is not my first language so sorry about my bad English. i have the same issue with MPG X570 GAMING EDGE WIFI with amd ryzen 5900X but i changed only my proccessor and motherboard from i7-6700k with msi m7 gaming Z170A so, i am sure that other components is working properly. I updated my bios 7C37v1C to 7C37v1D2(Beta version) so i will test today if it fixed or not.
Note: I couldn't make my ram 3600MHz it was giving WHEA 19 and in 1 hour it restarts pc without error and event logger says WHEA 18. Now with last bios update i can at least use 3600MHz without WHEA 19 error. I hope this bios update will fix my WHEA 18 issue too.

Processor: AMD 5900X.
Graphic Card: MSI 2080 Ti.
Motherboard: MSI X570 GAMING Edge Wi-Fi.
PSU: Cooler Master G750M modular
CPU Cooler: Xigmatek Aurora Arctic 240.

 
0 Likes

Run ram test

0 Likes

A friend of mine was having this problem with his PC he had recently built (CPU: Ryzen 7 3700X, Graphics: MSI Radeon RX 5700 XT Gaming X, MOBO: MSI MPG X570 Gaming Plus) After a few hours of troubleshooting, I stumbled across a solution that worked with his setup. The source for our solution is here

Symptoms observed: PC would crash while playing games. Noticed the screen flickering before the system crashed. Windows Event Viewer logs indicated WHEA Logger Event ID 18.

Solutions we tried: installed numerous driver versions between SEP2020 and JAN2021. Updated BIOS on MOBO to the latest version as of writing this. Attempted underclocking GPU in Radeon software. Stress tested with numerous system, and graphics tools and still observed crashes and WHEA with Event ID 18 in Event Viewer.

The solution that worked for us: Uninstalled MSI afterburner. I am not even sure why he had installed it in the first place, because there were no profiles set, and he stated that he had never used it. It may sound dumb, and may not work for everyone, but it did fix his problem.

After uninstalling MSI afterburner, and rebooting the problem seems to have completely gone away. Some people have stated that closing the MSI Afterburner interface could help, but we hadn't launched it, and the uninstall seems to have done the trick. We are now on the latest driver ( 20.12.1 ) as of writing this with zero issues for the past several days. Hopefully, this helps someone else who is having a similar issue.

0 Likes

Hi, I'm hoping this community can help me as I'm at my wits end with my build. Sorry for the long-winded synopsis, but I figure as much detail as possible would be best.

Built my pc in July, worked well for approximately two months before the issues started. The PC would BSOD with a multitude of code (but no specifics on what), sometimes the pc crashes and restarts without warning, and sometimes specific apps/games will lock and then come back, or crash out.

PC Build:

AMD 3600X
B450 Tomahawk Max
Corsair H60 Cooler
G. Skill Trident Neo 3600mhz 16gb
Corsair RM 750 PSU
MSI RX480 Gaming 8GB  (from my previous build)
Samsung 850 SSD (From my previous build)

My event view is littered with warnings, errors, and criticals (Kernal-Power ID41) however I've noticed WHEA-logger fatal hardware errors showing up recently (i'll attach the dump files)

Here's what I've done:
-Clean install
-Update BIOS
-Update all drivers
-Tested RAM (Showed errors with memtest, sent away for RMA - Lost package so I bough a new pair while it's getting sorted)
-Bought new RAM (Exact same as previous, installed and issues remained - Re-tested brand new RAM, shows no errors)
-Re-seated CPU
-Swapped out my RX480 with an older GPU (issues remained)
-Checked power connections, etc

1). https://drive.google.com/file/d/10nZggHEd2oR2-sK9br0C_tbOn0LzIh_4/view?usp=sharing

2). https://drive.google.com/file/d/1gpN5G_Kg377SoVMWqezj-LezAv860a8V/view?usp=sharing

0 Likes

Friends,

It's hard. I decided in addition to updating the Adrenalin derivatives to version 20.12.1 WHQL, to return to BIOS 7C91v153. When reconfiguring the BIOS I went through a parameter which I remembered that in the past I had a huge problem keeping it enabled. It is the Spread Spectrum feature. I kept everything in the standard of what I usually configure, but I disabled this feature. Let's see what happens.

I had no problems with crashing with version 7C91v13, but I want to check the Spread Spectrum parameter, because by default it is enabled and the correct thing would be not to come, as it negatively affects overclocking. I'm not a fan of overclocking, but when the CPU does BOOST, we are using automatic overclocking. And we still have the XMP of the memories.

I will bring news soon.

[ AMD Ryzen 7 5700X (step B2) | CM MASTERLIQUID PL360 FLUX | MSI MPG B550 GAMING EDGE WIFI - 7C91v1D | 32GB DDR4 3600MHz XPG SPECTRIX | ASUS Dual GeForce RTX 3060 OC Ed 12GB GDDR6 ]
0 Likes
brownan
Journeyman III

I am also having this issue however I have a 3700X and an nVidia RTX 2070 super GPU. Although mine does not occur very often. It happened 5 days ago and then again today with the same error OP listed in event viewer albeit mine had different APIC ID's

EDIT: Turns out for me it was a bad BIOS update. I downgraded to the last BIOS that I knew for sure was stable and the issue stopped.

0 Likes
sniperzee
Adept II

Hi,

I just changed my GPU to RTX 2070 Super. I will see how it goes and keep you guys posted.

0 Likes
sniperzee
Adept II

Hello Everyone,

I changed my GPU to RTX 2070 Super today. After testing for few days, I will get back with an update.

Hello, judging by the fact that you still have not answered here, you are doing fine, and forgot this forum as a bad dream

I know the question was not for me, but I don't remember the last I got a reboot. I completely avoid alt+tabbing, played during several long-hours session and it's been fine. I play less Destiny 2 now, but more rencetly I went back to Anthem, and no restarts so far.

Please remind me which solution fixed the problem for you, I got lost in this thread. If we are only talking about alt + tabbing, then in the latest driver release this problem was solved in the description, but not really solved unfortunately. Most games are stable unless I minimize them, but there are a few that crash right during gameplay, so avoiding alt + tab doesn't help in some cases.

0 Likes

To be fair, besides keeping the drivers updated, updating to the last BIOS of my mobo and avoid alt-tabbing, I have not done anything. I am not OC'ing my CPU, PBO is disabled, I am using A-XMP profile 1, and the GPU is undervolted/overclocked.

0 Likes
sniperzee
Adept II

Hello Everyone,
Since changing the GPU, I still did not have any WHEA error or sudden restarts. There was just once when the game crashed but PC did not get stuck. I was able to kill the game and reopen it and it happened just once. I have minimised games and did other stuff like watching videos or browsing and then went back to the game without trouble. I hope changing the GPU solved the WHEA error for good.
0 Likes

Not surprised, thanks for the answer. I already forgot that you can just use the PC, minimize the games whenever you want, launch the browser in the background, and not be in constant stress waiting for the next crash, and not wait for a new driver to be released soon, which will finally fix your gpu like a christmas miracle. rx 5700 is my latest AMD graphics card I swear

0 Likes

I went to shop to purchase a RTX2070 to upgrade from GTX970 and instead purchased 5700XT.

And everyday i regret my purchase.

This is my second AMD GPU since ATI 6670 and definitely my last one from AMD.

I had 9500GT, GTX560 as well and never had so many issues ever.

I think this is something we all agree on.

0 Likes
kasferatu
Adept II

I have been having problems with my PC build since last year, and I created my own post here: 5700 XT causing PC to restart or blue screen 

However, a few weeks ago I borrowed a friends Nvidia 1650 and all the problems went away.  Based on this I had my GPU replaced by my PC vendor - from a reference MSI 5700XT to a Powercolor Red Dragon 5700XT.  However my problems persisted.  I was then advised to install the windows 2004 update and since then I have had a couple of these WHEA Logger Event ID 18 errors.

Kind of at the end of my tether on what I should do about this, and by the looks of this thread and my own experience it looks like the only solution that works is to get an Nvidia card instead.  This seems fairly drastic but honestly not sure what else to try.

maybe your PC vendor will let you swap teams. 

0 Likes

I'm having a VERY similar issue with my new ryzen build. I am not happy with this. Coming from intel, this has been a headache trying to troubleshoot. I don't get BSOD. I get random reboots, straight to black screen and fans rev up. Other times, my system will stall/freeze while watching youtube videos. The video playback will go from smooth to choppy, and I cannot close apps, open new apps, or shut my computer down from the start menu.

https://pcpartpicker.com/list/hWr4FG    This is my current hardware setup. I've upgraded to the most current BIOS version 2607. Latest chipset drivers/lan/audio all the drivers are updated including my GPU. I've tried disabling DOCP profile for memory in BIOS. I've enabled DOCP. Ran windows memory diagnostic a few times. RAM passed on standard version of tests, but froze on extended version of test every time. Tested RAM together and separately. Moved onto memtest86 and my RAM passed. Then I used HCI memtest and RAM passed there as well.  Ran uniengine heaven benchmark for my GPU. Everything passed with no crashes. I ran prime95 blended several times, each time for over an hour. Passed no issues.

My temperatures for all my hardware are fine. Not close to thermal throttling at all. Air cooled system, good case with airflow.

The only things I haven't done are reinstall windows and check my PSU.

When I go to event viewer, I get the Error>Source:WHEA-Logger>Event ID: 18 

A FATAL HARDWARE ERROR HAS OCCURRED.

REPORTED BY COMPONENT: PROCESSOR CORE

ERROR SOURCE: MACHINE CHECK EXCEPTION

ERROR TYPE: BUS/INTERCONNECT ERROR

PROCESSOR APIC ID: 0

+System
-Provider
[ Name]Microsoft-Windows-WHEA-Logger
[ Guid]{c26c4f3c-3f66-4e99-8f8a-39405cfed220}
EventID18
Version0
Level2
Task0
Opcode0
Keywords0x8000000000000000
-TimeCreated
[ SystemTime]2020-09-26T23:44:29.0870496Z
EventRecordID7236
-Correlation
[ ActivityID]{4e25f749-bc49-47e6-bb47-2ce082c309ff}
-Execution
[ ProcessID]4704
[ ThreadID]5224
ChannelSystem
ComputerJarvis
-Security
[ UserID]S-1-5-19
-EventData
ErrorSource3
ApicId0
MCABank27
MciStat0xbaa000000002080b
MciAddr0x0
MciMisc0xd01a0ffe00000000
ErrorType10
TransactionType256
Participation0
RequestType0
MemorIO2
MemHierarchyLvl3
Timeout0
OperationType256
Channel256
Length936
RawData435045521002FFFFFFFF03000100000002000000A8030000122C17001A0914140000000000000000000000000000000000000000000000000000000000000000BDC407CF89B7184EB3C41F732CB57131FE6FF5E89C91C54CBA8865ABE14913BB2FE35DF25E94D60102000000000000000000000000000000000000000000000058010000C00000000003000001000000ADCC7698B447DB4BB65E16F193C4F3DB0000000000000000000000000000000001000000000000000000000000000000000000000000000018020000800000000003000000000000B0A03EDC44A19747B95B53FA242B6E1D0000000000000000000000000000000001000000000000000000000000000000000000000000000098020000100100000003000000000000011D1E8AF94257459C33565E5CC3F7E8000000000000000000000000000000000100000000000000000000000000000000000000000000007F010000000000000002040000030000100F87000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000007000000000000000000000000000000100F8700000810000B32D87EFFFB8B170000000000000000000000000000000000000000000000000000000000000000B3F8F31CB1C5A249AA595EEF92FFA63C01000000000000009E07C0060400000000000000000000000000000000000000000000000000000000000000000000000200000002000000EBF02AF35E94D60100000000000000000000000000000000000000001B0000000B0802000000A0BA000000000000000000000000FE0F1AD00000000000000000000500002E0001000200025D000000007D000000270000000000000000000000000000000000000000000000000010000000000000001000000000000000100000000000000010001B00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0 Likes

Assuming your memory is on the QVL list from Asus for your board? If not that could be your whole problem. The fact that your memory fails any memory check is suspect.

Have you talked with Asus support at all about your issue? If your memory is not the problem then your board or processor is. Asus should be able to help you determine which is more likely. I am sure ASUS would be happy to help you and RMA your board if need be. I know AMD will do the same with your processor.

I have the same processor and SSD as you. I have a 2070 super with mine. I do have an MSI B450 board. In fact I have 3 of these boards and 3 ryzen processors. No issues like yours with any. So I can tell you that the issues you have are not normal with Ryzen. So I would talk to the support department at Asus and go from there. 

0 Likes
p30p13h4t3m3
Journeyman III

Got my problem fixed - seems to be VCore / CPU-Load related

The cause of the WHEA-Logger Problem could be a lot of things when reading multiple threads.

I've also got the instant random black screen since a year now where a restart occurred within a day.

Mostly the restart occurred when the CPU is near Idle when the CPU load is between 10-20% which means 1-3 cores are involved in doing stuff.

But because everything was working ok and changing parts was a hassle for me I just stuck with this problem until now.

At last I got mine fixed and I hope maybe somebody else could fix it with this solution.

My current setup is:

CPU: AMD 3900x

GPU: Vega Frontier

Ram: G.Skill F4-3200C14-16GVK (3200MHz CL14 - 64GB)

Mainboard: X570 AORUS XTREME

PSU: Be quiet dark power pro 1200W

Hardware:

I've changed PSU, Ram, GPU, checked if the cooler was properly mounted.

Yes, I didnt change mainboard or CPU cause I could not track down the cause of which part is failing.

Software:

With a clean install and everything up-to-date I did a torture test for the CPU, Ram and GPU. And while doing the torture test for at least 8 hours the PC did not randomly black screen, everything was functioning properly. I've even checked If it was a driver problem by analyzing the minidump after the crash (which was described here in the thread).

BIOS:

I've installed the most recent BIOS, cleared CMOS, set all settings to factory default. This did not help.

I've disabled PBO or other related overclocking features. This didnt help either.

Solution in BIOS:

After one ******* year I was tired getting the forced restart every single day and tried more things out on the BIOS. At the end I found a solution for myself (Beware, I'm no expert in Overclocking/Undervolting and if you want to try it out you alone are responsible for its outcome!):

1. Changing the Vcore's Load Line Calibration from Auto --> Medium

2. Setting the VCore from Auto --> Normal

3. Undervolting via relative VCore from Auto --> -0,8125V

Conclusion:

My PC works flawlessly since one week without any black screen restart bulls*it.

I suspect that some VCore settings from the mainboard are not properly set or maybe my CPU is to sensitive in what my mainboard assumes to be a good VCore at a specific load.

Its your personal case, but in my case the error goes away when using a different gpu or using an old driver. 

0 Likes

Hey all,

I realize I'm replying to an old topic but this problem has been happening to my pc since I built it in March of this year and it's driving me absolutely crazy. It reboots out of the blue mostly in the somewhat 'higher load' games like CoD / Metro Exodus / Horizon New Dawn.  It doesn't matter if I run the games on 1080 or 1440p the reboots will happen eventually. Sometimes very frequently (4-5 in an hour) sometimes I can play for a couple of hours before it happens. 

I replaced the PSU recently as I thought that was the main issue, I upgraded the 550w to a 750w due to the recommended power supply for my GPU which I missed / didn't research properly enough when I bought it. Here's my full specs: 

-Motherboard: MSI B450 Tomahawk Max
-GPU: Powercolor 5700xt Red Dragon
-CPU: Ryzen 5 3600
-PSU: Corsair RM750 Gold
-RAM: G.Skill Aegis F4-3000 16GB 
-CPU Cooler: CoolerMaster Hyper 212 Black Edition
-SSD: Samsung 860 EVO 500GB
-HDD: Seagate Barracuda 2TB 

Here's some of the stuff I've already tried or done already:

-BIOS updated to 7C02v37 (latest version of MSI website for the b450 max) / chipset and sata drivers installed
-GPU drivers updated to 20.11.1
-Replaced / reconnect all components in their respective slots and cables, including cleaning and reapplying thermal paste to the CPU heatsink
-Tried the other PCIE slot for the GPU
-Tried various power outlets on the wall
-Replaced PSU and DP cables
-Tried all the different programs ranging from Balanced/High performance/AMD optimized
-Tried running PBO / XMP both on/off 
-Did various testing with Cinebench/Heaven/3dMark all of which can run several times without problems. Heaven ran for at least 30 minutes last week without issues. 
-Ran the Memtest86, no issues found on either stick
-Underclocked the GPU 

Since two weeks the WHEA logger event ID 18 has been added with the crashes. Before that it would only be Kernel power event ID 41 (63) with 6008 (before that is since the pc was built in March). As the WHEA Logger was added I found this thread hence my try here for a post. I did read ofcourse that some people had the issue resolved by changing out the 5700XT, and if that's really the only solution then I'm afraid I'll have to do that as well but perhaps anyone sees anything in these WHEA logs that I could try or has any other tips/solutions? 

Here is the latest log from today, if more are needed let me know. 

Any help is highly appreciated! 

 

0 Likes