Jump to content

Stargazers Lounge Uses Cookies

Like most websites, SGL uses cookies in order to deliver a secure, personalised service, to provide social media functions and to analyse our traffic. Continued use of SGL indicates your acceptance of our cookie policy.

sgl_imaging_challenge_banner_30_second_exp_2.thumb.jpg.7719b6f2fbecda044d407d8aba503777.jpg

kharga

Problems installing drivers in Windows 10

Recommended Posts

Hi

Reinvigorated into imaging after attending a weekend SPA course at Preston Montford FSC centre, I've bought myself a Windows 10 laptop, but come up against a problem: I'm trying to install the drivers for the OpticStar DS335C ICE camera. I've got the latest drivers from OpticStar, but each time I try to install them, using the step-by-step instructions, I come up with a blue screen and the message:

"stop code SYSTEM THREAD EXCEPTION NOT HANDLED
What failed DS 335C64.sys"

I've checked that I have administrator rights and that my laptop is indeed 64 bit.

I've had no problems installing programs such as FireCapture (although version 6 didn't include the webcam option, so installed v.5 instead). Nebulosity which is on the same disk as the OpticStar camera loaded fine.

Can anyone help, before I chuck the blasted laptop through the window and really make it crash!!!! (I should probably say that I'm normally a Mac user, so not used to such problems!)

Edited by kharga
speeling

Share this post


Link to post
Share on other sites

Hi

I don't know the camera but it sounds like you're trying to install something that is not compatible with your Windows 10? Maybe get in touch with the supplier? Or try Windows 7 compatibility mode?

Louise

Share this post


Link to post
Share on other sites
2 minutes ago, Thalestris24 said:

Hi

I don't know the camera but it sounds like you're trying to install something that is not compatible with your Windows 10? Maybe get in touch with the supplier? Or try Windows 7 compatibility mode?

Louise

The drivers provided by OpticStar are supposed to work okay in Windows 10. I've been in contact with them and they tell me that other customers running Windows 10 have had no problems

Share this post


Link to post
Share on other sites

Are you running native Windows 10 i.e. not under another os? Are there any pre-requisites such as having the Ascom platform installed? Antivirus software causing a problem?

If you have access to another Windows 10 PC or laptop you could try that.

Other than the above, I don't know what to suggest I'm afraid.

Louise

Edit: is it a new laptop? Is the win 10 up to date? Does it recognize your camera (without the driver)? Is the driver on a CD or downloaded? Try disabling anti virus (disconnect from internet)

Edited by Thalestris24

Share this post


Link to post
Share on other sites

Thanks for your replies. It's a new laptop running Win 10. It seems to have updated itself. When I plug the camera in, it wants to load drivers automatically, but as per the instructions I have been given I prevent it and go through the manual loading process, but no luck. I contacted Opticstar when I encountered the problem and just in case the files had corrupted during downloading, they sent me a cd with the files, but I still end up with the same error message. I'm now considering getting a more modern camera, which is probably the best way forward, since the imaging chips have improved enormously since I bought the Opticstar camera.

Edited by kharga

Share this post


Link to post
Share on other sites

Hi 

I assume you have the driver installation files saved on your hard drive. There are a few things you could try - run the installation in compatibility mode as a windows 7 file. Try running the installation as administrator. Not sure if it might be possible to install 32-bit drivers in xp/compatibility mode. Anyway, it's probably something simple causing the problem if Opticstar say it should work...

Louise

Share this post


Link to post
Share on other sites

There may well have been folk using the camera OK on Win10 but when was this ? any Windows update can stuff anything that worked before  :-(

You could install a Bootcamp partition on your Mac to run Windows stuff I've done this with mine, seems to work OK

Dave

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By alexwolf
      Hello!
      Today we published first release candidate to version 0.19.1 - please help us testing Stellarium!
      List of changes between version 0.19.0 and master (0.19.0.16926/0.19.1RC1):
      - Added allow to search an inactive meteor showers in Search Tool/Lists tool
      - Added 'Azimuth vs. Time' graph into AstroCalc/Graphs tool
      - Added feature to show tracks for latest several selected planets (GH: #539)
      - Added calculation and showing the orbital period for artificial satellites
      - Added revolutions per day info for artificial satellites
      - Added tools for jumping to the next or previous time of rising, transit or setting for selected object (GH: #484)
      - Added new behavoir for AstroCalc/Graphs when clicking within graph area now sets current time.
      - Fixed issue in script 'Mercury Triple Sunrise and Sunset'
      - Fixed crash of Stellarium for eyepieces with permanent crosshair
      - Fixed Stellarium crash when Remote Control plugin is working
      - Fixed computation of assume radius for minor planets.
      - Fixed the issue of the scrolling not working properly on Mac (GH: #393)
      - Fixed crash in Scripting Engine (Hide artificial satellites through StelProperties in core.clear() method to avoid crash if plugin was didn't loaded)
      - Fixed planetarium crash in HiPS (network manager delete problem)
      - Fixed position problems on the Poles (GH: #391)
      - Fixed scaling Telrad sign on HighDPI monitors
      - Fixed surface occlusion bug even with landscape turned off in scripting engine (GH: #680)
      - Fixed building with cmake -DBUILD_SHARED_LIBS=ON (GH: #683)
      - Fixed error in constellation file format (Babylonian)
      - Fixed Europe/Volgograd time zone settings (GH: #686)
      - Fixed HiPS handling of allsky download (GH: #671)
      - Fixed progress bar rendering (GH: #671)
      - Fixed positive declinations issue in AstroCalc tool when option 'Use decimal degrees' is enabled (GH: #690)
      - Fixed file names inconsistency
      - Fixed constellation line in "Japanese Moon Stations" skyculture
      - Fixed file name for constellation boundaries in Stellarium User Guide
      - Fixed the user interface problems in Oculars plug-in (GH: #580)
      - Fixed getting the wrong values in objects/info method for selected object for different formats (Remote Control plugin)
      - Fixed refresh plots when AstroCalc dialog becomes visible again (AstroCalc/Graphs tool)
      - Fixed jquery vulnerability (GH: #694)
      - Fixed date and time dialog behaviour: Hour/Minute/Second spinners now correctly trigger signals dateChanged(), dateChangedByYear and dateChangedForMonth() when days, months or years are affected by it.
      - Fixed update graphs in AstroCalc/Graphs tool when days change
      - Updated planetary nomenclature
      - Updated common names of stars and DSO's
      - Updated cmake rules for Windows deployment
      - Updated DSO textures
      - Updated behaviour of HiPS survey if Stellarium started without network (GH: #681)
      - Updated GUI for ArchaeoLines plugin (GH: #689, #682)
      - Updated default pulsars catalog (v1.60)
      - Updated list of asterisms
      - Excluded Armintxe skyculture and landscape from default package
      Download link: https://github.com/Stellarium/stellarium-data/releases/tag/beta
    • By noah4x4
      I wasn't sure where to post this tip....it is probably of most use here....
      Many of us with observatories or indoor Mission Control use Windows 10 Pro Remote Desktop to control a scope side computer running camera and scope control software from a second computer indoors. This works superbly at 1080p resolution.
      However, I have struggled for a year trying to perfect a wireless solution that works with 4K UHD cameras terminating in a 4K UHD display.  Until now, whilst cat 6 cable does work fine, wireless even at 5Ghz 802.11ac has struggled with some lag and poor performance. I have spent a fortune upgrading wireless adapters and range extenders, but this isn't the issue!
      Here is a solution;
      1.  Seperate your dual band network into distinct 5Ghz and 2.4 Ghz channels.
      This is easy with  (say) a BT Home Hub. If you don't do this, it can be a bit hit or miss whether your 5 Ghz wireless adapters connect to the right channel. You will now see TWO channels, one at 2.4 Ghz with a suffix like <hub name> and another at 5 Ghz named <hub name -5>. Connect your 5Ghz adapters to the latter. If your internal adapters are merely 2.4Ghz, you can disable them via Device Manager and plug in a USB version costing around £5. Note that at 5 Ghz wireless range might drop. If so, a Netgear EX8000 wireless extender is recommended as it employs 'mesh' technology. 
      2. ONLY if you have a fast network, and powerful CPUs and quality graphics card, try DISABLE 'RemoteFX compression' in RDP.
      This allows uncompressed screen data to flow across RDP.  I have found this improves performance whether using 802.11ac wireless or cat 6 cable. What RemoteFX compression appears to do is limit effective RDP speeds to under 10Mbps (due to translation times). That is crazy if you have 433 Mbps adapters,  and an 802.11ac network (or catv6 cable). Unleash the beast! Send across uncompressed data! The issue is not with speed or bandwidth, it is an artificially imposed limit in RDP.
      To do this type 'Edit Group Policy' in the Windows 10 Pro search box (doesn't work in Win 10 Home). You need to drill down through about five levels of Windows Configeration Folders, and Administration Templates and Remote Desktop Services/Host folders to find a utility named <Edit RemoteFX Compression>. In that, your options are <disable> compression or <enable> a compromise mode.
      If you don't know how to do this try Googling 'Disabling RemoteFX Compression' to find a lengthy Microsoft tutorial. Or visit https://docs.microsoft.com/en-us/windows-server/administration/performance-tuning/role/remote-desktop/session-hosts .
      I deliberately don't here state the quick route sequence to access this deeply embedded network utility command because you are delving deep into developer/administrator territory and do need to understand what you are doing and how to revert to your original RDP settings if your network can't handle these levels of uncompressed screen data. We don't want any novice attempting this on a cheap Compute Stick on an inadequate network!
      3.  When employing RDP from your computer indoors, select <WAN 10 Mbps> or <LAN 10 Mbps> as appropriate via <Options><Experience>. The default <auto-select my connectivity> often selects too low an option. The irony here is you can select this and still not enjoy faster speeds unless you have edited/disabled RemoteFX compression.
      I now have Atik Infinity plus CPWI software running in an end to end 4K UHD system terminating in a 4K UHD monitor. Over 802.11ac wireless it is now rock steady.  Over cat 6 cable my system is now turbo powered. If you don't need RemoteFX Compression, don't let it restrict your network performance. It is evidently set to ensure it works on lowest common denominator networks. If you have a fast network/CPU, disable RemoteFX compression and finally release the beast of 4k UHD over RDP.
       
    • By Gfamily
      I gave a demonstration/workshop at my local Astro Group* about a simple way of removing light pollution from an Astro Photo. 
      The description I gave was deliberately for beginners, using a wide angle tripod shot photo and using one of the easiest packages to get to grips with (Paint.net). 
      The attached pdf covers the basic technique. 
      I'd appreciate any feedback on it. 
       
       
       
      * The Mid Cheshire Astronomical Group - all welcome, we meet on the last Friday of the Month.
      LP MCAG.pdf
    • By 5haan_A
      Hi,
      What software or apps do you use to help you get around the night sky easier? 
      Currently I might use starmap on my phone to help me when I'm out observing and I recently downloaded sterllarium, but I'm still getting to grips with it.
      Thanks,
       
      Shaan
    • By Sunshine
      Hello! I was wondering if there was a preferred version of windows for imaging with dedicated cams? Have I read somewhere in SGL that many favor windows 7 over 10?.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.