"BEX error" in "N360.exe"

Dear community,

I am experiencing the following problem:

 

Problemsignatur:
  Problemereignisname:    BEX
  Anwendungsname:    N360.exe
  Anwendungsversion:    12.11.0.16
  Anwendungszeitstempel:    524cbb5e
  Fehlermodulname:    StackHash_0a9e
  Fehlermodulversion:    0.0.0.0
  Fehlermodulzeitstempel:    00000000
  Ausnahmeoffset:    00000000
  Ausnahmecode:    c0000005
  Ausnahmedaten:    00000008
  Betriebsystemversion:    6.1.7601.2.1.0.256.48
  Gebietsschema-ID:    1031
  Zusatzinformation 1:    0a9e
  Zusatzinformation 2:    0a9e372d3b4ad19135b953a78882e789
  Zusatzinformation 3:    0a9e
  Zusatzinformation 4:    0a9e372d3b4ad19135b953a78882e789

 

Operating system Windows 7 64bit, no other AV software used. Clean install 7 days ago, problem has not existed before. Might be related to new drivers?!

 

Would highly appreciate a solution.

Dear community,

I am experiencing the following problem:

 

Problemsignatur:
  Problemereignisname:    BEX
  Anwendungsname:    N360.exe
  Anwendungsversion:    12.11.0.16
  Anwendungszeitstempel:    524cbb5e
  Fehlermodulname:    StackHash_0a9e
  Fehlermodulversion:    0.0.0.0
  Fehlermodulzeitstempel:    00000000
  Ausnahmeoffset:    00000000
  Ausnahmecode:    c0000005
  Ausnahmedaten:    00000008
  Betriebsystemversion:    6.1.7601.2.1.0.256.48
  Gebietsschema-ID:    1031
  Zusatzinformation 1:    0a9e
  Zusatzinformation 2:    0a9e372d3b4ad19135b953a78882e789
  Zusatzinformation 3:    0a9e
  Zusatzinformation 4:    0a9e372d3b4ad19135b953a78882e789

 

Operating system Windows 7 64bit, no other AV software used. Clean install 7 days ago, problem has not existed before. Might be related to new drivers?!

 

Would highly appreciate a solution.

Dear DistEd2,

I tried to use the solution from the Windows community forum using the DEP trick. However, Windows 7 ist telling me that I cannot set this attribute on a 64-bit executable file. I tried it with "Program Files (x86)\Norton 360\Engine64\21.1.0.18\uiStub.exe" as the "N360.exe" is referring to that file.

 

Your help is highly appreciated as this error drives me crazy (popping up again and again)

 

Best

OK; that actually makes sense, as it's a problem with 32-bit code being executed inside a 64-bit program. I saw a variant on the same solution that basically just tells the system to do that for all 32-bit files...so I'm going to operate on the theory that if "N360.exe" can refer to one file that isn't named "N360.exe" then it may be a central, 64-bit "routing point" within the Norton code that  passes execution to any file within Norton that it needs to execute--many of which are 32-bit code--and that one of them is what's "really" causing your error.

 

This variant was on a tech tips kind of site that I wasn't familiar with, so I went with the Microsoft one instead. Here's the new one to try:

 

http://trendythisweek.com/bex-error-fix-windows-7/155/

 

This time, substitute "your Norton 360 folder" for "your game folder" in the instructions.

 

Keep us posted. I've never seen this happen to Norton before, so it's possible wwe just need to have you do a Remove-and-Reinstall. But let's try this first. You might also want to check and make sure your system date & time are correct.

 

V/R,

--DistEd2

 

Dear DistEd2,

Windows is not convinced :(


If I try to select the files from the Norton 32bit folder Windows says "This program must run with active Data Execution Prevention. You cannot turn off Data Execution Prevention for this program". This is for all files in the Engine Folder.

 

If I try to select the files from the Norton 64bit folder Windows says "DEP cannot be set for 64bit files". This is for all files in the Engine 64 Folder.

 

I have similar problems with another Win 8.1. computer. I really welcome any suggestions :/

 

Thnks for your help.


Best

John

OK, it sounds like you have your DEP settings correct, then. That is the only solution for this problem that I've seen.

 

There is one more thing we can try here, and that's the Norton Remove and Reinstall tool:

 

https://support.norton.com/sp/en/us/home/current/solutions/v60392881_EndUserProfile_en_us

 

If that doesn't work, you're probably going to need to pursue a solution via a Microsoft forum ( maybe http://www.sevenforums.com/ ), as this is actually an issue with Windows and not Norton, and you're likely to find more of the most relevant expertise there.

 

Keep us posted!

 

V/R,

--DistEd2

I have tried the tool already. Thanks for your assistance, lets see what Microsoft says :)

Try to keep you updated.

OK; good luck. Keep checking back here for a bit, too: I'm only one volunteer among many, so there may be other folks with better ideas or more experience with this error.

 

V/R,

--DistEd2

Hey hey,

I have executed the DEP turn off command: bcdedit.exe /set {current} nx AlwaysOff

Now I get an Appcrash, not a BEX error anymore. Trying to check the Win Forum, however in case you have an idea, please let me know :)

 

Problemsignatur:
  Problemereignisname:    APPCRASH
  Anwendungsname:    N360.exe
  Anwendungsversion:    12.11.0.16
  Anwendungszeitstempel:    524cbb5e
  Fehlermodulname:    StackHash_0a9e
  Fehlermodulversion:    0.0.0.0
  Fehlermodulzeitstempel:    00000000
  Ausnahmecode:    c0000005
  Ausnahmeoffset:    00000000
  Betriebsystemversion:    6.1.7601.2.1.0.256.48
  Gebietsschema-ID:    1031
  Zusatzinformation 1:    0a9e
  Zusatzinformation 2:    0a9e372d3b4ad19135b953a78882e789
  Zusatzinformation 3:    0a9e
  Zusatzinformation 4:    0a9e372d3b4ad19135b953a78882e789

 

----

 

Name der fehlerhaften Anwendung: N360.exe, Version: 12.11.0.16, Zeitstempel: 0x524cbb5e
Name des fehlerhaften Moduls: unknown, Version: 0.0.0.0, Zeitstempel: 0x00000000
Ausnahmecode: 0xc0000005
Fehleroffset: 0x00000000
ID des fehlerhaften Prozesses: 0xf4c
Startzeit der fehlerhaften Anwendung: 0x01cf19c1e31925cf
Pfad der fehlerhaften Anwendung: C:\Program Files (x86)\Norton 360\Engine\21.1.0.18\N360.exe
Pfad des fehlerhaften Moduls: unknown
Berichtskennung: 034bbc69-85b8-11e3-8f6d-028037ec0200

Well, reviewing your case, I note this was a clean install of Norton 360 a week or two ago. Was there any security software (McAfee, Kaspersky, Malwarebytes, SuperAntiSpyware, etc.) on your machine before--i.e., did you switch to Norton from something else, or buy a new machine with trials of a few things installed? Having multiple security products that scan your computer in real time will cause serious issues, and this could conceivably be a result of that. If this is the case, let us know which product(s), and we'll guide you to their specialized removal tools.

 

The other possibility the recent install brings to mind is that you might actually have been infected by some malware prior to installing Norton. Did you buy Norton because something had happened that caused you to wonder about this? Some malware is designed to bblock or interfere with the operation of security software the user might install to try to get rid of it, and if that's what you've got then we're going to need to direct you to a specialized forum where a trained "removalist" with additional tools can work with you one-on-one to pull it out by the roots.

 

The best way I have to check this under these circumstances is to ask you to download and install the free version only of Malwarebytes. This software omits the real-time scanners that the paid version contains, and so is safe to use with your Norton as a secondary scanner. Malwarebytes isn't as good at keeping nasties off your system...but it does have a knack for still being able to detect them after malware has already entrenched itself on a system. If it finds anything, do not let it remove it; just cut-and-paste the log it produces into a message here so we can see what we're dealing with.

 

V/R,

--DistEd2

I have not used any anti-virus software before. I have done a clean Windows (!) install around 10 days ago. Installed drivers and software and thats it. Started with Norton very early, second program after Firefox. Please find my report below, however I assume that malware is not the source.

 

Malwarebytes Anti-Malware 1.75.0.1300
www.malwarebytes.org

Datenbank Version: v2014.01.25.08

Windows 7 Service Pack 1 x64 NTFS
Internet Explorer 9.0.8112.16421
John :: TOSHIBA [Administrator]

25.01.2014 18:00:33
mbam-log-2014-01-25 (18-00-33).txt

Art des Suchlaufs: Vollständiger Suchlauf (C:\|X:\|)
Aktivierte Suchlaufeinstellungen: Speicher | Autostart | Registrierung | Dateisystem | Heuristiks/Extra | HeuristiKs/Shuriken | PUP | PUM
Deaktivierte Suchlaufeinstellungen: P2P
Durchsuchte Objekte: 385800
Laufzeit: 45 Minute(n), 30 Sekunde(n)

Infizierte Speicherprozesse: 0
(Keine bösartigen Objekte gefunden)

Infizierte Speichermodule: 0
(Keine bösartigen Objekte gefunden)

Infizierte Registrierungsschlüssel: 0
(Keine bösartigen Objekte gefunden)

Infizierte Registrierungswerte: 0
(Keine bösartigen Objekte gefunden)

Infizierte Dateiobjekte der Registrierung: 0
(Keine bösartigen Objekte gefunden)

Infizierte Verzeichnisse: 0
(Keine bösartigen Objekte gefunden)

Infizierte Dateien: 0
(Keine bösartigen Objekte gefunden)

(Ende)

Huh. In theory, there shouldn't have been much likelihood there for an infection. And yet there (unless I'm being confused by something in the German language report) is a Potentially Unwanted Program, or "PUP."

 

Ordinarily, given all this, I'd probably have just told you to let Malwarebytes take care of it, and sent you on your way to sevenforums to try to straighten out the Windows issues. However because we are pretty much at the end of the things we could try to resolve it--treating it as just a Windows or Norton issue--I think I'm going to suggest you go to one particular removalist forum (info copied from delphinium's list on our Tech Outpost):

 

Bleeping Computer:

Always very good.  They run scans to check the system first before any removals, they use the latest tools, and if they run into trouble, they have the ability to fix Windows problems as well.  They have higher level specialists to handle the higher level infections.  They will ask you to remove illegal software and u-torrent.

 

Because they are so well known, it can be a lengthy wait to get assistance.

 

http://www.bleepingcomputer.com/forums/f/22/virus-trojan-spyware-and-malware-removal-logs/

 

 

As delphinium notes, they'll be up to the task of the worst malware you might have...but they'll also be happy to straighten it out for you if it's "just" a PUP and a Windows 7 issue.

 

V/R,

--DistEd2

 

[Edit: I can't quite reconcile what appears to be a PUP detection with what appear to be "0" threats detected in each Malwarebytes category--so I may be misunderstanding the translation somewhere. But given the uncertainty, plus the fact that there's definitely a tricky Windows problem involved, I'd rather err on the side of caution--unless someone else comes along with a fresh perspective and some better ideas.]

Don't forget about hardware DEP.

Your BCD edit turned off software enforced DEP,  You need to go into the BIOS and disable the "NX" or "NoExecute" bit if it is supported.

 

Of course, that would juet be a trobleshooting step.  I ideally you want your system to work with DEP enabled.

If disabling the NX bit makes the error stop I would concentrate on your first assumption, it's a driver.

 

Dave

It seems that I could isolate the error. When I deinstall my graphics driver the error disappears. Currently, I use the offical and newest Intel graphics driver for my chipset, however the error still occurs :( Quite frustrating. In case you have any further ideas - highly appreciated!

How is your chipset driver?

When setting up a new build the latest chipset driver should be installed first, expecially before graphic  and USB.

I used to be tempted to install the graphic driver first so I could "see everything" better but without the chipset driver the onboard hardware may not get correctly identified.

 

If you started with the graphic driver, try reapplying the chipset driver and then the graphic driver.

 

Dave

You say it was a "clean install" but I'm not sure if it was a new build or an existing system that had a working operating system on it before.

 

If it's a new build it could also be incompatible RAM or an issue fixed in a BIOS update.

I'm always reluctant to update a BIOS unless I find something in the "readme" file that pertains to the problem being experianced.

 

If it's a existing build that had another version of windows installed before then you can rule out a RAM problem but not necessarily a BIOS correction.

 

If it had a working version of windows 7 on it before then there is no reason why it will not work with the latest drivers.

 

Dave

Dear Dave,

I had Wind 7 64bit on the machine before. I whiped the hard drive and set up a new install with USB. However, your first thought might be a good idea to check as I have installed the graphics driver first. So, would it be sufficient to deinstall graphics, USB, chipset, restart and then install in this order: chipset, usb, graphics?

 

Best

John

I would uninstall 360 using the option to save all settings and click no to installing the free toolbar.

Then reboot and uninstall the grapic driver if you put it back on.  You can leave the rest of the drivers.

re-install the chipset driver right over the top, reboot and reinstall the graphic driver.

Verify that Aero is working and set the screen resolution to what you like.

 

Personally I hate DEP but I would re-enable both hardware and windows DEP and make sure the system can go through a few reboots without any errors.  Norton was not causing those errors in the first place regardless of what the error report was saying.

 

Then I would install 360 again and see what happens.

If you had everything working on the same system before with the same version of windows I see no reason why you should have any errors at this point unless you have some kind of graphic related program or tool that was not present on the old installation.

 

Best of luck,

Dave

Dear Dave,

as you pointed out I tried the following:

 

1. Uninstalled N360, however I used the removal tool.

2. Reboot

3. Uninstalled INTEL graphics driver

4. Reboot

5. Re-Installed INTEL Chipset driver

6. Reboot

7. Installed INTEL graphics driver

8. Installed N360
 
Same error :(
 
I used the removal tool, however I do not feel that a different removal strategy might fix the issue. Maybe I try to remove Norton and use another Anti-virus tool. Just for the sake to test the virus / malware hypothesis again.

However, it crushed once, restarted and now it runs. So lets see how it works out over the next days.