BSOD Failed:tcpip.sys Stop code:driver_irql_not_less_or_equal

Page 1 of 2 12 LastLast

  1. Posts : 10
    Windows 10
       #1

    BSOD Failed:tcpip.sys Stop code:driver_irql_not_less_or_equal


    Hello guys,
    My laptop is fairly new only like 3-4 months. last week it started giving me blue screens. started happening more often. Failed:tcpip.sys Stop code:driver_irql_not_less_or_equal. then I did a "reset this pc" with keeping data. it was working fine for a few days and it blue screened today while watching a lecture on chrome. If it helps I was on my schools network when it happened. I installed only the crucial programs to do my school work. I would just drop it off at the microsoft store but I need the laptop for school and if I could fix it quickly it would be better. I uploaded the zip if you need anything else I'll get to it asap.
    Thank you
      My Computer


  2. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #2

    Sorry for the late response. Do you still need assistance?

    Only 1 dump in the zip you uploaded and it doesn't have any useful data in it. If you are running any HD cleanup programs, like CCleaner, please don't run it again until this problem is resolved. If using CCleaner, uncheck Minidumps so they don't get erased.

    Attachment 99649

    Run DM_Log_collector again if you get another BSOD.

    Meanwhile, let's give Driver Verifier a try, see if it shakes out anything.
    ===================================================
    Driver Verifier
    is a diagnostic tool built into Windows 10, it is designed to verify both native Microsoft drivers and third party drivers. Driver Verifier's verification process involves putting heavy stress on drivers with the intention of making bad, outdated, incompatible or misbehaving drivers fail. The required result is a BSOD (Blue Screen of Death) which will generate a crash dump for debugging purposes.
    Machines exposed to Driver Verifier will run very sluggishly due to the stress being applied to the drivers.

    Driver Verifier - Enable and Disable in Windows 10

    Pay close attention to
    PART TWO
    and make sure the correct boxes are checked.

    Warning:
    It is not advised to run Driver Verifier for more than 48 hours at a time. Disable Driver Verifier after 48 hours or after receiving a BSOD, whichever happens soonest.

    Always create a Restore Point prior to enabling Driver Verifier.

    What we're looking for is a BSOD with a mini dump that will tell us what driver caused it.
      My Computers


  3. Posts : 10
    Windows 10
    Thread Starter
       #3

    I actually haven't run ccleaner in a while haven't reinstalled after the reset. it just causes more problems than it fixes from previous experience. I actually haven't got it again yet but I got another BSOD for ndis.sys once Dont know if it was a coincidence but it happen exactly once I opened vlc through right clicking and selecting it to open a file. I uploaded the new zip. I'll run driver verifier and see what happens. Thanks
    Ztruker said:
    Sorry for the late response. Do you still need assistance?

    Only 1 dump in the zip you uploaded and it doesn't have any useful data in it. If you are running any HD cleanup programs, like CCleaner, please don't run it again until this problem is resolved. If using CCleaner, uncheck Minidumps so they don't get erased.

    Attachment 99649

    Run DM_Log_collector again if you get another BSOD.

    Meanwhile, let's give Driver Verifier a try, see if it shakes out anything.
    ===================================================
    Driver Verifier
    is a diagnostic tool built into Windows 10, it is designed to verify both native Microsoft drivers and third party drivers. Driver Verifier's verification process involves putting heavy stress on drivers with the intention of making bad, outdated, incompatible or misbehaving drivers fail. The required result is a BSOD (Blue Screen of Death) which will generate a crash dump for debugging purposes.
    Machines exposed to Driver Verifier will run very sluggishly due to the stress being applied to the drivers.

    Driver Verifier - Enable and Disable in Windows 10

    Pay close attention to
    PART TWO
    and make sure the correct boxes are checked.

    Warning:
    It is not advised to run Driver Verifier for more than 48 hours at a time. Disable Driver Verifier after 48 hours or after receiving a BSOD, whichever happens soonest.

    Always create a Restore Point prior to enabling Driver Verifier.

    What we're looking for is a BSOD with a mini dump that will tell us what driver caused it.
      My Computer


  4. Posts : 10
    Windows 10
    Thread Starter
       #4

    ok so once i booted up my laptop from sleep(i think) it was on BSOD here is the new zip
      My Computer


  5. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #5

    The latest dump indicates
    Code:
    BugCheck A, {1f80, 2, 0, fffff802d58454f8}
    Probably caused by : CmBatt.sys ( CmBatt!CmBattSendDownStreamIrp+76 )
    Read about it here: CmBatt.sys Windows process - What is it?

    Try running these commands in sequence from a Elevated Command Prompt.

    Dism /Online /Cleanup-Image /StartComponentCleanup
    Dism /Online /Cleanup-Image /RestoreHealth
    SFC /scannow


    If that doesn't help then see if you can disable it in services.msc (Windows key+R, type services.msc and press Enter).
      My Computers


  6. Posts : 10
    Windows 10
    Thread Starter
       #6

    I ran everything and sfc didnt find any violations and the Dism commands completed successfully. Hopefully there isn't anything wrong left. if I get a BSOD I'll update the thread. I'm just hoping it doesn't cause a BSOD while I'm taking my exam on tuesday.
    Thank you!
    Ztruker said:
    The latest dump indicates
    Code:
    BugCheck A, {1f80, 2, 0, fffff802d58454f8}
    Probably caused by : CmBatt.sys ( CmBatt!CmBattSendDownStreamIrp+76 )
    Read about it here: CmBatt.sys Windows process - What is it?

    Try running these commands in sequence from a Elevated Command Prompt.

    Dism /Online /Cleanup-Image /StartComponentCleanup
    Dism /Online /Cleanup-Image /RestoreHealth
    SFC /scannow


    If that doesn't help then see if you can disable it in services.msc (Windows key+R, type services.msc and press Enter).
      My Computer


  7. Posts : 10
    Windows 10
    Thread Starter
       #7

    ok I got another BSOD same as the first one. here is the zip.
      My Computer


  8. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #8

    This one indicates a problem with dzudd.sys:
    Code:
    ffff9800`fd9ceb20  fffff803`e1921ca0Unable to load image \SystemRoot\System32\drivers\rzudd.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for rzudd.sys
    *** ERROR: Module load completed but symbols could not be loaded for rzudd.sys
     rzudd+0x21ca0
    I believe this belongs to a Razer mouse driver. If you have one you might try uninstalling the druiver then try a different mouse for awhile, see what that does.
      My Computers


  9. Posts : 10
    Windows 10
    Thread Starter
       #9

    Ztruker said:
    This one indicates a problem with dzudd.sys:
    Code:
    ffff9800`fd9ceb20  fffff803`e1921ca0Unable to load image \SystemRoot\System32\drivers\rzudd.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for rzudd.sys
    *** ERROR: Module load completed but symbols could not be loaded for rzudd.sys
     rzudd+0x21ca0
    I believe this belongs to a Razer mouse driver. If you have one you might try uninstalling the druiver then try a different mouse for awhile, see what that does.
    Well I'm using a razer laptop no external mouse so idk what to do lol.
      My Computer


  10. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #10

    Me either. You could try the Razdr Synapse All-In-One installer from there web site, see what that does for you: Razer Synapse All-in-one Installer

    I'm guessing that install all available drivers.

    I did notice your laptop has a Synaptics touch pad. Are you using an external mouse?
      My Computers


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 22:44.
Find Us




Windows 10 Forums