Welcome to another edition of Maximum PC Theater. For our main attraction this evening, we’re featuring a play by Vigor Gaming entitled Force Recon QXN. There’s a scene in act 1 in which the computer utterly fails to run in any useful capacity… it brings tears to our eyes. Be sure you don’t miss it.
Or, rather, do miss the Force Recon QXN. As has become an unfortunate tradition at Maximum PC, we again find ourselves with a system that looks sweet on paper but utterly fails the quality assurance part of the benchmarking process. In layman’s terms, it does not work. It fails to boot consistently. It fails benchmark runs.
We blame overly aggressive overclocking for this electronic disaster. Like those who came before it, Vigor cranked an Intel QX6700 quad-core processor from the stock speed of 2.66GHz to a mighty 3.46GHz. But we certainly don’t blame the company for doing so; in today’s extreme-computing (and non-multicore-supported) environment, a stock-clocked quad-core processor simply can’t hold up to dual-core clock speeds.
See that wiring job? Now that’s quality work. At least your new footrest will look great.
If only Vigor had spent as much time testing the machine as it put into its appearance, we might have had an actual working computer. This system is loaded with more tweaks than any of the similarly configured quad-core machines we’ve reviewed, so we were a bit surprised to see lower frame rates in all of our gaming tests (when they ran). Our quad-champion Maingear F131 (reviewed in our January 2007 issue) destroyed the poor Force Recon by almost 15fps in FEAR and 20fps in Quake 4.
Application testing painfully highlighted the Force Recon’s stability problems, particularly our standard video encoding test, in which we use Nero Recode to transform a DVD-quality rip of Terminator 2 into an H.264-based video iPod file. It’s as if the Force Recon took one look at the project and decided to head out for a smoke break. The process took nearly 40 minutes to complete, almost double the 22-minute score the Maingear laid down.
We were beginning to wonder if we should just take this sick machine out back and shoot it, but the Force Recon didn’t even make it out the door. The machine officially died during our Premiere encoding test. No blue screen, just random restarts.
When SYSmark caused the same problems, we set all the components back to stock clock speeds, but the system got progressively worse. After Force Recon started to reboot spontaneously, we gave Vigor a call, and the company sent us a recovery-disc image.
Said recovery disk ended up destroying what was left of the system. Windows barely made it to the loading screen before blue-screening.
The final nail in the Force Recon’s coffin is that it actually ran slower than all of the other nonworking systems we’ve tested, at least in the benchmarks we got to run. That’s certainly not something to be proud of.
Share to Facebook
Tidak ada komentar:
Posting Komentar