"WHEA_UNCORRECTABLE_ERROR" on Ryzen 5 5600x

[JC_123]

Hello.

Since upgrading to an R5 5600x I've been getting tons of bluescreens regardless of if I am overclocked or not. It took some time but I figured out the bluescreens ONLY happen when a malwarebytes scan is running, or occasionally when the malwarebytes app was open and I was changing settings, etc. My PC always seems to fail to create an actual dump in minidump or whatever but of course we do get some info from event viewer (below). My system is an R5 5600x, an MSI B450i (yes I have a zen 3 ready bios), some Micron E-die DDR4 (I also tested a different memory kit with the same results), 750W EVGA G3, and an EVGA GTX 1070 ti. I have Windows 10 home, Malwarebytes premium and was using the latest non-beta release (also tried uninstalling, reinstalling).

Event viewer reads this as a critical error:

Quote

Event ID: 41, Task Category: (63)

 

Quote

 

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

- <System>

  <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331c3b3a-2005-44c2-ac5e-77220c37d6b4}" />

  <EventID>41</EventID>

  <Version>8</Version>

  <Level>1</Level>

  <Task>63</Task>

  <Opcode>0</Opcode>

  <Keywords>0x8000400000000002</Keywords>

  <TimeCreated SystemTime="2021-08-17T23:28:31.0620987Z" />

  <EventRecordID>33519</EventRecordID>

  <Correlation />

  <Execution ProcessID="4" ThreadID="8" />

  <Channel>System</Channel>

  <Computer>(my pc's name)</Computer>

  <Security UserID="S-1-5-18" />

  </System>

- <EventData>

  <Data Name="BugcheckCode">292</Data>

  <Data Name="BugcheckParameter1">0x10</Data>

  <Data Name="BugcheckParameter2">0x0</Data>

  <Data Name="BugcheckParameter3">0x0</Data>

  <Data Name="BugcheckParameter4">0x0</Data>

  <Data Name="SleepInProgress">0</Data>

  <Data Name="PowerButtonTimestamp">0</Data>

  <Data Name="BootAppStatus">0</Data>

  <Data Name="Checkpoint">0</Data>

  <Data Name="ConnectedStandbyInProgress">false</Data>

  <Data Name="SystemSleepTransitionsToOn">0</Data>

  <Data Name="CsEntryScenarioInstanceId">0</Data>

  <Data Name="BugcheckInfoFromEFI">true</Data>

  <Data Name="CheckpointStatus">0</Data>

  <Data Name="CsEntryScenarioInstanceIdV2">0</Data>

  <Data Name="LongPowerButtonPressDetected">false</Data>

  </EventData>

  </Event>

 

Now I know this is apparently a "hardware" error but I have not been able to replicate it with anything except a malwarebytes scan that happens to be running while other things are also being processed (games, videos, downloads, GPU rendering/encoding something, really anything). Defender scans don't do it, stress tests in 3DMark, Prime95, memtest, MemTest86 also don't do it.

For now, I have uninstalled malwarebytes. Don't want to reinstall until I get a clue as to why this is happening. Don't want to upload your "sysnativefilcollection" to a public forum since it contains my IP address and more potentially privacy-infringing stuff.

Thanks!

[axe0]

Hi JC_123,

I don't mean to be rude here.

You're asking for help but are not willing to provide the requested data that is necessary to help. I am not sure what anyone can do for you if you're not willing to provide the requested data.

Regarding any privacy-infringing stuff, there's no privacy-infringing stuff collected. You can have a look at it yourself, but the main things that are collected is events, error logs, system and hardware information. We will need to know that information otherwise there's no chance for anyone to provide the least bit suggestion that is any relevant.

You are one in a thousand of users who makes it known about their privacy concerns, but in the thousands of users that have gone before you there haven't been any complaint about any log truly violating their privacy. IP stuff I can somewhat understand, but it's there because the Sysnative log collector is really a generic log collector that can be used for different problems which include network-related problems, performance problems and more. Considering that the Sysnative log collector is available for many years, and in that time there hasn't been a problem significant enough to temporarily pull the Sysnative log collector to fix problems in recent years, I say it does not violate your privacy. Note that with 'problems' I do not just mean complaints about privacy, but for example also problems with running it. Believe me, if there was any violation in anyone's privacy the tool would have been pulled long ago and updated accordingly. Sysnative is a credible site with staff that is critical and well privacy & security aware. I am a little biased as I am a moderator at Sysnative forums, but I do not want to start an argument with any of them if I don't have sufficient facts and evidence to back myself up for any statement I make.

Having said that, I would like you to upload the logs from the zip generated by the Sysnative log collector as we really need it to look into those crashes. The event you posted is useless as it does not give much insight. The best I can gather from it is that it is possibly a result of a driver error. The question only the logs can help answer is which driver?

[Porthos]

21 hours ago, JC_123 said:

Don't want to upload your "sysnativefilcollection" to a public forum since it contains my IP address and more potentially privacy-infringing stuff.

Only you and authorized users can access them here.

[Porthos]

21 hours ago, JC_123 said:

For now, I have uninstalled malwarebytes.

So no BSOD's with MB uninstalled?

Do you have any og the software listed here installed.this support article