Again??

  1. #21
    Anny is offline Junior Member

    Re: Turns off

    nooooooooo, the comp went off again twice in less than a minute...what i did wrong?'??. is it possible that i might have a virus in this? or the problem is reaalllyy in the modem or in his drives?? this is really boringgg. ..

    event viewer:

    0000: 53 79 73 74 65 6d 20 45 System E
    0008: 72 72 6f 72 20 20 45 72 rror Er
    0010: 72 6f 72 20 63 6f 64 65 ror code
    0018: 20 30 30 30 30 30 30 63 000000c
    0020: 32 20 20 50 61 72 61 6d 2 Param
    0028: 65 74 65 72 73 20 30 30 eters 00
    0030: 30 30 30 30 30 37 2c 20 000007,
    0038: 30 30 30 30 30 63 64 34 00000cd4
    0040: 2c 20 30 32 30 61 30 30 , 020a00
    0048: 30 36 2c 20 38 34 32 62 06, 842b
    0050: 35 65 33 38 5e38

    ID: 1003
    Source: system error
    Type: error
    File name: faultrep.dll
    category: 102

    the usual.........


  2. #22
    jephree is offline ¨*·.¸ «.·°·..·°·.» ¸.·*¨
    Did you ever go to Windows Update & have your computer scanned?

    However the problem does seems to be that driver. You should try to get the newer one installed.

    I downloaded it & the Read Me states that you need to uninstall the old driver first & then I am unclear if you need to install the new one from a floppy or if it will install from your hard drive. The Read Me refers one back to the modem manual. Do you have this?

  3. #23
    Anny is offline Junior Member
    what i dint understand is why my old pc that is really slow dont give me problems with the modem...it never turned off..and my note book have all this problems...and i installed the modem the same way and they both have the same driver and driver...
    the modem only comes with the cd...but when i clic to update the driver it asks me for the cd---but dont let update by that way...very weird. but th driver that i downloaded to the hard drive dont work?

  4. #24
    jephree is offline ¨*·.¸ «.·°·..·°·.» ¸.·*¨
    Did you uninstall the old driver before trying to install the new?

    Before doing this create a Restore Point at start/all programs/accessories/system tools/system restore

  5. #25
    Anny is offline Junior Member
    hello, i´ve already done what u said. I uninstall the old driver and install that new one.Now lets hope that it nevers hut down again, im going to cross my fingers......i´ll keep in touch...tks **

  6. #26
    Anny is offline Junior Member
    well, some days had passed and nothings wrong,,,im extremely happy....reallyyyyy. i would like to thank u a lot for this precious help...i was really going crazy with this. i will make god publicity about this site and u, that helped me so quicky and with good tips. If i can i will try to make some donation, since im a student. ThANK U VERY MUCHHHHHHHH. kisses and until a next time

  7. #27
    jephree is offline ¨*·.¸ «.·°·..·°·.» ¸.·*¨
    I am merging these threads as the basic error appears to be the same.

    Modem driver.
    Last edited by jephree; 28-07-2005 at 01:44 AM.

  8. #28
    Anny is offline Junior Member
    hello, long time no see...im a little worried...i though that my problem ended but sudently...my notebook shut down twice with no reason...i did what u said months ago when i had problems....

    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-02.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

    what do u think it is this time : P. thanks

  9. #29
    jephree is offline ¨*·.¸ «.·°·..·°·.» ¸.·*¨
    That was only the beginning of a log.

    Did you follow these instructions:


    1) Download and install the
    Debugging Tools from Microsoft
    2) Download and install this
    debugwiz
    3) Open the Wiz & Browse to, or paste in the path to, your latest .dmp file.
    4) After the Wiz creates a Text document attach it back to this thread.

  10. #30
    Anny is offline Junior Member
    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-02.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 18:47:50.437 2005 (GMT+1)
    System Uptime: 0 days 0:37:45.204
    *** 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, 20a0002, 83304438}

    ***** 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: 020a0002, Memory contents of the pool block
    Arg4: 83304438, 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: 83304438

    BUGCHECK_STR: 0xc2_7

    CUSTOMER_CRASH_COUNT: 2

    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.
    f7978dd4 80550fc5 000000c2 00000007 00000cd4 nt!KeBugCheckEx+0x1b
    f7978e24 805503e3 83304438 00000000 f7978e78 nt!ExFreePool+0xbf1
    f7978e34 f73aa181 83304438 83246f07 83246e28 nt!ExFreePool+0xf
    f7978e78 f728cee5 83246e28 83e99ed8 8422e028 NetMotCM+0x2181
    f7978ee0 f728db57 83304438 00000000 8422e7d8 USBPORT!USBPORT_CompleteTransfer+0x373
    f7978f10 f728e754 026e6f44 8422e0e0 8422e0e0 USBPORT!USBPORT_DoneTransfer+0x137
    f7978f48 f728ff6a 8422e028 804e56fc 8422e230 USBPORT!USBPORT_FlushDoneTransferList+0x16c
    f7978f74 f729dfb0 8422e028 804e56fc 8422e028 USBPORT!USBPORT_DpcWorker+0x224
    f7978fb0 f729e128 8422e028 00000001 83eac938 USBPORT!USBPORT_IsrDpcWorker+0x37e
    f7978fcc 804dcd22 8422e64c 6b755044 00000000 USBPORT!USBPORT_IsrDpc+0x166
    ffdff980 83e9e7b4 f7979000 00026043 00000002 nt!KiDispatchInterrupt+0x4c0
    8422e670 00000000 00000000 00000000 00000000 0x83e9e7b4


    FOLLOWUP_IP:
    NetMotCM+2181
    f73aa181 ?? ???

    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=6ba00024 esi=83304430 edi=83304438
    eip=805371aa esp=f7978dbc ebp=f7978dd4 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.
    f7978dd4 80550fc5 000000c2 00000007 00000cd4 nt!KeBugCheckEx+0x1b
    f7978e24 805503e3 83304438 00000000 f7978e78 nt!ExFreePool+0xbf1
    f7978e34 f73aa181 83304438 83246f07 83246e28 nt!ExFreePool+0xf
    f7978e78 f728cee5 83246e28 83e99ed8 8422e028 NetMotCM+0x2181
    f7978ee0 f728db57 83304438 00000000 8422e7d8 USBPORT!USBPORT_CompleteTransfer+0x373 (FPO: [Non-Fpo])
    f7978f10 f728e754 026e6f44 8422e0e0 8422e0e0 USBPORT!USBPORT_DoneTransfer+0x137 (FPO: [Non-Fpo])
    f7978f48 f728ff6a 8422e028 804e56fc 8422e230 USBPORT!USBPORT_FlushDoneTransferList+0x16c (FPO: [Non-Fpo])
    f7978f74 f729dfb0 8422e028 804e56fc 8422e028 USBPORT!USBPORT_DpcWorker+0x224 (FPO: [Non-Fpo])
    f7978fb0 f729e128 8422e028 00000001 83eac938 USBPORT!USBPORT_IsrDpcWorker+0x37e (FPO: [Non-Fpo])
    f7978fcc 804dcd22 8422e64c 6b755044 00000000 USBPORT!USBPORT_IsrDpc+0x166 (FPO: [Non-Fpo])
    ffdff980 83e9e7b4 f7979000 00026043 00000002 nt!KiDispatchInterrupt+0x4c0
    8422e670 00000000 00000000 00000000 00000000 0x83e9e7b4
    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)
    eee0d000 eee36f00 kmixer kmixer.sys Wed Aug 04 07:07:46 2004 (41107D32)
    eee37000 eee47980 NAVENG NAVENG.Sys Tue Mar 15 20:35:44 2005 (42374720)
    eee48000 eeee0e20 NavEx15 NavEx15.Sys Tue Mar 15 20:51:30 2005 (42374AD2)
    ef391000 ef3d1100 HTTP HTTP.sys Sat Oct 09 00:48:20 2004 (41672744)
    ef922000 ef974180 srv srv.sys Wed Aug 04 07:14:44 2004 (41107ED4)
    efc65000 efc67480 osaio osaio.sys Tue Jun 01 04:45:10 2004 (40BBFBC6)
    efdfd000 efe29400 mrxdav mrxdav.sys Wed Aug 04 07:00:49 2004 (41107B91)
    effe7000 efffb400 wdmaud wdmaud.sys Wed Aug 04 07:15:03 2004 (41107EE7)
    f017c000 f018ad80 sysaudio sysaudio.sys Wed Aug 04 07:15:54 2004 (41107F1A)
    f04fc000 f0511580 irda irda.sys Wed Aug 04 07:00:50 2004 (41107B92)
    f063e000 f0641280 ndisuio ndisuio.sys Wed Aug 04 07:03:10 2004 (41107C1E)
    f0742000 f0759480 dump_atapi dump_atapi.sys Wed Aug 04 06:59:41 2004 (41107B4D)
    f0822000 f0890400 mrxsmb mrxsmb.sys Wed Jan 19 04:26:50 2005 (41EDE18A)
    f08b9000 f08e3a00 rdbss rdbss.sys Thu Oct 28 02:13:57 2004 (418047D5)
    f08e4000 f0936000 SPBBCDrv SPBBCDrv.sys Thu Jul 22 00:08:26 2004 (40FEF76A)
    f0936000 f0957d00 afd afd.sys Wed Aug 04 07:14:13 2004 (41107EB5)
    f0958000 f097fc00 netbt netbt.sys Wed Aug 04 07:14:36 2004 (41107ECC)
    f0980000 f09c6460 symidsco symidsco.sys Fri Mar 04 02:55:44 2005 (4227CE30)
    f09c7000 f09efdc0 SYMFW SYMFW.SYS Tue Apr 05 19:11:07 2005 (4252D4BB)
    f09f0000 f0a10f00 ipnat ipnat.sys Wed Sep 29 23:28:36 2004 (415B3714)
    f0a11000 f0a50ce0 SYMTDI SYMTDI.SYS Tue Apr 05 19:10:52 2005 (4252D4AC)

    thats it...

+ Reply to Thread
Page 3 of 5 FirstFirst 1 2 3 4 5 LastLast