New
#41
Fingers crossed :)!
Thanks for the update.
BSOD with Qualcomm WLAN(?) - BCCode d1, 4a
-
-
New #42
I'm baaaack! These errors seem more insightful though, hopefully.
Ran fine for five days before crashing this morning. The first time around, I kept it in in sleep mode instead of shutting it off for about three days. I forgot one evening and did a cold restart, and when that seemed fine did it a second time this morning as a test.
It failed the test.
Two blue screens, back to back. Information is in the attached .zip file.
-
New #43
Hi,
The one of the new dumps doesn't hold very much information apart from being related to steam.exe.
The second is very much blaming the nVidia driver again
.
We're back to post #8, where I stated that there is a known issue with the 7xx series of GPUs
drivers and suggested to use the integrated graphics as a way stabilize the system for now.
-
New #44
Admittedly, I'm not particularly happy that the solution seems to be "wait for NVIDIA to fix their drivers."
This video card only had good reviews and was said to work with the motherboard fine; it seems astounding that I can't find more information about the situation if it was a driver dependent thing. Still, I guess I can afford to wait until the next set of NVIDIA drivers come out... or something.
Attached is one final set of logs, just to see if anything comes out of that before I give up on the matter for now.
Edit: As a final aside, of all the things that have been updated, it occurs to me that the BIOS has not received an update. Could this make a difference, or is it irrelevant to our problem?
Edit Edit: I think I may have found a solution. Some people have suggested taking the 314.22 drivers and modifying it to accept the GTX 760 as a driver on the system. http://forums.guru3d.com/showthread.php?t=377158 is an example of the process.
I've seen it a few times on the forum, so it seems like it could work. Do you think this is a good idea? Is it risk free?Last edited by asura8; 05 Sep 2013 at 09:45.
-
New #45
I advise against, no it is not risk free.
The kernel is a place where code can execute without limits with the utmost level of privilege
and the OS is trusting that the drivers know what they are doing,
Modifying the drivers can lead to data corruption, which is what the BSOD is trying to prevent
each time it detects a violation of the kernel rules.
If experienced professionals in big companies such as nVidia and AMD for example write a driver
and validating the driver internally before it hits millions if not billions of PC, but issues still pop-up
has something to say about the complexity of the manner.
By running a modified version of the driver you're basically a test subject.
I do not recommend this in any way shape or form.
-
New #46
Okay: so don't try a non-700 series driver that has been juryrigged. Got it.
I just considered that this is an EVGA Superclocked GTX760, so would it be worth using their 3rd party equipment to try turning down the clock speed on the GPU? This doesn't seem to me like it would be related to the stability issues, but...
Kinda running out of thoughts other than: "Pray for a better WHQL soon"
-
New #47
By all means you can do anything you feel that will mitigate the crashes it is your
own right to perform whatever you desire with the hardware you own.
But from a technical stand point I don't see how downclocking a processor, in this a GPU, that it's whole
purpose in life is to fulfill the wish of the software, in this case a driver, will help.
Sorry for your situation, you can take comfort to the fact that it may arrive any day now.
-
New #48
Operating under the assumption that it was simply the drivers/video card combination, I have uninstalled the video card+drivers, installed a GTX 460 in its place, and reinstalled a stable driver for that. I got a blue screen similar to the others.
I have now uninstalled those drivers and reinstalled with the newest driver (which was the previously mentioned unstable 320.46 WHQL), and will tell you if there are any further issues.
Is this a sign that it is more likely a bad PCI-E slot?
-
New #49
The dump prior to last did pertain to the GPU, which one was installed?
How did you go about un/installing the drivers between the switch?
The last dump shows signs of of a root-kit again, did you remove the suspicious file last time?
I don't see any active anti-virus protection running on the machine as well.
Download Microsoft Security Essentials and Malwarebytes, install and perform a full system scan
of both but not simultaneously.
It also shows a lot of I/O activity. Is the SSD or any of the drives for that matter
connected to directly to the motherboard?
Are you using a SATA controller add-in card of some sort?
Also regarding the RAM testing, you have the latest intel chipset Z87, which isn't compatible
with the latest releases of MEMtest so the testing performed earlier are not valid, sorry I missed it before.
-
New #50
I'll try to answer as much as I can...
The dump PRIOR to last should have been with the GTX 760, unless I missed a fast blue screen (which is possible) on reboot. It has happened before.
The suspicious file was just a registration tool for ASUS, so I didn't remove it. I could always do so in the next run.
Both the SSD and Internal HD are directly connected to the motherboard. There were additional devices attached (mouse, keyboard, external HD, webcam), though these were all present while the computer was running without the video card and having no issues.
Considering the new chipset, how likely is it that a memory problem was missed? Wouldn't that be unlikely since the computer appears to run fine without the video card?
I'll remove the video card to attempt to get some stability and run both of those security programs, though TDSS Killer has found nothing of note in the past. It only finds SOMETHING if I require it to verify signatures.
Edit: It crashed with the GTX 460 on another PCI-E slot, so I doubt it is that/
Quote
Related Discussions