APPEAL TO E:D COMPUTER GURUS. WANT A CHALLENGE?

[g0d0fnerds]

Bear with me, because this one is weird and long:

About December 11th, before the last big update, my joystick failed, rendering the game unplayable. For Christmas, I got a new Thrustmaster joystick, so I went and plugged it in Christmas morning. And what happened next is that I hit The Play Button Problem.

The Play Button Problem is a known issue, documented in the FAQ here:

https://support.frontier.co.uk/kb/faq.php?id=66

So I began working through the FAQ, and got to the following point:

"These files are called elitedangerous64.exe, elitedangerous32.exe, Watchdog32.exe and Watchdog64.exe. These programs can be found in either the EDLaunch folder or the game folder. You can find these by using the folder locations FAQ.

Please note: Certain antivirus programs may cause the Watchdog files to be unable to load even after disabling the antivirus program or white-listing it. To resolve this, please white-list all Elite Dangerous folders in your antivirus and then delete the Watchdog files manually. You can re-obtain both Watchdogs by verifying the game files via Steam or by using the Validate Game Files option in the Launcher."

I whitelisted the files as directed, to no effect. I then deleted them manually. When I deleted them (later I discovered that it was WatchDog64.exe that was specifically responsible), the game went to the loading screen, loaded the shaders and the planetary generation system and then said: "LOGIN FAILURE To ensure you are playing the most up to date version, please use the launcher to start the game."

I have opened a ticket with FDev to address this, and so far the results have been ZERO.

Here is what we have tried over the past week:

I have uninstalled and reinstalled all the Microsoft C++ Redists.

I have done a complete uninstall/reinstall of the game.

I uninstalled the Microsoft .Net Framework 4.7.2 and reinstalled 4.6.1. This caused both Steam and E:D to completely fail to launch by hanging forever. I rolled back. Of course, before I did this, I was directed to "turn off" all the Microsoft .NET apps in Windows Launcher (running Windows 7 OS, BTW) before doing the uninstall/reinstall, and I tried that, but the box that was supposed to be populated with things to turn off was empty.

I whiltelisted the relevant files in my antivirys (AVG Free). I uninstalled the antivirus.

Again, none of this has had the slightest effect on the original Play Button Problem, except deleting the WatchDog64.exe file, which led to the LOGIN FAILURE message above, and rolling back Microsoft .NET to 4.6.1 which caused Steam and ED to fail to launch at all.

At this point, FDev's ED Customer Support Wing is starting to tell me to do things I have already done, as if I have never done them, and they don't seem to be listening to what I'm telling them. Anyone have any ideas? I'm NOT a computer whiz, but I WILL listen and learn.

Thank you.

[ZombieHunter]

Oprindeligt skrevet af g0d0fnerds:

Oprindeligt skrevet af ZombieHunter:

Surface scan it or find a utility to do so. You need to deep scan the thing, etc. Also a defrag would reveal bad sectors but the Windows defrag sucks big time. The company that wrote it has another version that is super fast. Diskkeeper is the name of the product and the team that wrote it is the team that wrote the defrag in Windows.

Diskkeeper. Any advice on utilities for scan? I don't know the difference between a deep and a surface scan.

I mean you need to run the disk through several scans. Read / write, etc. Sometimes a bad sector is tough to find. Our disks are massive.

It is most likely not your SSD. SSD's are pretty tough. They do have a limited number of read / writes but you won't likely hit that any time soon.

Also when you scan make sure you are NOT inside of Windows. Inside of Windows certain areas cannot be scanned. And since sfc /scannow basically says your Windows is borked you probably won't find the problematic areas inside of Windows.

The solution to your problem is reinstall Windows. I'm just trying to find out what the hell went wrong and why. If money is not an issue just get a new drive and reinstall and be done with it. Sometimes finding out why takes more time than just getting new hardware. But some people are on a tight budget and that isn't an option. I 'think' you need a new drive from everything you've posted thus far. That doesn't mean I'm right but I don't know what else could cause that kind of corruption if the memory is ok.

So we know your Windows is corrupted.
We know you need to reinstall.
We know something caused it.
We know it is likely pointing to the drive.

So Occam's razor....the simplest answer is usually the right one.

But I would hate for you to get a new drive and have the same issues. And that is a possible scenario here. Troubleshooting isn't exactly an exact science all the time.

[g0d0fnerds]

Okay, so here is a sampling of some of the events:

20: Installation Failure: Windows failed to install the following update with error 0x80073712: 2018-12 Security Monthly Quality Rollup for Windows 7 for x64-based Systems (KB4471318).

10:Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.

7006: The ScRegSetValueExW call failed for Start with the following error:
Access is denied.

36887: The following fatal alert was received: 40.
(This, one, by the way, is ALWAYS preceded by The following fatal alert was received: 70.
This is the most comon error I have.

33: Activation context generation failed for "C:\Program Files\Logitech\Gaming Software\LWEMon.exe". Dependent Assembly Microsoft.VC80.MFC,processorArchitecture="amd64",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.4053" could not be found. Please use sxstrace.exe for detailed diagnosis.

14: The description for Event ID 14 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

ffffffff(ffffffff) ffffffff ffffffff

the message resource is present but the message is not found in the string/message table

1000: Your computer has lost the lease to its IP address 2600:1702:3c90:7ff0::49 on the Network Card with network address 0x2C303326DD80.

1001: Your computer was not assigned an address from the network (by the DHCP Server) for the Network Card with network address 0x2C303326DD80. The following error occurred: 0x79. Your computer will continue to try and obtain an address on its own from the network address (DHCP) server.

10005: DCOM got error "1084" attempting to start the service WSearch with arguments "" in order to run the server:
{9E175B6D-F52A-11D8-B9A5-505054503030}

[g0d0fnerds]

I think I'm going to get a new SSD to replace the old one along with a Win10 OS to replace Win 7

[Mu77ley]

TBH it sounds like your Windows installation is completely fubar, At the very least backing up your important files and then nuking the installation (format hard disk) and reinstalling would be my recommendation.

To be frank I would suggest moving to Windows 10 while you do it, as Windows 7 is going completely out of support in about a year (mainstream support ended 4 years ago), at which point Microsoft will no longer be providing any bug or security fixes for it.

[ZombieHunter]

20: Installation Failure: Windows failed to install the following update with error 0x80073712: 2018-12 Security Monthly Quality Rollup for Windows 7 for x64-based Systems (KB4471318).

Just a failed KB install. Happens all the time. Probably not anything.

10:Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.

This is a SQL query but it looks like it is from Windows Management Instrumentation.

After some searching I am correct is it coming from WMI.
https://answers.microsoft.com/en-us/windows/forum/all/windows-7-error-0x80041003-events-cannot-be/fc8f5ff7-4517-4d83-a418-6bfba59751fe

7006: The ScRegSetValueExW call failed for Start with the following error:
Access is denied.

Access was denied to a registry key to set a value. After a bit of research appears to be related to a KB or an AV denying access.

http://www.tomshardware.com/answers/id-2533232/event-7006-scregsetvalueexw-call-failed-logged-startup-fault-windows-update.html

Probably occurring due to a bad KB that was later patched by Microsoft. It means you don't have all the latest updates b/c according to many sites this was fixed.

36887: The following fatal alert was received: 40.
(This, one, by the way, is ALWAYS preceded by The following fatal alert was received: 70.
This is the most comon error I have.

33: Activation context generation failed for "C:\Program Files\Logitech\Gaming Software\LWEMon.exe". Dependent Assembly Microsoft.VC80.MFC,processorArchitecture="amd64",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.4053" could not be found. Please use sxstrace.exe for detailed diagnosis.

This is a very bad error. It means that LWEMon.exe could not load Microsoft.VC80.MFC with the given token, etc. All the details denote the exact version. This is a Microsoft Foundation Classes library and should have been installed by whatever program needed it. This is a dependency load problem and points to corruption or failed installs.

You can use sxstrace to diagnose side by side errors. This is a side by side error. It is hard to explain b/c you would have to have some experience with the way C++ redists use to link and work. Microsoft changed it in 2005 and now we have the current system known as side by side.

This DLL is from MSVS (Microsoft Visual Studio) 2005. It is the Logitech Profiler. As long as it is not installed in System32 it is fine. Some viruses use it to hide in Windows/System32. Yours is coming from the correct location and thus is not a virus, but is also not installed correctly. Points to a bad Logitech driver / utility install.

14: The description for Event ID 14 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

ffffffff(ffffffff) ffffffff ffffffff

the message resource is present but the message is not found in the string/message table

This is coming from the Nvidia driver. It is a symptom of a corrupted display driver.
https://answers.microsoft.com/en-us/windows/forum/windows8_1-hardware/nvidia-the-description-for-event-id-14-from-source/cc7a7b67-a812-41c8-ab2a-fd7a4ce1b588

1000: Your computer has lost the lease to its IP address 2600:1702:3c90:7ff0::49 on the Network Card with network address 0x2C303326DD80.

This is nothing. Just notifying you your DHCPv6 lease time expired. The lease should auto renew. If in doubt go to Command Prompt and run ipconfig /renew.

1001: Your computer was not assigned an address from the network (by the DHCP Server) for the Network Card with network address 0x2C303326DD80. The following error occurred: 0x79. Your computer will continue to try and obtain an address on its own from the network address (DHCP) server.

DHCP error likely caused by a sudden disconnection from the internet. Will resolve when you reconnect.

It can also occur if you have more than one LAN adapter / connection but only using one while keeping the other one enabled. Disable the one you are not using and this error will disappear.

10005: DCOM got error "1084" attempting to start the service WSearch with arguments "" in order to run the server:
{9E175B6D-F52A-11D8-B9A5-505054503030}

This error indicates either a virus or your Windows install is corrupted. It points to corruption and likely hard drive failure. DCOM is core to Windows and if it is not working correctly Windows nor applications that run on it will work correctly.

To see all the redists and other dependencies that have been installed go to:

<windows_drive>:<windows_path>/winsxs

All the Visual C++ redists you have installed will be there. Note that the MFC redists should be installed by programs that depend on it. The only reason I can think of it not finding it is b/c it didn't install correctly or the install failed.

[g0d0fnerds]

So, anyway, I should still go for a full Windows reinstall, yes?

[ZombieHunter]

Oprindeligt skrevet af g0d0fnerds:

So, anyway, I should still go for a full Windows reinstall, yes?

Yes. Your Windows needs reinstalled. The sfc /scannow result is enough to come to that conclusion.

[g0d0fnerds]

​Well, three weeks later, here's what's going on:

I have spent the last three weeks getting a new SSD (which was bad. Oddly, the older mechanical drive was fine), and a fresh install of Windows 10.

Took all night last night to reinstall Steam and Elite Dangerous on the new system.
​
​And I still have the same problem. Play button disappears and reappears.
​
​I have checked to make sure that Elite Dangerous is allowed through the Windows Defender firewall. It is.
​
​I have no other antivirus installed. I installed AVG and then uninstalled it and rebooted the computer when this issue appeared. It made no difference.
​
​I have run sfc /scannow and it returned a clean bill of health. I have not tried reinstalling the redists, because they were literally just installed by the game.

At this point, I can only conclude that God or ♥♥♥♥♥ have determined that I am not allowed to play this game for reasons.

Any suggestions?

[Les Grossman]

Since you tried pretty much everything and I don't know where you live, did you, per chance, tried playing it through VPN? Maybe there are some connection/server issues that prevent you from launching game properly. Try Windscribe for example? Easy to register and you have 2/10Gb free for testing purposes, literally easy one button app. Just put it in AV soft exclusions since it modifies Hosts file (yeah, it's safe).

P.S. OP, do you actually have any similar issues with any other games or software?

[Hobo Misanthropus]

Oprindeligt skrevet af g0d0fnerds:

​Well, three weeks later, here's what's going on:

I have spent the last three weeks getting a new SSD (which was bad. Oddly, the older mechanical drive was fine), and a fresh install of Windows 10.

Took all night last night to reinstall Steam and Elite Dangerous on the new system.
​
​And I still have the same problem. Play button disappears and reappears.
​
​I have checked to make sure that Elite Dangerous is allowed through the Windows Defender firewall. It is.
​
​I have no other antivirus installed. I installed AVG and then uninstalled it and rebooted the computer when this issue appeared. It made no difference.
​
​I have run sfc /scannow and it returned a clean bill of health. I have not tried reinstalling the redists, because they were literally just installed by the game.

At this point, I can only conclude that God or ♥♥♥♥♥ have determined that I am not allowed to play this game for reasons.

Any suggestions?

Download a program called "Prime95" you may have heard of it, it is an academic utilitity designed to find Mersenne prime numbers, however, because of how it runs its calculations, it's also the best CPU diagnostic tool on the market. The utility is free, and you do not need to participate (in fact, the foundation recommends against it on any hardware older than 5 years) in the project to utilize it. On the page, it will have all the info you need.

WARNING: Prime95 is an extremely intensive CPU torture test, if your cooling is inadaquate, and there is a microcode error in the CPU, you can burn out CPU cores, always monitor temperatures (Tdie especially) while running Prime95.


Why am I suggesting you use this? Your CPU is a very old model, CPUs do not last forever, and your CPU may be beyond the point of electromigration failure, causing errors to accumulate. Prime95 Will detect this, as it checks the very precise calculations required to return Mesernne prime numbers. In addition, it can detect complicated memory failures (through a general Mesernne prime fail) as well as Motherboard errors (Typically VRM)

As a general rule, if you cannot run Prime 95 for at least 1 hour, your PC has a fatal fault. A failure within 15minutes indicates a particularly severe issue.


How to proceed if Prime95 Returns errors:

1: Buy a new CPU, Your socket is old, so you can probably score a second-hand CPU for the socket, for well under $100

2: Buy a new Motherboard (Which you will then need a new CPU for)


I had an issue with a motherboard failure, about a year back. Every standard diagnostic tool told me my PC was fine, but it was behaving in an incredibly strange fashion. Prime95 was the only diagnostic that returned any type of error. Not even Memtest86 returned an error, nor Intel's CPU Diagnostic tool


I want to reiterate, Prime95 is an extremely intense torture test on a CPU, if there is some fault in your system, it is perilously likely that Prime95 will exacerbate the issue, perhaps even rendering the PC inoperable. Use it at your own risk. Before starting, make sure you know the following:

1: The max operating temperature of your CPU (Kill the probram if the CPU crosses this, even by one degree)

2: The integrity of your Power Supply and motherboard power delivery. If your motherboard/PSU is old, the sudden voltage/amp spike through the 12v can blow capacitors. If your motherboard blows up, it usually takes everything connected to it. (Good hardware will over overvoltage/current protection nowadays)

[g0d0fnerds]

CANCEL ALERT!!

Well, the issue is fixed. As it turns out, a newly released (1/15) NVIDIA graphics card driver fixed it.

Thanks to everyone who responded.

[Hobo Misanthropus]

Oprindeligt skrevet af g0d0fnerds:

CANCEL ALERT!!

Well, the issue is fixed. As it turns out, a newly released (1/15) NVIDIA graphics card driver fixed it.

Thanks to everyone who responded.

...


New Drivers isn't literally the first thing you tried?


See, this is why Technical support always goes through the rote process.

[ZombieHunter]

Oprindeligt skrevet af Hobo Misanthropus:

Oprindeligt skrevet af g0d0fnerds:

CANCEL ALERT!!

Well, the issue is fixed. As it turns out, a newly released (1/15) NVIDIA graphics card driver fixed it.

Thanks to everyone who responded.

...


New Drivers isn't literally the first thing you tried?


See, this is why Technical support always goes through the rote process.

This did not fix the entire issue. His sfc / scannow reported hundreds of errors. This level of system corruption is usually caused by bad hardware. He says his drive was bad and he did a fresh install. The reason his other fresh installs were not working is b/c he was using bad hardware to install it.

What he had were numerous problems. But the core issue was a bad Windows due to a bad drive. Then when he reinstalled he did not update to the latest Nvidia driver which caused his other issue. They are not related except that the fresh install did not install the latest NVidia driver.

But no game crash and no driver issue can cause sfc /scannow to report hundreds of errors.

But in the end its fixed. We were correct in our diagnosis of what was wrong. As always first you walk then you run. He couldn't even walk at the top of this thread.

[Hobo Misanthropus]

Oprindeligt skrevet af ZombieHunter:

Oprindeligt skrevet af Hobo Misanthropus:

...


New Drivers isn't literally the first thing you tried?


See, this is why Technical support always goes through the rote process.

This did not fix the entire issue. His sfc / scannow reported hundreds of errors. This level of system corruption is usually caused by bad hardware. He says his drive was bad and he did a fresh install. The reason his other fresh installs were not working is b/c he was using bad hardware to install it.

What he had were numerous problems. But the core issue was a bad Windows due to a bad drive. Then when he reinstalled he did not update to the latest Nvidia driver which caused his other issue. They are not related except that the fresh install did not install the latest NVidia driver.

But no game crash and no driver issue can cause sfc /scannow to report hundreds of errors.

But in the end its fixed. We were correct in our diagnosis of what was wrong. As always first you walk then you run. He couldn't even walk at the top of this thread.

Oh, lol. Sorry, I just take a lot of stuff for granted, I always download the latest driver suite before reformatting anything, so I can install the critical software in the unlikely, but all too common instance that you can't connect to the internet for some reason or another. (especially an issue with wireless dongles)

[g0d0fnerds]

Oprindeligt skrevet af Hobo Misanthropus:

Oprindeligt skrevet af g0d0fnerds:

CANCEL ALERT!!

Well, the issue is fixed. As it turns out, a newly released (1/15) NVIDIA graphics card driver fixed it.

Thanks to everyone who responded.

...


New Drivers isn't literally the first thing you tried?


See, this is why Technical support always goes through the rote process.

Yeah, that would be more convincing if literally ANYONE had said, "Hey, what's your graphics card and have you tried new drivers?" NO ONE said this. I started this conversation out with an admission that I know little about computers. I would very much be interested to know whether downloading a new driver would have temporarily fixed the problem back in December. I doubt it, but there's no way to know. For one thing, the driver I ended up downloading didn't exist until a week ago.
HOWEVER, as ZombieHunter already pointed out, even if this HAD worked, my SSD and Windows were still borked and needed to be fixed, so I would like to once again publicly thank him for his extensive and valuable help.