Generic APPCRASH and BEX Related Errors

[xfimblex]

I just signed up today to write this post, I hope it helps someone because it stumped me good for a bit.

The other day I reinstalled my operating system (Win7 Pro 64bit) to clean it up as I sometimes get the urge to do. After doing that and reinstalling my critical applications I found that ePSXe no longer worked! It worked beautifully prior and for a good while before. Also for what it's worth, it never has worked on my work PC (also Win7 Pro 64bit) though I never cared much as I don't need it at work anyway and thus didn't spend much time troubleshooting it.

The emulator would die when loading a game or simply running the BIOS. Checking eventviewer logs I was getting a generic APPCRASH entry. None too helpful.
http://i.imgur.com/kpSWv.jpg

I checked everywhere for solutions and tried out many different things (many from these boards) but nothing worked. The problem in my case ended up being my TeamViewer application. More specifically the "QuickConnect" feature it has. This feature overlays a small button to the top of any open window and that feature is what was causing the problem.

So you've got two options if you're a TeamViewer user:

• Simply stop the TeamViewer application
• Or keep it running but go into its options and disable the "QuickConnect"

Here's some pictures on how to disable the "QuickConnect" button:
http://i.imgur.com/ep6T3.png
http://i.imgur.com/NNcxY.png


Once I nipped that issue at home and it all worked again, I decided to try ePSXe on my work PC expecting it to work but to my dismay it still didn't. It would crash at the same exact spot as before but this time I got the BEX error. Not worrying since this one is pretty well documented here and elsewhere I figured I'd simply add an exception to DEP for ePSXe.exe and I'd be fine. The exception however didn't work! Disabling DEP outright, globally did though. I couldn't care less about having ePSXe at work but if the exception doesn't work for anyone else here's the commands to manipulate DEP globally on Win 7 (and presumably Vista):

First open an elevated command prompt and type the appropriate command and then reboot your PC (reboot is required!):

To disable DEP:
bcdedit.exe /set {current} nx AlwaysOff

To enable DEP:
bcdedit.exe /set {current} nx OptIn

If for some reason you want to more easily be able to toggle this on or off at will you can create a batch file and stick that on your desktop. Run it as an Administrator and select the appropriate option. Here's a batch file that could do that for you:

@ECHO OFF

cls
ECHO.
ECHO This utility will enable or disable Data Execution Protection. A reboot is required before changes will take effect.

:start
ECHO 1. Enable DEP globally
ECHO 2. Disable DEP globally
ECHO 3. Enable DEP globally and reboot computer.
ECHO 4. Disable DEP globally and reboot computer.
ECHO.
ECHO.
set /p choice=Please choose an option:
if not '%choice%'=='' set choice=%choice:~0,1%
if '%choice%'=='1' goto enable
if '%choice%'=='2' goto disable
if '%choice%'=='3' goto enableandboot
if '%choice%'=='4' goto disableandboot

ECHO "%choice%" is not valid please try again
ECHO.
goto start


:enable
bcdedit.exe /set {current} nx OptIn
goto end


:disable
bcdedit.exe /set {current} nx AlwaysOff
goto end

:enableandboot
bcdedit.exe /set {current} nx OptIn
ECHO.
goto reboot


:disableandboot
bcdedit.exe /set {current} nx AlwaysOff
ECHO.
goto reboot


:end
ECHO.
pause
exit

:reboot
ECHO Initiating a reboot...
pause
shutdown.exe /r /t 3

[jperkins79]

I just registered here, so that I could post this:

@xfimblex
THANK YOU! THANK YOU!

Seriously dude, I thought my computer was hosed up royally (and this was after I just did a fresh OS install a month ago). I'd been trying everything I could think of to get this fixed. I even went as far as creating a new virtual machine, which didn't work anyway (due to lack of real video hardware, is my thought...).

Anyway, this was exactly what caused the problem. I use TeamViewer a lot, and that was what was causing my generic 'APPCRASH'.

Ahh.... I'm so glad this is fixed. I've been working very hard on getting an all-in-one arcade/HTPC together, and this was a major roadblock (I NEED my PSX! ;-) ). I'll have to make a script to close out TeamViewer when running my emulator front end (GameEx, very awesome - I highly recommend it), but that's easy.

Anyways, thanks again! I very much appreciate you taking your time to post this fix. Most people don't think about it, but even if you solve your own problem, let us know, it can help others in the future who end up having the same problem

[xfimblex]

Originally Posted by jperkins79

I just registered here, so that I could post this:

@xfimblex
THANK YOU! THANK YOU!

Seriously dude, I thought my computer was hosed up royally (and this was after I just did a fresh OS install a month ago). I'd been trying everything I could think of to get this fixed. I even went as far as creating a new virtual machine, which didn't work anyway (due to lack of real video hardware, is my thought...).

Anyway, this was exactly what caused the problem. I use TeamViewer a lot, and that was what was causing my generic 'APPCRASH'.

Ahh.... I'm so glad this is fixed. I've been working very hard on getting an all-in-one arcade/HTPC together, and this was a major roadblock (I NEED my PSX! ;-) ). I'll have to make a script to close out TeamViewer when running my emulator front end (GameEx, very awesome - I highly recommend it), but that's easy.

Anyways, thanks again! I very much appreciate you taking your time to post this fix. Most people don't think about it, but even if you solve your own problem, let us know, it can help others in the future who end up having the same problem

I posted this in the hopes Google would invariably lead someone to it and ultimately to their solution. Glad it found you!

[tapeq]

ePSXe.exe PE Image have disabled NX in header so system should not use DEP. Problem can be some DLLs (plugins etc) loaded to ePSXe process, not ePSXe itself. For me all ePSXe's from version 1.0.0 to 1.8.0 works fine without changing anything.

[Squall-Lionh@rt]

The DEP crash tends to be a bug in the CPU microcode due to running an old bios or your mainboard vendor totally left you in the dark and failed to patch the issue.

The crash tends to occur in an windows module (like kernel32.dll) where it should NEVER occur.

[jperkins79]

Originally Posted by xfimblex

I posted this in the hopes Google would invariably lead someone to it and ultimately to their solution. Glad it found you!

Oh my gosh... so am I. Again, thanks so much!