Could not reset the Direct3D device. This sample will now exit

Hi Guys, I need some help with this problem.

error20141019.txt

2014/10/19 16:58:22 Could not reset the Direct3D device.

This sample will now exit.

2014/10/19 17:25:52 Oct 16 2014 23:23:35 1 rCnt=1

Neuz.exe caused an EXCEPTION_ACCESS_VIOLATION in module Neuz.exe at 0023:004491AA

- Registers

EAX=00000000 EBX=7EFDE000 ECX=00000000 EDX=0018EB18 ESI=00000000
EDI=758B1225 EBP=0018EB3C ESP=0018EB38 EIP=004491AA FLG=00210246
CS=0023 DS=002B SS=002B ES=002B FS=0053 GS=002B

0023:004491AA Neuz.exe
0023:00728D5D Neuz.exe
0023:007850D8 Neuz.exe
0023:00783805 Neuz.exe
0023:004DF407 Neuz.exe
0023:0050CD6C Neuz.exe
0023:0050CB4E Neuz.exe
0023:0046FC20 Neuz.exe
0023:0048FA2F Neuz.exe
0023:0048F845 Neuz.exe
0023:0047778C Neuz.exe
0023:0090E1AC Neuz.exe
0023:758B3677 kernel32.dll
0023:77D09D72 ntdll.dll
0023:77D09D45 ntdll.dll

I googled for several links and mostly said its a DirectX or Virdeo Card problem (maybe the drivers are out of date).

Others games has the same problem, and all indicates a direcx or vga problem.

But, I'm not totally convinced. Not sure if its really a VGA problem or server/client problem. What do you think?

Thans for any help ^^

Still same problem :(

any idea?

this doesnt occur with all players.

I think this Problem involve the Source. Try to Look in your "_DirectX" folder.
Because your Problem falls in Direct3D Device. So im quite sure its in that folder.

Humm I will check with many sources I have and compare codes. Thank You!

Or it could just be your computer with the d3dapplication. If you're moving the window and it pops up with said error, you can check other sources or you can check the OnSizeChange and reset3denvironment codes.

It has to do with this part
HRESULT CD3DApplication::HandlePossibleSizeChange()

Cause if you noticed when you are in window mode and you move your screen sometime it will occur that you will have small black borders inside the client.

// Name: HandlePossibleSizeChange()
// Desc: Reset the device if the client area size has changed.

For your information its not 100% player sided. Its an factor of both.

What you can do is try to update the directx to the latest version. If you dont have the skills to do so. Then good luck.( I also dont have the skill yet :D)

The issue you're describing occurs when the direct3d device must be reset. Common causes for this would be if the PC goes into sleep mode or is locked. It happens because the reference count of the direct3d device object is not zero. To remedy this, you'll need to properly release all resources that are allocated with the D3DPOOL_DEFAULT flag. I think there are only a few that aren't properly released, if you can find them, let me know.

Oh also the issue is obviously in the flyff code. Any other games that have this issue are also probably designed as poorly as flyff as that's the only thing that would cause an issue like this.