thermalfake
Ostatni Mohikanin
Liczba postów: 13.580
|
RE: Resety/BlueScreeny/Paski/Zawiasy Prośba o odczytanie minidump!
Najprawdopodobniej problemy z pamięcią RAM.
Zrób długi memtest, pozamieniaj pamięci, zostaw jeden komplet, ustaw napięcia i timingi. Sam musisz pokombinować.
Kod:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C: \Users\user\Desktop\bsody\DMP\091111-16645-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: C: \Symbols;symsrv*symsrv.dll*c: \symb*http: //msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.x86fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0x8300d000 PsLoadedModuleList = 0x831564f0
Debug session time: Sun Sep 11 14: 43: 42.087 2011 (UTC + 2: 00)
System Uptime: 0 days 0: 00: 33.274
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
....
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: fcb74000, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: 830468dc, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000002, (reserved)
Debugging Details:
------------------
Unable to load image \?\C: \Windows\system32\drivers\aswMonFlt.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswMonFlt.sys
*** ERROR: Module load completed but symbols could not be loaded for aswMonFlt.sys
WRITE_ADDRESS: GetPointerFromAddress: unable to read from 83176848
Unable to read MiSystemVaType memory at 83155e40
fcb74000
FAULTING_IP:
nt!memcpy+11c
830468dc 89448ff0 mov dword ptr [edi+ecx*4-10h],eax
MM_INTERNAL_CODE: 2
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: MMLoadDrv.exe
CURRENT_IRQL: 0
TRAP_FRAME: a3b05028 -- (.trap 0xffffffffa3b05028)
ErrCode = 00000002
eax=00000020 ebx=00000000 ecx=00000004 edx=00000000 esi=88d5b000 edi=fcb74000
eip=830468dc esp=a3b0509c ebp=a3b050a4 iopl=0 nv up ei ng nz ac pe cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010297
nt!memcpy+0x11c:
830468dc 89448ff0 mov dword ptr [edi+ecx*4-10h],eax ds: 0023: fcb74000=?
Resetting default scope
LAST_CONTROL_TRANSFER: from 8304e3e8 to 8309b3db
STACK_TEXT:
a3b05010 8304e3e8 00000001 fcb74000 00000000 nt!MmAccessFault+0x106
a3b05010 830468dc 00000001 fcb74000 00000000 nt!KiTrap0E+0xdc
a3b050a4 8c24684c fcb74000 88d5b000 00000010 nt!memcpy+0x11c
a3b05140 8c23768d a3b05220 88d0a008 a322d880 Ntfs!NtfsNonCachedNonAlignedIo+0x30a
a3b05210 8c238cf7 a3b05220 88d0a008 00c8070a Ntfs!NtfsCommonRead+0x10b5
a3b0534c 8304458e 86baa020 88d0a008 88d0a008 Ntfs!NtfsFsdRead+0x279
a3b05364 8c0e220c 86ba2b50 88d0a008 00000000 nt!IofCallDriver+0x63
a3b05388 8c0e23cb a3b053a8 86ba2b50 00000000 fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x2aa
a3b053c0 8304458e 86ba2b50 88d0a008 88d0a008 fltmgr!FltpDispatch+0xc5
a3b053d8 830d19de 8897f841 8897f7c8 88cdc322 nt!IofCallDriver+0x63
a3b053f4 8328dbeb 88cdc320 88d27370 8897f800 nt!IoPageRead+0x1f5
a3b05428 8328defd 88c55400 00000001 a4140000 nt!MiPfExecuteReadList+0x10c
a3b05454 830c26b5 00000000 00000000 00001000 nt!MmPrefetchForCacheManager+0xa4
a3b05494 83275bfb 88cdc320 00000001 a3b0550c nt!CcFetchDataForRead+0x94
a3b054d0 8327112f 88cdc320 00000000 00000000 nt!CcMapAndCopyFromCache+0x70
a3b05510 8c23edf7 88cdc320 a3b05554 00000400 nt!CcCopyRead+0x107
a3b0553c 8c237779 8814c898 88cdc320 88974cf8 Ntfs!NtfsCachedRead+0x13e
a3b05618 8c238cf7 8814c898 88974cf8 2f966d86 Ntfs!NtfsCommonRead+0x11a1
a3b05688 8304458e 86baa020 88974cf8 88974cf8 Ntfs!NtfsFsdRead+0x279
a3b056a0 8c0e220c 00000000 88d1be40 00000000 nt!IofCallDriver+0x63
a3b056c4 8c0e30bf a3b056e4 86ba2b50 00000000 fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x2aa
a3b056fc 8c0e34e7 881887c0 88cf0c00 00000400 fltmgr!FltPerformSynchronousIo+0xb9
a3b0576c 82406eb5 881887c0 88cdc320 a3b057a8 fltmgr!FltReadFile+0x2ed
WARNING: Stack unwind information not available. Following frames may be wrong.
a3b05814 8240799a 88188df0 881887c0 86ba07c0 aswMonFlt+0x2eb5
a3b05888 82436f5d a3b0598c 88d06840 a3b05928 aswMonFlt+0x399a
a3b05968 8c0de324 88d06840 a3b0598c 00000000 aswMonFlt+0x32f5d
a3b059d0 8c0e1512 00d067e0 88d067e0 1000000c fltmgr!FltpPerformPostCallbacks+0x24a
a3b059e4 8c0e1b46 88d067e0 88d0bbb8 a3b05a24 fltmgr!FltpProcessIoCompletion+0x10
a3b059f4 8c0e229c 86ba2b50 88d0bbb8 88d067e0 fltmgr!FltpPassThroughCompletion+0x98
a3b05a24 8c0f58c9 a3b05a44 00000000 00000000 fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x33a
a3b05a70 8304458e 86ba2b50 86ba07c0 88cdc37c fltmgr!FltpCreate+0x2db
a3b05a88 8325334f 9346eae0 a3b05c30 00000000 nt!IofCallDriver+0x63
a3b05b60 83232b56 869fb600 85b88040 88a11c68 nt!IopParseDevice+0xed7
a3b05bdc 83242f68 00000000 a3b05c30 00000040 nt!ObpLookupObjectName+0x4fa
a3b05c38 83239a46 0039c904 85b88040 9346ed01 nt!ObOpenObjectByName+0x165
a3b05cb4 8325d2be 0039c960 80100080 0039c904 nt!IopCreateFile+0x673
a3b05d00 8304b1fa 0039c960 80100080 0039c904 nt!NtCreateFile+0x34
a3b05d00 76e070b4 0039c960 80100080 0039c904 nt!KiFastCallEntry+0x12a
0039c968 00000000 00000000 00000000 00000000 0x76e070b4
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiTrap0E+dc
8304e3e8 85c0 test eax,eax
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!KiTrap0E+dc
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4e02a389
FAILURE_BUCKET_ID: 0x50_nt!KiTrap0E+dc
BUCKET_ID: 0x50_nt!KiTrap0E+dc
Followup: MachineOwner
---------
Kod:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C: \Users\user\Desktop\bsody\DMP\091111-16348-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: C: \Symbols;symsrv*symsrv.dll*c: \symb*http: //msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.x86fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0x8304c000 PsLoadedModuleList = 0x831954f0
Debug session time: Sun Sep 11 15: 57: 38.864 2011 (UTC + 2: 00)
System Uptime: 0 days 0: 04: 12.994
Loading Kernel Symbols
...............................................................
................................................................
........................................
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 8324ac3e, a60e0a94, 0}
Probably caused by : hardware ( nt!AlpcpReserveDestroyProcedure+88 )
Followup: MachineOwner
---------
5: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 8324ac3e, The address that the exception occurred at
Arg3: a60e0a94, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod 0x%08lx odwo
FAULTING_IP:
nt!AlpcpReserveDestroyProcedure+88
8324ac3e d88bc2f00fb1 fmul dword ptr [ebx-4EF00F3Eh]
TRAP_FRAME: a60e0a94 -- (.trap 0xffffffffa60e0a94)
ErrCode = 00000000
eax=a9056d18 ebx=a9051478 ecx=00000000 edx=00000001 esi=a9056d20 edi=00010000
eip=8324ac3e esp=a60e0b08 ebp=a60e0b14 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nt!AlpcpReserveDestroyProcedure+0x88:
8324ac3e d88bc2f00fb1 fmul dword ptr [ebx-4EF00F3Eh] ds: 0023: 5a15053a=?
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 0
MISALIGNED_IP:
nt!AlpcpReserveDestroyProcedure+88
8324ac3e d88bc2f00fb1 fmul dword ptr [ebx-4EF00F3Eh]
LAST_CONTROL_TRANSFER: from 832c2697 to 8324ac3e
STACK_TEXT:
a60e0b14 832c2697 a9051478 a9051478 890bd59c nt!AlpcpReserveDestroyProcedure+0x88
a60e0b24 832c5c92 890bd594 890bd4e8 890bd594 nt!AlpcpDestroyBlob+0x1c
a60e0b40 832c54fe 85b848c0 890bd4e8 00000001 nt!AlpcpFlushResourcesPort+0xea
a60e0b50 832abf76 890bd4d0 88fd6d48 a60e0bac nt!AlpcpDoPortCleanup+0x8a
a60e0b60 8326ff47 890ba370 890bd4e8 00000001 nt!AlpcpClosePort+0x3b
a60e0bac 83291394 890ba370 a9060080 88fd6d48 nt!ObpDecrementHandleCount+0x139
a60e0bf0 832bfc51 a905ffc0 a9060080 890ba370 nt!ObpCloseHandleTableEntry+0x203
a60e0c20 832a802c a905ffc0 a60e0c34 a905f760 nt!ExSweepHandleTable+0x5f
a60e0c40 832b570e 96f30475 88fd6d48 c0000005 nt!ObKillProcess+0x54
a60e0cb4 832c90f9 c0000005 88cb5048 00000001 nt!PspExitThread+0x5db
a60e0ccc 830fd880 88cb5048 a60e0cf8 a60e0d04 nt!PsExitSpecialApc+0x22
a60e0d1c 8308a2b4 00000001 00000000 a60e0d34 nt!KiDeliverApc+0x28b
a60e0d1c 773070b4 00000001 00000000 a60e0d34 nt!KiServiceExit+0x64
WARNING: Frame IP not in any known module. Following frames may be wrong.
0053ff4c 00000000 00000000 00000000 00000000 0x773070b4
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!AlpcpReserveDestroyProcedure+88
8324ac3e d88bc2f00fb1 fmul dword ptr [ebx-4EF00F3Eh]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!AlpcpReserveDestroyProcedure+88
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: hardware
FAILURE_BUCKET_ID: IP_MISALIGNED
BUCKET_ID: IP_MISALIGNED
Followup: MachineOwner
---------
Kod:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C: \Users\user\Desktop\bsody\DMP\090611-15069-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: C: \Symbols;symsrv*symsrv.dll*c: \symb*http: //msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.x86fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0x82c39000 PsLoadedModuleList = 0x82d824f0
Debug session time: Tue Sep 6 13: 00: 08.935 2011 (UTC + 2: 00)
System Uptime: 0 days 0: 02: 02.761
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {0, 2, 0, 82cca9e0}
Probably caused by : memory_corruption ( nt!MiDispatchFault+289 )
Followup: MachineOwner
---------
5: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 82cca9e0, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from 82da2848
Unable to read MiSystemVaType memory at 82d81e40
00000000
CURRENT_IRQL: 2
FAULTING_IP:
nt!MiDispatchFault+289
82cca9e0 8b0f mov ecx,dword ptr [edi]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: explorer.exe
TRAP_FRAME: a5cc3bbc -- (.trap 0xffffffffa5cc3bbc)
ErrCode = 00000000
eax=84b8b340 ebx=84b8b340 ecx=00000000 edx=00000001 esi=84b8b340 edi=00000000
eip=82cca9e0 esp=a5cc3c30 ebp=a5cc3c90 iopl=0 nv up ei ng nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010282
nt!MiDispatchFault+0x289:
82cca9e0 8b0f mov ecx,dword ptr [edi] ds: 0023: 00000000=?
Resetting default scope
LAST_CONTROL_TRANSFER: from 82cca9e0 to 82c7a5db
STACK_TEXT:
a5cc3bbc 82cca9e0 badb0d00 00000001 00000000 nt!KiTrap0E+0x2cf
a5cc3c90 82cc98ad 09000000 00000000 87e6f588 nt!MiDispatchFault+0x289
a5cc3d1c 82c7a3e8 00000000 09000000 00000001 nt!MmAccessFault+0x25cc
a5cc3d1c 777ef5e7 00000000 09000000 00000001 nt!KiTrap0E+0xdc
WARNING: Frame IP not in any known module. Following frames may be wrong.
028cdcec 00000000 00000000 00000000 00000000 0x777ef5e7
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiDispatchFault+289
82cca9e0 8b0f mov ecx,dword ptr [edi]
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!MiDispatchFault+289
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4e02a389
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: 0xA_nt!MiDispatchFault+289
BUCKET_ID: 0xA_nt!MiDispatchFault+289
Followup: MachineOwner
---------
Kod:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C: \Users\user\Desktop\bsody\DMP\091111-16270-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: C: \Symbols;symsrv*symsrv.dll*c: \symb*http: //msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.x86fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0x83008000 PsLoadedModuleList = 0x831514f0
Debug session time: Sun Sep 11 16: 09: 44.742 2011 (UTC + 2: 00)
System Uptime: 0 days 0: 00: 25.913
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {c0000005, 8c54afab, 8e40bb70, 8e40b750}
Probably caused by : rdyboost.sys ( rdyboost!B_TREE<unsigned long,ST_STORE<SMD_TRAITS>: _ST_REGION_ENTRY,4096,NP_CONTEXT>: BTreeInsertEx+6b )
Followup: MachineOwner
---------
4: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 8c54afab, The address that the exception occurred at
Arg3: 8e40bb70, Exception Record Address
Arg4: 8e40b750, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod 0x%08lx odwo
FAULTING_IP:
rdyboost!B_TREE<unsigned long,ST_STORE<SMD_TRAITS>: _ST_REGION_ENTRY,4096,NP_CONTEXT>: BTreeInsertEx+6b
8c54afab 8a4303 mov al,byte ptr [ebx+3]
EXCEPTION_RECORD: 8e40bb70 -- (.exr 0xffffffff8e40bb70)
ExceptionAddress: 8c54afab (rdyboost!B_TREE<unsigned long,ST_STORE<SMD_TRAITS>: _ST_REGION_ENTRY,4096,NP_CONTEXT>: BTreeInsertEx+0x0000006b)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 00000003
Attempt to read from address 00000003
CONTEXT: 8e40b750 -- (.cxr 0xffffffff8e40b750)
eax=88be0930 ebx=00000000 ecx=869e8094 edx=8313e7c0 esi=88ce0590 edi=869e8084
eip=8c54afab esp=8e40bc38 ebp=8e40bc4c iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
rdyboost!B_TREE<unsigned long,ST_STORE<SMD_TRAITS>: _ST_REGION_ENTRY,4096,NP_CONTEXT>: BTreeInsertEx+0x6b:
8c54afab 8a4303 mov al,byte ptr [ebx+3] ds: 0023: 00000003=?
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod 0x%08lx odwo
EXCEPTION_PARAMETER1: 00000000
EXCEPTION_PARAMETER2: 00000003
READ_ADDRESS: GetPointerFromAddress: unable to read from 83171848
Unable to read MiSystemVaType memory at 83150e40
00000003
FOLLOWUP_IP:
rdyboost!B_TREE<unsigned long,ST_STORE<SMD_TRAITS>: _ST_REGION_ENTRY,4096,NP_CONTEXT>: BTreeInsertEx+6b
8c54afab 8a4303 mov al,byte ptr [ebx+3]
BUGCHECK_STR: 0x7E
DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE
LAST_CONTROL_TRANSFER: from 8c54b98a to 8c54afab
STACK_TEXT:
8e40bc4c 8c54b98a 869e8078 869e8084 8e40bc84 rdyboost!B_TREE<unsigned long,ST_STORE<SMD_TRAITS>: _ST_REGION_ENTRY,4096,NP_CONTEXT>: BTreeInsertEx+0x6b
8e40bc64 8c553f6b 869e8078 8e40bc84 869e8084 rdyboost!B_TREE<unsigned long,ST_STORE<SMD_TRAITS>: _ST_REGION_ENTRY,4096,NP_CONTEXT>: BTreeInsert+0x34
8e40bc94 8c5543e6 869e8050 8e40bcf8 8e40bcb4 rdyboost!ST_STORE<SMD_TRAITS>: StDmpSinglePageInsert+0x89
8e40bce0 8c5547cb 931e0000 8e40bcf8 8825a8d8 rdyboost!ST_STORE<SMD_TRAITS>: StDmpSinglePageAdd+0x186
8e40bd10 8c554cfc 869e8050 8825a8d8 8825a8d8 rdyboost!ST_STORE<SMD_TRAITS>: StDmPageAdd+0x47
8e40bd28 8c554f14 869e8008 8825a8d8 00000000 rdyboost!ST_STORE<SMD_TRAITS>: StWorkItemProcess+0x2c
8e40bd50 83210fda 00000000 beb34871 00000000 rdyboost!SMKM_STORE<SMD_TRAITS>: SmStWorker+0xfe
8e40bd90 830b91d9 8c554e16 869e8008 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: rdyboost!B_TREE<unsigned long,ST_STORE<SMD_TRAITS>: _ST_REGION_ENTRY,4096,NP_CONTEXT>: BTreeInsertEx+6b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: rdyboost
IMAGE_NAME: rdyboost.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce78e17
STACK_COMMAND: .cxr 0xffffffff8e40b750 ; kb
FAILURE_BUCKET_ID: 0x7E_rdyboost!B_TREE_unsigned_long,ST_STORE_SMD_TRAITS_: _ST_REGION_ENTRY,4096,NP_CONTEXT_: BTreeInsertEx+6b
BUCKET_ID: 0x7E_rdyboost!B_TREE_unsigned_long,ST_STORE_SMD_TRAITS_: _ST_REGION_ENTRY,4096,NP_CONTEXT_: BTreeInsertEx+6b
Followup: MachineOwner
---------
Kod:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C: \Users\user\Desktop\bsody\DMP\090811-17050-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: C: \Symbols;symsrv*symsrv.dll*c: \symb*http: //msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (5 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.x86fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0x83052000 PsLoadedModuleList = 0x8319b4f0
Debug session time: Thu Sep 8 15: 02: 41.725 2011 (UTC + 2: 00)
System Uptime: 0 days 2: 21: 13.896
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 8c0edd97, 8d5a67f0, 0}
Unable to load image \SystemRoot\System32\Drivers\aswFsBlk.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswFsBlk.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswFsBlk.SYS
Probably caused by : memory_corruption
Followup: memory_corruption
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 8c0edd97, The address that the exception occurred at
Arg3: 8d5a67f0, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod 0x%08lx odwo
FAULTING_IP:
fltmgr!FltpGetNormalizedFileNameWorker+51
8c0edd97 8b5104 mov edx,dword ptr [ecx+4]
TRAP_FRAME: 8d5a67f0 -- (.trap 0xffffffff8d5a67f0)
ErrCode = 00000000
eax=88eca370 ebx=0000003a ecx=0000003a edx=0000003a esi=8847db80 edi=00000000
eip=8c0edd97 esp=8d5a6864 ebp=8d5a6874 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
fltmgr!FltpGetNormalizedFileNameWorker+0x51:
8c0edd97 8b5104 mov edx,dword ptr [ecx+4] ds: 0023: 0000003e=?
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: CODE_CORRUPTION
BUGCHECK_STR: 0x8E
PROCESS_NAME: Engine.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 8c0ee505 to 8c0edd97
STACK_TEXT:
8d5a6874 8c0ee505 8847db80 893eee38 88eca384 fltmgr!FltpGetNormalizedFileNameWorker+0x51
8d5a688c 8c0eb765 8847db80 893eee38 8847db80 fltmgr!FltpGetNormalizedFileName+0x19
8d5a68a4 8c0d5773 8847db80 00000000 8847db80 fltmgr!FltpCreateFileNameInformation+0x81
8d5a68c4 8c0d58c7 86ba49d8 00000000 00000000 fltmgr!HandleStreamListNotSupported+0x125
8d5a68f4 8c0d5fa3 c00000bb 8d5a6944 8d5a6988 fltmgr!FltpGetFileNameInformation+0xc7
8d5a691c 94e6b600 003eee40 00000101 8d5a6940 fltmgr!FltGetFileNameInformation+0x12b
WARNING: Stack unwind information not available. Following frames may be wrong.
8d5a6964 94e6b350 8d5a69b4 893eee40 8d5a6988 aswFsBlk+0x1600
8d5a6994 8c0cfaeb 00100001 8d5a69b4 8d5a69e0 aswFsBlk+0x1350
8d5a6a00 8c0d29f0 8d5a6a44 89179aa8 00000000 fltmgr!FltpPerformPreCallbacks+0x34d
8d5a6a18 8c0e61fe 8d5a6a44 8c0e9f3c 00000000 fltmgr!FltpPassThroughInternal+0x40
8d5a6a2c 8c0e68b7 8d5a6a44 89179aa8 894c8cf8 fltmgr!FltpCreateInternal+0x24
8d5a6a70 8308958e 86ba4b60 86ba4620 894c8d54 fltmgr!FltpCreate+0x2c9
8d5a6a88 8329834f bc52cd4f 8d5a6c30 00000000 nt!IofCallDriver+0x63
8d5a6b60 83277b56 869e6558 85b896e0 89700718 nt!IopParseDevice+0xed7
8d5a6bdc 83287f68 00000000 8d5a6c30 00000040 nt!ObpLookupObjectName+0x4fa
8d5a6c38 8327ea46 21a2e5b8 85b896e0 00000001 nt!ObOpenObjectByName+0x165
8d5a6cb4 832a22be 21a2e5f0 00100001 21a2e5b8 nt!IopCreateFile+0x673
8d5a6d00 830901fa 21a2e5f0 00100001 21a2e5b8 nt!NtCreateFile+0x34
8d5a6d00 77bc70b4 21a2e5f0 00100001 21a2e5b8 nt!KiFastCallEntry+0x12a
21a2e5f4 00000000 00000000 00000000 00000000 0x77bc70b4
STACK_COMMAND: kb
CHKIMG_EXTENSION: !chkimg -lo 50 -d !fltmgr
8c0edd98 - fltmgr!FltpGetNormalizedFileNameWorker+52
[ 50: 51 ]
1 error : !fltmgr (8c0edd98)
MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: ONE_BIT
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT
BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT
Followup: memory_corruption
---------
Kod:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C: \Users\user\Desktop\bsody\DMP\090711-15256-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: C: \Symbols;symsrv*symsrv.dll*c: \symb*http: //msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.x86fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0x82c48000 PsLoadedModuleList = 0x82d914f0
Debug session time: Wed Sep 7 13: 37: 29.368 2011 (UTC + 2: 00)
System Uptime: 0 days 0: 03: 54.554
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
.....
Unable to load image \SystemRoot\system32\DRIVERS\atipmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atipmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atipmdag.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {c000001d, 924f60cb, 8de6bbbc, 8de6b7a0}
Probably caused by : atipmdag.sys ( atipmdag+2e80cb )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c000001d, The exception code that was not handled
Arg2: 924f60cb, The address that the exception occurred at
Arg3: 8de6bbbc, Exception Record Address
Arg4: 8de6b7a0, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {WYJ
FAULTING_IP:
atipmdag+2e80cb
924f60cb 0f ?
EXCEPTION_RECORD: 8de6bbbc -- (.exr 0xffffffff8de6bbbc)
ExceptionAddress: 924f60cb (atipmdag+0x002e80cb)
ExceptionCode: c000001d (Illegal instruction)
ExceptionFlags: 00000000
NumberParameters: 0
CONTEXT: 8de6b7a0 -- (.cxr 0xffffffff8de6b7a0)
eax=8f48080e ebx=924f60cf ecx=00000000 edx=000000af esi=8f48080e edi=000000af
eip=924f60cb esp=8de6bc84 ebp=8de6bc9c iopl=0 nv up di pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010006
atipmdag+0x2e80cb:
924f60cb 0f ?
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x7E
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc000001d - {WYJ
LAST_CONTROL_TRANSFER: from 9237347c to 924f60cb
FAILED_INSTRUCTION_ADDRESS:
atipmdag+2e80cb
924f60cb 0f ?
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
8de6bc9c 9237347c 00000003 8de6bd1c 00000000 atipmdag+0x2e80cb
8de6bd50 82e50fda 926c8614 bcac1470 00000000 atipmdag+0x16547c
8de6bd90 82cf91d9 923732b0 926c8614 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
FOLLOWUP_IP:
atipmdag+2e80cb
924f60cb 0f ?
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: atipmdag+2e80cb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: atipmdag
IMAGE_NAME: atipmdag.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4b68f954
STACK_COMMAND: .cxr 0xffffffff8de6b7a0 ; kb
FAILURE_BUCKET_ID: 0x7E_BAD_IP_atipmdag+2e80cb
BUCKET_ID: 0x7E_BAD_IP_atipmdag+2e80cb
Followup: MachineOwner
---------
Kod:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C: \Users\user\Desktop\bsody\DMP\083011-15568-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: symsrv*symsrv.dll*c: \symb*http: //msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.x86fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0x82c42000 PsLoadedModuleList = 0x82d8b4f0
Debug session time: Tue Aug 30 16: 43: 01.809 2011 (UTC + 2: 00)
System Uptime: 0 days 2: 26: 13.995
Loading Kernel Symbols
...............................................................
................................................................
......................................
Loading User Symbols
Loading unloaded module list
......
4: 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: 0000009a,
Arg2: 000cfb25
Arg3: 00000006
Arg4: 00000002
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for asusgsb.sys
*** ERROR: Module load completed but symbols could not be loaded for asusgsb.sys
BUGCHECK_STR: 0x4E_9a
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: Engine.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 82d2c4d8 to 82d20eb4
STACK_TEXT:
aa5cba40 82d2c4d8 0000004e 0000009a 000cfb25 nt!KeBugCheckEx+0x1e
aa5cba58 82d6112a 00000000 00300000 00000000 nt!MiBadRefCount+0x26
aa5cbb38 82d62ef1 85b25000 00300000 00000004 nt!MiFreePoolPages+0x124
aa5cbba0 9414bb84 85b25000 544f4853 aac8ad97 nt!ExFreePoolWithTag+0x436
WARNING: Stack unwind information not available. Following frames may be wrong.
aa5cbbe8 9414bd39 86c64988 859f5890 86c64988 asusgsb+0xb84
aa5cbbfc 82c7958e 86c64988 859f5890 859f5890 asusgsb+0xd39
aa5cbc14 82e6ca31 88a31cd0 859f5890 859f5924 nt!IofCallDriver+0x63
aa5cbc34 82e6fc03 86c64988 88a31cd0 00000000 nt!IopSynchronousServiceTail+0x1f8
aa5cbcd0 82eb649c 86c64988 859f5890 00000000 nt!IopXxxControlFile+0x6aa
aa5cbd04 82c801fa 000010d8 00000000 00000000 nt!NtDeviceIoControlFile+0x2a
aa5cbd04 778970b4 000010d8 00000000 00000000 nt!KiFastCallEntry+0x12a
00113534 00000000 00000000 00000000 00000000 0x778970b4
STACK_COMMAND: kb
FOLLOWUP_IP:
asusgsb+b84
9414bb84 ? ?
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: asusgsb+b84
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: asusgsb
IMAGE_NAME: asusgsb.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 46fbaca7
FAILURE_BUCKET_ID: 0x4E_9a_asusgsb+b84
BUCKET_ID: 0x4E_9a_asusgsb+b84
Followup: MachineOwner
---------
![[Obrazek: 2089620800_1406976151.png]](http://obrazki.elektroda.pl/2089620800_1406976151.png)
W zamian za pomoc oczekuję poprawnej pisowni. Stop niechlujstwu.
Jak mądrze zadawać pytania? - przejrzyj poradnik na forum.
Nie udzielam porad via PW.
|
Post: #1
z Win7 Ultimate x86 jak w temacie i zaskakuje dopiero po kilku reserach ale i tak nie na tyle długo żebym mógł sprawdzić DMP . Nie wiem co jest grane? 
Czy to problem sprzętowy czy programowy. Dlatego prosze o szybką pomoc w odczytaniu minidump.
