Cannot kill BF3.exe

Capt Caveman

Lifer
Jan 30, 2005
34,543
651
126
Starting tonight when I attempted to start BF3, it wouldn't open. The process BF3.exe would be listed in the Taskmanager but I am not able to kill it.

I've used taskmanager, pskill, etc and the process will not go away. Prior to tonight, I could terminate it.

To add insult to injury, I am also not able to shutdown or restart Windows 7 x64, I'm forced to poweroff the computer to shutdown/restart.

Google search hasn't found a problem. Note, the process BF3.exe is not shown to be an active process either. I've tried restarting BF3.exe with no success. I have also performed a repair of BF3(thru Origin). No success.

Anything else I should try?

edit - nvm, doing some more searching I discovered the problem. For some reason now, I needed to add BF3.exe to the Trusted Process list of the Behavioral shield of my AV software.
 
Last edited:

0___________0

Senior member
May 5, 2012
284
0
0
Try Process Hacker 2, its runs a driver that can kill pretty much anything, even AV products.

Do you have a recent system restore point from before the problem occurred? Might try that.

What does Origin's repair do? Does it remove and reinstall everything? Or just look for corrupted files?
 

Capt Caveman

Lifer
Jan 30, 2005
34,543
651
126
Try Process Hacker 2, its runs a driver that can kill pretty much anything, even AV products.

Do you have a recent system restore point from before the problem occurred? Might try that.

What does Origin's repair do? Does it remove and reinstall everything? Or just look for corrupted files?

Thanks for the recommendation. I didn't try that program.

Yes, I had a system restore but with the issue being the AV program. My guess would reupdating the AV engine would cause the issue again.

The Origin repair was for BF3 only(right click on BF3 icon within Origin gives you some options, one of them is Repair), it says it repairs corrupt files. I ran it a couple of times, the first time it downloaded a 99mb file and the next time 26mb.

edit - I'm actually thinking the problem came from the latest Origin update that occurred the other day.
 
Last edited:

Nothinman

Elite Member
Sep 14, 2001
30,672
0
0
An unkillable process means it's waiting on something in the kernel, usually I/O to/from disk or network and killing it before that completes would likely cause the kernel to crash.