Hello,
I see you waiting for so long so here is what your dumps look like:
Dump 1:
Code:
6: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
[B]CRITICAL_STRUCTURE_CORRUPTION (109)[/B]
[COLOR=#ff0000]This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
[/COLOR]1) A driver has inadvertently or deliberately modified critical kernel code
or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
debugger that was not attached when the system was booted. Normal breakpoints,
"bp", can only be set if the debugger is attached at boot time. Hardware
breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a3a01f5a16fa06f3, Reserved
Arg2: b3b72be069793ea6, Reserved
Arg3: fffff8017f72d380, Failure type dependent information
Arg4: 0000000000000001, Type of corrupted region, can be
0 : A generic data region
1 : Modification of a function or .pdata
2 : A processor IDT
3 : A processor GDT
4 : Type 1 process list corruption
5 : Type 2 process list corruption
6 : Debug routine modification
7 : Critical MSR modification
Debugging Details:
------------------
PG_MISMATCH: 200000
MEMORY_CORRUPTOR: ONE_BIT
FAULTING_IP:
Ntfs!NtfsFreeReservedClusters+29b00
fffff801`7f72d380 488b4b58 mov rcx,qword ptr [rbx+58h]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: CODE_CORRUPTION
BUGCHECK_STR: 0x109
PROCESS_NAME: System
CURRENT_IRQL: 2
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
STACK_TEXT:
ffffd001`12493088 00000000`00000000 : 00000000`00000109 a3a01f5a`16fa06f3 b3b72be0`69793ea6 fffff801`7f72d380 : nt!KeBugCheckEx
STACK_COMMAND: kb
CHKIMG_EXTENSION: !chkimg -lo 50 -d !Ntfs
fffff8017f72d3af - Ntfs!NtfsFreeReservedClusters+29b2f
[ 48:58 ]
1 error : !Ntfs (fffff8017f72d3af)
MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT
BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:memory_corruption_one_bit
FAILURE_ID_HASH: {e3faf315-c3d0-81db-819a-6c43d23c63a7}
Followup: memory_corruption
---------
Dump 2:
Indicates that a severe memory management error occurred, dump 1 says it could also be caused by failing RAM or or even Hard drive, just assuming because it stuck at Ntfs!NtfsFreeReservedClusters
Code:
7: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
[B]MEMORY_MANAGEMENT (1a)[/B]
[COLOR=#ff0000]# Any other values for parameter 1 must be individually examined.[/COLOR]
Arguments:
Arg1: 0000000000000[COLOR=#ff0000]402[/COLOR], The subtype of the bugcheck.
Arg2: ffffc00090da4e40
Arg3: 8000000174818b8a
Arg4: ffffc00098da4e41
Debugging Details:
------------------
BUGCHECK_STR: 0x1a_402
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 2
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
LAST_CONTROL_TRANSFER: from fffff8007f38e4c7 to fffff8007f361ca0
STACK_TEXT:
ffffd000`315718d8 fffff800`7f38e4c7 : 00000000`0000001a 00000000`00000402 ffffc000`90da4e40 80000001`74818b8a : nt!KeBugCheckEx
ffffd000`315718e0 fffff800`7f28126c : 00000000`00000000 ffffe001`28970690 00000000`00384000 00000000`00384000 : nt! ?? ::FNODOBFM::`string'+0x1c307
ffffd000`31571940 fffff800`7f5ba00b : ffffe001`28970690 00000000`00002000 ffffe001`00002001 00000000`00000000 : nt!MiDeleteSegmentPages+0x1c0
ffffd000`315719d0 fffff800`7f257f69 : 00000000`00000002 ffffd000`31571a40 ffffe001`2145f080 fffff800`7f2c2226 : nt!MiSegmentDelete+0x57
ffffd000`31571a10 fffff800`7f63e944 : 00000000`00000000 00000000`00000000 ffffe001`2145f080 ffffc000`8bbb32f0 : nt!MiCheckControlArea+0x1bd
ffffd000`31571a70 fffff800`7f26401f : 00000000`00000000 ffffe001`28db92f0 ffffc000`8bbb3320 fffff800`7f4c3340 : nt!ObpRemoveObjectRoutine+0x64
ffffd000`31571ad0 fffff800`abeb5042 : ffffe001`28db92f0 ffffe001`2836f880 00000000`00000000 fffff800`7f4c3340 : nt!ObfDereferenceObject+0x8f
ffffd000`31571b10 fffff800`7f2be6bc : fffff800`7f283354 ffffe001`2836f9c0 ffffe001`26376610 fffff800`7f4c3340 : dxgmms1!VidMmProcessAsyncOperation+0x1a
ffffd000`31571b50 fffff800`7f31136c : 00000001`46dbc000 ffffe001`2836f880 00000000`00000080 ffffe001`2836f880 : nt!ExpWorkerThread+0x28c
ffffd000`31571c00 fffff800`7f3682c6 : ffffd001`c8240180 ffffe001`2836f880 ffffe001`21888880 ffffe001`29c3c6b0 : nt!PspSystemThreadStartup+0x58
ffffd000`31571c60 00000000`00000000 : ffffd000`31572000 ffffd000`3156c000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
dxgmms1!VidMmProcessAsyncOperation+1a
fffff800`abeb5042 8b05f86dfeff mov eax,dword ptr [dxgmms1!Microsoft_Windows_DxgKrnlEnableBits (fffff800`abe9be40)]
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: dxgmms1!VidMmProcessAsyncOperation+1a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 54505506
IMAGE_VERSION: 6.3.9600.17415
BUCKET_ID_FUNC_OFFSET: 1a
FAILURE_BUCKET_ID: 0x1a_402_dxgmms1!VidMmProcessAsyncOperation
BUCKET_ID: 0x1a_402_dxgmms1!VidMmProcessAsyncOperation
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x1a_402_dxgmms1!vidmmprocessasyncoperation
FAILURE_ID_HASH: {4cfe95d7-cae2-1726-7c73-a2ae9711b69f}
Followup: MachineOwner
---------
Dump 3:
Parameter 1 indicates whether a single DPC exceeded a timeout, or whether the system cumulatively spent an extended period of time.
Determining the cause with a first parameter of 1 is a bit more difficult because the problem is a result of DPCs running from multiple drivers, so the call stack is insufficient to determine the culprit.
Code:
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
[B]DPC_WATCHDOG_VIOLATION (133)[/B]
[COLOR=#ff0000]The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.[/COLOR]
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
DISPATCH_LEVEL or above. The offending component can usually be
identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: 0000000000000000
Arg4: 0000000000000000
Debugging Details:
------------------
DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x133
PROCESS_NAME: svchost.exe
CURRENT_IRQL: d
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
LAST_CONTROL_TRANSFER: from fffff8016a3f8f7e to fffff8016a3ddca0
STACK_TEXT:
fffff801`6bf2fc88 fffff801`6a3f8f7e : 00000000`00000133 00000000`00000001 00000000`00001e00 00000000`00000000 : nt!KeBugCheckEx
fffff801`6bf2fc90 fffff801`6a2c9871 : fffff801`6bf2fe60 00000000`00261717 ffff2352`ebbd934d fffff801`762a83b5 : nt! ?? ::FNODOBFM::`string'+0xadbe
fffff801`6bf2fd20 fffff801`6a2257b5 : 00000000`00400a02 ffffd001`cddb1bf0 fffff801`762a81c0 00000000`00006001 : nt!KeClockInterruptNotify+0x91
fffff801`6bf2ff40 fffff801`6a364143 : fffff801`6bf2ff60 00000000`00000008 fffff801`6bf2ff50 00000000`0000000c : hal!HalpTimerClockIpiRoutine+0x15
fffff801`6bf2ff70 fffff801`6a3df12a : fffff801`6a271800 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa3
fffff801`6bf2ffb0 fffff801`6a3df50f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
ffffd000`33a45a90 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchLBControl+0x11f
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+adbe
fffff801`6a3f8f7e cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+adbe
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 550f41a6
IMAGE_VERSION: 6.3.9600.17736
BUCKET_ID_FUNC_OFFSET: adbe
FAILURE_BUCKET_ID: 0x133_ISR_nt!_??_::FNODOBFM::_string_
BUCKET_ID: 0x133_ISR_nt!_??_::FNODOBFM::_string_
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x133_isr_nt!_??_::fnodobfm::_string_
FAILURE_ID_HASH: {89366ad1-5557-ac2b-d015-8f6ec2fdbf31}
Followup: MachineOwner
---------
As you can see there is nothing obvious at first glance, and it looks like it won't be easy to solve.
First 2 dumps could be about either a bad driver or failing hardware.
So first step the to eliminate either of these 2 possible causes is to test you hardware nice that's easier than hunting bad drivers.
To perform memory test follow this link:
Diagnosing memory problems on your computer
To Check your hard drive for bad sectors follow this link:
Check your hard disk for errors
To diagnoze your processor:
Intel® Processor Diagnostic Tool (64-bit)
As for dump 3 we would need to sit in from of your PC to possibly catch the driver, however here is a tutorial on how to do it yourself.
Windows Performance Toolkit
Check this one too
Providing more dumps could really help, if you're able to provide more then please do so.
Since bad driver could also be the cause check this website for updates:
Gygabyte drivers
Also visit Intel, Nvidia and other official websites for latest driver updates.
If you're unsure how to find latest and correct drivers let me know...
Disabling Windows update from updating your drivers is not bad:
Disable Searching Windows Update for Device Drivers
Afterwards you can run windows update and install optional updates ( if any )
Please post results of at least first 3 tests, and after you fully updated your system drivers. and then we will continue next.