BSOD 0x10e while watching Youtube vid, but laptop is recently unstable

Hi,

Reseating the RAM can help, it is known as "Chip Creep".
Chip creep refers to the problem of chips that, over time, would work their way out of the socket. Chip creep occurred due to thermal expansion; the contracting and expanding during system heat up and cool down.
While chip creep is usually most common with older memory modules it was a problem with other main chips that were inserted into sockets.
To fix chip creep, users of older systems would often have to remove the case cover and push the loose chip back into the socket.

I would advise to run memtest again with them in reversed slots (just what you wanted to hear eh!)

Is the computer running better now you have reseated the RAM? Anymore crashes?

Cheers

Dave

I would say at least 8 passes is better :)

Early night?

Ok, Good luck :)

Hi,

Your Wifi driver is being blamed, as are the Nividia drivers:

Code:

 
Unable to load image \SystemRoot\system32\DRIVERS\NETwNs64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for NETwNs64.sys
*** ERROR: Module load completed but symbols could not be loaded for NETwNs64.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc000001d, fffff88004edb815, fffff8800ab78338, fffff8800ab77b90}
Probably caused by : NETwNs64.sys ( NETwNs64+208815 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)

Code:

 
Driver: NETwNs64.sys  
Dated: Jan 23 22:44:07 2012
Refers to: Intel(R) Wireless WiFi Link 5000 Series Adapter Driver for Windows 7

Try here as there are some 2013 drivers listed:

http://www.intel.com/support/wireless/wtech/proset-ws/sb/CS-034041.htm

You will need to find your version number first:

http://www.intel.com/support/wireless/wlan/sb/CS-025417.htm

Also your Nividia drivers are being blamed again, now from post #29 this driver was dated 2013
and I got you to install the stable driver 306.23, now its dated 2012? Have you updated it?
It seems likely that your Graphics card is only able to run on the stable driver, as this is
quite a few times your Nividia drivers have been at fault:

Code:

Driver: nvlddmkm.sys
Refers to: Nividia Video drivers
Dated: Thu Aug 30 16:50:16 2012

Reinstall the stable driver:
http://www.nvidia.com/object/notebook-win8-win7-winvista-64bit-306.23-whql-driver.html

Now as this is a STOP 1000007E, there is a Hotfix available that you can try which fixes issues
with GPU's under heavy load, it may (or may not) apply to your particular problem:

http://support.microsoft.com/kb/983615

Now test to see if your issue remains?

If the Hotfix fails to fix your issue run these tests:

Video Card - Stress Test with Furmark: Video Card - Stress Test with Furmark
Video Card - Stress Test with OCCT: Video Card - Stress Test with OCCT

Monitor temperature of the system during the tests:

Speccy System Information
HWMonitor

And this old driver is "still" somewhere on your system :

Code:

 
Driver: WinRing0x64.sys 
Dated: Sat Jul 26 14:29:37 2008

Post back any outcome / memtest results

cheers

Dave

Hmmm...seems very odd indeed that you are unable to locate the WinRing0x64.sys driver!!

I provided a link for Intel® WiFi Link 5300 2013 drivers in my last post, not the automatic detector.

The latest version is: 15.6.1 Found here :)

If you are using the stable driver 306.23 and it is failing, then run those video stress tests as that
driver never fails as a rule and if it does its usually the card at fault.

cheers

Dave

Yes, I actually ran the same search on C:\ and it simply did not pop up at all. Quite curious.
If you need me to run SF Tool again and upload the report, I'll gladly do so.

And sorry, I must've misunderstood that somehow. I'll update it with the latest, then run both Furmark and OCCT and see what that gives.

And as a last resort, we can always run Driver Fusion & Sweeper again and see. I doubt I botched something up, but it's not uncommon that I botch something up I was fully certain I had done properly.

EDIT:
I ran the update for the latest one that you linked, yet the version number for the driver remains at 14.3.2.1