Windows 10: Rnadom BSOD mostly KMODE Exception or kernel trap errors

Hi I've been getting non stop BSOD errors non-stop since I purchased this machine... mostly KMODE EXCEPTION FAULT related to clipsp.sys
I've attached the contents of the minidump file below …

Can someone help me troubleshoot this? (I've already had a motherboard replacements and isolated all 4 memory DIMMs only to find that the errors are still happening … the CPU is being replaced this week as well, but I suspect it is something inside of windows that is the problem).


Microsoft (R) Windows Debugger Version 10.0.18272.1001 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\121118-13421-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 17134 MP (32 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 17134.1.amd64fre.rs4_release.180410-1804
Machine Name:
...............................................................
................................................................
...............................................................
Loading User Symbols
Loading unloaded module list
...........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff800`908520a0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffa901`7a88a530=000000000000007f
7: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: ffffa9017a88a670
Arg3: ffffa9017a893000
Arg4: fffff802f0b43db4

Debugging Details:
------------------


KEY_VALUES_STRING: 1


STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 17134.1.amd64fre.rs4_release.180410-1804

SYSTEM_MANUFACTURER: Alienware

SYSTEM_PRODUCT_NAME: Alienware Area-51 R6

SYSTEM_SKU: 833

BIOS_VENDOR: Alienware

BIOS_VERSION: 1.1.4

BIOS_DATE: 01/29/2018

BASEBOARD_MANUFACTURER: Alienware

BASEBOARD_PRODUCT: 08FN1W

BASEBOARD_VERSION: A01

DUMP_TYPE: 2

BUGCHECK_P1: 8

BUGCHECK_P2: ffffa9017a88a670

BUGCHECK_P3: ffffa9017a893000

BUGCHECK_P4: fffff802f0b43db4

BUGCHECK_STR: 0x7f_8

TRAP_FRAME: ffffa9017a88a670 -- (.trap 0xffffa9017a88a670)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff802f0b453a0
rdx=000000b498bfd208 rsi=0000000000000000 rdi=0000000000000000
rip=fffff802f0b43db4 rsp=ffffa9017a893000 rbp=ffff858bfdf32a70
r8=000000007e97a312 r9=ffffa9017d970dd4 r10=00000000d3f920c7
r11=00000000cf630253 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
clipsp+0x3db4:
fffff802`f0b43db4 51 push rcx
Resetting default scope

CPU_COUNT: 20

CPU_MHZ: d42

CPU_VENDOR: AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 1

CPU_STEPPING: 1

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXPNP: 1 (!blackboxpnp)


CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: svchost.exe

CURRENT_IRQL: 1

ANALYSIS_SESSION_TIME: 12-11-2018 17:43:51.0935

ANALYSIS_VERSION: 10.0.18272.1001 amd64fre

BAD_STACK_POINTER: ffffa9017a893000

LAST_CONTROL_TRANSFER: from fffff80090862c69 to fffff800908520a0

STACK_TEXT:
ffffa901`7a88a528 fffff800`90862c69 : 00000000`0000007f 00000000`00000008 ffffa901`7a88a670 ffffa901`7a893000 : nt!KeBugCheckEx
ffffa901`7a88a530 fffff800`9085e57f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffffa901`7a88a670 fffff802`f0b43db4 : fdf33c90`00000000 00000000`ffff858b 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0x27f
ffffa901`7a893000 fdf33c90`00000000 : 00000000`ffff858b 00000000`00000000 00000000`00000000 7a88a800`00000000 : clipsp+0x3db4
ffffa901`7a893008 00000000`ffff858b : 00000000`00000000 00000000`00000000 7a88a800`00000000 7a88c800`ffffa901 : 0xfdf33c90`00000000
ffffa901`7a893010 00000000`00000000 : 00000000`00000000 7a88a800`00000000 7a88c800`ffffa901 7a890800`ffffa901 : 0xffff858b


THREAD_SHA1_HASH_MOD_FUNC: 573260407b371f6e7847ac4e329301640001c79b

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 1afd1b80ce7cd6b1fa6ef57ab78ce9fa7d53277d

THREAD_SHA1_HASH_MOD: 90df5b10d4a62af8f1369674ad30c00578ddc212

FOLLOWUP_IP:
clipsp+3db4
fffff802`f0b43db4 51 push rcx

FAULT_INSTR_CODE: d43b4851

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: clipsp+3db4

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: clipsp

IMAGE_NAME: clipsp.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5c0b743f

IMAGE_VERSION: 10.0.17134.471

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 3db4

FAILURE_BUCKET_ID: 0x7f_8_STACKPTR_ERROR_clipsp!unknown_function

BUCKET_ID: 0x7f_8_STACKPTR_ERROR_clipsp!unknown_function

PRIMARY_PROBLEM_CLASS: 0x7f_8_STACKPTR_ERROR_clipsp!unknown_function

TARGET_TIME: 2018-12-11T23:17:28.000Z

OSBUILD: 17134

OSSERVICEPACK: 471

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: 2018-12-08 01:36:08

BUILDDATESTAMP_STR: 180410-1804

BUILDLAB_STR: rs4_release

BUILDOSVER_STR: 10.0.17134.1.amd64fre.rs4_release.180410-1804

ANALYSIS_SESSION_ELAPSED_TIME: 28cb

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x7f_8_stackptr_error_clipsp!unknown_function

FAILURE_ID_HASH: {48f2dfdf-6e28-ad4e-f693-f41bb475ff86}

Followup: MachineOwner
---------

7: kd> .trap 0xffffa9017a88a670
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff802f0b453a0
rdx=000000b498bfd208 rsi=0000000000000000 rdi=0000000000000000
rip=fffff802f0b43db4 rsp=ffffa9017a893000 rbp=ffff858bfdf32a70
r8=000000007e97a312 r9=ffffa9017d970dd4 r10=00000000d3f920c7
r11=00000000cf630253 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
clipsp+0x3db4:
fffff802`f0b43db4 51 push rcx
7: kd> !blackboxbsd
Stream size mismatch (expected = 168, read = 136)
7: kd> !blackboxpnp
PnpActivityId : {00000000-0000-0000-0000-000000000000}
PnpActivityTime : 131890433044513382
PnpEventInformation: 6
PnpEventInProgress : 0
PnpProblemCode : 31
PnpVetoType : 0
DeviceId : ROOT\SYSTEM\0004
VetoString :

7: kd> lmvm clipsp
Browse full module list
start end module name
fffff802`f0b40000 fffff802`f0c42000 clipsp (export symbols) clipsp.sys
Loaded symbol image file: clipsp.sys
Mapped memory image file: C:\ProgramData\Dbg\sym\clipsp.sys\5C0B743F102000\clipsp.sys
Image path: \SystemRoot\System32\drivers\clipsp.sys
Image name: clipsp.sys
Browse all global symbols functions data
Timestamp: Fri Dec 7 23:35:27 2018 (5C0B743F)
CheckSum: 000FCBC0
ImageSize: 00102000
File version: 10.0.17134.471
Product version: 10.0.17134.471
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 3.7 Driver
File date: 00000000.00000000
Translations: 0409.04b0
Information from resource tables:
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: clipsp.dll
OriginalFilename: clipsp.dll
ProductVersion: 10.0.17134.471
FileVersion: 10.0.17134.471 (WinBuild.160101.0800)
FileDescription: CLIP Service
LegalCopyright: © Microsoft Corporation. All rights reserved.
7: kd> x /D /f clipsp!a*

:)

 

Windows 10 - BSOD: KMODE EXCEPTION NOT HANDLED

Thanks Andre,

Was able to restore to previous point.

Now KB4088776 is back.

However,previous problem persists - Kmode exception error when running the game, though now a second error appeared as well -

Unexpected Kernel Mode Trap

 

unexpected kernel mode trap BSOD

Hi Adam,

Thank you for posting in Community.

We understand your concern and we will provide the information required to help you resolve the issue.

Before we proceed, I would like you to provide the information stated below:

Do you get the error message/BSOD only when you uninstall, reinstall, etc third party app?

The error UNEXPECTED_KERNEL_MODE_TRAP indicates that the Intel CPU generated a trap and the kernel failed to catch this trap. This trap could be a
bound trap (a trap the kernel is not permitted to catch) or a double fault (a fault that occurred while processing an earlier fault, which always results in a system failure).

To know the exact cause of the BSOD, I suggest that you provide the Dump files that were produced when the error occurred, or the Event ID from your Event Viewer which was recorded during the time of the crash.

Hope this helps

 

BSOD

So I got a new PC and I started getting A LOT OF BSOD(Up tp 25-30 a day) most of them read:

-Kernel mode trap error

-pfn list corrupt

-kernel security check failiure

-Memory Management

-irql_not_less_or_equal

-system service exception (win32kbase.sys)

-kmode exception not handled

-drive_irql_not_less_or_equal

my mini dumps: minidump2.rar