Das hat doch mal was erbracht. In beiden Speicherdumps wird als Auslöser der Treiber:
athwnx.sys benannt. Das ist der Treiber Deines Atheros Netzwerkadapters. Also erneuere mal diesen Treiber, lade ihn aber von der Gigabyte Hompage herunter.
Die Auswertung der Speicherdumps (Hervorhebungen sind von mir):
-------------------------------------------------------------
Loading Dump File [D:\Downloads\110514-4421-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred symsrv*symsrv.dll*C:\Programdata\Microsoft\Localsymbols*
http://msdl.microsoft.com/download/symbols
Symbol search path is: symsrv*symsrv.dll*C:\Programdata\Microsoft\Localsymbols*
http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.16384.amd64fre.winblue_rtm.130821-1623
Machine Name:
Kernel base = 0xfffff802`8a287000 PsLoadedModuleList = 0xfffff802`8a54e9b0
Debug session time: Wed Nov 5 12:46:09.331 2014 (UTC + 1:00)
System Uptime: 0 days 0:02:31.968
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 D1, {0, 2, 8, 0}
*** WARNING: Unable to verify timestamp for athwnx.sys
*** ERROR: Module load completed but symbols could not be loaded for athwnx.sys
Probably caused by : athwnx.sys ( athwnx+f540e )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: 0000000000000000, address which referenced memory
Debugging Details:
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8028a5d7150
GetUlongFromAddress: unable to read from fffff8028a5d7208
0000000000000000 Nonpaged pool
CURRENT_IRQL: 2
FAULTING_IP:
+27d67b694df6
00000000`00000000 ?? ???
PROCESS_NAME: svchost.exe
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: AV
ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
DPC_STACK_BASE: FFFFF8028BBE3FB0
TRAP_FRAME: fffff8028bbe37e0 -- (.trap 0xfffff8028bbe37e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffe00002817030 rbx=0000000000000000 rcx=ffffe00002817030
rdx=ffffe000027fa2a0 rsi=0000000000000000 rdi=0000000000000000
rip=0000000000000000 rsp=fffff8028bbe3978 rbp=fffff8028bbe3b79
r8=fffff80001f66ca0 r9=fffff8028bbe3738 r10=ffffe00002c10470
r11=fffff80001d76328 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
00000000`00000000 ?? ???
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff8028a3e2be9 to fffff8028a3d70a0
FAILED_INSTRUCTION_ADDRESS:
+27d67b694df6
00000000`00000000 ?? ???
STACK_TEXT:
fffff802`8bbe3978 fffff800`01da940e : 00000000`00000000 fffff802`00000000 00000000`00000000 fffff800`01f573ee : 0x0
fffff802`8bbe3980 00000000`00000000 : fffff802`00000000 00000000`00000000 fffff800`01f573ee 00000000`027fa030 : athwnx+0xf540e
STACK_COMMAND: .trap 0xfffff8028bbe37e0 ; kb
FOLLOWUP_IP:
athwnx+f540e
fffff800`01da940e ?? ???
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: athwnx+f540e
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: athwnx
IMAGE_NAME: athwnx.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 51591bd5
FAILURE_BUCKET_ID: AV_CODE_AV_NULL_IP_athwnx+f540e
BUCKET_ID: AV_CODE_AV_NULL_IP_athwnx+f540e
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:av_code_av_null_ip_athwnx+f540e
FAILURE_ID_HASH: {7251d0a5-6b23-414c-0c37-837d73eb93e9}
Followup: MachineOwner
---------
0: kd> lmvm athwnx
start end module name
fffff800`01cb4000 fffff800`0203d000 athwnx T (no symbols)
Loaded symbol image file: athwnx.sys
Image path: \SystemRoot\system32\DRIVERS\athwnx.sys
Image name: athwnx.sys
Timestamp: Mon Apr 01 07:32:05 2013 (51591BD5)
CheckSum: 003894D2
ImageSize: 00389000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
-------------------------------------------------------------
