Hardware monitor program?
in [Asus]
|
Prev: WANTED TO BUY - NETWORKING, TELECOM EQUIPMENT & SOFTWARE - CISCO, NORTEL, LUCENT, JUNIPER, EXTREME, FOUNDRY, FUJITSU, MICROSOFT, ADOBE, SYMANTEC & MORE
Next: Asus Mobo P6X58D-E, backing up and configure SATA as IDE
From: John on 29 May 2010 14:17 I'm still trying to track down the source of the intermittent lockups in my computer and thinking that it might be helpful to monitor temperatures and voltages over time and see if there's any correlation between the sensor readings and the lockups. I'd like to find a program (free is nice but I'm willing to pay for a good one) that can sense temperature and voltage readings and record them to a file. Because my problem is so intermittent, I can't count on being there at the time of the failure, and I want to record them so I can look back after the fact. Can anybody recommand such an app? I've Googled around and tried several and found them all lacking in one repect or another, mostly in an inability to record. John Reply-to address is real
From: Anssi Saari on 29 May 2010 15:24 John <fakeaddress(a)nowhere.com> writes: > Can anybody recommand such an app? I've Googled around and tried > several and found them all lacking in one repect or another, mostly in > an inability to record. It would help if you said what you tried already. I think speedfan is common, but I have no idea about logging. Not big on Windows. Should be easy to find a program that loads your system and causes heating, if that's the problem. If you can't find a suitable tool, hardware diagnostics for a PC is pretty straightforward. Let's see, three steps? Step 1. Test RAM (real test, meaning memtest86 or memtest86+, whichever is current at the time, or both). Step 2. Remove all non-essential components. Any extra cards, USB devices, RAM, disks, other storage and see if that helps. If not, then Step 3. Start swapping components, first PSU, then motherboard.
From: John on 30 May 2010 22:08 On Sat, 29 May 2010 22:24:19 +0300, Anssi Saari <as(a)sci.fi> wrote: >It would help if you said what you tried already. I think speedfan is >common, but I have no idea about logging. Not big on Windows. Should >be easy to find a program that loads your system and causes heating, >if that's the problem. Speedfan, as far as I can see, has no ability to log its readings. I'm not interested in stressing the system, I've done that already and found the the failures seem unrelated to load. I'm interested in monitoring its behavior; that's why I was inquiring about a monitor app. >If you can't find a suitable tool, hardware diagnostics for a PC is >pretty straightforward. Let's see, three steps? >Step 1. Test RAM (real test, meaning memtest86 or memtest86+, >whichever is current at the time, or both). Yeah, BTDT. Ran about 9 hours of memory checks with MS Memory Test amd memtest86+. No errors. >Step 2. Remove all non-essential components. Any extra cards, USB >devices, RAM, disks, other storage and see if that helps. If not, then Given the intermittent nature of the problem (the system can run for days or even a week or more without failure) this approach isn't very practical. >Step 3. Start swapping components, first PSU, then motherboard. .... or RAM ... or video card ... or ? Straightforward? perhaps, but time-consuming and expensive. That's why I was hoping to find a monitor app that would allow me to get some idea of where the problem might lie before I just started throwing parts at it. Thanks for the thoughts. John Reply-to address is real
From: Foke on 31 May 2010 16:47 On Sat, 29 May 2010 14:17:54 -0400, John <fakeaddress(a)nowhere.com> wrote: > >I'm still trying to track down the source of the intermittent lockups >in my computer and thinking that it might be helpful to monitor >temperatures and voltages over time and see if there's any correlation >between the sensor readings and the lockups. > >I'd like to find a program (free is nice but I'm willing to pay for a >good one) that can sense temperature and voltage readings and record >them to a file. Because my problem is so intermittent, I can't count >on being there at the time of the failure, and I want to record them >so I can look back after the fact. > >Can anybody recommand such an app? I've Googled around and tried >several and found them all lacking in one repect or another, mostly in >an inability to record. > >John > >Reply-to address is real Everest Ultimate isn't free ($30 US) but does provide logging capability. You can install it on up to three machines, which is nice.
From: Jack Simms on 1 Jun 2010 02:17
On Sun, 30 May 2010 22:08:03 -0400, John <fakeaddress(a)nowhere.com> wrote: >On Sat, 29 May 2010 22:24:19 +0300, Anssi Saari <as(a)sci.fi> wrote: > >>It would help if you said what you tried already. I think speedfan is >>common, but I have no idea about logging. Not big on Windows. Should >>be easy to find a program that loads your system and causes heating, >>if that's the problem. > >Speedfan, as far as I can see, has no ability to log its readings. > >I'm not interested in stressing the system, I've done that already and >found the the failures seem unrelated to load. I'm interested in >monitoring its behavior; that's why I was inquiring about a monitor >app. > >>If you can't find a suitable tool, hardware diagnostics for a PC is >>pretty straightforward. Let's see, three steps? >>Step 1. Test RAM (real test, meaning memtest86 or memtest86+, >>whichever is current at the time, or both). > >Yeah, BTDT. Ran about 9 hours of memory checks with MS Memory Test >amd memtest86+. No errors. > > >>Step 2. Remove all non-essential components. Any extra cards, USB >>devices, RAM, disks, other storage and see if that helps. If not, then > >Given the intermittent nature of the problem (the system can run for >days or even a week or more without failure) this approach isn't very >practical. > > >>Step 3. Start swapping components, first PSU, then motherboard. > >... or RAM ... or video card ... or ? > >Straightforward? perhaps, but time-consuming and expensive. That's >why I was hoping to find a monitor app that would allow me to get some >idea of where the problem might lie before I just started throwing >parts at it. > >Thanks for the thoughts. > >John > >Reply-to address is real if ur running windows .. is there any useful info in the event logs ? |