• Crash to desktop with no error
    6 replies, posted
Been trying to join servers and every time I get in, the game crashes to desktop with no error. I hate to make a thread here because most of the time when I google problems and find threads in this section, they are never resolved. Here is a link to the crash mdmp file: [URL]https://mega.co.nz/#!oRpUmLbA!hz07HjqiS3M2oSSwnqPGP0AfNRpYZzKR-Sw0zU_zSBo[/URL]
Have you verified game cache?
[QUOTE=Catheter Cat;44397098]Have you verified game cache?[/QUOTE] Yes. I also tried to re-install the game.
What are your computer specifications? And are your drivers up to date?
Thanks for the replies. I have a Toshiba laptop from early 2009. It is a craptop by today's standards but always ran gmod fine on medium settings. Windows Vista 32bit SP2 AMD Turion X2 @ 2 GHz ATI Radeon mobile graphics 4.00 GB RAM 250 GB HDD I reformatted it when I took it to university in summer 2012. I've kept it primarily junk free since. It isn't good by any standard, but it [I]should[/I] be able to run at least gmod. As I stated I tried to verify cache as well as re-install the game. Occasionally I'll get into a server and my game will CTD with an engine error about memory allocation. I googled it and apparently it is a problem with how Vista allocated memory for applications. I have a desktop at home (As I said I'm off at university) that has Windows 7, and I don't plan on upgrading this laptop. I honestly should have replaced it when I went to university but didn't have the money at the time. (Still don't now.)
Uh yeah Vista and its memory allocation, I remember the problems I had. You don't necessarily have to replace the laptop, you could just upgrade to Windows 7 or 8
[QUOTE=djjkxbox360;44407717]Uh yeah Vista and its memory allocation, I remember the problems I had. You don't necessarily have to replace the laptop, you could just upgrade to Windows 7 or 8[/QUOTE] I have the disks and a key, but this laptop really isn't worth updating. It was on the cusp of becoming outdated when I bought it in early '09.
Sorry, you need to Log In to post a reply to this thread.