 | |
| |
| 09 Jun 2011 | #1 |
| | BSOD When connecting with tmobile huawei e1750 Is Windows 7 . . . - x86 (32-bit) or x64 ? x64 - the original installed OS on the system? zes Windows 7 - an OEM or full retail version? oem vaio - OEM = came pre-installed on system - Full Retail = you purchased it from retailer - What is the age of system (hardware)? unknown, not brand new - What is the age of OS installation (have you re-installed the OS?) unknown, similar when I hit the connect button in telekom internet manager BSOD happens everz time. apparently just where it should be online. This is a relativelz new issue, appeared after installing and uninstalling network sharing software connectify and virtual router. strangely the german keyboard layout just confused itself as well. z and y order reversed, as would be on anz other keyboard. ugh. not my computer to saz the least. please see attached file as per instructions.. |
My System Specs | |
| 09 Jun 2011 | #2 |
| | 
Quote: Originally Posted by heorling  Is Windows 7 . . . - x86 (32-bit) or x64 ? x64 - the original installed OS on the system? zes Windows 7 - an OEM or full retail version? oem vaio - OEM = came pre-installed on system - Full Retail = you purchased it from retailer - What is the age of system (hardware)? unknown, not brand new - What is the age of OS installation (have you re-installed the OS?) unknown, similar when I hit the connect button in telekom internet manager BSOD happens everz time. apparently just where it should be online. This is a relativelz new issue, appeared after installing and uninstalling network sharing software connectify and virtual router. strangely the german keyboard layout just confused itself as well. z and y order reversed, as would be on anz other keyboard. ugh. not my computer to saz the least. please see attached file as per instructions.. virtaully identical and caused by connectify. I would remove it to test. Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\060911-16239-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;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Machine Name:
Kernel base = 0xfffff800`0300b000 PsLoadedModuleList = 0xfffff800`03248e50
Debug session time: Thu Jun 9 15:19:08.935 2011 (GMT-4)
System Uptime: 0 days 0:03:09.495
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {3f8, 2, 0, fffff80003072640}
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 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000000000003f8, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80003072640, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032b30e0
00000000000003f8
CURRENT_IRQL: 2
FAULTING_IP:
nt!memcpy+250
fffff800`03072640 488b440af8 mov rax,qword ptr [rdx+rcx-8]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: svchost.exe
TRAP_FRAME: fffff880097810b0 -- (.trap 0xfffff880097810b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa80038f9790 rbx=0000000000000000 rcx=fffffa80038f9bb8
rdx=0000057ffc706848 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003072640 rsp=fffff88009781248 rbp=fffffa80038eb1a0
r8=0000000000000400 r9=0000000000000020 r10=fffff8000320a888
r11=fffffa80038f97b8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe cy
nt!memcpy+0x250:
fffff800`03072640 488b440af8 mov rax,qword ptr [rdx+rcx-8] ds:0006:00000000`000003f8=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff8000307ac69 to fffff8000307b700
STACK_TEXT:
fffff880`09780f68 fffff800`0307ac69 : 00000000`0000000a 00000000`000003f8 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`09780f70 fffff800`030798e0 : fffffa80`06ab81a0 fffff880`09781748 fffffa80`06ab81a0 fffff880`0171caed : nt!KiBugCheckDispatch+0x69
fffff880`097810b0 fffff800`03072640 : fffff880`044949bc ffff0000`081770fa fffff800`63416d4d 00000000`00001000 : nt!KiPageFault+0x260
fffff880`09781248 fffff880`044949bc : ffff0000`081770fa fffff800`63416d4d 00000000`00001000 00000000`00000028 : nt!memcpy+0x250
fffff880`09781250 ffff0000`081770fa : fffff800`63416d4d 00000000`00001000 00000000`00000028 fffffa80`038f9790 : connctfy+0x39bc
fffff880`09781258 fffff800`63416d4d : 00000000`00001000 00000000`00000028 fffffa80`038f9790 ffffffff`ffffffff : 0xffff0000`081770fa
fffff880`09781260 00000000`00001000 : 00000000`00000028 fffffa80`038f9790 ffffffff`ffffffff fffffa80`0374d870 : 0xfffff800`63416d4d
fffff880`09781268 00000000`00000028 : fffffa80`038f9790 ffffffff`ffffffff fffffa80`0374d870 fffff880`09781748 : 0x1000
fffff880`09781270 fffffa80`038f9790 : ffffffff`ffffffff fffffa80`0374d870 fffff880`09781748 00000000`40010008 : 0x28
fffff880`09781278 ffffffff`ffffffff : fffffa80`0374d870 fffff880`09781748 00000000`40010008 fffff880`0449332d : 0xfffffa80`038f9790
fffff880`09781280 fffffa80`0374d870 : fffff880`09781748 00000000`40010008 fffff880`0449332d fffff880`016f6110 : 0xffffffff`ffffffff
fffff880`09781288 fffff880`09781748 : 00000000`40010008 fffff880`0449332d fffff880`016f6110 00000000`00000000 : 0xfffffa80`0374d870
fffff880`09781290 00000000`40010008 : fffff880`0449332d fffff880`016f6110 00000000`00000000 fffffa80`06ab81a0 : 0xfffff880`09781748
fffff880`09781298 fffff880`0449332d : fffff880`016f6110 00000000`00000000 fffffa80`06ab81a0 fffffa80`06ab8f68 : 0x40010008
fffff880`097812a0 fffff880`016f6110 : 00000000`00000000 fffffa80`06ab81a0 fffffa80`06ab8f68 fffffa80`06ab81a0 : connctfy+0x232d
fffff880`097812a8 00000000`00000000 : fffffa80`06ab81a0 fffffa80`06ab8f68 fffffa80`06ab81a0 fffff880`0171a10c : ndis!WPP_GLOBAL_Control
STACK_COMMAND: kb
FOLLOWUP_IP:
connctfy+39bc
fffff880`044949bc ?? ???
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: connctfy+39bc
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: connctfy
IMAGE_NAME: connctfy.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4bfe3927
FAILURE_BUCKET_ID: X64_0xA_connctfy+39bc
BUCKET_ID: X64_0xA_connctfy+39bc
Followup: MachineOwner
---------
1: kd> lmvm connctfy
start end module name
fffff880`04491000 fffff880`0449c000 connctfy T (no symbols)
Loaded symbol image file: connctfy.sys
Image path: \SystemRoot\system32\DRIVERS\connctfy.sys
Image name: connctfy.sys
Timestamp: Thu May 27 05:19:35 2010 (4BFE3927)
CheckSum: 0000EAEA
ImageSize: 0000B000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4 |
| My System Specs |
| 09 Jun 2011 | #3 |
| | Un installed both already.. How else to remove them? |
| My System Specs |
| . |
| |
| 10 Jun 2011 | #4 |
| |
Quote: Originally Posted by heorling Un installed both already.. How else to remove them? |
| My System Specs |
| 11 Jun 2011 | #5 |
| | did not fix.. tried removing connctfy.sys, which avoids the blue screen, but instead can't reach internet the through the huawei usb umts stick. had to go into safe mode, take ownership, etc, when this is done, the system complains, and was reset to an earlier configuration where connctfy.sys still exist, and back to square BSOD. Ideas? All out.. |
| My System Specs |
| 15 Jun 2011 | #6 |
| | I also had same problem. (BSOD as soon as I try to connect to internet using the usb HSPA modem.) It crashes with this error - IRQL_NOT_LESS_OR_EQUAL I was using "huawei ec1260 modem" and connectify 2.0.2 version. I did not care to look at the crash dumps and since it was fresh system, I went ahead with factory reset. For now I am avoiding to install connectify and usb modem by itself seems to be working fine. And will try to make the hotspot work using IntelMyWifi adaptor support.( my laptop has intel centrino 6230 card) . hotspot is working, but still some work left to be done to share the internet. |
| My System Specs |
 |
BSOD When connecting with tmobile huawei e1750 problems?
| Thread Tools | |
| Similar help and support threads for: BSOD When connecting with tmobile huawei e1750 | ||||
| Thread | Forum | |||
| BSOD When Huawei 3G Dongle Plugged in | BSOD Help and Support | |||
| BSOD When Huawei 3G Dongle Plugged in | BSOD Help and Support | |||
| Huawei E1750 3 Dongle problem | Hardware & Devices | |||
| Having problem with huawei E1750 mobile broadband. | Drivers | |||
| Huawei E630 BSOD after pluging | Drivers | |||
All times are GMT -5. The time now is 03:16 PM.
