BSOD when dial up connects

[tweaks_sav]

I've changed modems. Done virus and spyware scans.
Every time I dial up to bellsouth, I get a BSOD.
Windows 2000
Dumps attached.
Thanks!

 

[kirock]

Open device manager and uninstall the ethernet card. Turn -off pc. Pull and clean the copper fingers of the ethernet card. Reinstall, reboot, let windows find new hardware and install drivers for you.
See if that helps.

Cheers.

 

[Ididmyc600]

Open device manager and uninstall the ethernet card. Turn -off pc. Pull and clean the copper fingers of the ethernet card. Reinstall, reboot, let windows find new hardware and install drivers for you.
See if that helps.

Cheers.

Cant quite see how doing that will help. the poster is using a modem to dial up , whether its an ADSL or phone modem I dont know,

My advice is that the Modem driver is faulty, try removing it in device manager and removing it from the machine, power on the PC without the modem in and let windows settle for a few minutes, then power of and replace the modem, the power on and let windows reinstall it,

It could be a deeper issue requiring you to remove all the network related items such as TCP/IP and Client for microsoft network etc but let us know and we will try to help more.

 

[tweaks_sav]

It's a phone modem.

I've tried two different modems with two different drivers and chipset.

 

[Ididmyc600]

It's a phone modem.

I've tried two different modems with two different drivers and chipset.

Ok that clarifies that then, lol , well hang on I'm sure someone who can analyze minidumps should be around shortly, in the meantime, i'm off to learn how to do it..If I learn in time, i'll get back to you

 

[tweaks_sav]

Any more ideas?

 

[Ididmyc600]

Any more ideas?

I'm still learning to read minidumps, but from my initial guess (and yes if i'm wrong someone may correct me) the problem lies with your memory , heres the output from Windbg in case someone wants to correct me.

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP:
+ffffffff811c1317
811c1317 ?? ???

EXCEPTION_PARAMETER1: 00000001

EXCEPTION_PARAMETER2: 4949556c

WRITE_ADDRESS: unable to read from 80481518
unable to read from 804811c8
unable to read from 804810a8
unable to read from 80472de0
unable to read from 804810c0
unable to read from 804811c4
unable to read from 80472de4
unable to read from 80481284
unable to read from 804814b8
4949556c

CUSTOMER_CRASH_COUNT: 5

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

BUGCHECK_STR: 0x1E

PROCESS_NAME: System

EXCEPTION_RECORD: c0000005 -- (.exr ffffffffc0000005)
Cannot read Exception record @ c0000005

TRAP_FRAME: 00000001 -- (.trap 1)
Unable to read trap frame at 00000001

LAST_CONTROL_TRANSFER: from 00000000 to 8042eee4

STACK_TEXT:
ed42a664 00000000 c0000005 811c1317 00000001 nt!KiDispatchException+0x318


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiDispatchException+318
8042eee4 ?? ???

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4344ec59

SYMBOL_NAME: nt!KiDispatchException+318

FAILURE_BUCKET_ID: 0x1E_W_nt!KiDispatchException+318

BUCKET_ID: 0x1E_W_nt!KiDispatchException+318

Followup: MachineOwner


Regards

 

[tweaks_sav]

I did a memtest86+ all night with no erros.
Grrr

 

[pilotmatt]

what program do you use to read the minidumps?

sorry if it is stupid question.

 

[tweaks_sav]

WinDBG, provided by Microsoft.
http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx
</threadjack>