Get D3DERR_INVALIDCALL on directX new device

Can anyone please help me with this problem. I look at simmilar questions, but the code is too different from mine to use the solution I found from other got the same error. It's only happens on some computers. Directx work with other programs on the computers my program is not working on.

This is the error message:
-2005530516 (D3DERR_INVALIDCALL)
   at Microsoft.DirectX.Direct3D.Device..ctor(Int32 adapter, DeviceType deviceType, Control renderWindow, CreateFlags behaviorFlags, PresentParameters[] presentationParameters)

Thanks for your help!
void init()
        {
            _wnd = new Form();
            _wnd.FormBorderStyle = FormBorderStyle.None;
            _wnd.Text = "RenderWindow";
            _wnd.Size = _fullScreenSize;
            _wnd.BackColor = Color.Black;
            //_wnd.Show();
            Application.DoEvents();
 
//this line is causing the error
            _device = new D3D.Device(  _screen, D3D.DeviceType.Hardware, _wnd, CreateFlags.MixedVertexProcessing | CreateFlags.FpuPreserve, getPresentParams() );
            _device.DeviceLost += new EventHandler(_device_DeviceLost);
            _rt = _device.GetRenderTarget(0);
            _frameInterval = TimeSpan.FromSeconds( 1.0 / _device.DisplayMode.RefreshRate );
                      
 
            _keyboard = new DI.Device( SystemGuid.Keyboard );
            _keyboard.SetCooperativeLevel( _wnd, CooperativeLevelFlags.Foreground | CooperativeLevelFlags.Exclusive | CooperativeLevelFlags.NoWindowsKey );
 
            QueryPerformanceFrequency( out _timerFrequency );
            QueryPerformanceCounter( out _timerBaseline );
            _timeBaseline = DateTime.Now;
        }

Open in new window

OddisWAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

PaulHewsCommented:
A couple of thoughts just thrown out there.

-Do the samples from the DirectX SDK work properly?  Look in <DirectX SDK install folder>\Samples\Managed\Direct3D
-What does the call to getPresentParams return?

0
OddisWAuthor Commented:
The sample DirectX work properly on the macines where it failed. In fact my customer have tested it on 5 machines, and it only worked on one. DxDiag work on all of them.

The getPresentParams return:
MultiSampleQuality: 0
PresentationInterval: Default
FullScreenRefreshRateInHz: 0
PresentFlag: None
AutoDepthStencilFormat: Unknown
EnableAutoDepthStencil: False
Windowed: True
DeviceWindowHandle: 0
DeviceWindow:
SwapEffect: Discard
MultiSample: None
BackBufferCount: 0
BackBufferFormat: Unknown
BackBufferHeight: 0
BackBufferWidth: 0
ForceNoMultiThreadedFlag: False


0
PaulHewsCommented:
The PresentParams look okay, and everything looks pretty generic.  Try passing 0 instead of _screen.

Do the affected computers have the right version of DirectX?  Do they have up to date drivers?

0
Cloud Class® Course: Microsoft Office 2010

This course will introduce you to the interfaces and features of Microsoft Office 2010 Word, Excel, PowerPoint, Outlook, and Access. You will learn about the features that are shared between all products in the Office suite, as well as the new features that are product specific.

OddisWAuthor Commented:
Thanks for your response Paul.

The _screen was already 0 at the time new Device is called.

The other computers has the latest build of DX 9. We have double checked that it's the same versions. The program was initially wroten for about 3 years ago when DX 9 was new, but then it was not thouroughly tested.
0
PaulHewsCommented:
And are the video drivers all the same version?
0
OddisWAuthor Commented:
I ended up rewritting the entire code and used an example from microsoft to initialize the directx with the correct parameters. It seems like it was some of the graphics drivers that didn't worked with vertex processing in hardware mode.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
.NET Programming

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.