Messages

1

General / Re: Access Violation (idg10iumd64.dll)

« on: September 22, 2015, 10:50:47 pm »

This error was caused by Windows 10.
I'm not sure if it was because W10 force updated my Intel drivers or something stupid, but I've reverted back to 8.1 and now everything is working perfectly again.

From what I can gather, W10 updates Intel drivers to a new version which doesn't support OpenGL 2.0+, or something ridiculous like that.

2

General / Re: Access Violation (idg10iumd64.dll)

« on: September 22, 2015, 07:07:32 pm »

Ah yes, the intermittent nature of this bug made me think it was just dependant on my projects, but I tried opening osu! four or so times and it crashed in the same way (you can set osu! to use OpenGL as the renderer).

3

General / Re: Access Violation (idg10iumd64.dll)

« on: September 22, 2015, 06:35:37 pm »

No, this is a Debug build.
Again, I'd like to stress that this error is not dependant on whether I build for release, debug, static or dynamic.
As I said in my previous post, this error is now occurring on sfml projects which previously had no issues - even if my current project was somehow misconfigured, these others would not be.

I managed to update my drivers finally, to no effect.
Incidentally, the update manager now offers to download the driver software which is apparently the exact same version as mine.
https://i.gyazo.com/0e6b49bd286686746d18d0fe55a37951.png

No, the std libraries are not being statically linked.

Sorry about the quote.

4

General / Re: Access Violation (idg10iumd64.dll)

« on: September 22, 2015, 04:59:58 pm »

How did you verify they're up-to-date? Keep in mind that the Windows device manager is not reliable in that respect. You need to consult the manufacturer's homepage. Never download drivers from inofficial sources.

What's the callstack of that access violation? Does it always occur at the same place?

And, most importantly, are you absolutely sure that everything is linked correctly, with the correct compiler versions, flags and configurations? You don't mix anything between SFML and your project? I'm asking because there have been many threads here where people were allegedly sure, and after 2 pages of discussion it was a silly overlook in the tutorial so please double- and triple-check your configuration.

Ok, I installed Intel's own driver update utility, however when it tries to update my drivers, at some point during the installation my screen will go black (although I can still see my mouse?), and I have to turn my laptop off and back on.

As for configuration issues, I linked an imgur gallery showing all of my configuration, even images of the directories I'm using. Just to check, I tried running an older project of mine which uses opengl and sfml, and got the exact same issue. This issue has never occurred to me before.
Additionally, I'm usually able to run my project once with no issue. In fact, this problem is very intermittent, it will usually break, but not always. If it doesn't crash within the first second, it won't crash again.

Finally, after playing around with it, it seems that the error occurs on the 'window.display()' method.

Here is the call stack I can see when the breakpoint is hit

5

General / Re: Access Violation (idg10iumd64.dll)

« on: September 22, 2015, 05:59:30 am »

My graphics drivers are up to date, and the page you linked is not for the graphics card I have.

6

General / Access Violation (idg10iumd64.dll)

« on: September 22, 2015, 05:05:23 am »

Alright, I've spent hours trying to find the cause for this error. This will occur at some time during the main program loop - usually from 2 to 10 loops will trigger this to happen:

#include "SFML\Graphics.hpp"

int main()
{
        sf::RenderWindow window(sf::VideoMode(800, 400), "hi");

        while (window.isOpen())
        {
                sf::Event e;
                while (window.pollEvent(e))
                {
                        if (e.type == sf::Event::Closed)
                                window.close();
                }
                window.clear(sf::Color::Black);
                window.display();
        }


        return 0;
}

For context, this error has followed me through two different versions of SFML since I encountered it this morning: 2.2 and 2.3.2.
I have tried the builds from the download page and my own builds from the source, neither seem to affect this issue.
Additionally, I've tried using both 32 bit and 64 bit builds on both of the aforementioned sfml versions.
I've also tried using both static and dynamic linking (debug) both with 32 and 64 bit on both versions.
Yes, I did change my settings to adjust for the different build versions.

From what I can gather, this error might be somehow related to my graphics card (Intel(R) HD Graphics 4000).

I have a hunch this error is related to my upgrade to Windows 10. Certainly, I never had anything like this on 8.1.

Here are all my project settings etc:
https://imgur.com/a/j4670/all

If anybody can shed some light onto what is happening, your help would be greatly appreciated.
Alternatively, if you can show me some way of debugging this issue myself, that would also be welcome.