KMODE_EXCEPTION_NOT_HANDLED TCPIP.SYS with BLACK MONITOR and [winload.exe] error

[Nanakji]

Dear Tom's Hardware community:
I got the BSOD which I found it is kind of common to people of this forum with the KMODE_EXCEPTION_NOT_HANDLED error. But in my case, I feel it is something more difficult to solve or maybe is something silly that I haven't noticed yet. But having a black screen with no boot is not helping at all to try all the fixes that I have found in this forum (such as making a driver update for some components or a Windows self repair process, so on)

When the error occurred I was just deleting regular files and emptying the Trash Bin, and at the same time, downloading the latest Nvidia Driver (GTX 960) with the Geforce software (but the driver was not even started downloading anyway, or it was kind of stucked at 0% so I remember than when trying to close Gforce Experience SUDDENLY, the BSOD showed with the specific error described below)

KMODE_EXCEPTION_NOT_HANDLED what failed: TCPIP.SYS

After that, I rebooted the Pc and this another blue screen showed:
"the check sum of this file does not match the calculated check sum
FILE: \Windows\System32\winload.exe
Error Code: 0xc0000221"

So I made another reboot but this time the PC sounded correctly, fans, hard drive, but there was no signal at all! Black Monitor (idle). I remember that sometimes some components need to unload all the charge so the system could function properly, so I umpluged the main cable and left it like that.

The next day, the PC worked just fine! The signal was sent to the monitor, I could see the regular BIOS startup and Windows 10 was loading properly. I tried it for couple of days, updated the Nvidia driver with no problem but didn't have the time to make a deep fix or use the repair functions of Windows.

So now I'm paying for my lack of time and the PC made this strange thing:
-Started properly, monitor was showing the BIOS screen
-It went to idle for a moment, then rebooted it self like 2 or 3 more times before monitor went to complete idle
-After that reboot the monitor is still in idle but PC starts as normal, all the beepings and fans and hard drive sounds are there, you can even hear the hard drive sound making its work!

I read that sometimes you need to unplug the cord from behind the Pc while pushing the start button for 30 to 60 seconds and then plug and push ON. I have tried that but the monitor is still idle, no signal sent to the monitor, no blue screen or bios screen, no nothing!

It is strange that I left it like a couple of days and then it worked again! Maybe I have to try that again before attempting another start up so I can begin to make proper software scans, fixes or CMD chkdisk commands or something like that!

Also I read that TCPIP.SYS has something to do with the lan or wireless cards attached to the MOBO so removing CMOS battery can help in issues like this... I will try that after writing this post, but I really need some technical guidance before calling an expensive technician...I feel we can find a solution!!

Please let me know if you guys need more info about this strange issue. Thanks in advance for kind response and patience to read my info!

 

[Colif]

Download the Windows 10 media creation tool and use it to make a win 10 installer on USB - this is just a boot disc

what are specs of PC?
start it up and go into the BIOS with which ever key matches PC (can be F2 or DEL, among other choices)
See if it restarts here... i doubt it, sounds like win 10 still having problems with winload.exe

Try running start up repair:
change boot order so USB is first, hdd second
boot from installer
on screen after languages, choose repair this pc, not install.
choose troubleshoot
choose advanced
choose start up repair - this will scan PC and maybe fix this - will ask for logon info

if that doesn't help, see if you can get into safe mode:
boot from installer, on 2nd screen after languages, choose repair this pc, not install
choose troubleshoot
choose advanced
choose start up options
hit the restart button
choose a safe mode (it doesn't matter which) by using number associated with it.
Pc will restart and load safe mode


Below helps if you can get screen to work...
TCPIP.SYS = Transmission Control Protocol/Internet Protocol. It controls networking... I would upgrade network drivers as they are likely the cause of the error. Ethernet or WIFI drivers manly... not sure about the CMOS battery fix?

If the guess isn't good enough, Can you go to c:\windows folder
set view to show hidden files
How big is Memory.dmp file? if its not several GB in size, can you make a copy of it to documents
Upload the copy from documents to a file sharing web site and show link here. I will ask someone to translate it into a format we can read and hopefully resolve problem

If Memory.dmp is several gb, can you follow option one here
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c windows/minidump after the next BSOD
copy that file to documents
upload the copy from documents to a cloud server and share the link here and someone with right software to read them will help you fix it

 

[Nanakji]

Download the Windows 10 media creation tool and use it to make a win 10 installer on USB - this is just a boot disc

what are specs of PC?
start it up and go into the BIOS with which ever key matches PC (can be F2 or DEL, among other choices)
See if it restarts here... i doubt it, sounds like win 10 still having problems with winload.exe

Try running start up repair:
change boot order so USB is first, hdd second
boot from installer
on screen after languages, choose repair this pc, not install.
choose troubleshoot
choose advanced
choose start up repair - this will scan PC and maybe fix this - will ask for logon info

if that doesn't help, see if you can get into safe mode:
boot from installer, on 2nd screen after languages, choose repair this pc, not install
choose troubleshoot
choose advanced
choose start up options
hit the restart button
choose a safe mode (it doesn't matter which) by using number associated with it.
Pc will restart and load safe mode


Below helps if you can get screen to work...
TCPIP.SYS = Transmission Control Protocol/Internet Protocol. It controls networking... I would upgrade network drivers as they are likely the cause of the error. Ethernet or WIFI drivers manly... not sure about the CMOS battery fix?

If the guess isn't good enough, Can you go to c:\windows folder
set view to show hidden files
How big is Memory.dmp file? if its not several GB in size, can you make a copy of it to documents
Upload the copy from documents to a file sharing web site and show link here. I will ask someone to translate it into a format we can read and hopefully resolve problem

If Memory.dmp is several gb, can you follow option one here
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c windows/minidump after the next BSOD
copy that file to documents
upload the copy from documents to a cloud server and share the link here and someone with right software to read them will help you fix it

Thanks for your kind answer! Whenever I make the PC sends signal to the monitor I will try everything you recommended me in your post. I just purchased a new CMOS battery so let's see if that also helps in resetting the BIOS properly so I can have signal again!! (strange that the first time after couple of days of total disconnection from electricity the PC started like nothing, so that indicates that maybe between the corrupted files and something electric I could find the answer).

Thanks and I hope to bring good news soon!