EVE Search - Crash after 20 ish seconds on both Sisi and Tranq

All Channels

Issues, Workarounds & Localization

Crash after 20 ish seconds on both Sisi and Tranq

» Click here to find additional results for this topic using Google

Monitor this thread via RSS [?]

Pages: [1] :: one page
Author	Thread Statistics \| Show CCP posts - 0 post(s)
General Paul Atomic Heroes Chain of Chaos	Posted - 2009.09.03 20:56:00 - [1] I've had eve working fine for nearly two years but just recently ran into major problems. My computer crashed (possibly due to this bug) and took down my windows and forced me to reformat my HDD, it blue screened, mentioned it was dumping the physical memory to disc then the HDD corrupted and wouldn't start. Ive had everything up and running and PC plays other games fine but jsut lately (not right after the reinstall) Eve seems to go to this freeze state, then it will blue screen and complain of possible driver issues/ and there isnt much I can do about it. same happens for Test server. don't suppose anyone has an idea whats going wrong? Operating System: Windows XP Home Edition (5.1, Build 2600) Service Pack 3 (2600.xpsp_sp3_gdr.090206-1234) Language: English (Regional Setting: English) System Manufacturer: alienware System Model: alienware BIOS: BIOS Date: 08/10/06 20:36:11 Ver: 08.00.12 Processor: Intel(R) Pentium(R) 4 CPU 3.60GHz (2 CPUs) Memory: 3328MB RAM Page File: 417MB used, 6847MB available Windows Dir: C:\WINDOWS DirectX Version: DirectX 9.0c (4.09.0000.0904) DX Setup Parameters: Not found DxDiag Version: 5.03.2600.5512 32bit Unicode ------------ DxDiag Notes ------------ DirectX Files Tab: No problems found. Display Tab 1: No problems found. Sound Tab 1: No problems found. Music Tab: No problems found. Input Tab: No problems found. Network Tab: No problems found. -------------------- DirectX Debug Levels -------------------- Direct3D: 0/4 (n/a) DirectDraw: 0/4 (retail) DirectInput: 0/5 (n/a) DirectMusic: 0/5 (n/a) DirectPlay: 0/9 (retail) DirectSound: 0/5 (retail) DirectShow: 0/6 (retail) --------------- Display Devices --------------- Card name: NVIDIA GeForce 7800 GTX Manufacturer: NVIDIA Chip type: GeForce 7800 GTX DAC type: Integrated RAMDAC Device Key: Enum\PCI\VEN_10DE&DEV_0091&SUBSYS_C5293842&REV_A1 Display Memory: 256.0 MB Current Mode: 1280 x 960 (32 bit) (60Hz) Monitor: Plug and Play Monitor Monitor Max Res: 1600,1200 Driver Name: nv4_disp.dll Driver Version: 6.14.0011.9038 (English) DDI Version: 9 (or higher) Driver Attributes: Final Retail Driver Date/Size: 7/14/2009 19:54:00, 5842816 bytes WHQL Logo'd: Yes WHQL Date Stamp: n/a VDD: n/a Mini VDD: nv4_mini.sys Mini VDD Date: 7/14/2009 19:54:00, 7741664 bytes Device Identifier: {D7B71E3E-43D1-11CF-BC78-22E500C2CB35} Vendor ID: 0x10DE Device ID: 0x0091 SubSys ID: 0xC5293842 Revision ID: 0x00A1 Revision ID: 0x00A1 Video Accel: ModeMPEG2_C ModeMPEG2_D ModeWMV9_B ModeWMV9_A 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 {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,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,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)=(YV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,
Lork Niffle Gallente The Scope	Posted - 2009.09.03 20:58:00 - [2] Can you give the stop code of the Blue screen. Also for the 7000 series of Geforce cards try using an older driver, it is a very outdated chipset and the newer drivers have problems on the older cards. Also try setting Interval to 1. ------------------------------------- Read my bio ingame for tips on how to live and not be called nasty names by me.
General Paul Atomic Heroes Chain of Chaos	Posted - 2009.09.03 21:06:00 - [3] Faulting application ExeFile.exe, version 6.10.1.22539, faulting module python25.dll, version 2.5.3100.1013, fault address 0x0002be77. Fault bucket 1369687930. I dont want to get the bluescreen again because when I get it it either restarts ok or currupts and consequently needs to reformat the C drive (all of it) Also reset the interval is easy to do ? Ill try re-rolling back to last set of drivers
Lork Niffle Gallente The Scope	Posted - 2009.09.03 21:10:00 - [4] For the 7000 series you are going to have to go back maybe a year or 2 preferable back to 2007/ late 2006 for the drivers you start at. ------------------------------------- Read my bio ingame for tips on how to live and not be called nasty names by me.
General Paul Atomic Heroes Chain of Chaos	Posted - 2009.09.03 21:16:00 - [5] Nvdia site says it should work fine (is backwards compatible) Anyway also found in system Error code 000000ea, parameter1 88fa1b00, parameter2 8a244578, parameter3 8a264d70, parameter4 00000001. I was brave and let eve hang and it didn't go to blue screen this time but simply froze completely (luckily it restarted)
Lork Niffle Gallente The Scope	Posted - 2009.09.03 21:20:00 - [6] Well would the nVidia site say oh, btw these drivers dont work with older cards? Of course they'll say that. But old card support especially with nVidia has been very poor especially on the 7000 series which was the last different chip they made, the current 200 series are remakes of the 9000 which are remakes of the 8000 series. I've had a 6800 and had to go back to 2005 before i got a stable driver. Just go back to 2006/7 and try them. ------------------------------------- Read my bio ingame for tips on how to live and not be called nasty names by me.
General Paul Atomic Heroes Chain of Chaos	Posted - 2009.09.03 21:23:00 - [7] Rolling back to 178 (2008) to try, I suppose since my HDD nuked itself I may have loaded the wrong or too modern drivers.. Still wouldn't explain why it messed up originally but we shall see.
General Paul Atomic Heroes Chain of Chaos	Posted - 2009.09.03 21:43:00 - [8] 178 failed to load my graphics card altogether, not good.
rofflesausage	Posted - 2009.09.03 23:07:00 - [9] Originally by: Lork Niffle For the 7000 series you are going to have to go back maybe a year or 2 preferable back to 2007/ late 2006 for the drivers you start at. Absolutely terrible advice. Both nVidia and ATI have very good processes for testing the latest drivers on old cards. Specifically nVidia use a unified driver architecture which means you never have the worry of older drivers working massively better. Sure, the odd FPS better here and there, reverting to a driver several years old for a graphics card? Utter madness. Please - don't do it. If you know a new release has a specific problem, sure roll back to a latter (but recent one). If you don't know of a specific problem then use the latest one.
Lork Niffle Gallente The Scope	Posted - 2009.09.04 08:15:00 - [10] Must i repeat. I have used a Asus 6800 back in 2008. The curretn at that time 180 caused blue screen issues in Directx9.0c games and software rendering. I rolled back to a 162 version and got a lot less blue screens. If you don't try how can you know if it doesn't fix the issue. For older cards it is generally the idea to either use the latest or move back a year. This is even more important for nVidia cards since since teh 8000 series the card has not change that means the latest drivers 175+ have all been based on the 8000 core found in the 9000 and 200 series. The 7000 is left on legacy support so the later drivers do not consider the older cards. nVidia or ATI won't fret over getting the really old cards workign especially when they are 4 generations behind. ------------------------------------- Read my bio ingame for tips on how to live and not be called nasty names by me.
Bahamir Minmatar	Posted - 2009.09.04 12:49:00 - [11] Originally by: General Paul DirectX Version: DirectX 9.0c (4.09.0000.0904) DX Setup Parameters: Not found DxDiag Version: 5.03.2600.5512 32bit Unicode Try to update your DirectX drivers, there are a lot of version of 9.0c, the last one is march 2009.
General Paul Atomic Heroes Chain of Chaos	Posted - 2009.09.04 16:42:00 - [12] Updateing Dx drivers now, DX 10 is not for me ?
General Paul Atomic Heroes Chain of Chaos	Posted - 2009.09.04 16:55:00 - [13] Ive got to say my Phantasms side chrome now look circular rather than with pixels, maybe it was DX that id forgot to update.
General Paul Atomic Heroes Chain of Chaos	Posted - 2009.09.04 16:59:00 - [14] ahh no crashed/hung again right after I d loaded the dx
General Paul Atomic Heroes Chain of Chaos	Posted - 2009.09.04 19:37:00 - [15] Error code 100000ea, parameter1 88cad440, parameter2 88ce68e8, parameter3 f78bacbc, parameter4 00000001.

Pages: [1] :: one page
First page \| Previous page \| Next page \| Last page

COPYRIGHT NOTICE
EVE Online, the EVE logo, EVE and all associated logos and designs are the intellectual property of CCP hf. All artwork, screenshots, characters, vehicles, storylines, world facts or other recognizable features of the intellectual property relating to these trademarks are likewise the intellectual property of CCP hf. EVE Online and the EVE logo are the registered trademarks of CCP hf. All rights are reserved worldwide. All other trademarks are the property of their respective owners. CCP hf. has granted permission to EVE-Search.com to use EVE Online and all associated logos and designs for promotional and information purposes on its website but does not endorse, and is not in any way affiliated with, EVE-Search.com. CCP is in no way responsible for the content on or functioning of this website, nor can it be liable for any damage arising from the use of this website.