Intermediate BSODs when shutting down/restart/sleep/hibernate computer

Page 7 of 9 FirstFirst ... 56789 LastLast
  1. philc43's Avatar
    Posts : 5,003
    64bit Win 10 Pro ver 20H2 Build 19042.868 and W10 Insider Preview Build 21343
       #61

    In the crash analysis I did see reference to a Synaptics Touch Pad driver that was implicated prior to the Pnp synchronisation wait, if there is a newer driver it would be worth updating. @zbook was this the driver you were talking about?
    SynTP.sys Driver date: Mon Jul 9 16:15:35 2018

      My Computers


  2. Posts : 38,422
    windows 10 professional version 1607 build 14393.969 64 bit
       #62

    Yes same driver.

    There was no beta log collector received.

    The computer that I'm using to type this chat is the G2.
    The driver is readily available on the HP website.
      My Computer


  3. das
    Posts : 36
    Windows 10 x64
    Thread Starter
       #63

    philc43 said:
    In the crash analysis I did see reference to a Synaptics Touch Pad driver that was implicated prior to the Pnp synchronisation wait, if there is a newer driver it would be worth updating. @zbook was this the driver you were talking about?
    SynTP.sys Driver date: Mon Jul 9 16:15:35 2018

    There's not a newer one.

    I'm on 19.0.19.68 which is the same on HPs website.
      My Computer


  4. das
    Posts : 36
    Windows 10 x64
    Thread Starter
       #64

    I've sent you both the latest dump and logs
      My Computer

  5. philc43's Avatar
    Posts : 5,003
    64bit Win 10 Pro ver 20H2 Build 19042.868 and W10 Insider Preview Build 21343
       #65

    Looking at the crash dump I can see that one of the pnp devices that appears to be causing a problem is the
    Microsoft RRAS Root Enumerator SWD\MSRRAS\{5E259276-BC7E-40E3-B93B-8F89B5F3ABC0}

    Code:
    0: kd> !blackboxpnp
        PnpActivityId      : {00000000-0000-0000-0000-000000000000}
        PnpActivityTime    : 131858790011549375
        PnpEventInformation: 3
        PnpEventInProgress : 1
        PnpProblemCode     : 24
        PnpVetoType        : 0
        DeviceId           : SWD\MSRRAS\{5e259276-bc7e-40e3-b93b-8f89b5f3abc0}
        VetoString         : 
    It appears in the thread holding the pnp lock.


    I hoping this might give you a clue on where to investigate next.
      My Computers


  6. das
    Posts : 36
    Windows 10 x64
    Thread Starter
       #66

    philc43 said:
    Looking at the crash dump I can see that one of the pnp devices that appears to be causing a problem is the
    Microsoft RRAS Root Enumerator SWD\MSRRAS\{5E259276-BC7E-40E3-B93B-8F89B5F3ABC0}

    Code:
    0: kd> !blackboxpnp
        PnpActivityId      : {00000000-0000-0000-0000-000000000000}
        PnpActivityTime    : 131858790011549375
        PnpEventInformation: 3
        PnpEventInProgress : 1
        PnpProblemCode     : 24
        PnpVetoType        : 0
        DeviceId           : SWD\MSRRAS\{5e259276-bc7e-40e3-b93b-8f89b5f3abc0}
        VetoString         : 
    It appears in the thread holding the pnp lock.


    I hoping this might give you a clue on where to investigate next.
    Seems to be a new driver causing BSOD each time.
    Though all seems to be related to Networking, right?

    Maybe I should try to reset the network in Windows.
      My Computer

  7. philc43's Avatar
    Posts : 5,003
    64bit Win 10 Pro ver 20H2 Build 19042.868 and W10 Insider Preview Build 21343
       #67

    I suspect it is the same driver all the time but it is not obvious from the dumps. I also agree it is probably something related to the control of the pnp network devices.
      My Computers


  8. Posts : 38,422
    windows 10 professional version 1607 build 14393.969 64 bit
       #68

    For share links please use one of these: one drive, drop box, or google drive.

    The other websites often have numerous download buttons to click that may have PUP, PUA, etc.

    Please use one of these to repost/resend the latest files.
      My Computer


  9. das
    Posts : 36
    Windows 10 x64
    Thread Starter
       #69

    zbook said:
    For share links please use one of these: one drive, drop box, or google drive.

    The other websites often have numerous download buttons to click that may have PUP, PUA, etc.

    Please use one of these to repost/resend the latest files.
    Transfernow.net doesn't have that.
    It's a safe site.
      My Computer


  10. Posts : 38,422
    windows 10 professional version 1607 build 14393.969 64 bit
       #70

    Can Mcafee be uninstalled?
    Can Carbon black be uninstalled?
    Can Windows driver verifier be turned off?

    When available post an image of the HP diagnostic log:
    HP PC Hardware Diagnostics | HP® Official Site


    Run HD Tune: (free version) (test all drives)
    Post images of the test results for these tabs:
    a) Health
    b) Benchmark
    c) Full error scan


    In the left lower corner search type: verifier > click run command > move the dot to delete existing settings > click ok > reboot

    If the above method fails to turn off Windows driver verifier then use the windows advanced troubleshooting menu command prompt and type:
    verifier /reset > reboot
    if the above command
    verifier /bootmode resetonbootfail > reboot


    There was one new driver in the latest bsod crash.

    1) uninstall the Nvidia GPU driver using DDU (display driver uninstaller)
    2) re-install the Nvidia GPU driver from the HP website
    3) make sure that you check the clean install box and if available install the physx driver.
    Display Driver Uninstaller Download version 17.0.8.2 (or newer version if available)
    Display Driver Uninstaller: How to use - Windows 7 Help Forums
    NVIDIA
    Download Display Driver Uninstaller - MajorGeeks



    Driver - HP ZBook 17 G2 Mobile Workstation | HP® Customer Support




    Code:
    mfewfpk.sys
    McAfee
    http://home.mcafee.com/store/downloads.aspx
    
    mfehidk.sys
    McAfee Host Intrusion Detection Link Driver
    http://home.mcafee.com/root/support.aspx
    Code:
    cbk7.sys     Wed Mar 29 15:33:57 2017 (58DC3655)
    Code:
    mfewfpk  mfewfpk.sys  Tue Mar 13 11:14:21 2018 (5AA814FD)
    mfehidk  mfehidk.sys  Tue Mar 13 11:13:52 2018 (5AA814E0)

    Code:
    Event[8884]:
      Log Name: System
      Source: Disk
      Date: 2018-10-24T17:17:09.077
      Event ID: 11
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-J212TNG
      Description: 
    The driver detected a controller error on \Device\Harddisk3\DR4.
    
    Event[8885]:
      Log Name: System
      Source: Disk
      Date: 2018-10-24T17:17:09.296
      Event ID: 11
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-J212TNG
      Description: 
    The driver detected a controller error on \Device\Harddisk3\DR4.
    
    Event[8886]:
      Log Name: System
      Source: Disk
      Date: 2018-10-24T17:17:09.499
      Event ID: 11
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-J212TNG
      Description: 
    The driver detected a controller error on \Device\Harddisk3\DR4.
    
    Event[8887]:
      Log Name: System
      Source: Disk
      Date: 2018-10-24T17:17:09.702
      Event ID: 11
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-J212TNG
      Description: 
    The driver detected a controller error on \Device\Harddisk3\DR4.
    
    Event[8888]:
      Log Name: System
      Source: Disk
      Date: 2018-10-24T17:17:09.921
      Event ID: 11
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-J212TNG
      Description: 
    The driver detected a controller error on \Device\Harddisk3\DR4.

    Code:
    Event[13031]:
      Log Name: System
      Source: Disk
      Date: 2018-11-05T09:06:32.330
      Event ID: 51
      Task: N/A
      Level: Warning
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-J212TNG
      Description: 
    An error was detected on device \Device\Harddisk3\DR4 during a paging operation.


    Code:
    Event[13270]:
      Log Name: System
      Source: AFD
      Date: 2018-11-05T10:19:35.620
      Event ID: 16001
      Task: N/A
      Level: Warning
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-J212TNG
      Description: 
    A TDI filter (\Driver\NEOFLTR_825_50207) was detected. This filter has not been certified by Microsoft and may cause system instability.
    Code:
    Driver	c:\windows\system32\driverstore\filerepository\nvbl.inf_amd64_aa900d663b62b12b\nvlddmkm.sys (22.21.13.8573, 14,91 MB (15*629*752 bytes), 2017-10-20 16:27)
    Last edited by zbook; 06 Nov 2018 at 15:08.
      My Computer


 
Page 7 of 9 FirstFirst ... 56789 LastLast

  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 07:19.
Find Us




Windows 10 Forums