Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[renluop]

I am bemused by today’s happenings.
I have DSLStats set up to take snapshots every three hours ( sampling interval 60secs) and include error and event logs.
However, after that record made just before 10 there is no record at 1 and error and event texts are missing even at 10.
From about 11.30 I was out or otherwise away from the computer to 3.30. Shortly after then a pop up warned the program had stopped working. The produced graphs, covering from 12.40 to 3.40 were flat lines, and somehow the sampling time had moved forward by ~ 15 minutes.
All is most weird. Has anyone at all got ideas what could be happening, be it the program or elsewhere in my system; a nasty of some sort?

[roseway]

This is not normal behaviour of course. The first thing I would ask is - do you really need all these snapshots? Also, is it possible that your PC rebooted while you were away?

The only way to diagnose this sort of issue is to cut down the problem as much as possible, so turn off all the snapshots and other features you don't absolutely need; QLN and HLog, for example, are only refreshed by the modem at sync time, so there's no point in taking multiple snapshots of these.

Run DSLstats in this reduced way for a while, then gradually add more options a bit at a time until you hit a problem.

That being said, I do suspect that your PC may be misbehaving.

[renluop]

Usually at any reboot or restart a DOS ( what ever it's called now) appears to choose Win 10 or..., so am not too convinced a reboot happening being a culprit. I wonder if the computer event log may reveal something, but they're Sanskrit, or may as well be.

I'll follow your suggestion about reduction of snapshots. Would sampling frequency be best altered from 60 secs?

Quick mention: why the flat lining, which incidentally I saw along with the floating point errors I have experienced?

[renluop]

Found in System Event  Log errors. I know many of you are Linuxites or close kin! , but do they suggest anything?

Code: [Select]

This morning at start

Faulting application name: dslstats.exe, version: 5.8.4.0, time stamp: 0x00000000
Faulting module name: dslstats.exe, version: 5.8.4.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000f8a7
Faulting process id: 0x1670
Faulting application start time: 0x01d2034cd052ba7f
Faulting application path: C:\Users\....\AppData\Local\dslstats\dslstats32W-5.8.4\dslstats.exe
Faulting module path: C:\Users\....\AppData\Local\dslstats\dslstats32W-5.8.4\dslstats.exe
Report Id: 877fe447-faab-4c2f-a3f9-2bd4bed1931e
Faulting package full name:
Faulting package-relative application ID:
Faulting application name: dslstats.exe, version: 5.8.4.0, time stamp: 0x00000000
Faulting module name: dslstats.exe, version: 5.8.4.0, time stamp: 0x00000000
Exception code: 0xc0000409
Fault offset: 0x0006357e
Faulting process id: 0x1670
Faulting application start time: 0x01d2034cd052ba7f
Faulting application path: C:\Users\....\AppData\Local\dslstats\dslstats32W-5.8.4\dslstats.exe
Faulting module path: C:\Users\....\AppData\Local\dslstats\dslstats32W-5.8.4\dslstats.exe
Report Id: 5a5e0f7c-69f1-4a1a-98ef-ae1223f4e3ce
Faulting package full name:
Faulting package-relative application ID:
 
This afternoon after stopped working
Faulting application name: dslstats.exe, version: 5.8.4.0, time stamp: 0x00000000
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0xff850000
Faulting process id: 0x394
Faulting application start time: 0x01d202e4adec3a7d
Faulting application path: C:\Users\....\AppData\Local\dslstats\dslstats32W-5.8.4\dslstats.exe
Faulting module path: unknown
Report Id: cae44afa-bb9a-4647-a445-494a3867a956
Faulting package full name:
Faulting package-relative application ID:



[renluop]

I'm going for a complete uninstallation and start over. Have you recommendations how the build up should progress, beyond speed and snrm graphs that is?

[roseway]

There shouldn't be any problem with enabling everything you want in "Items to monitor", but I suggest that you set the sample rate to 60 seconds if a lot of items are enabled. Don't use automatic recording start until you're sure that everything else is working properly. Keep snapshots to a minimum at first, then add more later if you need them.

You did mention recently that your PC randomly reboots itself periodically. I have to say that this shouldn't happen and it implies that something in the PC is seriously misbehaving. It would be good if you could sort this out, as it does make it difficult to diagnose other issues.

[renluop]

The random reboots have not been present of late and sfc /scannow conducted recently showed no corruption.
Did a basic install of 5.8.5 on Friday and no problem has arisen, apart from just before lunch today, when a stack overflow warning, worded like the floating point one was generated. Event viewer had nothing posted for that time.

[ejs]

Maybe try testing your computer's RAM with Windows Memory Diagnostic, or by booting a memtest86 CD or USB.

[renluop]

Memory Diagnostic report is clean.

[roseway]

The 'stack' in this context is an area of memory which is reserved by the operating system for use by a program. Each program thread has its own stack and it's used by the program for local variables (variables which are associated with a particular function and don't exist outside that function) and other temporary purposes. The point here is that a stack overflow is the result of too much space being occupied by local variables, etc., and if the possibility exists of this happening in a program, it's likely that lots of users would be affected by it.

So, the suspicion is that what you are seeing isn't actually a stack overflow, but is stack corruption, caused by memory problems. I can look at the program and make some changes to reduce stack use, but I have little confidence that this will bear fruit.

[renluop]

@roseway
Thanks! I'm sure you have better and much more important things on hand.

@ejs Is memtest86 any superior to WMD? ATM am trying to find way burn bootable ISO of memtest86. Maybe not best done today until hospital sedation wears off.

[ejs]

I've only used memtest86 (and memtest86+ back when that was more up to date than the original memtest86). Severely faulty RAM will show up pretty quickly on any test, so it doesn't really matter which test program is technically superior or has some really long tests which take hours.

[Chrysalis]

memtest86+ is ok, but I have found sometimes it wont pick up unstable ram, so I usually follow up a passed memtest86+ test with a "mem test" windows online memory test, that test tends to be very picky and will fail very easily if ram stability issues.

link here http://hcidesign.com/memtest/

if you have lots of ram and want to speed it up then start multiple instances so e.g. with 16 gig of ram and 4 cpu cores, start 4 of them scanning 4 gig each although you wont be able to scan 100% of ram, it can only scan ram not in use by windows.

[renluop]

@ Chrysalis Thanks for link! Is there any time when "all unused ram" default choice would be better altered?
For now I intend to leave matter stand, as 10 passes with Memtest 86 raised nothing.