Question Machine Check Exception Event 46 and 3B crashes

Page 2 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.

LordMangas

Junior Member
Apr 12, 2022
12
1
11
Hi forum

First type of crash: EVENT 46 Component is the Memory and a Memory Check Exception. PC freezes in game and reboots.

Second crash I find: When browsing on windows screen YouTube etc, PC freezes and reboots. This is a crash error of 3B code.

These memory check exception crashes are recent. I have undervolted with PBO2 and I have a Ryzen 5800X with a 6700XT.

Motherboard red light shows BOOT and VGA light.

I post WinDbg crash dumps below if anyone can tell me what the issue is.


SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:


PROCESS_NAME: procexp64.exe





STACK_TEXT:
ffff800a`b6587590 fffff800`716251e4 : 00000000`00000003 ffff800a`b6587b20 00000000`00000000 00000000`00000004 : dxgkrnl!DxgkVidMmAllowFailOnOfferReclaimErrors+0xb85
ffff800a`b6587600 fffff800`715740cb : ffffa989`637ec080 ffffa989`637ec080 00000000`00000004 ffff73fd`1a200000 : dxgkrnl!NtGdiDdDDIQueryClockCalibration+0x6b4
ffff800a`b6587a70 fffff800`63a28a78 : ffffa989`637ec080 ffff800a`b6587b20 00000000`000008fc ffffa989`00000000 : dxgkrnl!NtGdiDdDDIQueryStatistics+0xb


SYMBOL_NAME: dxgmms2!VidSchQueryProcessNodeStatistics+30

MODULE_NAME: dxgmms2

IMAGE_NAME: dxgmms2.sys

FAILURE_BUCKET_ID: AV_dxgmms2!VidSchQueryProcessNodeStatistics


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
nt!_WHEA_ERROR_RECORD structure that describes the error condition. Try !errrec Address of the nt!_WHEA_ERROR_RECORD structure to get more details.
Arguments:
Arg1: 0000000000000000, Machine Check Exception

MODULE_NAME: AuthenticAMD

IMAGE_NAME: AuthenticAMD.sys

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: 0x124_0_AuthenticAMD_MEMORY__UNKNOWN_FATAL_IMAGE_AuthenticAMD.sys
 

Markfw

Moderator Emeritus, Elite Member
May 16, 2002
25,482
14,434
136
Personally, i'd rather know what the issue was with some certainty before doing a RMA.
I read a reddit post where the guy returned his CPU for RMA and the new one gave the exact same MCE error.
It can be time consuming, but really all we can do is try eliminating the components one by one to determine what is having the problem. Unfortunately I have no experience with windows, but i'd think there is a way to get a more detailed error report than what's in your first post.
When I was dialing in my ram settings I first set my cpu to an all core clock with all the pbo stuff disabled.

You have to find some state where everything is fully stable and work from there (if at all possible).
You can try running your RAM 1 step slower MHz just to see if it is stable. Is your FCLK/UCLK running 1:1 with MCLK ?

EDIT: post some pictures of your bios settings (all voltages in particular).
Including NOT using XMP, just let it default to 1066 or whatever ridiculous speed the default is. See what happens. If that works, just have just identified memory as being the cause.
 

Soulkeeper

Diamond Member
Nov 23, 2001
6,712
142
106
Also, to clarify, AMD considers PBO a form of overclocking and don't guarantee it'll work (it voids warranty if you admit it).
Chances are that you will have to adjust other voltages/settings to get PBO stable, which can take more time than most anything.
 

LordMangas

Junior Member
Apr 12, 2022
12
1
11
Also, to clarify, AMD considers PBO a form of overclocking and don't guarantee it'll work (it voids warranty if you admit it).
Chances are that you will have to adjust other voltages/settings to get PBO stable, which can take more time than most anything.
Which is why you don't admit it. Who does?

So far I have disabled all forms of undervolting on the CPU and no crashes thus far. However to confirm it was 100% the undervolt, I will go a few more days with all undervolt settings removed and see if any crash/ freeze pops up.
 

LordMangas

Junior Member
Apr 12, 2022
12
1
11
Including NOT using XMP, just let it default to 1066 or whatever ridiculous speed the default is. See what happens. If that works, just have just identified memory as being the cause.
I already tried to put the RAM speeds and FCLK down. The same freeze happended when I did.
 

Soulkeeper

Diamond Member
Nov 23, 2001
6,712
142
106
Another thing to consider is that the warranty is 3yrs, so you have plenty of time to try to get everything working :)

BTW I just upped my VDDP (PHY) voltage a little and my errors seem to have gone away. (EDIT: Error came back).
Just like you, 1 day, or even 1 week might not be enough to validate a setting's stability.
 
Last edited:

LordMangas

Junior Member
Apr 12, 2022
12
1
11
Another thing to consider is that the warranty is 3yrs, so you have plenty of time to try to get everything working :)

BTW I just upped my VDDP (PHY) voltage a little and my errors seem to have gone away. (EDIT: Error came back).
Just like you, 1 day, or even 1 week might not be enough to validate a setting's stability.
I want to update this thread: There has been no crashes since removing all undervolt settings including PBO2 and PBT limits on the motherboard. It's fair to say all my crashes were the fault of PBO2 and PBT limits not being stable. All set to default and I believe the problem has been solved.
 

Markfw

Moderator Emeritus, Elite Member
May 16, 2002
25,482
14,434
136
I want to update this thread: There has been no crashes since removing all undervolt settings including PBO2 and PBT limits on the motherboard. It's fair to say all my crashes were the fault of PBO2 and PBT limits not being stable. All set to default and I believe the problem has been solved.
You do realize thats why defaults are called defaults. They work almost all the time. PBO2 and PBT are NOT defaults, and should only be used when they don't cause a problem, so I would not say they are the problem, but setting them is what caused the problem.
 
  • Like
Reactions: scannall

Shmee

Memory & Storage, Graphics Cards Mod Elite Member
Super Moderator
Sep 13, 2008
7,382
2,417
146
To test stability if you want to retry your tweaking, I would recommend core cycler to start with, which will test individual cores. Also you could use prime 95 in general, all core. And memtest86 for testing memory.
 

Soulkeeper

Diamond Member
Nov 23, 2001
6,712
142
106
Don't feel bad, a lot of people are struggling with PBO and CO. They are much harder to get fully stable than your typical review might suggest(and take a lot of time). Countless threads have people saying "no errors" ... then they reply a few days later saying they came back.