Pc Crash On Exit

SvenySveny Join Date: 2005-03-30 Member: 46991Members
in Tech Support
<div class="IPBDescription">help?</div>
Everytime I start up NS it works fine, but when I open up console and exit (or esc ==> quit) my pc just locks up and I have to reboot.

I am using directx 9.0c, and (i think) latest gfx/sound drivers.

Anyone else having this problem, and any idea's why/how to fix it?

Sven
Off Topic Disagree Agree Awesome

Comments

  • Lt_PatchLt_Patch Join Date: 2005-02-07 Member: 40286Members
    Is this being caused by a STOP error, and automatically rebooting the PC?

    If you've got XP, then disable the Automatic Restart, but going to *deep breath*
    Start-> Control Panel->System. Then click on the "Advanced" Tab, then on the third Settings box down (Under "Startup and Recovery"). Make sure there isn't a tick in "Automatically Restart". Click Ok. Then Ok to the System Properties menu.

    Disable that, assuming you've got XP, then try running the game, and getting the same thing happen. If the screen goes blue, make sure you write down the <b>EXACT</b> stop code you get, then post it up here, and I will help you if I can.
    Off Topic Disagree Agree Awesome
  • Frayed_EndsOf_SanityFrayed_EndsOf_Sanity Join Date: 2005-04-01 Member: 47178Members
    same thing is happening to me, on exit and map change

    stop:0x0000007F(0x00000000D,0x00000000,0x00000000)
    Off Topic Disagree Agree Awesome
  • Frayed_EndsOf_SanityFrayed_EndsOf_Sanity Join Date: 2005-04-01 Member: 47178Members
    BUMP
    Off Topic Disagree Agree Awesome
  • Lt_PatchLt_Patch Join Date: 2005-02-07 Member: 40286Members
    I need the actual stop code string. What you've given me is the physical adressing codes.
    The string will be something like...
    IRQ_NOT_LESS_OR_EQUAL.

    That's just an example, it might even be the string you're getting.
    Off Topic Disagree Agree Awesome
  • TororoTororo Join Date: 2005-04-11 Member: 48148Members
    same here, many time occured when shutdown NS.
    so, error message is
    KMODE_EXCEPTION_NOT_HANDLED
    -ntoskrnl.exe

    i extended memory on my PC last week,(1GB ->2GB)
    and change to such bluebacky PC.
    of course memtest passed completely

    thank you
    Off Topic Disagree Agree Awesome
  • Lt_PatchLt_Patch Join Date: 2005-02-07 Member: 40286Members
    Analysis: KMODE is a function of the NT Kernel (ntoskrnl.exe)
    EXEPTION NOT HANDLED, means that an error has occured that the kernel couldn't recover from. Common causes of this are erroneous programs, failing/faulty RAM, program critical data being loaded from a bad hard drive sector, or being passes into a swap file in a bad sector.

    Suggestion 1: Run "chkdsk c: /x /f /r". This will run Disk Checker in full recovery mode on the next reboot. It forces CHKDSK to dismount the drive first, then runs a sector-by-sector analysis of your drive, and attempts to recovery any data that is in a bad sector.
    Suggestion 2: Upgrade *all* drivers to their latest versions, to see if this is being caused by a driver problem. This fixes more problems that you would think.
    Suggestion 3: Try an RST cycle. an RST cycle can be performed by something like QuickTech Pro (If you work with computers, or know someone who works with them), or FreeMemTestX32 (never used it, but people have said good things about it to me) the RAM Stress Test will hammer your system RAM, and ideally will run O/S independant (ie, from a DOS-like environment) If faulty RAM is the cause, don't both reseating it to see if that makes your RST pass everything, it's like sweeping dust under the carpet. The problem will still be there, just buy a new RAM module.
    Suggestion 4: Run a full Disk Defragment pass, and get everything in your HDD in proper order. Again, this fixes more things than you would expect.

    If the problem occured when you changed to 2GB of RAM, then try just using 1GB, and see if the problem goes away.
    Off Topic Disagree Agree Awesome
Sign In or Register to comment.