Level 3 cache detected?

Page 2 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.
Alright. I'm back. Im on the new computer and i found the motherboard.

AsusTek Model: EMERY

I did some search on it and no results. On ASUS site too.

My L2 cache is pretty hign. 2048 KB.
My hard disk is a SamSung.
On CPU-Z it say: L1 Cache: 16 KB
8-way
Line size: 64 kb
Adaptive.

L1 trace: size: 12 kuops 8-way

CPU instruction: MMX SSE SSE2 SSE3 EM64T


Is that good? My computer is 32 or 64?

FSB: 200.1 MHz
Bus Speed: 800.3 MHz
2800.9 MHz
CPU clocks:
 
My computer is not home builded. I buyed it. Here the full computer name:

HP Media Center PC m7350n

And for my old computer, i had only 1 stick of RAM. 512 mb.
 
This forum is suposed to help right?

You have 2 pages of replies over a 2-day period.

I would suggest not insulting the people that are trying to help.

If you don't get an answer to your question, please rephrase it or be more specific. Your english is a little choppy and people might not understand the question.
 
Help how? Everyone knows that HP specifies their own boards, and that mid-range HP's generally use Asus boards that are modified from the standard version by removing features.

I din't not know that. Why din't u tell me? And sorry for my english, im a french.
 
Well first, your BIOS is out of date. Try updating that first.

While CPU-Z reports your BIOS as version 1002 of Motherboard P4S8X-X, the specifications for your HP box says it's something else - a P5LP-LE.

In either case, your BIOS version is out of date.

Lastly, the answer to your question lies in the "staging" of the L2 Cache. - Or you could say that the access granularity results in the "increased latency". Technically, the test is detecting the cache correctly, and incorrectly depending on how you look at it. Obviously in your CPU there is more than one stage of the level 2 cache, or there is an access granularity issue, where only a certain amount of L2 cache can be pulled from one access method.