Starfront collision hd data drivers#
Starfront collision hd data update#
Starfront collision hd data driver#

The problem code that can cause this crash is not that complicated so it seems likely that other software programs have or will have hit the same problem.

Starfront collision hd data drivers#

I know you get a lot of questions and I sympathise with your situation, but is this issue likely to be looked at?ДЄs my last post says, I've now updated the 'crash' program to a release build.ДЄnyway, It looks like an issue in your drivers as I can't repeat this crash on any other graphics card.

Starfront collision hd data update#

I was wondering if there is any update to this as it has been a while.

Starfront collision hd data driver#

It may worth trying this on Intel HD Graphics 42 because both use same driver package as Intel HD Graphics 4600. This further complicates the situation because we are not talking about just 1 driver release being affected but at least 2. It appears that Intel HD Graphics 4600 which is bundled with 4th generation Intel Core processors use drivers from a different line of drivers packages. I made some research since you mentioned Intel HD Graphics 4600 as well. Intel HD Graphics 25 use drivers from same line of drivers packages thus having the same driver version.Д¬heck these 2 links. This program works fine on all other computers we have with different graphics cards. It should crash on second loop of for render loop (see crash.jpg and crashstacktrace.jpg)ДЄlso I've attached my output program screenshot, where we render the red square on a blue background.ДЄs I said the actual problem is our software on clients machines, so this program is only a way I found to replicate the same issue on similar hardware at my end. I'm using Visual studio 2008 and Directx9, but I'm sure this happens on other versions of VS I've attached screenshots as requested and also my VS 2008 solution which also contains my build version of the. I take it the errors you get are not what you think I get? Our software PhotoVidShow creates Photo DVD and HD slideshows, so we need to do this constant copying from the back buffer to send to our mpg encoders which runs on the CPU.

Also at lower resolution surfaces like 720p, this problem only happens if there are 3 surfaces etc. Only creating one surface above fixes the issue, so is a possible workaround for us. It maybe we're doing something silly, but I'm also wondering if this is an issue in the HD 4000 drivers? This code runs on other computers with no problem, including with Nvidia cards as well as things like an integrated Mobile Intel 4 Series Express Chipset After about the 3rd call to GetRenderTargetData() it crashes in igdumdim32.dll We alternate the surface on each call to render.

Then under the normal render loop we copy the back buffer (same size) from the GPU to a surface. Here we create 2 surfaces in system memory (1920x1080 32 bit). This problem has been seen on windows 8 and 7 computers.ДЄfter investigation the problem seems to be a crash on a directx9 call to Idirect3DDevice9::GetRenderTargetData method.ДЄttached is a Directx9 program which demonstrates this problem as simply as possible. This seems to happen on most versions of the driver included the latest 10. We have had crash issues with users using our software on computers with Intel HD 4000 range graphics cards. Hi, I'm a developer on the PhotoVidShow software.