Windows 10: BSOD caused by the following modules : win32kfull.sys ,ntoskrnl.exe

Discus and support BSOD caused by the following modules : win32kfull.sys ,ntoskrnl.exe in Windows 10 BSOD Crashes and Debugging to solve the problem; Hi, It has been months since I'm getting different types of BSOD and I'm unable to solve this problem. I would be grateful if you could help me with... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by BADER Wael, Oct 12, 2019.

  1. BSOD caused by the following modules : win32kfull.sys ,ntoskrnl.exe


    Hi,


    It has been months since I'm getting different types of BSOD and I'm unable to solve this problem.

    I would be grateful if you could help me with this issue.


    Wael,



    Crash dumps are enabled on your computer.

    Crash dump directories:
    C:\Windows
    C:\Windows\Minidump

    On Sat 12/10/2019 18:01:18 your computer crashed or a problem was reported
    crash dump file: C:\Windows\Minidump\101219-8500-01.dmp
    This was probably caused by the following module: win32kfull.sys (0xFFFFDFBF4D6D3FB4)
    Bugcheck code: 0x3B (0xC0000005, 0xFFFFDFBF4D6D3FB4, 0xFFFFCE070AAEEBD0, 0x0)
    Error: SYSTEM_SERVICE_EXCEPTION
    file path: C:\Windows\system32\win32kfull.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Full/Desktop Win32k Kernel Driver
    Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



    On Sat 12/10/2019 18:01:18 your computer crashed or a problem was reported
    crash dump file: C:\Windows\MEMORY.DMP
    This was probably caused by the following module: win32kfull.sys (0xFFFFDFBF4D6D3FB4)
    Bugcheck code: 0x3B (0xC0000005, 0xFFFFDFBF4D6D3FB4, 0xFFFFCE070AAEEBD0, 0x0)
    Error: SYSTEM_SERVICE_EXCEPTION
    file path: C:\Windows\system32\win32kfull.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Full/Desktop Win32k Kernel Driver
    Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



    On Sat 12/10/2019 17:29:16 your computer crashed or a problem was reported
    crash dump file: C:\Windows\Minidump\101219-8125-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x1C1220)
    Bugcheck code: 0xA (0xFFFFFFFEFFFFFFF8, 0x2, 0x0, 0xFFFFF80309842B74)
    Error: IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
    This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Sat 12/10/2019 15:02:52 your computer crashed or a problem was reported
    crash dump file: C:\Windows\Minidump\101219-11125-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x1C1220)
    Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8045381DEF8, 0x1, 0x0)
    Error: KMODE_EXCEPTION_NOT_HANDLED
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
    This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Thu 10/10/2019 23:17:49 your computer crashed or a problem was reported
    crash dump file: C:\Windows\Minidump\101019-11171-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x1C1220)
    Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80476E33054, 0xFFFFA78932CD6C40, 0x0)
    Error: SYSTEM_SERVICE_EXCEPTION
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Wed 09/10/2019 21:56:40 your computer crashed or a problem was reported
    crash dump file: C:\Windows\Minidump\100919-11187-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x1C1220)
    Bugcheck code: 0x1A (0x403, 0xFFFF8D8AF45C5920, 0x81000001D0669867, 0xFFFF8D8AF41B5920)
    Error: MEMORY_MANAGEMENT
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that a severe memory management error occurred. The page table and PFNs are out of sync . This is probably a hardware error, especially if parameters 3 & 4 differ by only a single bit.
    This is likely to be caused by a hardware problem. This error suggests a case of memory corruption because of a hardware problem. It is suggested you do a test on your RAM modules (memory test) and make sure your system is not getting overheated. This problem might also be caused because of overheating (thermal issue).
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    :)
     
    BADER Wael, Oct 12, 2019
    #1

  2. BSOD ntoskrnl..exe+1b35e0

    Hi, KirbyBakken

    My name is Maritza and I am an Independent Advisor. I would be happy to help you today.

    Check this link, I hope it helps

    https://www.thewindowsclub.com/ntoskrnl-exe-hig...

    Note: This is a non-Microsoft website. The page appears to be providing accurate, safe information. Watch out for ads on the site that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised
    on the site before you decide to download and install it.

    Let us know if these steps help you to resolve the issue.
     
    MaritzaCapiro, Oct 12, 2019
    #2
  3. XYZ B. Win User
    XYZ B., Oct 12, 2019
    #3
  4. axe0 Win User

    BSOD caused by the following modules : win32kfull.sys ,ntoskrnl.exe

    BSODs caused by ntoskrnl.exe and win32kbase.sys while playing League


    Have you finished post #49?
     
Thema:

BSOD caused by the following modules : win32kfull.sys ,ntoskrnl.exe

Loading...
  1. BSOD caused by the following modules : win32kfull.sys ,ntoskrnl.exe - Similar Threads - BSOD caused following

  2. BSOD Minidump shows page_faul ntoskrnl..exe

    in Windows 10 BSOD Crashes and Debugging
    BSOD Minidump shows page_faul ntoskrnl..exe: KUKutter_UKFirstly, I would like to say that I am posting this again because after having an instant reply from an 'Andrew', and posting my dmp files as requested on July 24th I haven't heard anything back since! I have responded a couple of times but nothing is happening to...
  3. BSOD Minidump shows page_faul ntoskrnl..exe

    in Windows 10 BSOD Crashes and Debugging
    BSOD Minidump shows page_faul ntoskrnl..exe: Hi there, My new machine around 8 months old now runs perfectly most of the time. Uptime 3 - 6 weeks at a time. NO issues at all - I am a heavy PC user: Gaming, Audio Work and some 3D modelling, so my machine goes through its paces.Every now and then on boot, I get the error...
  4. BSOD win32kfull

    in Windows 10 Drivers and Hardware
    BSOD win32kfull: HiI have started to get this blue screen error any ideas. There are no driver problems in device manager. Please let me know if you can see what has happened,I have left the latest dmp files herehttps://www.dropbox.com/sh/ei6t5oy0u4afik3/AAB8iAzMZhNvWtGnSTHePIK3a?dl=0Thanks...
  5. 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...
  6. BSOD This was probably caused by the following module: ntoskrnl.exe nt+0x3F5780 Bugcheck...

    in Windows 10 BSOD Crashes and Debugging
    BSOD This was probably caused by the following module: ntoskrnl.exe nt+0x3F5780 Bugcheck...: Hi, I'm currently having BSOD every time my pc is under intense gaming 3 hours My cpu and gpu are both overclocked. I have enough storage, all drivers are up to date. CPU: i7-8700k w/ Corsair H115i AIO liquid cooler GPU: Aorus RX 580 MOBO: Aorus Gaming 7 RAM: Corsair...
  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 ntoskrnl..exe

    in Windows 10 BSOD Crashes and Debugging
    BSOD ntoskrnl..exe: My computer has crashed a few times often when i play games. I bought more ram because i thought that it was the issue but it didn't help. It did work a few days but then the crashes came back. After that i fixed the BSOD´s by lowering the graphics and the resolution on the...
  9. BSOD ntoskrnl..exe+1b35e0

    in Windows 10 BSOD Crashes and Debugging
    BSOD ntoskrnl..exe+1b35e0: Help. Getting 4-5 of these a day. Running latest Windows 10 Pro, Xibo signboard, Docker with Xibo server. Always the same 'Caused By Address'. Put in new memory, ran memory test, no errors, all drivers up to date. Change disk type to AHCA, made sure windows driver was...
  10. BSOD caused by ntoskrnl exceptions

    in Windows 10 BSOD Crashes and Debugging
    BSOD caused by ntoskrnl exceptions: Hello to anyone that is willing to help my name is Glenn, My pc was assembled by professionals but it got really hot so a month ago I took my cpu cooler off and noticed that they left the plastic on the cpu cooling block, So I fixed that issue after emailing the people...

Users found this page by searching for:

  1. this was probably caused by the following module: ntoskrnl.exe (nt 0x1c1220)