BSOD STOP 101 when watching netflix (fine when gaming in bf3/Diablo 3)

on a side note,

i'm going to follow this guide on Saturday to see if its the CPU or not.
Class 101 for 0x101 Bugchecks

We prefer that you follow the https://www.sevenforums.com/crashes-d...tructions.html to provide more information, but I will do the best I can with the given information.


3rd Party Drivers:

Drivers in red should be updated. Drivers in blue are corrupted and should be uninstalled and re-installed. Drivers in sea green are known to cause issues with Windows 7 and the software should be removed from the system:

Code:

lmimirr.dll unavailable  0 00:00:00 1969 (00000000)
lmimirr2.dll unavailable  0 00:00:00 1969 (00000000)
lmimirr.sys Tue Apr 10 16:32:45 2007 (461C108D)
RaInfo.sys Fri Jan 4 11:57:14 2008 (477E818A)
LMIRfsDriver.sys Mon Jul 14 10:26:56 2008 (487B7E50)
gdrv.sys Thu Mar 12 21:22:29 2009 (49B9D175)
GEARAspiWDM.sys Mon May 18 06:17:04 2009 (4A1151C0)
RtNdPt60.sys Sun Jul 19 20:27:32 2009 (4A63D614)
amdsata.sys Wed Oct 7 14:13:09 2009 (4ACCF655)
amdxata.sys Wed Oct 7 14:13:10 2009 (4ACCF656)
LGVirHid.sys Mon Nov 23 18:36:48 2009 (4B0B38B0)
LGBusEnum.sys Mon Nov 23 18:36:48 2009 (4B0B38B0)
rikvm_9EC60124.sys Tue Oct 5 19:27:35 2010 (4CABD087)
AppleCharger.sys Mon Jan 10 02:57:29 2011 (4D2AD809)
ALSysIO64.sys Sat Jul 9 18:27:45 2011 (4E18F201)
EtronXHCI.sys Mon Jul 25 15:30:56 2011 (4E2DE090)
EtronHub3.sys Mon Jul 25 15:30:59 2011 (4E2DE093)
LHidFilt.Sys Fri Sep 2 00:23:09 2011 (4E60764D)
LMouFilt.Sys Fri Sep 2 00:23:15 2011 (4E607653)
LUsbFilt.Sys Fri Sep 2 00:23:19 2011 (4E607657)
RTCore64.sys Tue Sep 6 06:24:50 2011 (4E661112)
usbfilter.sys Wed Dec 14 00:44:02 2011 (4EE853C2)
RTKVHD64.sys Tue Jan 17 04:14:33 2012 (4F155819)
nvhda64v.sys Tue Jan 17 05:45:46 2012 (4F156D7A)
MpFilter.sys Fri Mar 9 04:05:26 2012 (4F59E3F6)
nvlddmkm.sys Tue Apr 3 07:01:59 2012 (4F7AF4C7)
Rt64win7.sys Wed Apr 11 10:29:16 2012 (4F85B15C)

lmimirr.dll
lmimirr2.dll
lmimirr.sys
RaInfo.sys
LMIRfsDriver.sys
gdrv.sys
GEARAspiWDM.sys
RtNdPt60.sys
amdsata.sys
amdxata.sys
LGVirHid.sys
LGBusEnum.sys
rikvm_9EC60124.sys
AppleCharger.sys
ALSysIO64.sys
EtronXHCI.sys
EtronHub3.sys
LHidFilt.Sys
LMouFilt.Sys
LUsbFilt.Sys
RTCore64.sys
usbfilter.sys
RTKVHD64.sys
nvhda64v.sys
MpFilter.sys
nvlddmkm.sys
Rt64win7.sys

Recommend removing your Gigabyte utilities through Start Menu -> Control Panel -> Uninstall a program. They can provide software interfaces with the hardware for overclocking, and even when the overclock is not enabled, that interface can cause instability. They are also not needed for the system to function properly and may reduce system resources.

Analysis:

The link you refer to is a good place to start. It is strange that it is pointing to a network driver, though. I rarely see 0x101 show a driver in the stack; it is usually all Windows based... I wonder if it is due to the corrupted LogMeIn software.

well after looking thru the memory.dmp and checking the interupt levels on the processors, it doesnt appear to be bad hardware as the 'r if' output was 0 and not 1. I've attached the requested full info dump.

Im having my friend reinstall logmein and remove the gigabyte software

You seem well versed in using the debugger. Nice work! I assume you read the thread by Vir Gnarus, who is probably the best I have seen at digging deep into .dmp files and coming out with very useful info.

Let us know how things go with the LogMeIn re-install and whether fixing its drivers stops the processor hang.

I am also a software developer. I enjoy doing the debugging work and determining what is causing crashes.

Unfortunately, I have not yet learned the differences between the minidump and kernel dump since I rarely receive a MEMORY.DMP on these forums. I just started learning this back in November, and we have since lost a number of our blue screen experts due to them burning out, moving to other things, etc. so I have picked up a number of threads to keep the crashes and debugging forum well supported. I work on here as a volunteer in my free time, and spend the rest of my time doing PhD research. I say all this because it leaves me with very little free time to learn more of the intricacies of kernel based analysis.

I feel bad that you uploaded that file since I cannot provide more insight with it.

Quick update on this issue.

Uninstalled the realtek NIC and did the 'remove driver' option, then also went into device manager, showed hidden devices and removed the realtek NDIS device. Rebooted and reinstalled the nic drivers (RtNdPt60.sys Dec 13 2010 (NDIS driver), RT64Win7.sys Sep 29 2011 (device driver)) and it seems to be working at the moment as we where able to watch netflix for 30 minutes without a crash.

I'll monitor for a week before writing up a final resolution post and marking as solved

Thank you for posting back the details of your steps. That may help others who have similar problems. Was LogMeIn also taken care of?

Even though it may not have been the direct cause, LogMeIn was corrupted and may cause other issues down the line. Just wanted to make sure that was also resolved. :)

We uninstalled logmein, and watched netflix prior to my purging of all things realtek. Still got a bsod. After reinstalling the realtek driver per my last post, theres only been 1 bsod (same issue) but before the bsod, silverlight actually did an appcrash first. So.... hopefully there's some info in there on whats going on :)