Jenner
#0
Hej gutter....
Hvis jeg køber et intel baseret micro-atx bundkort, som er oplyst til at kunne køre med de nye 1333mhz cpu'er, kan jeg så være sikker på, at jeg også kan smide en 1066mhz cpu i, og clocke den til 333 mhz fsb?
Mvh
PS.. Har endelig fået lov at skifte mit efterhånden aldrende system ud, så jeg leger med tanken om at skaffe mig et micro-atx kabinet fra Lianli i stilren sort og så skal der et lille, men lækkert vandkølingssystem ind i, hvis det kan lade sig gøre 😀!!!
Hvis jeg køber et intel baseret micro-atx bundkort, som er oplyst til at kunne køre med de nye 1333mhz cpu'er, kan jeg så være sikker på, at jeg også kan smide en 1066mhz cpu i, og clocke den til 333 mhz fsb?
Mvh
PS.. Har endelig fået lov at skifte mit efterhånden aldrende system ud, så jeg leger med tanken om at skaffe mig et micro-atx kabinet fra Lianli i stilren sort og så skal der et lille, men lækkert vandkølingssystem ind i, hvis det kan lade sig gøre 😀!!!
#1
Du er garanteret, at bundkortet kan køre 333mhz FSB. Du er til gengæld ikke garanteret, at du kan ændre de instillinger i BIOS der skal til, før du får din cpu op på 333mhz FSB. Hvis du forstår?
#3
Hmm.. Nogen der ved, om det virkelig er så slemt med de amd phenoms der er ude lige for tiden? Vil de ikke køre ting som 3dmark og spil ordentlig ? 😕
#4
De cpu'er er slet ikke så dårlige, man får bare ikke så meget ydelse som ved intel.
#5
Med hensyn til Erratum 298 som fejlen ved processorerne hedder syntes jeg at AMD gav et godt svar til Legit Reviews
"It's unfortunate that the TLB erratum that affects the AMD Phenom 9500 and 9600 processors has garnered as much attention as it has. Unfortunate not just for AMD, but for customers because I believe it has been blown out of proportion. Every processor, ours and our competition's, has errata. Phenom is no different. Erratum number 298 is L3 protocol issue which can cause a system hang when running certain client workloads. That may sound scary, but some perspective is needed. It is extremely unlikely desktop users are going to find themselves in a scenario that could trigger this erratum. I won't go so far as to say no one will ever see it, because I'm not going to claim absolutes like that, and AMD wants to always land on the side of caution and prudence. That's why I'd point out that the fix is in. We've communicated a BIOS modification to motherboard vendors that will ensure system stability, and we're implementing a silicon fix in future CPUs. But what really stands out to me is that we put a switch in the AMD OverDrive utility that enables PC users to disable the BIOS workaround. That should send a message of our confidence that desktop users should not lose sleep about this particular erratum." - AMD PR to Legit Reviews on 12/19/2007 (http://www.legitreviews.com/ar... )
"It's unfortunate that the TLB erratum that affects the AMD Phenom 9500 and 9600 processors has garnered as much attention as it has. Unfortunate not just for AMD, but for customers because I believe it has been blown out of proportion. Every processor, ours and our competition's, has errata. Phenom is no different. Erratum number 298 is L3 protocol issue which can cause a system hang when running certain client workloads. That may sound scary, but some perspective is needed. It is extremely unlikely desktop users are going to find themselves in a scenario that could trigger this erratum. I won't go so far as to say no one will ever see it, because I'm not going to claim absolutes like that, and AMD wants to always land on the side of caution and prudence. That's why I'd point out that the fix is in. We've communicated a BIOS modification to motherboard vendors that will ensure system stability, and we're implementing a silicon fix in future CPUs. But what really stands out to me is that we put a switch in the AMD OverDrive utility that enables PC users to disable the BIOS workaround. That should send a message of our confidence that desktop users should not lose sleep about this particular erratum." - AMD PR to Legit Reviews on 12/19/2007 (http://www.legitreviews.com/ar... )