PDA

View Full Version : Useless Windows Error Messages


classicsoftware
04-18-2004, 10:56 PM
Client on a stable system running Windows XP home edition. Athlon 1.3GHZ with 506MB RAM (some of it,up to 8MB, shared with video or bios shadowed?). It;s a compuke 5315KS ALL service packs and critical updates installed. For full specs: go here (http://h20015.www2.hp.com/en/document.jhtml?reg=&plc=&lc=en&cc=us&cat=prodinfo&prodId=compaqpres93203&docName=c00009490) Use LANtasic as the network operating system. System has developed a series of bizarre error messages incluiding

IRQL_NOT_LESS_THAN_OR_EQUAL

BAD_POLL_CALLER

PAGE_FAULT_IN_NONPAGED_AREA

There is an additional error message, not in my notes, that points to the LANtasic client AFSD.SYS. After searching the MS site it could be:

A) A bad driver
B) Bad RAM
C) Other bad hardware

This provides little guidance on where to begin to troubleshoot this. I guess before I re-install the NIC driver, pull the RAM and test it, ininstall and re-install LANtastic, check the video and sound card drivers I was wondering if any of you have experienced these error messages before?

I have not yet run the spyware software to check for malware or a full virus scan.

The system grinds to a halt with a BSOD and the system has to be restarted from the tower. I will send an e-mail to the maker of LANtastic to see if they have any ideas. The problem only occurs when accessing word processing documents on the server and only in one folder. I checked the hard drive on the server and it is OK. All other computers (WIN9X) can access the files without a problem.

If this is a LANtastic problem, why does it only happen when accesing files in one particular folder? It occcurs in WordPerfect or in Windows Explorer. I think the Lantastic file comes up because it's browsing the network when the error occurs.

Anyway

Paleo Pete
04-19-2004, 02:30 AM
IRQL (http://www.ntsecrets.com/info/problems.htm) info...and Here (http://www.aumha.org/win5/kbestop.htm) for the IRQL message.

0x000000C2: BAD_POOL_CALLER

A kernel-mode process or driver incorrectly attempted to perform memory operations. Typically, a faulty driver or buggy software causes this.

Didn't see the third one, and it's about time to go get horizontal, but it might be on that 2nd site, or hit Google (http://www.google.com)...and copy the exact error message into the search.

Strangely enough, first 3 pages of results for the first error message didn't drag out a single M$ link...hmmmm...