problems with rebooting while playing games *Screenie*

hi, i know there is already a post on this topic about y computers restart or reboot all of sudden while playing the game! but, if i post in that topic, i know ppl won't be able to read it, so i think its necessary for me to start a new one, btw, i think mine is quite different i guess, since ppl say is over heating problems or rams or w/e this time i think its my video card.

Everytime i play guild wars, ONLY GUILD WARS! well other games i have probllems like diablo2 always getting unhandled exception only when playing window mode, but anyways when i play guild wars, my computer would all of sudden restart. it really pisses me off, i tried looking it up, and ppl said its heating problems, so i opened up my computer, and dust blew everything, now the inside is all clean, but then when i play guild wars, i notice there is even MORE restarting, like it happens every 25 seconds or around, somtimes faster or longer! it really pisses me off! does anyone know what to do? i did that thing that shows the blue screen if it helps



its something about nv4.disp.dll or something like that, im guessing thats video card, but seriously, ive restinall drivers, did the cleaning thing for old driver files many times! i use that nasty file remover or w/e NFR or soemthing like that, and this nv4 always shows up again when i remove everything and do the check again, so any nvidia pros here know how to do this??


comp specs:

-Pentium 4 SP2 3.2ghz
-1.5 gig of ram, i have 4 slots, first 2 slots have 2x 512s and the other 2 slots have 2x 256s
-geforce fx 5900

what else do i need to add?

someone help!

Coupla Qs is this a notebook comp?? I do know the fixes that have worked for people are many and varied on this problem. Google nv4.disp.dll and start trying anything that sounds like it might work. I know that I used to get that error alot on my last tower. Caused by a really bad combo of vid card and motherboard(note to self dont buy bare bones deals that look good, they arnt).

Good luck on fixing it

What driver version are you using? If its not the latest, get em.
And go to start>run and type 'dxdiag', do a direct3d test and give us the results.

This is quite a common problem and is ussually just caused cause you dont have the latest drivers. But if that doesnt fix it the dxdiag direct3d test should give us some info.

I have the same problem... anywhere, randomly, from 2-20 minutes into a game GW will reset. I just purchased a new X1900XT from Newegg.com and I started to receive these errors.. never had them before.

Sometimes using the latest drivers will cause more problems than they solve, so try going back to about the 71.89 drivers. That should be a very good combo for your card seeing as it isn't the newest of the bunch. My 6800GT used to run every game flawlessly on those drivers, and it was a generation ahead.

im currently using the newest drivers, im not at home at the moment, but when im home ill give u guys the results for the 3d thing,

my motherboard is a MSI 865PE Neo2, and my video card as said already is a geforce fx 5900, is that a bad combo or something? lol

Looks like a page file error. How much HD space do you have left? You could try setting your page file to Windows managed. Just do this.

Right click My computer and hit properties. Then click the advanced tab, then performance, then the advanced button. make sure the first 2 options are on programs then click change. Change your pf to system managed.

This could be one of MANY errors. Here are some things to check:
-Power Supply Problem. Make sure you have 20A on the 12V rail on your power supply. If you don't that might be causing this problem.
-RAM problem. It is a video card error, but this error comes up when you have bad RAM, or bad settings for it. Just reset everything to default in the BIOS (make sure you know what you are doing and how to undo it again), and see if that works.
-Video Card problem. A little while ago I had the same problem and tried everything. After a long series of e-mails from the company, I found out it was a problem with the actual Video card. I got it replaced, and no more problems.

There could, obviously, be many other problems, but these are the most common. Also, Guild Wars is sorta known to have these problems with Nvidia cards, even when the card runs fine with any other game. If none of these things fix it, do what I used to do, which virtually eliminated the problem: Run the game in Window Mode (F11 -> Resolution -> Window). That should stop the errors.

Hope this helped.

20A on the 12Vrail? I agree it could be a power supply problem. But there are many crappy PSUs boasting what looks like good specs. I'd more be concerned with the brand of the PSU. Even if he has 20A on the 12V the PSU could be crapping out.

He's better off grabbing a program like Sandra or Everest and checking what his voltages are like. Just Google them you'll find it.

Power supplies? People need to get educated...

Anyways...!

This problem is usually caused by a device driver or service, a damaged registry hive, bad sectors on the hard drive, or faulty memory (whether that be L2 cache on the CPU, video RAM or actual system RAM).



nv_disp.dll is a nvidia driver, so if you have the latest drivers; try rolling them back to an earlier version. If you're on an earlier version and do not have the latest drivers, try updating to the latest.



Should this not resolve the issue, try the steps below to resolve it or contact your local PC Technician.

Steps to fix this issue:

1. Perform an extensive memory test
   
   Faulty memory modules (or improper configurations/timings) are the leading cause of STOP errors. It is advisable to test your memory with the most accurate memory testing utility ever made: memtest86+. Shut down your computer, remove all but one memory module (except in the case of Rambus "RDRAM", which requires module pairs and terminator sticks) and boot the memtest86+ disk/disc. You should allow all 10 tests to pass at least 5 times. If a fault is detected, shut down the computer, replace the memory module with the next one (if applicable), and continue testing. Note: the Microsoft Memory Diagnostic utility is often not extensive or accurate enough, and thus is not recommended.
   
   
2. Use Last Known Good Configuration
   
   If you've recently installed a device or suspect registry damage, you should invoke the "Last Known Good Configuration" boot option to attempt to revert to your previously working system. This option causes the registry to use a previous version of the HKEY_LOCAL_MACHINE\System\CurrentControlSet registry key. Tap the F8 key before the Windows logo appears when you are first booting your computer, use the arrow keys to highlight "Last Known Good Configuration", and press Enter.
   
   
3. Attempt registry roll-back
   
   The SYSTEM hive, which is located in %systemroot%\system32\config\SYSTEM, is responsible for the entire HKEY_LOCAL_MACHINE\System tree. This is where hardware driver information is stored. If the Last Known Good option fails to solve the issue, it may be possible to revert to a previous SYSTEM hive by taking advantage of the System Volume Information folder. There are many other ways to cause this STOP error, including buggy drivers and damaged memory modules or other hardware.
   
   
4. Boot into Safe Mode
   
   In some cases, it may be possible to boot into Safe Mode. To do this, tap the F8 key repeatedly just before the Windows logo appears when you first boot your computer. Highlight "Safe mode" in the list using the arrow keys, and press Enter.
   
   If you are able to login under Safe Mode, there are a number of troubleshooting steps you can perform including using System Restore to roll back the registry to a previous state. This rolls all registry hives back, so recently installed software may no longer function if you choose to do this. It is better to have a technician roll back the SYSTEM hive (or other affected hives) manually using the techniques outlined in the System Volume Information article, to avoid losing software or user setting changes.
   
   If you need to perform a CHKDSK to validate the state of the hard drive and filing system, you can do this from Safe Mode via Start -> Run and entering "CMD" to open a Command Prompt. You can then enter "CHKDSK <boot_drive>" to check the drive.
   
   Running CHKDSK this way forces the initial testing to be done in "Read-Only" mode so that any errors or issues with the drive or filing system can be seen before you run CHKDSK /F to fix them. If the errors appear to be serious, numerious or could cause loss of valuable data then you can refer to a Technican for more indepth drive testing or data recovery.
   
   
5. CHKDSK /r
   
   Boot your Windows installation media, begin setup, and press R at the first screen to enter Recovery Console. An alternate way to jump straight into Recovery Console is to tap F10 when you see the status message about pressing F6 for mass storage drivers. NOTE: if your mass storage controller is SATA, SCSI, or external EIDE, you may need to press F6 (depending on whether the controller is in INT13/legacy mode or not) to allow Windows Setup to load mass storage device drivers from a floppy diskette so that Recovery Console will be able to see your system drive.
   
   Once you are logged into Recovery Console, type chkdsk /r and press Enter.
   
   If you are unable to log-in to recovery console, try reverting one or more registry hives from a previous backup as outlined in Solution #3. SYSTEM, SAM, and SECURITY, are three hives that should be considered (in that order).

This will not work, as every time you successfully boot your computer, the "Last Known Good Configuration" gets reset to the current configuration. So, that means that it will only work when you change something that prevents the computer from successfully booting up, there-by allowing you to revert back to the last configuration that did boot.

Here is some info for you to try:

0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
Requested data was not in memory. An invalid system memory address was referenced. Defective memory (including main memory, L2 RAM cache, video RAM) or incompatible software (including remote control and antivirus software) might cause this Stop message, as may other hardware problems (e.g., incorrect SCSI termination or a flawed PCI card). Use the General Troubleshooting of STOP Messages checklist above.
You receive a Stop 0x00000050 error on a Blue Screen {KB 894278} Win 2000, Win XP, Server 2003 (with concurrent 1003/System entry in Event Viewer: possible Rootkit spyware infestation)
Possible Resolutions to STOP 0x0A, 0x01E, and 0x50 Errors {KB 183169} Win NT, Win 2000, Win XP

Check the MS KB articles listed for more help....

Glad you read the full post, jjdefan. I think I hear your grade school teacher calling for you.

Did you miss where he said it only happens during games? That means his Windows Configuration is fine. The Last Known Good Configuration is fine. His problem is the display driver by nvidia.

Here, I'll point out the solution more for you here, and even edit my post to avoid more cases like yours.

nv_disp.dll is a nvidia driver, so if you have the latest drivers; try rolling them back to an earlier version. If you're on an earlier version and do not have the latest drivers, try updating to the latest.

kthx

Tarun is correct, if i had to bet anything on this issue it's video card drivers.

nv4_disp is an nvidia driver, i had this same problem on my GeForce4 MX440 card.. everything was fine in game until i got into the shiverpeak areas, especially the Droknars run because of the falling snow... when it BSOD'ed it was the same stop 0x0000050 error with nv4_disp.

i resolved this issue by backing up too the nvidia 45.23 drivers (thats Release Date: August 13, 2003) anything newer to that usually results in less performance on my card.

ya i find having the newiest drivers isen't actully always good especially if you have a older card try useing drives that where released around the same time your card was this is usaully only a problem with last generation cards along the lines of FX or 9000 series cards or older

Actually, the tech support told me it could also be a problem with the power supply...so....yeah. Im thinking that is one of the causes.

Also, to pick the right driver, go for the one that came out right after your video card was released, unless newer ones have fixes you need to play a certain game. Might take some research but that should bring good results. Last I saw, the driver that fixed this problem for some people was a 71.XX driver, though im not sure of the specific number.

Nothing like a 3.2ghz processor with an FX 5900

I am tech support. It's not the power supply.

I'm not kidding either. I work for a local tech shop doing all kinds of tech support. This issue is not caused by the power supply.

K, I was just suggesting it because, while looking around on forums for this fix, I saw that some people got this fixed by replacing the power supply and the support told me. However, I just noticed it was a FX 5900. Yeah, that wont be a Power Supply problem. I was thinking 6 series or like 7900.

Actually, I was having a similar problem, Nvidia card, 0x50 blue screen.

Turns out my rails weren't pumping out enough juice, and would dip too low when playing GW, and no other time. Replaced crappy no-name PSU with an OCZ ModStream, and crashes went away.

I've been building systems for... oh, ten years now, so I may not work in tech support, but I've done my share of it. It really could be a bad/crappy PSU.

Then again, it could also be overheating. Check your case air flow and cpu/ambient temps.