View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000332 | SpeedFan | Hardware support | public | 2005-08-15 11:54 | 2005-08-23 10:04 |
| Reporter | thom-s | Assigned To | alfredo | ||
| Priority | normal | Severity | major | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| OS | Win | OS Version | XPSP2 | ||
| Product Version | 4.24 | ||||
| Summary | 0000332: System won | ||||
| Description | I am using an ASUS A8N-E nForce4 Ultra Mainboard with the latest available production BIOS from ASUS which is V1005. Speedfan is working fine (though - I have to configure the voltage settings correctly but I do not see any problems there), but I have a strange problem when I try to reboot my machine. Whenever I have Speedfan running while shutting down the computer for a reboot - the system won | ||||
| Steps To Reproduce | Let Speedfan running while shutting the system down for a reboot with an ASUS A8N-E board | ||||
| Tags | No tags attached. | ||||
| Motherboard Model | |||||
| Video Card Model | |||||
|
|
additional info: I installed the current beta BIOS (1006-003) and tried again to start speedfan with the options: /NOPCISCAN /NOSMBSCAN /NOSUPERIO /NOSCSISCAN /NOACPISCAN /NOTOSHIBA /NOASUSSCAN /NONVIDIAI2C - this time with success. Using speedfan without all the paramters still results in the error mentioned in the initial report. |
|
|
This is quite unusual. Please, send me a SEND REPORT and then drop me an email to point me at it. |
|
|
You should still be able to use all SpeedFan features even with /NOSMBSCAN /NOACPISCAN. Does it fix your issue? |
|
|
/NOSMBSCAN /NOACPISCAN did not help me out of this. But I played around with all the parameters and finally found out that using /NOSCSISCAN fixes this for me. I do not have a meaningful explanation for this - but it helps ... |
|
|
SCSI support never caused any issue. You are the very first one to report such an issue. I can't say it for sure, but it looks like SpeedFan is triggering something odd inside your SCSI controller's drivers. Anyway: I'm closing this issue as it is resolved :-) |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2005-08-15 11:54 | thom-s | New Issue | |
| 2005-08-16 11:31 | thom-s | Note Added: 0001099 | |
| 2005-08-21 01:38 | alfredo | Note Added: 0001102 | |
| 2005-08-21 01:38 | alfredo | Status | assigned => acknowledged |
| 2005-08-22 08:40 | alfredo | Note Added: 0001105 | |
| 2005-08-23 08:13 | thom-s | Note Added: 0001109 | |
| 2005-08-23 10:04 | alfredo | Note Added: 0001110 | |
| 2005-08-23 10:04 | alfredo | Status | acknowledged => resolved |
| 2005-08-23 10:04 | alfredo | Resolution | open => fixed |
