nvidia monitor crashing in vista x64

[JAG87]

Hi all, I just installed vista x64. Im going to keep this short and sweet.

nforce drivers: 15.00
forceware: 158.43 beta
ntune: 5.05.38.00

basically when I launch NVmonitor I get "this applications has crashed", and I just choose close the program. my system is in my sig I dont think it matters too much thou because everything else works fine so I doubt its something hardware related. I am going to install the 158.45 beta drivers tomorrow (btw they just came out today for those who are interested).

Could it be because I am running beta drivers? I never tried with the 158.18 WHQL ones. Anybody else in the same conditions?

:frown:

 

[cprince]

You should get the release version of the driver instead of the beta version. Beta version always have problems(that's why it's beta).

 

[JAG87]

I am going to try that today.

anybody else experiencing this with Vista x64 + 680i + 8800 cards?

 

[imported_Wanger]

mine does it also with same setup

 

[lamere]

vista......ugh...

someone kill it before it spreads to the rest of the populace and jacks their machines too....

 

[JAG87]

Originally posted by: Wanger
mine does it also with same setup

sigh... its not just me then. crap, nvidia FIX IT! I need to monitor my temps...

 

[terentenet]

NVmonitor works here!

Drivers I'm using:
Forceware 158.45
nTune 5.05.38.00
nForce 680i v15.00 from Nvidia, with Vista RAID/SATA Driver v9.92 from EVGA

Try this driver configuration, post back. It all has to do with the Forceware driver. NVmonitor crashes when trying to get the temps from the GPU, which means FW drivers are broken. Hope this helps.

JAG and everybody using EVGA 680i, you also might want to update the RAID/SATA driver with the one provided by EVGA; I gave the link up there. It improved performance for me (slight improvement).
It also fixed the warm boot RAID ARRAY detection issue I used to have when rebooting Vista.
To explain this issue I used to have, whenever I rebooted Vista, RAID ARRAY detection at POST would take 20-30 seconds, opposed to the normal of 1 second. This only happened when rebooting Vista, XP is not affected.

 

[JAG87]

Terentenet, I have the reboot problem as well! The hard drives spin down and then they spin back up when the array is detected, and it takes like 10 seconds extra to reboot. I am going to try and install the 9.92 raid drivers tonight and see if it helps. but honestly, I doubt its going to fix nvmonitor.

Did you install the drivers in any particular order? also I have P28, do you? I cant think of anything else that is different between out systems. sigh I need nvmonitor to work, vista heats up your hardware more than xp and I need to keep an eye on temps...

 

[terentenet]

Here's the order... how I do it.
1. official Nforce v15.00 from Nvidia; reboot
2. Vista RAID/SATA v9.92 from EVGA. Unpack the zip, go to Device Manager, manually update Nvidia RAID Class controller. That should update all drivers under SCSI/RAID Controllers. Check the versions, make sure all controllers were upddated; reboot, the delay should be gone
3. Forceware 158.45 (Uninstall old version first if you want. I never do that and I never had any problems. I just update drivers one on top of the older one . I only walk the extra mile if something goes wrong).
Make sure to install 158.45 version. 158.43 that you're using right now might be the culprit; reboot
4. Install nTune

Give it a shot. It works here and our systems are parctically the same, so, what works for me should work for you as well.

Post back and let us know the results.

 

[gnumantsc]

Nvidia just released new drivers as well today so try the new ones. As far as running x64 bit version of Vista I would highly advise against it as even the 32bit version is still poor with driver support.

 

[JAG87]

nothing terent, same crap. I uninstalled and reinstalled the drivers in that order, ntune is still screwing up. it doesn't detect voltages in the performance section, and nvmonitor crashes. sigh. I give up.

edit, the raid drivers fixed the spin down problem
-1 bugs... 99 to go...

 

[terentenet]

Including the video card driver? If that doesn't work, I don't know. We have the same hw configuration, now you've installed the same drivers... I don't see the reason it's not working.

Perhaps it's something in the BIOS. Try freeing as much resources (IRQs) as possible... doesn't have anything to do with NVmonitor, but should keep the chipset cooler by putting less strain on it.
I only have SATA drives, IDE controller disabled. Disabled FDC controller. Disabled on-board sound and serial port.
In the CPU section, disabled everything (Virtualization, execute bit, thermal control... all disabled).
Disabled Nvidia GPU Ex.
.
.
.
UGHHHH... it MUST work!

 

[JAG87]

Originally posted by: terentenet
Including the video card driver? If that doesn't work, I don't know. We have the same hw configuration, now you've installed the same drivers... I don't see the reason it's not working.

Perhaps it's something in the BIOS. Try freeing as much resources (IRQs) as possible... doesn't have anything to do with NVmonitor, but should keep the chipset cooler by putting less strain on it.
I only have SATA drives, IDE controller disabled. Disabled FDC controller. Disabled on-board sound and serial port.
In the CPU section, disabled everything (Virtualization, execute bit, thermal control... all disabled).
Disabled Nvidia GPU Ex.
.
.
.
UGHHHH... it MUST work!

I have IDE enabled, everything else disabled, including firewire.
CPU section is all disabled.
GPU Ex is enabled.

so 2 differences. I doubt they make the difference though. stupid hunk of crap, they better release a working ntune. i have nvidia branded motherboard, video cards, ram, and even my damned zalman heatsink has an nvidia sticker on it, and their software doesn't work... what else is new.

 

[terentenet]

I think I have another ideea.
When I installed Vista x64 Ultimate, I turned off some components that were bugging me. I'm an advanced user anyway, no need for overprotection. I've been using XP for years without those and never felt the need for such security mechanisms so... I turned off Windows Defender and UAC. UAC has the ability to crash your program. Plus, they eat system resources.
I don't even use antivirus software and I didn't get any virus since 2000-2001.

Windows defender and UAC is what I can remember so far. I think I also made some other adjustments, I can't remember.

Check this site. Some tricks and tips.

I turned off UAC as follows. 1st, I made the nag screens dissapear:
Disable User Account Control(UAC) For Administrators Only
Then, I disabled it for good:
Disable User Account Control (UAC) the Easy Way on Windows Vista

To turn off the Windows Defender, you need to run services.msc; look in the list for Windows Defender, double click it, set the Startup Type as Manual or Disabled.
Then, run msconfig, go to the Startup tab, uncheck Windows Defender, hit Apply, reboot.

 

[JAG87]

already done dude. I cant stand UAC. Windows Defender is not completely off, I turned off autoscanning, but real-time protection is still on. I doubt its crashing nvmonitor, but ill give it a shot...

since you are running x64, maybe you can give me some pointers with a few games... dod source (as well as Episode 1) seem to run like complete ass compared to XP, plus everytime I switch maps it crashes with some HL2 error. BF2 also crashes occasionally with some memory heap allocation error of some kind, and Call of duty 2 multiplayer (which I run in dx7) has a 25-30 second lag-black screen launch issue (but it still launches if you wait for 30 seconds). Its amazing how the only game that hasen't given me problems is good old cs 1.6. I figured old games would have compatibility issues, but hey microsoft proves me wrong once again. x64 architecture has a long road ahead still...

thanks for all your help terry, I appreciate it.