Windows Start Up Error b.exe

[Guest]

When Windows starts up.... an error reporting message pops up saying
"b.exe has encountered a problem and needs to close. We are sorry for the
inconvenience."

And this is the error signature that appears in the details:
AppName: b.exe AppVer: 0.0.0.0 ModName: b.exe
ModVer: 0.0.0.0 Offset: 000c4000


And the report also refers to this file
-- C:\DOCUME~1\pramod\LOCALS~1\Temp\a7ea_appcompat.txt


Could anyone please help me out in figuring what this is actually about...

Appreciate a response..

Regards,
Pramod

 

[Radenko Zec]

Simple remove that b.exe from startup.

 

[DL]

Thats because your sys is infected by trojan/virus.
Turn off sys restore
Run an online scan eg www.trendmicro.com
Download SpyBot , Adaware , windows Defender and update run them all
http://www.microsoft.com/security/default.mspx
Do not turn on sys restore untill the sys is clean

 

[steam3801]

When Windows starts up.... an error reporting message pops up saying
"b.exe has encountered a problem and needs to close. We are sorry for the
inconvenience."

And this is the error signature that appears in the details:
AppName: b.exe AppVer: 0.0.0.0 ModName: b.exe
ModVer: 0.0.0.0 Offset: 000c4000


And the report also refers to this file
-- C:\DOCUME~1\pramod\LOCALS~1\Temp\a7ea_appcompat.txt


Could anyone please help me out in figuring what this is actually about...

Tried a Google search for "b.exe"? Incredible what that finds ....

 

[cquirke (MVP Windows shell/user)]

On Sun, 7 May 2006 00:11:02 -0700, Pramodpaluri

When Windows starts up.... an error reporting message pops up saying
"b.exe has encountered a problem and needs to close. We are sorry for the
inconvenience."

And this is the error signature that appears in the details:
AppName: b.exe AppVer: 0.0.0.0 ModName: b.exe
ModVer: 0.0.0.0 Offset: 000c4000

And the report also refers to this file
-- C:\DOCUME~1\pramod\LOCALS~1\Temp\a7ea_appcompat.txt

Could anyone please help me out in figuring what this is actually about...

There's unlikely to be any legitimate "b.exe" file, so you're most
likely infected by some malware or other.

Although this may be the most common thing to go wrong in the world of
Windows, MS offers no tools to manage this properly (i.e. that does
not involve running the infected code base you are trying to clean).

Google( Bart PE). Yes, it takes some smarts to learn and use, but at
least it's possible, in spite of MS's failure to step up to the plate.

---------- ----- ---- --- -- - - - -

Don't pay malware vendors - boycott Sony