Machine Check Analysis Tool 2.3.2 Download PC/Windows This program reads the Log File produced by the windows OS EventViewer "System" event log and decodes the MCAs for the Debugging and Analyzing of your MCA Hardware. MAy of the Log File produced by the windows eventlog are very similar and the decoder can usually understand what type of MCA is being reported and can decode and display all MCA errors to a readable format. The output from the decoder can be written to the output files, or can be displayed on screen. This utility is written in C and is run on any Windows operating system. It will automatically detect your MCA module type and will display all of your MCA Bank, Status, Address, and Misc. This program can alternatively be run in the Debug Mode (Bypassing all other normal logic in the MCU). This allows you to extract all MCA Error Codes from any given MCA module. MCA Error Code Table: MCA Registers have a unique MCA number that is between 0000 and 9999. MCA 0000 is the first Error code in the MCA Table. This is the base MCA number for any given MCA Module. MCA 1 is MCA Registers 2 to 3, MCA 2 is Registers 4 to 5 and MCA 3 is registers 6 to 7. MCA 0000 is always 0x200, any of the other MCA's are different depending on the Module type. So if the MCA was given an MCA number of 0x200 then its MCA 0 (0x200) will be displayed. The MCA Error Codes used with this utility are identified using the K8 MCA specification. K8 MCA Specification: The K8 MCA specification is available from the manufacturer and can be found at the following website. Since we are using the K8 specification, then the K8 command is very similar to the old G command. Use K8 to instruct the utility on what MCA to use. The MCA number can be a 0 to a 9999 and the MCA can be banked, status, address, or misc. The K8 command gives specific values to those fields that you want to set. For example, if you want to set the module type to be 7 then use the K8 command. This will Machine Check Analysis Tool 2.3.2 Crack MCAT is an open source program that is based on MCA specification (originally developed by Eric McNeil). It is also a modified version of the open source program "MCAT2" by Christian Dittrich. This new version is based on Windows 8.1 and is capable of running on multiple OS's such as Linux, BSD, Solaris, OS X and others. Many of the following sections have been written using this application: 1. Modify MCAT2 to support Windows 8.1 2. Written user guide for MCAT2 (can be found under directory instructions/) 3. Modified MCAT2 (Using VDI and WinDbg) 4. Moved MCAT under a new repository. 5. Setup a "Steam Partner" registration account. 6. Upgrade all MCAT2 users to MCAT2 v1.0.5 (can be found under download/r5). Version 1.0.0 Version 1.0.1 Version 1.0.2 Version 1.0.3 Version 1.0.4 Version 1.0.5 License: MIT Author(s): Christian Dittrich, Eric McNeil Contact: Christian Dittrich at Christian.Dittrich@mcel.org Date: 2014-07-11 Website: 1. Modify MCAT2 to support Windows 8.1 MCAT2 and MCAT can decode Windows System Event Log files. The MCE Error is defined as a subfield in the standard MCA event format. To extract the MCE Error information from the Event Log file: 1. Convert the MCE event into an Acpi Event. 2. Create an Event Log trigger in Windows Event Viewer to call the Acpi Event. 3. Monitor the event log for events matching the created trigger. Some interesting events that I have observed: 1. The MCA Event will be marked as "MCE" when one of the following fields has a value other than zero: a. Address - The logical address of the MCE Error b. Status - Status is an MCA status code describing the status of the operation. The values of Status are as follows: MSR_EVENT_MCE_SUCCESS - A successful MSR address decode. MSR_EVENT_MCE_ERROR - A failed MSR address decode. MSR_EVENT_MCE_MESSAGE_ERROR - An MSR message decode error. MSR_EVENT_MCE_BUS_ERROR - A MCE bus error. 2. The 1a423ce670 Machine Check Analysis Tool 2.3.2 PC/Windows The "KEYMACRO" is used to define the MCA "key" field that should be used to encrypt the fields supplied after the "KEYMACRO". Example: The keyword "Data01" is used to encrypt the byte contents of the “bank” field with the use of the MAC specified as “Key01”. The “KEYMACRO” contains the MAC to be used for encrypting a specific field within the MCA Error Log. Example: The "KEYMACRO" value “Data01” would encrypt the data in the “bank” field using the MAC “Key01” specified in the "KEYMACRO" as follows: For bytes 0 to 7 of the “bank” field, the data is encrypted with MAC “Key01” For bytes 8 to 15 of the “bank” field, the data is encrypted with MAC “Key02” For bytes 16 to 23 of the “bank” field, the data is encrypted with MAC “Key03” For bytes 24 to 31 of the “bank” field, the data is encrypted with MAC “Key04” If a field in the MCA Error Log is not encrypted, then it will not be included in the decoded MCA log. The "KEYMACRO" is only used when the MCA Specification is 2.5. The path to the "Source_EventLog" will be the same as the path of the log file name provided in the command line. The full path to the MCA Error Log will be the same as the path to the "Source_EventLog" file and the path to the "Source_McaLogs" file. Example: If the MCA Error Log file name is "System.evt", then the "Source_EventLog" will be "System.evt" and the "Source_McaLogs" will be the same as the path to the "System.evt". if the MCA Error Log file name is "System.evt", then the "Source_EventLog" will be "System.evt" and the "Source_McaLogs" will be the same as the path to the "System.evt". Key01 Key02 What's New In Machine Check Analysis Tool? System Requirements: OS: Windows 10 / 8 / 7 (64-bit) Processor: Intel Pentium 4 2.8GHz or faster Memory: 2GB RAM Video: NVIDIA GeForce 8800 or ATI X1800 or better DirectX: Version 9.0c Hard Drive: 20 GB available space Sound Card: DirectX 9.0c Compatible Sound Card ISSUES: “Injustice: Gods Among Us Ultimate Edition” is available for download via Xbox Live, Playstation Network and Steam.
Related links:
Comments