Machine Check Exception - Cache Hierarchy Error (2)

Question

System with FX-6200, first time check- instant reboot after error.

Here are the addresses:

- System 
  - Provider 

   [ Name]  Microsoft-Windows-WHEA-Logger 
   [ Guid]  {c26c4f3c-3f66-4e99-8f8a-39405cfed220} 
 
   EventID 18 
 
   Version 0 
 
   Level 2 
 
   Task 0 
 
   Opcode 0 
 
   Keywords 0x8000000000000000 
 
  - TimeCreated 

   [ SystemTime]  2022-04-25T05:40:13.3889636Z 
 
   EventRecordID 430444 
 
  - Correlation 

   [ ActivityID]  {6bd42abf-b24f-47fa-8da4-5fa24876bd65} 
 
  - Execution 

   [ ProcessID]  3744 
   [ ThreadID]  4232 
 
   Channel System 
 
   Computer ThatsMeBabe 
 
  - Security 

   [ UserID]  S-1-5-19 

- EventData 

  ErrorSource 3 
  ApicId 0 
  MCABank 1 
  MciStat 0xb600000000100153 
  MciAddr 0xd 
  MciMisc 0x0 
  ErrorType 9 
  TransactionType 0 
  Participation 256 
  RequestType 5 
  MemorIO 256 
  MemHierarchyLvl 3 
  Timeout 256 
  OperationType 256 
  Channel 256 
  Length 936 
  RawData 435045521002FFFFFFFF03000100000002000000A803000024270500190416140000000000000000000000000000000000000000000000000000000000000000BDC407CF89B7184EB3C41F732CB57131FE6FF5E89C91C54CBA8865ABE14913BBBA97BAD36658D80102000000000000000000000000000000000000000000000058010000C00000000003000001000000ADCC7698B447DB4BB65E16F193C4F3DB0000000000000000000000000000000001000000000000000000000000000000000000000000000018020000800000000003000000000000B0A03EDC44A19747B95B53FA242B6E1D0000000000000000000000000000000001000000000000000000000000000000000000000000000098020000100100000003000000000000011D1E8AF94257459C33565E5CC3F7E8000000000000000000000000000000000100000000000000000000000000000000000000000000007F010000000000000002010300030000120F60000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000007000000000000000000000000000000120F6000000806000B22981EFFFB8B170000000000000000000000000000000000000000000000000000000000000000F50157A5EFE3DE43AC72249B573FAD2C03000000000000009F00D406000000000D00000000000000000000000000000000000000000000000000000000000000020000000200000027564CD96658D80100000000000000000000000000000000000000000100000053011000000000B60D00000000000000000000000000000000000000100000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 

BugcheckCode 0 
  BugcheckParameter1 0x0 
  BugcheckParameter2 0x0 
  BugcheckParameter3 0x0 
  BugcheckParameter4 0x0 
  SleepInProgress 0 
  PowerButtonTimestamp 0 
  BootAppStatus 0 
  Checkpoint 0 
  ConnectedStandbyInProgress false 
  SystemSleepTransitionsToOn 0 
  CsEntryScenarioInstanceId 0 
  BugcheckInfoFromEFI false 
  CheckpointStatus 0 
  CsEntryScenarioInstanceIdV2 0 
  LongPowerButtonPressDetected false 

Looks like an info, but where is it from?
The system has had previous form, and been rather sluggish of late.
There have also been freezes, nothing in the event logs to explain them.
Thanks.

Answer 1

Here's another one after an unscheduled reboot after loading desktop on a clean reboot. No errors in the first reboot,

Of interest on the second reboot is an event 7009 (followed by an event 7000) with the Eaton UPSCompanion which produces an error like the following.

The only way to mute the error is to re-install the driver for the UPS. Their tech support had no idea of the nature of the error or what it signified, and point to the PC as being at fault, and not their software.

There is also an event 7030 in the system log:

The Eaton UPS Companion service is marked as an interactive service. However, the system is configured to not allow interactive services. This service may not function properly.

Also on the second reboot, there was Session "Microsoft.Windows.WindowsUpdate.RUXIMLog" failed to start with the following error: 0xC0000035

Would it be indicative of something else that would cause Windows to reboot?

Thanks again.

Answer 2

Hi,

The system booted, and froze (black screen- no keyboard) after going to sleep- it's usually in a low custom power state.

Here's a dump taken on startup after the freeze- there were a couple of errors on some task launching since, nothing else beside the "usual."

Thanks

Answer 3

Hi Laurie, no problem at all, I will be here, if your system generates minidump files.

Answer 4

Hi @DaveM121,

Thanks for response!

Minidumps on this rig were not enabled at the time, unfortunately. Enabled now. All right with you if we keep this thread open for the next bug check?

Laurie

Answer 5

Hi LmStearn

I am Dave, I will help you with this.

Please check to see if your PC is producing any minidump files, I will check those to see if they provide any insight into a potential cause of the system crashes.

Open Windows File Explorer.

Navigate to C:\Windows\Minidump

Copy any minidump files onto your Desktop, then zip those up.

Upload the zip file to the Cloud (OneDrive, DropBox... etc.), then choose to share those and get a share link.

Then post the link here to the zip file, so we can take a look for you.