BSOD being caused by Garmin device, possible driver issue?


  1. Posts : 2
    Windows 7 Professional 64 bit (SP1)
       #1

    BSOD being caused by Garmin device, possible driver issue?


    Hello

    About a month ago I bought a new HP ProBook 5330M running Win 7 Professional 64 bit. After installing (a) the Garmin USB driver and (b) the Garmin Communicator plugin, I was able to use my Garmin Edge 800 without any problems.

    This week however whenever I connect the Garmin, it immediately causes a BSOD crash. I have studied the Garmin forums, where 'MarkStowell' (Garmin Product Support) suggests that installing new USB driver version 2.3.1 (dated 11 May 2012) should fix the problem. I tried this, and it sounded positive - the laptop made the sound that it had recognised a new USB device - it then went to BSOD.

    Following that, I even followed the following additional instructions prescribed by Garmin on the forum, and as far as I can tell, the only driver I have installed is the most recent 2.3.1 version:

    "I would suggest going to the inf directory found at "C:\Windows\inf". You will need to change your setting to show hidden and system files and folders in the "Folder Options" that can be found in the Control Panel. Open every inf file that starts with "oem". There will be a bunch of them starting near "oem1.inf" You are looking for any file that's first line is "; Installation file for grmnusb driver". When you find one of these files, look for a line in that file that starts "DriverVer=". If that line says anything except "DriverVer=04/19/2012,2.3.1.0", you need to close that file and delete it from the inf directory along with the .PNF file of the same name. WARNING: Do NOT delete any inf files that are not for the Garmin USB driver. which will all start with the line "; Installation file for grmnusb driver"

    So if you find a file named oem31.inf and it is for a driver version "DriverVer=09/23/2003, 2.1", delete oem31.inf and oem31.PNF. There may be several of these in this directory. go through every oemxx.inf file until you are sure there are no more to be found. Then, plug the device back in a see what happens. It is likely to install the newest driver if it was accessing one of the older ones."


    I've uploaded the ZIP. Is anyone able to suggest what might be causing this?

    Many thanks in advance.
      My Computer


  2. Posts : 138
    Windows 7 Enterprise x64, Windows 8 Enterprise x64
       #2

    I would guess that McAfee Endpoint Encryption is the culprit, see if there's any updates available for it.
      My Computer


  3. Posts : 2
    Windows 7 Professional 64 bit (SP1)
    Thread Starter
       #3

    Thanks Tobias - one thing, as far as I'm aware, I don't have that installed on my system (at least, I can't see it?). The HP bloatware asks me if I want to encrypt my drive from time to time. Could that be it, masked as HP software?
      My Computer


  4. Posts : 138
    Windows 7 Enterprise x64, Windows 8 Enterprise x64
       #4

    Probably, since the path to the "McAfee Endpoint Encryption Encryption Monitor" running on your system is "c:\program files\hewlett-packard\drive encryption\epepcmonitor.exe".
      My Computer


 

  Related Discussions
Our Sites
Site Links
About 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 00:39.
Find Us