none
Driver\WUDFRd failed to load...

    Question

  • I keep getting this warning at power-up. MS on-line support has no results. Dell has no answers (it is beyond their level of expertise !). I don't know how to contact MS windows 7 support (Dell won't tell me--probably beyond their level of expertise also). So if someone can take an educated guess at what this driver is, or steer me in the right direction I would appreciate it. I have recently noticed that a 'run' windows opens briefly during PUP but closes too quickly for me to see what if anything is displayed in the command line. I don't know how to run a 'trace' on this OS or even if 'trace' is even used these days. Thank you for your time and any thoughts.

    __________________________________________________________________________________________________
    Log Name: System

    Source: Microsoft-Windows-Kernel-PnP

    Date: 1/25/2010 4:07:45 PM

    Event ID: 219

    Task Category: (212)

    Level: Warning

    Keywords:

    User: SYSTEM

    Computer: George-PC

    Description:

    The driver \Driver\WUDFRd failed to load for the device USB\VID_BEEF&PID_0006\AAAAAAAAAAAAAAAAAAAA.

    Event Xml:

    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

    <System>

    <Provider Name="Microsoft-Windows-Kernel-PnP" Guid="{9C205A39-1250-487D-ABD7-E831C6290539}" />

    <EventID>219</EventID>

    <Version>0</Version>

    <Level>3</Level>

    <Task>212</Task>

    <Opcode>0</Opcode>

    <Keywords>0x8000000000000000</Keywords>

    <TimeCreated SystemTime="2010-01-25T21:07:45.746021500Z" />

    <EventRecordID>75881</EventRecordID>

    <Correlation />

    <Execution ProcessID="4" ThreadID="56" />

    <Channel>System</Channel>

    <Computer>George-PC</Computer>

    <Security UserID="S-1-5-18" />

    </System>

    <EventData>

    <Data Name="DriverNameLength">42</Data>

    <Data Name="DriverName">USB\VID_BEEF&amp;PID_0006\AAAAAAAAAAAAAAAAAAAA</Data>

    <Data Name="Status">3221226341</Data>

    <Data Name="FailureNameLength">14</Data>

    <Data Name="FailureName">\Driver\WUDFRd</Data>

    <Data Name="Version">0</Data>

    </EventData>

    </Event>

    Friday, January 29, 2010 9:34 PM

Answers

All replies

  • If this is a driver issue, the fastest way to track this down is to use a testing tool called Driver Verifier.

    If this tool finds a problem, your machine will crash again.  Hopefully with it enabled, it will allow you to easily identify the bad driver.

    Enable driver verifier
    1) Open an elevated command prompt
    2) Type "verifier /standard /all"  (no quotes)
    3) Reboot your machine
    4) Use machine again until it crashes (hopefully this will be fast :)

    After the crash & reboot, go into safe mode.  http://windowshelp.microsoft.com/Windows/en-US/Help/323ef48f-7b93-4079-a48a-5c58eec904a11033.mspx

    Disable driver verifier
    1) Open an elevated command prompt
    2) Type "verifier /reset" (no quotes)
    3) Reboot your machine

    Upload the minidump file to the pubic folder of www.skydrive.com so someone can look at the files to see if they can pinpoint the cause.

    I would also do a memory check with http://www.memtest.org/ and verify the ram is good.
    MCSE, MCSA, MCDST [If this post helps to resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others find the answer faster.]
    Friday, January 29, 2010 10:52 PM
  • I assume too since this is a Dell, that Dell had you run the full onboard diagnostics (if the OEM partition wasn't removed that held the onboard diagnostics) otherwise download the latest diagnostics utility for your machine and run the FULL set of tests.
    MCSE, MCSA, MCDST [If this post helps to resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others find the answer faster.]
    Friday, January 29, 2010 10:55 PM
  • I ran the verifier utility and the system promptly crashed to the BSOD which said a driver in the kernal stack was attempting to corrupt windows and needed to be replaced with a working version. Where do I find the minidump file ? Do I need to go into advanced system settings and redirect it to a new location?
    Saturday, January 30, 2010 7:08 PM
  • C:\Windows\Minidump folder we need the *.dmp files
    MCSE, MCSA, MCDST [If this post helps to resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others find the answer faster.]
    Sunday, January 31, 2010 1:36 AM
  • Can't find C:\Windows\minidump.
    Sunday, January 31, 2010 1:39 AM
  • (%systemroot%\minidump)  you may need to enable folder options to see hidden files and folders
    MCSE, MCSA, MCDST [If this post helps to resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others find the answer faster.]
    Sunday, January 31, 2010 1:47 AM
  • I remember finding this file when I had Vista, but I looked everywhere in Windows 7 and can't find it. I may have the advanced system crashdump set up wrong.

    Sunday, January 31, 2010 1:58 AM
  • I went into system settings / advanced. I checked and the Crashdump file was supposed to be written to %systemroot%\Minidump. I tried a small memory dump, a kernal dump and got absolutely nothing to show for it. I have searched everywhere for any file that corresponds with the time of the BSOD. The closest thing I got was in C:\users\george\AppData\Local\ElevatedDiagnostics. I have a file called 'setupact' and one called 'ntbtlog'. All of these files are too large to post on this site. I want to thank you for your time and effort and hope you understand that I am not that computer literate. I will keep trying. The verifier found the problem but I can't produce a file with the results. Last night I re-installed Windows 7 x64 as an upgrade and still have : "a driver attempting to corrupt Windows has been caught. This driver needs to be replaced with a working version.' Everything works. If something didn't work I could find it. I don't know what to do. I ain't got nothin'.
    Sunday, January 31, 2010 4:33 AM
  • what is your machine make, model and model # (be very specific). Be specific to the actual error you're receiving, any error codes, messages. Make sure that you have no 3rd party firewalls/security suites installed, Itunes, Zonealarm, antivirus.

    Install the latest Windows software updates. Don't forget to check for non-critical updates too!

    To manually get updates, open Internet Explorer (you can't use a non-Microsoft browser for updates).

    For IE 8 and later: Click on Safety, then Windows Update. Follow the instructions.

    If you can get the system up for more than a few minutes or can use safe mode, try removing the last installed software application or driver.

    For removal of an application (Windows 7 & Vista):

    1. Click on Start, Control Panel, then Programs and Features.
    2. Select the software to uninstall and select Uninstall.

    For removal of an application (Windows XP):

    1. Click on Start, Control Panel, then Add or Remove Programs.
    2. Select the software to uninstall and select Remove.

    To disable a driver:

    1. Bring up the system information dialog:

      On the keyboard, press the Windows key + Pause/Break.

        or
    2. Select Start, right click Computer and on the drop-down, select Properties.

    3. Click on the left side option Advanced system settings (7/Vista only).
    4. In System Properties, select the Hardware tab, then click on Device Manager button.
    5. Find the hardware/driver of interest (you may need to expand a choice at the "plus" graphic) and double click the choice.
    6. Select the Driver tab. Here you can perform a number of actions such as update the driver, roll Back the driver to an older version, disable or uninstall the driver.
    7. Click OK to exit, then close the Device Manager and other previously opened dialogs.

     


    MCSE, MCSA, MCDST [If this post helps to resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others find the answer faster.]
    Sunday, January 31, 2010 5:08 AM
  • The PC is a DEll XPS-420 Dimension Desktop / Core2 Quad Core Q6600 2.4 GHz / 8GB RAM / NVIDIA GeForce 9500GT 1GB video board. The system only freezes up and crashes when I use 'verifier'. The 'Blue Screen Of Death' states that a driver attempting to corrupt Windows has been caught. This driver needs to be replaced with a working version. Other than that, I only get the warning stated in the beginning of my question. No matter what I do I cannot get a crash dump file to be generated. If it is being generated, I can't find it --- anywhere. The only files being generated at the time of the crash are named in the above panel.
    Sunday, January 31, 2010 8:45 AM
  • How does the verifier work? I suspect that it works with  an USB device and the device driver is not compatible with Windows 7. If Dell cannot provide Windows 7 compatible driver, we are not able to resolve this issue.

    All the latest drivers for your computer can be downloaded from the following website.

    Drivers & Downloads for XPS/Dimension 420 

    Important Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.

    You may install the driver that is related to the USB device. If the issue is not resolved, we need to wait for Dell for the new drivers.


    Arthur Xie - MSFT
    Monday, February 01, 2010 8:13 AM
    Moderator
  • Hi Zuhl

    Are you using a Logitech keyboard on that system?

    The driver WUDFRd.sys is associated with Logitech keyboards and some of these are not compatible with Windows 7.

    Check the following.

    Go to the following website: Windows 7 Compatibility Center

     

    You will see a Software and Hardware tab that you can use to locate the product you wish to check for compatibility.

     

    Select the Compatibility FAQ that will explain how to use the compatibility website.

     

    If you find an installed software/hardware item that does not appear on the compatibility list, go to the website of the maker of that product and check for any updates.

    Let us know what you find.

    Thank You for using Windows 7


    Ronnie Vernon MVP
    Monday, February 01, 2010 4:56 PM
    Moderator
  • I am using a Logitech Classic 200 USB keyboard. This keyboard is listed as 64 and 32 bit compatible with no action compatible. I have tried a Logitech wireless mouse before and have uninstalled all drivers related to it. I also uninstalled all Logitech Gaming software and drivers for my joystick with no results. I was getting this warning when I was still using the original Dell USB keyboard. I did try a Microsoft wireless laser mouse and later a Microsoft wireless keyboard and mouse combo. I was unhappy with the performance of these products and stopped using them. There may still be drivers left over from them that need to be removed.
    Monday, February 01, 2010 6:05 PM
  • I am using a Logitech Classic 200 USB keyboard. This keyboard is listed as 64 and 32 bit compatible with no action compatible. I have tried a Logitech wireless mouse before and have uninstalled all drivers related to it. I also uninstalled all Logitech Gaming software and drivers for my joystick with no results. I was getting this warning when I was still using the original Dell USB keyboard. I did try a Microsoft wireless laser mouse and later a Microsoft wireless keyboard and mouse combo. I was unhappy with the performance of these products and stopped using them. There may still be drivers left over from them that need to be removed.

    I also have something called 'Interlock driver setup x64' by 'Pace Anti-piracy' listed as being installed on 11/14/09. Didn't find it at Compatibiliy Center. Don't know if I can uninstall it without any ill effects. Please advise if possible.
    Monday, February 01, 2010 7:45 PM
  • I also have something called 'Interlock driver setup x64' by 'Pace Anti-piracy' listed as being installed on 11/14/09. Didn't find it at Compatibiliy Center. Don't know if I can uninstall it without any ill effects. Please advise if possible.
    Hi

    It's possible that this application could be the problem. The pace Interlock Driver Anti-piracy is apparently a component that protects software from theft or illegal copying. It is not available as a stand alone product, but is installed by software makers when you install their products.

    More information here: PACE Anti-Piracy -- Frequently Asked Questions for End Users

    Apparently Pace does not provide end user support.

    I would recommend checking to see what software product was installed at the same time that the Pace product was installed to determine which software installed this component. Whatever product you find is where you will need to check for any possible known issues.

    You can take a look in Control Panel/Programs and Features/Installed Programs for the information.

    Doing some more checking on the WUDFRd.sys component and it turns out that this is the "Windows Driver Foundation - User Mode Framework Reflector" which is a core Windows driver component.

    It's possible that whatever driver is misbehaving is associated with the software that installed the Pace product.

    Let us know what you find. 

    Thank You for using Windows 7


    Ronnie Vernon MVP

    Monday, February 01, 2010 10:58 PM
    Moderator
  • I did a search on PACE and read that it was installed 'covertly' with some trial versions of software. The article claimed that PACE could not be removed unless it was edited out of the offending program which is why I asked. If I remember correctly, the article was dated 2005 or so. PACE does appear in ControlPanel as being able to be uninstalled, so I guess I'll try it. The only other programs installed on the same date were 1)Microsoft Sync Framework 2.0 Provider Services (x64) and 2) WIDCOMM Bluetooth Software 6.0.1.4300. I don't have any Bluetooth devices but I don't know if uninstalling WIDCOMM would cause problems elsewhere. I don't know where 'Sync Framework' came from. Maybe an update? Can it be safely removed?
    Monday, February 01, 2010 11:16 PM
  • I did a search on PACE and read that it was installed 'covertly' with some trial versions of software. The article claimed that PACE could not be removed unless it was edited out of the offending program which is why I asked. If I remember correctly, the article was dated 2005 or so. PACE does appear in ControlPanel as being able to be uninstalled, so I guess I'll try it. The only other programs installed on the same date were 1)Microsoft Sync Framework 2.0 Provider Services (x64) and 2) WIDCOMM Bluetooth Software 6.0.1.4300. I don't have any Bluetooth devices but I don't know if uninstalling WIDCOMM would cause problems elsewhere. I don't know where 'Sync Framework' came from. Maybe an update? Can it be safely removed?

    I successfully removed PACE but still have the same warnings. 1) Driver failed to load---this one and 2) wininit---dll files for all applications are being loaded.
    Monday, February 01, 2010 11:39 PM
  • I have installed my own minidump folder with an empty minidump.dmp file inside. I will enable KernelEventTracing in Event viewer to see if I can capture the driver attempting to corrupt Windows.
    Wednesday, February 03, 2010 10:35 PM
  • http://support.microsoft.com/kb/974720

    Warning is due to the timing of components being installed and is safe to ignore.
    • Marked as answer by Zuhl3156 Friday, February 05, 2010 4:42 AM
    Friday, February 05, 2010 4:42 AM
  • Well...  I had the same exact error, but it appears that some further reading is required.  Read this:  http://support.microsoft.com/kb/978977

    If you have the Smart Card Reader or other "!" point for a related device, you may beed the associated HotFix...  I did... Cleared up the "!" and the WUDFRd event...

    • Edited by cautery Saturday, May 01, 2010 12:20 PM fix link
    • Marked as answer by Zuhl3156 Saturday, May 01, 2010 4:36 PM
    • Unmarked as answer by Zuhl3156 Saturday, May 01, 2010 4:36 PM
    • Marked as answer by Zuhl3156 Saturday, May 01, 2010 4:43 PM
    Saturday, May 01, 2010 12:17 PM
  • I had no "!" in my Device Manager or anywhere else other than the error in Event Viewer. I chose to ignore the error as MSFT advised and nothing ever malfunctioned because of it. My error went away probably due to a MSFT update. Your answer is probably more correct as this Question was posted before the support document you are referring to was not published until March.
    Saturday, May 01, 2010 4:43 PM
  • I'm not sure this applies, KB974720 is talking about device ROOT\*ISATAP\0000, not USB\VID_BEEF&PID_0006\AAAAAAAAAAAAAAAAAAAA.

    ISATAP is a software-only network stack driver, where as the USB\VID_BEEF prefix suggests memory corription is involved.

    Sunday, February 06, 2011 8:01 PM
  • I think I used 'Unknown Device Identifier' from HunterSoft to find the device and remove its drivers.

     http://download.cnet.com/windows/huntersoft/3260-20_4-85156.html

    It's a rather lengthy process where I had to open each device listed and look at the 'Hardware ID' to find it. It has been so long ago that I don't even remember what I had eventually found. I even forgot about this post. It might have been the drivers from a USB joystick that I'd removed because of a conflict with a game and forgot to remove its drivers that were looking for a joystick at startup that wasn't there anymore.

    Sunday, February 06, 2011 8:31 PM
  • I have the exact same problem on Windows 7 SP1.

    Windows 7 SP1 is supposed to have this fix included and is not allowing me to apply. Any idea what to do?

    Thursday, April 14, 2011 4:55 PM
  • I have the very same error on Windows 7 SP1 but it is really not a problem, the warning is due to the timing of components being installed and is safe to ignore.


    Sunday, May 22, 2011 7:38 AM
  • Ronnie,

    you state above "The driver WUDFRd.sys is associated with Logitech keyboards and some of these are not compatible with Windows 7."

    Really? Not just with any device using a user-mode driver? I get this error with my external legacy usb disk, but there is no malfunction - it's just that it appears in the event log.

    Sunday, May 22, 2011 7:47 AM
  • I get the exact same error.  Same system.  I ran Dell's diagnostics with no errors.  Skipped the extended memory checks though.  I am working with Dell to get this issue resolved.  The fact that this is due to the timing of component installation doesn't fix the issue for me.  I am planning on disconnecting the media card reader tonight to see if the warning is involving that. I will post results later.
    Mark Carroll
    Sunday, August 07, 2011 3:39 AM
  • I ran the verifier and sure enough I got a blue screen.  I took a picture of the screen as it flashed up and promptly rebooted.  The error involves the HIDCLASS.SYS driver.  No DMP file was created as the system rebooted before it could be saved.
    Mark Carroll
    Sunday, August 07, 2011 4:23 AM
  • Hi folks, my machine is very similar to he one above (Dell XPS 420 running windows 7 Home premium SP1) I have had no changes but am getting the same error.

    "The driver \driver\wudfrd failed to load for the device USB\VID_Beef&PID_0006\aaaaaaaaaaaaaaaaaaaa"

    I have placed my dump file here https://skydrive.live.com/?cid=90dde58410e48a22&sc=documents&uc=1&id=90DDE58410E48A22%21117

    I tried analyzing it myself but even after downloading the symbols and following the instructions here http://windows7themes.net/how-to-open-dmp-files-in-windows-7.html I get the message

    *** WARNING: Unable to verify timestamp for PSHED.dll
    *** ERROR: Module load completed but symbols could not be loaded for PSHED.dll
    ***********************************************
    ***                                                                          ***
    ***                                                                          ***
    ***    Your debugger is not using the correct symbols  ***

    Any help would be greatly appreciated

    Regards

    Alec

    Thursday, September 08, 2011 4:32 PM
  • BUGCHECK_STR:  0x124_GenuineIntel indicates a hardware failure. You should download, install and run Intel's Processor Diagnostic Utility to rule out a defective CPU. Be sure to install the correct bit version for your system:

    1)32-bit(x86): http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=19791

    2)64-bit(x64): http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=19792

     

    Thursday, September 08, 2011 7:31 PM
  • Hi Folks.  I have verified that this error involves the little 3"x1" miniview display unit on my XPS-420.  As such, when I uninstall the XPS MiniView device the error disappears.  But then windows automatically reinstalls the device upon reboot and the error reappear.
    Mark Carroll
    Friday, September 09, 2011 6:15 AM
  • Hi Folks.  I have verified that this error involves the little 3"x1" miniview display unit on my XPS-420.  As such, when I uninstall the XPS MiniView device the error disappears.  But then windows automatically reinstalls the device upon reboot and the error reappear.
    Mark Carroll
    You might try to disable the XPS MiniView display in the Device Manager. You could also disable it using MSCONFIG start-up options and unchecking the Dell MiniView box.
    Friday, September 09, 2011 7:06 PM
  • Hi Zuhl3156......disabling the XPS MiniView in Device manager solved my issue with the warning message.  Now when I boot my PC and go into Event Viewer I have zero errors and warnings and all I see is information.
    Mark Carroll
    Wednesday, December 07, 2011 5:59 AM

  • Windows
    Driver Foundation =
    FailureName
    \Driver\WUDFRd
    ---WpdBusEnumRoot\UMB\2&37c186b&0&STORAGE#VOLUME#_??_USBSTOR#DISK&VEN_FLASH&PROD_DRIVE_AU_USB20&REV_8.07#Q5H88IPKYFROLCQT4YKS&0#


    Error is caused by Windows Driver Foundation - User-mode Driver Framework
    "Service" being disabled or will load sometimes in manual, should be automatic.


    • Edited by ThisCanHelp Thursday, November 29, 2012 3:26 AM
    Thursday, November 29, 2012 3:20 AM

  • Windows
    Driver Foundation =
    FailureName
    \Driver\WUDFRd
    ---WpdBusEnumRoot\UMB\2&37c186b&0&STORAGE#VOLUME#_??_USBSTOR#DISK&VEN_FLASH&PROD_DRIVE_AU_USB20&REV_8.07#Q5H88IPKYFROLCQT4YKS&0#

    error is caused by Windows Driver Foundation - User-mode Driver Framework
    "Service" being disabled or will load sometimes in manual, should be automatic.


    • Edited by ThisCanHelp Thursday, November 29, 2012 3:25 AM
    • Proposed as answer by 'Mike P Wednesday, December 26, 2012 4:43 PM
    Thursday, November 29, 2012 3:23 AM
  • The driver \Driver\WUDFRd failed to load for the device ROOT\LENOVOVHID\0000 

    Instantly Fixed !!!! so far;)...  Thanks 'ThisCanHelp'!

    win8x64 upgrade

    Wednesday, December 26, 2012 4:45 PM
  • gob0nkers,
    What exactly did you do to get this "instantly fixed"?

    Saturday, December 29, 2012 8:45 PM
  • Excellent worked for me.

    Start/Run/services.msc

    Go to Windows Driver Foundation - User-mode Driver Framework

    Change startup type to automatic.

    That's it, thanks again.

    • Proposed as answer by flyinghuman Saturday, January 19, 2013 2:07 PM
    Monday, December 31, 2012 10:38 PM
  • "D00ger wrote:

    Excellent worked for me.

    Start/Run/services.msc

    Go to Windows Driver Foundation - User-mode Driver Framework

    Change startup type to automatic.

    That's it, thanks again."

    =============================

    ###with windows 7 original release the startup mentioned above was set to automatic by default...if you have installed sp1 which hopefully by now everyone has you will see significant slow down on your boot up process with a dark screen showing AFTER you see the "welcome to windows" screen and four color jpeg of windows. that happens because there is a conflict with way "Windows Driver Foundation - User-mode Driver Framework" was setup before SP1 which changed "Windows Driver Foundation - User-mode Driver Framework" to a MANUAL startup.

    While it stopped my "warning" in event log it wasn't worth the boot/restart slowdown issue. There was a reason MS changed the Windows Driver Foundation - User-mode Driver Framework startup with SP1 so I will look for another fix. It is only a 15-20 second slow up but the dark screen doesn't give me a warm and fuzzy feeling....

    I have tested this on one desktop and 3 laptops I have in my home with exact same results I mentioned... i went back and change "Windows Driver Foundation - User-mode Driver Framework" back to MANUAL and got a normal startup back and my issue comes when I plug in my iphone 5 and only after Apple released latest update for iOS 6.1.3

    Good Luck to all....




    • Edited by chevysales Friday, April 19, 2013 2:39 PM
    Friday, April 19, 2013 2:34 PM
  • If this is a driver issue, the fastest way to track this down is to use a testing tool called Driver Verifier.

    If this tool finds a problem, your machine will crash again.  Hopefully with it enabled, it will allow you to easily identify the bad driver.

    Enable driver verifier
    1) Open an elevated command prompt
    2) Type "verifier /standard /all"  (no quotes)
    3) Reboot your machine
    4) Use machine again until it crashes (hopefully this will be fast :)

    After the crash & reboot, go into safe mode.

    Disable driver verifier
    1) Open an elevated command prompt
    2) Type "verifier /reset" (no quotes)
    3) Reboot your machine

    Upload the minidump file to the pubic folder of

    so someone can look at the files to see if they can pinpoint the cause.

    I would also do a memory check with

    and verify the ram is good.


    MCSE, MCSA, MCDST [If this post helps to resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others find the answer faster.]

    hi cdobbs. I  followed this procedure. I uploaded to the public folder my file .dmp (100213-28111-01.dmp): can someone give a look and help me please?

    thanks a lot

    Wednesday, October 02, 2013 1:08 AM
  • I get

    The driver \Driver\WudfRd failed to load for the device SWD\WPDBUSENUM\{d878e377-621c-11e2-be65-806e6f6e6963}#0000000000100000.

    for me this is because I do not have a certain usb stick plugged in when I boot. SO may also be same on this thread.

    my question, though, is how do I  stop this error ..or the expectation that a usb stick will be plugged in?

    Thursday, November 07, 2013 10:10 AM
  • hadı
    Tuesday, January 14, 2014 6:17 PM