Hi Allan thanks for looking into this. I take it the errors you get are not what you think I get?
I've attached screenshots as requested and also my VS 2008 solution which also contains my build version of the .exe in the debug folder
Step by step:-
Run the crash.exe in the debug folder
Load crash solution into Visual Studio. I'm using Visual studio 2008 and Directx9, but I'm sure this happens on other versions of VS
Run it in the debugger
It should crash on second loop of for render loop (see crash.jpg and crashstacktrace.jpg)
my output.txt file looks like this
Render loop 1 surface(1)
Render loop 1 surface(2)
Render loop 2 surface(1)
Also I've attached my output program screenshot, where we render the red square on a blue background.
As 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. This program works fine on all other computers we have with different graphics cards.
I can reproduce it too. I have an Intel Core i3-3220 with Intel HD Graphics 2500. Driver version 188.8.131.52.3958. Motherboard information:
-Opened solution and upgraded it using Visual Studio 2013 For Windows Desktop Update 4, got some warnings though (upgrade log attached);
-After getting errors on linking, I got a stripped down version of DirectX SDK from here: https://github.com/hrydgard/minidx9;
-Extracted contents of dx9sdk\Lib\x86 in.\crash
-Did a clean build because on first attempt I got corrupted PDB related error when building;
-I built it using Debug profile for Win32 (it is the only mode that builds successfully).
When I launched it directly, it crashed shortly after start-up.
After re-launching it in Visual Studio instead, with debugging, I got a very similar crash signature as one posted by StuPVS
Hi Pal1000, thanks for trying this out. I would say you have the same issue I have.
Interesting it was on a HD 2500 but no surprise. Without knowing too much myself, I suppose it is the same or similar drivers.
Users of our software who have this problem (and got back to me with hardware information) were using either HD 4000 or HD 4600. After that I didn't bother asking because I knew the conflict was with using the Intel HD drivers. I have a Sony Vaio wth HD4000 here myself to try things out.
1 of 1 people found this helpful
Yes, @StuVPS, you are right. Intel HD Graphics 2500 and 4000 use drivers from same line of drivers packages thus having the same driver version.
Check these 2 links. Both redirect to same driver package:
I made some research since you mentioned Intel HD Graphics 4600 as well. 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. See: https://downloadcenter.intel.com/SearchResult.aspx?lang=eng&ProdId=3720
This further complicates the situation because we are not talking about just 1 driver release being affected but at least 2.
So don't hope for it to be fixed soon.
It may worth trying this on Intel HD Graphics 4200 and 4400 because both use same driver package as Intel HD Graphics 4600.
All,, Our debug team is working to reproduce the issue and we are seeing errors when running the crash.exe. We are seeing missing file errors and it looks like we do not have the correct symbols. We are seeing this on both VS 8 and 10. Is there any additional steps to reproduce the issue that we may be missing?
Hi Robert, thanks for looking at this. I'm guessing you are missing MSVCR90D.DLL, this is the debug version of the Microsoft c runtime libraries. The crash.exe I uploaded was the debug version and I forgot it needed this (sorry). If you have VS 2008 installed then you would have this installed and it will work.
To save you time, I've attached the release version of the crash.exe which has the c runtime libraries built in. So this should work fine. It also needs directx 9 (d3d9.dll) but this will be included with windows 7/8 anyway.
Saying all that, running the crash.exe will probably only get you so far... I suspect to get to the bottom of this you will need to build your own version of this program, like what PAL1000 did. This is why I only provided the source code on my initial post and later provided my VS2008 solution.
If you need any more info or having problems, then let us know
crashrelease.zip 86.9 K