Windows 10: win32kbase.sys and win32kfull.sys BSOD

Discus and support win32kbase.sys and win32kfull.sys BSOD in Windows 10 BSOD Crashes and Debugging to solve the problem; Hello, This is a newly built pc. After using it for atleast 3-4 months, I kept getting these errors bsod Microsoft R Windows Debugger Version... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by SimonCabradilla, Sep 28, 2020.

  1. win32kbase.sys and win32kfull.sys BSOD

    Hello, This is a newly built pc. After using it for atleast 3-4 months, I kept getting these errors bsod

    Microsoft R Windows Debugger Version 10.0.19041.1 AMD64

    Copyright c Microsoft Corporation. All rights reserved.

    Loading Dump File [C:\Windows\Minidump\092820-7453-01.dmp]

    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: srv*

    Executable search path is:

    Windows 10 Kernel Version 19041 MP 6 procs Free x64

    Product: WinNt, suite: TerminalServer SingleUserTS Personal

    Built by: 19041.1.amd64fre.vb_release.191206-1406

    Machine Name:

    Kernel base = 0xfffff804`33400000 PsLoadedModuleList = 0xfffff804`3402a310

    Debug session time: Mon Sep 28 06:42:56.818 2020 UTC - 7:00

    System Uptime: 0 days 0:15:47.499

    Loading Kernel Symbols





    Loading User Symbols

    Loading unloaded module list


    For analysis of this file, run !analyze -v

    0: kd> !analyze -v


    * *

    * Bugcheck Analysis *

    * *



    An exception happened while executing a system service routine.


    Arg1: 00000000c0000005, Exception code that caused the bugcheck

    Arg2: ffffaed8476f985d, Address of the instruction which caused the bugcheck

    Arg3: ffff930823e6ec20, Address of the context record for the exception that caused the bugcheck

    Arg4: 0000000000000000, zero.

    Debugging Details:



    Key : Analysis.CPU.Sec

    Value: 3

    Key : Analysis.DebugAnalysisProvider.CPP

    Value: Create: 8007007e on DESKTOP-0ABACKB

    Key : Analysis.DebugData

    Value: CreateObject

    Key : Analysis.DebugModel

    Value: CreateObject

    Key : Analysis.Elapsed.Sec

    Value: 4

    Key : Analysis.Memory.CommitPeak.Mb

    Value: 92

    Key : Analysis.System

    Value: CreateObject


    BUGCHECK_P1: c0000005

    BUGCHECK_P2: ffffaed8476f985d

    BUGCHECK_P3: ffff930823e6ec20

    BUGCHECK_P4: 0

    CONTEXT: ffff930823e6ec20 -- .cxr 0xffff930823e6ec20

    rax=0000000000000138 rbx=ffffaeac82875060 rcx=0000000000000000

    rdx=ffffaeac8281fb20 rsi=ffffaeac82875288 rdi=0000000000000200

    rip=ffffaed8476f985d rsp=ffff930823e6f620 rbp=ffffaeac828750a8

    r8=0000000000000000 r9=0000000000000000 r10=0000000000000000

    r11=ffff930823e6f690 r12=0000000000000138 r13=0000000000000138

    r14=ffffaeac82875094 r15=ffffaeac82875090

    iopl=0 nv up ei pl nz na po nc

    cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050206


    ffffaed8`476f985d 448be0 mov r12d,eax

    Resetting default scope

    BLACKBOXBSD: 1 !blackboxbsd

    BLACKBOXNTFS: 1 !blackboxntfs

    BLACKBOXPNP: 1 !blackboxpnp



    PROCESS_NAME: csrss.exe


    ffff9308`23e6f620 ffffaed8`476f9346 : 00000000`00000000 00000000`000e751c 00000000`00000001 00000000`00000004 : win32kfull!TimersProc+0x1fd

    ffff9308`23e6f6b0 ffffaed8`46481eb4 : ffff830d`5f73d0c0 ffff830d`5f73d0c0 00000000`00000000 00000000`00000005 : win32kfull!RawInputThread+0x7f6

    ffff9308`23e6f870 ffffaed8`47698961 : ffff830d`5f73d0c0 00000000`00000000 00000000`00000005 00000000`00000005 : win32kbase!xxxCreateSystemThreads+0xc4

    ffff9308`23e6f9a0 ffffaed8`46a4474e : ffff830d`5f73d0c0 ffff830d`5f73d0c0 00000000`00000000 00000000`00000000 : win32kfull!NtUserCallNoParam+0x71

    ffff9308`23e6f9d0 fffff804`338058b5 : ffff830d`00000005 00000000`00000005 00000247`100051a0 00000000`000003dc : win32k!NtUserCallNoParam+0x16

    ffff9308`23e6fa00 00007ffa`1a1710e4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25

    000000bd`7d27fce8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`1a1710e4

    SYMBOL_NAME: win32kfull!TimersProc+1fd

    MODULE_NAME: win32kfull

    IMAGE_NAME: win32kfull.sys

    IMAGE_VERSION: 10.0.19041.508

    STACK_COMMAND: .cxr 0xffff930823e6ec20 ; kb


    FAILURE_BUCKET_ID: 0x3B_c0000005_win32kfull!TimersProc

    OS_VERSION: 10.0.19041.1

    BUILDLAB_STR: vb_release


    OSNAME: Windows 10

    FAILURE_ID_HASH: {e19a4cac-ba4d-937b-93bc-07ff9528cd63}

    Followup: MachineOwner

    SimonCabradilla, Sep 28, 2020


    This was probably caused by the following module:
    qcamain1.sys (Qcamain10x64+0x108678)

    Bugcheck code: 0x1D3 (0x333, 0x0, 0x0, 0x0)


    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: qcamain1.sys .

    Google query: qcamain1.sys CUSTOM_ERROR

    Using WhoCrashed I found this thread: QCAMAIN1.SYS CAUSING BSOD (Code 37 Error) however without
    solution, locked.

    I did get BSOD almost everytime I moved the laptop.

    This worked for me:

    unscrew wifi module, push a little into the socket. Screw in. DONE
    Horus-3-Echo, Sep 28, 2020
  3. 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, Sep 28, 2020
  4. win32kbase.sys and win32kfull.sys BSOD

    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: Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.
    interestingkid005140, Sep 28, 2020

win32kbase.sys and win32kfull.sys BSOD

  1. win32kbase.sys and win32kfull.sys BSOD - Similar Threads - win32kbase sys win32kfull

  2. Fresh install build 1903 - 2 BSOD Win32kBase & Win32kFull

    in Windows 10 BSOD Crashes and Debugging
    Fresh install build 1903 - 2 BSOD Win32kBase & Win32kFull: New install of 1903, using all drivers auto installed by windows2 BSOD in relatively short time period using google chrome stable no help in the event viewer Thank you for any assistance you can give 135958
  3. BSOD L1C63x64.sys

    in Windows 10 BSOD Crashes and Debugging
    BSOD L1C63x64.sys: Heya guys, this is my first post here *Smile. I just had like 3 or 4 BSODs in these last two days, never had any. I just updated my Atheros 8151 PCI-e driver from Network adapter->properties->update driver. I'm not sure if it is the cause, so I used the tool and attached...
  4. BSOD L1C63x64.sys driver

    in Windows 10 BSOD Crashes and Debugging
    BSOD L1C63x64.sys driver: Hi, I am getting BSODs and the error message it gives is: Driver_IRQL_NOT_LESS_OR_EQUAL(L1C63x64.sys) I believe that is the Qualcomm Atheros Network driver, but mine is up to date to the last Windows8 compatible driver on the Atheros website. This leads me to believe...
  5. BSOD featuring dxgmms2.sys

    in Windows 10 BSOD Crashes and Debugging
    BSOD featuring dxgmms2.sys: Got another BSOD earlier tonight, this time with dxgmms2.sys cited onscreen. 85143
  6. BSOD blaming L1C63x64.sys

    in Windows 10 BSOD Crashes and Debugging
    BSOD blaming L1C63x64.sys: BSOD happened several times in this week after I updated my windows 10 into the latest version, especially when I was uploading or downloading something through utorrent via ipv6. Windows blame the LiC63x64.sys, and I have updated all my Atheros drivers but it still happen....
  7. BSOD blaming L1C63x64.sys

    in Windows 10 BSOD Crashes and Debugging
    BSOD blaming L1C63x64.sys: Like many others I am the victim of this, it happens more than once a day. It never happened on windows 8.1. At Toshiba's request, I have back-dated my driver to the one that Windows installs with windows 10. I am hoping this fixes the issue, if not, here's my dump 58971
  8. wdf01000.sys BSOD

    in Windows 10 BSOD Crashes and Debugging
    wdf01000.sys BSOD: Hey, this is more of a question. My keyboard has been malfunctioning due to liquid damage, so to disable it I installed an incompatible keyboard/touchpad driver intentionally. The day after, I've been getting wdf01000.sys BSOD errors during startup, which brings me to a...
  9. Frequent BSODs - L1C63x64.sys

    in Windows 10 BSOD Crashes and Debugging
    Frequent BSODs - L1C63x64.sys: Since upgrading to Windows 10 I am getting frequent BSODs with DRIVER_IRQL_NOT_LESS_OR_EQUAL in L1C634x64.sys especially when the network is loaded (heavy bit torrent activity) Googling has led me to believe that it is problems lies with my Atheros driver so I have updated...
  10. BSOD tdr_failure_igdkmd64.sys

    in Windows 10 BSOD Crashes and Debugging
    BSOD tdr_failure_igdkmd64.sys: I have been encountering this error frequently when running games, mostly World of Tanks and the World of Warships beta test. I ALWAYS get this error whenever I accidentally bump the windows key on my laptop in game. If I am at the port or garage screen with all my ships,...