IRQL_NOT_LESS_OR_EQUAL and Hypaudio.sys Problem

[Rorimusik]

Hi,

every once in a while I am getting the blue screen of death. I have not discovered the problem yet. But when I looked at other forums like @ http://gearslutz.com/board/archive/inde ... 32687.html, users are talking about the same problem.

They are mentioning.......
One screen mentioned a file (hypaudio.sys), another gave a IRQL_NOT_LESS_OR_EQUAL effort.

This is exactly the problem I have. I was running the Win XP verifier application to have my drivers checked and the first thing that pops up is the hypaudio.sys and then a blue screen of death.

I am having 2 UAD, 1 TC Powercore, mLAN is installed. AMD Athlon 64, 3500+.

How would I fix this problem to eliminate the blue screens of death?

Thanks much
Roland

 

[ambrose]

I got this the whole time when my powercore was in my machine. I later found it to be sharing an IRQ with the UAD card, which didn't work well for me. Only by faffing about for hours with cards & different slot positions was i able to resolve the problem. You can see what IRQ the card is on by looking in the windows device manager and using \"view resources by connection\" and clicking on the one that mentions IRQ. Hope that helps.

 

[DAWgEAR]

I used to get this a lot with one UAD-1 in an A7V8X. Then with two in an A7N8X-E Deluxe. Over time, I've upgraded components here and there and now I have 3 UAD-1s in an A8V Deluxe and strangely, I do not get that message anymore. No PoCo at any time.

For the record, they are in PCI slots 1, 2, and 5 and my Lynx AES 16 is in slot 4. The UAD-1s in slots 1 and 5 share an IRQ which is also shared with the AGP slot (Matrox G450) and the third in slot 2 shares an IRQ with Gigabit LAN (Waves APA).

Which version of the UAD-1 driver/plugins are you using?

I swear a lot of my BSOD problems ended when I upgraded my power supply (currently Antec 500W, used to be Antec 380W). Might be coincidence, might not.

 

[Fundy]

That error normally happens when there is an IRQ conflict, shared memory range conflict or there is a device (driver) error. Sometimes it just a case of updating drivers, however sometimes you may find you need to update your BIOS Firmware. Check the driver file is fragmented and corrupted or both, and perhaps using a defragmentation app wouldn't go a miss.

The PSU may also be not giving out enough juice however up till now, I have never had that issue when any of my equipment. Although I did have a Nividia card that went south and gave me a random memory error.

 

[Awesom-o]

I have had this several times in the past on different XP systems, in every case it turned out that the graphics card was faulty. I replaced the cards and all was OK. Also check your system for overheating, as that can also cause hardware errors that generate this stop message. UAD-1's kick out a lot of heat!!!