my game keeps crashing. constantly....I can play for a few minutes and then it crashes, each time i get this error message.
http://img339.imageshack.us/i/errorri.jpg/
and after spending 5-10 minutes verifying the files after i reload the game, it crashes a few minutes later, again with the same stupid error message.
can anybody help?
Comments
i deleted the entire 'hoggs' folder and repatched it. the game worked fine for about 30 minutes, now im getting the same ****ing error message as before, just a different corrupt model this time.
Now, i'm not saying this is 100% your problem, but it is best to eliminate all possibilities.
i completely uninstalled the game and reinstalled. after patching up i was able to play for about 10 minutes until the game crashed. no error message was given....it just crashed.
im fed up with this TRIBBLE. Im definately not gonna keep paying 15/month to play 1-2 minutes at a time.
will post the report next
System Information
Time of this report: 4/20/2011, 15:24:58
Machine name: CTSMAINPC
Operating System: Windows 7 Ultimate 32-bit (6.1, Build 7600) (7600.win7_gdr.101026-1503)
Language: English (Regional Setting: English)
System Manufacturer: INTEL_
System Model: DP35DP__
BIOS: Default System BIOS
Processor: Intel(R) Core(TM)2 Duo CPU E7200 @ 2.53GHz (2 CPUs), ~2.5GHz
Memory: 4096MB RAM
Available OS Memory: 3322MB RAM
Page File: 1320MB used, 5322MB 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 32bit Unicode
DxDiag Previously: Crashed in system information (stage 4). Re-running DxDiag with "dontskip" command line parameter or choosing not to bypass information gathering when prompted might result in DxDiag successfully obtaining this information
DxDiag Notes
Display Tab 1: No problems found.
Display Tab 2: No problems found.
Sound Tab 1: No problems found.
Sound Tab 2: No problems found.
Sound Tab 3: No problems found.
Sound Tab 4: No problems found.
Input Tab: No problems found.
DirectX Debug Levels
Direct3D: 0/4 (retail)
DirectDraw: 0/4 (retail)
DirectInput: 0/5 (retail)
DirectMusic: 0/5 (retail)
DirectPlay: 0/9 (retail)
DirectSound: 0/5 (retail)
DirectShow: 0/6 (retail)
Display Devices
Card name: NVIDIA GeForce GT 240
Manufacturer: NVIDIA
Chip type: GeForce GT 240
DAC type: Integrated RAMDAC
Device Key: Enum\PCI\VEN_10DE&DEV_0CA3&SUBSYS_069D10DE&REV_A2
Display Memory: 2391 MB
Dedicated Memory: 986 MB
Shared Memory: 1405 MB
Current Mode: 1920 x 1080 (32 bit) (60Hz)
Monitor Name: Generic PnP Monitor
Monitor Model: HP w2338h
Monitor Id: HWP281C
Native Mode: 1920 x 1080(p) (60.000Hz)
Output Type: HDMI
Driver Name: nvd3dum.dll,nvwgf2um.dll,nvwgf2um.dll
Driver File Version: 8.17.0012.7061 (English)
Driver Version: 8.17.12.7061
DDI Version: 10.1
Driver Model: WDDM 1.1
Driver Attributes: Final Retail
Driver Date/Size: 4/8/2011 00:14:00, 10071656 bytes
WHQL Logo'd: Yes
WHQL Date Stamp:
Device Identifier: {D7B71E3E-4FE3-11CF-FB68-91261CC2C535}
Vendor ID: 0x10DE
Device ID: 0x0CA3
SubSys ID: 0x069D10DE
Revision ID: 0x00A2
Driver Strong Name: oem24.inf:NVIDIA_SetA_Devices.NTx86.6.1:Section005:8.17.12.7061:pci\ven_10de&dev_0ca3
Rank Of Driver: 00E62001
Video Accel: ModeMPEG2_A ModeMPEG2_C ModeVC1_C ModeWMV9_C
Deinterlace Caps: {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
D3D9 Overlay: Supported
DXVA-HD: Supported
DDraw Status: Enabled
D3D Status: Enabled
AGP Status: Enabled
it's to the point where I can't even log into a character before the game crashes.
One thing I did notice is that my CPU is "pegging". I have a performance monitor that runs through my keyboard display that shows in running close to 99% of CPU. I have seen it run to 100%. Just wondering if there is some sort of memory/cpu leak now after this patch. Notes say they made some "stability tweaks" but that could have gone the other way.
Just.. BAM.. desktop.
Something got messed up hard in last night's patch.... and it is very frustrating.
Um, it has been working relatively fine since Beta for me ( with the exception of dynamic lighting was was fixed by the 11.3 ATI drivers ).
My computer falls asleep playing this game. This crashing did not start until this morning's patch. So, I don't think that "turn the graphics down" thing is the issue.
P.s. That is the first thing I tried. I turned off EVERY bell and whistle...
BAM ... Desktop
They broke something. It is as simple as that.
then the server went down for maintenance. when I logged on just a while ago i was able to play for about 10 minutes then the game crashed with no error message.
this TRIBBLE is really starting to **** me off.
i wonder if i should clean reinstall the game to then, i have been having some trouble with the game booting me out, but i allways thought it was me rig overheating. idk
Delete your corrupted hogg files, then verify then log into the game, Go into your video settings and set the lighting quality to LOW ! Now scroll down to the bottom of the video options and click on the button that says troubleshooting and scroll to the bottom and change the "limit frame rate" to 30...
do that and see if your game still crashes.... If it still crashes on corrupt files then your possibly looking at faulty memory or your hard drive is on the brink of death.
The reason your setting the lighitng to low is because the lighting in STO runs via software using your CPU not your graphics card, in fact a good chunk of the video settings is done via software (all thanks to the great season 3 patch).... this is why STO practically runs your CPU at 100% and if your CPU cooling is not that great then it will overheat and thats where weird things like crashes and corrupt data can come into play.
if the hogg files keep corrupting then you need to look for what may be causing the corruption
some things to look at
1. antivirs programs. some of these programs add a checsum to files that may be corrupting the files. panda 2011 has been noted for corrupting files on downloads
2. if using win7 or vista having the program installed in the porgram files folder will cause problems because of windows new security feature on files in that folder.
3. weak or failing CPU
4. bad or fauling hard drive
5. weak wireless connection
6. bad or failing memory
7. weak or failing power supply
runnning teamviewer will crash the game.
Process:
Process ID: 0x5b4
Process Name: C:\Users\Public\Games\Cryptic Studios\Star Trek Online\Live\GameClient.exe
Service Request Information:
Privileges: SeTcbPrivilege
Dr. Google reveals:
SeTcbPrivilege
SeTcbPrivilege gives service privilege to act as part of the operating system.
Allows a process to assume the identity of any user and thus gain access to the resources that the user is authorized to access. Typically, only low-level authentication services require this privilege.
Default setting: Not assigned.
Note that potential access is not limited to what is associated with the user by default; the calling process might request that arbitrary additional privileges be added to the access token. The calling process might also build an access token that does not provide a primary identity for tracking events in the audit log.
When a service requires this privilege, configure the service to log on using the Local System account, which has the privilege inherently. Do not create a separate account and assign the privilege to it.
Going outside to play but thought it was interesting... no app or system entries. Patch caused a perms problem??
It is the patch.
It is not system issues.
I expect them to have an emergency patch out sometime today or tomorrow, because of it.
I love how some people always look past the obvious.. the only thing that has changed in the last 24 hours in STO.... is the patch.
That is the most logical thing to look at.
Just ask in zone. I got DOZENS of instant replies from people saying "yeah the game has crashed "X" times on me today already, what is going on?" or something like that.
If you have a car,..and it works.. and you change one part on that car.. and it now no longer works.... I would say it is a safe assumption that the part that you changed is the problem. I don't go and start replacing the rest of the parts on the car to fix the problem. Logic would indicate what the problem is.
Just accept it. There is a problem in the patch.
except I've been having this issue for several days now....
And many people have been having this exact problem, just starting today. Now, may be something in the code that is incompatible with certain hardware/software combinations. Maybe you got hit last patch,..and this is just the moving forward of a relatively unseen problem since then.
But seriously.. ask around in zone chat today. You will get a chorus of people wondering "WTF"
I have a friend who is crashing now every 3 or so minutes.. he can't even play today. He was fine yesterday....so was I.
I was fine running the game UP UNTIL the patch. The notes clearly state that Cryptic did something to improve stability and I suggest that it had the opposite effect for many that were previously able to play without problems.....which I was one.
I still really think it has some to do with CPU overflow...but what do I know.
Also, please remember that we need much more information than just "my game crashes" to be able to help you. There can be many reasons for it and the better you can describe the crash, the more we can try to help.
Anything you can add to your posts can help here. Examples are in which zone you crash; what precisely crashes (launcher, game); when you crash (during PvP; in ESD, when in combat with NPCs...) and so forth.
Mostly during foundry play.
I played a mission called Resting Raptors and the game crashed 3 times during that mission. Each time that happened I was engaged in ground combat with romulan troops.
There were also some crashes a few days back while in the foundry editor. I am working on a city/outpost map for a time travel mission. Every time I place a new object into the map I preview it to get the placing of the objects etc. right.
After a few times around 3-4 times the game crashes. Luckily each time that happened there was an autosave file that restored my changes and work that I had done. I could then save it again. But it gets very frustrating and that is why I have currently suspended my project for now until this gets fixed.
As chance would happen.....that is where I am crashing in the same Foundry mission. I will attempt to try some "other" content and see what happens. I haven't been crashing in any previous Foundry missions and only once crash in the Foundry editor before the last update for that. But again, this was all before todays patch.
I wasn't doing any foundry missions -- both were Exploration missions on the Klingon side. Since I had no problems at all with the game until the patch I assumed it was a bug in the update and just stopped playing.
The first mission was an interior ship map and the second was planetary. I believe both involved combat with Federation troops, but I can't say for certain.
There are no new patch notes yet but I am hopefull that it will deal with these constant game crashes.