Hey all
My friend is having this error:
http://steamcommunity.com/app/398170/di ... 302007502/
details of what he's tried are in comments
attached is his DxDiag.txt
Thanks for your help
-Max (or whatever my name is on here. I haven't been on here for ages and it auto-logged in :p)
[EL 1.0488] CTD on startup: file error *.x *FIXED*
-
- Ensign
- Posts: 21
- Joined: Fri Jan 18, 2013 8:57 pm
- Location: On the dark side of the moon.
[EL 1.0488] CTD on startup: file error *.x *FIXED*
- Attachments
-
- DxDiag (2).txt
- (27.66 KiB) Downloaded 261 times
Last edited by Biscuit390 on Sun Jan 29, 2017 1:16 am, edited 2 times in total.
Re: [EL] CTD on startup: file error *.x
That indicates the system blocked the game from being able to access one of its media files. Most of the time, that indicates direct interference on the user's system:
- Most often > security program(s) blocking the required read/write operations the game performs
- Less often > insufficient memory or insufficient hard drive space (including possible insufficient video memory, ie integrated Intel HD graphics)
- Least often > failing memory/hard drive.
Have them follow the steps outlined here:
http://www.starwraith.com/forum/viewtop ... =26&t=6595
Then if they can't find the cause and the problem persists, have them follow the steps here to send me a msinfo report on their system and I can likely help further: http://www.starwraith.com/evochronlegacy/faq.htm#208
- Most often > security program(s) blocking the required read/write operations the game performs
- Less often > insufficient memory or insufficient hard drive space (including possible insufficient video memory, ie integrated Intel HD graphics)
- Least often > failing memory/hard drive.
Have them follow the steps outlined here:
http://www.starwraith.com/forum/viewtop ... =26&t=6595
Then if they can't find the cause and the problem persists, have them follow the steps here to send me a msinfo report on their system and I can likely help further: http://www.starwraith.com/evochronlegacy/faq.htm#208
-
- Ensign
- Posts: 21
- Joined: Fri Jan 18, 2013 8:57 pm
- Location: On the dark side of the moon.
Re: [EL] CTD on startup: file error *.x
Thanks Vice
Turns out he was running AVG Free.
Edit: nope, it's stopped working again
Turns out he was running AVG Free.
Edit: nope, it's stopped working again
Re: [EL] CTD on startup: file error *.x **FIXED**
Ok, thanks for the follow up. Not sure what the state of AVG is these days, but if it offers a 'gaming mode', he could try that first then move to something else if it continues to cause interference.
Edit: We can keep investigating if the problem persists. Did he uninstall it or just 'disable' it... or try a 'gaming mode'?
Edit: We can keep investigating if the problem persists. Did he uninstall it or just 'disable' it... or try a 'gaming mode'?
-
- Ensign
- Posts: 21
- Joined: Fri Jan 18, 2013 8:57 pm
- Location: On the dark side of the moon.
Re: [EL] CTD on startup: file error *.x
Currently he's only set it to disabled.
I'm going to have him run sysinternal's procmon and set the filter to 'evo' to see if anything/what is accessing the files
edit: turns out he has "bytefence security", which honestly sounds like the dodgiest AV next to "spybot search and destroy". disabling that and we'll try again
edit2: disabling that seems to have fixed it. thanks for your help Vice
edit3: oversized image was oversized
I'm going to have him run sysinternal's procmon and set the filter to 'evo' to see if anything/what is accessing the files
edit: turns out he has "bytefence security", which honestly sounds like the dodgiest AV next to "spybot search and destroy". disabling that and we'll try again
edit2: disabling that seems to have fixed it. thanks for your help Vice
edit3: oversized image was oversized
Re: [EL] CTD on startup: file error *.x
Wow, I haven't even heard of that security program I'll add it to my list of possible problematic programs for future reference. Hopefully, stopping that will sort it out.