Usuario
SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION muy frecuente, junto a otros BSOD.
Pregunta
-
SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION ha sido un pantallazo azul muy frecuente ultimamente en mi computadora. Necesito ayuda de alguien que entienda lo que quiere decir el análisis del dmp realizado en OSR Online
Aunque tambíen ayer me apareció un pantallazo azul (IRQL_NOT_LESS_OR_EQUAL) mientras jugaba al Counter Strike GO, el cual nunca antes había pasado ANTES de actualizar los drivers de atapi.sys que causaban otro pantallazo azul llamado ATTEMPTED_WRITE_READ_ONLY_MEMORY.
Análisis de SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1) Special pool has detected memory corruption. Typically the current thread's stack backtrace will reveal the guilty party. Arguments: Arg1: a8d6cf90, address trying to free Arg2: a8d6cffc, address where bits are corrupted Arg3: 00c74070, (reserved) Arg4: 00000024, caller is freeing an address where bytes after the end of the allocation have been overwritten Debugging Details: ------------------ TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2 BUGCHECK_STR: 0xC1_24 SPECIAL_POOL_CORRUPTION_TYPE: 24 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP PROCESS_NAME: System CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 830f0c91 to 830e2428 STACK_TEXT: 80da19d4 830f0c91 000000c1 a8d6cf90 a8d6cffc nt!KeBugCheckEx+0x1e 80da1abc 83128b73 a8d6cf90 00000000 a8d6cf90 nt!MmFreeSpecialPool+0x52 80da1b24 83336f90 a8d6cf90 00000000 a0dbb480 nt!ExFreePoolWithTag+0xd7 80da1b38 98fac38e a8d6cf90 00000000 a8d10e60 nt!VerifierExFreePoolWithTag+0x30 WARNING: Stack unwind information not available. Following frames may be wrong. 80da1b74 866bfb82 80da1c04 80da1b9c 984c8f8c diginet+0x138e 80da1c0c 866bf642 8e1360e0 85be6430 8334030b ndis!ndisInitializeBinding+0x255 80da1c9c 866c2c5e 8e1360e0 a8d10e60 00000000 ndis!ndisCheckAdapterBindings+0x155 80da1d34 8665a08e 00d10e60 00000000 89a4e820 ndis!ndisCheckProtocolBindings+0x128 80da1d50 831f8400 00000000 ab648a69 00000000 ndis!ndisWorkerThread+0xa4 80da1d90 83099979 86659fea 00000000 00000000 nt!PspSystemThreadStartup+0x9e 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19 STACK_COMMAND: kb FOLLOWUP_IP: diginet+138e 98fac38e ?? ??? SYMBOL_STACK_INDEX: 4 SYMBOL_NAME: diginet+138e FOLLOWUP_NAME: MachineOwner MODULE_NAME: diginet IMAGE_NAME: diginet.sys DEBUG_FLR_IMAGE_TIMESTAMP: 535deaed FAILURE_BUCKET_ID: 0xC1_24_VRF_diginet+138e BUCKET_ID: 0xC1_24_VRF_diginet+138e Followup: MachineOwner ---------
Análisis de IRQL_NOT_LESS_OR_EQUAL
******************************************************************************* * * * 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: 00000001, memory referenced Arg2: 00000002, IRQL Arg3: 00000001, 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: 830a77d2, address which referenced memory Debugging Details: ------------------ TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2 WORKER_ROUTINE: +0 00000001 ?? ??? WORK_ITEM: 830a77d2 CURRENT_IRQL: 2 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP BUGCHECK_STR: 0xA PROCESS_NAME: csgo.exe TRAP_FRAME: 80d8ada4 -- (.trap 0xffffffff80d8ada4) ErrCode = 00000002 eax=00000001 ebx=83174688 ecx=00ffff08 edx=00000001 esi=9c6dd819 edi=00000000 eip=830a77d2 esp=80d8ae18 ebp=80d8ae50 iopl=0 nv up ei pl nz na po nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00210202 nt!KiTimerWaitTest+0x1c1: 830a77d2 0000 add byte ptr [eax],al ds:0023:00000001=?? Resetting default scope MISALIGNED_IP: nt!KiTimerWaitTest+1c1 830a77d2 0000 add byte ptr [eax],al LAST_CONTROL_TRANSFER: from 830a77d2 to 83088c9b STACK_TEXT: 80d8ada4 830a77d2 badb0d00 00000001 88685d3c nt!KiTrap0E+0x2cf 80d8ae50 830a74e5 83172d20 00000001 83174680 nt!KiTimerWaitTest+0x1c1 80d8af38 830a7418 83172d20 80d8af78 00000000 nt!KiProcessExpiredTimerList+0x8b 80d8afac 830a57ce 000130fa aafbbd34 00000000 nt!KiTimerExpiration+0x25c 80d8aff4 830a4f9c aafbbce4 00000000 00000000 nt!KiRetireDpcList+0xcb 80d8aff8 aafbbce4 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2c WARNING: Frame IP not in any known module. Following frames may be wrong. 830a4f9c 00000000 0000001a 00d6850f bb830000 0xaafbbce4 STACK_COMMAND: kb FOLLOWUP_IP: nt!KiTrap0E+2cf 83088c9b 833d80aa1a8300 cmp dword ptr [nt!KiFreezeFlag (831aaa80)],0 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!KiTrap0E+2cf 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 ---------
Análisis de ATTEMPTED_WRITE_TO_READONLY_MEMORY (Posiblemente arreglado)
******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* ATTEMPTED_WRITE_TO_READONLY_MEMORY (be) An attempt was made to write to readonly memory. The guilty driver is on the stack trace (and is typically the current instruction pointer). When possible, the guilty driver's name (Unicode string) is printed on the bugcheck screen and saved in KiBugCheckDriver. Arguments: Arg1: 857ac7c4, Virtual address for the attempted write. Arg2: 02f4e121, PTE contents. Arg3: aac3b7c4, (reserved) Arg4: 0000000a, (reserved) Debugging Details: ------------------ TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2 DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP BUGCHECK_STR: 0xBE PROCESS_NAME: System CURRENT_IRQL: 9 TRAP_FRAME: aac3b7c4 -- (.trap 0xffffffffaac3b7c4) ErrCode = 00000003 eax=00000102 ebx=00000404 ecx=d07dbf98 edx=87bf80e0 esi=d07dbf98 edi=857ac78c eip=85791e11 esp=aac3b838 ebp=aac3b840 iopl=0 nv up ei pl nz na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206 atapi!AtapiHandleAtaCommand+0xd: 85791e11 897738 mov dword ptr [edi+38h],esi ds:0023:857ac7c4=0008c25d Resetting default scope LAST_CONTROL_TRANSFER: from 8244daa8 to 82473d67 STACK_TEXT: aac3b7ac 8244daa8 00000001 857ac7c4 00000000 nt!MmAccessFault+0xbf aac3b7ac 85791e11 00000001 857ac7c4 00000000 nt!KiTrap0E+0xdc aac3b840 85791e8d 857ac78c d07dbf98 aac3b868 atapi!AtapiHandleAtaCommand+0xd aac3b850 8579c6a5 857ac78c d07dbf98 00000102 atapi!AtapiHwStartIo+0x29 aac3b868 857a1a5d 87bf80e0 d07dbd10 89dc80e8 ataport!CallMiniPortHwStartIo+0x87 aac3b884 82446add d07dbd10 87bf8002 87bf80e0 ataport!IdeStartCrbSynchronized+0x61 aac3b8a8 857a2153 87bf80e0 857a19fc d07dbd10 nt!KeSynchronizeExecution+0x3d aac3b8d4 85730074 d07dbd10 aac3b90c 8281ca2e ataport!IdeStartIoCallBack+0xbb aac3b8e0 8281ca2e 879cde10 00000000 d07dbd6c PCIIDEX!BmReceiveScatterGatherList+0x1e aac3b90c 85730199 d07dbd6c 879cde10 87afbac8 hal!HalBuildScatterGatherList+0x1ba aac3b948 857a1b52 879cdec8 d07dbd10 d07dbd00 PCIIDEX!BmSetup+0x3d aac3b964 857a204d 87bf80e0 d07dbd00 d07dbd10 ataport!IdePortSetupScatterGatherList+0x2a aac3b97c 857a0a1e 87bf80e0 d07dbd10 89dc80e8 ataport!IdeDispatchChannelRequest+0x59 aac3b994 857a0def 87bf80e0 d07dbd10 89fe4464 ataport!IdeStartChannelRequest+0x42 aac3b9b8 857a1fb4 00dc80e8 007dbd10 dbc79500 ataport!IdeStartDeviceRequest+0x15d aac3b9d8 8579e46b 00000103 bbf02f20 aac3ba0c ataport!IdePortPdoDispatch+0x9a aac3b9e8 8273a6c3 89dc8030 bbf02f20 bbf02f20 ataport!IdePortDispatch+0x1d aac3ba0c 8244401e 00000000 ffcd3ff4 89dc8030 nt!IovCallDriver+0x258 aac3ba20 856373da ffcd3ff4 aac3ba40 8563dc20 nt!IofCallDriver+0x1b aac3ba2c 8563dc20 879d7b70 bbf02f20 bbf02fd8 ACPI!ACPIDispatchForwardIrp+0x2a aac3ba40 85637664 879d7b70 bbf02f20 879d7b70 ACPI!ACPIIrpDispatchDeviceControl+0xa4 aac3ba70 8273a6c3 879d7b70 84b97260 89e78ce8 ACPI!ACPIDispatchIrp+0x198 aac3ba94 8244401e 00000000 89fe43b8 879d7b70 nt!IovCallDriver+0x258 aac3baa8 85e745a4 a6cc4e28 89fe43b8 aac3baf8 nt!IofCallDriver+0x1b aac3bab8 85e73fe8 879d7b70 89e75878 89e784a8 CLASSPNP!SubmitTransferPacket+0x103 aac3baf8 85e74303 00000000 00cc4e28 87a1ca18 CLASSPNP!ServiceTransferRequest+0x225 aac3bb20 85e743bf 89e757c0 00000000 a6cc4e28 CLASSPNP!ClassReadWrite+0x172 aac3bb34 8273a6c3 89e757c0 a6cc4e28 89e760d8 CLASSPNP!ClassGlobalDispatch+0x20 aac3bb58 8244401e 00000001 a6cc4f8c 89e757c0 nt!IovCallDriver+0x258 aac3bb6c 856bd117 87a27f90 a6cc4e28 89e76020 nt!IofCallDriver+0x1b aac3bb80 856bd152 89e760d8 a6cc4f70 a6cc4e28 partmgr!PmReadWrite+0x112 aac3bb94 8273a6c3 89e76020 a6cc4e28 4c319000 partmgr!PmGlobalDispatch+0x1d aac3bbb8 8244401e 00000001 89e7acc8 89e76020 nt!IovCallDriver+0x258 aac3bbcc 856ce9ae dbdb9100 a6cc4e28 89e7ac10 nt!IofCallDriver+0x1b aac3bbe8 8273a6c3 89e7ac10 a6cc4e28 a6cc4e28 volmgr!VmReadWrite+0x1a8 aac3bc0c 8244401e 00000001 a6cc4e28 89e7ac10 nt!IovCallDriver+0x258 aac3bc20 85e2e475 89e7cd38 aac3bc48 85e2e548 nt!IofCallDriver+0x1b aac3bc2c 85e2e548 89e7cd38 a6cc4e28 824ba9bc fvevol!FveRequestPassThrough+0x31 aac3bc48 85e2e759 89e7cd38 a6cc4e00 dbc2c4e8 fvevol!FveReadWrite+0x4e aac3bc78 8273a6c3 89e7cc80 a6cc4e28 dbc7fd18 fvevol!FveFilterRundownReadWrite+0x197 aac3bc9c 8244401e 00000001 00000000 89e7cc80 nt!IovCallDriver+0x258 aac3bcb0 85da3996 a6cc4e28 dbc7fd18 89e7d020 nt!IofCallDriver+0x1b aac3bcc4 85da59c9 89e7d0d8 89e7d020 a6cc4e28 volsnap!VolSnapReadFilter+0x12e aac3bcd8 8273a6c3 89e7d020 a6cc4e28 aac3bd28 volsnap!VolSnapRead+0x1b aac3bcfc 8244401e 00000001 a42d882c 89e7d020 nt!IovCallDriver+0x258 aac3bd10 85874829 a42d878c aac3bd34 82472166 nt!IofCallDriver+0x1b aac3bd1c 82472166 a42d882c 00000000 ffffffff Ntfs!NtfsStorageDriverCallout+0x14 aac3bd1c 8247225d a42d882c 00000000 ffffffff nt!KiSwapKernelStackAndExit+0x15a a42d879c 00000000 00000000 00000000 00000000 nt!KiSwitchKernelStackAndCallout+0x31 STACK_COMMAND: kb FOLLOWUP_IP: atapi!AtapiHandleAtaCommand+d 85791e11 897738 mov dword ptr [edi+38h],esi SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: atapi!AtapiHandleAtaCommand+d FOLLOWUP_NAME: MachineOwner MODULE_NAME: atapi IMAGE_NAME: atapi.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bbf13 FAILURE_BUCKET_ID: 0xBE_VRF_atapi!AtapiHandleAtaCommand+d BUCKET_ID: 0xBE_VRF_atapi!AtapiHandleAtaCommand+d Followup: MachineOwner ---------
jueves, 27 de septiembre de 2018 22:05
