Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.



Windows 7: BSOD When pluged in TP-LINK Wireless adapter and trying to connect wif

27 Apr 2013   #1

Windows 7 x64
 
 
BSOD When pluged in TP-LINK Wireless adapter and trying to connect wif

I bought a new Tp-Link WN721N Wireless adapter and after starting it, when it was connecting the wireless network, a BSOD suddenly came. it happened for the first time.My pc is running on Windows Ultimate x64 i installed who crash it and this was the message i got

On Fri 26/04/2013 8:59:47 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\042613-28126-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BD0)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

Can any one help me solving this? i have attached the dump file. hope it helps.


Thanks in Advance

My System SpecsSystem Spec
.

27 Apr 2013   #2

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64Bit
 
 

Activation

Crashes indicate a possible issue with the windows installation. Please post this report before we begin:Windows Genuine and Activation Issue Posting Instructions
My System SpecsSystem Spec
27 Apr 2013   #3

Windows 7 x64
 
 

I Had copied the DMP file into another computer and had run who crash it app so it may be misleading. i ran the app in my computer and here what the lates BSOD dmp file had to say :


Code:
On Sat 27-04-2013 08:32:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042713-14944-01.dmp
This was probably caused by the following module: wdf01000.sys (0xFFFFF88000EA869C) 
Bugcheck code: 0xD1 (0x10, 0x2, 0x0, 0xFFFFF88000EA869C)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Mode Driver Framework Runtime
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. 



On Sat 27-04-2013 08:22:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042713-14601-01.dmp
This was probably caused by the following module: afd.sys (0xFFFFF88003D30684) 
Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF88003D30684)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\afd.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Ancillary Function Driver for WinSock
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. 



On Fri 26-04-2013 15:23:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042613-17222-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x50B49) 
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88001850B49, 0xFFFFF88002AD3760, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. 
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. 



On Fri 26-04-2013 14:18:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042613-23930-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x2D27D) 
Bugcheck code: 0xFE (0x6, 0xFFFFFA8005455A00, 0x50456368, 0x0)
Error: BUGCODE_USB_DRIVER
file path: C:\Windows\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time
never the less, the windows installation error that you were talking about, i ran that application and it showed the following result :

Code:
Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->

Validation Code: 0
Cached Online Validation Code: N/A, hr = 0xc004f012
Windows Product Key: *****-*****-GJY49-VJBQ7-HYRR2
Windows Product Key Hash: W5/6nm6F2UPXrCkY5xUhXb/+21g=
Windows Product ID: 00426-OEM-8992662-00006
Windows Product ID Type: 2
Windows License Type: OEM SLP
Windows OS version: 6.1.7601.2.00010100.1.0.001
ID: {DB4ED050-5646-4B1A-953C-E0B1D60AC068}(1)
Is Admin: Yes
TestCab: 0x0
LegitcheckControl ActiveX: N/A, hr = 0x80070002
Signed By: N/A, hr = 0x80070002
Product Name: Windows 7 Ultimate
Architecture: 0x00000009
Build lab: 7601.win7sp1_gdr.130318-1533
TTS Error: 
Validation Diagnostic: 
Resolution Status: N/A

Vista WgaER Data-->
ThreatID(s): N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002

Windows XP Notifications Data-->
Cached Result: N/A, hr = 0x80070002
File Exists: No
Version: N/A, hr = 0x80070002
WgaTray.exe Signed By: N/A, hr = 0x80070002
WgaLogon.dll Signed By: N/A, hr = 0x80070002

OGA Notifications Data-->
Cached Result: N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002
OGAExec.exe Signed By: N/A, hr = 0x80070002
OGAAddin.dll Signed By: N/A, hr = 0x80070002

OGA Data-->
Office Status: 109 N/A
OGA Version: N/A, 0x80070002
Signed By: N/A, hr = 0x80070002
Office Diagnostics: 025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3

Browser Data-->
Proxy settings: N/A
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
Default Browser: C:\Users\Murtaza Vohra\AppData\Local\Google\Chrome\Application\chrome.exe
Download signed ActiveX controls: Prompt
Download unsigned ActiveX controls: Disabled
Run ActiveX controls and plug-ins: Allowed
Initialize and script ActiveX controls not marked as safe: Disabled
Allow scripting of Internet Explorer Webbrowser control: Disabled
Active scripting: Allowed
Script ActiveX controls marked as safe for scripting: Allowed

File Scan Data-->

Other data-->
Office Details: <GenuineResults><MachineData><UGUID>{DB4ED050-5646-4B1A-953C-E0B1D60AC068}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010100.1.0.001</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-HYRR2</PKey><PID>00426-OEM-8992662-00006</PID><PIDType>2</PIDType><SID>S-1-5-21-486122560-190863599-3723462861</SID><SYSTEM><Manufacturer>Gigabyte Technology Co., Ltd.</Manufacturer><Model>H61M-D2H</Model></SYSTEM><BIOS><Manufacturer>Award Software International, Inc.</Manufacturer><Version>F5</Version><SMBIOSVersion major="2" minor="4"/><Date>20120518000000.000000+000</Date></BIOS><HWID>FFE10C00018400FE</HWID><UserLCID>4009</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>India Standard Time(GMT+05:30)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>GBT   </OEMID><OEMTableID>GBTUACPI</OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults>  

Spsys.log Content: 0x80070002

Licensing Data-->
Software licensing service version: 6.1.7601.17514

Name: Windows(R) 7, Ultimate edition
Description: Windows Operating System - Windows(R) 7, OEM_SLP channel
Activation ID: 7cfd4696-69a9-4af7-af36-ff3d12b6b6c8
Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
Extended PID: 00426-00178-926-600006-02-16393-7601.0000-0762013
Installation ID: 005326800381584821776080215360993804444965776535267011
Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88338
Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88339
Use License URL: http://go.microsoft.com/fwlink/?LinkID=88341
Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88340
Partial Product Key: HYRR2
License Status: Licensed
Remaining Windows rearm count: 3
Trusted time: 27-04-2013 13:24:54

Windows Activation Technologies-->
HrOffline: 0x00000000
HrOnline: N/A
HealthStatus: 0x0000000000000000
Event Time Stamp: N/A
ActiveX: Registered, Version: 7.1.7600.16395
Admin Service: Registered, Version: 7.1.7600.16395
HealthStatus Bitmask Output:


HWID Data-->
HWID Hash Current: MAAAAAAABAABAAEAAAACAAAAAQABAAEAJJQO4krdPkJyOGI0nsTqzc6aXD+d9C5z

OEM Activation 1.0 Data-->
N/A

OEM Activation 2.0 Data-->
BIOS valid for OA 2.0: yes
Windows marker version: 0x20001
OEMID and OEMTableID Consistent: yes
BIOS Information: 
  ACPI Table Name	OEMID Value	OEMTableID Value
  APIC			GBT   		GBTUACPI
  FACP			GBT   		GBTUACPI
  HPET			GBT   		GBTUACPI
  MCFG			GBT   		GBTUACPI
  MSDM			GBT   		GBTUACPI
  ASPT			GBT   		PerfTune
  SSPT			GBT   		SsptHead
  TAMG			GBT   		GBT   B0
  SSDT			INTEL		PPM RCM 
  MATS					MATS RCM
  SLIC			GBT   		GBTUACPI

I have also attached the two latest DMP files for your help.

Thanks
My System SpecsSystem Spec
.


27 Apr 2013   #4

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)
 
 

The installation is counterfeit.

An Acer OEM_SLP Key on a retail Gigabyte motherboard - with a GigaByte SLIC table.

The fact that the report shows it as licensed means that the installation has been forced by a hacker's Activation Exploit.

You need to reformat and reinstall using legitimate media and Key.
My System SpecsSystem Spec
27 Apr 2013   #5

Windows 7 x64
 
 

Is it necessary to instal a geniune one? Coz i dont have a key. And secondly i've used the wifi adapter in my friend's pc, there it was working just fine.
My System SpecsSystem Spec
27 Apr 2013   #6

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)
 
 

We cannot assist with non-genuine installs.
My System SpecsSystem Spec
Reply

 BSOD When pluged in TP-LINK Wireless adapter and trying to connect wif





Thread Tools




Our Sites

Site Links

About Us

Find 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 03:21 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33