|
Post by meatpopsicle on Aug 9, 2010 6:17:21 GMT
So whenever i complete the loading process to play my map in game with Gmod, i walk around for about 2-3 seconds then it freezes, the sound loops and i get this message: The instruction at "0x14dcdad" referenced memory at "0x0d21b018". The memory could not be "read". I've tested this to see if it happens with any other map and it does not. Only with the one i have created does it happen. I have gone over many of the problems i could think of that caused this including pressing Alt+p to check for problems and the two were "there is no 'player_start'" (which i had a player_deathmatch instead) and some sort of error with the window breaking texture thing (still haven't gotten the hang of that) I fixed both which didn't fix the main problem (or else i wouldn't be typing this). I saw a guy with a slightly similar error message but he had to reinstall the HL2 stuff. Hopeful i don't have too
|
|
|
Post by Zeph on Aug 9, 2010 12:45:00 GMT
It's most likely dodgy RAM mate. Download a ram checker and check your RAM.
Is that error a blue screen or game error?
|
|
|
Post by meatpopsicle on Aug 9, 2010 17:13:21 GMT
Its a game error. When i play the map in HL2dm i just get a "sorry but windows encountered a problem and had to close, we're sorry for the inconvenience" kind of message. Its weird though i was able to run it just fine a few changes back... EDIT: ran the RAM check and it encountered no errors.
|
|
|
Post by Zeph on Aug 9, 2010 19:16:51 GMT
Then it could be your HDD, perhaps a file is corrupt. Verify the game cache of the Game, Source SDK, and Source SDK Base: In Steam: Right click the Game/Tool Click Properties Go to the "Local Files" tab Click "Verify Integrity of Game Cache"
Usually a RAM error would be a BSOP, Blue Screen, but since you didn't get one it probably isn't your RAM. Also things that can't be 'read' is HDD or even your Graphics Card Ram. Basically i'm inclined towards hardware fault.
Give the map to someone else and see if it works for them, or if it's only on your computer.
|
|
|
Post by meatpopsicle on Aug 9, 2010 20:19:22 GMT
Thanks for helping out, i ran another map that i made and it was flawless in game. In a few days i will test the problem map on my other (better) computer and see if it works then. And the caches are not corrupt.
|
|
|
Post by meatpopsicle on Aug 11, 2010 21:00:38 GMT
Alright i tried it on the other computer and I seemed to be able to last longer (for about 7 seconds) until it does finally crash...
|
|
|
Post by Zeph on Aug 11, 2010 22:14:07 GMT
Ok it must be something in the map then.
Send me the VMF file and i'll see if i can spot something. Very hard to do anything about it otherwise.
|
|
|
Post by meatpopsicle on Aug 12, 2010 5:03:16 GMT
I am idiot and only have the .bsp file. is there a way to make that a .vmf?
|
|
|
Post by Angush :] on Aug 12, 2010 6:25:05 GMT
If you made the map, open it in Hammer and save it as a VMF on your desktop or something, then upload it somewhere.
If you didn't make the map, just provide a link to the BSP.
|
|
|
Post by meatpopsicle on Aug 12, 2010 16:50:53 GMT
well i made the map but i sent the .bsp and not the .vmf to the computer i am using now. It is my first map and very incomplete so please do not make fun of it xP Attachments:
|
|
|
Post by Zeph on Aug 12, 2010 19:12:06 GMT
I don't have GMod (this should be in GMod forum!) and only just saw that your map is for it. I can't test it, sorry. I could probably still look at the VMF though if you could get it.
|
|
|
Post by meatpopsicle on Aug 12, 2010 23:27:31 GMT
I realize its called gmodhouse but i am able to use it in deathmatch (it still crashes weather its in gmod or deathmatch)
|
|
|
Post by therealguymins on Aug 24, 2010 6:32:21 GMT
It's most likely dodgy RAM mate. Download a ram checker and check your RAM. Is that error a blue screen or game error? Random and pointless** Do you know how you can get a screenshot of the bsod?
|
|
|
Post by Zeph on Aug 24, 2010 10:00:20 GMT
Yes, your comment was. Quite Troll-like to be honest.
Its not a BSod, its a game error, as was not stated clearly and therefore needed to be asked. Usually "memory cant be read" suggests that the memory cannot be read (duh), due to a fault. Memory = ram, gfx ram or hdd. It was my initial thought, and a quite acceptable one too. So no, not pointless; the first step to helping someone. You cant get a screenshot but you can look at the dump records or just write down what the error was like meatpopsicle did.
One thing that can be tried is to copy the map and paste into a new file. Sometimes this fixes not seen errors.
I'll try the map in deathmatch.
|
|