![]() |
How to fix the Exception EAccessViolation in "SocketDataAvailable" As mentioned in a previous message... uninstall xolox, purge the registry of the xolox keys, delete the xolox program folder and reinstall. Just tried it, and it seems to be working fine now. |
purge the registry of the xolox keys? How do I purge the registry of the xolox keys? |
go to start > run > type in regedit. Navigate to HKEY_CURRENT_USER > Software > XoloX. Delete the key |
That Works Yup, that does the trick! Thanx, dude! |
EAccessViolation That did it. Thank you !!!! |
I done that, and am still receiving: Version: '1.20 build 177' Error message: 'Unhandled exception EAccessViolation Exception message:Access violation at address 77D5BCA9 in module ''user32.dll''. Write of address 03987809 Call stack: "[77D5BCA9] GetCursor" [0040442D] [0047B3FF] [0047B0C2] [0047853F] [0047A09C] [0047A337] [00528879]' Why? |
Me too I'm having the same problem, even though I purged the registry. |
Kaya: Should I make another small util to clear the reg keys of xolox completely [or add to my pre-existing tool?] |
I deleted the keys, uninstalled XoloX and used RegCleaner to get rid of remaining keys. However, when I reinstalled XoloX 1.22 I still occasionally get the same message about Socket Data. It tends to be a problem that causes XoloX to crash a lot over a period of an hour or so but then be fine for the rest of the day so I assume it is a problem with data being sent or recieved incorrectly from certain sources. Now that I am downloading less I am finding I am getting the message far less frequently. |
do you have to re-download xolox or just uninstall it |
All times are GMT -7. The time now is 12:50 PM. |
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2025, vBulletin Solutions, Inc.
SEO by vBSEO 3.6.0 ©2011, Crawlability, Inc.
Copyright © 2020 Gnutella Forums.
All Rights Reserved.