BSOD by nvidia driver?

Matallar · Jul 9, 2013

Hello all. I come seeking help.

I have recently just finished my build (about a week ago) and have been plagued with problems ever since. For the past week I have been runing tests and such to figure out what's causing it and have narrowed it down to the video drivers. This is also backed up by bluescreen viewer wich lists "nvlddmkm.sys" as the driver causing the problem.

I want to know why and what is causing this driver to fail and what I should do to remedy this. Here's what I already tried:

-Memtest for 32 hours (no errors)
-Prime95 for 11 hours (no errors)
-furmark for 3 hours (no errors)
-Complete reformat with Windows 7 profesional (Problem persists)

Here are my specs:
[Case] NZXT Phantom 820
[CPU] I7 4770k @ 4.4Ghz
[GPU] SLI EVGA 780GTX SC
[Ram] 32Gb Patriot Black Mamba 1600Mhz
[Mobo] Asus Sabertooth Z87
[PSU] 1500W Silverstone ST1500
[SSD] Raid 0 Samsung 840 Pro
[Cooler] Swiftech H220 Liquid Cooler
[MISC] A couple AP Corsair Fans

Also note, for the sake of testing, I am running only half of the ram, so 16gb and I removed the Overclock on the CPU to keep everything as stable as possible.

Ill attach the dumps to the post.
Any help would be greatly appreciated.
Thanks!

Matallar · Jul 9, 2013

Sorry, I hadn't read the post guidelines, here's the zip folder following the guidelines, however, I was denied access for some reason to perfmon /report, even though I ran it as admin and am the only account on the PC. Either way, here you go.

Patrick · Jul 9, 2013

Also note, for the sake of testing, I am running only half of the ram, so 16gb and I removed the Overclock on the CPU to keep everything as stable as possible.

Good call on removing the OC. It will help us a lot in troubleshooting. Troubleshooting OC'd systems is a royal pain.

Moving on, various bugchecks here:

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)

A system thread generated an exception that the error handler did not catch.

Usual causes are a bug in a device driver.

SYSTEM_SERVICE_EXCEPTION (3b)

An exception happened while executing a routine that transitions from non-privileged code to privileged code.

This bugcheck is generally related to a video driver issue.

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)

A kernel-mode driver attempted to access pageable memory at a process IRQL (Interrupt Request Level) that was too high.

Usual causes are a device driver has a bug and attempted to access invalid memory, the pagefile has been corrupted or there is a memory problem.

There's plenty of nvlddmkm.sys (nVidia video driver) throughout the dumps and on the stacks.

Ensure you have the latest video card drivers. If you are already on the latest video card drivers, uninstall and install a version or a few versions behind the latest to ensure it's not a latest driver only issue. Do note that you can go ahead and use beta drivers if you aren't having luck with rolling back a few versions, or with the latest.

AsIO fffff880`04b35000 fffff880`04b3b000 Wed Aug 22 05:54:47 2012 (5034ac67) 0000ea4f AsIO.sys

^

Asus PCProbe Utility. I'm going to recommend removing this and any other Asus utilities for troubleshooting purposes. They are known to cause issues.

Regards,

Patrick

Matallar · Jul 9, 2013

Hmm that's awfully weird because I paid a huge amount of attention to not install any of that Asus suite stuff, I even didn't use their motherboard CD and selectively downloaded directly from the website, ill go and take a look if I missed one.

I did read alot of problems with the newest Nvidia driver, I just did a complete uninstall reinstall with driver sweeper and in safe mode, and am awaiting the results of that. If it persists ill revert to an old driver.
Also, I lurked the forums a bit and read something about PSU causing similar problems. Now I have a complete overkill 1500W PSU, but I use only 1 PCIE cable per card.(Not to confuse, but per cable there's 1 6 pin and 1 8 pin wich is what the cards need). Do you think I should we two separate cables per card, or it shouldn't matter?

Matallar · Jul 9, 2013

Huh your right, I found ASIO in both my programfiles and programfiles(x86), although the uninstall .exe doesen't seem to work, should I just select and manually delete the folders?

Patrick · Jul 9, 2013

Edit~~~

You could give Download Revo Uninstaller Freeware - Free and Full Download - Uninstall software, remove programs, solve uninstall problems a try

Regards,

Patrick

Matallar · Jul 9, 2013

Alright, ill give that a try.

Also, I just recovered from a hard lock where my screens all shut off and a purple bar showed up on my main screen for a quick second. then they regained picture but was completly frozen, had to manually reset, so there was no dump. However checking the event viewer I had a kernel pnp critical error (because I shut it down unexpectedly) but also 3 errors, wich are the following:

Source WMI:
"Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected."

Source: Service Control Manager:
"A timeout (30000 milliseconds) was reached while waiting for a transaction response from the AudioEndpointBuilder service."

And the other is it just logging the manual shut down.

Aswell as a warning mentioning what im about to try to uninstall:
Source: Kernel-PnP
"The driver \Driver\WUDFRd failed to load for the device ACPI\PNP0A0A\2&daba3ff&2."

The ACPI was in the same folder as ASIO.

Matallar · Jul 9, 2013

Doesen't seem to find it, the only thing I remotly found related to Assus is in the autorun manager theres a service called Asus Com service, but for some reason I can't click remove on it.

Matallar · Jul 9, 2013

I don't know if it has anything to do with it, but something that's also really weird is that for some reason, the computer cannot keep the time. Every couple hours or so, the time will go back a couple hours or so. This is without shutting it off or doing anything to it manually. If I go manually and click sync with internet it syncs itself to the proper time and continues to work for awhile.

Very weird.

Patrick · Jul 9, 2013

Hi,

Sorry, I was at classes all day. Before removing ASACPI.sys and other utilities, you should try updating them first. If you don't want them at all, the control panel remove programs list should work just fine. If not, you could give removing them with CCleaner a try and then manually and carefully removing the registry keys yourself (please do not use a cleaner).

I don't know if it has anything to do with it, but something that's also really weird is that for some reason, the computer cannot keep the time. Every couple hours or so, the time will go back a couple hours or so. This is without shutting it off or doing anything to it manually. If I go manually and click sync with internet it syncs itself to the proper time and continues to work for awhile.

Sounds like your CMOS battery is on its way out. It happens - How to replace the CMOS battery.

Enable Driver Verifier, please. I want to see if we have a device driver issue going on here:

Driver Verifier:

What is Driver Verifier?
Driver Verifier is included in Windows 7, Windows Server 2008 R2, Windows Vista, Windows Server 2008, Windows 2000, Windows XP, and Windows Server 2003 to promote stability and reliability; you can use this tool to troubleshoot driver issues. Windows kernel-mode components can cause system corruption or system failures as a result of an improperly written driver, such as an earlier version of a Windows Driver Model (WDM) driver.
Essentially, if there's a 3rd party driver believed to be at issue, enabling Driver Verifier will help flush out the rogue driver by flagging it and causing your system to BSOD.
Before enabling Driver Verifier, it is recommended to create a System Restore Point:
Vista - START | type rstrui - create a restore point
Windows 7 - START | type create | select "Create a Restore Point"
How to enable Driver Verifier:
Start > type "verifier" without the quotes > Select the following options -
1. Select - "Create custom settings (for code developers)"
2. Select - "Select individual settings from a full list"
3. Check the following boxes -
- Special Pool
- Pool Tracking
- Force IRQL Checking
- Deadlock Detection
- Security Checks (Windows 7)
- Concurrentcy Stress Test (Windows 8)
- DDI compliance checking (Windows 8)
- Miscellaneous Checks
4. Select - "Select driver names from a list"
5. Click on the "Provider" tab. This will sort all of the drivers by the provider.
6. Check EVERY box that is NOT provided by Microsoft / Microsoft Corporation.
7. Click on Finish.
8. Restart.
Important information regarding Driver Verifier:
- If Driver Verifier finds a violation, the system will BSOD.
- After enabling Driver Verifier and restarting the system, depending on the culprit, if for example the driver is on start-up, you may not be able to get back into normal Windows because Driver Verifier will flag it, and as stated above, that will cause / force a BSOD.
If this happens, do not panic, do the following:
- Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.
- Once in Safe Mode - Start > type "system restore" without the quotes.
- Choose the restore point you created earlier.
If you did not set up a restore point, do not worry, you can still disable Driver Verifier to get back into normal Windows:
- Start > Search > type "cmd" without the quotes.
- To turn off Driver Verifier, type in cmd "verifier /reset" without the quotes.
- Restart and boot into normal Windows.
How long should I keep Driver Verifier enabled for?
It varies, many experts and analysts have different recommendations. Personally, I recommend keeping it enabled for at least 36-48 hours. If you don't BSOD by then, disable Driver Verifier.
My system BSOD'd, where can I find the crash dumps?
They will be located in C:\Windows\Minidump
Any other questions can most likely be answered by this article:
http://support.microsoft.com/kb/244617Using Driver Verifier to identify issues with Windows drivers for advanced users

Regards,

Patrick

Matallar · Jul 10, 2013

I was going to make a system restore point using the scearch bar when this BSOD came up "PAGE_FAULT_IN_NONPAGED_AREA" caused by "win32k.sys+8d2c1" this is the first time this driver is listed as the problem. Ill attach the dump.

The dump this one pertains to is the one ending in 5070.

Patrick · Jul 10, 2013

Hi,

The attached dump is of the PAGE_FAULT_IN_NONPAGED_AREA (50) bugcheck.

This indicates that invalid system memory has been referenced.

Usual causes are a bug in a device driver, hardware related memory issues, corrupt NTFS volume, anti-virus software.

There is mention of dxgmms1.sys (DirectX graphics mms) throughout the dump and on the stack.

Ensure you have the latest video card drivers. If you are already on the latest video card drivers, uninstall and install a version or a few versions behind the latest to ensure it's not a latest driver only issue. You can give beta video drivers a try if falling back to earlier versions and latest versions do not help.

-furmark for 3 hours (no errors)

-Memtest for 32 hours (no errors)

How long ago? I am going to recommend them again.

Regards,

Patrick

Matallar · Jul 10, 2013

I did those tests roughly 4 days ago. I have reformatted since though. I might try installing some legacy drivers that I knew worked before like you suggested if it crashes again here.

Patrick · Jul 10, 2013

Matallar said:
I might try installing some legacy drivers that I knew worked before like you suggested if it crashes again here.

Great idea, keep me updated.

Regards,

Patrick

Matallar · Jul 12, 2013

So I ran driver verifier for about two days now, it was fine until just about ten minutes ago where I was playing a game of Dota2 and when the match ended I got BSOD. Ill attach the dump to the post so you can check it out. Also, for the sake of testing, I tried to run both cards seperatly to see if it was a hardware problem with the graphic cards, but problems occured with both cards, regardless of wich one it was.

Thanks for helping out.

Patrick · Jul 12, 2013

Hi,

The latest attached dump is of the MEMORY_MANAGEMENT (1a), however verifier was enabled. We're likely dealing with a hardware issue here at this point, however, a few driver things I want to tackle. First off, navigate to Asus' website and get the latest version of ASACPI.sys. Ensure you update the AISuite, PCProbe and several other utilities available from your Asus motherboard page. My previous instructions were actually incorrect, and updating it should have been my only instruction, not remove it afterwards. My sincere apologies.

Second, in regards to video card drivers, did you follow my instructions about going to either beta drivers or continue to try older versions?

Regards,

Patrick

Matallar · Jul 12, 2013

No actually, that's one thing that I forgot to do, I have not reverted down to old drivers yet, I was testing the cards separately first. The only other driver available for the 780GTX is the 320.18 which is also know for having alot of bugs.
Should I still try it?

Patrick · Jul 12, 2013

Yep, give it a try.

Regards,

Patrick

Matallar · Jul 12, 2013

Alright I have reverted to older drivers and will continue testing.
Also I don't have any of the AISuite installed, should I? Or are those instructions there in case I did have them?

Patrick · Jul 12, 2013

Hi, good work.

Also I don't have any of the AISuite installed, should I? Or are those instructions there in case I did have them?

Please reinstall them. My previous instructions to update them were correct, however, I did not mean to add 'or remove them'.

Regards,

Patrick

BSOD by nvidia driver?

Active member

Attachments

Active member

Attachments

Sysnative Staff

Active member

Active member

Sysnative Staff

Active member

Active member

Active member

Sysnative Staff

Active member

Attachments

Sysnative Staff

Active member

Sysnative Staff

Active member

Attachments

Sysnative Staff

Active member

Sysnative Staff

Active member

Sysnative Staff