Very Annoying Ns Crash
Kamikazi
Join Date: 2003-01-07 Member: 11975Members
Join Date: 2003-01-07 Member: 11975Members
in Tech Support
<div class="IPBDescription">MSV C++ Runtime Error</div> Right, this is getting tedious now. I had a problem with getting C++ Runtime Errors at completely random intervals throughout the game. I'd start up NS, join a server, any server at all or even a LAN game, and at a random point it closes and says 'Microsoft Visual C++ Runtime Error'.
Now so far I have tried the following :
- Re-Installing NS
- Re-Installing HL, NS and Re-Patching
- Re-Installing My Runtime Files
- Changing The Compatability Modes
- Running It On Different Accounts
- Running It In Safe Mode
<b>AND</b>
- Completely Formatting My Hard Drive And Doing A Complete Re-Install
And this is the interesting part - <b> I STILL GET THE SAME BLOODY ERROR MESSAGE</b> <!--emo&:angry:--><img src='http://www.unknownworlds.com/forums/html/emoticons/mad.gif' border='0' style='vertical-align:middle' alt='mad.gif'><!--endemo-->
I have done everything i can think of to get it working short of buying another computer to run it on (let's not go too far like) However, i would appreciate <b>ANY</b> suggestions you may have regarding my situation. The other thing i can think of would be to download NS again completely hoping it is a file that got corrupted during download.
Anyway, as i said - Would Appreciate ANY help at all <!--emo&:D--><img src='http://www.unknownworlds.com/forums/html/emoticons/biggrin.gif' border='0' style='vertical-align:middle' alt='biggrin.gif'><!--endemo-->
Now so far I have tried the following :
- Re-Installing NS
- Re-Installing HL, NS and Re-Patching
- Re-Installing My Runtime Files
- Changing The Compatability Modes
- Running It On Different Accounts
- Running It In Safe Mode
<b>AND</b>
- Completely Formatting My Hard Drive And Doing A Complete Re-Install
And this is the interesting part - <b> I STILL GET THE SAME BLOODY ERROR MESSAGE</b> <!--emo&:angry:--><img src='http://www.unknownworlds.com/forums/html/emoticons/mad.gif' border='0' style='vertical-align:middle' alt='mad.gif'><!--endemo-->
I have done everything i can think of to get it working short of buying another computer to run it on (let's not go too far like) However, i would appreciate <b>ANY</b> suggestions you may have regarding my situation. The other thing i can think of would be to download NS again completely hoping it is a file that got corrupted during download.
Anyway, as i said - Would Appreciate ANY help at all <!--emo&:D--><img src='http://www.unknownworlds.com/forums/html/emoticons/biggrin.gif' border='0' style='vertical-align:middle' alt='biggrin.gif'><!--endemo-->
Comments
I REALLY WANT TO PLAY NS FOR LONGER THAN 5 MINUTES !!!!!!!! - Please Help In Anyway You Can People.
I would REALLY like help getting my NS working.
Thanx
From your layout of screenshots, I'm assuming your running in WinXP. I've came across very few repeatable errors where a program can't write to the memory. 1 have had seen was attempting to playback a specifi windows media video on the Opera web browser. This lead me to believe that the error was video card related.
Check your video drivers. What card are you running and what driver version are you using?
Also, check your device manager for any devices with an ! in a triangle or ? in a triangle. You probably know it, but they're the wonderful devices that have conflicts, are shut off, or have driver issues.
Odds are, due to the fact that this is a recreateable scenario on your computer (after 5 minutes of gameplay), something is happening hardware wise that isn't cool and probably isn't Half-Life or Natural Selection doing it.
My brother had issues with a network card that had IRQ conflicts on his system, and he could play online for any length of time and it would randomly blue screen winXP. Moved the NIC to a new slot, got a new IRQ assigned, no crash since. But it was only in Half-Life where the error presented itself.
Edit: Also, did you install the Direct X software dev kit for Visual C++? If you did, sometimes the difference between release and debug mode can screw up directx games/programs.
I suggest against deleting msvcrt.dll. It's one of those precious system files. Replacing it won't stop the errors unless it is truly corrupted (unlikely).
do you have any microsoft visual C++ products installed? visual studio?
secondly have you tried updating the runtime libarys by googling them?
2 : I run the 'un-signed' 41.09 Drivers On An nVidia GPU
3 : No Conflicts
4 : Dont have a clue what you mean by MS Direct X Dev Kit For C++ (As far as I know, I have nothing to do with C++ installed on my PC) I have installed DX 9 tho didn't help. T'was just like the DX 8 and 8.1 drivers.
5: I tried replacing it. I've also Moved the file to an encrypted folder so windows cant access it. Didn't do a thing <!--emo&???--><img src='http://www.unknownworlds.com/forums/html/emoticons/confused.gif' border='0' style='vertical-align:middle' alt='confused.gif'><!--endemo-->
--------------------
Yes I have googled the C++ Runtime files and downloaded and installed new ones OVER the old ones. Did't do anything as far as can see <!--emo&:angry:--><img src='http://www.unknownworlds.com/forums/html/emoticons/mad.gif' border='0' style='vertical-align:middle' alt='mad.gif'><!--endemo-->
--------------------
There is one thing I would like to add regardless of whos fault this is : WHY CAN'T YOU JUST WORK ?
You see the thing is, the system never done this when I first got it and it worked fine. Just recently. Could it have ANYTHING at all to do with the extra 64MB RAM I added to my system ? I know it was compatible with my system/motherboard etc - Possibly Faulty ?
Thanx For Your Advice Tho - Any Info On The RAM Thing ?
Stick with DX 8.1 for the time, just for testing purposes. If drivers are good, and all other software checks out, which it looks like it does, I'll put a lot of money on the ram bugging you out.
The error where it can't read the memory address xxxxxxxx in your screenshot.... that could very likely be the RAM fuXoring up in certain spots and when halflife reaches the point where it needs the extra ram, it hits your new chip and *blam* error. Only way to really test is to remove it and play.
1. Removing the RAM didn't help, though it was a good idea. NS just lags more.
2. I still get the C++ Error though it was more like 8 minutes rather than 5 this time. No Memory Error.
The RAM error really doesn't bother me as it only happend like once every 7 hours or so. Something like that, but what does bother me is this damned C++ Error. Does anyone have any more ideas as to how to end this Runtime fiasco that Microsoft has deliberately created within my Half-Life games ? Would appreciate ANY help at all.
Thanx
First Impression:
Swap out ALL the RAM in the machine with known-good from another system. See if it helps. Cannot READ errors usually indicate hardware failure at some level. Cannot WRITE errors normally manifest as general protection faults (Blue screens of death, colloquially) and are considerably more common.
A VC++ Runtime Library is, for almost all intents and purposes, the same as a DLL. Update to the latest officially-released DirectX drivers. If it's just Whistler having a problem, that could be it.
Also, what brand/speed/type of RAM is in the machine? Have you tried underclocking it? Did it help at all?
I have the 2 RAM chips in, The original is a Samung Make and the one that i had lying around is a Hyundai make. Why does that matter ?
Does anyone know the executable commands that can be used with ns eg :
C:\SIERRA\Half-Life\hl.exe -noipx etc ? I figure there may be something i can add to my exe command line to stop it from causing errors. A list of these commands would be nice.
Anyway, Thanx - Keep Thinking Guys. You all have good ideas, just none of them have worked yet. Keep 'em commin'
The closest thing to being C++ related on my pc is the VB EXE that comes with MS Word. Don't think that'd do anything.
I have the 2 RAM chips in, The original is a Samung Make and the one that i had lying around is a Hyundai make. Why does that matter ?
Does anyone know the executable commands that can be used with ns eg :
C:\SIERRA\Half-Life\hl.exe -noipx etc ? I figure there may be something i can add to my exe command line to stop it from causing errors. A list of these commands would be nice.
Anyway, Thanx - Keep Thinking Guys. You all have good ideas, just none of them have worked yet. Keep 'em commin' <!--emo&:p--><img src='http://www.unknownworlds.com/forums/html/emoticons/tounge.gif' border='0' style='vertical-align:middle' alt='tounge.gif'><!--endemo-->
I'd suggest talking to whoever you bought the system/RAM from, as most pre-built machines come with at least a year warranty. I'd also get a stress-tester and run it overnight, to make sure. Otherwise, it could just be a Whistler problem. Odd though that no one else has that problem, and you're running 'stock' Whistler, and the only real difference between the machines is the hardware involved.
If you have the expertise and nerves neccessary, you could try flashing your motherboard's BIOS, as it *could* be a problem with that. What brand of mobo/BIOS type is in the box?
If underclocking your RAM breaks anything, that only reinforces the 'bad RAM' hypothesis. Underclocking never BREAKS a machine that works properly at top-rated spec. Just makes it run a little slower. If underclocking stops the machine from booting at all/throws bunches of errors, either you underclocked it incorrectly, or you've got a bad stick of RAM. Try clocking it one rating-spec down (PC-133 becomes PC-100, for non-DDR machines, as an example). If it still breaks, you've got bigger problems than not being able to play NS. You more likely got a lemon machine.
1. A bug in NS. In which case, we would need Flayra to take a look at it to try and figure out why there are memory errors.
2. A fault with your hardware. The error message details what seems to be a Memory error. These can be because of many things (bad RAM is one that springs to mind).
Please, post ALL of your computer details, settings and NS video/audio modes, it will make it a lot easier for people to try to help you. Do a thorough check on your system. I shall leave this post here, just in case it happens to be number 1. Good luck finding the problem (and the solution <!--emo&:)--><img src='http://www.unknownworlds.com/forums/html/emoticons/smile.gif' border='0' style='vertical-align:middle' alt='smile.gif'><!--endemo--> ).