Arie
vanochtend dacht ik even de dump files te analyseren, maar mijn debugomgeving was corrupt geraakt (had deze ook al in geen jaren meer gebruikt). Deze aan de praat gebracht, de symbols aangepast en toen jouw file erdoorheen gehaald.
Dit is het resultaat.
- Code:
Microsoft (R) Windows Debugger Version 6.5.0003.7
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Temp\minidump\012214-13447-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*C:\Program Files\Debugging Tools for Windows\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Longhorn Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Kernel base = 0xfffff800`03008000 PsLoadedModuleList = 0xfffff800`0324b6d0
Debug session time: Wed Jan 22 21:22:36.543 2014 (GMT+1)
System Uptime: 0 days 0:38:31.401
Loading Kernel Symbols
........................................................................................................................................................
Loading unloaded module list
.......
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffffae003e3989b, 0, fffff800030677af, 5}
Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+425 )
Followup: MachineOwner
---------
5: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffffae003e3989b, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff800030677af, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000005, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: GetUlongFromAddress: unable to read from fffff800032b5100
fffff800032352c0: Unable to get special pool info
fffff800032352c0: Unable to get special pool info
fffffae003e3989b
FAULTING_IP:
nt!MiAgeWorkingSet+425
fffff800`030677af 410fb65e1b movzx ebx,byte ptr [r14+0x1b]
MM_INTERNAL_CODE: 5
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x50
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff800030fef25 to fffff800030677af
TRAP_FRAME: fffff88003532680 -- (.trap fffff88003532680)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed.
rax=0000058000000000 rbx=0000000000000000 rcx=fffff680019aa9e0
rdx=0000000000000001 rsi=fffff70001080000 rdi=fffff800035f4b7f
rip=fffff800030677af rsp=fffff88003532810 rbp=00000000019aa9e6
r8=0000000000000001 r9=fffffa8018a683f8 r10=0000000000000005
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!MiAgeWorkingSet+0x425:
fffff800`030677af 410fb65e1b movzx ebx,byte ptr [r14+0x1b] ds:00000000`0000001b=??
Resetting default scope
STACK_TEXT:
fffff880`03532810 fffff800`030fef25 : fffffa80`18a683f8 fffff880`00000001 00000000`00000001 fffff880`03532a70 : nt!MiAgeWorkingSet+0x425
fffff880`035329c0 fffff800`03067b06 : 00000000`00000908 00000000`00000000 fffffa80`00000000 00000000`00000003 : nt! ?? ::FNODOBFM::`string'+0x4c7f6
fffff880`03532a40 fffff800`03067fb3 : 00000000`00000008 fffff880`03532ad0 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e
fffff880`03532a90 fffff800`0331a2ea : fffffa80`1884b9d0 00000000`00000080 fffffa80`18823740 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
fffff880`03532c00 fffff800`0306e8e6 : fffff880`009b3180 fffffa80`1884b9d0 fffff880`009be0c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03532c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
FOLLOWUP_IP:
nt!MiAgeWorkingSet+425
fffff800`030677af 410fb65e1b movzx ebx,byte ptr [r14+0x1b]
SYMBOL_STACK_INDEX: 0
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: nt!MiAgeWorkingSet+425
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 521ea035
STACK_COMMAND: .trap fffff88003532680 ; kb
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0x50_nt!MiAgeWorkingSet+425
BUCKET_ID: X64_0x50_nt!MiAgeWorkingSet+425
Followup: MachineOwner
---------
Je PC heeft een "memory_corruption" of te wel een defect geheugen. Dit kan ook sporadisch optreden (bijv. een warmte probleem) of veroorzaakt worden van slecht contact van de geheugenbank in het moederbordslot.
Om geheugen te testen gebruik je memtest86+
http://www.memtest.org/#downiso.
Download de versie waar *NEW achter staat.
Op
http://www.pcwebplus.nl/phpbb/viewtopic.php?f=244&t=8919 (Nederlandstalig) staat in de 2e helft van deze pagina beschreven hoe je dit op de USB stick zet. LET OP: de USB stick wordt geformatteerd, dus de data daarop eerst even veilig stellen.
Vervolgens de HauptwerkPC opstarten vanaf deze USB stick en memtest86+ een nacht laten draaien (tenzij je direct al fouten zit, want dan is het duidelijk)
Door banken te verwisselen of of de layout van je moederbord te kijken, kun je bepalen welke defect is.
En als je nog garantie op de PC hebt, zou ik alleen de test uitvoeren en dan naar de computershop gaan.
Maak een foto van het memtest86+ scherm, zeker als de fout later pas zichtbaar wordt in de duurtest en laat ze de afdruk zien (een print screen maken gaat dus niet) zodat zij de foute bank kunnen vervangen.