BSOD (Bluescreen) windows 10

[Smilingjack]

I'm having very regular BSOD and Although Im able to undestand to some extend the minidumps I cant quite fix it myself so I was wondering if you would help me I used driver verifier to find and crash the system to see the results and I will give you the dumpfile if you could help me
http://www.filedropper.com/020917-21078-01 the link to the minidump

and here is the report of windbg on the minidump for those that cant download
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 14393 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 14393.693.amd64fre.rs1_release.161220-1747
Machine Name:
Kernel base = 0xfffff801`d667e000 PsLoadedModuleList = 0xfffff801`d6983060
Debug session time: Thu Feb 9 18:01:29.349 2017 (UTC + 2:00)
System Uptime: 0 days 1:42:58.176
Loading Kernel Symbols
..

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

.............................................................
................................................................
................................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C4, {f6, 6b4, ffffe487a2b52800, fffff801d6b51f5e}

*** WARNING: Unable to verify timestamp for xhunter1.sys
*** ERROR: Module load completed but symbols could not be loaded for xhunter1.sys
Probably caused by : xhunter1.sys ( xhunter1+13f6 )

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

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught. This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 00000000000000f6, Referencing user handle as KernelMode.
Arg2: 00000000000006b4, Handle value being referenced.
Arg3: ffffe487a2b52800, Address of the current process.
Arg4: fffff801d6b51f5e, Address inside the driver that is performing the incorrect reference.

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10.0.14393.693 (rs1_release.161220-1747)

SYSTEM_PRODUCT_NAME: To Be Filled By O.E.M.

SYSTEM_SKU: To Be Filled By O.E.M.

SYSTEM_VERSION: To Be Filled By O.E.M.

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: P1.60

BIOS_DATE: 07/23/2015

BASEBOARD_MANUFACTURER: ASRock

BASEBOARD_PRODUCT: H81M-DGS R2.0

BASEBOARD_VERSION:

DUMP_TYPE: 2

DUMP_FILE_ATTRIBUTES: 0xc
Insufficient Dumpfile Size
Kernel Generated Triage Dump

BUGCHECK_P1: f6

BUGCHECK_P2: 6b4

BUGCHECK_P3: ffffe487a2b52800

BUGCHECK_P4: fffff801d6b51f5e

BUGCHECK_STR: 0xc4_f6

CPU_COUNT: 4

CPU_MHZ: dab

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3c

CPU_STEPPING: 3

CPU_MICROCODE: 6,3c,3,0 (F,M,S,R) SIG: 1E'00000000 (cache) 1E'00000000 (init)

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME: xcoronahost.xe

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST: SECRETLYINSANE

ANALYSIS_SESSION_TIME: 02-09-2017 18:04:59.0400

ANALYSIS_VERSION: 10.0.14321.1024 amd64fre

LAST_CONTROL_TRANSFER: from fffff801d6d8a360 to fffff801d67c86f0

STACK_TEXT:
ffffb181`415df298 fffff801`d6d8a360 : 00000000`000000c4 00000000`000000f6 00000000`000006b4 ffffe487`a2b52800 : nt!KeBugCheckEx
ffffb181`415df2a0 fffff801`d6d8f955 : ffffe487`a2b52800 00000000`00000000 ffffe487`00000000 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x48
ffffb181`415df2e0 fffff801`d6c59afb : 00000000`00000000 00000000`00000000 fffff801`d6b0ccd0 ffffe487`6f858800 : nt!VfCheckUserHandle+0x1ad
ffffb181`415df3c0 fffff801`d6b51f5e : fffff801`d69a2400 ffffb181`001fffff 00000000`00000000 fffff801`d67ce200 : nt! ?? ::NNGAKEGL::`string'+0x618bb
ffffb181`415df460 fffff805`7d6113f6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000079 : nt!ObReferenceObjectByHandle+0x2e
ffffb181`415df4b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000079 ffffb181`415df4f0 : xhunter1+0x13f6


STACK_COMMAND: kb

THREAD_SHA1_HASH_MOD_FUNC: 14901a8d5265138a3bbdc4cb65e883a7cb721603

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 3368ab3d4d1a7d5f0e3bc83345a9f5133bfbd369

THREAD_SHA1_HASH_MOD: 4f1c0c40351f3b579f4d5fae7f0d58204065436e

FOLLOWUP_IP:
xhunter1+13f6
fffff805`7d6113f6 ?? ???

SYMBOL_STACK_INDEX: 5

SYMBOL_NAME: xhunter1+13f6

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: xhunter1

IMAGE_NAME: xhunter1.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 58006e6a

BUCKET_ID_FUNC_OFFSET: 13f6

FAILURE_BUCKET_ID: 0xc4_f6_VRFK_xhunter1!unknown_function

BUCKET_ID: 0xc4_f6_VRFK_xhunter1!unknown_function

PRIMARY_PROBLEM_CLASS: 0xc4_f6_VRFK_xhunter1!unknown_function

TARGET_TIME: 2017-02-09T16:01:29.000Z

OSBUILD: 14393

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: 2016-12-21 08:50:57

BUILDDATESTAMP_STR: 161220-1747

BUILDLAB_STR: rs1_release

BUILDOSVER_STR: 10.0.14393.693

ANALYSIS_SESSION_ELAPSED_TIME: 422

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0xc4_f6_vrfk_xhunter1!unknown_function

FAILURE_ID_HASH: {599d1c3e-6660-9452-9f5f-4cd786730e0b}

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

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught. This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 00000000000000f6, Referencing user handle as KernelMode.
Arg2: 00000000000006b4, Handle value being referenced.
Arg3: ffffe487a2b52800, Address of the current process.
Arg4: fffff801d6b51f5e, Address inside the driver that is performing the incorrect reference.

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10.0.14393.693 (rs1_release.161220-1747)

SYSTEM_PRODUCT_NAME: To Be Filled By O.E.M.

SYSTEM_SKU: To Be Filled By O.E.M.

SYSTEM_VERSION: To Be Filled By O.E.M.

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: P1.60

BIOS_DATE: 07/23/2015

BASEBOARD_MANUFACTURER: ASRock

BASEBOARD_PRODUCT: H81M-DGS R2.0

BASEBOARD_VERSION:

DUMP_TYPE: 2

DUMP_FILE_ATTRIBUTES: 0xc
Insufficient Dumpfile Size
Kernel Generated Triage Dump

BUGCHECK_P1: f6

BUGCHECK_P2: 6b4

BUGCHECK_P3: ffffe487a2b52800

BUGCHECK_P4: fffff801d6b51f5e

BUGCHECK_STR: 0xc4_f6

CPU_COUNT: 4

CPU_MHZ: dab

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3c

CPU_STEPPING: 3

CPU_MICROCODE: 6,3c,3,0 (F,M,S,R) SIG: 1E'00000000 (cache) 1E'00000000 (init)

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME: xcoronahost.xe

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST: SECRETLYINSANE

ANALYSIS_SESSION_TIME: 02-09-2017 18:05:00.0462

ANALYSIS_VERSION: 10.0.14321.1024 amd64fre

LAST_CONTROL_TRANSFER: from fffff801d6d8a360 to fffff801d67c86f0

STACK_TEXT:
ffffb181`415df298 fffff801`d6d8a360 : 00000000`000000c4 00000000`000000f6 00000000`000006b4 ffffe487`a2b52800 : nt!KeBugCheckEx
ffffb181`415df2a0 fffff801`d6d8f955 : ffffe487`a2b52800 00000000`00000000 ffffe487`00000000 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x48
ffffb181`415df2e0 fffff801`d6c59afb : 00000000`00000000 00000000`00000000 fffff801`d6b0ccd0 ffffe487`6f858800 : nt!VfCheckUserHandle+0x1ad
ffffb181`415df3c0 fffff801`d6b51f5e : fffff801`d69a2400 ffffb181`001fffff 00000000`00000000 fffff801`d67ce200 : nt! ?? ::NNGAKEGL::`string'+0x618bb
ffffb181`415df460 fffff805`7d6113f6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000079 : nt!ObReferenceObjectByHandle+0x2e
ffffb181`415df4b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000079 ffffb181`415df4f0 : xhunter1+0x13f6


STACK_COMMAND: kb

THREAD_SHA1_HASH_MOD_FUNC: 14901a8d5265138a3bbdc4cb65e883a7cb721603

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 3368ab3d4d1a7d5f0e3bc83345a9f5133bfbd369

THREAD_SHA1_HASH_MOD: 4f1c0c40351f3b579f4d5fae7f0d58204065436e

FOLLOWUP_IP:
xhunter1+13f6
fffff805`7d6113f6 ?? ???

SYMBOL_STACK_INDEX: 5

SYMBOL_NAME: xhunter1+13f6

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: xhunter1

IMAGE_NAME: xhunter1.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 58006e6a

BUCKET_ID_FUNC_OFFSET: 13f6

FAILURE_BUCKET_ID: 0xc4_f6_VRFK_xhunter1!unknown_function

BUCKET_ID: 0xc4_f6_VRFK_xhunter1!unknown_function

PRIMARY_PROBLEM_CLASS: 0xc4_f6_VRFK_xhunter1!unknown_function

TARGET_TIME: 2017-02-09T16:01:29.000Z

OSBUILD: 14393

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: 2016-12-21 08:50:57

BUILDDATESTAMP_STR: 161220-1747

BUILDLAB_STR: rs1_release

BUILDOSVER_STR: 10.0.14393.693

ANALYSIS_SESSION_ELAPSED_TIME: 434

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0xc4_f6_vrfk_xhunter1!unknown_function

FAILURE_ID_HASH: {599d1c3e-6660-9452-9f5f-4cd786730e0b}

Followup: MachineOwner

 

[Colif]

i see Bulgaria on their contacts list on web site so I have to assume the warranty would work and they should have someone you can send ram stick(s) back to.

Have you had any bsod since identifying ram?

 

[Smilingjack]

So I've returned the ram and got the replacement from them so far havent had any bsod will update further as I use it before usage I did a complete memtest with no errors this time in either stick or slot