Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Windows Driver Framework Stop Error [BSOD FUN]


  • Please log in to reply
5 replies to this topic

#1 WeazelGhast

WeazelGhast

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:12:24 PM

Posted 14 February 2009 - 02:38 AM

First off, as a first time poster here I have to thank anyone that's actually spending their time attempting to help a complete stranger. Thank you, I am infinitely grateful.

I installed the windows 7 Beta [build 7000] a few days ago and things went smoothly for about 48 hours. I now get BSODs within moments of a reboot. Specifically a stop error.

http://www.faultwire.com/solutions_bsod/Th...0010D-1266.html

[ also a second resource on the topic: http://msdn.microsoft.com/en-us/library/aa469186.aspx ]

that picture is the screen with my specific error code being:
0x0000010D (0x00000006, 0x00000003, 0x0000057 FFA41DF08, 0xFFFFFA8006610710)

"The driver attempted to send a framework request that has already been sent to an I/O target" is my problem according to my 1st two parameters, I just can't figure out what to do from there.

Attempted fixes:
- updated any obvious drivers in device manager
- disabled virtually everything that had an exclamation point
- checked for loose hardware in my computer
- dusted my computer for good measure
- system restored back to 1st day - bsod was delayed by about 24 hours.

other notes: My Pc has been running XP pro 64bit perfectly for the 7 months prior to trying the windows 7 beta.

Once again, thank you any and all for your assistance! =D

BC AdBot (Login to Remove)

 


#2 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:01:24 PM

Posted 14 February 2009 - 09:01 AM

Try this link to perform an analysis of the memory dump that was generated by the BSOD event: http://www.bleepingcomputer.com/forums/t/176011/how-to-receive-help-diagnosing-blue-screens-and-windows-crashes/

Copy/Paste the results into your next post and we'll see if we can figure it out from there.
My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#3 WeazelGhast

WeazelGhast
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:12:24 PM

Posted 14 February 2009 - 12:57 PM

Microsoft ® Windows Debugger Version 6.11.0001.402 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Downloads\021409-27970-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
Executable search path is:
Windows 7 Kernel Version 7000 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7000.0.amd64fre.winmain_win7beta.081212-1400
Machine Name:
Kernel base = 0xfffff800`02a0b000 PsLoadedModuleList = 0xfffff800`02c59050
Debug session time: Sat Feb 14 01:58:32.352 2009 (GMT-5)
System Uptime: 0 days 0:05:04.333
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10D, {6, 3, 57ffa41df08, fffffa8006610710}

Unable to load image athrxusb.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for athrxusb.sys
*** ERROR: Module load completed but symbols could not be loaded for athrxusb.sys
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 : athrxusb.sys ( athrxusb+6dd0b )

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




I am downloading the 300mb symbol pack for windows 7 beta 64bit as we speak, but I amgoing to wait for confirmation to install, as its just a guess that that is the problem.

#4 WeazelGhast

WeazelGhast
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:12:24 PM

Posted 14 February 2009 - 01:06 PM

Note:

athrxusb.sys

this is the driver for an atheros based wifi chip. I am using a TP-Link TL-WN620G with windows vista 64bit drivers.

#5 WeazelGhast

WeazelGhast
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:12:24 PM

Posted 14 February 2009 - 01:09 PM

Also here is the !analyzeV part. I accidentally split this into two posts.



*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

WDF_VIOLATION (10d)
The Kernel-Mode Driver Framework was notified that Windows detected an error
in a framework-based driver. In general, the dump file will yield additional
information about the driver that caused this bug check.
Arguments:
Arg1: 0000000000000006, A fatal error was made in handling a WDF request. In this case,
Parameter 2 further specifies the type of fatal error that has
been made, as defined by the enumeration WDF_REQUEST_FATAL_ERROR.
Arg2: 0000000000000003, The driver attempted to send a framework request that has
already been sent to an I/O target.
Arg3: 0000057ffa41df08, The WDF request handle value.
Arg4: fffffa8006610710, Reserved.

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

*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************

BUGCHECK_STR: 0x10D_6

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff8800080d362 to fffff80002aa6900

STACK_TEXT:
fffff800`03f80ed8 fffff880`0080d362 : 00000000`0000010d 00000000`00000006 00000000`00000003 0000057f`fa41df08 : nt!KeBugCheckEx
fffff800`03f80ee0 fffff880`0080db5b : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`0661ea60 : Wdf01000!FxIoTarget::SubmitLocked+0xca
fffff800`03f80f90 fffff880`0080c6c2 : fffffa80`03ba6010 fffffa80`0661ea60 00000000`00000000 fffffa80`05d1f820 : Wdf01000!FxIoTarget::Submit+0x63
fffff800`03f80fd0 fffff880`0080c822 : fffffa80`0661ea60 fffffa80`0661ea60 fffff800`03f8125c 00000000`00000000 : Wdf01000!FxIoTarget::SubmitPendedRequest+0x26
fffff800`03f81020 fffff880`00808a0f : fffffa80`0661ea60 fffff800`03f8125c fffffa80`03ba8030 fffffa80`03e2d9e0 : Wdf01000!FxIoTarget::Start+0x5a
fffff800`03f81080 fffff880`0667ad0b : fffffa80`0661ea60 fffff880`066ae3d5 fffffa80`03ba8030 fffffa80`40002200 : Wdf01000!imp_WdfIoTargetStart+0x83
fffff800`03f810c0 fffffa80`0661ea60 : fffff880`066ae3d5 fffffa80`03ba8030 fffffa80`40002200 00000017`80001060 : athrxusb+0x6dd0b
fffff800`03f810c8 fffff880`066ae3d5 : fffffa80`03ba8030 fffffa80`40002200 00000017`80001060 fffff880`0667af27 : 0xfffffa80`0661ea60
fffff800`03f810d0 fffffa80`03ba8030 : fffffa80`40002200 00000017`80001060 fffff880`0667af27 0000057f`f99e1598 : athrxusb+0xa13d5
fffff800`03f810d8 fffffa80`40002200 : 00000017`80001060 fffff880`0667af27 0000057f`f99e1598 fffff880`06670885 : 0xfffffa80`03ba8030
fffff800`03f810e0 00000017`80001060 : fffff880`0667af27 0000057f`f99e1598 fffff880`06670885 fffffa80`03ba8030 : 0xfffffa80`40002200
fffff800`03f810e8 fffff880`0667af27 : 0000057f`f99e1598 fffff880`06670885 fffffa80`03ba8030 fffffa80`40002200 : 0x17`80001060
fffff800`03f810f0 0000057f`f99e1598 : fffff880`06670885 fffffa80`03ba8030 fffffa80`40002200 00000028`00000000 : athrxusb+0x6df27
fffff800`03f810f8 fffff880`06670885 : fffffa80`03ba8030 fffffa80`40002200 00000028`00000000 fffffa80`00000000 : 0x57f`f99e1598
fffff800`03f81100 fffffa80`03ba8030 : fffffa80`40002200 00000028`00000000 fffffa80`00000000 00000000`00000034 : athrxusb+0x63885
fffff800`03f81108 fffffa80`40002200 : 00000028`00000000 fffffa80`00000000 00000000`00000034 fffff880`0667a7ae : 0xfffffa80`03ba8030
fffff800`03f81110 00000028`00000000 : fffffa80`00000000 00000000`00000034 fffff880`0667a7ae fffffa80`0660c3d0 : 0xfffffa80`40002200
fffff800`03f81118 fffffa80`00000000 : 00000000`00000034 fffff880`0667a7ae fffffa80`0660c3d0 fffffa80`04f09048 : 0x28`00000000
fffff800`03f81120 00000000`00000034 : fffff880`0667a7ae fffffa80`0660c3d0 fffffa80`04f09048 fffffa80`03ba8030 : 0xfffffa80`00000000
fffff800`03f81128 fffff880`0667a7ae : fffffa80`0660c3d0 fffffa80`04f09048 fffffa80`03ba8030 80001060`40002200 : 0x34
fffff800`03f81130 fffffa80`0660c3d0 : fffffa80`04f09048 fffffa80`03ba8030 80001060`40002200 fffffa80`0660c3d0 : athrxusb+0x6d7ae
fffff800`03f81138 fffffa80`04f09048 : fffffa80`03ba8030 80001060`40002200 fffffa80`0660c3d0 00000000`00000007 : 0xfffffa80`0660c3d0
fffff800`03f81140 fffffa80`03ba8030 : 80001060`40002200 fffffa80`0660c3d0 00000000`00000007 fffffa80`00fc0000 : 0xfffffa80`04f09048
fffff800`03f81148 80001060`40002200 : fffffa80`0660c3d0 00000000`00000007 fffffa80`00fc0000 fffff880`06696597 : 0xfffffa80`03ba8030
fffff800`03f81150 fffffa80`0660c3d0 : 00000000`00000007 fffffa80`00fc0000 fffff880`06696597 fffffa80`06609030 : 0x80001060`40002200
fffff800`03f81158 00000000`00000007 : fffffa80`00fc0000 fffff880`06696597 fffffa80`06609030 fffffa80`05338b40 : 0xfffffa80`0660c3d0
fffff800`03f81160 fffffa80`00fc0000 : fffff880`06696597 fffffa80`06609030 fffffa80`05338b40 00000000`00000000 : 0x7
fffff800`03f81168 fffff880`06696597 : fffffa80`06609030 fffffa80`05338b40 00000000`00000000 40002200`00000001 : 0xfffffa80`00fc0000
fffff800`03f81170 fffffa80`06609030 : fffffa80`05338b40 00000000`00000000 40002200`00000001 fffffa80`0661ea60 : athrxusb+0x89597
fffff800`03f81178 fffffa80`05338b40 : 00000000`00000000 40002200`00000001 fffffa80`0661ea60 fffff880`06670aa1 : 0xfffffa80`06609030
fffff800`03f81180 00000000`00000000 : 40002200`00000001 fffffa80`0661ea60 fffff880`06670aa1 fffffa80`03ba8030 : 0xfffffa80`05338b40


STACK_COMMAND: kb

FOLLOWUP_IP:
athrxusb+6dd0b
fffff880`0667ad0b ?? ???

SYMBOL_STACK_INDEX: 6

SYMBOL_NAME: athrxusb+6dd0b

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: athrxusb

IMAGE_NAME: athrxusb.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 46c54b08

FAILURE_BUCKET_ID: X64_0x10D_6_athrxusb+6dd0b

BUCKET_ID: X64_0x10D_6_athrxusb+6dd0b

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

#6 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:01:24 PM

Posted 14 February 2009 - 02:10 PM

I really suspect it's your TP-Link TL-WN620G (they use Atheros drivers).

Download a fresh copy of the drivers from the TP-Link website
Uninstall the software from the Programs and Features applet in Control Panel.
Then uninstall the network device in Device Manager (it must be plugged in for this to work)
Then unplug the device and reboot.

Once rebooted, plug the device back in. If it doesn't detect the device automatically, then install the drivers (using compatibility mode).

BTW - we can't get more out of the dump file because it appears that either you're not connected to the internet or the symbol files aren't loaded correctly (from the link above). Try resetting the symbol files and make sure you're connected to the internet - then generate a new analysis. If it's free of the "Your debugger is not using the correct symbols" messages then all is well. If not we'll have to research it further. As an additional thought, you are using the 64 bit version of the debugging tools when debugging this dump on a 64 bit system?
My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users