Windows 10: Regular BSOD after upgrading to windows 10

Hi everyone,

I have recently upgrading to windows 10 on a fairly new machine, after doing so I have had regular BSOD (IRQL unexpected error), there doesn't seem to be much connection between them other than watching videos whilst online. When I got the first one I read a bug fix online which said to fix it either revert back to my previous OS (windows 8) or reinstall windows 10. I did the later thinking I could always revert back if that didn't work but alas it has now gotten rid of that option and the problem still persisted. I downloaded bluescreen view to work out that it was a problem with nwifi.sys driver, and so updated my wifi driver accordingly but the problem still persists. Any help would be appreciated, I hopefully have attached the associated info dump. Any help would be greatly appreciated, please let me know if you need more information.

All the best,
Alex

:)

 

Windows 10 ntoskrnl.exe bsod

Raju,

This is not helpful.

A. It's for Windows 8

B. It is MICROSOFT system files causing BSOD crashes with Windows 10: both
ntoskrnl.exe and ntdll.sys.

I've had the same problem on my machine and never had any BSODs until the Windows 10 upgrade. Not only have I encountered multiple BSOD because of the two Microsoft system files mentioned above, but also encountered regular system freeze ups and crashes.
On top of that, these files seem to cause my system to ignore my harddrives so when it reboots after the BSOD, it says it can't find the OS drive.

My OS is on an Intel SSD in prime condition.

Again, never had a single issue with my system until I upgraded from 8.1 to 10.

Please take this issue seriously. There is a problem with your OS that needs to be fixed ASAP!

 

Regular BSOD after upgrade to Windows 10 because of CRITICAL_PROCESS_DIED

I have similar problem. Full description BSOD svchost.exe

P.S.

Resolved.

 

Hi AlexWendy,

Welcome to the 10forums.

The TP-link driver is causing the crashes.
It seems like the TP-Link driver hasn't been updated.
Driver Reference Table - athrx.sys
Code: *** WARNING: Unable to verify timestamp for athrx.sys *** ERROR: Module load completed but symbols could not be loaded for athrx.sys 7: kd> lmvm athrx start end module name fffff801`1afb0000 fffff801`1b252000 athrx T (no symbols) Loaded symbol image file: athrx.sys Image path: \SystemRoot\System32\drivers\athrx.sys Image name: athrx.sys Timestamp: Tue Feb 22 21:17:31 2011 (4D6419DB) CheckSum: 0029D477 ImageSize: 002A2000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4[/quote] Code: Name [00000000] TP-LINK 450Mbps Wireless N Adapter Adapter Type Ethernet 802.3 Product Type TP-LINK 450Mbps Wireless N Adapter Installed Yes PNP Device ID PCI\VEN_168C&DEV_0030&SUBSYS_3112168C&REV_01\4&287D6E42&0&00E7 Last Reset 13/11/2015 00:04 Index 0 Service Name athr IP Address 192.168.0.4, fe80::45a:2946:de8:99fb IP Subnet 255.255.255.0, 64 Default IP Gateway 192.168.0.1 DHCP Enabled Yes DHCP Server 192.168.0.1 DHCP Lease Expires 14/11/2015 19:02 DHCP Lease Obtained 13/11/2015 19:02 MAC Address ‪C4:E9:84:13F:83‬ Memory Address 0xF71E0000-0xF71FFFFF IRQ Channel IRQ 4294967290 Driver c:\windows\system32\drivers\athrx.sys (9.2.0.310, 2.61 MB (2,736,640 bytes), 01/09/2015 12:52)[/quote] Old drivers:
Code: amdkmpfd Fri Dec 13 06:33:52 2013 (52aa9c40) amdkmpfd.sys TeeDriverx64 Tue Sep 23 22:01:14 2014 (5421d18a) TeeDriverx64.sys RTKVHD64 Tue Sep 30 14:02:07 2014 (542a9bbf) RTKVHD64.sys[/quote] Driver Reference Table - amdkmpfd.sys
Driver Reference Table - TeeDriverx64.sys
Driver Reference Table - RTKVHD64.sys

 

Thanks axe0,

I have reinstalled the driver I am hoping that will fix it (yn). I realised on the driver download site that it doesn't list Windows 10 as a compatible OS but that could be an over sight.

Anyway thanks a lot,
Alex

 

If reinstalling helps, the driver was corrupted.
If reinstalling doesn't help, the driver is incompatible with Windows 10.

If it is the 2nd, you could upload as many files as you want, but I don't think I could help you further if the same driver keeps causing you the problem.