Windows 10: KMODE_EXCEPTION_NOT_HANDLED TCPIP.SYS BLACK SCREEN can't share info

Discus and support KMODE_EXCEPTION_NOT_HANDLED TCPIP.SYS BLACK SCREEN can't share info in Windows 10 BSOD Crashes and Debugging to solve the problem; Dear Ten Forums Community: Before reading notice that my monitor is totally black (like idle) while de PC seems to run normally, all sounds and... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by nanakji, Jan 13, 2018.

  1. nanakji Win User

    KMODE_EXCEPTION_NOT_HANDLED TCPIP.SYS BLACK SCREEN can't share info


    Dear Ten Forums Community:

    Before reading notice that my monitor is totally black (like idle) while de PC seems to run normally, all sounds and beeps ok, components look physically well, no fat capacitors....SO I CAN'T PUT IN PRACTICE ANY FIX UNTIL I FIND HOW TO RECOVER SIGNAL FROM MY MOBO TO MY MONITOR *cry

    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!

    :)
     
    nanakji, Jan 13, 2018
    #1
  2. robbarros Win User
    robbarros, Jan 13, 2018
    #2
  3. error: KMODE_EXCEPTION_NOT_HANDLED (tcpip.sys)

    We do need the actual log files (called a DMP files) as they contain the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

    Please follow our instructions for finding and uploading the files we need to help you fix your computer. They can be found here
    If you have any questions about the procedure please ask
     
    ZigZag3143 (MS -MVP), Jan 13, 2018
    #3
  4. axe0 New Member

    KMODE_EXCEPTION_NOT_HANDLED TCPIP.SYS BLACK SCREEN can't share info

    Hi nanakji,

    Basically, you can't boot because the files are corrupted.
    Corruption is often due to hardware issues and rarely something else.

    For HDtune, use WinPE.
    Windows 10 Recovery Tools - Bootable Rescue Disk - Windows 10 Forums




    KMODE_EXCEPTION_NOT_HANDLED TCPIP.SYS BLACK SCREEN can't share info [​IMG]
    Diagnostic Test
    KMODE_EXCEPTION_NOT_HANDLED TCPIP.SYS BLACK SCREEN can't share info [​IMG]
    RAM TEST
    *Arrow Run HDTune to
    • check the health,
    • scan for errors, no quick scan but full scan
    • run a benchmark.
    It may take some time, but please take the time you need to perform it properly.
    When above is done please make screenshots of the following
    • the health,
    • the error scan,
    • the benchmark incl. following
      • transfer rate,
      • access time,
      • burst rate,
      • cpu usage.

    *Arrow Run SeaTools DOS to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums
    Run the long test.
    *Arrow Run chkdsk
    Disk Check - Windows 7 Help Forums
    Use option TWO with parameter /r
    Upload the chkdsk log *Arrow Check Disk (chkdsk) - Read Event Viewer Log - Windows 7 Help Forums
     
  5. nanakji Win User
    *Arrow Run HDTune to
    • check the health,
    • scan for errors, no quick scan but full scan
    • run a benchmark.
    It may take some time, but please take the time you need to perform it properly.
    When above is done please make screenshots of the following
    • the health,
    • the error scan,
    • the benchmark incl. following
      • transfer rate,
      • access time,
      • burst rate,
      • cpu usage.

    *Arrow Run SeaTools DOS to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums
    Run the long test.
    *Arrow Run chkdsk
    Disk Check - Windows 7 Help Forums
    Use option TWO with parameter /r
    Upload the chkdsk log *Arrow Check Disk (chkdsk) - Read Event Viewer Log - Windows 7 Help Forums Wow! Thanks brother for such a kind an extensive response. I will try step by step beginning with the rescue disk you provided. And i will pass every single test and post results. I hope I can pass the black screen first though (with the help of that disk). Thanks again and I will keep you informed.

    Greetings!
     
    nanakji, Jan 15, 2018
    #5
  6. nanakji Win User
    Dear community. I downloaded the tool provided by axe0 and riped it on a DVD, but the result is the same: PC is on and seems to work fine but there is no signal to the monitor or even the mouse (it is a Cooler Master Inferno mouse that always lights on so you know the PC is booting properly....)....So it is imposible for me to make any tests with the knowledge or tools that I have at my disposal... is it my only option to call the technician? Thanks and excuse my english.

    UPDATE1: Maybe i didn't understand the steps correctly...All I did was download the recovery ISO, burned it on the DVD and that's it. I don't know if I missed an important step or my black screen is a no end street?? *Sad
     
    nanakji, Jan 15, 2018
    #6
  7. nanakji Win User
    Second attempt:
    -I tried by removing RAM sticks and turning on the PC with each one of them in different slots nothing. At the same time I was trying to force the Dual Bios system typical of the Gygabite MOBOS. (this is important you'll see)
    -Then i placed again the two memory sticks and took off the Nvidia GPU and connected to the on board HDMI port. After pressing on I saw the Dual Bios screen, finally a sign of life! but it leaded to typical repair screen, as i forgot to plug in the keyboard also I needed to reboot so im not sure which method was the one that braught the dual bios screen!! dam! But at least I know that taking the GPU (which is new no more than a year) helped to see some life and that my backup bios is there...but again i got back to another black screen, horrible idle black screen *Sad
     
    nanakji, Jan 15, 2018
    #7
  8. nanakji Win User

    KMODE_EXCEPTION_NOT_HANDLED TCPIP.SYS BLACK SCREEN can't share info

    Third attempt, some strange discovery:
    Ok, so after reading alot about how to force dual BIOS ona Gigabyte MOBO, I tried them all but nothing seemed to force that secondary bios boot. So, It seemed strange that I got some signal on monitor after removing GPU, so I tried to reboot again with the recovery disc by changing one of the stick rams from slot 2 to slot 1, the booted begun with the normal BIOS screen and then a "using secondary bios" screen, then a "_" cursor on the left upside screen side. Then nothing.

    I rebooted again ,confirmed that the screen remains black, once and again no matter what until I remove the same memory stick to any other slot, then the PC boots with signal again, but ONLY AFTER MAKING A PHISICAL CHANGE FROM SLOT X to SLOT Y or whatever...so now i tried to boot with my regular Windows FLash recovery and I could see the widows login with different resolution (im using the onboard gpu HDMI slot) but after some seconds another BSOD was shown with the error code: KMODE_EXCEPTION_NOT_HANDLED FLGTMR.SYS ,which is a different .SYS file than the first one in this case.

    Now the Pc reboooted it self into another BSOD with different error code...then rebooted it self with windows logo there...so strange...and then there is signal but black screen (no idle, but just black light screen if you know what i mean).

    My poor discoveries so far:
    -I can replicate the booting with succesfull signal and bios screen with BOTH stick rams in the same slot (slot 1 to 4). So maybe i ican discard that there is a faulty stick ram or slot.
    -I can replicate that boot with the onboard gpu HDMI SLOT. And with the Nvidia GPU (GTX 960) COULDNT REPLICATE THE "SUCCESFUL" BOOTING at all. Only by not having the GPU and I can confirm that the fan works very lightly and if you gently place your finger on it, it stops like nothing, no more spinning.

    But, very important and strange: I could only make this thing send some life signal if I REMOVE SOMETHING like a memory stick ram and place another, or place the same stick RAM into ANOTHER SLOT, or by removing the GPU as described above. But even with GPU removed I needed to change stick Rams, if not, after some reboots it will stop booting properly.
    -In this case, if no flash memory is inserted after windows logo, and a while loading, and after black screen (loading?) another BSOD comes with the same file "ntoskrnl.exe error code: 0xc0000221"
    -In any case, i can access the BIOS menu with all its functions, so I dont know, maybe that can helps. If i go to boot options and chose "CD ROM" to see if the recovery disc provided by you guys works this is what happens: windows logo appears, circle spinning, then black screen (not idle) like "thinking...." then regular login password screen is being shown...then it worked for lets say, some half hour, enough to try a chk disc or something, but after some time another BSOD came...strange...everything worked just fine...but then that...I didnt have the time to perform any regular scanning or repair

    -Trying to boot with flash memory with windows recovery leads to failure, nothing really happens no recovery options are shown, I will try to force boot from BIOS booting options tomorrow from an original recovery flash drive....

    Thats it...I dont know what is really wrong...can't say: is the RAM, is the Nvidia GPU....(the PC worked fine for some time with that GPU...but well, who knows!). I guess I will need to go to a PC doctor *Sad
     
    nanakji, Jan 15, 2018
    #8
  9. nanakji Win User
    Cooler Master 750W. I may think that it can be also a part or if not, the main issue here. I need to measure the PSU to see if its working properly!
     
    nanakji, Jan 15, 2018
    #9
  10. axe0 New Member
    With your actions I'm suspicious of the motherboard, but check the psu indeed.
     
  11. nanakji Win User
    Yes dude I will! thanks for everything and have a nice week!
     
    nanakji, Apr 5, 2018
    #11
Thema:

KMODE_EXCEPTION_NOT_HANDLED TCPIP.SYS BLACK SCREEN can't share info

Loading...
  1. KMODE_EXCEPTION_NOT_HANDLED TCPIP.SYS BLACK SCREEN can't share info - Similar Threads - KMODE_EXCEPTION_NOT_HANDLED TCPIP SYS

  2. Windows 10 KMODE_EXCEPTION_NOT_HANDLED, driver srv2.sys when accessing SMB admin shares

    in Windows 10 BSOD Crashes and Debugging
    Windows 10 KMODE_EXCEPTION_NOT_HANDLED, driver srv2.sys when accessing SMB admin shares: I ran into an issue, would like to know if anyone else ever had this: Multiple Windows 10 1803 PCs throw a BSOD (KMODE_EXCEPTION_NOT_HANDLED, driver srv2.sys) when trying to access certain folders ("\\SOMEPC\c$\Users", "\\SOMEPC\c$\Program Files" ..) remotely via the SMB...
  3. BSOD KMODE_EXCEPTION_NOT_HANDLED igdkmd64.sys ERROR MESSAGE

    in Windows 10 BSOD Crashes and Debugging
    BSOD KMODE_EXCEPTION_NOT_HANDLED igdkmd64.sys ERROR MESSAGE: I've been experiencing random crashes on my computer over the last couple of weeks, I believe it has something to do with my graphics card drivers (igdkmd64.sys) but the update/rollback attempts didn't help nor did completely uninstalling and reinstalling the newest drivers....
  4. Bsod: Kmode_exception_not_handled

    in Windows 10 BSOD Crashes and Debugging
    Bsod: Kmode_exception_not_handled: Been recently encountering BSoDs with KMODE_EXCEPTION_NOT_HANDLED when gaming, specifically the open beta of Monster Hunter Online. Happens after around 2 hours or so. Doesn't happen with other games and has not happened before. Attached my minidump and required...
  5. BSOD browsing on chrome - KMODE EXCEPTION NOT HANDLED (igdkmd64.sys)

    in Windows 10 BSOD Crashes and Debugging
    BSOD browsing on chrome - KMODE EXCEPTION NOT HANDLED (igdkmd64.sys): Hi all. I had a previous problem which was different to this current one that just occurred, before it wouldn't boot sometimes or able to wake from sleep and get BSODs, my laptop has been working for last few months after a complete clean re-install of Windows 10 but now i...
  6. kmode_exception_not_handled

    in Windows 10 BSOD Crashes and Debugging
    kmode_exception_not_handled: Intermittently hitting this error on boot up. I initially got it when I upgraded from Windows 7 to Windows 10. I got the BSOD on bootup a few times and during normal use; system would go to BSOD then would reboot to desktop fine until it finally stayed in the BSOD on every...
  7. KMODE_EXCEPTION_NOT_HANDLED (wdf01000.sys)

    in Windows 10 BSOD Crashes and Debugging
    KMODE_EXCEPTION_NOT_HANDLED (wdf01000.sys): Got a blue screen while using discord, here's the attachment 102937
  8. igdkmd64.sys/ntoskrnl.exe BSOD & Black screen flickers

    in Windows 10 BSOD Crashes and Debugging
    igdkmd64.sys/ntoskrnl.exe BSOD & Black screen flickers: Hi, Recently after I sold my Gtx 1070 GPU and start to use i5 6500 integrated graphics Intel 530 on Windows 10, my PC is experiencing a few BSOD caused by driver igdkmd64.sys and caused by address ntoskrnl.exe. Besides getting BSOD or crash, my screen also flickers to...
  9. kmode_exception_not_handled partmgr.sys

    in Windows 10 BSOD Crashes and Debugging
    kmode_exception_not_handled partmgr.sys: Hi, guys, This is odd, one of my computers had this BSOD error : kmode_exception_not_handled, partmgr.sys the system has crashed 3 times this morning. I run a chkdsk, all is clear (on a ssd) Attachment 117369 75024
  10. BSOD kmode_exception_not_handled

    in Windows 10 BSOD Crashes and Debugging
    BSOD kmode_exception_not_handled: Today I was playing left 4 dead 2 and suddenly got a BSOD with the following message: KMODE_EXCEPTION_NOT_HANDLED. I immediately used dm_log_collector hoping it would help resolve the issue. I had a previous BSOD long time ago but it was different and never had it again and...