Sign in to follow this  

OpenGL All OpenGL-based programs crash on my computer

Recommended Posts

frankoguy    122
I have a very big problem: I just purchased a book called Beginning OpenGL Game Programming, by Dave Astle and Kevin Hawkins. And all the programs that come with the book crash with the same type of error message box every time on my laptop computer: "The instruction at 0x69666f60 referenced memory at 0x0019194c. The memory could not be written." This exact same kind of error also happens with every OpenGL program I write. The crash always occurs either on the first glClear(myflags) call, or on the first SwapBuffers(hdc) (if I skip the call to glClear() which it crashes on); I'm using wgl to write my opengl apps. All glut-based and wiggle-based OpenGL code crashes on my laptop pc: every single program that came with this book and all my own code as well. I DON'T GET IT!! I'm guessing it's some kind of graphics driver problem?? I just don't know how to resolve (and where to look) in order to fix this. My laptop computer uses onboard video hardware from nvidia 6800 equivalent. With every single Direct3D application I've written, these kinds of runtime crashes don't occur. I've been coding a very long time: so I'm very confident it's not due to a logic mistake. But nevertheless, this is a behavior I haven't seen before. My windows platform sdk allows for opengl and wgl calls to be made. Compiles and links without problems. Could it be that Microsoft is being evil, and is forcing the rest of us to use Direct3D? haha...maybe? Or is it nVidia? or both? Anyways, I'd deeply appreciate any help I can get on this. Thanks

Share this post

Link to post
Share on other sites
Oranda    122
That definitely sounds like either a problem with the drivers themselves or else with whatever code utility you are using to setup OpenGL.

I would try getting an OpenGL demo from someplace else and try running that. If it works, you can rule out the drivers, in which case it may be time to get a new version of GLUT :D.

Try using the Jogl demos. They run with Java Webstart so you don't even need to unpack anything. Just click the link and wait to see if they run or not. You can find them here:

Share this post

Link to post
Share on other sites
frankoguy    122
Wow, I solved my own problem.

Now I feel kind of stupid for asking the question.

I just turned off driver instrumentation, and that solved the issue. Now all my opengl programs run correctly, including my Direct3D apps.

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  

  • Similar Content

    • By povilaslt2
      Hello. I'm Programmer who is in search of 2D game project who preferably uses OpenGL and C++. You can see my projects in GitHub. Project genre doesn't matter (except MMO's :D).
    • By ZeldaFan555
      Hello, My name is Matt. I am a programmer. I mostly use Java, but can use C++ and various other languages. I'm looking for someone to partner up with for random projects, preferably using OpenGL, though I'd be open to just about anything. If you're interested you can contact me on Skype or on here, thank you!
      Skype: Mangodoor408
    • By tyhender
      Hello, my name is Mark. I'm hobby programmer. 
      So recently,I thought that it's good idea to find people to create a full 3D engine. I'm looking for people experienced in scripting 3D shaders and implementing physics into engine(game)(we are going to use the React physics engine). 
      And,ye,no money =D I'm just looking for hobbyists that will be proud of their work. If engine(or game) will have financial succes,well,then maybe =D
      Sorry for late replies.
      I mostly give more information when people PM me,but this post is REALLY short,even for me =D
      So here's few more points:
      Engine will use openGL and SDL for graphics. It will use React3D physics library for physics simulation. Engine(most probably,atleast for the first part) won't have graphical fron-end,it will be a framework . I think final engine should be enough to set up an FPS in a couple of minutes. A bit about my self:
      I've been programming for 7 years total. I learned very slowly it as "secondary interesting thing" for like 3 years, but then began to script more seriously.  My primary language is C++,which we are going to use for the engine. Yes,I did 3D graphics with physics simulation before. No, my portfolio isn't very impressive. I'm working on that No,I wasn't employed officially. If anybody need to know more PM me. 
    • By Zaphyk
      I am developing my engine using the OpenGL 3.3 compatibility profile. It runs as expected on my NVIDIA card and on my Intel Card however when I tried it on an AMD setup it ran 3 times worse than on the other setups. Could this be a AMD driver thing or is this probably a problem with my OGL code? Could a different code standard create such bad performance?
    • By Kjell Andersson
      I'm trying to get some legacy OpenGL code to run with a shader pipeline,
      The legacy code uses glVertexPointer(), glColorPointer(), glNormalPointer() and glTexCoordPointer() to supply the vertex information.
      I know that it should be using setVertexAttribPointer() etc to clearly define the layout but that is not an option right now since the legacy code can't be modified to that extent.
      I've got a version 330 vertex shader to somewhat work:
      #version 330 uniform mat4 osg_ModelViewProjectionMatrix; uniform mat4 osg_ModelViewMatrix; layout(location = 0) in vec4 Vertex; layout(location = 2) in vec4 Normal; // Velocity layout(location = 3) in vec3 TexCoord; // TODO: is this the right layout location? out VertexData { vec4 color; vec3 velocity; float size; } VertexOut; void main(void) { vec4 p0 = Vertex; vec4 p1 = Vertex + vec4(Normal.x, Normal.y, Normal.z, 0.0f); vec3 velocity = (osg_ModelViewProjectionMatrix * p1 - osg_ModelViewProjectionMatrix * p0).xyz; VertexOut.velocity = velocity; VertexOut.size = TexCoord.y; gl_Position = osg_ModelViewMatrix * Vertex; } What works is the Vertex and Normal information that the legacy C++ OpenGL code seem to provide in layout location 0 and 2. This is fine.
      What I'm not getting to work is the TexCoord information that is supplied by a glTexCoordPointer() call in C++.
      What layout location is the old standard pipeline using for glTexCoordPointer()? Or is this undefined?
      Side note: I'm trying to get an OpenSceneGraph 3.4.0 particle system to use custom vertex, geometry and fragment shaders for rendering the particles.
  • Popular Now