|
#31
July 23rd, 2012, 03:06 PM
|
|||
|
|||
|
Alright thanks for the tips.
Fix for me: I downloaded a program called registry easy (you could probably use any other registry cleaning program) and that seemed to have cleared up a lot of conflicts. I haven't crashed yet but we'll see. I also found the successor to driver sweeper called driver fusion: http://treexy.com/products/driver-fusion.aspx This helped as well. (I thought had cleaned out everything but fusion found some extra stuff, not sure if that made the difference though, hard to say) Thirdly, I found a beta update that wasn't out when I first put my computer together for the xonar phoebus drivers that fix guess what, crashes with battlefield 3 and punkbuster... I wonder if that's the culprit? Even though I uninstalled the original phoebus drivers and used onboard sound for a while maybe residual registry was causing the problem. Well we'll see how it goes. And lastly as a rant, I bought another vertex 4 256gb for raid 0, and the drive turned out to be only 128gb despite saying 256 on the box and barcode on the drive. Dat luck...... Also my computer (windows and bios) can't seem to detect the hard drive, It was detected at first but then I restarted and can't find it. Messed with the cables, tried disabling the port and re-enabling but to no avail. Anyway kind of off topic but if you have any protips there. I couldn't find the hard drive under the managing section where I would format. Anyway :P I'll need to RMA it anyway haha. If new one doesn't work i'll mess with cables again. Edit: So far so good! I put everything back in and back together, enabled xmp, etc. Going to just play for a few hours. Edit: Well everything seems to be fixed! Like I said going to be RMAing the 128gb hard drive anyway but everything else is good. My friend got my battlefield 3 account banned so I was only able to test in non-punkbuster servers until he gets me a new one haha, but it didn't crash! I'll post back if anything happens, thanks for your help everyone! and MaDef! Last edited by Supcutie; July 24th, 2012 at 02:21 PM. 
|
|
#32
July 24th, 2012, 03:31 PM
|
||||
|
||||
|
Looks like maybe you found the problem and (hopefully) got it sorted out.
Not sure why you want to raid your SSD, unless your playing with lots of large files (ie; sequential file reads/writes such as databases, dvd/blueray files etc.). Outside of a benchmark I don't really think you'll see faster load times for the programs.
|
|
#34
August 25th, 2012, 03:40 AM
|
|||
|
|||
|
Hi,
I am having very similar issues to you, Supcutie. I am a new builder who just put together the following system: 3770k (stock) 2x EVGA GTX 670 FTW (stock OC) GeIL 16 GB 1600 MHz DDR3 (1.5V, CAS 9); no XMP, so 1333 MHz Asus Maximus V Formula Seasonic Platinum 1000W power supply Corsair H100 cooler Corsair 650D case 2x 128 GB Crucial M4 SSD WD Caviar Black 1 TB LG Blu-Ray RE Windows 7 Home Premium When I go into a 3D game, I will crash after a variable time of very smooth play. Crashing often means a drop in frames over ten seconds, followed by a freeze frame and strange audio (sharp, grinding beeps), and eventually a blue screen and/or automatic reboot. I admire how persistent you were with building. I have not gotten to the point of RMAing, but I have posted in forums and contacted EVGA and Blizzard. So far, the diagnostics have not helped. Do you have advice having had so much experience with the issue? Crosses fingers, jleon088 Last edited by jleon088; August 25th, 2012 at 03:46 AM.
|
|
#35
August 31st, 2012, 01:01 PM
|
|||
|
|||
|
Hey Jleon088, sorry you're having the issue.
It definitely is a toughy, I guess I'm lucky mine just happened to be a sound card driver issue. Anyway, if you haven't read through the entire thread I would recommend that first, maybe it will give you some ideas. If not, well let's see here, I'll list off some things you could think about... 1. I assume you don't have a sound card since it wasn't listed so I suppose that isn't the problem. 2. I am assuming this issue is after a fresh install? Install order of drivers/updates may be important for you. 3. The issue is going to be either software or hardware related. Usually a fresh install and proper drivers will eliminate the software portion, but it can still be a problem which is why I was so confused (beta sound drivers conflicting very specifically). 4. The way that I eventually isolated the issue was on the hardware end, which does take a long time but it worked. I simply swapped out every component and swapped the slots the components were in until the problem was narrowed down. Not sure if you have a friend to help you out or any spare parts lying around, but if you have tried everything and want to continue troubleshooting, try replacing hardware. -I guess I would start with graphics cards, with only one stick of ram in. (I'm assuming you ran prime95 and memtest etc) 4. Troubleshooting the issue did take pretty much all of my time everyday for almost two weeks, and it really bummed me out. Keep your head up though! The problem is somewhere and with enough troubleshooting it will be found ^_^ Last edited by Supcutie; August 31st, 2012 at 01:08 PM.
|
|
#36
September 2nd, 2012, 11:20 PM
|
|||
|
|||
|
I am also having problems with my GTX 670, except mine is from MSI.
I recently bought a computer from IBuyPower.com with an Nvidia MSI 670 GTX. It came preformatted so I installed Windows 7 on it and all the drivers. Everything was running great until I opened Deus Ex: Human Revolution and I get a driver error with excessive screen tearing followed by a blank screen. I am then minimized to my desktop where a notification in the bottom right says that the driver has stopped working and successfully recovered. I also did a burn test in Furmark with error 3 coming back. All games seem to work until about 15 seconds after initial rendering occurs. I've disabled the HD sound, and only have the base Nvidia graphics driver installed (no 3D vision or anything of the sort.) I've went as far as changing my registry to allow PCI-E 3.0, and have wiped my SSD once now. Also, my PSU is an 850W and I have updated the BIOS on my board ( Gigabyte GA-X79-UD3 -- 4x PCI-E x16, 6x SATA 6Gb/s) Dunno if it will help, but here's what my screen looks like after the driver goes kaput. http://sphotos-a.xx.fbcdn.net/hphoto...03863928_n.jpg Edit: Various Specs Intel® Core™ i7 3820 Processor (4x 3.60GHz/10MB L3 Cache) - Intel Core i7 3820 Processor Cooling Corsair Hydro Series H60 Liquid CPU Cooling System - ARC Dual Silent High Performance Fan Upgrade (Push-Pull Airflow) Memory 16 GB [4 GB X4] DDR3-1600 Memory Module - G.Skill Ripjaws X Video Card NVIDIA GeForce GTX 670 - 2GB - Single Card Video Card Brand Motherboard Gigabyte GA-X79-UD3 -- 4x PCI-E x16, 6x SATA 6Gb/s Power Supply 850 Watt - Corsair CMPSU-850AX Primary Hard Drive 256GB ADATA SP900 Optical Drive [12X Blu-Ray] LG BLU-RAY Reader, DVD±R/±RW Burner Combo Drive - Black Flash Media Reader / Writer 12-In-1 Internal Flash Media Card Reader/Writer - Black Sound Card Creative Labs Sound Blaster X-Fi Xtreme Audio Network Card Onboard LAN Network (Gb or 10/100) Last edited by Bellololol; September 2nd, 2012 at 11:24 PM.
|
|
#37
September 3rd, 2012, 05:51 AM
|
|||
|
|||
|
Hey Bell,
Screen tearing occurs when the fps you're running at is much higher than your monitor refresh rate, which is why vsync limits at 120, 60, 30, etc. (this is why adaptive vsync is pretty cool) Anyway that said, I'm not sure what you're describing is exactly screen tearing but nevertheless a rendering problem :P My first inkling would be that the card is overheating. Try downloading msi afterburner or evga precision x if you have an evga account and set a custom fan curve. I don't think heating should be a problem, but I did it to my cards just to make sure they don't overheat.
|
|
#38
September 5th, 2012, 04:52 AM
|
|||
|
|||
|
Hi everyone,
Thank you for the responses =) . I have done some troubleshooting over the past couple of weeks and will post some of my most important findings. 0) I noticed that I was crashing after playing 3D games (I will call it the "Brrr" error, since crashing was accompanied by a grinding noise). Also, I was getting unexpectedly low FPS. I was on 301.42 WHQL NVIDIA drivers. 1) I did most of the diagnostics Supercutie mentioned in his first post. Drivers were uninstalled as directed by EVGA (http://www.cybertechhelp.com/forums/...40#post1244440). 2) I reseated my two cards, switching their positions. NO BRRR ERROR since =O!!! I also reinstalled Windows, installing drivers in the following order: chipset, NVIDIA (no HD Audio), Audio, SATA, LAN, Wireless/Bluetooth. Again, no brrr error. What a huge leap forward!!! Let me know if anyone needs more details. 3) I was disappointed by in-game FPS and went through an (ongoing) benchmarking phase. I was interested in performance, temperatures, and PSU consistency: - Performance was low at the time of mentioned Windows reinstallation, but has inexplicably improved. I tried a variety of settings, and would be happy to share all results. I seem to be on par with similar systems in benchmarks (Unigine and 3DMark), and may have actually reached good in-game performance (player testimonies/comments). - Temperatures are harder. My CPU is happy (avg @ stock is 40C idle, 71C Prime95). My GPUs seems happy (avg @ stock OC is 43/40C idle, 74/70 Unigine), but I have a feeling heat may be in an issue (90F ambient, no side fans). This is hard to test because of my financial circumstances, but I am working towards it  . YouTubers and forums report around 78C Unigine temps for other 670 cards.- PSU is very consistent according to software. I am a little nervous about using a multimeter, but would like to invest in one soon. 4) This may be most relevant to Bell. I crashed playing Guild Wars 2, but in exactly Bell's experience (here called "Kernal Mode"). This crash usually does not involve a BSOD nor an automatic reboot. I will get a black screen with a quick spray of red lines, and my computer will freeze and recover. The cool part is that I finally have the aforementioned error message for reference. While originally an isolated incident, the Kernal Mode error has come up a lot recently, even while web browsing (overclocked and out-of-the-box configurations; 301.42 WHQL and 306.02 beta). I will be researching more now, and here is a first link: http://answers.microsoft.com/en-us/w...c-3ecd6650f91d . Let us know your findings as well. Error Message: http://oi50.tinypic.com/ekgvpe.jpg Please assist, jleon088 Last edited by jleon088; September 5th, 2012 at 08:57 PM.
|
 |
| Bookmarks |
«
Previous Topic
|
Next Topic
»
| Topic Tools | |
|
|
All times are GMT +1. The time now is 05:33 PM.
