Jump to content
  • 0
Sign in to follow this  
Followers 0

Crashes & Errors

Question

Posted

For awhile now I have been experiencing some major issues with my new system.

 

My specs are :

 

Intel Core i7 4770K 3.5GHz Quad Core
ASRock Z87E Mini ITX
G.SKILL Ripjaws X Series 16GB DDR3 1866 RAM
Gigabyte Geforce GTX 770 2GB Overclock Edition
Samsung 840 Series 500GB SSD
SeaSonic Platinium 760W PSU Modular
BitFenix Prodigy Mini ITX Black Case
27" 2560x1440 IPS LED Monitor & 24" 1920x1200 IPS LCD Monitor

 

Now there are 3 issues I have.

 

1. The screen will freeze and then go black, and then back to desktop with the message your driver has crashed and recovered.

2. The system will freeze, unfreeze, freeze, unfreeze...and keep doing that until I reboot the system (seems like it's using CPU, but not sure) And when I mean freeze, I can't move the mouse, then I can, then I cant. etc

3. It will just stop, and reboot. Random reboot.

 

For #1 I have of course tried different drivers without any real luck, some seem better than others but not really. And have done clean installs of these drivers. Based off other people, the latest betas fix all issues the 770s had.

 

Event Log has a bunch of stuff, not sure if any is helpful.

 

One is

 

taskhostex (1436) An attempt to open the file "C:\Users\Brendon\AppData\Local\Microsoft\Windows\WebCache\WebCacheV01.dat" for read only access failed with system error 32 (0x00000020): "The process cannot access the file because it is being used by another process. ".  The open file operation will fail with error -1032 (0xfffffbf8).

 

Another is,

 

The description for Event ID 14 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
 
If the event originated on another computer, the display information had to be saved with the event.
 
The following information was included with the event: 
 
\Device\Video3
abf5(1e98) 00000000 00000000
 
If there is a way to attach the entire Event Viewer I will do that, let me know how.
 
Any ideas, suggestions..
 

Share this post


Link to post
Share on other sites

25 answers to this question

  • 0

Posted

Could you use the program blue screen viewer to show exactly which drivers crashed? 

Have you overclocked your machine or gpu at all? 

Share this post


Link to post
Share on other sites
  • 0

Posted

The first issue, is 100% the graphics driver, but that problem seems to be the least of my worries, it seems to have resolved. At least it's not happening as often as it did before, the other 2 are my concern.

 

And no, no overclocking at all on anything.

Share this post


Link to post
Share on other sites
  • 0

Posted

Try your card in a friend or twos computer, try to replicate the activities that led up to the problem.  If it happens again possibly the GPU (RMA), if not then something like your motherboard might be the culprit

Share this post


Link to post
Share on other sites
  • 0

Posted

So I put my old card into my new system (the one having issues)

 

and its been running without issue. Now the new card is in the old system, and it seems to be fine as well (though I'm not really using it).

 

So it's the Videocard, but also sorta the PSU I think.

Share this post


Link to post
Share on other sites
  • 0

Posted

Interesting you have any friends with decent mobos or mobos at all?

Share this post


Link to post
Share on other sites
  • 0

Posted

No I do not,

 

I have the second computer I used to test it. As I said above.

 

The card seems to be running fine on the old system, but is that because im not doing anything on the old system, or is the card problamatic with some other part of my new system?

Share this post


Link to post
Share on other sites
  • 0

Posted

Let's assume the card is fine.

What could be interacting with it in my new system that could cause this? The MOBO, RAM, CPU?

Share this post


Link to post
Share on other sites
  • 0

Posted

If you are running 4 sticks of ram, pull out 2 and see if that changes anything.

Share this post


Link to post
Share on other sites
  • 0

Posted

Is that based on some theory? What would pulling out two sticks do, and that's a real question, not being rude :)

Share this post


Link to post
Share on other sites
  • 0

Posted

Your first issue sounds like a TDR116 error possibly related to a defective GPU or video memory, test your card with OCCT. Try test your RAM with memtest86+.

Share this post


Link to post
Share on other sites
  • 0

Posted


Is that based on some theory? What would pulling out two sticks do, and that's a real question, not being rude :)

 

It could be a compatibility/memory timing/voltage issue. I just went through this with a Gigabyte board on the new Z87 chipset. Almost identical to what symptoms you are seeing.

 

Is that memory model specifically listed as compatible on the motherboard mfg web-site? Either way that is where I would start

Share this post


Link to post
Share on other sites
  • 0

Posted

Try manually setting RAM timings and RAM voltage. Could be a SPD detection issue.

Share this post


Link to post
Share on other sites
  • 0

Posted

I am running the OCCT test on the card (in the old system) right now. See what happens.

 

Then tonight when I head to bed I will run the memtest on my new system (without the card)....then depending on that, will put the card back into the new system, and run both tests again.

 

 

Never actually looked at the motherboard mfg website for that information, I used a tool that did auto compatible stuff. So I will update when this stuff is done.

Share this post


Link to post
Share on other sites
  • 0

Posted

Test finished on old system, no errors. But it was ran for 45 minutes, how long am I suppose to run it for..

Share this post


Link to post
Share on other sites
  • 0

Posted

Only a few minutes into the test and I got this. 

 

So what does this mean, is it my memory? Then why am I having no issues with my old video card? 

 

 

Share this post


Link to post
Share on other sites
  • 0

Posted

So should I run the test on each single piece of RAM? Or is it still video card related, as the old one is running fine?

 

Basically, the ram is bad, I will test to see which one it is, if not all....but how do I know that is indeed the cause of my issues?

 

Once tested, run with only the good ram with new video card?

Share this post


Link to post
Share on other sites
  • 0

Posted

If the video card drivers were being loaded into one of your bad ram sections (or indeed any application code that was utilising them) it could have caused them to crash, same with kernel data. The RAM is the most likely culprit for all of your issues (Pretty much all data including some file system reads/writes can pass through ram so bad memory can cause a whole multitude of errors), But yes, the only way to know for sure which stick(s) are bad is to run the test on them 1 by 1.

Share this post


Link to post
Share on other sites
  • 0

Posted

So I tested each peice of RAM (which is only 2 sticks in total) on each slot, and MemTest found errors each time, 20+ errors, even 84 errors one time.

 

So now what? Is it my RAM or my Motherboard?

 

Also note, that MEM test (shown in the picture above) has weird CAS timings shown, but in the BIOS they are set correctly for the RAM i have...not sure if that is important.

Share this post


Link to post
Share on other sites
  • 0

Posted

So I tested each peice of RAM (which is only 2 sticks in total) on each slot, and MemTest found errors each time, 20+ errors, even 84 errors one time.

 

So now what? Is it my RAM or my Motherboard?

the only easy way to test that is get more ram and test those sticks

Share this post


Link to post
Share on other sites
  • 0

Posted

So I tested each peice of RAM (which is only 2 sticks in total) on each slot, and MemTest found errors each time, 20+ errors, even 84 errors one time.

 

So now what? Is it my RAM or my Motherboard?

 

Also note, that MEM test (shown in the picture above) has weird CAS timings shown, but in the BIOS they are set correctly for the RAM i have...not sure if that is important.

 

Did you get the chance to test your ram in any other computers? Or any other sticks of ram in yours. If it's a controller/board error, you're likely to see problems with any ram you put in, but if your ram works in another computer it could be a compatibility issue.

 

Have you tried setting all of your memory timings, speed, and voltage to their automatic or default settings?

Share this post


Link to post
Share on other sites
  • 0

Posted

Javik,

 

This system is brand new, so it's all default. I don't have another system that is the same, so I can't do that.

 

I am basically buying new ram, testing it, and if need be, returning it for a small fee. It really is the easiest solution at this moment. Will update when done.

Share this post


Link to post
Share on other sites
  • 0

Posted

So I finally got other ram, put it in my system, tested it and they had a bunch of errors.

 

So it's the motherboard? Any more tests I can do?

Share this post


Link to post
Share on other sites
  • 0

Posted

If you could test with another PSU that'd rule out that, but memtest errors are usually RAM, motherboard or CPU. Given that CPUs basically never fail, it's likely to be the motherboard at this point. Are you running the latest BIOS?

Share this post


Link to post
Share on other sites
  • 0

Posted

Yup, everything is new and updated.

 

So I suppose I can do the same thing with a MOBO, buy one..test...and return if I have too. It's just a lot more work.

Share this post


Link to post
Share on other sites
  • 0

Posted

So I picked up a Asus ROG Maximus VI Impact to test the last thing on my system, figured might as well go as high end as possible in case I am keeping it.

 

It's been running without issue for 6 days, which is test enough for me (the issue was more frequent than that).

 

Truth, it could be a different driver, could be the old MOBO just didn't like my RAM, could be other factors, but likely hood, it was my AsRock MOBO.

 

Thanks for all the help.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0

  • Recently Browsing   0 members

    No registered users viewing this page.