Windows 7 BSOD by nvidia driver?

[Matallar]

Hello! I am new to this forum and come seeking help.
I have recently just finished my build and ever since I have been getting BSOD's. Sometimes sevral at once, and sometimes a couple hours apart. So far, I have narrowed it down to the video cards, seeing as blue screen viewer shows "nvlddmkm.sys" as the cause every time.

However I can't seem to figure out why this driver is crashing.
I have ran memtest86+ for 32Hours with no errors, prime95 for a full night with no errors aswell, and odly enough, furmark also ran for 3 hours with out any problems.

I have also disabled SLI, in hopes of finding a card that might be the culprit but to no avail.
I am seeking advice and maybe a more accurate estimation of what the problem could be.

My specs are:
[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

Ill attach my dumps.

 

[Matallar]

Here's the dumps using one of those programs that do it for you. Hadn't read before I posted...

 

[usasma]

Only 111 Windows Updates installed. Most systems have 160 or more. Please visit Windows Update and get ALL available updates (it may take several trips to get them all).

No Hard Drives listed in MSINFO32. Please do this:

MSINFO32:
Please go to Start and type in "msinfo32.exe" (without the quotes) and press Enter
Save the report as an .nfo file, then zip up the .nfo file and upload/attach the .zip file with your next post.
Also, save a copy as a .txt file and include it also (it's much more difficult to read, but we have greater success in getting the info from it).

If you're having difficulties with the format, please open an elevated (Run as administrator) Command Prompt and type (or copy/paste) "msinfo32 /nfo %USERPROFILE%\Desktop\TEST.NFO" (without the quotes) and press Enter. Then navigate to Desktop to retrieve the TEST.NFO file. If you have difficulties with making this work, please post back. Then zip up the .nfo file and upload/attach the .zip file with your next post.

Drivers for your USB 3.0 Controller aren't installed, please install them

4 memory dumps, 3 different BSOD error codes, all point to nVidia video drivers
Please update with the latest version available at World Leader in Visual Computing Technologies | NVIDIA .

MSI Afterburner (along with Riva Tuner and EVGA Precision) are known to cause BSOD's in some Windows systems (it's driver is usually RTCore64.sys). Please un-install it immediately! If using Corsair Link2 it may be a part of that also.

If you're overclocking, please stop the overclock while we're troubleshooting. Feel free to resume the overclock once the system has been stabilized.

Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

ALSysIO64.sys Sun Apr 19 15:41:04 2009 (49EB7E50)
Core Temp - CPU temperature monitor
Link Removed




Analysis:
The following is for informational purposes only.

[FONT=lucida console]**************************Tue Jul  9 01:07:58.703 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\070913-12885-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:00:20.404[/B]
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by :[B]nvlddmkm.sys ( nvlddmkm+180a82 )[/B]
BugCheck [B]1000007E, {ffffffffc000001d, fffff880059eba82, fffff8800dca8048, fffff8800dca78a0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: ffffffffc000001d, The exception code that was not handled
Arg2: fffff880059eba82, The address that the exception occurred at
Arg3: fffff8800dca8048, Exception Record Address
Arg4: fffff8800dca78a0, Context Record Address
BUGCHECK_STR:  0x7E
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID: [B]X64_0x7E_BAD_IP_nvlddmkm+180a82[/B]
CPUID:        "Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: [B]3500[/B]
  BIOS Version                  1007
  BIOS Release Date             05/17/2013
  Manufacturer                  ASUS
  Product Name                  All Series
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jul  8 22:25:57.590 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\070813-6739-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:36:11.291[/B]
Probably caused by :[B]nvlddmkm.sys ( nvlddmkm+180a82 )[/B]
BugCheck [B]3B, {c000001d, fffff88005a3aa82, fffff8800d4dc800, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 00000000c000001d, Exception code that caused the bugcheck
Arg2: fffff88005a3aa82, Address of the instruction which caused the bugcheck
Arg3: fffff8800d4dc800, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  FlashPlayerPlu
FAILURE_BUCKET_ID: [B]X64_0x3B_nvlddmkm+180a82[/B]
CPUID:        "Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: [B]3500[/B]
  BIOS Version                  1007
  BIOS Release Date             05/17/2013
  Manufacturer                  ASUS
  Product Name                  All Series
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jul  8 21:50:41.318 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\070813-13010-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:00:55.019[/B]
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by :[B]nvlddmkm.sys ( nvlddmkm+61a02 )[/B]
BugCheck [B]3B, {c000001d, fffff880058bba02, fffff880121cf440, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 00000000c000001d, Exception code that caused the bugcheck
Arg2: fffff880058bba02, Address of the instruction which caused the bugcheck
Arg3: fffff880121cf440, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  firefox.exe
FAILURE_BUCKET_ID: [B]X64_0x3B_nvlddmkm+61a02[/B]
CPUID:        "Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: [B]3500[/B]
  BIOS Version                  1007
  BIOS Release Date             05/17/2013
  Manufacturer                  ASUS
  Product Name                  All Series
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jul  8 21:50:20.517 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\070813-5475-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:00:34.218[/B]
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by :[B]nvlddmkm.sys ( nvlddmkm+441a82 )[/B]
BugCheck [B]D1, {fffff28011c8a320, 2, 0, fffff88005c79a82}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: fffff28011c8a320, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88005c79a82, address which referenced memory
BUGCHECK_STR:  0xD1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]X64_0xD1_nvlddmkm+441a82[/B]
CPUID:        "Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: [B]3500[/B]
  BIOS Version                  1007
  BIOS Release Date             05/17/2013
  Manufacturer                  ASUS
  Product Name                  All Series
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/FONT]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.

[FONT=lucida console]**************************Tue Jul  9 01:07:58.703 2013 (UTC - 4:00)**************************
intelppm.sys                Mon Jul 13 19:19:25 2009 (4A5BC0FD)
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
CORSGKB.sys                 Mon Jun 20 22:38:24 2011 (4E000420)
AsIO.sys                    Wed Aug 22 05:54:47 2012 (5034AC67)
HECIx64.sys                 Mon Dec 17 14:32:21 2012 (50CF7345)
iaStorA.sys                 Mon Jan 14 13:00:27 2013 (50F447BB)
dump_iaStorA.sys            Mon Jan 14 13:00:27 2013 (50F447BB)
iaStorF.sys                 Mon Jan 14 13:00:29 2013 (50F447BD)
nvhda64v.sys                Mon Feb 25 00:27:35 2013 (512AF647)
e1d62x64.sys                Tue Feb 26 19:23:37 2013 (512D5209)
RTKVHD64.sys                Tue Mar  5 08:21:03 2013 (5135F13F)
nvlddmkm.sys                Fri Jun 21 05:06:16 2013 (51C41788)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jul  8 22:25:57.590 2013 (UTC - 4:00)**************************
[COLOR=RED][B]ALSysIO64.sys               Sun Apr 19 15:41:04 2009 (49EB7E50)[/B][/COLOR]
[COLOR=RED][B]RTCore64.sys                Mon Mar 11 01:32:06 2013 (513D6C56)[/B][/COLOR]
[/FONT]

Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
e1d62x64.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
Link Removed
Link Removed
Link Removed
Link Removed

 

[Matallar]

Alright, here attached is the MSINFO that you asked for.

Also, I had already assumed that I would need to remove the overclocks so I already did that, and intead of runing the full 32gb of ram im only running 16gb.

Ill complete all the windows updates, however I sometimes have problems where they freeze halfway into installing (About 1 out 2) so it's difficult.

As for the USB 3.0 Controller, this was another problem. When I downloaded it directly from the Assus website for my motherboard, the install would give a blank error (like an error box with a circled red X but with no description at all, not a single letter). So I then decided to install the driver directly from the motherboard CD, that succeded but I was plagued with CONSTANT BSOD about every minute or so after booting up. Unistalling it fixed it, so I haven't put it back on since.

Ill uninstall EVGA precision here, aswell as for corsair link, I have corsair K90 Keyboard configuration installed, should I remove that?

Also, all the links at the bottom of your post, are those all things I should install?

 

[usasma]

First the stuff that I found in MSINFO32, then I'll answer your questions.

You have 3 SSD's, SSD's were temperamental when they first came out, but their reliability has improved greatly over the last year or two. There are 2 things that MUST be checked on systems with BSOD's and SSD's:

1) That the SSD firmware is the latest available for the SSD
2) That the storage controller drivers on the motherboard are the most recent. They must date from late 2012 or later. This is ALL controllers, not just the one that the SSD is attached to.

Your Intel RAID storage driver (iaStorV.sys) dates from before mid-2013 (actually it's from 2010) and isn't good for SSD's. Try this driver (I got this link on 10 Jul 2013):
Link Removed
Use the SetupRST.exe file - the other 2 are the "preinstall" drivers for use when first installing an OS that doesn't have these drivers. If it doesn't install, post back and I'll research it further.

USB 3.0 drivers aren't installed (as you already know). I have to wonder why the drivers won't install properly - and I suspect a damaged USB 3.0 controller. If this is the case, it's possible that it's causing the issues and that the BSOD's won't stop until the mobo is replaced. Right now this is just speculation, but keep it in mind for when we're further along in the attempts to fix this.

No need to un-install the Corsair Keyboard software. The Corsair Link2 was a guess on my part as I wasn't able to look at the MSINFO32 report.

The EVGA Precision X isn't the same thing as the EVGA Precision software. No need to un-install it as it's not known to cause BSOD's (but if it's un-installed, leave it off until the system is stabilized - just in case)

Everything below the is just for documentation, there's no need to do anything with it.:

Analysis:
The following is for informational purposes only.

I have to wonder if your Windows Update problems are related to the USB controller issue. What we'll be looking for (in the long run) is that we've fixed all the 3rd party (non-Windows) driver problems and then we've ruled out most hardware issues and Windows issues.

Since you suspect your video cards, it's important that you:
- download a fresh set of the latest, Win7 compatible drivers from World Leader in Visual Computing Technologies | NVIDIA
- un-install the current video drivers from your system
- install the freshly downloaded video drivers
- monitor for further BSOD's
2 paragraphs below this is a link to the hardware diagnostics that include video stress tests, try them after you've replaced the video drivers (if you're still getting BSOD's).

The next step is to see if the system continues to BSOD. If it does, zip up the contents of the C:\Windows\Minidump folder and upload it with the next post. Analysis of the new memory dumps will let us know if the 3rd party driver issues have been dealt with. We'll continue this step until all of the 3rd party driver issues are "fixed"

Once they're all fixed, then you'll try these 2 procedures to see if you can isolate a hardware problem:
- Link Removed (this also contains tests for your video cards)
- Link Removed

Somewhere in all of this, you'll also have to do a clean install of Windows ( Link Removed ) in order to rule out Windows as a problem.

Once you've done all of this you'll have a good idea what components are left

 

[Matallar]

Alright, thanks for the reply. Im currently at work for another 8 hours so i wont be able to try anything until I get home. Ill get back to you as soon as i've completed everything.

 

[Matallar]

Alright, so I used the magician software and updated the firmware on the SSD, what was odd though is that one of them had the latest firmware installed, and the other didn't. I also updated the Intel Raid storage driver.

I have already installed a fresh copy of windows 3 times, but have no problems in doing it again to be honest. Also, all the windows updates are applied, and I have already done a fresh install of the video drivers using the exact method you posted. I also took the liberty of trying the cards alone ( removed one and tried to run them solo) and problems still persist.

Here's a new dump for you.

Also maybe this could point you to something. The windows time on the bottom left of the desktop resets every so often to the last time it was updated by checking the internet. I have resorted to manually telling it check the web for the time, to which it updates correctly and will continue for a short time before resetting.

EDIT: Also please note that I was running driver verifier while this happened and that event viewer in the windows system had no critical error, error or warnings to report about the indecent.

 

[usasma]

From your description of the other issues, I'm pretty certain that this is a low-level issue - most likely your motherboard. But this is just a hunch at this point - don't go out and buy a new mobo based on this alone.

The RTCore64.sys driver is still installed. It is the most likely 3rd party problem as it's a known BSOD cause.
Have you removed MSI Afterburner/Riva Tuner/EVGA Precision? This driver has to be ruled out before we can say that all the 3rd party stuff is fixed.

Could you please provide this info? It'll show the majority of notable events in Event Viewer:

- open Event Viewer (eventvwr.msc)
- expand the Custom Views category (left click on the > next to the words "Custom Views")
- right click on Administrative Events
- select "Save all Events in Custom View as..."
- save the file as Admin.evtx
- zip up the file (right click on it, select "Send to", select "Compressed (zipped) folder")
- upload it with your next post (if it's too big, then upload it to a free file-hosting service and post a link here).

Corsair Gaming Keyboard driver continues to show up in the dumps. Although not essential, it might be a good idea to un-install it to see if that makes any difference.

Running Driver Verifier won't necessarily cause crashes, especially if this is a hardware issue. It's good to know that it's been run tho', as this will provide further evidence for a hardware problem. And, since you've already reinstalled Windows several times, there's probably nothing significant to be gained by doing it again.

Please get a head start on the hardware diagnostics here: Link Removed

Analysis:
The following is for informational purposes only.

[FONT=lucida console]**************************Thu Jul 11 22:32:02.163 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\071113-5928-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 5:20:30.999[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13702 )[/B]
BugCheck [B]1A, {41201, fffff68000794a80, 8ab00003f7b10867, fffffa8011703b50}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 0000000000041201, The subtype of the bugcheck.
Arg2: fffff68000794a80
Arg3: 8ab00003f7b10867
Arg4: fffffa8011703b50
BUGCHECK_STR:  0x1a_41201
PROCESS_NAME:  dota.exe
FAILURE_BUCKET_ID: [B]X64_0x1a_41201_VRF_nt!_??_::FNODOBFM::_string_+13702[/B]
CPUID:        "Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: [B]3500[/B]
  BIOS Version                  1007
  BIOS Release Date             05/17/2013
  Manufacturer                  ASUS
  Product Name                  All Series
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/FONT]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.

[FONT=lucida console]**************************Thu Jul 11 22:32:02.163 2013 (UTC - 4:00)**************************
intelppm.sys                Mon Jul 13 19:19:25 2009 (4A5BC0FD)
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
CORSGKB.sys                 Mon Jun 20 22:38:24 2011 (4E000420)
ALSysIO64.sys               Sat Jul  9 20:27:45 2011 (4E18F201)
HECIx64.sys                 Mon Dec 17 14:32:21 2012 (50CF7345)
e1d62x64.sys                Tue Feb 26 19:23:37 2013 (512D5209)
RTKVHD64.sys                Tue Mar  5 08:21:03 2013 (5135F13F)
[COLOR=RED][B]RTCore64.sys                Mon Mar 11 01:32:06 2013 (513D6C56)[/B][/COLOR]
dump_iaStorA.sys            Mon Mar 18 19:36:36 2013 (5147A504)
iaStorA.sys                 Mon Mar 18 19:36:36 2013 (5147A504)
iaStorF.sys                 Mon Mar 18 19:36:37 2013 (5147A505)
nvlddmkm.sys                Fri Jun 21 05:06:16 2013 (51C41788)
[/FONT]

Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
e1d62x64.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed

 

[Matallar]

Alright I have uninstalled EVGA precision and the Corsair Keyboard Driver, I will attach what you asked me to do as well. I kinda doubt it worked correctly though since you mentioned it might be too big, but my file once zipped is extremely small.

Also, should I continue to run driver verifier? I have since turned it off after the last BSOD.

 

[Matallar]

Also on the topic of my motherboard, I just checked the Assus website and a new version of the BIOS came out two days ago (the 11th) stating "Improves stability". Ill give it a try tomorow, seeing as im to tired to do it tonight.

 

[usasma]

The upload is fine, different systems have different sizes.
In your case, there's issues with the ACPI\PNP0A0A (AMD A00 Interface).
I'd:
1) Update the AMDA00 Interface driver. If you can't locate it, install the Asus AISuite as it's contained in there. Then check to see if the errors are fixed in the Admin.evtx logfile.
2) Run stress tests on your CPU to see if that may be the cause. Link Removed

Don't bother to run Driver Verifier, we're pretty certain that this is a hardware problem - and if not, you've covered most of the problem 3rd party drivers.

Looking forward to the BIOS update - be very, very careful with it tho!

 

[Matallar]

Alright the BIOS update went well and I now have the new version installed. While i'm at work today, ill run the CPU stress tests and see if I get different results then the ones I got a couple days ago when there was still no errors after 9 hours.

I also installed the AISuite like you suggested that I got from the assus website here Link Removed

I proceeded to install all the utilities that were in the Aisuite because I wasn't sure which one had the needed .sys file.

 

[Matallar]

Alright, so I ran prime 95 during my time at work. And interestingly I got an error, I was using the small FFT setting.

[Jul 13 13:00] Test 1, 800000 Lucas-Lehmer iterations of M172031 using FFT length 12K.
[Jul 13 13:02] Test 2, 800000 Lucas-Lehmer iterations of M163839 using FFT length 12K.
[Jul 13 13:04] Test 3, 800000 Lucas-Lehmer iterations of M159745 using FFT length 12K.
[Jul 13 13:07] Test 4, 800000 Lucas-Lehmer iterations of M157695 using FFT length 12K.
[Jul 13 13:09] Test 5, 800000 Lucas-Lehmer iterations of M155649 using FFT length 12K.
[Jul 13 13:11] Test 6, 800000 Lucas-Lehmer iterations of M153599 using FFT length 12K.
[Jul 13 13:13] Test 7, 800000 Lucas-Lehmer iterations of M147455 using FFT length 12K.
[Jul 13 12:15] Self-test 12K passed!
[Jul 13 12:15] Test 1, 380000 Lucas-Lehmer iterations of M280335 using FFT length 14K.
[Jul 13 12:17] Test 2, 380000 Lucas-Lehmer iterations of M278527 using FFT length 14K.
[Jul 13 12:18] Test 3, 380000 Lucas-Lehmer iterations of M274335 using FFT length 14K.
[Jul 13 12:19] Test 4, 380000 Lucas-Lehmer iterations of M270335 using FFT length 14K.
[Jul 13 12:20] Test 5, 380000 Lucas-Lehmer iterations of M266241 using FFT length 14K.
[Jul 13 12:22] Test 6, 380000 Lucas-Lehmer iterations of M262143 using FFT length 14K.
[Jul 13 12:23] Test 7, 380000 Lucas-Lehmer iterations of M260335 using FFT length 14K.
[Jul 13 12:24] Test 8, 460000 Lucas-Lehmer iterations of M250519 using FFT length 14K.
[Jul 13 12:26] Test 9, 460000 Lucas-Lehmer iterations of M245759 using FFT length 14K.
[Jul 13 12:27] Test 10, 460000 Lucas-Lehmer iterations of M245281 using FFT length 14K.
[Jul 13 12:29] Test 11, 460000 Lucas-Lehmer iterations of M243713 using FFT length 14K.
[Jul 13 12:30] Self-test 14K passed!
[Jul 13 12:30] Test 1, 340000 Lucas-Lehmer iterations of M319487 using FFT length 16K.
[Jul 13 12:32] Test 2, 340000 Lucas-Lehmer iterations of M315393 using FFT length 16K.
[Jul 13 12:33] Test 3, 340000 Lucas-Lehmer iterations of M311295 using FFT length 16K.
[Jul 13 12:34] Test 4, 340000 Lucas-Lehmer iterations of M308295 using FFT length 16K.
[Jul 13 12:35] Test 5, 340000 Lucas-Lehmer iterations of M307201 using FFT length 16K.
[Jul 13 12:37] Test 6, 380000 Lucas-Lehmer iterations of M291913 using FFT length 16K.
[Jul 13 12:38] Test 7, 380000 Lucas-Lehmer iterations of M286719 using FFT length 16K.
[Jul 13 12:39] Test 8, 380000 Lucas-Lehmer iterations of M282625 using FFT length 16K.
[Jul 13 12:41] Test 9, 380000 Lucas-Lehmer iterations of M280335 using FFT length 16K.
[Jul 13 12:42] Test 10, 380000 Lucas-Lehmer iterations of M278527 using FFT length 16K.
[Jul 13 12:44] Test 11, 380000 Lucas-Lehmer iterations of M274335 using FFT length 16K.
[Jul 13 12:45] Test 12, 380000 Lucas-Lehmer iterations of M270335 using FFT length 16K.
[Jul 13 12:46] Self-test 16K passed!
[Jul 13 12:46] Test 1, 800000 Lucas-Lehmer iterations of M135169 using FFT length 8K.
[Jul 13 12:48] Test 2, 800000 Lucas-Lehmer iterations of M172031 using FFT length 8K.
[Jul 13 12:49] Test 3, 800000 Lucas-Lehmer iterations of M163839 using FFT length 8K.
[Jul 13 12:50] Test 4, 800000 Lucas-Lehmer iterations of M159745 using FFT length 8K.
[Jul 13 12:52] Test 5, 800000 Lucas-Lehmer iterations of M157695 using FFT length 8K.
[Jul 13 12:53] Test 6, 800000 Lucas-Lehmer iterations of M155649 using FFT length 8K.
[Jul 13 12:54] Test 7, 800000 Lucas-Lehmer iterations of M153599 using FFT length 8K.
[Jul 13 12:55] Test 8, 800000 Lucas-Lehmer iterations of M147455 using FFT length 8K.
[Jul 13 12:57] Test 9, 800000 Lucas-Lehmer iterations of M143361 using FFT length 8K.
[Jul 13 12:58] Test 10, 800000 Lucas-Lehmer iterations of M141311 using FFT length 8K.
[Jul 13 12:59] Test 11, 800000 Lucas-Lehmer iterations of M135169 using FFT length 8K.
[Jul 13 13:01] Test 12, 800000 Lucas-Lehmer iterations of M172031 using FFT length 8K.
[Jul 13 13:02] Self-test 8K passed!
[Jul 13 13:02] Test 1, 560000 Lucas-Lehmer iterations of M210415 using FFT length 10K.
[Jul 13 13:03] Test 2, 560000 Lucas-Lehmer iterations of M208897 using FFT length 10K.
[Jul 13 13:04] Test 3, 560000 Lucas-Lehmer iterations of M204799 using FFT length 10K.
[Jul 13 13:06] Test 4, 560000 Lucas-Lehmer iterations of M200705 using FFT length 10K.
[Jul 13 13:07] Test 5, 560000 Lucas-Lehmer iterations of M196607 using FFT length 10K.
[Jul 13 13:08] Test 6, 560000 Lucas-Lehmer iterations of M194561 using FFT length 10K.
[Jul 13 13:09] Test 7, 560000 Lucas-Lehmer iterations of M188415 using FFT length 10K.
[Jul 13 13:11] Test 8, 560000 Lucas-Lehmer iterations of M186369 using FFT length 10K.
[Jul 13 13:12] Test 9, 560000 Lucas-Lehmer iterations of M184319 using FFT length 10K.
[Jul 13 12:13] Self-test 10K passed!
[Jul 13 12:13] Test 1, 800000 Lucas-Lehmer iterations of M143361 using FFT length 12K.
[Jul 13 12:15] Test 2, 800000 Lucas-Lehmer iterations of M141311 using FFT length 12K.
[Jul 13 12:18] Test 3, 800000 Lucas-Lehmer iterations of M135169 using FFT length 12K.
[Jul 13 12:20] Test 4, 460000 Lucas-Lehmer iterations of M250519 using FFT length 12K.
[Jul 13 12:21] Test 5, 460000 Lucas-Lehmer iterations of M245759 using FFT length 12K.
[Jul 13 12:22] Test 6, 460000 Lucas-Lehmer iterations of M245281 using FFT length 12K.
[Jul 13 12:24] Test 7, 460000 Lucas-Lehmer iterations of M243713 using FFT length 12K.
[Jul 13 12:25] Test 8, 460000 Lucas-Lehmer iterations of M235519 using FFT length 12K.
[Jul 13 12:26] Test 9, 460000 Lucas-Lehmer iterations of M233473 using FFT length 12K.
[Jul 13 12:27] Test 10, 460000 Lucas-Lehmer iterations of M231183 using FFT length 12K.
[Jul 13 12:29] Self-test 12K passed!
[Jul 13 12:29] Test 1, 460000 Lucas-Lehmer iterations of M235519 using FFT length 14K.
[Jul 13 12:30] Test 2, 460000 Lucas-Lehmer iterations of M233473 using FFT length 14K.
[Jul 13 12:32] Test 3, 460000 Lucas-Lehmer iterations of M231183 using FFT length 14K.
[Jul 13 12:33] Test 4, 460000 Lucas-Lehmer iterations of M229375 using FFT length 14K.
[Jul 13 12:35] Test 5, 460000 Lucas-Lehmer iterations of M225281 using FFT length 14K.
[Jul 13 12:36] Test 6, 460000 Lucas-Lehmer iterations of M221183 using FFT length 14K.
[Jul 13 12:38] Test 7, 560000 Lucas-Lehmer iterations of M212991 using FFT length 14K.
[Jul 13 12:40] Test 8, 560000 Lucas-Lehmer iterations of M210415 using FFT length 14K.
[Jul 13 12:42] Test 9, 560000 Lucas-Lehmer iterations of M208897 using FFT length 14K.
[Jul 13 12:43] Test 10, 560000 Lucas-Lehmer iterations of M204799 using FFT length 14K.
[Jul 13 12:45] Self-test 14K passed!
[Jul 13 12:45] Test 1, 380000 Lucas-Lehmer iterations of M266241 using FFT length 16K.
[Jul 13 12:47] Test 2, 380000 Lucas-Lehmer iterations of M262143 using FFT length 16K.
[Jul 13 12:48] Test 3, 380000 Lucas-Lehmer iterations of M260335 using FFT length 16K.
[Jul 13 12:50] Test 4, 460000 Lucas-Lehmer iterations of M250519 using FFT length 16K.
[Jul 13 12:51] Test 5, 460000 Lucas-Lehmer iterations of M245759 using FFT length 16K.
[Jul 13 12:53] Test 6, 460000 Lucas-Lehmer iterations of M245281 using FFT length 16K.
[Jul 13 12:55] Test 7, 460000 Lucas-Lehmer iterations of M243713 using FFT length 16K.
[Jul 13 12:56] Test 8, 460000 Lucas-Lehmer iterations of M235519 using FFT length 16K.
[Jul 13 12:58] Test 9, 460000 Lucas-Lehmer iterations of M233473 using FFT length 16K.
[Jul 13 13:00] Test 10, 460000 Lucas-Lehmer iterations of M231183 using FFT length 16K.
[Jul 13 13:01] Self-test 16K passed!
[Jul 13 13:01] Test 1, 800000 Lucas-Lehmer iterations of M163839 using FFT length 8K.
[Jul 13 13:02] Test 2, 800000 Lucas-Lehmer iterations of M159745 using FFT length 8K.
[Jul 13 13:04] Test 3, 800000 Lucas-Lehmer iterations of M157695 using FFT length 8K.
[Jul 13 13:05] Test 4, 800000 Lucas-Lehmer iterations of M155649 using FFT length 8K.
[Jul 13 13:06] Test 5, 800000 Lucas-Lehmer iterations of M153599 using FFT length 8K.
[Jul 13 13:08] Test 6, 800000 Lucas-Lehmer iterations of M147455 using FFT length 8K.
[Jul 13 13:08] FATAL ERROR: Rounding was 0.4997558594, expected less than 0.4
[Jul 13 13:08] Hardware failure detected, consult stress.txt file.
[Jul 13 13:08] Torture Test completed 353 tests in 53 minutes - 1 errors, 0 warnings.
[Jul 13 13:08] Worker stopped.


Now as you can see by the time logs, the time seems to reset once every hour (roughly) and proves what I was talking about. Sugestions?

Also, for a couple days the computer was sorta stable, where games would run but get random shut downs everynow and then with no BSOD. However for the last day I have been plagued with constant BSOD all caused by the Nvidia driver, where it's to the point I can't even find a game in Dota2 before I get a BSOD. Ill post the last couple logs so you can see.

Ill also post the event viewer log.

 

[usasma]

Here's an error in Prime95 (and is further evidence of a hardware problem):

[Jul 13 13:08] FATAL ERROR: Rounding was 0.4997558594, expected less than 0.4
[Jul 13 13:08] Hardware failure detected, consult stress.txt file.

Errors in Prime95 are most likely due to one of these things:
- bad RAM
- bad CPU cache
- bad memory controller (in i7's the memory controller is on the CPU)

Admin event viewer log shows a number of Event ID 41 errors. These are errors where Windows doesn't know why it shutdown. Most often these are hardware errors. It also shows a disk controller error - which may be a disk problem.

As we have numerous issues that may be hardware, I'd strongly suggest that you run all of the hardware diagnostics here: Link Removed Feel free to skip the tests that you've already run. When done, please post back with a summary of the results of each test.

Have you monitored the temperature of your CPU and other components? If not, please use this free utility to see what the temps are when running Prime95 in Small FFT's: http://www.cpuid.com/softwares/hwmonitor.html

Please also (if you haven't already) run this memory diagnostic: Link Removed
And, please run these CPU stress tests if the problem isn't overheating or RAM: Link Removed

Finally the BSOD's seem to point to hardware, and there may even be a video card issue combined with this.

Analysis:
The following is for informational purposes only.

[font=lucida console]**************************Sat Jul 13 23:03:36.907 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\071313-8611-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 10:29:57.509[/B]
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by :[B]nvlddmkm.sys ( nvlddmkm+1abd3e )[/B]
BugCheck [B]50, {fffffa00130a4490, 1, fffff88005ca7d3e, 7}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: fffffa00130a4490, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff88005ca7d3e, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000007, (reserved)
BUGCHECK_STR:  0x50
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  firefox.exe
FAILURE_BUCKET_ID: [B]X64_0x50_nvlddmkm+1abd3e[/B]
CPUID:        "Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: [B]3500[/B]
  BIOS Version                  1205
  BIOS Release Date             06/26/2013
  Manufacturer                  ASUS
  Product Name                  All Series
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Jul 13 12:21:37.806 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\071313-9516-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:11:08.179[/B]
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by :[B]nvlddmkm.sys ( nvlddmkm+1aca04 )[/B]
BugCheck [B]3B, {c0000005, fffff880059d3a04, fffff8800df903d0, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff880059d3a04, Address of the instruction which caused the bugcheck
Arg3: fffff8800df903d0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  firefox.exe
FAILURE_BUCKET_ID: [B]X64_0x3B_nvlddmkm+1aca04[/B]
CPUID:        "Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: [B]3500[/B]
  BIOS Version                  1205
  BIOS Release Date             06/26/2013
  Manufacturer                  ASUS
  Product Name                  All Series
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Jul 13 01:19:11.115 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\071313-8923-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 2:06:32.911[/B]
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by :[B]nvlddmkm.sys ( nvlddmkm+1aca04 )[/B]
BugCheck [B]3B, {c0000005, fffff88005a1da04, fffff88011455260, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff88005a1da04, Address of the instruction which caused the bugcheck
Arg3: fffff88011455260, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  dota.exe
FAILURE_BUCKET_ID: [B]X64_0x3B_nvlddmkm+1aca04[/B]
CPUID:        "Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: [B]3500[/B]
  BIOS Version                  1007
  BIOS Release Date             05/17/2013
  Manufacturer                  ASUS
  Product Name                  All Series
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Jul 13 01:13:33.388 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\071313-9063-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:00:55.073[/B]
Probably caused by :[B]nvlddmkm.sys ( nvlddmkm+7fa4a )[/B]
BugCheck [B]3B, {c0000005, fffff8800591ca4a, fffff8800e224af0, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff8800591ca4a, Address of the instruction which caused the bugcheck
Arg3: fffff8800e224af0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  firefox.exe
FAILURE_BUCKET_ID: [B]X64_0x3B_nvlddmkm+7fa4a[/B]
CPUID:        "Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: [B]3498[/B]
  BIOS Version                  1205
  BIOS Release Date             06/26/2013
  Manufacturer                  ASUS
  Product Name                  All Series
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Jul 12 22:02:26.003 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\071213-9048-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 2:39:01.634[/B]
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by :[B]hardware ( nvlddmkm+3a4a38 )[/B]
BugCheck [B]3B, {c0000005, fffff88005bc7a38, fffff8800d8ad560, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff88005bc7a38, Address of the instruction which caused the bugcheck
Arg3: fffff8800d8ad560, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  FlashPlayerPlu
FAILURE_BUCKET_ID: [B]X64_IP_MISALIGNED_nvlddmkm.sys[/B]
CPUID:        "Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: [B]3500[/B]
  BIOS Version                  1007
  BIOS Release Date             05/17/2013
  Manufacturer                  ASUS
  Product Name                  All Series
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Jul 12 17:45:09.494 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\071213-9001-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:16:36.195[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!CmpKcbCacheLookup+1de )[/B]
BugCheck [B]50, {fffff8a00a5de00c, 0, fffff8000314af7e, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments: 
Arg1: fffff8a00a5de00c, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff8000314af7e, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000000, (reserved)
BUGCHECK_STR:  0x50
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  LaunchGTAIV.ex
FAILURE_BUCKET_ID: [B]X64_0x50_nt!CmpKcbCacheLookup+1de[/B]
CPUID:        "Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: [B]3500[/B]
  BIOS Version                  1007
  BIOS Release Date             05/17/2013
  Manufacturer                  ASUS
  Product Name                  All Series
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.

[font=lucida console]**************************Sat Jul 13 23:03:36.907 2013 (UTC - 4:00)**************************
intelppm.sys                Mon Jul 13 19:19:25 2009 (4A5BC0FD)
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
AsUpIO.sys                  Mon Aug  2 22:47:59 2010 (4C57835F)
AsIO.sys                    Wed Aug 22 05:54:47 2012 (5034AC67)
HECIx64.sys                 Mon Dec 17 14:32:21 2012 (50CF7345)
asahci64.sys                Wed Jan  9 21:52:36 2013 (50EE2CF4)
ndisrd.sys                  Thu Feb  7 03:26:48 2013 (51136548)
nvhda64v.sys                Mon Feb 25 00:27:35 2013 (512AF647)
e1d62x64.sys                Tue Feb 26 19:23:37 2013 (512D5209)
RTKVHD64.sys                Tue Mar  5 08:21:03 2013 (5135F13F)
dump_iaStorA.sys            Mon Mar 18 19:36:36 2013 (5147A504)
iaStorA.sys                 Mon Mar 18 19:36:36 2013 (5147A504)
iaStorF.sys                 Mon Mar 18 19:36:37 2013 (5147A505)
nvlddmkm.sys                Fri Jun 21 05:06:16 2013 (51C41788)
[/font]

Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
e1d62x64.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed

 

[Matallar]

Alright using CPUID, on max load the CPU maxes out at 52C (after about an hour).
I just finished clearing the CMOS after the Bios update and am runing Prime95 again (small FFT) to see if the fatal error shows up again.

Then i'm gonna reinstall the video drivers. Because here's the weird part I forgot to mention. The computer was running fine, pretty much void of BSOD caused by the video driver, until I went and put the second card back in and turned on SLI, since then, even after having since removed that card again, the BSOD have started again. So im gonna go redo the drivers and see what happens.

 

[Matallar]

Alright, while runing prime95 with the non XMP settings on, I got a BSOD about 1H30 minutes in. Here's the dump:

 

[Matallar]

Was watching a Dota2 Replay when I got this completely new BSOD error code. Ill run Furmark right now and see how that goes.

EDIT: Actually unfortunately, with out EVGA precision X to control the fan speeds on the cards, the fans sit at 20% and the cards skyrocket in temps during the stress test to over 80C (I stopped it when it reached 80 in under 30 secs). If EVGA presision was enabled I could easily do the test and put the fans up to 50% were they will then sit at around 63C. But without it, it just isn't good for the cards.

 

[Matallar]

I have resorted to a complete fresh install of Windows right now. This is actually what I am typing to you from.
Odly enough wich seems pretty big to me.

DURING the INSTALLATION of windows, right after windows finishes isntalling the files and reboots to complete install (not even at the desktop part yet) I got a Page fault in non paged area BSOD. So early in the install infact that there wasen't even a minidump created cause it wasen't even at the point yet.

Also with this install of windows, I removed the samsung SSD's completly so I am only runing 1 drive at everything complete stock settings with no OC and only 1 of the 780GTX.

I will need to install the drivers and such all over again here, so it might take awhile here to get back to you.

 

[Matallar]

Sorry to post so many times in succession, but I'm posting as things develop and I keep trying things to no avail.

Alright well, while trying to install the windows update I got a BSOD for Memory Management, then after recovering from that I got another BSOD for Driver SQL mentioning the NVIDIA driver again, note this is after changing the card to the second one. I can always swap it back to the other one, but it's pretty clear both are doing it now.

Ill attach the dumps here.

Now assuming that this memtest is still correct:

(I can and will probably run in overnight again here to make doubly sure, also ill only run 1 stick instead of two)

Its plainly obvious now that it is a hardware problem, however I still can't make it what is the culprit. Is it the motherboard? The cpu? The last thing I want to do in to RMA or go out and buy another one to replace what I think might be defective and end up with the same problem. The wort case scenario is that sevral of the parts are defective, which would make it doubly a pain to narrow down.

This is by far the worst problem I have ever had in any build I have ever made.

 

[usasma]

From everything we've seen it's most likely the CPU or the mobo.
As you had errors in Prime95, I suspect the CPU the most (but mobo's go bad more often than CPU's)

A couple of CPU stress tests should tell you if it's the CPU or not: Link Removed