Hi,
BugCheck 50, {ffffe000e439f0e6, 0, fffff8010de48000, 0}
*** WARNING: Unable to verify timestamp for vuhub.sys
*** ERROR: Module load completed but symbols could not be loaded for vuhub.sys
Could not read faulting driver name
Probably caused by : vuhub.sys ( vuhub+8000 )
vuhub.sys dated 11/16/2007 ELTIMA Software USB to Ethernet Connector.
That is a very old driver - update the driver or remove the device.
As needed use the other methods in the troubleshooters below.
======================
Troubleshoot blue screen errors
<-- read this link
http://windows.microsoft.com/en-us/windows-10/troubleshoot-blue-screen-errors
We can analyze the minidumps if you make them available from the OneDrive or other file sharing sites (such as MediaFire).
If you have problems uploading the minidumps copy them to the Desktop or the Documents folder and upload them from there.
Adding files to your OneDrive
http://windows.microsoft.com/en-us/windows-8/getting-started-onedrive-tutorial
Upload photos and files
http://windows.microsoft.com/en-us/onedrive/add-photos-files
One-Drive - Share files and folders and change permissions
http://windows.microsoft.com/en-us/onedrive/share-file-folder
Zip or upload the contents of C:\Windows\minidump
Use OneDrive to upload collected files
http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65
====================================================
BCCode: 50 0x00000050
Have you added any hardware lately? Have you updated any driver just before these started? (Check Control Panel - Windows Updates to see if any drivers were updated there about the time this started) Main likely culprits are Video driver, other major
drivers, memory, and antivirus/antispyware/security products could be at fault as well as drive issues.
BCCode: 50 0x00000050 <-- read this link
http://www.faultwire.com/solutions-fatal_error/PAGE-FAULT-IN-NONPAGED-AREA-0x00000050-*1095.html?order=votes
or https://tinyurl.com/y5uhqvrt
==================================================
This utility makes it easy to see which versions are loaded :
Run DriverView - set VIEW to Hide Microsoft drivers - update those without
Dump in their names (and update BIOS and chipset drivers).
DriverView - Free - utility displays the list of all device drivers currently loaded on your system. For each driver in the list, additional useful information is displayed: load address of the driver, description, version, product name, company that created
the driver, and more.
http://www.nirsoft.net/utils/driverview.html
For Drivers check System Maker as fallbacks and Device Maker's which are the most current. Right Click the Start Button - Device Manager - Display Adapter - write down the make and complete model of your video adapter - double click - Driver's tab - write
down the version info. Now click UPdate Driver (this may not do anything as MS is far behind certifying drivers) - then Right Click - Uninstall - REBOOT this will refresh the driver stack.
Repeat that for Network - Network Card (NIC), Wifi, Sound, Mouse and Keyboard if 3rd party with their own software and drivers and any other major device drivers you have.
Now go to System Maker's site (Dell, HP, Toshiba as examples) (as rollback) and then Device Maker's site (Realtek, Intel, Nvidia, ATI as examples) and get their latest versions. (Look for BIOS, Chipset, and software updates at System Maker's site while there.)
Download - SAVE - go to where you put them - Right Click - RUN AD ADMIN - REBOOT after each installation.
Always check in Device Manager - Drivers tab to be sure the version you are installing actually shows up. This is because some drivers rollback before the latest is installed (sound drivers particularly do this) so install a driver - reboot - check to be sure
it is installed and repeat as needed.
Repeat at Device Makers - BTW at Device Makers DO NOT RUN THEIR SCANNER - check manually by model.
Manually look at manufacturer's sites for drivers - and Device Maker's sites.
http://pcsupport.about.com/od/driverssupport/ht/driverdlmfgr.htm
====================================================
Memory tests do not catch all errors such as mismatched memory (possible even for sticks that appear to be identical) and when faster memory is placed in system behind slower memory. So it is best to also swap sticks in and out to check for those even if all
memory tests fail to show a problem.
To test RAM check here - let it run 4+ hours or so. <-- best method
www.memtest.org
MemTestX86 - Test RAM With
http://www.tenforums.com/tutorials/14201-memtest86-test-ram.html
For the Windows Memory Diagnostic Tool.
Type in Cortana's search box -> Windows Memory Diagnostics at top of list - click it.
in Windows 8/8.1/10 the name is "Windows Memory
Diagnostic".
================================================
After doing ALL the updates you can, and if the issue continues, then run Driver Verifier. (Remember to use the Windows 10 methods posted at the top of the original reply above.)
Driver Verifier can help find some BSOD issues :
Using Driver Verifier to identify issues with Windows drivers for advanced users
http://support.microsoft.com/kb/244617
How To Troubleshoot Driver Problems in Windows Vista or 7. (8/8.1 and 10 are essentially the same).
http://www.winvistaclub.com/t79.html
Using Driver Verifier
https://msdn.microsoft.com/en-us/library/windows/hardware/ff545448%28v=vs.85%29.aspx?f=255&MSPPError=-2147217396
WINKEY + X - RUN - type in -> verifier /reset hit enter to disable
If DriverVerifier creates a minidump upload it and post the link here so we can analyze it.
Hope this helps.
--------------------------------------------------------------------------------------------
Rob Brown -
Microsoft MVP <- profile - Windows and Devices for IT : Bicycle - Mark Twain said it right.