Share via

BSOD Crashes

Anonymous
2019-03-30T21:54:33+00:00

Hello,

I often receive BSOD crashes. I've performed clean Windows 10 installation and I'm still having them. I need your help. Below you can find the dump files description of the today's crashes:

Crash dump directories:

C:\Windows

C:\Windows\Minidump

On Sat 30.3.2019 ?. 23:02:47 your computer crashed or a problem was reported

crash dump file: C:\Windows\Minidump\033019-6890-01.dmp

This was probably caused by the following module: win32kbase.sys (0xFFFFC29138FCBEC5)

Bugcheck code: 0x3B (0xC0000005, 0xFFFFC29138FCBEC5, 0xFFFFEA8B62F2ED70, 0x0)

Error: SYSTEM_SERVICE_EXCEPTION

file path: C:\Windows\system32\win32kbase.sys

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: Base 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 30.3.2019 ?. 23:02:47 your computer crashed or a problem was reported

crash dump file: C:\Windows\MEMORY.DMP

This was probably caused by the following module: win32kbase.sys (0xFFFFC29138FCBEC5)

Bugcheck code: 0x3B (0xC0000005, 0xFFFFC29138FCBEC5, 0xFFFFEA8B62F2ED70, 0x0)

Error: SYSTEM_SERVICE_EXCEPTION

file path: C:\Windows\system32\win32kbase.sys

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: Base 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 30.3.2019 ?. 22:17:03 your computer crashed or a problem was reported

crash dump file: C:\Windows\Minidump\033019-7890-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x1B35E0)

Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF804213D0905, 0x0, 0xFFFFFFFFFFFFFFFF)

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 Sat 30.3.2019 ?. 22:10:26 your computer crashed or a problem was reported

crash dump file: C:\Windows\Minidump\033019-7562-01.dmp

This was probably caused by the following module: wdfilter.sys (0xFFFFF808D1AD8EC7)

Bugcheck code: 0x50 (0xFFFFFFFFE98B491A, 0x2, 0xFFFFF808D1AD8EC7, 0x2)

Error: PAGE_FAULT_IN_NONPAGED_AREA

file path: C:\Windows\system32\drivers\wdfilter.sys

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: Microsoft antimalware file system filter driver

Bug check description: This indicates that invalid system memory has been referenced.

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 30.3.2019 ?. 21:12:29 your computer crashed or a problem was reported

crash dump file: C:\Windows\Minidump\033019-7937-02.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x1B35E0)

Bugcheck code: 0x4A (0x7FF95B21F954, 0x2, 0x0, 0xFFFFF18B13F17A80)

Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE

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 thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.

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 30.3.2019 ?. 19:54:34 your computer crashed or a problem was reported

crash dump file: C:\Windows\Minidump\033019-7406-01.dmp

This was probably caused by the following module: tcpip.sys (0xFFFFF803784EBF4A)

Bugcheck code: 0xD1 (0x0, 0x2, 0x1, 0xFFFFF803784EBF4A)

Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL

file path: C:\Windows\system32\drivers\tcpip.sys

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: TCP/IP Driver

Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.

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 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.

I've done the following:

  1. Updated all drivers (windows and all other) with the latest ones;
  2. Performed memory checks and almost everything which was written here in the community;
  3. Reinstalled windows and I'm still having them;
  4. Contacted two Microsoft Tech Support persons - they performed all needed checks and said it is probably drivers issue.

Than you for your time in advance!

Windows for home | Windows 10 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

14 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Igor Leyko 111K Reputation points Independent Advisor
    2019-03-30T22:36:23+00:00

    Laptop or motherboard manufacturers have instructions for BIOS update on their site.

    In my thinking this problem is hardware rather than software.

    Did you rum memory diagnostic in normal mode or in wide mode - you may change the mode before testing but after tool will start.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2019-03-30T22:24:52+00:00

    Hi Andrey

    BSOD's are generally caused by a corrupt or incompatible device driver and sometimes incompatible software, to diagnose the underlying issue, I need to analyse your Mini-dump file(s) to see if I can find the underlying issue:

    Open Windows File Explorer

    Navigate to C:\Windows\Minidump

    Zip up the contents of that folder

    If you have problems zipping those files, copy them out onto your Desktop and zip them from there

    Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)

    Then post a link here to the zip file, so we can take a look for you . . .

    Hi Dave,

    Please find the link for the dump files in OneDrive:

    https://1drv.ms/u/s!AuES\_6puJRBCjh4Lg6iQirbJ4WSz

    Was this answer helpful?

    0 comments
  3. Anonymous
    2019-03-30T22:23:37+00:00

    Hi Andrey,

    please repair system using DISM.exe /Online /Cleanup-Image /RestoreHealth

    command from Windows PowerShell (administrator) environment.

    Please check for bios and drivers updates.

    Did you use tools such as DpiverPack, DriverEasy or similar? They may install incorrect drivers causing different problems.

    And please run built-in memory diagnostic in wide mode.

    Hi Igor,

    1. [==========================100.0%==========================] The restore operation completed successfully.

    The operation completed successfully.

    I've done that as per your advice.

    1. All drivers were checked and are up to date except the BIOS ones. I do not know how to update the BIOS.
    2. No, I haven't used any third party program for drivers.
    3. I ran the memory diagnostic and nothing was found.

    Was this answer helpful?

    0 comments
  4. DaveM121 891.1K Reputation points Independent Advisor
    2019-03-30T22:05:53+00:00

    Hi Andrey

    BSOD's are generally caused by a corrupt or incompatible device driver and sometimes incompatible software, to diagnose the underlying issue, I need to analyse your Mini-dump file(s) to see if I can find the underlying issue:

    Open Windows File Explorer

    Navigate to C:\Windows\Minidump

    Zip up the contents of that folder

    If you have problems zipping those files, copy them out onto your Desktop and zip them from there

    Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)

    Then post a link here to the zip file, so we can take a look for you . . .

    Was this answer helpful?

    0 comments
  5. Igor Leyko 111K Reputation points Independent Advisor
    2019-03-30T22:04:26+00:00

    Hi Andrey,

    please repair system using DISM.exe /Online /Cleanup-Image /RestoreHealth

    command from Windows PowerShell (administrator) environment.

    Please check for bios and drivers updates.

    Did you use tools such as DpiverPack, DriverEasy or similar? They may install incorrect drivers causing different problems.

    And please run built-in memory diagnostic in wide mode.

    Was this answer helpful?

    0 comments