Nullsoft NSV Decoder v1.07 [in_nsv.dll]
 

I am getting repeated errors in this plugin which apparently occur during the transition between clips. They do not occur on the initial load.

They are occasionally accompanied by "windows" error "the memory cannot be read" and reference a null location.

I have verified the ram, the hard disk, reset the paging file and clean installed the latest version of Winamp.

How do we reproduce the problem?
(Full step-by-step method)

Also confirm that you are using no 3rd-party plugins with your clean install of Winamp 5.23, and include basic system specs in reply (Windows OS, cpu, graphics & sound cards, etc).

The system is a Dell Inspiron 1150, 2.4ghz Celeron with 512 mb ram and integrated Intel graphics. Sigmatel sound.

No 3rd party plugins.

I can't reproduce the problem systematically. I can only confirm that it seems to happen in the transition phase between streaming video clips.

I've disabled history tracking and title info, and ran for 35 minutes without error. This is longer than was previously occuring -- but not really exceptional.

I'm thinking it might be corrupt cache, but I would expect this to be cleared on an uninstall and reinstall -- unless it is using Internet Explorer.

It doesn't seem to occur on the desktop, which uses the same router and modem. The cable service is quite capable of handling the bandwidth.

Thanks for your reply.

any streams we can test with?

The one I have been viewing primarily is Demoscene HQ (http://www.shoutcast.com/sbin/tunein...on.pls?id=2190), a "600" kbps bandwidth stream that really comes in at about at up to 1200 kbps; but I've seen it also on "Mystery Science Theater 3000 (http://www.shoutcast.com/sbin/tunein....pls?id=507705), a much lower bandwidth stream, as well as others.

I don't know if some settings changes I've made (disable history tracking, read metadata) have affected this -- I haven't seen the problem in the last 1 hr of viewing time, but will continue to test today on both the desktop and notebook.

Any thoughts on the matter are appreciated. I don't know if this could officially be considered a "bug", but ran across the forum thread when researching the plugin version on Google. If a moderator wants to move it someplace else, I will understand. I also moderate a tech forum.


>>> well as I write this, the problem just happened after only 6 minutes of play on Demoscene HQ;

I'm uploading the error report, for what it's worth.

I see it just contains a lot of useless file verification data. The actual error is an exception violation c00000005

uploading a second, event viewer application log error.

Here is a screenshot; Dr Watson logs are also available if desired.

Well hopefully this is not premature, but I think I can safely say this is not a Winamp bug, but a problem with the laptop's CPU overheating on graphics intensive streams.

It only appears to occur when the CPUs temp is 6-8 degrees (celsius) over critical temp.

The Demoscene HQ stream can cause this in minutes and the error can occur on other streams if I switch and don't allow the CPU to cool first.

I guess I'm in the market for a good laptop cooler.

Thanks to those who took the time to read and consider the issue.

Ahhh! Yeah, that would certainly explain it.

I couldn't for the life of me reproduce the problem, other than the HQ stream kept constantly rebuffering (I suspect they don't have enough bandwidth to serve it at such high quality to too many viewers at once).

By the way, are you the Rollin' Rog from Tech Support Guy forums?
I used to help out there quite frequently a while back (user: The_Egg), mainly in the Security forum (how I loved examining all those HJT logs, hehe). Alas, I haven't had any free time to help out there since Winamp 5 release, but I'm sure I'll be back at some point...

Yes that's me -- and I remember you well as a matter of fact, from the Security forum.

Don't do much of that myself any more, it's a full time specialty keeping up with the rootkits and other very professional malware.

The Demoscene HQ site does some fascinating stuff -- but you are right, there are times when it constantly rebuffers no matter how good your bandwidth is. The same happens on the lower bandwidth main channel.