Cache error exception cisco

cache error exception cisco

These error messages may occur in the following locations: On the console: *** System received a Cache Parity Exception ***. When a problem is detected, a Machine Check Exception (MCE) is thrown. M86 Paf9e74900/40 Cache Hierarchy: Level 0 Data Cache Read Error. If you recently removed the chassis, or if you performed any hardware configuration changes, re-seat the DRAM chips to solve the problem. Otherwise, replace the.

Thematic video

SSL Certificate Error Fix [Tutorial]

Contact US


Thanks. We have received your request and will respond promptly.

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!

  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

Join Us!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, cache error exception cisco, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Tek-Tips Posting Policies

Contact US

cisco 7513 loop, Cache Parity Exception

cisco 7513 loop, Cache Parity Exception



If got a cisco 7513 that does not boot up, now i can go to rommon but that it, cache error exception cisco, i can,t getting it to boot up or to find out what is wrong.

Here is the output:

Error: primary data cache, fields: data,                                        
virtual addr 0x4016E2A8, physical addr(21:3) 0x16E2A8, vAddr(14:                                                               
virtual address corresponds to memd                                   

=== Flushing messages () ===                            

Buffered messages:                  
Queued messages:                
00:00:01: %SYS-3-LOGGER_FLUSHING: System pausing to ensure console debugging out                                                                                
Free space check for bootflash:crashinfo_19930301-000001 failed (1/691)                                                                       

*** System received a Cache Parity Exception ***                                                
signal= 0x14, code= 0xa016e2aa, context= 0x607d9200                                                   
PC = 0x601d1868, Cause = 0x420, Status Reg = 0x34008002                                                       
DCL Masked Interrupt Register = 0x000000bf                                          
DCL Interrupt Value Register = 0x0000001c                                         
DCL Interrupt Value Register = 0x0000001c                                         

Does anyone know how to solve this?



Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Cisco Systems OL-7469-04 Determining the MWAM Cisco IOS Image Name, Verifying the MWAM Configuration, DIMM Issue, MWAM Performance Tuning


Multiprocessor WAN Application Module User Guide


AppendixB Troubleshooting MWAM Problem Solving

Determining the MWAM Cisco IOS Image Name

To determine the MWAM Cisco IOS image name, execute the following command at the Cisco

Supervisor 2 (see the “Software Description” section on page1-7 for more details):

show cdp entry *

You can also execute the following command at the Supervisor to determine the MWAM Cisco IOS

image name:

session slot x processor [2-6]

Then issue the following command:

show version

You can also enter the following command from the privileged EXEC mode (also available through

showimages at the processor complex):

show version

Verifying the MWAM Configuration

To determine the MWAM configuration, see the “Verifying the MWAM Configuration” section on

page 6-14.

DIMM Issue

The following shows a possible DIMM issue (CSCin29212) that may be solved by re-inserting the

DIMM memory:

*** Cache Error Exception***

Cache Err Reg = 0x14001f20

instruction reference, primary cache,tag field error, error on internal request on

SysAD Bus,

PC = 0x800fb5d4, Cause Reg = 0x20008068, Status Reg = 0x400005

%MWAM-0-CORRECTABLE_ECC_ERR: A correctable ECC error has occurred,



RRECTABLE_ECC_ERR: A correctable ECC error has occurred.

MWAM Performance Tuning

You can improve system performance (by 6 to 12 percent depending on the traffic type) by turning off

VLAN accounting:

Router# configure terminal

Router(config)# no vlan accounting


Machine-check exception

A machine-check exception (MCE) is a type of computer hardwareerror that occurs when a computer's central processing unit detects a hardware error in the processor itself, the memory, the I/O devices, or on the system bus; in some architectures[a], an MCE only occurs for an unrecoverable error. On x86 architectures, a machine-check exception is not caused by software. However, on other architectures such as PowerPC, certain software bugs such as invalid memory cache error exception cisco can cause machine-check exceptions. The error usually occurs due to component failure cache error exception cisco the overheating or overclocking of hardware components. Most machine-check exceptions halt the operating system and require a restart before users can continue normal operation.[dubious – discuss] Diagnosing the failure can be often difficult because so little information about what caused cache error exception cisco problem is captured during the error.

Modern versions of Microsoft Windows on IA-32 and x86-64 processors handle machine-check exceptions through the Windows Hardware Error Architecture. When WHEA detects an uncorrectable machine check exception, it displays the error in a Blue Screen of Death, with the following parameters (which vary, but the first parameter is always 0x0 for a machine check exception):[1]

*** STOP: 0x00000124 (0x0000000000000000, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000)

Older versions of Windows handle similar exceptions through the Machine Check Architecture. In this case, the Blue Screen of Death will show an error similar to the following:[2]

STOP: 0x0000009C (0x00000030, 0x00000002, 0x00000001, 0x80003CBA)

On Linux, a process (such as [3]) writes a message to the kernel 10060 error builder c++ and/or the console screen (usually only to the console when the error is non-recoverable and the machine crashes as a result):

CPU 0: Machine Check Exception: 0000000000000004 Bank 2: f200200000000863 Kernel panic: CPU context corrupt

Problem types[edit]

Most of these errors relate specifically to the Pentium processor family. Similar errors may occur on other processors and will cause similar problems.

Some of the main hardware problems that cause MCEs include:

Possible causes[edit]

Machine checks are a hardware problem, not a software problem. They are often the result of overclocking or overheating. In some cases, cache error exception cisco, the CPU will shut itself off once passing a thermal limit to avoid permanent damage. But they can also be caused by bus errors introduced by other failing components, like memory or I/O devices. Possible causes include:

  • Poor CPU cooling due to a CPU heatsink and case fans (or filters) that's clogged with dust or has come loose.
  • Overclocking beyond the highest clock rate at which the CPU is still reliable.
  • Failing motherboard.
  • Failing processor.
  • Failing memory.
  • Failing I/O controllers, on either the motherboard or separate cards.
  • Failing I/O devices.
  • Inadequate or failing power supply.

Cooling problems are usually obvious upon inspection. A failing motherboard or processor can be identified by swapping them with functioning parts. Memory can be checked by booting to a diagnostic tool, like memtest86. Non-essential failing I/O devices and controllers can be identified by unplugging them if possible or disabling the devices to see if the problem disappears. If the failures typically only occur fairly soon after the OS is booted or not at all or not for days, cache error exception cisco, it may be suggestive of a power supply issue. With a power supply problem, the failure often occurs when power demand peaks as the OS starts up any external devices for use.

Decoding MCEs[edit]

For IA-32 and Intel 64 processors, consult the Intel 64 and IA-32 Architectures Software Developer's Manual[4] Chapter 15 (Machine-Check Architecture), or the Microsoft KB Article on Windows Exceptions.[5]

Programs to decode Intel and AMD MCEs[edit]

  • mcat: A Windows command-line program from AMD to decode MCEs from AMD K8, Family 0x10 and 0x11 processors.
  • mcelog[6] A Linux daemon by Andi Kleen to handle MCEs for modern x86 processors, cache error exception cisco. mcelog can also decode machine checks.
  • parsemce[7] a Linux program by Dave Jones to decode MCEs from AMD K7 processors.
  • mced[8] a Linux program by Tim Hockin to gather MCEs from the kernel and alert interested applications. Note that it does not try to interpret the MCE data, it simply alerts other programs.

See also[edit]


  1. ^On other architectures, an MCE may occur in order to log, e.g., a memory corrected by ECC.


External links[edit]

Trademarks of Cisco Systems, Inc. Updated: Apr 29, 2008 Document ID: 29320