| | | Morden2004 | | 16 Beiträge |  |
| | schrieb am 08.08.16 um 22:39 Uhr | | This Win 10 system (Windows 10 Version 1511 last update KB3173428 on 7/25/2016) seems to have hung and I can't find any obvious reason except Streamwriter. I only run Streamwriter (ver: 5.4.09.1 build 734) on this computer so I have assumed that it could be Streamwriter. This has happened a few times over the past few months. I have captured the LOG for you as it has a lot of the following strange entries:
2016-08-08 - 15:08:28 - Server - Host "streamwriter.org" could not be resolved
2016-08-08 - 15:08:29 - Saving the 70s - Connecting to listen.shoutcast.com:80…
2016-08-08 - 15:08:29 - Saving the 70s - Host "listen.shoutcast.com" could not be resolved
2016-08-08 - 15:08:29 - Saving the 70s - Connection closed
2016-08-08 - 15:08:33 - Server - Host "streamwriter.org" could not be resolved
2016-08-08 - 15:08:34 - Saving the 70s - Retried 100 times, stopping
2016-08-08 - 15:08:38 - Server - Host "streamwriter.org" could not be resolved
2016-08-08 - 15:08:43 - Server - Host "streamwriter.org" could not be resolved
2016-08-08 - 15:08:48 - Server - Host "streamwriter.org" could not be resolved
2016-08-08 - 15:08:53 - Server - Host "streamwriter.org" could not be resolved
Can you tell if it is Streamwriter that is having issues or should I look elsewhere.
Still a very happy user of Streamwriter - I capture several internet radio programs that I listen to daily!
Regards,
Paul Clarke
clarke.paul@eastlink.ca | | LOG.rar (16,9 KB, 1175 mal heruntergeladen) |
|
|
|
| | | alex | | 2549 Beiträge |  |
| | schrieb am 10.08.16 um 21:24 Uhr | | Hi,
since streamWriter is a regular application that runs only in usermode it should be impossible to crash Windows. The problem must be somewhere else… |
| | | | LG/Best regards, Alex
"Journalism is printing what someone else does not want printed. Everything else is public relations."
- George Orwell
D1734FA178BF7D5AE50CB1AD54442494 |
|
|
| | | Morden2004 | | 16 Beiträge | |
| | schrieb am 12.08.16 um 22:43 Uhr | | Good point. I'm stumped though. What are the connection retrys in the log?
Paul |
|
|
|
| | | alex | | 2549 Beiträge | |
| | schrieb am 13.08.16 um 15:38 Uhr | | Seems like the streamWriter server could not be reached. I was doing some updates in the last days, maybe that was the problem. Should be always reachable now if your internet connection is up |
| | | | LG/Best regards, Alex
"Journalism is printing what someone else does not want printed. Everything else is public relations."
- George Orwell
D1734FA178BF7D5AE50CB1AD54442494 |
|
|
| | | Morden2004 | | 16 Beiträge | |
| | schrieb am 14.08.16 um 20:22 Uhr | | SOLVED:
Alex:
Thanks for the help - I have found the problem. First since I only access this Windows 10 computer via Remote Desktop connections it was impossible to see what was actually causing it to stop or hang. It turns out it was not crashing! The NIC on the motherboard was failing after a few hours/days and therefore the network was disconnected making it 'look' like a hang/crash to the remote connection. That also explains the 'No Connection' error messages from Streamwriter.
I have popped in a separate NIC and all is now well!
Paul |
|
|
|
| | | alex | | 2549 Beiträge | |
| | schrieb am 22.08.16 um 09:57 Uhr | | | Nice to hear you found the source of the problem |
| | | | LG/Best regards, Alex
"Journalism is printing what someone else does not want printed. Everything else is public relations."
- George Orwell
D1734FA178BF7D5AE50CB1AD54442494 |
|
