Home › Forums › Help and Support › dispread: Error – new_disprd failed with 'Instrument Access Failed
- This topic has 25 replies, 12 voices, and was last updated 2 months, 2 weeks ago by Old Man.
-
AuthorPosts
-
2020-03-20 at 21:22 #23818
No, not everybody is crap. But the software that comes with gaming motherboards, keyboards and mice (so called “enthusiast gaming gear”) is [1]. By the way, if you keep being a dick, I will just remove your posting ability. This is not reddit. Either follow etiquette or get the fuck out.
[1] https://twitter.com/gsuberland/status/1175570500292108289 (archive.org link: https://twitter.com/gsuberland/status/1175570500292108289)
- This reply was modified 4 years, 1 month ago by Florian Höch. Reason: For reference
2020-03-20 at 21:32 #23821Thanks Florian for your reply below:
Florian Höch wrote:
No, not everybody is crap. But the software that comes with keyboards and mice (so called “enthusiast gaming gear”) is. By the way, if you keep being a dick, I will just remove your posting ability. This is not reddit. Either follow etiquette or get the fuck out.
Post Link: https://hub.displaycal.net/forums/topic/dispread-error-new_disprd-failed-with-instrument-access-failed/#post-23818
You are receiving this email because you subscribed to a forum topic.
Login and visit the topic to unsubscribe from these emails.
2020-03-20 at 21:33 #23822I will be sure to post your reply on all review sites today.
2020-03-20 at 21:33 #23823Go ahead and remove me, I will just create other accounts using my proxy
2020-03-20 at 21:36 #23825Good riddance.
And apologies to everyone else for the disturbance.
- This reply was modified 4 years, 1 month ago by Florian Höch.
2020-07-13 at 9:37 #25479If it helps, it seems any RGB related software could be the cause of the issue.
I went on a hunch and disable Alienware FX Display SmartInstaller Component Device under Software components in the Device Manager.
This allowed my device to work without any issues. Hope this helps everyone else.
2020-08-10 at 20:19 #25725Charming guy…
I had a similar issue and solved it by killing the process vpixxserver. It’s from a company that sells a modified version of the X-Rite i1 Display so it is perhaps unsurprising that this process would take control of it.2020-10-26 at 4:56 #26516Just wanted to chime in and thank everyone for their advice!
I was having this access failed issue with my new i1 Display Pro. My old i1 Display 2 worked fine (aside from terrible colors because its a 12 year old colorimiter). And yep, killing the Gigabyte AORUS app fixed it right up.
Thanks Gigabyte…
Calibrite Display Pro HL on Amazon
Disclosure: As an Amazon Associate I earn from qualifying purchases.2022-06-04 at 13:39 #35566Just set up a new machine to make a heavy deadline in vfx – because of the chip shortage I had to go with a motherboard that had a lot of silly rgb leds (I’m in no way a gamer), a Gigabyte Aorus xtreme Trx40. Like everyone above I found access to my xrite i1display3 blocked and was going nuts trying to track it down. I finally found this thread, shut down the Gigabyte LED programme RGBfusion.exe and voila problem solved.
Just wanted to thank everyone here particularly Florian (who showed admirable restraint with the painful poster he ejected earlier) – I’d never had guessed that the LED software could be the cause on my own. Dodgy software indeed . . .
2023-12-10 at 1:48 #140011If it helps, it seems any RGB related software could be the cause of the issue.
I went on a hunch and disable Alienware FX Display SmartInstaller Component Device under Software components in the Device Manager.
This allowed my device to work without any issues. Hope this helps everyone else.
I know this is an old thread but thank you
my xrite was working fine a couple days ago when I calibrated my Dell monitor and I went to try again using different corrections and had the same error. But removing Alienware command centre did the trick.
2023-12-10 at 10:46 #140012Just read the whole thread, this was happening with X-Rite and Argyll so the Alienware FX command centre was affecting both.
I did remove Argyll reboot PC and had the disprd failed error.
I then removed XRite services, reboot PC and only use Argyll and had the same error.2024-02-01 at 18:31 #140506The Windows Logitech G Hub service
logi_lamparray_service
for Logitech devices also causes err 32
2024-02-01 at 20:08 #140508Good to know, thanks
-
AuthorPosts