Multiple STOP errors

[TranquilChant]

Hey all,

I just received a brand new PC for Christmas (even though I had to pay for half of it). It's supposed to be top of the line, but it's caused me nothing but grief ...

ABit Fatal1ty AN8-SLI

AMD Athlon 64 X2 4800+ Toledo

BFG Tech GeForce 7800 GTX

Thermaltake Silent PurePower 680W

4x Patriot 1g DDR 400

2x WD Raptor 74 GB

2x WD Caviar 300 GB

Creative Sound Blaster Audigy 2 ZS Gamer

all bundled up in a nice Antec Super Lanboy

So that's the system.

The first problem I encountered was a STOP error when running a BitTorrent client (I've tried Azureus, TorrentStorm, and more). That is STOP error 0x000000D1 (IRQL_NOT_LESS_OR_EQUAL) with the file nvsnpu.sys specified. I have seen it a couple of times, but have not been able to replicate it in the past couple days (mostly because I've stopped using BitTorrent until I figure it out).

The second problem I encountered was a STOP error when running (online) games. I have Halo and Battlefield 2, both of which run fine (BF2 in single player mode, have not yet tested online). I also have World of Warcraft. Whenever I play WoW, I get one of two stop errors. I do not get these when playing Halo or BF2 single player. The first one I got is STOP error 0x00000050 (PAGE_FAULT_IN_NONPAGED_AREA) with the file win32k.sys specified. The second one I got is STOP ERROR 0x0000008E (0xc0000005, 0xBF9D77C3, 0xB9F49AD0, 0x00000000) with the file nv4_disp.dll specified (Address BF9D77C3 base at BF9D4000, DateStamp 439abe35.

Those are the major problems I've had. I don't know what is causing them, but the constant "nv" leads me to believe that it's something to do with my chipset (Nvidia) or my GPU (Nvidia). I've got the most recent BIOS release, chipset drivers, GPU drivers, everything.

I've had another weird problem lately. I opened my case to connect the front panel I/O (headset) jacks to the sound card. I took out the sound card, looked at it, realized that it doesn't have the right connectors, put it back in the PCI slot, and closed the case. I didn't touch anything else. When I booted up, I got a DISC READ ERROR HAS OCCURRED. So I went in to my BIOS and immediately noticed that the date and time had reset. So I look further and realize that my entire BIOS reset. I've got my HDDs set up in two RAIDs (one RAID0, one RAID1) and the RAID settings in BIOS had reset. So, I set the values I knew how to set and got the PC back up and running. However, I didn't know what to do with some of the other values in BIOS. I'm getting profession help with that tonight. Hopefully, when I get that help, the STOP errors occurring when I play WoW will stop (since I played it fine before the BIOS reset). I did have the BitTorrent problem before the BIOS reset though.

Thanks for reading this long post. I do not have any more information about the STOP errors and have had a tough time trying to replicate them, as it seems to always be a new one that occurs.

TC

[John Veteran]

The 0x0000008e error could either be 1. bad RAM or 2. bad drivers. Since the RAM is brand new and it specifically lists your video driver, It's fairly safe to assume an updated video driver will fix this error. Nvidia drivers are well known for this error, and I used to get this error with several driver versions on my old Geforce 3 Ti.

Your video driver is also likely to blame for the 0x00000050 error. Win32k.sys is the Windows GUI, and ususally errors citing this driver are actually caused by other drivers, but the error-prone data doesn't cause problems until it's in this driver, incorrectly leading the user to believe win32k.sys is at fault. Unfortunately, this makes it difficult to track down which driver is the actual source of the problem, unless you have a kernel mode debugger and step through every line of code (what fun that would be, if you even knew what to look for).

Finally, the 0x000000d1 error specifically says the IRQL of the nvsnpu.sys driver is too high, which basically means the driver isn't handling things correctly. I looked up this file on Google and it appears to be part of your chipset drivers, for the on-board network adapter. Look for updated chipset drivers, or even updated NIC drivers.

Hope this helps :)

[TranquilChant]

Hey John,

How's Hellhole, Illinois? :-p

All my drivers are the most recent releases. Everything is up to date. I've checked the drivers at least five times and, as far as I know, everything is the most recent.

Could it be IRQ problems? I looked at my System Information and I have four IRQs (18, 19, 21, and 22) that have more than one device/process.

18 - Creative SB Audigy 2 ZS (WDM)

18 - NVIDIA GeForce 7800 GTX

19 - Texas Instruments OHCI Compliant IEEE 1394 Host Controller

19 - OHCI Compliant IEEE 1394 Host Controller

21 - Standard Enhanced PCI to USB Host Controller

21 - NVIDIA nForce 4 Serial ATA RAID Controller

22 - NVIDIA nForce 4 Serial ATA RAID Controller

22 - NVIDIA Network Bus Enumerator

Could the cause of (some of) my problems possibly be IRQ 18?

Thanks John

Dylan

[John Veteran]

Hi Dylan :p

I don't think it would be IRQ problems, though if you want, you could try disabling your Audigy, or even physically removing it and putting it in another PCI slot.

I also noticed that your Nvidia Network Bus Enumerator (nsvnpu.sys) is sharing an IRQ with your RAID controller. Maybe the Network driver is incorrectly responding to IRQs to/from the hard drive, which could cause problems I guess. But still, the IRQs a device uses are controlled by Windows, with heavy influence from the drivers for that device, which again leads me to believe that if that device needed it's own IRQ, the driver should ask Windows for it.

If your drivers are all updated, I would uninstall your soundcard and put it in another PCI slot (thus forcing Windows to re-evaluate the IRQ for the soundcard), and connect your hard drive to the other RAID controller (so it uses the other IRQ). That may or may not fix either issue, but it's the only thing I can think of right now other than driver issues.

[TranquilChant]

John....

Remember how we cleared all those wires out of the way and then how the monitor wouldn't show anything? The monitor still won't activate, even after taking out the GPU and pushing it back in....

Waaaahhhh!

:-p

Dylan

[John Veteran]

For everyone here who doesn't know what happened, his PC was overheating, causing crashes. You should have SEEN the mess of cables inside :omg: Absolutely no airflow, whatsoever.

Dylan, you called me today and said you got it working just fine? What happened? :p

Edited January 9, 2006 by John

[s0nic69]

^ lol thanks for clearing that up, i was reading down and i was like, wait, what happened.