Windows 10: BSOD while watching video (80% sure) win32k.sys, hal.dll, etc.

Discus and support BSOD while watching video (80% sure) win32k.sys, hal.dll, etc. in Windows 10 BSOD Crashes and Debugging to solve the problem; Hey guys, I'm new here, so, hello! *Redface I'm on an Acer Aspire V15 Nitro and no new downloads or updates have been performed recently that I... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by onefreeinternet, May 31, 2017.

  1. BSOD while watching video (80% sure) win32k.sys, hal.dll, etc.


    Hey guys,

    I'm new here, so, hello! *Redface

    I'm on an Acer Aspire V15 Nitro and no new downloads or updates have been performed recently that I know of. However it's blue screened 6 times in the last 2 days, and 3 times within 10 minutes just now.

    Please see the zip attached for info. I'm new to dealing with chronic blue screens. Do you think you can help me figure out what's wrong? Attachment 137544

    :)
     
    onefreeinternet, May 31, 2017
    #1

  2. DRIVER_IRQL_NOT_LESS_OR_EQUAL (Netwbw02.sys)

    BSOD while using Youtube or watching videos on IE or Chrome. I'm using Windows 10. I bought Dell i7567 Inspiron. I had this BSOD and got my laptop replaced. After one week of use the new laptop has same BSOD. This happens only while watching Videos.

    I tried reinstalling OS, Updating Drivers, contacted Dell and they updated drivers manually and nothing has worked. Any idea on how to resolve this ?
     
    sharath chandrapatlolla, May 31, 2017
    #2
  3. "WHEA_UNCORRECTABLE_ERROR" BSOD while watching video in browsers (Google Chrome, Mozilla Firefox)

    Here are the bsod_minidumps, MSInfo32_export, Speccy_export.

    It's very strange that this behaviour is random - it appears from time to time. Sometimes I watch video and there is nothing, sometimes there are several BSODs in a row. I didn't find a straight corellation between watching videos in a browser and BSODs,
    but I have noticed that BSOD doesn't appear when I do all the other things (watching video in a local desktop player, playing games, working with Office, etc.).
     
    Nikita Glukhov, May 31, 2017
    #3
  4. zbook New Member

    BSOD while watching video (80% sure) win32k.sys, hal.dll, etc.

    Event[1834]:
    Log Name: System
    Source: Microsoft-Windows-Diagnostics-Networking
    Date: 2017-05-27T11:32:20.987
    Event ID: 6100
    Task: Helper Class Info
    Level: Information
    Opcode: Info
    Keyword: Helper Class Events
    User: S-1-5-19
    User Name: NT AUTHORITY\LOCAL SERVICE
    Computer: WD-LT-DM-01
    Description:
    Details about wireless network adapter diagnosis:


    For complete information about this session see the wireless connectivity information event.


    Helper Class: Native Wi-Fi MSM
    Initialize status: Success


    Information for connection being diagnosed
    Interface GUID: 75f1f474-14e4-44f7-9676-eb2c0fcf44b6
    Interface name: Qualcomm Atheros QCA61x4A Wireless Network Adapter
    Interface type: Native Wi-Fi
    Profile: Digicel_WiFi_w7wA
    SSID: Digicel_WiFi_w7wA
    SSID length: 17
    Connection mode: Infra
    Security: Yes
    Connect even if network is not broadcasting: No


    Result of diagnosis: Problem found


    Root cause:
    Wireless association to "Digicel_WiFi_w7wA" failed for an unknown reason


    Detailed root cause:
    802.11 connection failed due to status code 1: unspecified failure


    Repair option:
    Try connecting to "Digicel_WiFi_w7wA" again
    If the problem continues, try resetting the access point, or contact the network administrator or your hardware manufacturer for further assistance.




    Event[1835]:
    Log Name: System
    Source: Microsoft-Windows-Diagnostics-Networking
    Date: 2017-05-27T11:32:20.988
    Event ID: 4000
    Task: Diagnosis Success
    Level: Information
    Opcode: Info
    Keyword: Core Events
    User: S-1-5-19
    User Name: NT AUTHORITY\LOCAL SERVICE
    Computer: WD-LT-DM-01
    Description:
    The Network Diagnostics Framework has completed the diagnosis phase of operation. The following repair option was offered:


    Helper Class Name: RNWF MSM Helper Class


    Root Cause: Wireless association to "Digicel_WiFi_w7wA" failed for an unknown reason


    Root Cause Guid: {5C92E4E9-4699-418C-9DB6-82D57DCBF59F}


    Repair option: Try connecting to "Digicel_WiFi_w7wA" again
    If the problem continues, try resetting the access point, or contact the network administrator or your hardware manufacturer for further assistance.


    RepairGuid: {B56FDACA-62E3-43EF-8110-BC3E71360B84}


    Seconds required for repair: 300


    Security context required for repair: 0


    Interface: Wi-Fi ({75F1F474-14E4-44F7-9676-EB2C0FCF44B6})




    Event[1836]:
    Log Name: System
    Source: Microsoft-Windows-Diagnostics-Networking
    Date: 2017-05-27T11:32:20.989
    Event ID: 4000
    Task: Diagnosis Success
    Level: Information
    Opcode: Info
    Keyword: Core Events
    User: S-1-5-19
    User Name: NT AUTHORITY\LOCAL SERVICE
    Computer: WD-LT-DM-01
    Description:
    The Network Diagnostics Framework has completed the diagnosis phase of operation. The following repair option was offered:


    Helper Class Name: RNWF MSM Helper Class


    Root Cause: Wireless association to "Digicel_WiFi_w7wA" failed for an unknown reason


    Root Cause Guid: {5C92E4E9-4699-418C-9DB6-82D57DCBF59F}


    Repair option: Resetting your wireless network adapter
    This will disable and then enable the network adapter "Wi-Fi" on this computer.


    RepairGuid: {07D37F7B-FA5E-4443-BDA7-AB107B29AFB9}


    Seconds required for repair: 300


    Security context required for repair: 80


    Interface: Wi-Fi ({75F1F474-14E4-44F7-9676-EB2C0FCF44B6})




    Event[1837]:
    Log Name: System
    Source: Microsoft-Windows-Diagnostics-Networking
    Date: 2017-05-27T11:32:28.057
    Event ID: 5200
    Task: Repair Option Failure
    Level: Information
    Opcode: Info
    Keyword: Core Events
    User: S-1-5-19
    User Name: NT AUTHORITY\LOCAL SERVICE
    Computer: WD-LT-DM-01
    Description:
    The Network Diagnostics Framework failed to execute the following repair:


    Repair option: Resetting your wireless network adapter
    This will disable and then enable the network adapter "Wi-Fi" on this computer.


    RepairGuid: {07D37F7B-FA5E-4443-BDA7-AB107B29AFB9}




    Event[1854]:
    Log Name: System
    Source: Microsoft-Windows-Diagnostics-Networking
    Date: 2017-05-27T11:35:51.850
    Event ID: 4000
    Task: Diagnosis Success
    Level: Information
    Opcode: Info
    Keyword: Core Events
    User: S-1-5-19
    User Name: NT AUTHORITY\LOCAL SERVICE
    Computer: WD-LT-DM-01
    Description:
    The Network Diagnostics Framework has completed the diagnosis phase of operation. The following repair option was offered:


    Helper Class Name: AddressAcquisition


    Root Cause: Your computer has a local IP address
    You might not be able to access the Internet or some network resources.


    Root Cause Guid: {245A9D66-AE9C-4518-A5B4-655752B0A5BD}


    Repair option: Reset the "Wi-Fi" adapter
    This can sometimes resolve an intermittent problem.


    RepairGuid: {07D37F7B-FA5E-4443-BDA7-AB107B29AFB9}


    Seconds required for repair: 70


    Security context required for repair: 80


    Interface: Wi-Fi ({75F1F474-14E4-44F7-9676-EB2C0FCF44B6})




    Event[1857]:
    Log Name: System
    Source: Microsoft-Windows-Diagnostics-Networking
    Date: 2017-05-27T11:36:26.726
    Event ID: 5100
    Task: Validation Failure
    Level: Information
    Opcode: Info
    Keyword: Core Events
    User: S-1-5-19
    User Name: NT AUTHORITY\LOCAL SERVICE
    Computer: WD-LT-DM-01
    Description:
    The Network Diagnostics Framework (NDF) has completed the repair phase of operation. The following repair option or work-around was executed:


    Helper Class Name: AddressAcquisition


    Repair option: Reset the "Wi-Fi" adapter
    This can sometimes resolve an intermittent problem.


    RepairGuid: {07D37F7B-FA5E-4443-BDA7-AB107B29AFB9}


    The repair option appears to have successfully fixed the diagnosed problem. But NDF has detected the existence of other network problems. NDF should be re-run to diagnose these problems.




    Event[1863]:
    Log Name: System
    Source: Microsoft-Windows-Diagnostics-Networking
    Date: 2017-05-27T11:36:38.483
    Event ID: 6100
    Task: Helper Class Info
    Level: Information
    Opcode: Info
    Keyword: Helper Class Events
    User: S-1-5-19
    User Name: NT AUTHORITY\LOCAL SERVICE
    Computer: WD-LT-DM-01
    Description:
    Details about wireless connectivity diagnosis:


    For complete information about this session see the wireless connectivity information event.


    Helper Class: Auto Configuration
    Initialize status: Success


    Information for connection being diagnosed
    Interface GUID: 75f1f474-14e4-44f7-9676-eb2c0fcf44b6
    Interface name: Qualcomm Atheros QCA61x4A Wireless Network Adapter
    Interface type: Native Wi-Fi


    Result of diagnosis: Problem found
    Issue referred to: RNWF MSM Helper Class


    Root cause:
    Windows could not connect to "Digicel_WiFi_w7wA"
    You can try to connect again.


    Repair option:
    Resetting your wireless network adapter
    This will disable and then enable the network adapter "Wi-Fi" on this computer.




    Event[1864]:
    Log Name: System
    Source: Microsoft-Windows-Diagnostics-Networking
    Date: 2017-05-27T11:36:38.483
    Event ID: 6100
    Task: Helper Class Info
    Level: Information
    Opcode: Info
    Keyword: Helper Class Events
    User: S-1-5-19
    User Name: NT AUTHORITY\LOCAL SERVICE
    Computer: WD-LT-DM-01
    Description:
    Details about wireless network adapter diagnosis:


    For complete information about this session see the wireless connectivity information event.


    Helper Class: Native Wi-Fi MSM
    Initialize status: Success


    Information for connection being diagnosed
    Interface GUID: 75f1f474-14e4-44f7-9676-eb2c0fcf44b6
    Interface name: Qualcomm Atheros QCA61x4A Wireless Network Adapter
    Interface type: Native Wi-Fi
    Profile: Digicel_WiFi_w7wA
    SSID: Digicel_WiFi_w7wA
    SSID length: 17
    Connection mode: Infra
    Security: Yes
    Connect even if network is not broadcasting: No


    Result of diagnosis: Problem found


    Root cause:
    Wireless association to "Digicel_WiFi_w7wA" failed for an unknown reason


    Detailed root cause:
    802.11 connection failed due to status code 1: unspecified failure


    Repair option:
    Try connecting to "Digicel_WiFi_w7wA" again
    If the problem continues, try resetting the access point, or contact the network administrator or your hardware manufacturer for further assistance.




    Event[1865]:
    Log Name: System
    Source: Microsoft-Windows-Diagnostics-Networking
    Date: 2017-05-27T11:36:38.486
    Event ID: 4000
    Task: Diagnosis Success
    Level: Information
    Opcode: Info
    Keyword: Core Events
    User: S-1-5-19
    User Name: NT AUTHORITY\LOCAL SERVICE
    Computer: WD-LT-DM-01
    Description:
    The Network Diagnostics Framework has completed the diagnosis phase of operation. The following repair option was offered:


    Helper Class Name: RNWF MSM Helper Class


    Root Cause: Wireless association to "Digicel_WiFi_w7wA" failed for an unknown reason


    Root Cause Guid: {5C92E4E9-4699-418C-9DB6-82D57DCBF59F}


    Repair option: Try connecting to "Digicel_WiFi_w7wA" again
    If the problem continues, try resetting the access point, or contact the network administrator or your hardware manufacturer for further assistance.


    RepairGuid: {B56FDACA-62E3-43EF-8110-BC3E71360B84}


    Seconds required for repair: 300


    Security context required for repair: 0


    Interface: Wi-Fi ({75F1F474-14E4-44F7-9676-EB2C0FCF44B6})




    Event[1866]:
    Log Name: System
    Source: Microsoft-Windows-Diagnostics-Networking
    Date: 2017-05-27T11:36:38.487
    Event ID: 4000
    Task: Diagnosis Success
    Level: Information
    Opcode: Info
    Keyword: Core Events
    User: S-1-5-19
    User Name: NT AUTHORITY\LOCAL SERVICE
    Computer: WD-LT-DM-01
    Description:
    The Network Diagnostics Framework has completed the diagnosis phase of operation. The following repair option was offered:


    Helper Class Name: Dot3HelperClass


    Root Cause: A network cable is not properly plugged in or may be broken


    Root Cause Guid: {4DA030B8-86E5-4B6A-A879-2FFF8443B527}


    Repair option: Plug an Ethernet cable into this computer
    An Ethernet cable looks like a telephone cable but with larger connectors on the ends. Plug this cable into the opening on the back or side of the computer.
    Make sure the other end of the cable is plugged into the router. If that does not help, try using a different cable.


    RepairGuid: {1296DFF0-D04E-4BE1-A512-90F04DDFA3E6}


    Seconds required for repair: 0


    Security context required for repair: 0


    Interface: Ethernet ({68F87F7C-BFDF-4C05-BD8C-1F35FB88DE52})




    Event[1867]:
    Log Name: System
    Source: Microsoft-Windows-Diagnostics-Networking
    Date: 2017-05-27T11:36:38.487
    Event ID: 4000
    Task: Diagnosis Success
    Level: Information
    Opcode: Info
    Keyword: Core Events
    User: S-1-5-19
    User Name: NT AUTHORITY\LOCAL SERVICE
    Computer: WD-LT-DM-01
    Description:
    The Network Diagnostics Framework has completed the diagnosis phase of operation. The following repair option was offered:


    Helper Class Name: RNWF MSM Helper Class


    Root Cause: Wireless association to "Digicel_WiFi_w7wA" failed for an unknown reason


    Root Cause Guid: {5C92E4E9-4699-418C-9DB6-82D57DCBF59F}


    Repair option: Resetting your wireless network adapter
    This will disable and then enable the network adapter "Wi-Fi" on this computer.


    RepairGuid: {07D37F7B-FA5E-4443-BDA7-AB107B29AFB9}


    Seconds required for repair: 300


    Security context required for repair: 80


    Interface: Wi-Fi ({75F1F474-14E4-44F7-9676-EB2C0FCF44B6})




    Event[1870]:
    Log Name: System
    Source: Microsoft-Windows-Diagnostics-Networking
    Date: 2017-05-27T11:36:57.109
    Event ID: 6100
    Task: Helper Class Info
    Level: Information
    Opcode: Info
    Keyword: Helper Class Events
    User: S-1-5-19
    User Name: NT AUTHORITY\LOCAL SERVICE
    Computer: WD-LT-DM-01
    Description:
    Details about wireless connectivity diagnosis:


    For complete information about this session see the wireless connectivity information event.


    Helper Class: Auto Configuration
    Initialize status: Success


    Information for connection being diagnosed
    Interface GUID: 75f1f474-14e4-44f7-9676-eb2c0fcf44b6
    Interface name: Qualcomm Atheros QCA61x4A Wireless Network Adapter
    Interface type: Native Wi-Fi
    Profile: Digicel_WiFi_w7wA
    SSID: Digicel_WiFi_w7wA
    SSID length: 17
    Connection mode: Infra
    Security: Yes
    Connect even if network is not broadcasting: No


    Result of diagnosis: Problem found
    Issue referred to: RNWF MSM Helper Class


    Root cause:
    Windows could not connect to "Digicel_WiFi_w7wA"
    You can try to connect again.


    Repair option:
    Resetting your wireless network adapter
    This will disable and then enable the network adapter "Wi-Fi" on this computer.




    Event[2909]:
    Log Name: System
    Source: BTHUSB
    Date: 2017-05-31T14:38:33.167
    Event ID: 18
    Task: N/A
    Level: Information
    Opcode: N/A
    Keyword: Classic
    User: N/A
    User Name: N/A
    Computer: WD-LT-DM-01
    Description:
    Windows cannot store Bluetooth authentication codes (link keys) on the local adapter. Bluetooth keyboards might not work in the system BIOS during startup.




    The Microsoft (R) Windows Debugger Version 10.0.15063.137 AMD64 is malfunctioning. For all of the minidump files it is displaying GetContextState failed, 0x8007001E


    Probably caused by : win32kbase.sys ( win32kbase!CPTPEngine:*BiggrinoTPGestureProcessing+f5 )
    Probably caused by : win32kbase.sys ( win32kbase!CPTPEngine:*BiggrinoTPGestureProcessing+f5 )
    Probably caused by : win32kbase.sys ( win32kbase!CPTPEngine:*BiggrinoTPGestureProcessing+f5 )
    Probably caused by : win32kbase.sys ( win32kbase!CPTPEngine:*BiggrinoTPGestureProcessing+f5 )
    Probably caused by : mfeavfk04.sys ( mfeavfk04+7b30 )
    Probably caused by : win32kbase.sys ( win32kbase!CPTPEngine:*BiggrinoTPGestureProcessing+f5 )



    mfeavfk04.sys is a Mcafee driver





    This is preliminary information as the Microsoft (R) Windows Debugger Version 10.0.15063.137 AMD64 is malfunctioning with error code: GetContextState failed, 0x8007001E


    Open administrative command prompt and type or copy the following commands:
    1) sfc /scannow
    2) dism /online /cleanup-image /restorehealth
    3) chkdsk /scan


    4) control appwiz.cpl (Uninstall Mcafee antivirus)
    5) uninstall the residual Mcafee antivirus with the Mcafee uninstall tool

    Antivirus Software, Internet Security, Spyware and Malware Removal McAfee

    6) reinstall Mcafee antivirus

    7) open control panel > troubleshooting > left pane view all > run bluetooth and networking troubleshooters

    8) If bsod reoccurs after the above please provide new minidump and place the computer in clean boot::
    How to perform a Clean Boot in Windows 10 - TechNet Articles - United States (English) - TechNet Wiki

    https://support.microsoft.com/en-us/...oot-in-windows
     
    zbook, May 31, 2017
    #4
  5. axe0 New Member
  6. Hey there! thanks for the advice. Unfortunately this is my work laptop and I don't have the authorization to remove the antivirus that the company has provided for the machine.

    Is there any other way I can try to work through this? The antivirus has never caused complications before...
     
    onefreeinternet, Jun 1, 2017
    #6
  7. Hi! I'm sorry, I'm just seeing your post. I understand now what you guys are saying; I will ask admin if I can run this repair and report back to you guys.

    Thanks very much for your speedy assistance.
     
    onefreeinternet, Apr 5, 2018
    #7
Thema:

BSOD while watching video (80% sure) win32k.sys, hal.dll, etc.

Loading...
  1. BSOD while watching video (80% sure) win32k.sys, hal.dll, etc. - Similar Threads - BSOD while watching

  2. BSOD Issues while Gaming or Watching videos

    in Windows 10 BSOD Crashes and Debugging
    BSOD Issues while Gaming or Watching videos: Hello dear Support people, I've been having Multiple BSOD issues while playing games or even watching Videos with a PC I built myself and I have been hoping someone might be able to help me find out what is the cause of all of them and how to fix them. Here is the Event...
  3. BSOD while gaming / watching videos / randomly

    in Windows 10 BSOD Crashes and Debugging
    BSOD while gaming / watching videos / randomly: I have been getting errors and crashes for a few months, but it's been happening more and more frequently and it's driving me crazy. I just finished doing a fresh install of Windows 10 and now it's still occurring. I upgraded all my drivers and it didn't help. I tried sfc...
  4. BSOD while watching any videos(youtube, hulu, etc)

    in Windows 10 BSOD Crashes and Debugging
    BSOD while watching any videos(youtube, hulu, etc): For the past month or so I have been having an issue where I got the BSOD while watching any videos. Sometimes the screen will freeze but then recover, but when it doesn't I get the BSOD and a DPC Watchdog violation. I have tried many actions from the internet including...
  5. BSOD while watching online videos

    in Windows 10 BSOD Crashes and Debugging
    BSOD while watching online videos: Many times when I watch online videos( youtube/netflix/others) my laptop freezes and after 10 seconds brings bsod with the error dpc_watchdog_violation. Any help ? 91321
  6. BSOD while watching YouTube videos

    in Windows 10 BSOD Crashes and Debugging
    BSOD while watching YouTube videos: Hello. Had some BSOD while watching YouTube. And sometimes I go to sleep while watching videos and by the morning I notice the PC had reset. Cannot say if BSOD or an unexpected update, but most likely BSOD. Actually, my no-break's battery has run out of juice, so short...
  7. BSOD while watching a youtube video

    in Windows 10 BSOD Crashes and Debugging
    BSOD while watching a youtube video: Hello. System specs: CPU: I5-4690k RAM: Kingston Fury 2x4GB MOBO: Z97-D3H GPU:R9 280x PowerColor PSU: NZXT Hale v2 Browser: Google Chrome OS: Windows 10 x64 I was watching a youtube video with ~10 tabs open and I received a BSOD saying that I have kdcom.dll missing...
  8. BSOD while watching YouTube videos

    in Windows 10 BSOD Crashes and Debugging
    BSOD while watching YouTube videos: I've gotten three BSODs in the past hour or so while watching fullscreen youtube videos. after the first 2 and some googling it seemed to point to my GPU drivers. I used the AMD uninstall tool to wipe them and then reinstalled the latest drivers. I got another BSOD about 10...
  9. BSOD While watching Youtube Videos

    in Windows 10 BSOD Crashes and Debugging
    BSOD While watching Youtube Videos: Hey all. For the past few months, I have had BSODs while watching youtube videos. It has happened on both Chrome and Edge, so I don't believe its the browser. I also watch Twitch a lot, and it has never happened while watching that. I've attached the logs as the forum...
  10. Random BSOD while watching Youtube video

    in Windows 10 BSOD Crashes and Debugging
    Random BSOD while watching Youtube video: Was watching a Youtube video when suddenly I got this BSOD called UNEXPECTED_STORE_EXCEPTION Thanks in advance! 32640
Tags:

Users found this page by searching for:

  1. root cause guid: {5c92e4e9-4699-418c-9db6-82d57dcbf59f}