SL won't launch, tried multiple viewers

[GenettaGenetta]

Firestorm: http://gyazo.com/583e055cb6b099dc828066e573cbf4c1

Viewer 2: http://gyazo.com/7a05ca8f9adf03a65ef0b236cdb31f13

Black Dragon: http://gyazo.com/87a699c9b3abff663c8fd3703d5b6fdf

 

And then the suggested fix from the last thread I checked (which worked for the guy) won't even finish downloading... http://gyazo.com/3294741e4a48a9ecedd1b8d1426699cc

 

So what do I do here? >_< It was working fine for me until yesterday. I didn't change anything.

[Alwin Alcott]

think a system restore might help, this is happening before you connect to the internet, so it's most likely your machine what prevents it, might have done a update?

or try launching in the safe mode

 

if nothing helps, put your system info here, people might see more

[GenettaGenetta]

No go ;c

i5-2500K 3.30GHz

8GB RAM

64 bit OS

I'm not sure what other info to give without being asked. Sorry, only mediocre at computers.

[Antony Fairport]

I'm experencing the same issue, and I've seen a couple of other people mention it in other places. It seems to be related to this week's Windows updates (Windows 7 64bit here, that seems to be a common thread as well).

I've found that any viewer will run up just fine after the machine has been freshly restarted but, after some time, the freeze while detecting hardware happens.

While it's no fix, a workaround for now seems to be launching the viewer with -noprobe on the command line. I'm running fine with that for now (although I get the same hang when going to Help>>About, presumably because it probes for the details of the graphics card).

[Hunter Stern]

You might be having a conflicting cache issue (especially if you have several viewers installed). I recently updated FS without the prescribed clean install (I know I'm a bad  :smileylol: ) and when launching the viewer it would freeze on Initializing DFS or on Clearing Texture Cache.

Short solution, I went into User>>AppData>>Local>>FirestormOS_x64>>texturecache

and deleted ALL the contents of only the texturecache folder. Do the same thing for the Official LL viewer which is listed as Second Life in the same path directory.

It was a little slow initially but then went through.

Otherwise I would suggest a clean uninstall/install on all viewers if you have not done so.

[Jean Horten]

V2?

Hope you know that viewer 2 was discontinued and you cannot access sl with it anymore.

J.

[Hunter Stern]

sorry it was  late when I posted.

[Whirly Fizzle]

There's been a few reports of people having this problem since the last set of Windows updates.

For example see http://antonyfairport.blogspot.co.uk/2014/12/viewer-freezing-when-detecting-hardware.html

Hopefully Anthony will file a JIRA issue with logs, I left him a message asking him to.

I wonder if it's the kb3004394 update causing the problem - Microsoft already pulled that update - see http://anandtech.com/show/8782/win7-driver-issues-microsoft-amd-recommend-uninstalling-kb3004394

[Whirly Fizzle]

Oh you already posted here Anthony.

I need more coffee....

[Antony Fairport]

(For the benefit of anyone else following this thread -- I've sent details to Whirly in an offline IM)

I just set about recreating the problem so that I could grab logs and document with a view to filing a JIRA as requested and... right at this moment I can't recreate the problem. My machine has been up and running non-stop since I applied KB3024777 on Friday (the patch that undoes KB3004394) and after that restart the problem happened pretty quickly. I've not restarted since then and I've being running with -noprobe all the time since so I can actually get in-world.

Right now the SL viewer and Firestorm are working just fine and passing hardware detection despite that earlier failure. So whatever the issue is, if it still exists, it would seem that it comes and goes rather than comes and stays.

I'll carry on running up without -noprobe during normal work and see what happens.