Crash When Trying to Establish USB Modem Connection


  1. Posts : 2
    Windows 7 Home Premium 64 bit (SP1)
       #1

    Crash When Trying to Establish USB Modem Connection


    Hi, I have a problem with a 3G USB "dongle" type modem (a Huawei E173) - Windows tries to establish a connection but then computer black screens and reboots and on startup says it has recovered from a BlueScreen. I have tried setting up a manual dial up networking connection to bypass the supplied connection manager software but with same result. The shop will not take the product back as they are satisfied it works (by testing it on one of their laptops) and think it is my laptop. The support line for the product are no help.

    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7601.2.1.0.768.3
    Locale ID: 2057
    Additional information about the problem:
    BCCode: a
    BCP1: 00000000000003F8
    BCP2: 0000000000000002
    BCP3: 0000000000000000
    BCP4: FFFFF80002CC9900
    OS Version: 6_1_7601
    Service Pack: 1_0
    Product: 768_1
    Files that help describe the problem:
    C:\Windows\Minidump\061811-29390-01.dmp
    C:\Users\tobz\AppData\Local\Temp\WER-53055-0.sysdata.xml
    Read our privacy statement online:
    Windows 7 Privacy Statement - Microsoft Windows
    If the online privacy statement is not available, please read our privacy statement offline:
    C:\Windows\system32\en-US\erofflps.txt

    I've attached files as per the sticky.

    Windows 7 Home Premium 64 bit
    Original OS on system
    OEM version

    Hardware is just over a year old
    OS has not been reinstalled

    Attachment 160407

    Interested to know if there is any way I can resolve this myself. Many thanks.
      My Computer


  2. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #2

    Your ATI display driver was the cause of most BSODs, Connectify is to be blamed for the others
    Download and install the latest ATI Driver
    Remove any AVG software and use MSE
    Remove Connectify
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.
    Arguments:
    Arg1: fffffa8009f634e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff88004423f68, The pointer into responsible device driver module (e.g. owner tag).
    Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
    Arg4: 000000000000000d, Optional internal context dependent data.
    
    Debugging Details:
    ------------------
    
    
    FAULTING_IP: 
    atikmdag+12f68
    fffff880`04423f68 48895c2408      mov     qword ptr [rsp+8],rbx
    
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
    
    CUSTOMER_CRASH_COUNT:  1
    
    BUGCHECK_STR:  0x116
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    STACK_TEXT:  
    fffff880`01d60a68 fffff880`04aa3ef8 : 00000000`00000116 fffffa80`09f634e0 fffff880`04423f68 00000000`00000000 : nt!KeBugCheckEx
    fffff880`01d60a70 fffff880`04aa3c7f : fffff880`04423f68 fffffa80`09f634e0 00000000`00000000 fffffa80`07ac4410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
    fffff880`01d60ab0 fffff880`04b4af07 : fffffa80`09f634e0 00000000`00000000 00000000`00000000 fffffa80`07ac4410 : dxgkrnl!TdrIsRecoveryRequired+0x21f
    fffff880`01d60ae0 fffff880`04b74bd4 : fffffa80`00000000 00000000`00577fd1 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiReportHwHang+0x40b
    fffff880`01d60bc0 fffff880`04b462d5 : fffffa80`07ac4410 fffffa80`00000000 00000000`00577fd1 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0xd0
    fffff880`01d60bf0 fffff880`04b72e7a : 00000000`00000000 fffffa80`05966970 00000000`00000080 fffffa80`07ac4410 : dxgmms1!VidSchiScheduleCommandToRun+0x1e9
    fffff880`01d60d00 fffff800`02d26a86 : 00000000`fffffc32 fffffa80`07bd7b60 fffffa80`05398b30 fffffa80`07bd7b60 : dxgmms1!VidSchiWorkerThread+0xba
    fffff880`01d60d40 fffff800`02a5fb06 : fffff880`009e9180 fffffa80`07bd7b60 fffff880`009f40c0 39003100`36003500 : nt!PspSystemThreadStartup+0x5a
    fffff880`01d60d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    FOLLOWUP_IP: 
    atikmdag+12f68
    fffff880`04423f68 48895c2408      mov     qword ptr [rsp+8],rbx
    
    SYMBOL_NAME:  atikmdag+12f68
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: atikmdag
    
    IMAGE_NAME:  atikmdag.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4b0447a4
    
    FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmdag.sys
    
    BUCKET_ID:  X64_0x116_IMAGE_atikmdag.sys
    
    Followup: MachineOwner
    ---------
    Code:
    BugCheck A, {3f8, 2, 0, fffff80002cc9900}
    
    Unable to load image \SystemRoot\system32\DRIVERS\connctfy.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for connctfy.sys
    *** ERROR: Module load completed but symbols could not be loaded for connctfy.sys
    Probably caused by : connctfy.sys ( connctfy+39bc )
      My Computer


  3. Posts : 2
    Windows 7 Home Premium 64 bit (SP1)
    Thread Starter
       #3

    Thanks so much...after removing Connectify, the USB modem connected without the laptop crashing. I have also followed your other advice. Thanks again.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 08:23.
Find Us