View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000235 | SpeedFan | Other | public | 2005-04-02 21:11 | 2005-04-05 09:09 |
| Reporter | SVoyager | Assigned To | alfredo | ||
| Priority | normal | Severity | crash | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Platform | Custom built, P4 3.2 | OS | WinXP Pro | OS Version | 2002 SP2 |
| Product Version | 4.22 | ||||
| Summary | 0000235: *Crash* while detection of nvidia cards | ||||
| Description | This is more or less a crash and is a little bit related to issue 0000047 but with more severe consequences. When speedfan detects the GF6600GT (in my case) and has problems reading the data on it, my system will become unstable. Contrary to the 0000047 issue, I do not experience a slowdown when it is unable to read the data but if I do try to open an application at the same time of the detection process, I will get a big graphic corruption on the screen and browsing the system becomes close to impossible. The system does not crash however but the display is screwed until next reboot. I realised this was happening when speedfan took about 1-2 minutes to report what it had scanned on the taskbar and that it wasnt always detecting the same amount of chips after each reboot. | ||||
| Steps To Reproduce | Using the /NONVIDIAI2C to turn off the detection of the card and then trying to screw the display again and was unable. Using the switch to turn it back on again and after a few reboots I managed to screw the display again. 1- Set SpeedFan to start with /NONVIDIAI2C 2- Reboot 3- Once desktop is visible, open as many apps as possible even if windows is not done loading all programs 4- Unable to screw the display --- Do the same steps again with the switch to reactivate the detection of nvidia gfx cards 4- Able to screw the display on multiple occasions. Will not happen 100% of the time but often enough to be able to test | ||||
| Additional Information | At first I tought this was related to gfx drivers so I tryed 2 different sets. The latests ones by nvidia and one that has always been working fine with my setup. (71.84 and 66.93) both had the same problem when I did the steps mentionned above. However I didnt had alot of time to test this so if a tester here with nvidia gfx card could try to confirm my claims, and add it to this report, it would be appreciated. I tought it would be useful to report it anyway with what I had. Hope it helps make this already awesome soft even better! | ||||
| Tags | No tags attached. | ||||
| Motherboard Model | |||||
| Video Card Model | Asus EN 6600 (Nvidia GF6600 GT, PCI-Express version) | ||||
|
|
Unfortunately NVidia never answered any email. There is some other tool that is accessing the I2C bus on your video card and the lack of a proper synchronization should be the cause for this issue. The only solution, to date, is the /NONVIDIAI2C command line switch. |
|
|
I am using a BFG 6800 Ultra OC and the problem is much worse. I am using SpeedFan 4.22. I believe that there is a conflict between some nvidia software (nv4_disp.dll, NVIDIA Corporation, ver 6.14.10.6693) and SpeedFan. I have observed several different behaviors: 1. SpeedFan seems to get stuck in a loop and becomes unresponsive, it utilizes 25% CPU continuously in this state. 2. I get graphic problems, sometimes at the same interval that SpeedFan is logging its readings. The system often seems to hang when this starts to happen. 3. I get a blue screen in nv4_disp.dll, 0x100000ea (0x8678da18, 0x8650f458, 0xf7af2cbc, 0x00000001). Here is a Microsoft kb article about the stop error: http://support.microsoft.com/default.aspx?scid=kb;en-us;293078 Update: stopping and disabling a service called "NVIDIA Display Driver Service" (C:\WINDOWS\system32\nvsvc32.exe) seems to have solved the crash related problems with SpeedFan. The service description is "Provides system and desktop level support to the NVIDIA display driver". I have not noticed any change (other than SpeedFan working as expected) since I disabled the service. |
|
|
Doesn't the /NONVIDIAI2C fix your issue? |
|
|
Just a side note... I really can't understand why nVidia is not releasing, at the very least, the basic info to access hardware monitor data. It makes really little sense to me... |
|
|
Thanks alot for confirming the problem alfredo, too bad nvidia doesnt want to cooperate with this. Just a quick note/suggestion related to this tho. Judging from your response, it seems to be known stuff but I couldnt find specific infos about this problem besides on issue 47. Might be good to put a warning/option to ignore nvidia cards on future SF releases for that specific problem! |
|
|
Using /NONVIDIAI2C does solve the problem - without getting any temp readings from the video card. However, in my case, stopping the 'Nvidia Display Driver Service' allows SpeedFan to run in a stable manner AND I am able to get temp readings from the video card. |
|
|
I will consider both the /NONVIDIAI2C and the driver removal tool the right fix for this issue. Obviously, if I will ever receive any info from NVidia, I will be glad to improve support for their hardware. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2005-04-02 21:11 | SVoyager | New Issue | |
| 2005-04-02 21:11 | SVoyager | Video Card Model | => Asus EN 6600 (Nvidia GF6600 GT, PCI-Express version) |
| 2005-04-03 11:52 | alfredo | Note Added: 0000809 | |
| 2005-04-03 11:52 | alfredo | Status | assigned => acknowledged |
| 2005-04-03 20:59 | galloloco | Note Added: 0000815 | |
| 2005-04-03 23:22 | galloloco | Note Edited: 0000815 | |
| 2005-04-04 00:08 | alfredo | Note Added: 0000816 | |
| 2005-04-04 00:09 | alfredo | Note Added: 0000817 | |
| 2005-04-04 00:23 | SVoyager | Note Added: 0000818 | |
| 2005-04-04 01:01 | galloloco | Note Added: 0000819 | |
| 2005-04-05 09:09 | alfredo | Note Added: 0000823 | |
| 2005-04-05 09:09 | alfredo | Status | acknowledged => resolved |
| 2005-04-05 09:09 | alfredo | Resolution | open => fixed |
