SDL_SetVideoMode randomly stops working?

Access violation reading location 0x00000000[/quote]looks like you trying to read from a null pointer.

Access violation reading location 0x00000000

looks like you trying to read from a null pointer.
[/quote]
That's what I thought too, but my program was compiling fine just the way it is. I didn't even edit the code and it just stopped working
Another thing I noticed is that if I put return false right after it will work but then throw me the same or similar error somewhere else in my code

I fixed it!
I'm kinda glad i was able to fix it by myself so that in the future i am able to debug better. I commented out large chunks of my code and compiled. Saw if it worked and then made the comments smaller, repeated this till it would give me an error
[/quote]
Great stuff. This kind of divide and conquer approach can be very useful. It can be time consuming though. It can also negatively affect your code (unless you create a copy, or use version control. I recommend the latter, but the former will work too).

In this case though, once you have some experience using your debugger you will likely find that a far more efficient way to investigate these sorts of errors.

I have a log that i load and that log should tell me if any images did not load but that log was empty, haha it only works when the program runs fine so if someone can give me a link on a tut about properly using logs
[/quote]
How often do you flush your log? The basic I/O optimisations are caching and buffering. If you aren't explicitly flushing your logs, the data might be sitting in an application buffers, OS buffers, or both. When your process crashes, the OS will flush its buffers but it knows nothing about the application buffers.

How are you logging? If you're using the C file streams, you need to insert fflush() calls. If the C++ streams, you can insert std::flush or std::endl* into the stream, or call the flush() member function of the stream object.

* [size="1"]Note that this is one reason you should not use std::endl when you don't need flushing behaviour, because it is both a newline and a flush it can negatively impact performance when you need to write a large amount of data to a file.

If you want the log to be available in the case of a sudden crash, you'll need to flush it after each logical entry. One option is to wrap your logging in a custom function, and flush as part of that. Another might be this.