Access violation reading location 0x0000000c?

Your P/Invoke declarations are all wrong, using "int" where IntPtr is required. This code is indeed going to bomb on a 64-bit version of Windows. Get them fixed by getting the proper declarations from pinvoke.net.

1 You're 100% right, but in his case it's a 32bit DLL that's crashing. But without a correct signature, he's still going to have problems on x64. – Larry Osterman Jul 8 '10 at 23:34 Good point, that's a 32-bit exception.

– Hans Passant Jul 8 '10 at 23:37.

Looks like you're dereferencing a NULL (i.e. , a zero pointer) somewhere. While a NULL isn't formally a zero, it is in practice.(It's not an actual dereference of a zero pointer because the code is assuming there's a struct starting there and is accessing the 4th word of that struct.) Check for anywhere where you're calling the code with a null or zero parameter.

Also consider making all calls into the low-level API private and wrap them with safe versions that guard all the arguments. I can't diagnose much more than that; you don't provide quite enough info yet (well, for me to do so at least; someone more experienced may be able to help).

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.