Jump to content

Hoot

Members
  • Content Count

    47
  • Joined

  • Last visited

About Hoot

  • Rank
    New Member
  1. I must have misunderstood what the LEDs mean. I thought all 4 lit meant it was trying to initialize the CPU, but had not finished? Hoot
  2. Problem appears to be cornered. Double Variable! When this first transpired, I assumed the new components I added were reliable replacements. Never Assume. I replaced my suspect motherboard with a new one using my old processor. No Change I replaced my old processor with a new processor in the new motherboard. No Change I troubleshot other components in system with a suspicious eye on the PSU. No Change What did I miss? I did not try the new processor with my old motherboard! Upon doing so, everything came up okay. I should have thought of that. Trust Nothing Even new components! Now I have to deal with the motherboard seller from Ebay, but he has a reputation as a fair guy. We'll see... Thanks for riding along with me. Old Faithful is rolling again. Hoot
  3. Well, it's certainly starting to narrow down to that through the process of elimination. Unfortunately, at work, all we have are less powerful ones, or ones not ATX12V or EPS12V compliant. Does anyone have a link to a precise explanation of what the problem is with them? This isn't rocket science as there's a finite amount of outputs from it and all seem to do be doing what they should be. I'm a scrupulous person and hate to be put in a situation of buying one to trouble shoot with, then returning it. I have an Antec True550 left over from the days of CPU's that derived their core voltage from the +5V output. I may be able to sub it in enough to see if I can get past the 4 lit LED stage. That would probably yield enough evidence to start the RMA process with Seasonic. Thanks, Hoot
  4. The sad part about what you say is the Seasonic S12-600 is probably one of the best made, independent 18A to each of the 12V rail PSU's made. What they don't spend on bling and advertising, they put into their product. It's not like I'm running a pair of SLI hogs an array of DVD burners and RAID5 or something. I did some additional testing. The Mushkin memory didn't work either. The PWR OK signal does go high after the outputs get into spec. Here's an oddity. While checking the CPU voltage at the socket, it appears to only be .970V. Not nearly enough to run the CPU stable. No wonder it fails to pass CPU initialization stage. Not sure why this is happening with this new motherboard as I said before, all the rails feeding it from the PSU are in spec. I never checked the CPU voltage on the old motherboard before swapping it out, but will definitely swap it back and see.
  5. While I haven't tried another PSU, I did read that thread before posting. My reasoning was if it had a compatibility issue with my motherboard, why would it wait a year and a half to manifest? I do intend to check the PWR OK signal when I get home from work. I'm checking out a digital storage scope for the weekend to see the timing relationship to when the +5 and +3.3V rails come into spec. vs when PWR OK transitions from logic low to high, assuming it ever transitions. I also borrowed a 512MB stick of Mushkin DDR memory from one of the PCs here to see if that yields anything. I read also about issues with Crucial Ballistik 1GB sticks. Again, I can't imaging them taking a year and a half to develop a problem. The S12-600 is in warranty and if I determine it to be the source of the problem, I'll try contacting Jeff or whomever at Seasonic. Thanks for your input. Hoot
  6. I'm stale after a 2 year vacation from the OC scene, where I was a real mover and shaker since the Duron 600 was king, to finish my long sought-after BSEE, after 30 years as an Engineering Technician. All of this is to emphasize the fact that I don't need Tier1 support. I need a Witch Doctor! My rig in my signature, which was the Rock of Gibraltar for a couple of years refused to get past the 4 LEDs lit stage the other day. The amber standby power and memory power LEDs were lit. I turned off the PSU, pulled out the battery and cleared CMOS. No Change. I removed the memory sticks and tried each, by itself in every DIMM slot. No Change. I took my Fluke 189 and Oscilloscope and checked the Seasonic S12-600 outputs while plugged in and failing to POST. All four of the main voltages were in spec and no ripple or significant noise. It's was so locked up, holding the power on button (both front panel and easy touch) would not force a power down. I got the sense, I was not even getting past "first base". I pulled out the PCI-E video card and put in a no frills, functional PCI video card. No change. I unplugged the two SATA drives, front panel USB extension cable, floppy drive, anything not needed to get past POST. No change. I Did the 24 hour CMOS reset. No change. I Tried a different functional PS2 keyboard. No change. Now, we move from the "miserable to the horrible". Knowing that I had done a few low-risk mods to the motherboard, I assumed it may have croaked. After a lot of searching for a discontinued product, I located and purchased a brand new identical motherboard. Not Cheap! I swapped it out and still no change. :eek2: I was hooked on getting to the bottom of this. Newegg had a great deal on a new A64 4000+ ($69.99) so I ordered one and (I bet you know where this is heading by now) it arrived yesterday. I replaced my trusty 3700+ and NO CHANGE! :sad: I'm at wits end with this. Any suggestions would be appreciated. Consider nothing had changed before the initial malfunction. No OC experimentation. No high-risk mods. No nearby lightning strikes, EMPs, Nothing. Am I cursed for not participating in these forums for the past couple of years? I repent!!! H E L P..... Hoot
  7. I've been using 704-3 for quite some time. Yes, I read the warnings and avoided using Vcore multipliers above a certain amount. That bios has allowed me to run these Ballistix 2x1Gb sticks at 300 Mhz 3-3-3-8-1T at 2.77V (measured at the sockets). No massaging all those memory parameters. Everything at default or auto, except basic timings. That is the mark of a great bios to me. Though I'm saddened by the prospect of getting no more betas, I'm pretty happy with what I got. Hoot
  8. A brief follow-up. In examining the main .dll file associated with MBM, the SMBus access point in the NF3 and NF4 MCP is not defined. The definitions end with the NF2 MCP chips. So, bdea, bdea, bdats all folks. Hoot
  9. The sysinfo is quite large, but before I post it, I found it odd that the SMBus dump was totally empty. Not a single address with data in it. All zeros. I'm really starting to think my initial assessment that mbmio is not yielding any smbus data, not even the SPD from my ram sticks. Here's the sysinfo dump: ----MBM SYSTEM INFO----- MBM 5.3.7.0 MBM 5 Core EXE : 5.3.7.0 MBM 5 Core DLL : 5.3.7.0 MBM 5 Settings DLL : 5.3.7.0 MBM 5 Dashboard DLL : 5.3.5.0 MBM 5 Hibernation DLL : 5.0.0.0 MBM 5 Ras DLL : 5.0.0.0 MBM 5 Logger DLL : 5.3.4.0 MBM 5 Mail, FTP and UDP DLL : 5.3.4.0 MBM 5 OSD DLL : 5.0.0.3 MBM 5 ASPI DLL : 5.2.1.0 MBM 5 Heat Up EXE : 5.0.0.0 MBM 5 Wizard : 5.3.5.0 MBMIO DLL : 2.32.64.2 MBMIO Driver : 1.0 built by: WinDDK DLL Folder Location : C:Program FilesMotherboard Monitor 5DLL Data Folder Location : C:Program FilesMotherboard Monitor 5Data Language Folder Location : C:Program FilesMotherboard Monitor 5Language Log Folder Location (Alarm) : c:program filesmotherboard monitor 5log Log Folder Location (High Low): c:program filesmotherboard monitor 5log Log Folder Location (Interval): c:program filesmotherboard monitor 5log Selected Language : English Info ChipInfo.ini : 18154 bytes 8/22/2005 7:25:02 PM Info shdn.ini : 388 bytes 10/12/2000 7:47:06 PM Info Voltage.ini : 38013 bytes 4/15/2005 8:35:32 PM Info Language file : 22920 bytes 6/12/2004 9:43:20 AM Up Time MBM session : 00:00:16:43 Up Time MBM total : 15:11:52:31 ------Sensor Chip------- Main Sensor Chip : ITE8712F SMB Address : $0000 Used Bus : ISA ISA Address : $0290 -Sensor Chip Selections- Possible Temp Sensors[1] : ITE8712F-1 Possible Temp Sensors[2] : ITE8712F-1 Diode Possible Temp Sensors[3] : ITE8712F-2 Possible Temp Sensors[4] : ITE8712F-2 Diode Possible Temp Sensors[5] : ITE8712F-3 Possible Temp Sensors[6] : ITE8712F-3 Diode Possible Temp Sensors[8] : ST380021A [0] Selected Temp Sensors[1] : ITE8712F-1 (192) Selected Temp Sensors[2] : ITE8712F-2 (193) Selected Temp Sensors[3] : ITE8712F-3 (194) Selected Temp Sensors[4] : ST380021A [0] (437) Selected Temp Sensors[5] : Custom (185) Selected Temp Sensors[6] : Custom (185) Selected Temp Sensors[7] : Custom (185) Selected Temp Sensors[32] : Custom (185) Possible Voltage Sensors[2] : MBM Fixed Selected Voltage Sensors[1] : MBM Fixed (2) Selected Voltage Sensors[2] : MBM Fixed (2) Selected Voltage Sensors[3] : MBM Fixed (2) Selected Voltage Sensors[4] : MBM Fixed (2) Selected Voltage Sensors[5] : MBM Fixed (2) Selected Voltage Sensors[6] : MBM Fixed (2) Selected Voltage Sensors[7] : MBM Fixed (2) Selected Voltage Sensors[8] : MBM Fixed (2) Selected Voltage Sensors[14] : Custom (1) Selected Voltage Sensors[15] : MBM Fixed (2) Selected Voltage Sensors[16] : MBM Fixed (2) Possible Fan Sensors[1] : ITE8712F-1 Possible Fan Sensors[2] : ITE8712F-2 Possible Fan Sensors[3] : ITE8712F-3 Selected Fan Sensors[1] : ITE8712F-1 T1 D4 (48) Selected Fan Sensors[2] : ITE8712F-2 T1 D4 (49) Selected Fan Sensors[3] : ITE8712F-3 T1 D4 (50) Possible Voltage Sub Types[0] : ITE8712F Standard 1 Possible Voltage Sub Types[1] : ITE8712F Standard 2 Possible Voltage Sub Types[2] : ITE8712F Standard 3 Possible Voltage Sub Types[3] : ITE8712F Standard 4 Possible Voltage Sub Types[4] : GA-8PE667 Possible Voltage Sub Types[5] : CT-7NJS Possible Voltage Sub Types[6] : GA-8IK1100 Possible Voltage Sub Types[7] : Shuttle SB61G Possible Voltage Sub Types[8] : GA-8IPE1000Pro Possible Voltage Sub Types[9] : GA-8KNXP Possible Voltage Sub Types[10] : Gigabyte GA-7N400-L Possible Voltage Sub Types[11] : Asus A7V8X-X Possible Voltage Sub Types[12] : GA-8PE667 Ultra Possible Voltage Sub Types[13] : Elitegroup N2U400-A Selected Voltage Sub Type : ITE8712F Standard 4 (3) --Sensor Chip Readings-- Temperature Readout[1] : -55 Temperature Readout[2] : 31 Temperature Readout[3] : 41 Temperature Readout[4] : 32 Temperature Readout[5] : 0 Temperature Readout[6] : 0 Temperature Readout[7] : 0 Temperature Readout[32] : 0 Voltage Readout[1] : 1.52 Voltage Readout[2] : 1.264 Voltage Readout[3] : 3.216 Voltage Readout[4] : 4.914 Voltage Readout[5] : 12.01212 Voltage Readout[6] : 1.584 Voltage Readout[7] : 2.72 Voltage Readout[8] : 2.928 Fan Readout[3] : 2960 ---------System--------- Operating System : Microsoft Windows XP (NT 5.1) (Build 2600) Service Pack 2 User : Hoot Memory in use : 27% Total Physical Memory : 1046952 KB Available Physical Memory : 760984 KB ----------CPU----------- CPU Speed : 2862 MHz Nr of CPU's : 1 -------3rd Party-------- ShutDownNow : ----Advanced Settings--- Fan Temp : 0 Custom Temp Table : 0 Startup Delay : 0 2E 4E Enabled : 0 2E Forced : 0 4E Forced : 0 Do Not Reset : 1 SMB Scan Range : $10 - $7F
  10. I'm sorry, I forgot to remark on that. I tried all the MAX6657/8/9 remotes as well as local codes, as well as MAX1617 and 1617a and MAX6651 codes, all of which, use the SMBus. All to no avail. I did not disable checking the SMBus before the primary chip since I do not care about the primary chips readings and wanted the SMBus to have priority. Am I misunderstanding what that checkbox is for? Thanks, Hoot
  11. I'm not sure how secure the postal system is over there, but if you can help me solve my particular mystery, I'll send you a MAX6657. It is only 1 local and 1 remote channel, but it is better than nothing. I purchased mine online from MAXIM. They also will send samples, though I'm not sure how that works to overseas designers. With my setup, I have the MAX6658 chip actually bonded to my WB inlet water supply hose to monitor water temperature. The remote channel, as I said, goes to the CPU. Though I have grown accustomed to Speedfan these past few months, I still pine for my MBM dashboard. I am at work right now, but when I get home, I'll post my system information as it applies to the SMBus. At the risk of being redundant, it works fine with Speedfan, so I doubt my system is not communicating with the SMBus. Thanks, Hoot
  12. I have the current Nvidia chipset drivers installed and reading the SMBus works since Speedfan reads it just fine using giveio.sys Most, if not all motherboard manufacturers, in order to shave another few pennies from the cost of manufacturing, have discontinued providing an SMBus header. Take heart though, you can still access the SMBus from the DIMM slots Pins 92 and 91. Either strip off an old DDR module and solder to the appropriate edge connector pins and put it in an unused DIMM slot, or as I did, just Carefully solder to the backside of the board. You can get a ground connection on pin 89 and use shielded sub-miniature two conductor cable. I use some very small balanced microphone cable for this task, approximately 2mm outside diameter. Very easy to route to your external diode reader, but you also need to pick up +5V somewhere to power the chip. Hoot
  13. Okay, lets start over with a simpler inquiry. Has anyone succeeded in getting MBM 5.370 to recognize the SMBus and any monitoring devices connected to it on either NF3 Ultra-D or NF4 Ultra-D based motherboards? Thanks, Hoot
  14. It sees the chip, but since the diode is not connected to the chip, it reads -117. That's normal when the diode is rerouted away from the socket. I tried setting T1 for device 586 (Maxim 6657/8/9) but it reads zero. I'm assuming MBM is not reading the SMBus address $4C where the Maxim resides. This used to work when MBM used giveio.sys, which is what Speedfan still uses. Something about the new driver that came out when MBM jumped to 5xxx??? Hoot
  15. I use a Maxim 6658 external thermal diode reader, via the SMBus, to monitor my CPU. Don't ask how I get it routed away from the socket. That's a multi-page document. Anyway, starting with my Neo2 Platinum (NF3) as well as the DFI NF3-D, I could no longer read my Maxim 6658. Speedfan reads it fine, but not MBM. Now, I have the NF4 Ultra-D and still can't read it with MBM. I've spent some time messing with the sensor chip selections, but to no avail. My NF2 based board worked fine with MBM and the Maxim 6658, go figure... Any suggestions? Thanks, Hoot
×
×
  • Create New...