hammer editor crashes

[Riperzz]

My hammer editor started to crash today it doesnt crash all time but like after 10 times when i compile my map (Actually the compile window crashes :/ ) it crashes and i have to close it. If i try to launch any game or steam tool i get this error "SteamStartup(0xf,0x0018e0E4) failed with error1: failed to take master pipe connection lock" and i cant even close steam so only way to fix this is to reboot computer. So does anyone know wtf is this??

 

Reboot doesnt fix this because this happened me 2 times today...

[MPQC]

Don't run the game through hammer, load the game up manually.

 

And while googling, I stumbled across this:

 

So some of Steams pipes are broken, are they? Seems like you may need to turn a Valve somewhere.

 

Yeah, I'm out of material now.

 

Edit:

 

What seems to be the Source of the problem?

 

Edit:

 

Honestly, though. Try reinstalling Source SDK or something.

 

...

[`Pepper.]

Try reinstalling?

 

Use a different compiler (not sure if source maps can do this though, I know cs 1.6 maps could)

[Riperzz]

Ok im not sure if its map problem but last thing before it crashes on map log is this

[Reading texlights from 'lights.rad']
[1 texlights parsed from 'lights.rad']

Loading e:\steam\steamapps\riperzz\sourcesdk_content\cstrike\mapsrc\mymapproject.bsp
1445 faces
3075478 square feet [442868928.00 square inches]
0 displacements
0 square feet [0.00 square inches]
1445 patches before subdivision
86021 patches after subdivision
0 direct lights
0...1...2...3...4...5...6...7...8...9...100...1...

[mapper]

Ok im not sure if its map problem but last thing before it crashes on map log is this

[Reading texlights from 'lights.rad']
[1 texlights parsed from 'lights.rad']

Loading e:\steam\steamapps\riperzz\sourcesdk_content\cstrike\mapsrc\mymapproject.bsp
1445 faces
3075478 square feet [442868928.00 square inches]
0 displacements
0 square feet [0.00 square inches]
1445 patches before subdivision
86021 patches after subdivision
0 direct lights
0...1...2...3...4...5...6...7...8...9...100...1...

 

No that's perfectly fine. You didn't show the entire compile log tho.