BSOD while playing games in SLI Mode Event 41 Task 63 in E.V.

ThePiousPriest · 25 Mar 2012

Windows 7 Professional x64 Retail
Roughly 3 years old

I7 920 stock settings
6 Gigs of Corsair Dominator TR3X6G1600C8D
2 GTX 460's in SLI on 296.10 Drivers
1 TB Western Digital WD1001FALS
Intel 80 Gig SSD SSDSA2M080G2GC

My hunch is it is an Nvidia related problem, as the forum is flooded with complaints about the recent drivers causing issues, but can never be too sure.

ThePiousPriest · 25 Mar 2012

From the event viewer
Friendly
BugcheckCode 278
BugcheckParameter1 0xfffffa800cf6c010
BugcheckParameter2 0xfffff880104c1aa4
BugcheckParameter3 0xffffffffc000009a
BugcheckParameter4 0x4
SleepInProgress false
PowerButtonTimestamp 0

XML
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
<EventID>41</EventID>
<Version>2</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000002</Keywords>
<TimeCreated SystemTime="2012-03-25T16:07:34.836807600Z" />
<EventRecordID>173151</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>AgentJTP9</Computer>
<Security UserID="S-1-5-18" />
</System>
- <EventData>
<Data Name="BugcheckCode">278</Data>
<Data Name="BugcheckParameter1">0xfffffa800cf6c010</Data>
<Data Name="BugcheckParameter2">0xfffff880104c1aa4</Data>
<Data Name="BugcheckParameter3">0xffffffffc000009a</Data>
<Data Name="BugcheckParameter4">0x4</Data>
<Data Name="SleepInProgress">false</Data>
<Data Name="PowerButtonTimestamp">0</Data>
</EventData>
</Event>

usasma · 25 Mar 2012

Win 7 doesn't like wireless USB devices, especially those with older (Vista-era) drivers.
You have a Realtek RTL8191SU Wireless LAN 802.11n USB 2.0 Network Adapter
Here's my rant on these devices:

I do not recommend using wireless USB devices. Especially in Win7 systems.
These wireless USB devices have many issues with Win7 - and using Vista drivers with them is almost sure to cause a BSOD.
Should you want to keep using these devices, be sure to have Win7 drivers - DO NOT use Vista drivers!!!
An installable wireless PCI/PCIe card that's plugged into your motherboard is much more robust, reliable, and powerful.

We've seen a number of BSOD issues with SSD's recently. Here's the information that I've compiled:

There's not a whole bunch available to test SSD's. The "easiest" test is to remove the SSD, install a platter-based hard drive, install Windows and test for stability that way.

Here's some suggestions:
- Update the SSD's firmware to the latest available version (VERY IMPORTANT!!!)
- Slow the memory (RAM) down to the next slower speed (I've only seen one person who claimed that this worked for them).
- Use any manufacturer's utilities that you may have. If you don't have any, then try this free one (I haven't used it myself): Crystal Dew World
- Update chipset and storage controller drivers to the latest available from the manufacturer of the device (not the manufacturer of the motherboard). Be sure to update ALL controllers on the motherboard!
....NOTE: Recently (Nov 2011) we had BSOD issues with the Marvell 91xx controller and an SSD. You may have to switch controllers also.-
Replace the SSD with a platter based hard drive and see if that stops the BSOD's. If it does, then it's likely that there's a problem with the SSD OR an incompatibility with your system.
It's my opinion that SSD's aren't reliable enough (with current hardware) to be used on a system that needs to work reliably. Until I see reliability I will not recommend, nor will I use, SSD's for critical applications.
06 Dec 2011 - This post tends to confirm issues with certain SSD chipsets and certain controllers - [SOLVED] cant find the cause of BSOD F4 - Tech Support Forum

EVGA Precision (along with Riva Tuner and MSI Afterburner) are known to cause BSOD's in some Win7 systems. Please uninstall it immediately!

You have the 2005 version of ASACPI.sys - another known BSOD cause. This is the Asus ATK0110 ACPI Utility driver, and is available from the Asus download website for your motherboard (either under the ATK heading or the Utility heading). If you can't locate it, please provide the exact make and model of your motherboard.

Headed out to dinner, more to follow after........

usasma · 25 Mar 2012

You have a 2008 version of a Copy Protection program by Tages SA ( TAGES, the AAA Copy Protection System )
The driver is lirsgt.sys Please either update the program or uninstall it.

You have a 2009 version of an XBox USB controller driver. I've seen a lot of issues with these devices recently, and would suggest uninstalling the software and removing the device from your system until we've made the system stable again.

Your Logitech camera drivers date from 2009 - please update those.

Your Marvell Yukon network drivers date from 2009 - please update them.

Your Kaspersky drivers date from 2010. I'd strongly suggest updating to the latest version if you wish to continue using Kaspersky.

Finally, if the BSOD's continue after all of the above, please try the troubleshooting suggestions in this topic: STOP 0x116: VIDEO_TDR_ERROR troubleshooting

Further info on BSOD error messages available at: http://www.carrona.org/bsodindx.html

The following info is just FYI, I've already addressed the issues that I saw in the above paragraphs
3RD PARTY DRIVERS PRESENT IN THE DUMP FILES

Code:


vpchbus.sys     Sat Nov 20 06:35:38 2010 (4CE7B28A)
amdxata.sys     Fri Mar 19 12:18:18 2010 (4BA3A3CA)
vpcnfltr.sys    Sat Nov 20 06:35:20 2010 (4CE7B278)
kl1.sys         Wed Jun 09 09:34:19 2010 (4C0F985B)
xusb21.sys      Thu Aug 13 18:10:17 2009 (4A848F49)
RTL8192su.sys   Thu Nov 25 01:13:42 2010 (4CEDFE96)
klif.sys        Fri Oct 01 03:28:56 2010 (4CA58DB8)
kl2.sys         Wed Jun 09 09:24:47 2010 (4C0F961F)
klim6.sys       Thu Apr 22 11:07:24 2010 (4BD0662C)
vpcvmm.sys      Sat Nov 20 06:35:48 2010 (4CE7B294)
VBoxUSBMon.sys  Mon Dec 19 07:43:53 2011 (4EEF3189)
VBoxDrv.sys     Mon Dec 19 07:43:53 2011 (4EEF3189)
VBoxNetFlt.sys  Mon Dec 19 07:43:51 2011 (4EEF3187)
vpcusb.sys      Sat Nov 20 06:35:31 2010 (4CE7B283)
VBoxNetAdp.sys  Mon Dec 19 07:43:53 2011 (4EEF3189)
ASACPI.sys      Sun Mar 27 22:30:36 2005 (42476C4C)
nvhda64v.sys    Tue Jan 17 07:45:46 2012 (4F156D7A)
LV302V64.SYS    Thu Apr 30 18:43:26 2009 (49FA298E)
lv302a64.sys    Thu Apr 30 18:41:07 2009 (49FA2903)
lvrs64.sys      Thu Apr 30 18:43:25 2009 (49FA298D)
LHidFilt.Sys    Fri Sep 02 02:23:09 2011 (4E60764D)
LMouFilt.Sys    Fri Sep 02 02:23:15 2011 (4E607653)
cpuz134_x64.sys Fri Jul 09 07:16:58 2010 (4C37052A)
lirsgt.sys      Tue Jun 17 11:17:08 2008 (4857D574)
LVPr2M64.sys    Wed Oct 07 04:26:50 2009 (4ACC50CA)
nvlddmkm.sys    Thu Jan 26 05:19:23 2012 (4F2128AB)
nvBridge.kmd    Fri May 13 23:47:37 2011 (4DCDFB59)
yk62x64.sys     Mon Feb 23 10:02:27 2009 (49A2BA83)
nvlddmkm.sys    Thu Feb 09 21:02:58 2012 (4F347AD2)
nvlddmkm.sys    Wed Feb 29 13:04:52 2012 (4F4E68C4)
VMMR0.r0        Mon Dec 19 07:43:49 2011 (4EEF3185)
VBoxDDR0.r0     Mon Dec 19 07:43:49 2011 (4EEF3185)
VBoxDD2R0.r0    Mon Dec 19 07:43:49 2011 (4EEF3185)

Code:


Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\032512-13166-01.dmp]
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Sun Mar 25 12:06:50.089 2012 (UTC - 4:00)
System Uptime: 0 days 0:12:19.167
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+c9faa4 )
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
Bugcheck code 00000116
Arguments fffffa80`0cf6c010 fffff880`104c1aa4 ffffffff`c000009a 00000000`00000004
BiosVersion = 1003   
BiosReleaseDate = 03/08/2010
CPUID:        "Intel(R) Core(TM) i7 CPU         920  @ 2.67GHz"
MaxSpeed:     2670
CurrentSpeed: 2672
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\032112-9594-01.dmp]
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Wed Mar 21 10:00:19.162 2012 (UTC - 4:00)
System Uptime: 0 days 0:05:45.239
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+ca1aa4 )
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
Bugcheck code 00000116
Arguments fffffa80`0c63a010 fffff880`1054eaa4 ffffffff`c000009a 00000000`00000004
BiosVersion = 1003   
BiosReleaseDate = 03/08/2010
CPUID:        "Intel(R) Core(TM) i7 CPU         920  @ 2.67GHz"
MaxSpeed:     2670
CurrentSpeed: 2672
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\031512-9906-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Thu Mar 15 21:59:14.174 2012 (UTC - 4:00)
System Uptime: 0 days 0:08:05.141
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+ca1aa4 )
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
Bugcheck code 00000116
Arguments fffffa80`0cefe390 fffff880`104c7aa4 ffffffff`c000009a 00000000`00000004
BiosVersion = 1003   
BiosReleaseDate = 03/08/2010
CPUID:        "Intel(R) Core(TM) i7 CPU         920  @ 2.67GHz"
MaxSpeed:     2670
CurrentSpeed: 2672
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\022412-12230-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Fri Feb 24 15:04:55.468 2012 (UTC - 4:00)
System Uptime: 0 days 17:21:10.545
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceHandler+7c )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  VirtualBox.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!KiSystemServiceHandler+7c
Bugcheck code 0000003B
Arguments 00000000`c0000096 fffff880`0e850972 fffff880`08fc8ed0 00000000`00000000
BiosVersion = 1003   
BiosReleaseDate = 03/08/2010
CPUID:        "Intel(R) Core(TM) i7 CPU         920  @ 2.67GHz"
MaxSpeed:     2670
CurrentSpeed: 2672
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

ThePiousPriest · 26 Mar 2012

After various uninstalls and running the FurMark stress test, I believe the issue to be video card related. Whatever card in slot one shoots up to 100 C only after a few seconds of running the stress test. I've switched around the cards to see if it is a hardware problem, but both cards seem to do this. I've also disabled SLI mode to see if it works for some time, but it is subject to the same BSOD.Something could be wrong with the PCIE controllers or I am still standing by my statement that it could very well be driver related.