I'll try to make this short as best as I can. My old P3 system has an ASUS TUSL2-C mobo, PIII 1.2GHz Tualatain chip running XP Pro with 512 megs of RAM @133 (815E chipset limitation) This has been rock solid for 6 years and does everything we need it to do such as web surfing, Office applications, emailing, and school work. It also keeps my son off my newer rig. :rolleyes: Recently however we have been getting error beeps 2 short repeating high and low with one long beep repeating. According to Award BIOS 2 short and 1 long means video controll failure or video card failure. My son informed me yesterday that it happened when he was trying to boot up and not knowing what to do walked away and 2 hours later he came back and the system had booted to the desktop after BSODing and then the screen going blank. I was able to reboot and the system ran fine. But yesterday the system froze on my son and I was forced to reboot. Only this time the error beeps continued, the monitor remained black, and I have been unable to get into the BIOS. I have done everything I can think of: capacitors are clean and solid, unplugged I/O drives, etc., etc., etc. and evertime I start her up the same thing happens: error beeps, black screen (it is not the monitor or cable), and an inability to get into the BIOS. All fans are working including psu and cpu; there is not a heat or dust issue. If it is my video card the motherboard is designed for 2x/4x the best I can do is 4x/8x. And will I have issues with a 4x/8x card in a designed AGP slot of 2x/4x? But check the error below because I have a question. From Microsoft: Bug Check 0x35: NO_MORE_IRP_STACK_LOCATIONS The NO_MORE_IRP_STACK_LOCATIONS bug check has a value of 0x00000035. This bug check occurs when the IoCallDriver packet has no more stack locations remaining. Cause 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. This will prevent the lower-level driver from accessing its parameters. This is a disastrous situation, since the higher level driver is proceeding as if it has filled in the parameters for the lower level driver (as required). But since there is no stack location for the latter driver, the former has actually written off the end of the packet. This means that some other memory has been corrupted as well. NowI I read minidumps here but this one has me stumped. I have also never read before an error with such descriptive force. I have hit the ceiling of my current knowledge base, thus my inquiry here. Can anyone tell me what exactly MS is describing, why it is a disasterous error and what does it mean some other memory has been corrupted as well? Could it mean my video card memory has been corrupted and that is why I fail to get any monitor screen except black? I need to find the cause or otherwise I fear that what is causing the failures will burn out another vid card or sound card, or RAM. And there is absolutely no way at this time I can afford another PC. If it is a simple need to change video cards so be it, but what is causing the 0x35 and what do the cause descriptors mean? Thanks for taking the time to read this.