When I installed a sound card into a Windows 2000 Sever STD in never got the OS to recognize the sound card. I tried installing three different types of cards. I gave up until SP2 came out. When SP2 came out I quickly downloaded and installed it. Suddenly it recognized and installed my sound card, which is a Sound Blaster Live MP3+ 5.1. No extra software just the drivers and it worked great. Then I installed a software package called MovieDV by Aist. Then BOOM blue screen, and every time after that when it booted up I would be a blue screen. I then booted up in safe mode and uninstalled the MoveDV software. But I would still get a blue screen during the Windows graphical screen just as the blue bar passes the middle of the line. I removed the sound card and then the server would boot all the way to the login screen. Once logged in and it starts to load personal setting when it gets to loading the speaker symbol in the task bar BOOM blue screen. The only way I can get the server to stay up is to go into add/remove programs, Windows Components and then remove Windows Media services and Multimedia. As soon as I add Windows Media services and Multimedia or install the card I get a blue screen. The error is NO_MORE_IRP_STACK_LOCATIONS Begging dump of physical memory. I have the memory dump if this would help. Thank you for your help.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Getting blue screen errors related to audio.
- Thread starter scboyd
- Start date
I have read that McAfee 3.something can cause this. Try removing it if you have it. There are two common blurbs on the error out there. I pasted both below. It seems to me (per the second blurb) that when you install the media player, it tries to call something artifact from the now non-existent sound-card.
If neither of those two things help, I would try digging around in the registry for artifacts relating to the sound card and the Windows Media Services and removing them (after first backing them up!). Another option you could try would be getting another sound card and installing it.
hope this helps.
-------------------------------------
With this code, if you've added a new virus scanner or someone has accessed a shared volume over the network for the first time on the machine, the Server device driver can be at fault. The Server device driver constructs I/O request packets with a slot for every device driver on the path to the disk. Sometimes the number of I/O request packets the Server device driver allocates is insufficient, resulting in this Stop Code. Try increasing the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ LanmanServer\IrpStackSize setting to a number higher than 4 (or whatever it's set to) and see whether the problem goes away.
-------------------------------------
A higher level driver has attempted to call a lower level driver through the IoCallDriver() interface, but there are no more stack locations in the packet, so the lower level driver would not be able to access its parameters, as there are no parameters for it. This is a disastrous situation, since the higher level driver thinks it has filled in the parameters for the lower level driver (something it MUST do before calling the lower level driver); however, since there is no stack location for the latter driver, the former has written off of the end of the packet. This means that some other memory has probably been corrupted.
If neither of those two things help, I would try digging around in the registry for artifacts relating to the sound card and the Windows Media Services and removing them (after first backing them up!). Another option you could try would be getting another sound card and installing it.
hope this helps.
-------------------------------------
With this code, if you've added a new virus scanner or someone has accessed a shared volume over the network for the first time on the machine, the Server device driver can be at fault. The Server device driver constructs I/O request packets with a slot for every device driver on the path to the disk. Sometimes the number of I/O request packets the Server device driver allocates is insufficient, resulting in this Stop Code. Try increasing the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ LanmanServer\IrpStackSize setting to a number higher than 4 (or whatever it's set to) and see whether the problem goes away.
-------------------------------------
A higher level driver has attempted to call a lower level driver through the IoCallDriver() interface, but there are no more stack locations in the packet, so the lower level driver would not be able to access its parameters, as there are no parameters for it. This is a disastrous situation, since the higher level driver thinks it has filled in the parameters for the lower level driver (something it MUST do before calling the lower level driver); however, since there is no stack location for the latter driver, the former has written off of the end of the packet. This means that some other memory has probably been corrupted.
- Status
Similar threads
- Locked
- Question