Jump to content
Sign in to follow this  
Darius Vayandar

Hard crashing.

You are about to reply to a thread that has been inactive for 3390 days.

Please take a moment to consider if this thread is worth bumping.

Recommended Posts

So who else has an issue with a hard crash, meaning suddenly your viewer just closes on you with no warning or crash report or anything?

I have been having this issue since i switched from an ati card to an nvidia, it happened on my old 260 and its happening against on my new 560 Ti, it did not happen on my ati hd 5770.  though on the ati i would get a mem lead that would freeze the viewer so bad id have to restart. I just did a full and complete format of my computer and deleted every old file i had, the computer itsself is clean. so what am i missing?

------------------
System Information
------------------
 Operating System: Windows 7 Professional 64-bit (6.1, Build 7600) (7600.win7_rtm.090713-1255)
           Language: English (Regional Setting: English)
System Manufacturer: To Be Filled By O.E.M.
       System Model: To Be Filled By O.E.M.
               BIOS: Default System BIOS
          Processor: Intel(R) Core(TM) i7 CPU         870  @ 2.93GHz (8 CPUs), ~2.9GHz
             Memory: 6144MB RAM
Available OS Memory: 6104MB RAM
          Page File: 1857MB used, 10346MB available
        Windows Dir: C:\Windows
    DirectX Version: DirectX 11
DX Setup Parameters: Not found
   User DPI Setting: Using System DPI
 System DPI Setting: 96 DPI (100 percent)
    DWM DPI Scaling: Disabled
     DxDiag Version: 6.01.7600.16385 64bit Unicode

---------------
Display Devices
---------------
          Card name: NVIDIA GeForce GTX 560 Ti
       Manufacturer: NVIDIA
          Chip type: GeForce GTX 560 Ti
           DAC type: Integrated RAMDAC
         Device Key: Enum\PCI\VEN_10DE&DEV_1200&SUBSYS_15633842&REV_A1
     Display Memory: 3788 MB
   Dedicated Memory: 993 MB
      Shared Memory: 2795 MB
       Current Mode: 1680 x 1050 (32 bit) (59Hz)
       Monitor Name: Generic PnP Monitor
      Monitor Model: Acer X193W+
         Monitor Id: ACR0014
        Native Mode: 1680 x 1050(p) (59.954Hz)
        Output Type: DVI
        Driver Name: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um
Driver File Version: 8.17.0012.6666 (English)
     Driver Version: 8.17.12.6666
        DDI Version: 10.1
       Driver Model: WDDM 1.1
  Driver Attributes: Final Retail
   Driver Date/Size: 1/13/2011 23:10:00, 12862568 bytes
        WHQL Logo'd: Yes

-Second moniter-
 Card name: NVIDIA GeForce GTX 560 Ti
       Manufacturer: NVIDIA
          Chip type: GeForce GTX 560 Ti
           DAC type: Integrated RAMDAC
         Device Key: Enum\PCI\VEN_10DE&DEV_1200&SUBSYS_15633842&REV_A1
     Display Memory: 3788 MB
   Dedicated Memory: 993 MB
      Shared Memory: 2795 MB
       Current Mode: 1680 x 1050 (32 bit) (60Hz)
       Monitor Name: Generic PnP Monitor
      Monitor Model: Sceptre 
         Monitor Id: SPT2011
        Native Mode: 1680 x 1050(p) (59.883Hz)
        Output Type: DVI
        Driver Name: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um
Driver File Version: 8.17.0012.6666 (English)
     Driver Version: 8.17.12.6666
        DDI Version: 10.1
       Driver Model: WDDM 1.1
  Driver Attributes: Final Retail
   Driver Date/Size: 1/13/2011 23:10:00, 12862568 bytes
        WHQL Logo'd: Yes

Share this post


Link to post
Share on other sites

that's what's know as "Crash To Desktop"

you say that you "did a full and complete format of my computer and deleted every old file", and I'm hoping that means you formatted the hard drive and REINSTALLED windows (otherwise you could have some conflicting files in the OS portion, or might have removed some needed ones)... if that's not the case, my suggestion at this point be to do that and update all your drivers, as it'll save you a million headaches later when you discover something else borked.

Next I notice that you have dual monitors.... which SL doe not generally play nice with, so make sure SL is limited to a single main monitor for best compatibility.

and finally, if you copy the log from C:\Users\<cumputer-username>\AppData\Roaming\SecondLife\logs\SecondLife.log (default location for win7) the end of that may give a clue as to what the viewer is choking on.

Share this post


Link to post
Share on other sites

it pops up on one moniter but that moniter never renders my avatars, i just become a floating pile of prims. so i move it to the second moniter and play it on there only. i did reinstall windows and i am currently looking up the log, will edit with info when have it. 

 

can you tell me what im looking for? there are alot of warning logs here...

Share this post


Link to post
Share on other sites

 

-This line under here goes up for about 30 lines or so-
2011-05-04T00:58:54Z WARNING: LLAPRFile::remove:  Attempting to remove filename: C:\Users\Cyrus\AppData\Local\SingularityViewer\texturecache\7\77233781-04bc-447b-9da6-c1b0152ec355.texture
2011-05-04T00:58:54Z WARNING: ll_apr_warn_status: APR: The system cannot find the file specified.  
2011-05-04T00:58:54Z WARNING: LLAPRFile::remove:  Attempting to remove filename: C:\Users\Cyrus\AppData\Local\SingularityViewer\texturecache\7\77c7ba2a-1f09-3b3d-0bc7-8bfb76564cc0.texture
2011-05-04T00:58:54Z WARNING: ll_apr_warn_status: APR: The system cannot find the file specified.  
2011-05-04T00:58:54Z WARNING: LLAPRFile::remove:  Attempting to remove filename: C:\Users\Cyrus\AppData\Local\SingularityViewer\texturecache\7\794a9816-a016-d3fc-f5fa-ebd260543e59.texture
2011-05-04T00:58:54Z INFO: viewer_windows_exception_handler: Entering Windows Exception Handler...
2011-05-04T00:59:01Z INFO: LLAppViewer::handleViewerCrash: Handle viewer crash entry.
2011-05-04T00:59:01Z INFO: LLError::LLCallStacks:: print:  ************* PRINT OUT LL CALL STACKS ************* 
2011-05-04T00:59:01Z INFO: LLError::LLCallStacks:: print: display_update_camera line: 177 
2011-05-04T00:59:01Z INFO: LLError::LLCallStacks:: print: LLAppViewer::idleNetwork line: 4004 
2011-05-04T00:59:01Z INFO: LLError::LLCallStacks:: print: LLAppViewer::idleNetwork line: 3988 
2011-05-04T00:59:01Z INFO: LLError::LLCallStacks:: print: LLAppViewer::idleNetwork line: 3985 
2011-05-04T00:59:01Z INFO: LLError::LLCallStacks:: print: LLAppViewer::idleNetwork line: 3979 
2011-05-04T00:59:01Z INFO: LLError::LLCallStacks:: print: LLAppViewer::idleNetwork line: 3907 
2011-05-04T00:59:01Z INFO: LLError::LLCallStacks:: print: LLAppViewer::idleNetwork line: 3896 
2011-05-04T00:59:01Z INFO: LLError::LLCallStacks:: print:  *************** END OF LL CALL STACKS *************** 
2011-05-04T00:59:01Z INFO: LLAppViewer::handleViewerCrash: Creating crash marker file C:\Users\Cyrus\AppData\Roaming\SecondLife\logs\SecondLife.error_marker
2011-05-04T00:59:01Z INFO: LLAppViewer::handleViewerCrash: Created crash marker file C:\Users\Cyrus\AppData\Roaming\SecondLife\logs\SecondLife.error_marker
2011-05-04T00:59:01Z INFO: LLAppViewer::handleViewerCrash: Handle viewer crash generating stats log.
2011-05-04T00:59:01Z INFO: LLAppViewer::writeDebugInfo: Opening debug file C:\Users\Cyrus\AppData\Roaming\SecondLife\logs\debug_info.log

is this what you wanted?

Share this post


Link to post
Share on other sites

looks like it's choking on some cache purges and giving up.... the crash log probably says as much. (note that it's actually handling the crash so if you aren't getting a crash warning on restart you probably have those warnings turned off)

I'm assuming you are using sigularity from the folder path, and that you have it specified to use a different cache location than is standard for other viewers (a good thing). so my next suggestion is to navigate to C:\Users\Cyrus\AppData\Local\SingularityViewer\texturecache and delete thecontent of that folder before trying again.... make sure you refresh and that all files and folders under texturecache are gone before you do.

Share this post


Link to post
Share on other sites

Well it was crashing right after i did a reformat though, wouldnt there be nothing in that folder when i tried the first time? this happened before the format, it happened ever since i switched from my ati card to my nvidia one

Share this post


Link to post
Share on other sites

crashed again after removing the entire singularity folder...

 

 

2011-05-04T04:04:11Z WARNING: LLVOAvatar::getTargetAttachmentPoint: Object attachment point invalid: 127
2011-05-04T04:04:11Z WARNING: LLVOAvatar::getTargetAttachmentPoint: Object attachment point invalid: 127
2011-05-04T04:04:11Z WARNING: LLVOAvatar:: processAvatarAppearance: Boob Grav SET to 0.805882 for Daya Abbot
2011-05-04T04:04:11Z INFO: LLVOAvatar:: processAvatarAppearance: Daya Abbot does not have tattoo tinting.
2011-05-04T04:04:11Z WARNING: LLVOAvatar:: processAvatarAppearance: Boob Grav SET to -1.5 for Jonaleth Stormcrow
2011-05-04T04:04:11Z INFO: LLVOAvatar:: processAvatarAppearance: Jonaleth Stormcrow does not have tattoo tinting.
2011-05-04T04:04:14Z INFO: LLAppViewer::idle: Kills on unknown objects: 188
2011-05-04T04:04:15Z WARNING: ll_apr_warn_status: APR: The system cannot find the file specified.  
2011-05-04T04:04:15Z WARNING: LLAPRFile::remove:  Attempting to remove filename: C:\Users\Cyrus\AppData\Local\SingularityViewer\texturecache\1\1b64dff7-72d3-2435-3b5e-209f29dd6acc.texture
2011-05-04T04:04:15Z INFO: display_stats: FPS: 58.10
2011-05-04T04:04:16Z WARNING: ll_apr_warn_status: APR: The system cannot find the file specified.  
2011-05-04T04:04:16Z WARNING: LLAPRFile::remove:  Attempting to remove filename: C:\Users\Cyrus\AppData\Local\SingularityViewer\texturecache\4\4982999f-f71f-c0bb-2668-c34e84e60b86.texture
2011-05-04T04:04:17Z INFO: viewer_windows_exception_handler: Entering Windows Exception Handler...
2011-05-04T04:04:22Z INFO: LLAppViewer::handleViewerCrash: Handle viewer crash entry.
2011-05-04T04:04:22Z INFO: LLError::LLCallStacks:: print:  ************* PRINT OUT LL CALL STACKS ************* 
2011-05-04T04:04:22Z INFO: LLError::LLCallStacks:: print: display_update_camera line: 177 
2011-05-04T04:04:22Z INFO: LLError::LLCallStacks:: print: LLAppViewer::idleNetwork line: 4004 
2011-05-04T04:04:22Z INFO: LLError::LLCallStacks:: print: LLAppViewer::idleNetwork line: 3988 
2011-05-04T04:04:22Z INFO: LLError::LLCallStacks:: print: LLAppViewer::idleNetwork line: 3985 
2011-05-04T04:04:22Z INFO: LLError::LLCallStacks:: print: LLAppViewer::idleNetwork line: 3979 
2011-05-04T04:04:22Z INFO: LLError::LLCallStacks:: print: LLAppViewer::idleNetwork line: 3907 
2011-05-04T04:04:22Z INFO: LLError::LLCallStacks:: print: LLAppViewer::idleNetwork line: 3896 
2011-05-04T04:04:22Z INFO: LLError::LLCallStacks:: print:  *************** END OF LL CALL STACKS *************** 
2011-05-04T04:04:22Z INFO: LLAppViewer::handleViewerCrash: Creating crash marker file C:\Users\Cyrus\AppData\Roaming\SecondLife\logs\SecondLife.error_marker
2011-05-04T04:04:22Z INFO: LLAppViewer::handleViewerCrash: Created crash marker file C:\Users\Cyrus\AppData\Roaming\SecondLife\logs\SecondLife.error_marker
2011-05-04T04:04:22Z INFO: LLAppViewer::handleViewerCrash: Handle viewer crash generating stats log.
2011-05-04T04:04:22Z INFO: LLAppViewer::writeDebugInfo: Opening debug file C:\Users\Cyrus\AppData\Roaming\SecondLife\logs\debug_info.log

Share this post


Link to post
Share on other sites

odd, it still seems to be trying to remove textures from the cache location which is where it's dying each time, but it does seem to be starting to load the world based on the processAvatarAppearance: messages...

I would get with the Singularity Devs and send them the same info to see if they know what's up.... you luck will probably be better with them than to try and file a Jira for a TPV =/

At this point I've run out of obvious solutions, and I don't work on viewer code, so what I know is limited... unless someone happens to read this and know of any problems with Singularity, their devlopers are your best bet for a solution.

Share this post


Link to post
Share on other sites
You are about to reply to a thread that has been inactive for 3390 days.

Please take a moment to consider if this thread is worth bumping.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

×
×
  • Create New...