Windows 10: BSOD code 0x133 caused by hal.dll & ntsokrnl.exe

Discus and support BSOD code 0x133 caused by hal.dll & ntsokrnl.exe in Windows 10 BSOD Crashes and Debugging to solve the problem; DISM is used to restore SFC. Please run sfc/scannow in admin command prompt, reboot and run sfc/scannow again. Discussion in 'Windows 10 BSOD Crashes and Debugging' started by praneetsah, Nov 21, 2015.

  1. axe0 New Member

    BSOD code 0x133 caused by hal.dll & ntsokrnl.exe


    DISM is used to restore SFC.

    Please run sfc/scannow in admin command prompt, reboot and run sfc/scannow again.
     

  2. Gotcha! On it *Biggrin
     
    praneetsah, Nov 26, 2015
    #17
  3. Ran the scan multiple times over a period of 2 days and always it said "Windows Resource Protection did not find any integrity violations."

    So I hope that means everything is perfect? However, I've done nothing related to opencl.dll personally, is there anything I need to worry about? And BTW, the restart time is still around 4-5 minutes.
     
    praneetsah, Nov 29, 2015
    #18
  4. axe0 New Member

    BSOD code 0x133 caused by hal.dll & ntsokrnl.exe

    DISM restored SFC, SFC restored the opencl.dll corruption.
    You don't have to do anything more *Smile

    To find out what is taking so long, we need a log of what is happening

    • Search "msconfig" (without quotes) and press enter,
    • go to the boot tab
    • enable 'boot log'
    • click ok > apply
    • reboot when asked
    The boot log file should be located at {windows partition}\Windows\, but I'm not sure exactly what it is called.
     
  5. I apologize for a late reply. Anyway, I enabled Boot log and I'm attaching the same here. Let me know.
     
    praneetsah, Dec 2, 2015
    #20
  6. axe0 New Member
    Unfortunately, it does only state what has and hasn't been loaded.
    I can remember that there were times of how long the drivers take to load, but that could be from something else.

    Following drivers couldn't load, all are Windows drivers.
    This does has influence on the boot time, because it takes more time to find the drivers.
    Code: BOOTLOG_NOT_LOADED \SystemRoot\System32\DRIVERS\NDProxy.sys BOOTLOG_NOT_LOADED \SystemRoot\System32\DRIVERS\NDProxy.sys BOOTLOG_NOT_LOADED \SystemRoot\System32\DRIVERS\NDProxy.sys BOOTLOG_NOT_LOADED \SystemRoot\System32\DRIVERS\NDProxy.sys BOOTLOG_NOT_LOADED \SystemRoot\System32\DRIVERS\NDProxy.sys BOOTLOG_NOT_LOADED \SystemRoot\system32\drivers\WdFilter.sys BOOTLOG_NOT_LOADED \SystemRoot\System32\drivers\dxgkrnl.sys BOOTLOG_NOT_LOADED \SystemRoot\System32\drivers\dxgkrnl.sys BOOTLOG_NOT_LOADED \SystemRoot\System32\drivers\dxgkrnl.sys BOOTLOG_NOT_LOADED \SystemRoot\System32\drivers\dxgkrnl.sys BOOTLOG_NOT_LOADED \SystemRoot\System32\drivers\dxgkrnl.sys[/quote]



    BSOD code 0x133 caused by hal.dll & ntsokrnl.exe [​IMG]
    Diagnostics Test
    BSOD code 0x133 caused by hal.dll & ntsokrnl.exe [​IMG]
    Clean boot
    Please try the following:
    • Open taskmanager
      • Go to the tab startup
      • disable everything
    • Search msconfig and open it
      • Go to the tab services
      • Check 'hide microsoft services'
      • Uncheck all other services
      • Click apply and click ok
    • Reboot if asked
    See if the problem persist, if the problem does not persist enable in the startup tab in taskmanager 1 item and in the services tab in msconfig also 1 service, reboot and see if the problem persist. Keep doing this until you find the culprit or there is nothing left.
    If the problem still persist, try booting in safe mode and see if the problem still persist
     
Thema:

BSOD code 0x133 caused by hal.dll & ntsokrnl.exe

Loading...
  1. BSOD code 0x133 caused by hal.dll & ntsokrnl.exe - Similar Threads - BSOD code 0x133

  2. Valorant causes vgk.sys DLL causing BSOD

    in Windows 10 Gaming
    Valorant causes vgk.sys DLL causing BSOD: Hi, I've had some issues regarding Riot game's Vanguard "Vgk. sys" DLL file in which the BSOD presents itself with the Stop code "DRIVER_VERIFIER_DETECTED_VIOLATION" and ONLY that stop code. I've tried things such as giving Valorant Administrator perms or adding some files...
  3. Valorant causes vgk.sys DLL causing BSOD

    in Windows 10 Software and Apps
    Valorant causes vgk.sys DLL causing BSOD: Hi, I've had some issues regarding Riot game's Vanguard "Vgk. sys" DLL file in which the BSOD presents itself with the Stop code "DRIVER_VERIFIER_DETECTED_VIOLATION" and ONLY that stop code. I've tried things such as giving Valorant Administrator perms or adding some files...
  4. Valorant causes vgk.sys DLL causing BSOD

    in Windows 10 BSOD Crashes and Debugging
    Valorant causes vgk.sys DLL causing BSOD: Hi, I've had some issues regarding Riot game's Vanguard "Vgk. sys" DLL file in which the BSOD presents itself with the Stop code "DRIVER_VERIFIER_DETECTED_VIOLATION" and ONLY that stop code. I've tried things such as giving Valorant Administrator perms or adding some files...
  5. Valorant causes vgk.sys DLL causing BSOD

    in Windows 10 Software and Apps
    Valorant causes vgk.sys DLL causing BSOD: Hi, I've had some issues regarding Riot game's Vanguard "Vgk. sys" DLL file in which the BSOD presents itself with the Stop code "Kmode _Exception_Not_Handled" I've tried things such as giving Valorant Administrator perms or adding some files into exception for the firewall...
  6. Valorant causes vgk.sys DLL causing BSOD

    in Windows 10 Gaming
    Valorant causes vgk.sys DLL causing BSOD: Hi, I've had some issues regarding Riot game's Vanguard "Vgk. sys" DLL file in which the BSOD presents itself with the Stop code "Kmode _Exception_Not_Handled" I've tried things such as giving Valorant Administrator perms or adding some files into exception for the firewall...
  7. BSOD Ntsokrnl

    in Windows 10 Gaming
    BSOD Ntsokrnl: Hi GuysI have been continuing to get a bsod for sometime now. It appears to be random. Usually if I leave the PC on for a few hours and come back and its done it.I downloaded BlueScreenView to read minidumps and have the following...
  8. BSOD Ntsokrnl

    in Windows 10 Software and Apps
    BSOD Ntsokrnl: Hi GuysI have been continuing to get a bsod for sometime now. It appears to be random. Usually if I leave the PC on for a few hours and come back and its done it.I downloaded BlueScreenView to read minidumps and have the following...
  9. BSOD Ntsokrnl

    in Windows 10 BSOD Crashes and Debugging
    BSOD Ntsokrnl: Hi GuysI have been continuing to get a bsod for sometime now. It appears to be random. Usually if I leave the PC on for a few hours and come back and its done it.I downloaded BlueScreenView to read minidumps and have the following...
  10. Random 0x133 BSODs

    in Windows 10 BSOD Crashes and Debugging
    Random 0x133 BSODs: My PC has started crashing almost every day with a 0x133 BSOD. Sometimes it happens when browsing the internet, sometimes when I'm not even using the computer. Sometimes the computer runs happily for several days in a row, sometimes it crashes within minutes of resuming from...
Tags: