Messerschmitt Posted September 19, 2009 Share Posted September 19, 2009 This only happens when I have TF2 running and I want to start BF2. It does not always happen but most likely I will get this BSOD.Mini091509_02.rar Link to comment Share on other sites More sharing options...
The Metal God Posted September 20, 2009 Share Posted September 20, 2009 This only happens when I have TF2 running and I want to start BF2.Then you obviously should stop game nr1 before starting game nr2...I cant see why you want to have 2 games running on your pc at the same time Link to comment Share on other sites More sharing options...
cluberti Posted September 20, 2009 Share Posted September 20, 2009 Obviously without symbols I can't say what, but you're definitely failing in the ATI video driver here:1: kd> .trap 0xffffffffaa6f2340ErrCode = 00000000eax=aa6f23c8 ebx=00000000 ecx=00000000 edx=00a7c0c0 esi=e30b5080 edi=e1ecd018eip=bf039614 esp=aa6f23b4 ebp=aa6f250c iopl=0 vif nv up ei pl zr na pe nccs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00090246ati2dvag+0x27614:bf039614 ff7314 push dword ptr [ebx+14h] ds:0023:00000014=????????1: kd> kb *** Stack trace for last set context - .thread/.cxr resets itChildEBP RetAddr Args to Child WARNING: Stack unwind information not available. Following frames may be wrong.aa6f250c bf05aadf e3782a20 e1b755a4 e1b75480 ati2dvag+0x27614aa6f2554 bf8c6bad e3782a20 e1b755a4 e1b75480 ati2dvag+0x48adfaa6f25ac bf8c716f e3782a20 e1b755a4 e1b75480 win32k+0xc6badaa6f2870 8054162c 92011338 000000e0 00000000 win32k+0xc716faa6f2884 7c90e514 badb0d00 0013f64c 00000000 nt+0x6a62caa6f2888 badb0d00 0013f64c 00000000 aa6f2ab0 0x7c90e514aa6f288c 0013f64c 00000000 aa6f2ab0 00000207 0xbadb0d00aa6f2890 00000000 aa6f2ab0 00000207 e23c7000 0x13f64cSince it's a minidump I can't look at any of the pointers on the stack or unassemble, but it's obvious the ATI driver expected EBX to be something other than 0x0 because 0x0 + 14 hex gives 0x00000014, which falls below 0x00001000, and any memory from 0x0 to 0x00001000 (the first 64K of process space) is all marked PAGE_NO_ACCESS and the A/V occurs and your process crashes.I'd suggest configuring for a complete dump and providing the data to ATI support, as it's a driver issue. Link to comment Share on other sites More sharing options...
Messerschmitt Posted September 22, 2009 Author Share Posted September 22, 2009 Sorry for forgetting to give the following:0X0000008E (0xC0000005, [...])ati2dvag.dllHow can I configure for a complete dump? Link to comment Share on other sites More sharing options...
CoffeeFiend Posted September 22, 2009 Share Posted September 22, 2009 How can I configure for a complete dump?By using the forum search function, or looking at the first sticky in this section. Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now