Got those Event 47 and Event 46 messages in the event log? They make my computer restart again. What's going on?
Got those Event 47 and Event 46 messages in the event log? They make my computer restart again. What's going on?
I've been recently experiencing system reboots that I'm convinced are connected with recurring Event 47, WHEA-Logger errors. The details of the error state the following: A corrected hardware error has occurred. Component: Memory Error Source: Corrected Machine Check When my computer does crash, the Event 46, WHEA-Logger details are as follows: A fatal hardware error has occurred. Component: Memory Error Source: Machine Check Exception The details page shows the following: Event 46 Details: - <Event xmlns=" http://schemas.microsoft.com/win/2004/08/events/event "> - <System> <Provider Name=" Microsoft-Windows-WHEA-Logger " Guid=" {c26c4f3c-3f66-4e99-8f8a-39405cfed220} " /> <EventID>46</EventID> <Version>0</Version> <Level>2</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x8000000000000000</Keywords> <TimeCreated SystemTime=" 2023-07-23T05:11:46.1302526Z " /> <EventRecordID>1876</EventRecordID> <Correlation ActivityID=" {c3a98e0e-f8ba-4c15-9b36-93961bdc4320} " /> <Execution ProcessID=" 3744 " ThreadID=" 3972 " /> <Channel>System</Channel> <Computer>Shauns_PC</Computer> <Security UserID=" S-1-5-19 " /> </System> - <EventData> <Data Name=" ErrorSource ">3</Data> <Data Name=" FRUId ">{00000000-0000-0000-0000-000000000000}</Data> <Data Name=" FRUText " /> <Data Name=" ValidBits ">0x2</Data> <Data Name=" ErrorStatus ">0x0</Data> <Data Name=" PhysicalAddress ">0x1000003118ebe18</Data> <Data Name=" PhysicalAddressMask ">0x0</Data> <Data Name=" Node ">0x0</Data> <Data Name=" Card ">0x0</Data> <Data Name=" Module ">0x0</Data> <Data Name=" Bank ">0x0</Data> <Data Name=" Device ">0x0</Data> <Data Name=" Row ">0x0</Data> <Data Name=" Column ">0x0</Data> <Data Name=" BitPosition ">0x0</Data> <Data Name=" RequesterId ">0x0</Data> <Data Name=" ResponderId ">0x0</Data> <Data Name=" TargetId ">0x0</Data> <Data Name=" ErrorType ">0</Data> <Data Name=" Extended ">0</Data> <Data Name=" RankNumber ">0</Data> <Data Name=" CardHandle ">0</Data> <Data Name=" ModuleHandle ">0</Data> <Data Name=" Length ">1019</Data> <Data Name=" RawData ">435045521002FFFFFFFF04000100000002000000FB030000250B0500170717140000000000000000000000000000000000000000000000000000000000000000BDC407CF89B7184EB3C41F732CB57131FE6FF5E89C91C54CBA8865ABE14913BB8594BC2724BDD901020000000000000000000000000000000000000000000000A00100005000000000030000010000001411BCA5646FDE4EB8633E83ED7C83B100000000000000000000000000000000010000000000000000000000000000000000000000000000F0010000C00000000003000000000000ADCC7698B447DB4BB65E16F193C4F3DB00000000000000000000000000000000010000000000000000000000000000000000000000000000B0020000240100000003000000000000011D1E8AF94257459C33565E5CC3F7E800000000000000000000000000000000010000000000000000000000000000000000000000000000D4030000270000000003000000000000A13248C3C302524CA9F19F1D5D7723FC000000000000000000000000000000000300000000000000000000000000000000000000000000000200000000000000000000000000000018BE8E110300000100000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000007F010000000000000002010100010000100F87000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000B0000000000000000000000000000000000000000000000000000000000000000000000000000000300000002000000EAFD6C2824BDD90109000000000000000000000000000000000000000000000035010C000020A0BE18BE8E110300000100000000FF0F13D00A0000000B00000000000000B000000004381B1C3F0000007D000000070000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001B00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000010000000000000000000000FF00000000000000000000000000000000000000000000000000</Data> </EventData> </Event> This issue plagued me for a long time about a year ago and I replaced the memory after MEM TESTS came up inconclusive. This did not correct the issue. I eventually replaced the power supply because I eventually concluded that the issue was that the power supply was failing. After replacing the PS, the issue mostly went away. While I still received the Event 47 error, it was not nearly as often and I did not experience any system reboots because of it. That is until recently. My system has unexpectedly rebooted 5 times in the last couple of weeks and the occurrence of Event 47 has gone up drastically. At this point, in addition to clean OS installs, I have replaced everything related to the memory except for the CPU. Aside from replacing the CPU (which I'd really rather not do), I am unsure how to proceed and I'm hoping someone out there has anything else to try. Please see my computer specifications and a copy of the error log below. Screenshot of recent Event Viewer events: Event 47 Details: - <Event xmlns=" http://schemas.microsoft.com/win/2004/08/events/event "> - <System> <Provider Name=" Microsoft-Windows-WHEA-Logger " Guid=" {c26c4f3c-3f66-4e99-8f8a-39405cfed220} " /> <EventID>47</EventID> <Version>0</Version> <Level>3</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x8000000000000000</Keywords> <TimeCreated SystemTime=" 2023-07-23T03:12:46.9287349Z " /> <EventRecordID>1011</EventRecordID> <Correlation ActivityID=" {b9559660-87b1-47ea-acf4-d98504998072} " /> <Execution ProcessID=" 3612 " ThreadID=" 16280 " /> <Channel>System</Channel> <Computer>Shauns_PC</Computer> <Security UserID=" S-1-5-19 " /> </System> - <EventData> <Data Name=" ErrorSource ">1</Data> <Data Name=" FRUId ">{00000000-0000-0000-0000-000000000000}</Data> <Data Name=" FRUText " /> <Data Name=" ValidBits ">0x2</Data> <Data Name=" ErrorStatus ">0x0</Data> <Data Name=" PhysicalAddress ">0x100000537ac303c</Data> <Data Name=" PhysicalAddressMask ">0x0</Data> <Data Name=" Node ">0x0</Data> <Data Name=" Card ">0x0</Data> <Data Name=" Module ">0x0</Data> <Data Name=" Bank ">0x0</Data> <Data Name=" Device ">0x0</Data> <Data Name=" Row ">0x0</Data> <Data Name=" Column ">0x0</Data> <Data Name=" BitPosition ">0x0</Data> <Data Name=" RequesterId ">0x0</Data> <Data Name=" ResponderId ">0x0</Data> <Data Name=" TargetId ">0x0</Data> <Data Name=" ErrorType ">0</Data> <Data Name=" Extended ">0</Data> <Data Name=" RankNumber ">0</Data> <Data Name=" CardHandle ">0</Data> <Data Name=" ModuleHandle ">0</Data> <Data Name=" Length ">1019</Data> <Data Name=" RawData ">435045521002FFFFFFFF04000200000002000000FB0300002E0C0300170717140000000000000000000000000000000000000000000000000000000000000000BDC407CF89B7184EB3C41F732CB57131B248949139377F4BA8F1E0062805C2A316FD197E00BDD901000000000000000000000000000000000000000000000000A00100005000000000030000010000001411BCA5646FDE4EB8633E83ED7C83B100000000000000000000000000000000020000000000000000000000000000000000000000000000F0010000C00000000003000000000000ADCC7698B447DB4BB65E16F193C4F3DB00000000000000000000000000000000020000000000000000000000000000000000000000000000B0020000240100000003000000000000011D1E8AF94257459C33565E5CC3F7E800000000000000000000000000000000020000000000000000000000000000000000000000000000D4030000270000000003000000000000A13248C3C302524CA9F19F1D5D7723FC00000000000000000000000000000000030000000000000000000000000000000000000000000000020000000000000000000000000000003C30AC370500000100000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000007F010000000000000002010100010000100F87000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000A0000000000000000000000000000000000000000000000000000000000000000000000000000000300000002000000FD3DB38D13BDD90108000000000000000000000000000000000000000000000035010C000020209C3C30AC370500000100000000FE0F1AD00A0000000A00000000000000B000000004001B1A3F0000007D000000270000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001B00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000010000000000000000000000FF00000000000000000000000000000000000000000000000000</Data> </EventData> </Event> Computer Specs: CPU: AMD Ryzen 5 3600 MB: ASUS TUF Gaming B550-PLUS AMD AM4 Zen 3 Ryzen 5000 & 3rd Gen Ryzen ATX Gaming Motherboard RAM: 32GB Corsair DDR4-3200 (2 16 GB sticks) Graphics: NVIDIA GeForce RTX 3060 PS: Corsair RM750 750 Watt
Well, that's a big clue! I would download Memtest86 (free), use the imageUSB.exe tool from the download to make a bootable USB drive with Memtest86 (1GB is plenty big enough), and then start that USB drive. Memtest86 will run as soon as it boots. If no errors show up after four rounds of checking, I'd restart Memtest86 and do another four rounds.
Thanks for getting back to me. I'm going to run memtest again just to make sure, though it happened before with my first pair of memory sticks and they worked fine at that time. Even if those old ones passed back then, I thought they were the problem because they cost less. The new sticks have the same issue. I haven't run more than one pass on them yet, but since this bug shows up on two totally different kinds of sticks (from different makers), I think it's not a hardware fault in the RAM itself. But maybe I'm wrong, so I'll do a full test just to be completely sure.
QVL doesn't mean the RAM isn't compatible, it's just the RAM they tested and verified. I haven't used RAM in any QVL on my motherboards for as long as I can remember, and only one had a issue that was fixed simply by doing the settings manually.
@ubuysa Thanks so much for helping me out. Yeah, that thought popped into my head, but @hotaru.hino said that list just means those sticks have actually been tested. I couldn't find ANY popular RAM from newegg (sold and marketed as compatible) on their QVL list. That combined with the fact that I had the same problem with the old pair of sticks, chances were low that the issue was in the RAM itself. After trying a bunch of different things, I finally replaced my CPU, and it seems like that fixed everything so far. Before replacing, I got WHEA-Logger errors right after the system started up. Now that I've been playing heavy games for hours with this new CPU, there have been ZERO recorded errors in the log. It looks like the old CPU was broken somehow (my guess is it wasn't getting enough power/voltage), which caused those errors. Hopefully, we are finally out of this problem!
If you didn't mess with your voltage settings, Ryzen processors usually give them a lot of room. People have complained about this for years, thinking it goes up to nearly 1.5 volts. However, when boosting all the cores, it usually stays around 1.3 to 1.35 volts. It might just be that old technology is hitting its limit and the boost isn't working anymore. Based on my knowledge of failing CPUs, they often die like this when they run out of life. If you reach that point, your only choices are to lower the clock speed or raise the voltage, but raising it probably won't help because Zen 2 doesn't have a special safety curve for low-core workloads. Even if you do have an old processor, maybe trying to set a fixed base clock speed will fix those glitches. If you know what QVL means and understand its rules, why would you recommend checking it anyway? I've also seen cases where people thought something was easy to fix but turned out the solution wouldn't work at all. For example, someone might say "buy more RAM" when they actually have plenty of memory but their system is running slow because of a bad driver that's using too much RAM.