It doesn't matter which directx 10 sample of the 2010 Directx SDK I try to run in debugging mode on visual studio 2013 or 2010 or 2012, I always get an unhandled exception on the CreateWindow() function
I didn't get this exception before and I don't know how it started
anyone with this problem too?
running the RaycastTerrain sample in the directx 10 samples
and this is the line that is the same no matter which sample I run
You are passing a pointer somewhere that is 0 and shouldnt be zero. This 0xC0000005: Access violation writing location 0x00000000 exception always means you are trying to write to something through a pointer that has value 0.
I expect either strWindowTitle, hMenu or hInstance to be 0.
but I haven't modified those samples, and as I said no matter which random sample I select, It allways gets that exception
You are passing a pointer somewhere that is 0 and shouldnt be zero. This 0xC0000005: Access violation writing location 0x00000000 exception always means you are trying to write to something through a pointer that has value 0.
I expect either strWindowTitle, hMenu or hInstance to be 0.
Unhandled exception at 0x73374D66 in RaycastTerrain.exe: 0xC000041D: An unhandled exception was encountered during a user callback.
Although the last error occurs during the execution of the CreateWindow function, that may just be the culmination of the previous errors. I.e., something else may be getting trashed before that line.
I would start by looking at the exceptions before that line.
E.g., googling indicates DestructionView.dll is a part of NVIDIA PhysX. That library looks suspicious to be part of an SDK example. Have you been working with that library before? Driver libraries do get loaded, but I would look at those errors before worrying about a CreateWindow function.
I don't know what IDE you're working in (Visual Studio?), but (just a guess) it appears that you may be loading a foreign (foreign to the example) library for some reason. When you start the app, your output window (or debug window) should be displaying lots of information about what libraries are being loaded. Take a look through that info for dlls, etc., that don't come from Windows or the SDK directories. EDIT: don't worry about "Cannot find or open the PDB file" - that's just an indication that debug builds for those libraries aren't available.
FYI - as mentioned, it appears that destructionview.dll is an NVIDIA Physx Lab file. You didn't mention whether you'd ever played around with Physx.
If you can verify for yourself that you don't need that dll running, you may want to take a look at some RegSrvr32 info. Just for fun, you may want to scan the files with your antivirus program - just in case.
