Second Life crashes on startup during Initialising VFS

[Daemoz]

Second Life was working for a me a long time ago but now it crashes on Initialising VFS

I've tried using the official viewer, singularity viewer and firestorm viewer. I've tried uninstalling and reinstalling. I've tried deleting every trace of second life I can find. I've tried installing older versions of each of the viewers. I've tried updating my graphics drivers.

None of these have worked and I can't find any other solutions ;-;

I'll attach a crash log here if someone tells me where to find it

Edited December 4, 2018 by Daemoz

[Whirly Fizzle]

Graphics card: AMD Radeon R5 330
Graphics driver: 16.300.2301.0 (12/07/2016 -old!)

Your graphics drivers are over 2 years old.
Can you update your AMD graphics drivers to the latest version & see if that fixes the problem.
You can use the AMD driver auto-detect tool here: https://www.amd.com/en/support/kb/faq/gpu-131
 

[Rolig Loon]

Take a look at https://wiki.phoenixviewer.com/fs_install_crash , paying particular attention to the section on Firestorm "Locks Up" on "Initializing VFS"  .  That's written for the Firestorm viewer but it applies to any SL viewer.

[Lindal Kidd]

The Firestorm Wiki has this to say:

Firestorm "Locks Up" on "Initializing VFS"

If you have Intel Graphics HD, Intel Graphics HD2500 and Intel Graphics HD4000, and are using the 64bit version of Firestorm 5.0.7 or later, on Windows 10, refer to this page.

If you don't have the above graphics and this occurs, chances are good that some part of cache is corrupt. Deleting it should solve the problem.

• Locate your cache folder. You will probably need to do this manually, if you are unable to log in. Use a file manager (like Windows Explorer for Windows system, Dolphin, or some such) to locate the cache folder. In its default location, the cache folder is hidden on most OSs. To find it, you will need to show hidden folders. Default cache locations are:
  • Windows 7, 8.1, and 10: press [Win] + [R] and type %localappdata%, then look for the Firestorm folder. (This method avoids having to un-hide folders.)
  • Mac: ~/Library/Caches/Firestorm
  • linux: ~/.firestorm/cache or ~/.firestorm_x64/cache
• Delete the cache folder you located.
• Log back into SL, to a quiet region (try Hippo Hollow, Aich or Hatton). Allow your inventory and cache to repopulate fully.

Windows only: If the above doesn't work, then click the speaker icon in the system tray, then touch the volume slider, just enough to change the volume slightly. It may be that the Windows sound system has stalled; this should “give it a kick”.

If the above fails, then try doing a full wipe of all settings.

_______________________________________________________________________________

It sounds like you've already done most or all of that, but check again!

This thread may also provide some help: https://community.secondlife.com/forums/topic/407937-help-stuck-on-initializing-vfs/

[Daemoz]

yeah i tried all those options ;-;

[Whirly Fizzle]

This wiki page tells you where to find the crash logs on Firestorm viewer: https://wiki.phoenixviewer.com/file_a_jira#how_to_give_us_your_logs

It may also be helpful to provide a dxdiag report from your system: https://support.nexon.net/hc/en-us/articles/204335909-How-to-create-a-DxDiag-Report-in-Windows

[Daemoz]

alright here's my logs folder and the dxdiag report: https://www.dropbox.com/s/i1btgujyttggzvo/crash stuff.rar?dl=0

[Whirly Fizzle]

Thanks.

From viewer logs.

CPU: Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz (3408 MHz)
RAM: 8 GB
OS: Microsoft Windows 10 64-bit (Build 17134)
Viewer build: Firestorm-Releasex64 5.1.7.55786

Viewer crashes right after "LLWindowWin32::switchContext: Device context retrieved."
Next steps would be drawing context & recreating window - suspect graphics driver issue.
Crash shows "Last render pool type: 0" - 0 is again usually a graphics driver issue.

There is a dmp file, which is great.
Callstack from dmp:

Operating system: Windows NT
                  10.0.17134 
CPU: amd64
     family 6 model 94 stepping 3
     8 CPUs

Crash reason:  EXCEPTION_ACCESS_VIOLATION_READ
Crash address: 0x118b
Assertion: Unknown assertion type 0x00000000
Process uptime: not available

Thread 0 (crashed)
 0  atio6axx.dll + 0xffb555
 1  ntdll.dll + 0x10428
 2  ntdll.dll + 0x10428
 3  atio6axx.dll + 0xf63fc
 4  atig6pxx.dll + 0x8658
 5  atio6axx.dll + 0x1753bc8
 6  atio6axx.dll + 0x104098f
 7  atio6axx.dll + 0x103e505
 8  atig6pxx.dll + 0x8658
 9  atio6axx.dll + 0x1040bc9
10  atio6axx.dll + 0xff9c7c
11  atio6axx.dll + 0xffb532

 

Ok, so the crash is in atio6axx.dll, which is the AMD graphics driver.

Looking at your dxdiag now...

 

 

[Daemoz]

50 minutes ago, Whirly Fizzle said:

Graphics card: AMD Radeon R5 330
Graphics driver: 16.300.2301.0 (12/07/2016 -old!)

Your graphics drivers are over 2 years old.
Can you update your AMD graphics drivers to the latest version & see if that fixes the problem.
You can use the AMD driver auto-detect tool here: https://www.amd.com/en/support/kb/faq/gpu-131
 

Oh my goodness I didn't even realise I had an AMD card. This fixed my problem, i feel so silly ;-;

[Whirly Fizzle]

14 minutes ago, Daemoz said:

Oh my goodness I didn't even realise I had an AMD card. This fixed my problem, i feel so silly ;-;

Great, glad that's all the problem was 

You can remove the files from dropbox now.

[Lindal Kidd]

Another day saved!

...but NO CAPES!