Let me preface this by saying that I have tried deleting and reinstalling the bin folder, I am running as both administrator and am in XP compatibility mode, added "-dx9" to the command line for the shortcut, downloaded and installed the dual core thingy that was recommended, my .net is up-to-date, as well as my drivers, I added an exception to Windows firewall, and I am using the Live server. When I launch the game from the launchpad I get the initial splash screen, the game loads, then as soon as the music starts during the loading screen the game crashes with a white screen. I included what showed up in the crash reporter. I have sent a ticket and am waiting for a response still. Can anyone help? Problem signature: Problem Event Name: BEX Application Name: VGClient.exe Application Version: 1.0.2693.0 Application Timestamp: 50230917 Fault Module Name: VGClient.exe Fault Module Version: 1.0.2693.0 Fault Module Timestamp: 50230917 Exception Offset: 0095949a Exception Code: c000000d Exception Data: 00000000 OS Version: 6.1.7601.2.1.0.256.48 Locale ID: 1033 Additional Information 1: 7ebb Additional Information 2: 7ebb7d15d681a1243d6ba9a079247f07 Additional Information 3: 236b Additional Information 4: 236b8bdd5862173071deef42fa07e6c7
Hi BeakCha, I'm probably not the best person to try to give you advice about this; but I hate hearing that the game is crashing for you so thought I'd offer a quick "this is a possible cause." First up, -dx9 shouldn't do anything special from the game logic standpoint. Also, you probably do not need to worry about the UAC (the normal reason for running in XP mode or administrator mode). I personally am also unaware of any need to punch a hole in your firewall for any inbound traffic in order to play vanguard. I used to work in the platform group and am thus always suspect of any suggestion that laxing secuirity is the answer for playing a client side game. So please re-enable all that stuff . Now, on to your actual problem. A white screen crash is usually indicitive of the graphics pipeline having some issues. Or in a more professional response: To help verify what's causing this issue; try out some graphics benchmark apps: http://www.3dmark.com/3dmark11/. The likelihood that it is the graphics pipeline goes up if you experience this with other games that are graphics heavy; however, it naturally goes down otherwise. If you are seeing issues elsewhere and aren't getting expected proformance from a benchmark suite; then I'd recommend looking for dust bunnies hanging out near the GPU (overheating is a common scenerio). If, however, you aren't seeing issues anywhere other than Vanguard, then the below error is the next thing that I'd want to investigate: A BEX error means that there was a buffer overflow exception. I don't necessarily see anything in the crash report that would help point me to the right place to see if I can find the issue directly. However, if vanguard does crash for you and generate a minidump, it should request that it get sent in to us. That I can look at very easily and find out what happened. Also, as always, please use the petition and support system we have at SOE; those guys are great, very knowledgeable and should be able to get your problem solved much faster than I. Thanks for Playing!
BaakCha wrote: Can you post your system? be easier to offer help, but here are some ideas: 1 delete the vanguard cache folder 2 Delete vgclient.ini 3 install latest video drivers, then latest DX 9 4 make sure Vanguard is NOT in the program files, if so move it out to its own directory or under c:\games\vanguard as an example 5 make sure you have LP4 6 Launch game, go into options and do a file scan. let us know.
My computer: AMD Athlon 64 X2 6000+ 3.00 GHz 4Gb RAM DDR2 Windows 7 64-bit nvidia geforce 9800gt AMD chipset 780G MS-7411 To gpx1000, here's my benchmark SCORE P4478 3DMarks GRAPHICS SCORE 4848 CPU SCORE 3642 PC HEALTH CHECK Your PC is performing properly. 3DMark Score 4478 3DMarks Graphics Score 4848 CPU Score 3642 Jane Nash 14.16 FPS New Calico 14.24 FPS AI Test 450 operations/s Physics Test 6 operations/s
You're not alone. I've been having the exact same crash. I'm running Win 7 64-bit with an nvidia Geforce GTX 550 Ti. I've tried reinstalling/updating drivers. Reinstalling the game, compatability modes. DirectX diagnostics, etc. to no avail.
Hmm... well I don't know off the top of my head what would cause it. So let me translate the microsoft(ese) exception and see if we can't figure it out from there. Problem signature: Problem Event Name: BEX == This means that a Buffer Overflow Exception Application Name: VGClient.exe Application Version: 1.0.2693.0 == As defined at compile time in Resource file Application Timestamp: 50230917 == defined when the exception happened Fault Module Name: VGClient.exe Fault Module Version: 1.0.2693.0 Fault Module Timestamp: 50230917 Exception Offset: 0095949a == This translates to somehwere in the code that sets the current window within Vanguard. As best I can tell this is the SendMessageW call. Exception Code: c000000d == This means STATUS_INVALID_PARAMETER Exception Data: 00000000 == This means no further information. So to sum up; it looks like something is wonky when we get in to setting up a render context to switch to. I don't see any core dumps reported; and this should have generated one. Let me ask around for how you can get me a core dump to look at in the meantime; some resources on how to generate a core dump by hand: http://blogs.msdn.com/debugger/arch...create-one.aspx Also; before we get too terribly far; please ensure you have the latest WHQL certified drivers from NVidia (latest driver): http://www.nvidia.com/Download/inde...aspx?lang=en-us We'll see if we can't get this figured out for you; but it might wind up requiring a code change on our end.
There is a log file in your bin folder. I always find it helpful when troubleshooting this kind of thing. Look for FATAL or ERROR lines near the bottom.
Well, I can tell you what I was told after working with tech support for 10 - 12 days on just this issue. "It's not on our end, the 'c000000d' Exception Code means it has something to do with C++ and you need to talk to microsoft to fix it." After uninstalling almost everything on my computer 2 - 3 times, running CCleaner and Driver Fusion more times than I can count and tweaking every setting I could think of there was still no clue as to what was causing the issue in the multitudes of dxdiag and msinfos I sent. I reformated and started fresh, now the game launches fine. So some setting, somewhere down the line is causing vanguard to act all wonky. Absolutely no clue what it is though. Also, if this is the crash that I was getting, it doesn't collect a 'crash log', the log just runs to a certain point and then stops.
The support tech probably knows something I don't; I'm a recent addition to the Vanguard team. However, when windows pops up those error codes they can usually be found in the DirectX tool info display (or just google it): http://nologs.com/ntstatus.html. Buffer overflow exception is a universal exception type always assigned to BEX. My best guess remains on par with your support tech; there's probably something Vanguard is sitting on that is causing the issue (driver etc.) However, I must underline that it's only a guess. The way I got the information I did was by looking in the map file for where the exception address maps to and worked backwards (part of the art of debugging when you have the code). I did find out where the crashes get uploaded to; so I'm going to look there for anything that relates to this issue when I get some free time. However, please do go ahead and ensure that you're running the latest and great WHQL approved driver from nvidia if that's your card's manufacture. Also PM me your IP address and I'll see if there's a recent crash that was reported to us for your issue. My plate is a little full at the moment; so I might be slow at getting back to you; but will try. Also, you might have better luck going through our excellent customer support. They are most helpful to both you and me when it comes to problems like this; I'm at best guessing as to your issue.
I too am having the splash screen come up and then crash to desktop with a white background. I have the most up to date digitally signed nvidia drivers. Running Windows 7 Pro 64bit...I am keeping an eye on this thread to see what the deal is, if/when a resolution is presented.
