EVE Search - BSOD on sisi

All Channels

Test Server Feedback

BSOD on sisi

» 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)
davcin Caldari davcin Corp	Posted - 2009.02.15 21:48:00 - [1] Following this topic (EVE, and only EVE, making my system do a BSOD) I installed Vista 64 (I had Vista 32) and downloaded and updated everything with the 64 version drivers. Same problem, EVE, and only EVE, still crashes my computer with a Blue Screen of Death (BSOD). Tried the current sisi patch and it is even worst. With the current sisi version it crashed 5-10 sec after I came out from the station and now it crashes almost immediately when I see the ship in space. Any help? Any info I can send for you to check?
Sleepkevert Amarr Rionnag Alba	Posted - 2009.02.15 22:00:00 - [2] Make sure all your drivers are updated. The bluescreen is most likely a driver error or hardware fault. You might want to run a memory check (I think vista has a build in one, hold F8 during bootup to access it) to see if that is allright, and try to run a stresstest on the GPU (like 3dmark and the likes) and CPU (like prime95) to determine if those have any hardware / driver errors. The problem is, "a bluescreen" can be caused by a LOT of problems, hardware errors being the most likely of those. It might also be a program causing the error, but without any more info, we can't really tell. Next time you get a bluescreen, try to write down any info you get on screen, and post that in this thread as well. It may help in determining the source. _ Add your own line!
Astria Tiphareth Caldari 24th Imperial Crusade	Posted - 2009.02.15 22:05:00 - [3] Edited by: Astria Tiphareth on 15/02/2009 22:05:53 Given the change in OS, and a complete reinstall, it's certainly sounding like either problematic drivers or a hardware problem. Given that it's only EVE, most likely the first option, but no guarantees. Definitely worth a bug report, see here. I've not looked in-depth into Vista, but under XP, there's a folder under the Windows directory containing mini-dump files (C:\WINDOWS\Minidump on XP) which is the dump file from each BSOD, named by date. Sending that to CCP in a bug report may help locate the problem - it will definitely identify the crashing driver. As far as suggestions go in the mean time, as a fellow Creative X-Fi user (actually mine's an Auzentech) I'd recommend checking out the following ideas. First do you have onboard sound on your motherboard? If so, disable it (preferably in BIOS) and remove any drivers for it. Secondly, try uninstalling both Creative Alchemy and your sound drivers. Creative & Vista has been trouble for quite a few. See if EVE continues to cause a BSOD with that out of the picture. You may need to try a driver cleaner program to be sure you uninstalled properly unless their Vista uninstall is vastly better than XP. After that you're in the realms of graphics drivers, other more unusual 'drivers' like firewall miniports and other fun stuff like that, or hardware, but I'd expect hardware to cause a BSOD more unreliably or after a period. ___ My views may not represent those of my corporation, which is why I never get invited to those diplomatic parties... Environmental Effects
davcin Caldari davcin Corp	Posted - 2009.02.15 22:15:00 - [4] Originally by: Sleepkevert Make sure all your drivers are updated. The bluescreen is most likely a driver error or hardware fault. You might want to run a memory check (I think vista has a build in one, hold F8 during bootup to access it) to see if that is allright, and try to run a stresstest on the GPU (like 3dmark and the likes) and CPU (like prime95) to determine if those have any hardware / driver errors. The problem is, "a bluescreen" can be caused by a LOT of problems, hardware errors being the most likely of those. It might also be a program causing the error, but without any more info, we can't really tell. Next time you get a bluescreen, try to write down any info you get on screen, and post that in this thread as well. It may help in determining the source. Tried all that already (with the Vista 32 version) The new install haves all the drivers updated (64 version). A picture of the BSOD is already posted in the topic that I mention above, but here it is again (Vista 32 version): BSOD pic This error happens with EVE only! I run other games without any problem (Crysis, FarCry2 and others heavy GPU using games). It as to be a EVE problem. Maybe it is SLI related (I have a 9800 GX2). I don't know. What I know is it only happens when playing EVE. Meanwhile, I disabled "Scene 2" from the sisi version and the game isn't crashing immediately after I go to space anymore. My config: Windows Vista 64bit (updated) Creative X-Fi XtremeGamer 4Gb DDR3 Ram NVIDIA 9800GX2 600W psu Intel Quad 2.5 I also made a petition about this with no useful result. (sended dxdiag file at the time)
davcin Caldari davcin Corp	Posted - 2009.02.15 22:21:00 - [5] Originally by: Astria Tiphareth (...) First do you have onboard sound on your motherboard? If so, disable it (preferably in BIOS) and remove any drivers for it. Secondly, try uninstalling both Creative Alchemy and your sound drivers. Creative & Vista has been trouble for quite a few. See if EVE continues to cause a BSOD with that out of the picture. You may need to try a driver cleaner program to be sure you uninstalled properly unless their Vista uninstall is vastly better than XP. After that you're in the realms of graphics drivers, other more unusual 'drivers' like firewall miniports and other fun stuff like that, or hardware, but I'd expect hardware to cause a BSOD more unreliably or after a period. The BSOD happens with Alchemy installed and without. I had the BSOD before I installed it. No onboard sound (my board is a ASUS Maximus Extreme and the onboard sound is from a extra card that I didn't install, but disabled a related BIOS option anyway)
Sleepkevert Amarr Rionnag Alba	Posted - 2009.02.15 22:30:00 - [6] Edited by: Sleepkevert on 15/02/2009 22:35:11 Edited by: Sleepkevert on 15/02/2009 22:31:35 Google reveals a LOT of people have had this error and fixed it by setting a certain bios setting, though the setting is different for each case as well. Apparently the 0x0124 error can be caused by disk access, sound cards configured wrong, CPU settings, everything... The thing is, it's probably either bios or hardware related. Best thing you can try is to at least swap out your video card with an other one if you have one laying about, and see if the bluescreen persists with another card in your pc... Oh and, bugreporting it might be a good idea as well, be sure to include your minidump as well as a dxdiag file so CCP can analyse it. _ Add your own line!
Maria DeVille	Posted - 2009.02.16 10:15:00 - [7] Not sure if you have found your solution yet but I had a very similar problem but it was while I was on TQ. Lost an Astarte to it too The only way I have (temporarily) resolved it for me was to disable one of the GPU's on my 9800 GX2. Can't quite remember how I did it but google will find that answer. Not had a crash since but it is far from ideal since a GX2 is ment to run with both GPU's. Let us know if you try this and it works ok
Astria Tiphareth Caldari 24th Imperial Crusade	Posted - 2009.02.16 11:24:00 - [8] Originally by: davcin I also made a petition about this with no useful result. (sended dxdiag file at the time) Just to point out, there's a big difference between petitions and bug reports. Petitions are seen by GMs with little technical background. Bug reports go via bughunters to the QA team at CCP. If you meant bug report, then disregard . ___ My views may not represent those of my corporation, which is why I never get invited to those diplomatic parties... Environmental Effects
Molly Mayhem Caldari	Posted - 2009.02.16 11:58:00 - [9] I had a lot of crashes on TQ when I had forced AA enabled on my ATI card. When I set AA to "application controlled" and catalyst AI to low all of my TQ crashes stopped.
davcin Caldari davcin Corp	Posted - 2009.02.17 21:33:00 - [10] Originally by: Maria DeVille Not sure if you have found your solution yet but I had a very similar problem but it was while I was on TQ. Lost an Astarte to it too The only way I have (temporarily) resolved it for me was to disable one of the GPU's on my 9800 GX2. Can't quite remember how I did it but google will find that answer. Not had a crash since but it is far from ideal since a GX2 is ment to run with both GPU's. Let us know if you try this and it works ok Thanks, will try it. Still, if the problem didn't appear anymore then this is just a confirmation that it is a EVE problem SLI related.

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.