Windows 7 Blue Screen because of ConnectiFy

I had installed ConnectiFy on the other day in order to convert my Windows 7 machine as an Wireless access point, but it ended up giving me blue screen of death in my Windows 7. This is the first time I am seeing this on Windows 7 in over an year!

Even in safe mode, I could not uninstall the ConnectiFy drivers which got clinged onto all network adapters.

So be careful!

Comments

  1. SatteshMarch 29, 2011 at 9:38 PM

    Go to Control Panel\Network and Internet\Network Connections
    Right Click on Local Area Network and click on Properties
    In the networking tab there should be "This connection uses the following items" and under that should be a box with a list of thing.
    Un-check anything that has got ot do with connectify..

    I recommend checking only
    Client for Microsoft
    QoS Packet Scheduler
    File and Printer sharing for Microsoft
    Internet Protocol 6(TCP/IPv6)
    Internet Protocol 4(TCP/IPv4)
    Link-Layer Topology Discovery Mapper I/O Driver
    Link-Layer Topology Discovery Responder

    Do this for all connection that you have like wireless network connection

    That should do it...

    ReplyDelete
  2. Karthick SApril 2, 2011 at 6:43 PM

    Thanks for your response. Yes, I tried that, but could not even get to Windows.... I had to then format and re-install Windows completely...it was a pain as I had only C Drive.

    ReplyDelete
    Replies
    1. ARdvisorJune 25, 2019 at 12:03 AM

      You dont need to reinstall windows. go to "Safe Mode" when Windows starting (pressing F8, but the key on other windows may be different)

      and uninsntall Connectify or just disable feature in Connectify settings
      "Disable All on Boot interfaces"
      "Start connectify on start of windows"

      and than run connectify manually.

      Delete
  3. TJR99May 20, 2011 at 5:24 AM

    I just go BSOD with Connectify. I believe it was conflicting with Sprint Smartview driver(s). After uninstalling Connectify, all prograams that I tested worked fine and Windows booted fine, until I ran Smartview and hit CONNECT. BSOD appeared every time I tried to CONNECT with Smartview. I even uninstalled and reinstalled Smartview and its drivers, but still got BSOD when hitting CONNECT.

    Finally, I ran Windows Restore from safe mode from the point that I initially installed Connectify and everything has worked fine.

    ReplyDelete
  4. krisshJune 20, 2011 at 1:12 PM

    use "mhotspot" dude..no need to install it..
    even i faced same pblm with connectify and soo shifted to it

    www.mhotspot.com..chk it heree

    ReplyDelete
  5. Prashant Kumar Singh (PS)October 30, 2012 at 9:50 PM

    Just update your wireless driver hope it work

    ReplyDelete
  6. soumyaApril 9, 2018 at 3:41 PM

    I read this blog it’s really good for learning easily, check it once at MSBI Online Training Hyderabad

    ReplyDelete

Post a Comment

Popular posts from this blog

Using External Content Types with Stored Procedures with Input Parameters

Image
You must have tried External Content Types - the exciting new feature in SharePoint 2010 to connect to an external SQL table and provide a list where it lists, creates, updates data straight into the SQL table. People always wonder, how do you get a ECT to work with a Stored Procedure, one that has input parameters. You could do it this way... Step 1: In your SharePoint Designer 2010, create a new external content type Step 2: Connect to your SQL Server and then make sure you see the Routines (your stored procedures must be listed here) Step 3: Rt Click on the Stored Procedure name and create operations for "Read Item" and "Read List" - both are required for the External Content Type's SharePoint list to be created. During both these wizards, in the Input Parameters, your SP's Input Parameter will be listed. Here, you need to create a filter, which sends out it's value to the SP's filter. For example, if your SP's Input Parameter is @Emp...
Read more

Validate a SharePoint Date Field against Current Date in Javascript

Consider the following scenario: You have a SharePoint Site which has its regional settings set to English (UK) - so that the date format becomes dd/mm/yyyy in all date pickers You would like to validate a particular date field in your List or Document Library against the current date If the validation does not pass, you should not allow the form to save So what the script does is: Uses the sputility (check my previous posts and also look at http://sputility.codeplex.com) to get the particular SharePoint date field It comes out as a date datatype, so I cast it to string Since the format is in dd/mm/yyyy and Javascript compare and date functions work only with mm/dd/yyyy, I am converting them back to that format then using UTC string conversions and comparing... Enjoy! <script type="text/javascript"> function PreSaveAction() {  var createdate = SPUtility.GetSPField('Date of Creation').GetValue();  var createdatestr=createdate.toString();      ...
Read more