Again??

That dump nearly mirrors the old ones

Are the problems the same?

Are the shutdowns consistent?

Any new symptoms & or behaviors?

Also for the future please change your dump log setting via:
Right click My Computer then click Properties then Advanced then Startup and Recovery | Settings:
Write debugging information: change to Complete memory dump.

well, that only happens once since i´ve reported this, it never shut down again, so i dont know what hapenned that time. No symptoms & or behaviors to register. : /

so ive done what u said...now u want a new debugging report?

If you get a new one with a complete dump pass it along.

The above still goes back to your modem driver

well, this is the best i can do...

Opened log file 'c:\debuglog.txt'

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


Loading Dump File [C:\WINDOWS\Minidump\Mini050905-03.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
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Mon May 9 19:25:32.031 2005 (GMT+1)
System Uptime: 0 days 0:37:27.805
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Loading Kernel Symbols
.................................................. .................................................. .......................................
Loading unloaded module list
..............
Loading User Symbols
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck C2, {7, cd4, 80569a38, 84316930}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

Unable to load image NetMotCM.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for NetMotCM.sys
*** ERROR: Module load completed but symbols could not be loaded for NetMotCM.sys
unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_POOL_HEADER ***
*** ***
************************************************** ***********************
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
unable to get nt!MiSessionPoolStart
unable to get nt!MiSessionPoolEnd
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_POOL_HEADER ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_POOL_TRACKER_BIG_PAGES ***
*** ***
************************************************** ***********************
Cannot get _POOL_TRACKER_BIG_PAGES type size
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** ***********************
Probably caused by : NetMotCM.sys ( NetMotCM+2181 )

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

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

BAD_POOL_CALLER (c2)
The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 00000007, Attempt to free pool which was already freed
Arg2: 00000cd4, (reserved)
Arg3: 80569a38, Memory contents of the pool block
Arg4: 84316930, Address of the block of pool being deallocated

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

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_POOL_HEADER ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_POOL_HEADER ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_POOL_TRACKER_BIG_PAGES ***
*** ***
************************************************** ***********************
Cannot get _POOL_TRACKER_BIG_PAGES type size
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** ***********************

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 3be7ec01

POOL_ADDRESS: 84316930

BUGCHECK_STR: 0xc2_7

CUSTOMER_CRASH_COUNT: 3

DEFAULT_BUCKET_ID: DRIVER_FAULT

LAST_CONTROL_TRANSFER: from 80550fc5 to 805371aa

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
f7978e3c 80550fc5 000000c2 00000007 00000cd4 nt!KeBugCheckEx+0x1b
f7978e8c 805503e3 84316930 00000000 f7978ee0 nt!ExFreePool+0xbf1
f7978e9c f00f4181 84316930 831c439f 831c42c0 nt!ExFreePool+0xf
f7978ee0 f728cee5 831c42c0 833d6d70 84226028 NetMotCM+0x2181
f7978f48 f728db57 84316930 00000000 842267d8 USBPORT!USBPORT_CompleteTransfer+0x373
f7978f78 f728e754 026e6f44 84226028 842260e0 USBPORT!USBPORT_DoneTransfer+0x137
f7978fb0 f728eca8 84226028 80700427 ffdff9c0 USBPORT!USBPORT_FlushDoneTransferList+0x16c
f7978fcc 804dcd22 8422666c 2b667274 00000000 USBPORT!USBPORT_TransferFlushDpc+0x9a
ffdff980 8321a03c f7979000 0002f54e 00000002 nt!KiDispatchInterrupt+0x4c0
84226650 00000000 00000000 00000000 00000000 0x8321a03c


FOLLOWUP_IP:
NetMotCM+2181
f00f4181 ?? ???

SYMBOL_STACK_INDEX: 3

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: NetMotCM+2181

MODULE_NAME: NetMotCM

IMAGE_NAME: NetMotCM.sys

STACK_COMMAND: kb

BUCKET_ID: WRONG_SYMBOLS

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

eax=ffdff13c ebx=00000cd4 ecx=00000000 edx=0c290013 esi=84316928 edi=84316930
eip=805371aa esp=f7978e24 ebp=f7978e3c iopl=0 nv up ei ng nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000286
nt!KeBugCheckEx+0x1b:
805371aa 5d pop ebp
ChildEBP RetAddr Args to Child
WARNING: Stack unwind information not available. Following frames may be wrong.
f7978e3c 80550fc5 000000c2 00000007 00000cd4 nt!KeBugCheckEx+0x1b
f7978e8c 805503e3 84316930 00000000 f7978ee0 nt!ExFreePool+0xbf1
f7978e9c f00f4181 84316930 831c439f 831c42c0 nt!ExFreePool+0xf
f7978ee0 f728cee5 831c42c0 833d6d70 84226028 NetMotCM+0x2181
f7978f48 f728db57 84316930 00000000 842267d8 USBPORT!USBPORT_CompleteTransfer+0x373 (FPO: [Non-Fpo])
f7978f78 f728e754 026e6f44 84226028 842260e0 USBPORT!USBPORT_DoneTransfer+0x137 (FPO: [Non-Fpo])
f7978fb0 f728eca8 84226028 80700427 ffdff9c0 USBPORT!USBPORT_FlushDoneTransferList+0x16c (FPO: [Non-Fpo])
f7978fcc 804dcd22 8422666c 2b667274 00000000 USBPORT!USBPORT_TransferFlushDpc+0x9a (FPO: [Non-Fpo])
ffdff980 8321a03c f7979000 0002f54e 00000002 nt!KiDispatchInterrupt+0x4c0
84226650 00000000 00000000 00000000 00000000 0x8321a03c
start end module name
804d7000 806fe000 nt ntkrnlmp.exe Wed Mar 02 00:57:27 2005 (42250F77)
806fe000 8071ed00 hal halmacpi.dll Wed Aug 04 06:59:09 2004 (41107B2D)
bf800000 bf9c0580 win32k win32k.sys Wed Mar 02 01:06:42 2005 (422511A2)
bf9c1000 bf9d2580 dxg dxg.sys Wed Aug 04 07:00:51 2004 (41107B93)
bf9d3000 bfa0a000 ati2dvag ati2dvag.dll Sun May 16 03:42:03 2004 (40A6D4FB)
bfa0a000 bfa42000 ati2cqag ati2cqag.dll Sun May 16 02:20:30 2004 (40A6C1DE)
bfa42000 bfc42520 ati3duag ati3duag.dll Sun May 16 03:17:10 2004 (40A6CF26)
bfc43000 bfcbf740 ativvaxx ativvaxx.dll Sun May 16 02:42:46 2004 (40A6C716)
bffa0000 bffe5c00 ATMFD ATMFD.DLL Wed Aug 04 08:54:33 2004 (41109639)
eee84000 eeeadf00 kmixer kmixer.sys Wed Aug 04 07:07:46 2004 (41107D32)
ef106000 ef192480 Ntfs Ntfs.SYS Wed Aug 04 07:15:06 2004 (41107EEA)
ef963000 ef9a3100 HTTP HTTP.sys Sat Oct 09 00:48:20 2004 (41672744)
efb61000 efb75400 wdmaud wdmaud.sys Wed Aug 04 07:15:03 2004 (41107EE7)
efe9e000 efeacd80 sysaudio sysaudio.sys Wed Aug 04 07:15:54 2004 (41107F1A)
eff36000 eff88180 srv srv.sys Wed Aug 04 07:14:44 2004 (41107ED4)
effd9000 f0005400 mrxdav mrxdav.sys Wed Aug 04 07:00:49 2004 (41107B91)
f00ee000 f00f0480 osaio osaio.sys Tue Jun 01 04:45:10 2004 (40BBFBC6)
f00f2000 f00f5800 NetMotCM NetMotCM.sys Tue Nov 06 1317 2001 (3BE7EC01)
f052e000 f0543580 irda irda.sys Wed Aug 04 07:00:50 2004 (41107B92)
f0650000 f0653280 ndisuio ndisuio.sys Wed Aug 04 07:03:10 2004 (41107C1E)
f0774000 f078b480 dump_atapi dump_atapi.sys Wed Aug 04 06:59:41 2004 (41107B4D)
f082c000 f089a400 mrxsmb mrxsmb.sys Wed Jan 19 04:26:50 2005 (41EDE18A)
f089b000 f08c5a00 rdbss rdbss.sys Thu Oct 28 02:13:57 2004 (418047D5)
f08c6000 f0918000 SPBBCDrv SPBBCDrv.sys Thu Jul 22 00:08:26 2004 (40FEF76A)
f0918000 f0939d00 afd afd.sys Wed Aug 04 07:14:13 2004 (41107EB5)
f093a000 f0961c00 netbt netbt.sys Wed Aug 04 07:14:36 2004 (41107ECC)
f0962000 f09a8460 symidsco symidsco.sys Fri Mar 04 02:55:44 2005 (4227CE30)
f09a9000 f09d1dc0 SYMFW SYMFW.SYS Tue Apr 05 19:11:07 2005 (4252D4BB)
f09d2000 f09f2f00 ipnat ipnat.sys Wed Sep 29 23:28:36 2004 (415B3714)
f09f3000 f0a32ce0 SYMTDI SYMTDI.SYS Tue Apr 05 19:10:52 2005 (4252D4AC)
f0a5b000 f0ab2d80 tcpip tcpip.sys Mon Mar 14 00:55:05 2005 (4234E0E9)
f0ab3000 f0ac5400 ipsec ipsec.sys Wed Aug 04 07:14:27 2004 (41107EC3)
f0ae6000 f0af6980 NAVENG NAVENG.Sys Tue Mar 15 20:35:44 2005 (42374720)
f0af7000 f0b8fe20 NavEx15 NavEx15.Sys Tue Mar 15 20:51:30 2005 (42374AD2)
f0b90000 f0ba3000 SAVRTPEL SAVRTPEL.SYS Fri Dec 10 20:42:09 2004 (41BA0A21)
f0ba3000 f0bbca80 SYMEVENT SYMEVENT.SYS Tue Oct 19 22:18:08 2004 (41758490)

The problem remains the same.

This time your motherboard's USB drivers were also called out along with the modem.

If we can ID the board we can find chipset drivers. Try this scan:

http://www.belarc.com/free_download.html

What is listed under Main Circuit Board?

so what ever hapened did he get i fixed Or?
i have the exact same problem, down to the pin, and i also have motorolla modem
and so i googled the surfboard 4100/4200 problem and here i am any help would be gratley apreciated. (sorry my english im not from a english speaking country)

Hey,
I've HAD the same problem before with the Motorola Modem.

Everytime I format my computer
I have to go through this issue again (they were resolved by waiting for my computer to crash 3 times, then it went back to normal I dunno why).

Firstly, forget about using the Motorola Installation programs cause they are pathetic.

Secondly, when your computer reboots, quickly turn it of, and turn it on again (wait about 10 seconds), this makes sure that your hard drive does not start off currupt.
Yes, when i just let it reboot, it complete demolished my .nls files in my SystemRoot. So just be careful (i think it has something to do with my crappy hard drive).

Do you get that Error Report thingy? Try using them, they arn't so bad.

Well when i continued to get these errors (i jst fixed it 10 mins ago)

I used the Microsoft Crash Anaylisis help thingo...

Anyways, i found a link to this
http://broadband.motorola.com/consum...QL_Drivers.exe

Yes, My model is a 5100, but this driver IS COMPATIBLE WITH XP and is the latest version and seems to work (or i wouldn't be online).

Download the .exe (really a .zip)
Just extract the drivers into any folder,
Go into Device Manager,
Right Click on the Motorola Modem,
Click Update Driver,
Click No, do not uses Windows Update click next,
Click Advanced search and click Next.
Now Direct the DIR thingy to the folder you put the drivers in.

And it should update the netmotcm.sys file(s).

I hope this works for you.

All the best.

Hey, Update on that last post.

Latest Drivers for the Motorola SB5100 (The Black coloured one)
http://modem.free-driver-download.co...ver-2.4.1.html

Oh, and instead of clicking update your driver.
First Unistall your driver from your system.
Turn off and take out the USB cable from your computer.
Plug it back in and turn on your modem.
Now do exacly the same thing (from the last post).

It doesn't really matter which way you do it.
But i found better internet speed with this method.

All the Best.

Dude. Note sure if your modem has it (it damn well should), but don't use the USB plug. I don't care WHAT they/anyone says, you will always have not only odd problems like this, but slower performance.

So, get an cheap eithernet card if you need one (like $10), and uninstall any program/driver that came with the modem.