Cpu l2 cache error

CPU L2 Cache ECC Checking

Common Options : Enabled, Disabled

Quick Review of CPU L2 Cache ECC Checking

The CPU L2 Cache ECC Checking BIOS feature enables or disables the L2 (Level 2 or Secondary) cache’s ECC (Error Checking and Correction) capability, if available.

Enabling this feature is recommended because it will detect and correct single-bit errors in data stored in the L2 cache. As most data reads are satisfied by the L2 cache, the L2 cache’s ECC function should catch and correct almost all single-bit errors in the memory subsystem.

It will also detect double-bit errors although it cannot correct them. But this isn’t such a big deal since double-bit errors are extremely rare. For all practical purposes, the ECC check should be able to catch virtually all data errors. This is especially useful at overclocked speeds when errors are most likely to creep in.

So, for most intents and purposes, I recommend that you enable this feature for greater system stability and reliability.

Please note that the presence of this feature in the BIOS does not necessarily mean that your processor’s L2 cache actually supports ECC checking. Many processors do not ship with ECC-capable L2 cache. In such cases, you can still enable this feature in the BIOS, but it will have no effect.

Details of CPU L2 Cache ECC Checking

The CPU L2 Cache ECC Checking BIOS feature enables or disables the L2 (Level 2 or Secondary) cache’s ECC (Error Checking and Correction) capability, if available.

Enabling this feature is recommended because it will detect and correct single-bit errors in data stored in the L2 cache. As most data reads are satisfied by the L2 cache, the L2 cache’s ECC function should catch and correct almost all single-bit errors in the memory subsystem.

It will also detect double-bit errors although it cannot correct them. But this isn’t such a big deal since double-bit errors are extremely rare. For all practical purposes, the ECC check should be able to catch virtually all data errors. This is especially useful at overclocked speeds when errors are most likely to creep in.

[adrotate group=”2″]

There are those who advocate disabling ECC checking because it reduces performance. True, ECC checking doesn’t come free. You can expect some performance degradation with ECC checking enabled. However, unlike ECC checking of DRAM modules, the performance degradation associated with L2 cache ECC checking is comparatively small.

Balance that against the increased stability and reliability achieved via L2 cache ECC checking and the minimal reduction in performance seems rather cheap, doesn’t it? Of course, if you don’t do any serious work with your system and want a little speed boost for your games, disable CPU L2 Cache ECC Checking by all means.

But if you are overclocking your processor, ECC checking may enable you to overclock higher than was originally possible. This is because any single-bit errors that occur as a result of overclocking will be corrected by the L2 cache’s ECC function. So, for most intents and purposes, I recommend that you enable this feature for greater system stability and reliability.

Please note that the presence of this feature in the BIOS does not necessarily mean that your processor’s L2 cache actually supports ECC checking. Many processors do not ship with ECC-capable L2 cache. In such cases, you can still enable this feature in the BIOS, but it will have no effect.

Go Back To > The Tech ARP BIOS Guide | Home

Support Tech ARP!

If you like our work, you can help support our work by visiting our sponsors, participating in the Tech ARP Forums, or even donating to our fund. Any help you can render is greatly appreciated!

Having L2 cache problems? If your L2 cache fails, you’re probably suffering system-locking conflicts much the way a memory error will stop a system cold. The following are possible indications of cache problems:

• Unexplained system crashes or lockup
• The system fail to boot, or it stalls during a POST routine
• Seemingly random data error
• Unsually slow performance

Unfortunately, not many utilities can help you when it comes to L2 cache Problems. The cache interacts with your PC procssor and main memory at the lowest level, well below the notice of the operating system or its applications.

On pentium systems, the chipset knows if a cache is present and how large it is. It then sets internal bits that the BIOS can read. On older 486 systems,jumpers are used to set cache informationindependent of the BIOS.

If during the POST test you see the Massage System L2 Cache Problems Error — cache Disabled, the cache SIMM is probably bad. Although the PC will continue to run, it will do so without the benefit of L2 cache, affecting perfomance significantly.

Although you can try usual tricks, you might be looking at cache purchase. You can use a low-level diagnostic program, such as AMIDiag 5.0, to check on your cache. AMIDiag 5.0. If you’re experiencing system lock-ups that don’t seem related to RAM or other components, you can easily isolate the problem if it resides in COAST- format L2 cache. After you’ve encountered the symptom, do the following:

• Shut down the machine, unplug the power supply, and remove the cover.
• Making sure you’re properly grounded, lift the L2 cache from its socket. If the module won’t budge, try getting it started by pulling up one edge slightly and then evening the second edge.
• With the cache removed and place in safe location, plug your computer in and reboot.
• If your PC uses manual setting for cache configuration, enter your computer’s BIOS setup routine. Go to the section that controls cache settings and change the setting to 0 or No cache.
• Exit the BIOS setup environment, making sure to save changes.
• Complete boot-up and use the computer normally.

If the problem fails to recur, you’re probably experiencing trouble with the cache SIMM, or perhaps with the way it was seated. You should note whether you experience any noticeable degradation in performance after removing the L2 cache.

If not, your cache might not have been working properly in the first place. If this is the case, replacing the module should result in a welcome 20 to 25 percent perfomance boost.

Troubleshooting L2 Cache Problems

So you think your cache might be the culprit? Like RAM, the news is good and bad. If the cache memory modules themselves are bad, they’re gone. There is simply no repairing 15ns static RAM chips.

The good news is that the problem could just require a software tweak or minor adjustment. Here are a couple of things you should try before heading out to buy a new cache module.

Reseat The Cache Module

Press the module firmly into the COAST socket to make sure there is adequate contact between the pins.

Check Your BIOS

Go into the BIOS setting and try changing the cache settings. One possible culprit is that your BIOS is trying to conduct write through cache operations when only write back caching is supported.

Check For Overheating Problems

If problems occur only after sustained use, make sure you have proper ventilation in the chassis and that no wires are impeding airflow around the cache SIMMs.

See Also…

• How To Set Up CMOS Program Access
• Common Dll Issues and Solutions
• How to Fit CPU to Motherboard
• How To Delete the UpperFilters and LowerFilters Registry Values

Hello All,

Here’s my system specs. The Chip was NOT overclocked.

Motherboard: Asus Maximus Extreme (x38)

CPU: Intel Core 2 Extreme qx9770

Asus Geforce 6800

4GB OCZ Platinum DDR3 1600

WD Velociraptor

2x SAMSUNG Spinpoint F3 HD103SJ in RAID 1 Array

XIGMATEK HDT-S1283 120mm Rifle CPU Cooler

I believe I have a bad CPU as I have been getting a page_fault_in_nonpaged_area BSOD upon startup. I have eliminated all the other usual suspects. Here are the steps I have taken:

1) I have done memtest 3 times, once overnight. No Errors

2) Replaced the Power supply.

3) Pulled out and tessted how the machine with the RAM in different slots (i.e. only two RAM sticks at a time, shifting them to both slots after each successive failure.)

4) Reseated and eventually replaced CPU Fan & Heatsink.

5) Sent the motherboard in for repair.

6) Attemtped to boot up in Ubuntu Linux of a CD.

7) Booted up UBCD and ran CPU Stresstests. They always fail right away (i.e. Prime95)

Attempted Windows startup repair… BSOD

9) Attempted Windows Safe mode. Freeze and reboot.

10) Rolled back Motherboard BIOS to older version. I did this even though the last time I did a BIOS updatre was 8 months ago as a last ditch effort.

11) Bumped up the Voltage on the RAM to see if it needed more for stability.

12) Ensured the timins of the RAM in the BIOS matched the RAM Specifications.

I’d love to know if it could be something else, as this machine has been down for almost two weeks at this point. However, the L2 cache is the only thing I can think of that’s left. As a side note, the machine began doing this out of nowhere. First it would just shut down randomly every hour or so, then within a day all I could get was a BSOD.

Thanks.

Jamey