Shoutbox

... Until I've experienced this issue, I've not heard of the file nvdisp.drv. However, When I installed Messenger Plus! 2.54 it worked great. (did this 2 days ago).

When I shut off my computer for the night, and turned it on in the morning, Messenger would crash immediatly upon activation.

The Error Message:
******
*Msnmsgr has caused an error in NVDISP.DRV.
*Msnmsgr will now close.
*
*If you continue to experience problems,
*try restarting your computer.
******

The first time I run Messenger, the error appears, and locks up the computer until I say okay. The 2nd time I run Messenger, the error message does not appear; but the entire system will hang, leaving me with a cold boot as my only option. Restarting the computer after the 1st attempt will not change the order (If I restart after crashing once, the computer will still hang if I run it again).

Doing a bit of research, it seems the file NVDISP.DRV is a Device Driver (obviously), for the Nvidia series of video cards. This isn't my computer, so I didn't select the video card, but knowing the owner of the computer, it (the computer) is, with 95% certainty, using the 2MB on-board video cache.

Anyway, computer specs:
-- Hewlett Packard (augh...) Pavillion Series
-- Windows Millenium OS (gah... with the above, it's the combination from hell, I work for Microsoft so I can say that).
-- AMD Athalon Processor (not bad)
-- 128 MB RAM.

I just did a File Search for it, I have two occurances of the file. One is in the Windows CAB files, the other, the one that crashes Messenger, is in Windows/System... I wonder if the fact that all the letters are capitalized indicates that the file is infected...

Any help on the issue is appreciated.

It isn't likely to have anything to do with Plus!, still I suggest you upgrade the MSN Messenger as well as the nVidia driver to the latest version

quote:

---

Originally posted by Mnjul
as well as the nVidia driver to the latest version

---

shouldn't it be better to put version 45.23 instead ot the latest?

quote:

---

Originally posted by Choli
shouldn't it be better to put version 45.23 instead ot the latest?

---

Perhaps he's not using TNT series...

quote:

---

Originally posted by Mnjul
Perhaps he's not using TNT series...

---

I didn't know that I though the problem was with nVidia cards is general...

quote:

---

Originally posted by Choli
I didn't know that I though the problem was with nVidia cards is general...

---

(We're getting offtopic)
Oh no, that only happens with TNT/TNT2 series cards...generally GeForce series have no such problem

quote:

---

Originally posted by Mnjul
(We're getting offtopic)
Oh no, that only happens with TNT/TNT2 series cards...generally GeForce series have no such problem

---

Geforce4 Ti 4200 here, I did have problems (non-messenger related though, it was a multi-moni related problem) with latest driver and had to roll back also...

---on topic---
Could it be that NVDISP.DRV has just been corrupted by something? (too much fragmentation, error on disk, ...)
Also in the windows\system folder most filenames are capitalized with me. In windows\system32 there are a lot of nv*.* files, but no nv*.drv files (even not on my entire HDD).

quote:

---

Originally posted by CookieRevised
Also in the windows\system folder most filenames are capitalized with me.

---

do you mean they begin with Upper Case Letter? that's not the problem , because the file system (NTFS) is not case sensitive (although it can remember the case in which files were created)

no I mean they are all capitalized (well most of them)... well I used proberly the wrong word... I mean uppercased. I know it doesn't matter actually, but the thing is viruses or other programs could have overwritten the filename and used uppercase filenames instead of the original filename. That happens with some of them. This is what "The GLoC" meant by "I wonder if the fact that all the letters are capitalized indicates that the file is infected". So my reply was just to say that in windows\system most of the filenames are original uppercased (in my case, using XP).

For the record: neither my Geforce 2 and my GeForce4 ever experienced this problem.