Hi,
ich hatte die letzten tage unregelmäßig Bluescreens. Die Crash Dumps habe ich debugged:
(Hardware siehe Signatur, Hauptrechner)
Erster
Zweiter
Was hat das zu bedeuten ?
Wie kann ich das Problem fixen ?
Memtest habe ich schon 2 mal durch laufen lassen mit 0 errors.
ich hatte die letzten tage unregelmäßig Bluescreens. Die Crash Dumps habe ich debugged:
(Hardware siehe Signatur, Hauptrechner)
Erster
Code:
Microsoft (R) Windows Debugger Version 6.4.0007.2
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini071709-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*e:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt
Built by: 2600.xpsp_sp3_gdr.080814-1236
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Fri Jul 17 16:28:17.656 2009 (GMT+2)
System Uptime: 0 days 1:23:07.270
Loading Kernel Symbols
.........................................................................................................................................................
Loading unloaded module list
...........
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 4E, {99, 3516aa, 0, 0}
Probably caused by : memory_corruption ( nt!MiDecrementShareCount+3a )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc). If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 00000099, A PTE or PFN is corrupt
Arg2: 003516aa, page frame number
Arg3: 00000000, current page state
Arg4: 00000000, 0
Debugging Details:
------------------
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x4E
LAST_CONTROL_TRANSFER: from 80522ddc to 804f9f43
STACK_TEXT:
b03d4c88 80522ddc 0000004e 00000099 003516aa nt!KeBugCheckEx+0x1b
b03d4cb8 80524338 c0600128 c0025f80 00000000 nt!MiDecrementShareCount+0x3a
b03d4cf8 805204bb 04bf0000 00000030 0013e64c nt!MiCopyOnWrite+0x1e6
b03d4d4c 80544588 00000001 04bf0000 00000001 nt!MmAccessFault+0xae9
b03d4d4c 606aaaf0 00000001 04bf0000 00000001 nt!KiTrap0E+0xd0
WARNING: Frame IP not in any known module. Following frames may be wrong.
0013e624 00000000 00000000 00000000 00000000 0x606aaaf0
FOLLOWUP_IP:
nt!MiDecrementShareCount+3a
80522ddc ff4e08 dec dword ptr [esi+0x8]
SYMBOL_STACK_INDEX: 1
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: nt!MiDecrementShareCount+3a
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 48a3fbd9
STACK_COMMAND: kb
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: 0x4E_nt!MiDecrementShareCount+3a
BUCKET_ID: 0x4E_nt!MiDecrementShareCount+3a
Followup: MachineOwner
---------Zweiter
Code:
Microsoft (R) Windows Debugger Version 6.4.0007.2
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini072409-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*e:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.080814-1236
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Fri Jul 24 16:16:14.312 2009 (GMT+2)
System Uptime: 0 days 3:32:58.059
Loading Kernel Symbols
........................................................................................................................................................
Loading unloaded module list
.............
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 10000050, {fe1f3f80, 1, 8053708f, 0}
Could not read faulting driver name
Probably caused by : memory_corruption
Followup: memory_corruption
---------
1: 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: fe1f3f80, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: 8053708f, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
WRITE_ADDRESS: fe1f3f80
FAULTING_IP:
nt!ExAllocatePoolWithQuotaTag+5
8053708f 088b4004ff75 or [ebx+0x75ff0440],cl
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: CODE_CORRUPTION
BUGCHECK_STR: 0x50
LAST_CONTROL_TRANSFER: from af40dcd1 to 8053708f
STACK_TEXT:
ab330b54 af40dcd1 00000000 00000028 7070534b nt!ExAllocatePoolWithQuotaTag+0x5
ab330bb8 af40ded9 88203b40 00000003 ac345a30 ks!KspPropertyHandler+0xab
ab330bdc ac34728c 88203b40 00000003 ac345a30 ks!KsPropertyHandler+0x19
ab330c30 af40df95 88a1e030 88203b40 ab330c64 sysaudio!CPinInstance::PinDispatchIoControl+0x115
ab330c40 804ef19f 88a1e030 88203b40 806e7410 ks!DispatchDeviceIoControl+0x28
ab330c50 8057f982 88203c88 887e6028 88203b40 nt!IopfCallDriver+0x31
ab330c64 805807f7 88a1e030 88203b40 887e6028 nt!IopSynchronousServiceTail+0x70
ab330d00 80579274 0000044c 00000344 00000000 nt!IopXxxControlFile+0x5c5
ab330d34 8054162c 0000044c 00000344 00000000 nt!NtDeviceIoControlFile+0x2a
ab330d34 7c91e4f4 0000044c 00000344 00000000 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
03acfde4 7c91d26c 7c8016c2 0000044c 00000344 0x7c91e4f4
03acfe48 73e721a2 0000044c 002f0003 03acfeb0 0x7c91d26c
03acfe80 73e72bf4 0000044c 002f0003 03acfeb0 0x73e721a2
03acfec8 73e72b7d 0000044c 73e72ba0 00000005 0x73e72bf4
03acfefc 73e727cd 03acff40 03acff3c 00000000 0x73e72b7d
03acff18 73e7df8e 03acff40 03acff3c 00000000 0x73e727cd
03acff44 73e7e220 00000000 03acff98 76af4e4f 0x73e7df8e
03acff5c 00820961 011d6798 00000000 03acff98 0x73e7e220
03acffa0 00820bd1 00820c1c 0013f9e8 011d6000 0x820961
03acffec 00000000 00820bd7 00000000 00000000 0x820bd1
CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
80537080-805370bf 64 bytes - nt!ExAllocatePoolWithTagPriority+5a
[ 5d c2 10 00 cc cc cc cc:15 0c 41 55 80 ff 75 f8 ]
64 errors : !nt (80537080-805370bf)
MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: LARGE_64
STACK_COMMAND: kb
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE_64
BUCKET_ID: MEMORY_CORRUPTION_LARGE_64
Followup: memory_corruption
---------Was hat das zu bedeuten ?
Wie kann ich das Problem fixen ?
Memtest habe ich schon 2 mal durch laufen lassen mit 0 errors.
bei 2.04 Volt kein Problem.
memory_corruption ist es immer noch aber eine andere "Meldung" wenn man das so nennen kann (rot,fett markiert).
