Sign in to follow this  
Narf the Mouse

What's a "D3DERR_DRIVERINTERNALERROR: Driver internal error (-2005530585)"

Recommended Posts

Narf the Mouse    322
Quote:
Original post by Evil Steve
It's an internal driver error, which usually means your video card driver has a bug in it. Do the Debug Runtimes say anything? Do you have the latest drivers for your graphics card?

Ok, I've updated the drivers for my graphics card. It still happens.

It doesn't seem to happen in the debug version, only the release version (of DirectX). This is what DebugView output'd; hopefully, something there is helpful:


[3224]
[3224] *** HR originated: -2147024774
[3224] *** Source File: d:\iso_whid\x86fre\base\isolation\com\copyout.cpp, line 1391
[3224]
[3224]
[3224] *** HR propagated: -2147024774
[3224] *** Source File: d:\iso_whid\x86fre\base\isolation\com\identityauthority.cpp, line 278
[3224]
[3224]
[3224] *** HR originated: -2147024774
[3224] *** Source File: d:\iso_whid\x86fre\base\isolation\com\copyout.cpp, line 1391
[3224]
[3224]
[3224] *** HR propagated: -2147024774
[3224] *** Source File: d:\iso_whid\x86fre\base\isolation\com\identityauthority.cpp, line 278
[3224]
[3224]
[3224] *** HR originated: -2147024774
[3224] *** Source File: d:\iso_whid\x86fre\base\isolation\com\copyout.cpp, line 1391
[3224]
[3224]
[3224] *** HR propagated: -2147024774
[3224] *** Source File: d:\iso_whid\x86fre\base\isolation\com\identityauthority.cpp, line 278
[3224]

Share this post


Link to post
Share on other sites
Evil Steve    2017
According to Google, error -2147024774 (0x8007007a) is "The data area passed to a system call is too small." - does that ring any bells? Do you have any buffers that might be too small for the data going into them?

Can you make a minimal example program that reproduces the error?

This might be worth having a quick look over too.

Share this post


Link to post
Share on other sites
Narf the Mouse    322
Quote:
Original post by Evil Steve
According to Google, error -2147024774 (0x8007007a) is "The data area passed to a system call is too small." - does that ring any bells? Do you have any buffers that might be too small for the data going into them?

Can you make a minimal example program that reproduces the error?

This might be worth having a quick look over too.

Not ringing any bells, unfortunately. I can stick some checks on the buffers. I can also take that suggestion and put ".Present()" in a try-catch block and recreate the device as a quick fix until I find the real problem.

Share this post


Link to post
Share on other sites
Narf the Mouse    322
Ok, I've stuck the Device.Present() in try-catch-recreate code. I got the same error here, right after startup:

mapMeshes[mapX, mapZ] = new Mesh(
MainData.Display.Device,
terrain.tiles * 2,
terrain.tiles * 6,
MeshFlags.Dynamic | MeshFlags.Use32Bit | MeshFlags.SystemMemory,
VertexFormat.Position | VertexFormat.Normal | VertexFormat.Texture1
);

I also got two "Out of Memory" errors on it on subsequent startups, but that tends to happen after I have to stop the execution of the program - Memory doesn't always get garbage collected. I'll have to test after restart.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this