XP stop error 0x000000D1 only while using dialup

This BSOD error only occurs while connected to the internet using a dial up modem with the Conexant chipset (will test another one soon):
STOP: 0x000000D1 (0x00000000, 0x00000002, 0x00000008, 0x00000000). Usually the BSOD appears about an hour after continuous use.

At first I thought the modem was at fault and replaced it (same chipset though). Still the problem persisted. Trying to keep it short here but it seemed the CPU was going bad. So a new machine was built with a new power supply, new motherboard, new CPU, and new RAM. Thought the problem was taken care of but then the exact same BSOD occurred after a few days of usage. Is it possible that the incoming power is frying something? Or are there multiple issues present including the CPU and modem? What can I try next? It may be a while before I can post a dump, but I just can't believe the same error occurred on brand new hardware.

 

Hi, thepeel. Welcome to Windows BBS!

Have you tried downloading and installing the latest modem drivers from your modem manufacturer's/vendor's web site?



EDIT: Here's a link to a Microsoft KB article about a similar STOP error. (Three parameters differ, however.)

• Stop 0x000000D1 Error When You Dial a 9 for an Outside Telephone Line to Connect to ISP
  

EDIT #2: Upon closer comparison of the STOP errors, I realized that THREE parameters differ (so they might not be that similar after all). However, the modem still seems suspicious to me since you replaced just about everything else except the modem chipset. (Dunno about other devices such as CD ROM, printer, etc. though).

 

Hi and welcome to the BBS,
Have a look through these articles that are relevant:
http://support.microsoft.com/search...2&ast=3&ast=4&ast=10&ast=8&ast=9&mode=a&adv=1
One or two I checked mentioned VPN and IPSEC, if you have either of those enabled it may be the cause.

Is the modem internal or external (USB or COM port)?

Have you tried updating the drivers? You could get updated drivers from the manufacturer or a set of generic drivers from Conexant.

If the driver update did not work, I would boot into Safe Mode, look for any modem software in Add/Remove Programs and uninstall it (especially any from a previous modem). Go to Phone and Modem Options in Control Panel and remove it there and check it is gone in Device Manager. Boot back into normal mode and install it from the original drivers disk and/or use those the updated drivers I mentioned.

If Windows installed the drivers for it, they may be incomplete or the wrong ones. Make sure you know the model (at least the correct chipset model) when looking for drivers. Read the model number off the card/modem itself.

Matt

 

I have not checked to see if I am using the latest drivers for the modem. It's hard to suspect a driver problem since previously it had been working for at least 6 years. I guess I shouldn't rule it out though. The modem is an internal PCI card. The modem does not dial 9, just a standard 7 digit number.

I looked through the provided knowledge base link. The most interesting links are:
http://support.microsoft.com/kb/916595/en-us - mentions host firewall could be at fault, currently running Blink which was installed pretty recently. I'm not sure if Blink is even as old as the article though.

http://support.microsoft.com/kb/829120/en-us - stop error when establishing TCP/IP session, the session is established for a while though so maybe not

Of course those links are assuming the problem isn't the modem. Life would be a lot simpler if it was. For my own sanity and a fresh start I'm going to install a new modem with a different chipset. Then I'll make sure to load the latest drivers and we'll see what happens. Thanks for the help!

 

NOTE: I edited my post above again.


We have only one BSOD dump analysis expert I know of (cpc2004) who drops in occasionally. Perhaps if you follow the instructions in this link and post a few DebugWiz-generated dump logs for recent BSODs, he might be able to help you pinpoint the cause. (We might notice something too.)

Should be connected to the Internet (which I realize might be difficult in your case) when running DebugWiz so the proper symbols can be retrieved if necessary.

 

If you do install a new modem, be sure to uninstall the software for this current modem (and before shutting down to install the new modem you could uninstall the drivers the way I mentioned. I was going to say, not necessarily in safe mode, but it might a little more advantageous if you did).

Firewall... check what programs the new (Blink) firewall is blocking. A program might be trying to connect to the internet and won't stop trying, eventually it crashes the system (don't discount that it may be malware).

If you can hold out, post a dump log, actually, you should look at several and post any that are repetitive. cpc2004 visits occasionally, so you may not get an instantaneous reply. Being related directly to an internet connection though, one of the rest of us may see something (the tough ones are when the crash is indescriminant ).

Matt

 

It's hard to remember now but I think the firewall was installed for at least a month without problems. Anyway, I just installed the new Motorola based modem:
http://www.zonetusa.com/DispProduct.asp?ProductID=238
I downloaded the drivers from the site and installed them. Probably will be posting a dump from the new modem soon In the meantime, here is a minidump from the old modem:

Opened log file 'c:\debuglog.txt'

Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Documents and Settings\jbpeele\Desktop\downloads\Mini081707-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS\system32\drivers
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp2_gdr.070227-2254
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805533a0
Debug session time: Fri Aug 17 23:00:23.359 2007 (GMT-4)
System Uptime: 0 days 4:23:26.924
Loading Kernel Symbols
........................................................................................................................
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {0, 2, 8, 0}

Probably caused by : asyncmac.sys ( asyncmac!AsyncPPPCompletionRoutine+135 )

Followup: MachineOwner
---------

kd> !analyze -v;r;kv;lmtn;.logclose;q
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000008, value 0 = read operation, 1 = write operation
Arg4: 00000000, address which referenced memory

Debugging Details:
------------------


WRITE_ADDRESS: 00000000

CURRENT_IRQL: 2

FAULTING_IP:
+0
00000000 ?? ???

PROCESS_NAME: System

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

LAST_CONTROL_TRANSFER: from f28f1c2b to 00000000

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
f7a2fcec f28f1c2b 86562d0c f7a2fdc0 00000000 0x0
f7a2fd18 804f054c 00000000 025ba758 00000001 asyncmac!AsyncPPPCompletionRoutine+0x135
f7a2fd48 f6d12515 806d0720 86562d0c f7a2fdc0 nt!IopfCompleteRequest+0xa2
f7a2fd58 f6d12cbe 86562d02 86562934 f7a2fda4 HSFCXTS2!WinAcNtGetNextIrp+0x5d
f7a2fdc0 f6d12dff 005628d8 855ba758 865628d8 HSFCXTS2!WinAcNtStartRead+0x298
f7a2fdd8 f6d10ee9 865628d8 855ba758 86562934 HSFCXTS2!WinAcNtStartOrQueue+0x5d
f7a2fe00 804edfe3 86562820 855ba758 855ba758 HSFCXTS2!WinAcNtDispatchRead+0x5d
f7a2fe10 f791cce4 855ba758 86563730 866b4008 nt!IopfCallDriver+0x31
f7a2fe24 804edfe3 855ba858 855ba758 86507500 Modem!UniRead+0x4a
f7a2fe34 f28f1dbf 866b4008 86507500 00000000 nt!IopfCallDriver+0x31
f7a2fe4c f28f1e4d 86675318 855ba85b 855ba758 asyncmac!AsyncPPPRead+0x12f
f7a2fe64 804f054c 00000000 855ba758 86507500 asyncmac!AsyncWaitMaskCompletionRoutine+0x5b
f7a2fe94 f791870c f7a2febc f791bd95 00000005 nt!IopfCompleteRequest+0xa2
f7a2fe9c f791bd95 00000005 855ba758 00000000 Modem!RemoveReferenceAndCompleteRequest+0x3c
f7a2febc f791cf1f 86562448 f7a2ff24 00000001 Modem!UniRundownShuttledWait+0xa3
f7a2feec f791d7ce 86562402 00000002 00000002 Modem!UniPostProcessShuttledWaits+0x43
f7a2ff54 804f054c 86562390 8581e102 00000002 Modem!UniSniffWaitComplete+0xe6
f7a2ff84 f6d118ff 806d0737 00000000 ffdff000 nt!IopfCompleteRequest+0xa2
f7a2ff98 f6d11992 865628d8 00000000 f6d11902 HSFCXTS2!WinAcNtTryToCompleteCurrent+0x93
f7a2ffd0 80540f7d 86562bf0 865628d8 00000000 HSFCXTS2!WinAcNtDpcCompleteWait+0x2c
f7a2fff4 80540c4a f281ecc0 00000000 00000000 nt!KiRetireDpcList+0x46
f7a2fff8 f281ecc0 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2a
80540c4a 00000000 00000009 bb835675 00000128 0xf281ecc0


STACK_COMMAND: kb

FOLLOWUP_IP:
asyncmac!AsyncPPPCompletionRoutine+135
f28f1c2b 8a4d0f mov cl,byte ptr [ebp+0Fh]

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: asyncmac!AsyncPPPCompletionRoutine+135

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: asyncmac

IMAGE_NAME: asyncmac.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 41107c8e

FAILURE_BUCKET_ID: 0xD1_W_asyncmac!AsyncPPPCompletionRoutine+135

BUCKET_ID: 0xD1_W_asyncmac!AsyncPPPCompletionRoutine+135

Followup: MachineOwner
---------

eax=00000041 ebx=f7a2fd08 ecx=00000041 edx=00000002 esi=f28f1c1e edi=86562d0c
eip=00000000 esp=f7a2fcf0 ebp=f7a2fd18 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
00000000 ?? ???
ChildEBP RetAddr Args to Child
WARNING: Frame IP not in any known module. Following frames may be wrong.
f7a2fcec f28f1c2b 86562d0c f7a2fdc0 00000000 0x0
f7a2fd18 804f054c 00000000 025ba758 00000001 asyncmac!AsyncPPPCompletionRoutine+0x135 (FPO: [Non-Fpo])
f7a2fd48 f6d12515 806d0720 86562d0c f7a2fdc0 nt!IopfCompleteRequest+0xa2 (FPO: [Non-Fpo])
f7a2fd58 f6d12cbe 86562d02 86562934 f7a2fda4 HSFCXTS2!WinAcNtGetNextIrp+0x5d (FPO: [Non-Fpo])
f7a2fdc0 f6d12dff 005628d8 855ba758 865628d8 HSFCXTS2!WinAcNtStartRead+0x298 (FPO: [Non-Fpo])
f7a2fdd8 f6d10ee9 865628d8 855ba758 86562934 HSFCXTS2!WinAcNtStartOrQueue+0x5d (FPO: [Non-Fpo])
f7a2fe00 804edfe3 86562820 855ba758 855ba758 HSFCXTS2!WinAcNtDispatchRead+0x5d (FPO: [Non-Fpo])
f7a2fe10 f791cce4 855ba758 86563730 866b4008 nt!IopfCallDriver+0x31 (FPO: [0,0,0])
f7a2fe24 804edfe3 855ba858 855ba758 86507500 Modem!UniRead+0x4a (FPO: [Non-Fpo])
f7a2fe34 f28f1dbf 866b4008 86507500 00000000 nt!IopfCallDriver+0x31 (FPO: [0,0,0])
f7a2fe4c f28f1e4d 86675318 855ba85b 855ba758 asyncmac!AsyncPPPRead+0x12f (FPO: [Non-Fpo])
f7a2fe64 804f054c 00000000 855ba758 86507500 asyncmac!AsyncWaitMaskCompletionRoutine+0x5b (FPO: [Non-Fpo])
f7a2fe94 f791870c f7a2febc f791bd95 00000005 nt!IopfCompleteRequest+0xa2 (FPO: [Non-Fpo])
f7a2fe9c f791bd95 00000005 855ba758 00000000 Modem!RemoveReferenceAndCompleteRequest+0x3c (FPO: [Non-Fpo])
f7a2febc f791cf1f 86562448 f7a2ff24 00000001 Modem!UniRundownShuttledWait+0xa3 (FPO: [Non-Fpo])
f7a2feec f791d7ce 86562402 00000002 00000002 Modem!UniPostProcessShuttledWaits+0x43 (FPO: [Non-Fpo])
f7a2ff54 804f054c 86562390 8581e102 00000002 Modem!UniSniffWaitComplete+0xe6 (FPO: [Non-Fpo])
f7a2ff84 f6d118ff 806d0737 00000000 ffdff000 nt!IopfCompleteRequest+0xa2 (FPO: [Non-Fpo])
f7a2ff98 f6d11992 865628d8 00000000 f6d11902 HSFCXTS2!WinAcNtTryToCompleteCurrent+0x93 (FPO: [Non-Fpo])
f7a2ffd0 80540f7d 86562bf0 865628d8 00000000 HSFCXTS2!WinAcNtDpcCompleteWait+0x2c (FPO: [Non-Fpo])
start end module name
804d7000 806cd580 nt ntkrnlpa.exe Wed Feb 28 03:38:52 2007 (45E53F9C)
806ce000 806ee380 hal halaacpi.dll Wed Aug 04 01:59:05 2004 (41107B29)
bf000000 bf011580 dxg dxg.sys Wed Aug 04 02:00:51 2004 (41107B93)
bf012000 bf425a80 nv4_disp nv4_disp.dll Wed Aug 04 03:57:11 2004 (411096D7)
bf800000 bf9c2180 win32k win32k.sys Thu Mar 08 08:47:34 2007 (45F013F6)
f0d9b000 f0dc5180 kmixer kmixer.sys Wed Jun 14 04:47:45 2006 (448FCD31)
f25ed000 f2610000 Fastfat Fastfat.SYS Wed Aug 04 02:14:15 2004 (41107EB7)
f2843000 f2883280 HTTP HTTP.sys Thu Mar 16 20:33:09 2006 (441A03C5)
f28f0000 f28f3800 asyncmac asyncmac.sys Wed Aug 04 02:05:02 2004 (41107C8E)
f2c6e000 f2cbf480 srv srv.sys Mon Aug 14 06:34:39 2006 (44E051BF)
f2d0e000 f2d22400 wdmaud wdmaud.sys Wed Jun 14 05:00:44 2006 (448FD03C)
f2d4b000 f2d77400 mrxdav mrxdav.sys Wed Aug 04 02:00:49 2004 (41107B91)
f2e58000 f2e5ae40 mdmxsdk mdmxsdk.sys Wed Mar 17 15:04:10 2004 (4058A12A)
f2eb8000 f2ec6d80 sysaudio sysaudio.sys Wed Aug 04 02:15:54 2004 (41107F1A)
f2f18000 f2f1bb80 Aspi32 Aspi32.SYS Mon Dec 22 21:02:44 1997 (349F1BC4)
f3910000 f3911a80 ParVdm ParVdm.SYS Fri Aug 17 16:49:49 2001 (3B7D836D)
f43bc000 f43bf280 ndisuio ndisuio.sys Wed Aug 04 02:03:10 2004 (41107C1E)
f4448000 f4458000 eeyen eeyen.sys Mon Apr 16 12:43:20 2007 (4623A7A8)
f53d0000 f53e7480 dump_atapi dump_atapi.sys Wed Aug 04 01:59:41 2004 (41107B4D)
f53e8000 f53eae40 ndiskio ndiskio.sys Wed Oct 04 07:53:12 2006 (4523A0A8)
f5410000 f547ea00 mrxsmb mrxsmb.sys Fri May 05 05:41:42 2006 (445B1DD6)
f547f000 f54a9a00 rdbss rdbss.sys Fri May 05 05:47:55 2006 (445B1F4B)
f54aa000 f54cbd00 afd afd.sys Wed Aug 04 02:14:13 2004 (41107EB5)
f54cc000 f54ecf00 ipnat ipnat.sys Wed Sep 29 18:28:36 2004 (415B3714)
f54ed000 f5501000 eeyet eeyet.sys Mon Apr 16 12:43:36 2007 (4623A7B8)
f5501000 f5528c00 netbt netbt.sys Wed Aug 04 02:14:36 2004 (41107ECC)
f5529000 f5580d80 tcpip tcpip.sys Thu Apr 20 07:51:47 2006 (444775D3)
f5581000 f5593400 ipsec ipsec.sys Wed Aug 04 02:14:27 2004 (41107EC3)
f55b4000 f55d8000 eeyeh eeyeh.sys Mon Apr 16 12:43:51 2007 (4623A7C7)
f6728000 f6780e80 update update.sys Mon Apr 23 06:14:23 2007 (462C86FF)
f6821000 f6831e00 psched psched.sys Wed Aug 04 02:04:16 2004 (41107C60)
f6832000 f6848680 ndiswan ndiswan.sys Wed Aug 04 02:14:30 2004 (41107EC6)
f6849000 f685c900 parport parport.sys Wed Aug 04 01:59:04 2004 (41107B28)
f685d000 f6880980 portcls portcls.sys Wed Aug 04 02:15:47 2004 (41107F13)
f6881000 f6c57b00 ALCXWDM ALCXWDM.SYS Thu Nov 23 04:11:35 2006 (456565C7)
f6c58000 f6c7ae80 USBPORT USBPORT.SYS Wed Aug 04 02:08:34 2004 (41107D62)
f6c7b000 f6d22400 HSFCXTS2 HSFCXTS2.sys Thu Jun 17 18:55:36 2004 (40D22168)
f6d23000 f6e21480 HSFDPSP2 HSFDPSP2.sys Thu Jun 17 18:55:00 2004 (40D22144)
f6e22000 f6e44680 ks ks.sys Wed Aug 04 02:15:20 2004 (41107EF8)
f6e45000 f6e7ab80 HSFBS2S2 HSFBS2S2.sys Thu Jun 17 18:56:20 2004 (40D22194)
f6ebd000 f6ed0780 VIDEOPRT VIDEOPRT.SYS Wed Aug 04 02:07:04 2004 (41107D08)
f6ed1000 f70a03c0 nv4_mini nv4_mini.sys Wed Apr 07 22:30:48 2004 (4074B958)
f70a1000 f70a36a0 SilvrLnk SilvrLnk.sys Tue Aug 27 08:40:13 2002 (3D6B732D)
f737b000 f7395580 Mup Mup.sys Wed Aug 04 02:15:20 2004 (41107EF8)
f7396000 f73c2a80 NDIS NDIS.sys Wed Aug 04 02:14:27 2004 (41107EC3)
f73c3000 f744f400 Ntfs Ntfs.sys Fri Feb 09 06:10:31 2007 (45CC56A7)
f7450000 f7466780 KSecDD KSecDD.sys Wed Aug 04 01:59:45 2004 (41107B51)
f7467000 f7478f00 sr sr.sys Wed Aug 04 02:06:22 2004 (41107CDE)
f7479000 f7498780 fltmgr fltmgr.sys Mon Aug 21 05:14:57 2006 (44E97991)
f7499000 f74b0480 atapi atapi.sys Wed Aug 04 01:59:41 2004 (41107B4D)
f74b1000 f74cf880 ftdisk ftdisk.sys Fri Aug 17 16:52:41 2001 (3B7D8419)
f74d0000 f74e0a80 pci pci.sys Wed Aug 04 02:07:45 2004 (41107D31)
f74e1000 f750ed80 ACPI ACPI.sys Wed Aug 04 02:07:35 2004 (41107D27)
f7610000 f7618c00 isapnp isapnp.sys Fri Aug 17 16:58:01 2001 (3B7D8559)
f7620000 f762a500 MountMgr MountMgr.sys Wed Aug 04 01:58:29 2004 (41107B05)
f7630000 f763cc80 VolSnap VolSnap.sys Wed Aug 04 02:00:14 2004 (41107B6E)
f7640000 f7648e00 disk disk.sys Wed Aug 04 01:59:53 2004 (41107B59)
f7650000 f765c200 CLASSPNP CLASSPNP.SYS Wed Aug 04 02:14:26 2004 (41107EC2)
f7660000 f766ae80 uagp35 uagp35.sys Wed Aug 04 02:07:43 2004 (41107D2F)
f76a0000 f76a8d80 HIDCLASS HIDCLASS.SYS Wed Aug 04 02:08:18 2004 (41107D52)
f76b0000 f76bf900 Cdfs Cdfs.SYS Wed Aug 04 02:14:09 2004 (41107EB1)
f7740000 f7748d00 intelppm intelppm.sys Wed Aug 04 01:59:19 2004 (41107B37)
f7750000 f775a380 Imapi Imapi.SYS Wed Aug 04 02:00:12 2004 (41107B6C)
f7760000 f776ac80 NeroCd2k NeroCd2k.sys Mon Apr 16 06:54:24 2001 (3ADACF60)
f7770000 f777c180 cdrom cdrom.sys Wed Aug 04 01:59:52 2004 (41107B58)
f7780000 f778e080 redbook redbook.sys Wed Aug 04 01:59:34 2004 (41107B46)
f7790000 f779eb80 drmk drmk.sys Wed Aug 04 02:07:54 2004 (41107D3A)
f77a0000 f77afd80 serial serial.sys Wed Aug 04 02:15:51 2004 (41107F17)
f77b0000 f77bce00 i8042prt i8042prt.sys Wed Aug 04 02:14:36 2004 (41107ECC)
f77c0000 f77cc880 rasl2tp rasl2tp.sys Wed Aug 04 02:14:21 2004 (41107EBD)
f77d0000 f77da200 raspppoe raspppoe.sys Wed Aug 04 02:05:06 2004 (41107C92)
f77e0000 f77ebd00 raspptp raspptp.sys Wed Aug 04 02:14:26 2004 (41107EC2)
f77f0000 f77f8900 msgpc msgpc.sys Wed Aug 04 02:04:11 2004 (41107C5B)
f7800000 f7809f00 termdd termdd.sys Wed Aug 04 01:58:52 2004 (41107B1C)
f7810000 f7819480 NDProxy NDProxy.SYS Fri Aug 17 16:55:30 2001 (3B7D84C2)
f7830000 f783e100 usbhub usbhub.sys Wed Aug 04 02:08:40 2004 (41107D68)
f7850000 f7858700 netbios netbios.sys Wed Aug 04 02:03:19 2004 (41107C27)
f7870000 f7878880 Fips Fips.SYS Fri Aug 17 21:31:49 2001 (3B7DC585)
f7880000 f7888700 wanarp wanarp.sys Wed Aug 04 02:04:57 2004 (41107C89)
f7890000 f7896200 PCIIDEX PCIIDEX.SYS Wed Aug 04 01:59:40 2004 (41107B4C)
f7898000 f789c900 PartMgr PartMgr.sys Fri Aug 17 21:32:23 2001 (3B7DC5A7)
f7918000 f791f580 Modem Modem.SYS Wed Aug 04 02:08:04 2004 (41107D44)
f7928000 f792e800 usbehci usbehci.sys Wed Aug 04 02:08:34 2004 (41107D62)
f7930000 f7935000 usbuhci usbuhci.sys Wed Aug 04 02:08:34 2004 (41107D62)
f7938000 f793ea00 fetnd5 fetnd5.sys Fri Jul 20 07:40:24 2001 (3B5818A8)
f7940000 f7941000 fdc fdc.sys unavailable (00000000)
f7948000 f794e000 kbdclass kbdclass.sys Wed Aug 04 01:58:32 2004 (41107B08)
f7950000 f7954880 TDI TDI.SYS Wed Aug 04 02:07:47 2004 (41107D33)
f7958000 f795c580 ptilink ptilink.sys Fri Aug 17 16:49:53 2001 (3B7D8371)
f7960000 f7964080 raspti raspti.sys Fri Aug 17 16:55:32 2001 (3B7D84C4)
f7968000 f796da00 mouclass mouclass.sys Wed Aug 04 01:58:32 2004 (41107B08)
f7970000 f7975000 flpydisk flpydisk.sys Wed Aug 04 01:59:24 2004 (41107B3C)
f7980000 f7985200 vga vga.sys Wed Aug 04 02:07:06 2004 (41107D0A)
f7988000 f798ca80 Msfs Msfs.SYS Wed Aug 04 02:00:37 2004 (41107B85)
f7990000 f7997880 Npfs Npfs.SYS Wed Aug 04 02:00:38 2004 (41107B86)
f79a0000 f79a6180 HIDPARSE HIDPARSE.SYS Wed Aug 04 02:08:15 2004 (41107D4F)
f79a8000 f79ac500 watchdog watchdog.sys Wed Aug 04 02:07:32 2004 (41107D24)
f79f0000 f79f4f00 RET55 RET55.sys Sat Apr 14 02:38:31 2007 (462076E7)
f7a10000 f7a16780 USBSTOR USBSTOR.SYS Wed Aug 04 02:08:44 2004 (41107D6C)
f7a20000 f7a23000 BOOTVID BOOTVID.dll Fri Aug 17 16:49:09 2001 (3B7D8345)
f7a98000 f7a9a580 hidusb hidusb.sys Fri Aug 17 17:02:16 2001 (3B7D8658)
f7a9c000 f7a9ef80 mouhid mouhid.sys Fri Aug 17 16:47:57 2001 (3B7D82FD)
f7aac000 f7aae900 Dxapi Dxapi.sys Fri Aug 17 16:53:19 2001 (3B7D843F)
f7abc000 f7abfc80 serenum serenum.sys Wed Aug 04 01:59:06 2004 (41107B2A)
f7ac0000 f7ac2580 ndistapi ndistapi.sys Fri Aug 17 16:55:29 2001 (3B7D84C1)
f7ad0000 f7ad3c80 mssmbios mssmbios.sys Wed Aug 04 02:07:47 2004 (41107D33)
f7b0c000 f7b0e280 rasacd rasacd.sys Fri Aug 17 16:55:39 2001 (3B7D84CB)
f7b10000 f7b11b80 kdcom kdcom.dll Fri Aug 17 16:49:10 2001 (3B7D8346)
f7b12000 f7b13100 WMILIB WMILIB.SYS Fri Aug 17 17:07:23 2001 (3B7D878B)
f7b14000 f7b15500 viaide viaide.sys Wed Aug 04 01:59:42 2004 (41107B4E)
f7b2e000 f7b2f100 swenum swenum.sys Wed Aug 04 01:58:41 2004 (41107B11)
f7b34000 f7b35280 USBD USBD.SYS Fri Aug 17 17:02:58 2001 (3B7D8682)
f7b36000 f7b37f00 Fs_Rec Fs_Rec.SYS Fri Aug 17 16:49:37 2001 (3B7D8361)
f7b38000 f7b39080 Beep Beep.SYS Fri Aug 17 16:47:33 2001 (3B7D82E5)
f7b3a000 f7b3b080 mnmdd mnmdd.SYS Fri Aug 17 16:57:28 2001 (3B7D8538)
f7b3c000 f7b3d080 RDPCDD RDPCDD.sys Fri Aug 17 16:46:56 2001 (3B7D82C0)
f7b40000 f7b41100 dump_WMILIB dump_WMILIB.SYS Fri Aug 17 17:07:23 2001 (3B7D878B)
f7bd8000 f7bd8d00 pciide pciide.sys Fri Aug 17 16:51:49 2001 (3B7D83E5)
f7cc0000 f7cc0b80 Null Null.SYS Fri Aug 17 16:47:39 2001 (3B7D82EB)
f7cfc000 f7cfcd00 dxgthk dxgthk.sys Fri Aug 17 16:53:12 2001 (3B7D8438)
f7d07000 f7d07c00 audstub audstub.sys Fri Aug 17 16:59:40 2001 (3B7D85BC)

Unloaded modules:
f25c2000 f25ed000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f25c2000 f25ed000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f2610000 f263b000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f2cc0000 f2ceb000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f3801000 f3802000 drmkaud.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f6781000 f678e000 DMusic.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f2ceb000 f2d0e000 aec.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f2e88000 f2e96000 swmidi.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f3908000 f390a000 splitter.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7860000 f7869000 processr.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7978000 f797d000 Cdaudio.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f7b08000 f7b0b000 Sfloppy.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f7920000 f7925000 usbohci.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
Closing open log file c:\debuglog.txt

 

Thanks for your follow-up details!

While I don't claim to be an expert regarding dump analysis, according to this 4-page article, Network World: "How to solve Windows system crashes in minutes" (specifically the last paragraph of page 3 and all of page 4), it appears your problem might be caused by (or related to) asyncmac.sys.

• File.net Information About asyncmac.sys:
  

Therefore, your replacement of your modem might solve your issue. (fingers crossed)

 

I will add what I can as well.

It is another D1 crash. It was from a system/MS file (mailman's quote, asyncmac.sys), not a modem (hardware) driver.

The link I posted to the KB search seemed to identify the how internet connection is made. The ones I pinpointed were high security level. "Remote Access serial network driver" may be along the same lines.

I suggest running antispyware, if you only have one, try Spybot and AdAware.

Have you installed any programs yourself that may want to modify the connection?

Matt

 

Seeing how this is a computer built from scratch with all the latest patches, I just really doubt spyware is involved in any way. The only software I can think of that would effect anything regarding the internet connection would be Blink. It's hard for me to believe Blink would be causing such serious problems though. Sadly, the new modem has also crashed and I will be posting a mini-dump soon. I didn't realize the full dump was 1 gig. I've been having my Dad transfer the files to me which is why this is taking so long. I hope you guys don't lose interest

 

I'm coming to this late, but I can't see anywhere where you describe exactly when the internet connection fails and what you are doing when it fails.

• Does the problem happen at the same time, or is it random? For example, is it usually a few minutes after you connect or can it vary from as soon as you connect to many tens of minutes after you connect?
• Does the connection fail when you do something in particular - download software, connect to a particular service?
• Does your connection slow before the connection is lost?

Also modem connections are very susceptible to telephone line problems - are you connecting via an extension, or going directly into a wall socket with the cable supplied with the modem.

Lastly, have you discussed this problem with your ISP? There may be information in their logs that would help you diagnose the problem.

 

When Blink was installed it should have disabled Windows Firewall. Just check that Windows firewall is disabled.

I expect you still have the installation file/s for Blink. Me, I would just uninstall it and try going back to Windows firewall as a test. It should be just a matter of reinstalling it if it does not seem to be the cause. If it appears to be the cause, I would expect that it has closed ports that one or more programs are using to access the internet (why I wonder about spyware).

Patches do not stop spyware. When you see a popup that says XYZ program or ActiveX is requesting to be installed, if you don't know what that program/ActiveX is and click OK, you have just installed it. Some antispyware systems classify "junk" programs differently to others. That "fantastic" shopping program that you installed may be sending information about your buying habits back to it's server, although some antispyware systems just classify it as a normal program (particularly if you have agreed to any terms and conditions during it's installation...you may have agreed to it spying on you). Edit: This is just an example about spyware. The Blink firewall may be doing it's well and blocking internet ports, but that may be the cause of the problem. I like Zonealarm if you want to be told what programs are trying to access the internet. If you block programs, don't expect that they will just stop trying.

If you are switching between modems, check if they have an uninstaller in Add/Remove Programs. Also, go to Control Panel -> Phone and Modem options, highlight the modem and remove/uninstall it before you shutdown and physically disconnect it.

Matt

 

The problem is random but seems to take at least one hour before a BSOD occurs. I'm not doing anything in particular that causes the problem that I can tell. Downloading software, browsing the web, or just being connected doing nothing (I think I have done that before) all crash around after an hour. I don't think I have witnessed the connection slowing before crash, but I guess it's possible.

Agreed that modems are very sensitive. I am using an extension cord for the modem. But before recently I've also done this for 6 years with no problem. Also, the phone line is being routed through the surge protector.

I will check about Blink very carefully. I have removed the previous modem and its drivers completely. I know that spyware can be installed with the click of a mouse, but my father only visits sites that are safe. And supposedly Blink is supposed to protect against spyware as well...

Here's the latest crash dump with the new modem installed:

Opened log file 'c:\debuglog.txt'

Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Documents and Settings\jbpeele\Desktop\downloads\Mini090607-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS\system32\drivers
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp2_gdr.070227-2254
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805533a0
Debug session time: Thu Sep 6 22:48:14.500 2007 (GMT-4)
System Uptime: 0 days 1:21:05.063
Loading Kernel Symbols
......................................................................................................................
Loading User Symbols
Loading unloaded module list
...............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {0, 2, 8, 0}

Unable to load image smserial.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for smserial.sys
*** ERROR: Module load completed but symbols could not be loaded for smserial.sys
Probably caused by : asyncmac.sys ( asyncmac!AsyncPPPCompletionRoutine+135 )

Followup: MachineOwner
---------

kd> !analyze -v;r;kv;lmtn;.logclose;q
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000008, value 0 = read operation, 1 = write operation
Arg4: 00000000, address which referenced memory

Debugging Details:
------------------


WRITE_ADDRESS: 00000000

CURRENT_IRQL: 2

FAULTING_IP:
+0
00000000 ?? ???

PROCESS_NAME: blinkrm.exe

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

LAST_CONTROL_TRANSFER: from f2ab7c2b to 00000000

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
f7a2fcf4 f2ab7c2b f703acf8 f7a2fd88 00000000 0x0
f7a2fd20 804f054c 00000000 02719b90 00000070 asyncmac!AsyncPPPCompletionRoutine+0x135
f7a2fd50 f6f66364 00000000 f703acf8 f7a2fd88 nt!IopfCompleteRequest+0xa2
f7a2fd60 f6f64c25 85719b90 00000000 8673c3c8 smserial+0x8364
f7a2fd88 f6f66158 8666b040 8666b7f1 8666b040 smserial+0x6c25
f7a2fda4 f6f64c8e 0273c3c8 8666b040 8673c3d0 smserial+0x8158
f7a2fdc4 804edfe3 8666b040 85719b90 85719b90 smserial+0x6c8e
f7a2fdd4 f791cce4 85719b90 866b0340 856e0318 nt!IopfCallDriver+0x31
f7a2fde8 804edfe3 85719c48 85719b90 865668d0 Modem!UniRead+0x4a
f7a2fdf8 f2ab7dbf 856e0318 865668d0 00000000 nt!IopfCallDriver+0x31
f7a2fe10 f2ab7e4d 86443aa0 85719c4b 85719b90 asyncmac!AsyncPPPRead+0x12f
f7a2fe28 804f054c 00000000 85719b90 865668d0 asyncmac!AsyncWaitMaskCompletionRoutine+0x5b
f7a2fe58 f791870c f7a2fe80 f791bd95 00000005 nt!IopfCompleteRequest+0xa2
f7a2fe60 f791bd95 00000005 85719b90 00000000 Modem!RemoveReferenceAndCompleteRequest+0x3c
f7a2fe80 f791cf1f 86686798 f7a2fee8 00000001 Modem!UniRundownShuttledWait+0xa3
f7a2feb0 f791d7ce 86686702 00000002 00000002 Modem!UniPostProcessShuttledWaits+0x43
f7a2ff18 804f054c 866866e0 86537102 00000002 Modem!UniSniffWaitComplete+0xe6
f7a2ff48 f6f66364 8666b8a8 86537130 f7a2ff84 nt!IopfCompleteRequest+0xa2
f7a2ff58 f6f60b4a 86537130 00000000 f70435e0 smserial+0x8364
f7a2ff84 f6ffbf9d f70435e0 8666b040 00000004 smserial+0x2b4a
f7a2ffa4 f6f7bce6 86286000 0000000b 0000007f smserial+0x9df9d
f7a2ffb8 f6f6338a 86286000 f6f63036 0000000a smserial+0x1dce6
f7a2ffd0 80540f7d f703af94 f703af28 8666b040 smserial+0x538a
f7a2fff4 80540c4a f2864d44 00000000 00000000 nt!KiRetireDpcList+0x46
f7a2fff8 f2864d44 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2a
80540c4a 00000000 00000009 bb835675 00000128 0xf2864d44


STACK_COMMAND: kb

FOLLOWUP_IP:
asyncmac!AsyncPPPCompletionRoutine+135
f2ab7c2b 8a4d0f mov cl,byte ptr [ebp+0Fh]

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: asyncmac!AsyncPPPCompletionRoutine+135

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: asyncmac

IMAGE_NAME: asyncmac.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 41107c8e

FAILURE_BUCKET_ID: 0xD1_W_asyncmac!AsyncPPPCompletionRoutine+135

BUCKET_ID: 0xD1_W_asyncmac!AsyncPPPCompletionRoutine+135

Followup: MachineOwner
---------

eax=00000041 ebx=f7a2fd10 ecx=00000041 edx=00000002 esi=f2ab7c1e edi=f703acf8
eip=00000000 esp=f7a2fcf8 ebp=f7a2fd20 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
00000000 ?? ???
ChildEBP RetAddr Args to Child
WARNING: Frame IP not in any known module. Following frames may be wrong.
f7a2fcf4 f2ab7c2b f703acf8 f7a2fd88 00000000 0x0
f7a2fd20 804f054c 00000000 02719b90 00000070 asyncmac!AsyncPPPCompletionRoutine+0x135 (FPO: [Non-Fpo])
f7a2fd50 f6f66364 00000000 f703acf8 f7a2fd88 nt!IopfCompleteRequest+0xa2 (FPO: [Non-Fpo])
f7a2fd60 f6f64c25 85719b90 00000000 8673c3c8 smserial+0x8364
f7a2fd88 f6f66158 8666b040 8666b7f1 8666b040 smserial+0x6c25
f7a2fda4 f6f64c8e 0273c3c8 8666b040 8673c3d0 smserial+0x8158
f7a2fdc4 804edfe3 8666b040 85719b90 85719b90 smserial+0x6c8e
f7a2fdd4 f791cce4 85719b90 866b0340 856e0318 nt!IopfCallDriver+0x31 (FPO: [0,0,0])
f7a2fde8 804edfe3 85719c48 85719b90 865668d0 Modem!UniRead+0x4a (FPO: [Non-Fpo])
f7a2fdf8 f2ab7dbf 856e0318 865668d0 00000000 nt!IopfCallDriver+0x31 (FPO: [0,0,0])
f7a2fe10 f2ab7e4d 86443aa0 85719c4b 85719b90 asyncmac!AsyncPPPRead+0x12f (FPO: [Non-Fpo])
f7a2fe28 804f054c 00000000 85719b90 865668d0 asyncmac!AsyncWaitMaskCompletionRoutine+0x5b (FPO: [Non-Fpo])
f7a2fe58 f791870c f7a2fe80 f791bd95 00000005 nt!IopfCompleteRequest+0xa2 (FPO: [Non-Fpo])
f7a2fe60 f791bd95 00000005 85719b90 00000000 Modem!RemoveReferenceAndCompleteRequest+0x3c (FPO: [Non-Fpo])
f7a2fe80 f791cf1f 86686798 f7a2fee8 00000001 Modem!UniRundownShuttledWait+0xa3 (FPO: [Non-Fpo])
f7a2feb0 f791d7ce 86686702 00000002 00000002 Modem!UniPostProcessShuttledWaits+0x43 (FPO: [Non-Fpo])
f7a2ff18 804f054c 866866e0 86537102 00000002 Modem!UniSniffWaitComplete+0xe6 (FPO: [Non-Fpo])
f7a2ff48 f6f66364 8666b8a8 86537130 f7a2ff84 nt!IopfCompleteRequest+0xa2 (FPO: [Non-Fpo])
f7a2ff58 f6f60b4a 86537130 00000000 f70435e0 smserial+0x8364
f7a2ff84 f6ffbf9d f70435e0 8666b040 00000004 smserial+0x2b4a
start end module name
804d7000 806cd580 nt ntkrnlpa.exe Wed Feb 28 03:38:52 2007 (45E53F9C)
806ce000 806ee380 hal halaacpi.dll Wed Aug 04 01:59:05 2004 (41107B29)
bf000000 bf011580 dxg dxg.sys Wed Aug 04 02:00:51 2004 (41107B93)
bf012000 bf425a80 nv4_disp nv4_disp.dll Wed Aug 04 03:57:11 2004 (411096D7)
bf800000 bf9c2180 win32k win32k.sys Thu Mar 08 08:47:34 2007 (45F013F6)
f2ab6000 f2ab9800 asyncmac asyncmac.sys Wed Aug 04 02:05:02 2004 (41107C8E)
f2ac6000 f2b06280 HTTP HTTP.sys Thu Mar 16 20:33:09 2006 (441A03C5)
f2eef000 f2f03400 wdmaud wdmaud.sys Wed Jun 14 05:00:44 2006 (448FD03C)
f2fcc000 f301d480 srv srv.sys Mon Aug 14 06:34:39 2006 (44E051BF)
f3046000 f3072400 mrxdav mrxdav.sys Wed Aug 04 02:00:49 2004 (41107B91)
f30d7000 f30dab80 Aspi32 Aspi32.SYS Mon Dec 22 21:02:44 1997 (349F1BC4)
f3b63000 f3b64a80 ParVdm ParVdm.SYS Fri Aug 17 16:49:49 2001 (3B7D836D)
f3deb000 f3e0e000 Fastfat Fastfat.SYS Wed Aug 04 02:14:15 2004 (41107EB7)
f465a000 f465d280 ndisuio ndisuio.sys Wed Aug 04 02:03:10 2004 (41107C1E)
f5596000 f55a4d80 sysaudio sysaudio.sys Wed Aug 04 02:15:54 2004 (41107F1A)
f564e000 f5665480 dump_atapi dump_atapi.sys Wed Aug 04 01:59:41 2004 (41107B4D)
f568e000 f56fca00 mrxsmb mrxsmb.sys Fri May 05 05:41:42 2006 (445B1DD6)
f56fd000 f5727a00 rdbss rdbss.sys Fri May 05 05:47:55 2006 (445B1F4B)
f5728000 f5749d00 afd afd.sys Wed Aug 04 02:14:13 2004 (41107EB5)
f574a000 f576af00 ipnat ipnat.sys Wed Sep 29 18:28:36 2004 (415B3714)
f576b000 f577f000 eeyet eeyet.sys Mon Apr 16 12:43:36 2007 (4623A7B8)
f577f000 f57a6c00 netbt netbt.sys Wed Aug 04 02:14:36 2004 (41107ECC)
f57a7000 f57fed80 tcpip tcpip.sys Thu Apr 20 07:51:47 2006 (444775D3)
f57ff000 f5811400 ipsec ipsec.sys Wed Aug 04 02:14:27 2004 (41107EC3)
f5832000 f5856000 eeyeh eeyeh.sys Mon Apr 16 12:43:51 2007 (4623A7C7)
f586e000 f5870900 Dxapi Dxapi.sys Fri Aug 17 16:53:19 2001 (3B7D843F)
f698a000 f698ce40 ndiskio ndiskio.sys Wed Oct 04 07:53:12 2006 (4523A0A8)
f6992000 f69946a0 SilvrLnk SilvrLnk.sys Tue Aug 27 08:40:13 2002 (3D6B732D)
f6996000 f6998f80 mouhid mouhid.sys Fri Aug 17 16:47:57 2001 (3B7D82FD)
f699a000 f699c580 hidusb hidusb.sys Fri Aug 17 17:02:16 2001 (3B7D8658)
f69a6000 f69fee80 update update.sys Mon Apr 23 06:14:23 2007 (462C86FF)
f6a9f000 f6aafe00 psched psched.sys Wed Aug 04 02:04:16 2004 (41107C60)
f6ab0000 f6ac6680 ndiswan ndiswan.sys Wed Aug 04 02:14:30 2004 (41107EC6)
f6ac7000 f6ada900 parport parport.sys Wed Aug 04 01:59:04 2004 (41107B28)
f6adb000 f6afe980 portcls portcls.sys Wed Aug 04 02:15:47 2004 (41107F13)
f6aff000 f6ed5b00 ALCXWDM ALCXWDM.SYS Thu Nov 23 04:11:35 2006 (456565C7)
f6ed6000 f6ef8680 ks ks.sys Wed Aug 04 02:15:20 2004 (41107EF8)
f6f3b000 f6f5de80 USBPORT USBPORT.SYS Wed Aug 04 02:08:34 2004 (41107D62)
f6f5e000 f704d500 smserial smserial.sys Mon Jul 17 07:28:25 2006 (44BB7459)
f704e000 f7061780 VIDEOPRT VIDEOPRT.SYS Wed Aug 04 02:07:04 2004 (41107D08)
f7062000 f72313c0 nv4_mini nv4_mini.sys Wed Apr 07 22:30:48 2004 (4074B958)
f724a000 f724c280 rasacd rasacd.sys Fri Aug 17 16:55:39 2001 (3B7D84CB)
f737b000 f7395580 Mup Mup.sys Wed Aug 04 02:15:20 2004 (41107EF8)
f7396000 f73c2a80 NDIS NDIS.sys Wed Aug 04 02:14:27 2004 (41107EC3)
f73c3000 f744f400 Ntfs Ntfs.sys Fri Feb 09 06:10:31 2007 (45CC56A7)
f7450000 f7466780 KSecDD KSecDD.sys Wed Aug 04 01:59:45 2004 (41107B51)
f7467000 f7478f00 sr sr.sys Wed Aug 04 02:06:22 2004 (41107CDE)
f7479000 f7498780 fltmgr fltmgr.sys Mon Aug 21 05:14:57 2006 (44E97991)
f7499000 f74b0480 atapi atapi.sys Wed Aug 04 01:59:41 2004 (41107B4D)
f74b1000 f74cf880 ftdisk ftdisk.sys Fri Aug 17 16:52:41 2001 (3B7D8419)
f74d0000 f74e0a80 pci pci.sys Wed Aug 04 02:07:45 2004 (41107D31)
f74e1000 f750ed80 ACPI ACPI.sys Wed Aug 04 02:07:35 2004 (41107D27)
f7610000 f7618c00 isapnp isapnp.sys Fri Aug 17 16:58:01 2001 (3B7D8559)
f7620000 f762a500 MountMgr MountMgr.sys Wed Aug 04 01:58:29 2004 (41107B05)
f7630000 f763cc80 VolSnap VolSnap.sys Wed Aug 04 02:00:14 2004 (41107B6E)
f7640000 f7648e00 disk disk.sys Wed Aug 04 01:59:53 2004 (41107B59)
f7650000 f765c200 CLASSPNP CLASSPNP.SYS Wed Aug 04 02:14:26 2004 (41107EC2)
f7660000 f766ae80 uagp35 uagp35.sys Wed Aug 04 02:07:43 2004 (41107D2F)
f7690000 f7698880 Fips Fips.SYS Fri Aug 17 21:31:49 2001 (3B7DC585)
f76a0000 f76a8700 wanarp wanarp.sys Wed Aug 04 02:04:57 2004 (41107C89)
f76c0000 f76c8d80 HIDCLASS HIDCLASS.SYS Wed Aug 04 02:08:18 2004 (41107D52)
f76d0000 f76df900 Cdfs Cdfs.SYS Wed Aug 04 02:14:09 2004 (41107EB1)
f7720000 f7728d00 intelppm intelppm.sys Wed Aug 04 01:59:19 2004 (41107B37)
f7730000 f773a380 Imapi Imapi.SYS Wed Aug 04 02:00:12 2004 (41107B6C)
f7740000 f774ac80 NeroCd2k NeroCd2k.sys Mon Apr 16 06:54:24 2001 (3ADACF60)
f7750000 f775c180 cdrom cdrom.sys Wed Aug 04 01:59:52 2004 (41107B58)
f7760000 f776e080 redbook redbook.sys Wed Aug 04 01:59:34 2004 (41107B46)
f7770000 f777eb80 drmk drmk.sys Wed Aug 04 02:07:54 2004 (41107D3A)
f7780000 f778fd80 serial serial.sys Wed Aug 04 02:15:51 2004 (41107F17)
f7790000 f779ce00 i8042prt i8042prt.sys Wed Aug 04 02:14:36 2004 (41107ECC)
f77a0000 f77ac880 rasl2tp rasl2tp.sys Wed Aug 04 02:14:21 2004 (41107EBD)
f77b0000 f77ba200 raspppoe raspppoe.sys Wed Aug 04 02:05:06 2004 (41107C92)
f77c0000 f77cbd00 raspptp raspptp.sys Wed Aug 04 02:14:26 2004 (41107EC2)
f77d0000 f77d8900 msgpc msgpc.sys Wed Aug 04 02:04:11 2004 (41107C5B)
f77f0000 f77f9f00 termdd termdd.sys Wed Aug 04 01:58:52 2004 (41107B1C)
f7810000 f7819480 NDProxy NDProxy.SYS Fri Aug 17 16:55:30 2001 (3B7D84C2)
f7830000 f783e100 usbhub usbhub.sys Wed Aug 04 02:08:40 2004 (41107D68)
f7840000 f7850000 eeyen eeyen.sys Mon Apr 16 12:43:20 2007 (4623A7A8)
f7870000 f7878700 netbios netbios.sys Wed Aug 04 02:03:19 2004 (41107C27)
f7890000 f7896200 PCIIDEX PCIIDEX.SYS Wed Aug 04 01:59:40 2004 (41107B4C)
f7898000 f789c900 PartMgr PartMgr.sys Fri Aug 17 21:32:23 2001 (3B7DC5A7)
f7918000 f791f580 Modem Modem.SYS Wed Aug 04 02:08:04 2004 (41107D44)
f7920000 f7924280 usbohci usbohci.sys Wed Aug 04 02:08:34 2004 (41107D62)
f7928000 f792e800 usbehci usbehci.sys Wed Aug 04 02:08:34 2004 (41107D62)
f7930000 f7935000 usbuhci usbuhci.sys Wed Aug 04 02:08:34 2004 (41107D62)
f7938000 f793ea00 fetnd5 fetnd5.sys Fri Jul 20 07:40:24 2001 (3B5818A8)
f7940000 f7941000 fdc fdc.sys unavailable (00000000)
f7948000 f794e000 kbdclass kbdclass.sys Wed Aug 04 01:58:32 2004 (41107B08)
f7950000 f7954880 TDI TDI.SYS Wed Aug 04 02:07:47 2004 (41107D33)
f7958000 f795c580 ptilink ptilink.sys Fri Aug 17 16:49:53 2001 (3B7D8371)
f7960000 f7964080 raspti raspti.sys Fri Aug 17 16:55:32 2001 (3B7D84C4)
f7968000 f796da00 mouclass mouclass.sys Wed Aug 04 01:58:32 2004 (41107B08)
f7978000 f797d000 flpydisk flpydisk.sys Wed Aug 04 01:59:24 2004 (41107B3C)
f7988000 f798d200 vga vga.sys Wed Aug 04 02:07:06 2004 (41107D0A)
f7990000 f7994a80 Msfs Msfs.SYS Wed Aug 04 02:00:37 2004 (41107B85)
f7998000 f799f880 Npfs Npfs.SYS Wed Aug 04 02:00:38 2004 (41107B86)
f79b0000 f79b6180 HIDPARSE HIDPARSE.SYS Wed Aug 04 02:08:15 2004 (41107D4F)
f79c0000 f79c4500 watchdog watchdog.sys Wed Aug 04 02:07:32 2004 (41107D24)
f7a18000 f7a1cf00 RET55 RET55.sys Sat Apr 14 02:38:31 2007 (462076E7)
f7a20000 f7a23000 BOOTVID BOOTVID.dll Fri Aug 17 16:49:09 2001 (3B7D8345)
f7ab8000 f7abbc80 serenum serenum.sys Wed Aug 04 01:59:06 2004 (41107B2A)
f7abc000 f7abe580 ndistapi ndistapi.sys Fri Aug 17 16:55:29 2001 (3B7D84C1)
f7acc000 f7acfc80 mssmbios mssmbios.sys Wed Aug 04 02:07:47 2004 (41107D33)
f7ad0000 f7ad3f00 MODEMCSA MODEMCSA.sys Fri Aug 17 16:57:37 2001 (3B7D8541)
f7b10000 f7b11b80 kdcom kdcom.dll Fri Aug 17 16:49:10 2001 (3B7D8346)
f7b12000 f7b13100 WMILIB WMILIB.SYS Fri Aug 17 17:07:23 2001 (3B7D878B)
f7b14000 f7b15500 viaide viaide.sys Wed Aug 04 01:59:42 2004 (41107B4E)
f7b30000 f7b31700 RootMdm RootMdm.sys Fri Aug 17 16:57:36 2001 (3B7D8540)
f7b32000 f7b33100 swenum swenum.sys Wed Aug 04 01:58:41 2004 (41107B11)
f7b3a000 f7b3b280 USBD USBD.SYS Fri Aug 17 17:02:58 2001 (3B7D8682)
f7b40000 f7b41f00 Fs_Rec Fs_Rec.SYS Fri Aug 17 16:49:37 2001 (3B7D8361)
f7b42000 f7b43080 Beep Beep.SYS Fri Aug 17 16:47:33 2001 (3B7D82E5)
f7b44000 f7b45080 mnmdd mnmdd.SYS Fri Aug 17 16:57:28 2001 (3B7D8538)
f7b46000 f7b47080 RDPCDD RDPCDD.sys Fri Aug 17 16:46:56 2001 (3B7D82C0)
f7b58000 f7b59100 dump_WMILIB dump_WMILIB.SYS Fri Aug 17 17:07:23 2001 (3B7D878B)
f7bd8000 f7bd8d00 pciide pciide.sys Fri Aug 17 16:51:49 2001 (3B7D83E5)
f7c50000 f7c50d00 dxgthk dxgthk.sys Fri Aug 17 16:53:12 2001 (3B7D8438)
f7cb8000 f7cb8c00 audstub audstub.sys Fri Aug 17 16:59:40 2001 (3B7D85BC)
f7d2f000 f7d2fb80 Null Null.SYS Fri Aug 17 16:47:39 2001 (3B7D82EB)

Unloaded modules:
<SNIP>
Closing open log file c:\debuglog.txt

Here are my next steps gathered from here and elsewhere:
Update BIOS
Try telnetting to 127.0.0.2 (Microsoft KB article)
Check that Windows firewall is disabled
Uninstall Blink
Talk to ISP and check their logs

 

See if disabling the Routing and Remote Access Service has any effect. From what I can find out this is what asyncmac.sys is used for. You're getting exactly the same crash with two different modems, and this makes it likely that asyncmac.sys is the problem. Arg 3's value in the dumps is invalid, and the most times I've seen this it's been software related.

See the following link for some info on asyncmac.sys. http://www.mcse.ms/message2355481.html

Routing and Remote Access Service (RRAS)

 

Interesting development here. Turns out that the Windows Firewall was somehow still turned on! I don't know how Blink didn't disable it upon install. I would have never thought of rechecking it either (thanks mattman). This time the computer stayed online for over two hours which has never happened before. My dad said that a Blink firewall permission dialog popped up (going to check which program wanted to make a TCP connection later) and he clicked accept. As soon as he did that the same blue screen occurred. Sounds more like Blink is responsible based off of this. What do you guys think? I think I am going to uninstall Blink and see if the computer stabilizes.

 

Well Blink has been removed now and my dad was able to stay on the Internet for 4.5 hours. Looks promising. If I don't post here again Blink was at fault. Thanks for all the help!