stop!theradio
2[H]4U
- Joined
- Jul 13, 2007
- Messages
- 3,523
Alright so I've been running it with the 4th core unlocked without issue since October 13th. I have it overclocked to 3.4ghz. I've done increments of 3 hours at a time with Prime95 without fail. (I know some of you will say that's not good enough, though that's a different issue). I game quite a bit (Fallout New Vegas, GRID, some Far Cry 2), and though CPU usage is high when I game, it runs just fine without issue.
My point it this - my machine is absolutely stable for anything and everything I need it to do. Photoshop mainly, Premier and Media Encoder occasionally, gaming often, etc. The thing is, I decided to go to the event viewer and check out some things, and I see a constant stream of "A corrected hardware error has occurred - cache hierarchy error - error reported by: CPU core - Core ID: 2." This error is reported pretty much every few seconds, but I have no issues at all. I know it's because I have the 4th core unlocked - I locked it back up to stock and sure enough, the "error" is no longer there. But when I unlock the core again, the error is back in the event viewer, but the computer runs just as stable as ever, with zero issues aside from this reported error.
is this something to worry about? Or is it Windows simply being confused about reported core count versus detected cores and cache allocations? It seems to me since it says "corrected hardware error" that it fixes the issue without difficulty. Any info would be good, thanks!
My point it this - my machine is absolutely stable for anything and everything I need it to do. Photoshop mainly, Premier and Media Encoder occasionally, gaming often, etc. The thing is, I decided to go to the event viewer and check out some things, and I see a constant stream of "A corrected hardware error has occurred - cache hierarchy error - error reported by: CPU core - Core ID: 2." This error is reported pretty much every few seconds, but I have no issues at all. I know it's because I have the 4th core unlocked - I locked it back up to stock and sure enough, the "error" is no longer there. But when I unlock the core again, the error is back in the event viewer, but the computer runs just as stable as ever, with zero issues aside from this reported error.
is this something to worry about? Or is it Windows simply being confused about reported core count versus detected cores and cache allocations? It seems to me since it says "corrected hardware error" that it fixes the issue without difficulty. Any info would be good, thanks!