Ok i'm getting BSOD with a reference to NDISYS driver. Im pretty sure thats a network card related driver.

So my first move was to update the driver for the network card we have. The errors continued. Not surprising as we never use the network card as our internet connection is directly through a usb adsl modem. So just in case I updated the drivers for the modem (D-link DSL-200). Didnt help.

Next move was to change to two new (well borrowed, virtually new) sticks of RAM. Still the errors continue.

I dont think its memory related as the errors only occur while using Limewire and BT clients. I use utorrent and that uses like 5mb of memory so that bugs me even more.

I've included last 6 minidumps (attached). Any help would be appreciated.

Specs:
P4 2.8ghz HT
2x512mb generic ram
windows xp sp1
nothing is overclocked.

Hello and welcome to Techspot.

5 minidumps crash at gwausb.sys. This is your usb modem driver, and is most likely the cause of all your BSOD`s.

See HERE for further info.

Regards Howard :wave: :wave:

Thanks for your help. Seems as if the latest drivers for the modem are dodgy and that an earlier version is the most stable. I'll see if I get any more BSODs using these drivers.

Cheers, Zaf

Ok rolled back to earlier drivers. The problem is still continuing, although it is happening less frequently.

Would you be able to check out these latest minidumps to check if the new (older) driver is still causing the crashes.

Thanks again, Zaf

3 of your minidumps crash with memory corruption. They have bugchecks of 7F, and 24.

1 of your minidumps crashes at portcls.sys. Port Class (Class Driver for Port/Miniport Devices). It has a bugcheck of D1.

1 minidump crashes at ntkrnlmp.exe. Windows nt and kernel file. It has a bugcheck of 7F.


0x0000007F: UNEXPECTED_KERNEL_MODE_TRAP

One of three types of problems occurred in kernel-mode: (1) Hardware failures. (2) Software problems. (3) A bound trap (i.e., a condition that the kernel is not allowed to have or intercept). Hardware failures are the most common cause (many dozen KB articles exist for this error referencing specific hardware failures) and, of these, memory hardware failures are the most common.

0x00000024: NTFS_FILE_SYSTEM

A problem occurred within NTFS.SYS, the driver file that allows the system to read and write to NTFS file system drives. There may be a physical problem with the disk, or an Interrupt Request Packet (IRP) may be corrupted. Other common causes include heavy hard drive fragmentation, heavy file I/O, problems with some types of drive-mirroring software, or some antivirus software. I suggest running ChkDsk or ScanDisk as a first step; then disable all file system filters such as virus scanners, firewall software, or backup utilities. Check the file properties of NTFS.SYS to ensure it matches the current OS or SP version. Update all disk, tape backup, CD-ROM, or removable device drivers to the most current versions.

0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL

The system attempted to access pageable memory using a kernel process IRQL that was too high. The most typical cause is a bad device driver (one that uses improper addresses). It can also be caused by caused by faulty or mismatched RAM, or a damaged pagefile.

Go HERE and follow the instructions for testing your ram/hard drive. Instructions for replacing your page file can be found in reply #11 of the above link.

Regards Howard