Error in Hammer-memory could not be read

I am doing this tutorial map and they are going over how to do a door and make it slide. I made it an entity and then made it a lip of 4 then I go to move direction of door. I turn the knob to tell it the direction I want it to slide then when I hit apply it gives me this error:

The Instruction at 0x0ec7915b referenced memory at 0x0ec7915b. Memory could not be read. Click OK to close.


Pig Popper: I saw on another forums where you had a similar error in hammer. What did you do to fix it?

Not much you can do, when you load the map in hammer and get this error right away hammer.exe will crash. In other words you can't fix the map problem if you can't load the map.

This folder is your friend C:\HammerAutosave\

Or

could be the johnson rod

{EE}chEmicalBurn wrote:

lol at picture

Go on tools to change auto save settings. (Will not be a big loss if happens again)

as i said via steam dear - i got your map file and no errors here. all fine.
so...
validate hl2dm
validate sdk
validate hl2
start a new map (fresh = clean) and do it again
this time round - turn the world brush into func_door and hit Apply without modifying anything.
then double click on the entity (door) again. this will open properties. now do your thing.
see how that goes.
if this didn't work. reinstall game and sdk from scratch.

most importantly - don't falter on Valve's BS. you know better.

val

Eh just thinking of starting a new farking map of my own. Im getting a bit bored with the tutorial and I dont know if I want to rebuild it all over again.

Hmm I dont have hl2 installed, could that be part of the issue?

I did verify the SDK and DM files as well as defraged them.

Paradox wrote:I did verify the SDK and DM files as well as defraged them.

and did it work?

Havent tried since I did the DM files because I did them just before I went to sleep. I will try tonight if I have time.

I also updated my vid card drivers but that didnt work either.

Paradox wrote:I am doing this tutorial map and they are going over how to do a door and make it slide. I made it an entity and then made it a lip of 4 then I go to move direction of door. I turn the knob to tell it the direction I want it to slide then when I hit apply it gives me this error:

The Instruction at 0x0ec7915b referenced memory at 0x0ec7915b. Memory could not be read. Click OK to close.


Pig Popper: I saw on another forums where you had a similar error in hammer. What did you do to fix it?

link me the forum thread mate, might jog my memory.
But of the top of my head i think it may of been complex brushwork crashing hammer, I used to vertex the hell out of stuff back in the day, and didn't know func_detail was my friend. Dunno if this will help you though.

more and more i think this is not GPU or at all driver related. this looks like (as boshed put it) "hammer being hammer".
i don't think this is bad brushwork. i've seen the map and opened it locally. other than a few overlapping brushes i didn't see or had any problems and was able to tie to ent just fine.
The problem may becoming from one of the following :

Windows - anything modified or recently may have been in your windows explorer? is your Windows theme modified? any missing / problematic windows updates? can also be some application installed on your machine that can rearrange paths or file assignment. Are all window components including Net Framework 1, 3, or even Java properly installed on your machine?

or Steam - do you have Steam installed on D drive? or anything of Steam installed on a drive other than C:\ ?
Go here and run ALL THE TESTS in the Specific tests section. note that running these tests at different times might reveal a problem that emerges after a while of the machine working, etc.

corrupted or unreachable file - Hammer will be having problems with this.
if so, look at your Hammer options to make sure you got all your paths pointing to the right direction.

CPU - any weirdness in the PC's operation at all? slow rebooting processes? hanging or acting funny on Windows Explorer tasks? freezing on a big app launch while other apps are opened? taking a while to "recover" from playing a heavy game or even DM?

tbh i've had some odd experiances in hammer like maps that just needed to be renamed or else they crash ALL the time....
I.E. working fine as beta_mapname_001, beta_mapname_002, beta_mapname_003 but beta_mapname_004 just ain't having it

lol, i remeber when hammer would crash just if you looked away for half a second

[22g]Pig Popper wrote:lol, i remeber when hammer would crash just if you looked away for half a second

"would"? I still preemptively save before I open the texture dialog, the model viewer or the displacement editor

i just Ctr+S all the time

Could very easily be a ram or driver issue

ctrl+s FTW

I had crashes happening more than once in more than one map (didn't we all ). On most of them I solved the problem somehow.

But I remember one case (though this happened more times) in which I found I would have the crash everytime I did a certain action. I even saved the map before taking that action and it was THAT action. All I did in that case was deleting the object causing the crash, save the map, and redo the object from scratch. It worked. Never crashed anymore (in that map (or in that object :p)).

{EE}chEmicalBurn wrote:

You gotta love when that happens