Windows 10: HTTP.sys causing periodic BSODs

Discus and support HTTP.sys causing periodic BSODs in Windows 10 BSOD Crashes and Debugging to solve the problem; I am getting the following BSOD on all of my developer's workstations. Running 1909 x64. PAGE_FAULT_IN_NONPAGED_AREA 50 Invalid system memory was... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by ChasingGhosts, Mar 12, 2020.

  1. CHASINGGHOSTS
    ChasingGhosts Win User

    HTTP.sys causing periodic BSODs


    I am getting the following BSOD on all of my developer's workstations. Running 1909 x64.


    PAGE_FAULT_IN_NONPAGED_AREA 50

    Invalid system memory was referenced. This cannot be protected by try-except.
    Typically the address is just plain bad or it is pointing at freed memory.
    Arguments:
    Arg1: ffffa781771b6000, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff8043e80c79c, If non-zero, the instruction address which referenced the bad memory
    address.
    Arg4: 0000000000000000, reserved
    Debugging Details:
    ------------------
    Could not read faulting driver name
    KEY_VALUES_STRING: 1
    PROCESSES_ANALYSIS: 1
    SERVICE_ANALYSIS: 1
    STACKHASH_ANALYSIS: 1
    TIMELINE_ANALYSIS: 1
    DUMP_CLASS: 1
    DUMP_QUALIFIER: 400
    BUILD_VERSION_STRING: 18362.1.amd64fre.19h1_release.190318-1202
    SYSTEM_MANUFACTURER: Microsoft Corporation
    SYSTEM_PRODUCT_NAME: Surface Book 2
    SYSTEM_SKU: Surface_Book_1793
    SYSTEM_VERSION: D:0B:08K:1F:5C:10P:38
    BIOS_VENDOR: Microsoft Corporation
    BIOS_VERSION: 389.2837.768
    BIOS_DATE: 08/21/2019
    BASEBOARD_MANUFACTURER: Microsoft Corporation
    BASEBOARD_PRODUCT: Surface Book 2
    DUMP_TYPE: 2
    BUGCHECK_P1: ffffa781771b6000
    BUGCHECK_P2: 0
    BUGCHECK_P3: fffff8043e80c79c
    BUGCHECK_P4: 0
    READ_ADDRESS: fffff80440b733b8: Unable to get MiVisibleState
    Unable to get NonPagedPoolStart
    Unable to get NonPagedPoolEnd
    Unable to get PagedPoolStart
    Unable to get PagedPoolEnd
    ffffa781771b6000
    FAULTING_IP:
    HTTP!McTemplateK0zhsqqxs+e0
    fffff804`3e80c79c 44381401 cmp byte ptr [rcx+rax],r10b
    MM_INTERNAL_CODE: 0
    CPU_COUNT: 8
    CPU_MHZ: 840
    CPU_VENDOR: GenuineIntel
    CPU_FAMILY: 6
    CPU_MODEL: 8e
    CPU_STEPPING: a
    CPU_MICROCODE: 6,8e,a,0 F,M,S,R SIG: B4'00000000 cache B4'00000000 init
    BLACKBOXBSD: 1 !blackboxbsd
    BLACKBOXNTFS: 1 !blackboxntfs
    BLACKBOXPNP: 1 !blackboxpnp
    BLACKBOXWINLOGON: 1
    CUSTOMER_CRASH_COUNT: 1
    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
    BUGCHECK_STR: AV
    PROCESS_NAME: w3wp.exe
    CURRENT_IRQL: 2
    ANALYSIS_SESSION_HOST: <REDACTED>
    ANALYSIS_SESSION_TIME: 03-12-2020 10:07:55.0987
    ANALYSIS_VERSION: 10.0.18362.1 amd64fre
    TRAP_FRAME: ffff9f8476beec00 -- .trap 0xffff9f8476beec00
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000098 rbx=0000000000000000 rcx=ffffa781771b5f68
    rdx=0000000000000008 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff8043e80c79c rsp=ffff9f8476beed90 rbp=ffff9f8476beee29
    r8=ffff9f8476beef90 r9=0000000000000005 r10=0000000000000000
    r11=fffff8043e845120 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei pl nz na pe nc
    HTTP!McTemplateK0zhsqqxs+0xe0:
    fffff804`3e80c79c 44381401 cmp byte ptr [rcx+rax],r10b ds:ffffa781`771b6000=??
    Resetting default scope
    LAST_CONTROL_TRANSFER: from fffff8044082dfc1 to fffff804407c2380
    STACK_TEXT:
    ffff9f84`76bee958 fffff804`4082dfc1 : 00000000`00000050 ffffa781`771b6000 00000000`00000000 ffff9f84`76beec00 : nt!KeBugCheckEx
    ffff9f84`76bee960 fffff804`406c91bf : ffffa781`7725ae48 00000000`00000000 00000000`00000000 ffffa781`771b6000 : nt!MiSystemFault+0x195f11
    ffff9f84`76beea60 fffff804`407d0420 : 00000000`00000000 00000000`00000000 ffffa781`771b5f68 00000000`00000000 : nt!MmAccessFault+0x34f
    ffff9f84`76beec00 fffff804`3e80c79c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x360
    ffff9f84`76beed90 fffff804`3e8a17e4 : 00000000`000000ff 00000000`0000000c ffff9f84`00018124 00000000`000001c0 : HTTP!McTemplateK0zhsqqxs+0xe0
    ffff9f84`76beee60 fffff804`3e80c88a : ffffbe86`18129060 ffffbe86`18129060 00000000`000009b9 00000000`00000000 : HTTP!UlpCompleteCacheBuildWorker+0x184
    ffff9f84`76bef010 fffff804`3e8a6360 : ffffbe86`0a266a48 00000000`000009b9 00000000`000000d0 ffff9f84`76bef0f8 : HTTP!UlpCompleteCacheBuild+0x8a
    ffff9f84`76bef060 fffff804`3e8a66c4 : 00000000`00000000 ffffbe86`18129020 ffff9f84`76bef1e1 ffffbe86`0a2667a0 : HTTP!UlBuildCacheEntryWorker+0x210
    ffff9f84`76bef140 fffff804`3e89ff4e : ffffbe86`0a266dcb ffffbe86`0a2667a0 fffff804`3e8439a0 ffff9f84`76bef3e0 : HTTP!UlpBuildCacheEntry+0x224
    ffff9f84`76bef230 fffff804`3e8029b8 : 00000000`00000000 00000000`00000000 ffffbe86`0acf0010 00000000`00000168 : HTTP!UlSendHttpResponseIoctl+0x1bfe
    ffff9f84`76bef6e0 fffff804`4070a939 : ffffbe86`0acf0010 00000000`00000002 00000000`00000000 00000000`00000000 : HTTP!UxDeviceControl+0x78
    ffff9f84`76bef720 fffff804`40cb2995 : ffffbe86`0acf0010 00000000`00000000 ffffbe86`0acf0010 00000066`fab7e540 : nt!IofCallDriver+0x59
    ffff9f84`76bef760 fffff804`40cb27a0 : 00000000`00000000 ffff9f84`76befa80 fffff804`3e8029e0 ffff9f84`76befa80 : nt!IopSynchronousServiceTail+0x1a5
    ffff9f84`76bef800 fffff804`40cb1b76 : 00000000`00000000 00000000`00000000 00000000`00000000 0000023d`947699f8 : nt!IopXxxControlFile+0xc10
    ffff9f84`76bef920 fffff804`407d3c15 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtDeviceIoControlFile+0x56
    ffff9f84`76bef990 00007ffc`3d09c1a4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
    00000066`fab7e498 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`3d09c1a4
    THREAD_SHA1_HASH_MOD_FUNC: d06937697559cfebac14e1ad98ce811a9c5e68a7
    THREAD_SHA1_HASH_MOD_FUNC_OFFSET: d27b43ac6586733be10da5865f8a8067ff2a4197
    THREAD_SHA1_HASH_MOD: eca8ff46b4c254458eff7a1765cf091a6eb3518a
    FOLLOWUP_IP:
    HTTP!McTemplateK0zhsqqxs+e0
    fffff804`3e80c79c 44381401 cmp byte ptr [rcx+rax],r10b
    FAULT_INSTR_CODE: 1143844
    SYMBOL_STACK_INDEX: 4
    SYMBOL_NAME: HTTP!McTemplateK0zhsqqxs+e0
    FOLLOWUP_NAME: MachineOwner
    MODULE_NAME: HTTP
    IMAGE_NAME: HTTP.sys
    DEBUG_FLR_IMAGE_TIMESTAMP: 41916144
    IMAGE_VERSION: 10.0.18362.628
    STACK_COMMAND: .thread ; .cxr ; kb
    BUCKET_ID_FUNC_OFFSET: e0
    FAILURE_BUCKET_ID: AV_R_INVALID_HTTP!McTemplateK0zhsqqxs
    BUCKET_ID: AV_R_INVALID_HTTP!McTemplateK0zhsqqxs
    PRIMARY_PROBLEM_CLASS: AV_R_INVALID_HTTP!McTemplateK0zhsqqxs
    TARGET_TIME: 2020-03-11T14:34:46.000Z
    OSBUILD: 18362
    OSSERVICEPACK: 693
    SERVICEPACK_NUMBER: 0
    OS_REVISION: 0
    SUITE_MASK: 272
    PRODUCT_TYPE: 1
    OSPLATFORM_TYPE: x64
    OSNAME: Windows 10
    OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS
    OS_LOCALE:
    USER_LCID: 0
    OSBUILD_TIMESTAMP: unknown_date
    BUILDDATESTAMP_STR: 190318-1202
    BUILDLAB_STR: 19h1_release
    BUILDOSVER_STR: 10.0.18362.1.amd64fre.19h1_release.190318-1202
    ANALYSIS_SESSION_ELAPSED_TIME: 47f1
    ANALYSIS_SOURCE: KM
    FAILURE_ID_HASH_STRING: km:av_r_invalid_http!mctemplatek0zhsqqxs
    FAILURE_ID_HASH: {739d52e4-ddfc-d136-5601-a75e32602eca}
    Followup: MachineOwner

    :)
     
    ChasingGhosts, Mar 12, 2020
    #1
  2. INTERESTINGKID005140
    interestingkid005140 Win User

    wdf01000.sys and ntoskrnl.exe BSOD

    I'm on Windows 10, 64bit

    Basically, whenever I try to update my LPC controller through Device Manager, BSOD with WDF_VIOLATION occurs (culprit being wdf01000.sys)

    So I try to use the driver verifier to see which driver is causing the BSOD, but then it causes BSOD (cultprit being ntoskrnl.exe)

    Have no idea which driver is causing them

    Please help!

    Here are my list of drivers and system info: Documents
     
    interestingkid005140, Mar 12, 2020
    #2
  3. JOY KEMPRAI
    Joy Kemprai Win User
    BSOD - driver_irql_not_less_or_equal (l1c63x64.sys)

    Hi Seung,

    Sorry for the inconvenience caused by BSOD - driver_irql_not_less_or_equal (l1c63x64.sys).

    Please let us know the make/model of your computer.

    The L1C63x64.sys is the Atheros LAN driver and I would suggest to uninstall and reinstall the Atheros LAN driver but install the latest Atheros LAN driver by visiting the manufacture's website and avoid using any LAN driver available though Windows Update.

    However the problem could also be with any VPN software and other software so make sure you have the latest version of each of these software.

    If the errors continue uninstall the VPN software and check if the issue persist.

    Hope this helps. Get back to us for further queries for BSOD - driver_irql_not_less_or_equal (l1c63x64.sys). We are happy to help!
     
    Joy Kemprai, Mar 12, 2020
    #3
  4. VICTOR PACHECO
    Victor Pacheco Win User

    HTTP.sys causing periodic BSODs

    BSOD caused by igdkmd64.sys, but what's the reason???

    Hi Microsoft community, my problem holds on the fact that I was normally using my PC, and suddenly the computer crashed, showing a BSOD with the causing file (igdkmd64.sys), and a QR code with the problem that, unfortunately I couldn't scan. At the time
    the BSOD appeared, I was browsing the Internet (with Chrome browser), viewing some videos, looking on Facebook, Twitter, and also I had another program opened called "Kinovea" (for physical analysis of movement). The specs of my PC are:

    • Processor Intel Core i7 6500 u
    • 8 GB RAM and 1 TB HDD
    • Integrated Intel Graphics Card (as the problem file shows), and Nvidia GeForce 940m dedicated graphics card, active only when needed. If this info is useful, it appears that Nvidia drivers are NOT working after the BSOD.
    • ASUS X556U computer

    I was able to get the minidump (DMP) file from the BSOD, available at this link:

    Minidump File on OneDrive



    My computer is very new (less than a month that I bought it), and this type of error has never passed me before today, and it hasn't happened again after that time. Every help and analysis for my minidump and my problem will be appreciated.
     
    Victor Pacheco, Mar 12, 2020
    #4
Thema:

HTTP.sys causing periodic BSODs

Loading...

  1. HTTP.sys causing periodic BSODs - Similar Threads - HTTP sys causing

  2. BSOD caused by rtwlane601.sys?

    in Windows 10 Gaming
    BSOD caused by rtwlane601.sys?: Hi everyone,I seem to have been experiencing frequent Kernel Mode Heap Corruption BSODs and have already tried a few things but to no avail. Was hoping someone can help. System is relatively new, about 5 months old and wishing it isn't a hardware issue. Started experiencing...

  3. BSOD caused by rtwlane601.sys?

    in Windows 10 Software and Apps
    BSOD caused by rtwlane601.sys?: Hi everyone,I seem to have been experiencing frequent Kernel Mode Heap Corruption BSODs and have already tried a few things but to no avail. Was hoping someone can help. System is relatively new, about 5 months old and wishing it isn't a hardware issue. Started experiencing...

  4. BSOD caused by watchdog.sys and dxgmms2.sys

    in Windows 10 Software and Apps
    BSOD caused by watchdog.sys and dxgmms2.sys: Greetings, fellow Windows users!Yesterday, my computer had its BSOD while I'm using Adobe Premiere which was apparently caused by watchdog.sys and dxgmms2.sys.Here is a link to the dmp file: https://1drv.ms/u/s!AmT-xQXftxFWgiKU88vH7tRulzda?e=33kqdQThanks for any further help...

  5. BSOD caused by dxgmms2.sys and watchdog.sys

    in Windows 10 Software and Apps
    BSOD caused by dxgmms2.sys and watchdog.sys: I've tried reverting graphics drivers, windows updates, updating BIOS, resetting windows and other recommended methods such as chkdsk and DISM. I would like some confirmation on my issue being potentially video card related. Another pair of eyes/insight is the goal of this...

  6. BSOD caused by netwtw10.sys

    in Windows 10 Drivers and Hardware
    BSOD caused by netwtw10.sys: From a couple of days ago my machine has been frequently BSOD and showing the error to be caused by netwtw10.sys. I have attempted to reinstall network drivers, reset machine with content, reset to factory and the issue has persisted through all the changes I made. In...

  7. QCAMAIN1.SYS CAUSING BSOD

    in Windows 10 BSOD Crashes and Debugging
    QCAMAIN1.SYS CAUSING BSOD: This was probably caused by the following module: qcamain1.sys Qcamain10x64+0x108678 Bugcheck code: 0x1D3 0x333, 0x0, 0x0, 0x0 Error: CUSTOM_ERROR A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for...

  8. BSOD caused by Dot4.sys

    in Windows 10 BSOD Crashes and Debugging
    BSOD caused by Dot4.sys: I have a BSOD problem caused by Dot4.sys very often but I have no idea what is causing it. SYSTEM_SERVICE_EXCEPTION Dot4.sys+e23f IEEE-1284.4-1999 Driver Windows (R) Win 7 DDK driver Windows (R) Win 7 DDK provider 6.1.7600.16385 built by: WinDDK x64 ntoskrnl.exe+1aab90

  9. BSOD caused by QCamain10x64.sys and IntelHaxm.sys

    in Windows 10 BSOD Crashes and Debugging
    BSOD caused by QCamain10x64.sys and IntelHaxm.sys: My laptop crashed with STOP code DEVICE_IRQL_NOT_LESS_OR_EQUAL, stating that QCamain10x64.sys had failed, which according to Google, is the driver of my laptop's wireless adapter. Just to make sure before attempting to reinstall the driver via device manager, I saw this wiki...

  10. Random BSODs caused by cm11264.sys.

    in Windows 10 BSOD Crashes and Debugging
    Random BSODs caused by cm11264.sys.: Hi, i recently started having issues with my computer crashing. I will provide the dump files. I've looked up what cm11264.sys was connected to and it was my pair of Sennheiser 363d. I have since then tried multiple driver versions, and now have switched to a different port....