Winamp5 = autoreboot?

[Vash]

About every other time I start up my machine and load Winamp5, my machine reboots. No explanations, no nothing. Just a black screen and my memory counting.

It looks to me like a memory problem of some sort, though I know for a fact my memory's good. Has anyone else experienced this? I'm hoping that it's either a Windows creep/Winamp5 problem. I reinstalled Winamp3 and this runs without any problems.


Barton 2500+, stock speed
Abit NFS-7 2.0
1 GB Corsair matched 512's
Radeon 9500 soft modded, OC'd to 324/310

[saturnotaku]

Have you unchecked the box in your advanced system properties that says "automatically restart"? Right click on My Computer, properties, advanced (I think) and there's a settings button that adjusts startup and system error settings.

[Vash]

*smack's forehead*


Yup, it was checked. Unchecked it; now at least I'll be able to see the bloody error.

Thanks Sat.

[saturnotaku]

I also assume you're using WA 5.02? It's been working great for me. Even 5.01 was fine. Dunno what's up w/yours. :confused:

If you see this, gimme a holler on AIM tonight.

[Vash]

I'm getting the BSOD now with Firefox. I'm not sure what's going on, but I suspect that if I were to refresh my Windows install and update my drivers, it would go away. That's been on my list of things to do for a while; now's just the time to do it.

I'll try and catch you online tonight.

[saturnotaku]

What exactly is the BSOD it's giving you?

[Vash]

Stop 0x0000000A - IRQ_NOT_LESS_THAN_OR_EQUAL

But it only does it once - if it does happen and I reboot, I don't have any problems.

Man, I feel like an idiot... I've seen this problem before, and I've managed to clear it up before, but I can't remember what I did. Stupid job search sucks my brainpower.

[saturnotaku]

When my P4 system bit it, I was getting these errors left and right. It was a bad memory controller on the motherboard. Switching back to AMD hasn't given me trouble since.

Have you tried gaming and has that given you any trouble?

[Vash]

Yep, no problems whatsoever. Once it starts up and I run stuff w/out errors, then I'm perfectly, 100% stable.

IRQ_NOT_LESS_THAN_OR_EQUAL is the result of a driver failure of some sort - if I remember correctly, it's the result of the driver requesting a resource that's out of it's allotted range. I've fixed these at work, where once I got the faulty driver reinstalled, everything was back to normal.

So it's a driver somewhere that's occassionally giving me trouble. When I get around to a Windows reinstall, that should clear it up.


(Feel a bit better tonight as I landed an interview for an IT Technician position for Friday. *crosses fingers*)

[ALobpreis]

It may be a IRQ conflict. Check in System tools / System information / Hardware resources / IRQ.
If it's a memory problem, check it with www.memtest86.com .

[Vash]

Thanks! I'll give that a spin.