Unseen

It should be IW... they usually switch each release..

OR do the above and type in 3arc unlock

i've been running core temp, and logging my temps.. it never goes above 50 C on my CPU and 64 C on my GPU.. So well below my max's..

Okay, So i've been having black ops freeze issues the last week or so. I am running a good rig; Core 2 Duo Wolfsdale (E8400) oc'd 3.40 GHz Cooled with coolermaster V6 with 2 120mm fans at an average load temp of 45-50 C Intel dp45sg extreme mobo 8gb 1333 Kingston Ram Removed my SSD and am now running 2 1TB Seagate 7200 RPM HDD's configured to Raid0 (SSD was giving me problems) Fresh install of windows 7 pro 64 ati 5770 1gb ddr 5 video Antec 550 watt PSU So the game has been running fine up till last week, after about 2 hours of solid gaming it will lock causing me to ctrl-alt-del and force close the application. So I figured problem with the game it self, so I uninstalled re-installed updated ALL drivers.. still same problem.. I than went deeper, opened up msconfig and shut down processes I figured would not be needed... Same problem.. so I said eff it, did a format reload, and removed my ssd as it was having some weird issues and I just configured my drives to raid0... okay so fresh install, all updated drivers etc.. same problem... Looked up some .cfg changes etc.. and tips and tricks for people who have been having problems with freezes etc.. same problem... I got pointed towards my oc'd processor so I dialed it back down to original clock settings, same problem.. I am at an end.. I ran a system diagnostic, all my hardware passed with flying colors.. But still I am wondering if it is possibly my CPU or Vid card (although its brand new).. I dunno nothing is sticking out at me as being a major problem? This is the only game that does it as well, MOH and BFBC2 run perfectly fine, same as WoW.. any help would be much appreciated. THANKS

I am going to give that a try, yet I have not seen a root kit like this before. Usually I can get by with rkill and combo fix bam done! I have something I can try, its called hirens boot cd, http://www.hiren.info/pages/bootcd. This boot cd has EVERYTHING you need, i'm going to see what I can do DOS wise, but its seeming right now that the easy path is going to be data backup and format reload. ugh, and a 2nd/3rd computer have just come in with it.

I don't seem to see one lying around my shop.. Do you have a website you could point me towards? Like I said before, any attempt to modify, replace.. delete causing immediate BSOD. It is a NASTY root kit..

BSOD :/

That I haven't tried, but... hrmm BRB!

Sadly there is no way this time around, it will BSOD.. We've tried everything we could to get this thing off but we ended up booting into linux and pulling the data off.

see my above post about TDL3, sounds to me like an infection of some sorts.

Hey guys, so came across something very nasty today. Had a to do a virus removal today, on my run of combo fix it came up as a "root kit detected" so anyways gave me a path to the root kit etc.. This root kit is called "TDL 3" short for total data loss 3. When you attempt to open the path to this root kit it WILL blue screen your system. If you attempt to boot into safe mode with out it enabled it WILL blue screen you system. After running combo fix, removing and restarting it was still there. "TDL3 is the third generation of TDSS which uses rootkit technology to hide itself on a system by infecting drivers like atapi.sys, iastor.sys and a few others. Atapi.sys is a common target for this rootkit because it loads early during the boot process and is difficult to detect. Common symptons/signs of this infection include: •Google redirection. •Slowness of the computer and poor performance. •BSODs that occur immediately after XP splash screen appears. •infected atapi.sys and iastor.sys. Here is a little more information." http://virusvn.com/download/video-tutorial/tdl3_analysis_paper.pdf This virus has just emerged in the "wild" and at this point even has virus removal companies stumped. It is smart as it hides it self within your win32 drivers directory, when it is detected it shuts everything down and re-hides it self a BSOD will appear usually with an error pointing to "sptd.sys". So just a heads up, the only known fix as of right now is data back up and format reload of the OS.

okay, 2 pics for now! there we are sorry kind of dark.. I just did a system clean up and cable management for now... waiting on new psu and etc.. to go in!

if anyone is looking for a signature i'd be happy to throw one together for ya. just let me know what you want in it etc..