dylanm 2 Posted May 3, 2019 Share Posted May 3, 2019 I just had a 32-bit Windows 7 computer BSOD on me. Checking the dump gave me epfwwfp.sys as the culprit and IRQL_NOT_LESS_OR_EQUAL as the issue. Can anyone tell me whether this is the same issue as outlined in https://support.eset.com/kb2567/ which can be fixed by applying this https://support.microsoft.com/en-us/help/2664888/ hotfix? Here's the seemingly relevant bugcheck info: 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: 0072006f, 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: 83a18fa9, address which referenced memory FAULTING_IP: hal!KeAcquireInStackQueuedSpinLockRaiseToSynch+29 83a18fa9 8902 mov dword ptr [edx],eax TRAP_FRAME: 83b80950 -- (.trap 0xffffffff83b80950) ErrCode = 00000003 eax=83b80a04 ebx=86c0c3a8 ecx=8a6b8574 edx=0072006f esi=8a6b84e8 edi=8a6b85a8 eip=83a18fa9 esp=83b809c4 ebp=83b80a30 iopl=0 nv up ei ng nz na po nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010282 hal!KeAcquireInStackQueuedSpinLockRaiseToSynch+0x29: 83a18fa9 8902 mov dword ptr [edx],eax ds:0023:0072006f=???????? Resetting default scope LAST_CONTROL_TRANSFER: from 83a18fa9 to 83a92623 STACK_TEXT: Page a8ba4 not present in the dump file. Type ".hh dbgerr004" for details 83b80950 83a18fa9 badb0d00 0072006f 00000000 nt!KiTrap0E+0x353 83b809c0 9e40417b 83b8acc0 83b80aac 00000000 hal!KeAcquireInStackQueuedSpinLockRaiseToSynch+0x29 WARNING: Stack unwind information not available. Following frames may be wrong. 83b80a30 9e403cdb 83b80a7c 83ab7a7a 86c0c3f0 epfwwfp+0x417b 83b80a38 83ab7a7a 86c0c3f0 86c0c3a8 c9620c18 epfwwfp+0x3cdb 83b80a7c 83ab7a1d 80b96120 83b80ba8 00000001 nt!KiProcessTimerDpcTable+0x51 83b80b68 83ab78da 80b96120 83b80ba8 00000000 nt!KiProcessExpiredTimerList+0x101 83b80bdc 83ab58aa 0093dd47 877b2030 83b8acc0 nt!KiTimerExpiration+0x25c 83b80c20 83ab56c2 00000000 0000000e 00000000 nt!KiRetireDpcList+0xcb 83b80c24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x46 THREAD_SHA1_HASH_MOD_FUNC: 6c7bfcddebf5ec77ecef028d4c0bc84b2c5c706a THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 0861c39d7c4013f1434a247142212272a8e0c777 THREAD_SHA1_HASH_MOD: 499ccb1114d9c774835e65a03d3aa1e4c4282652 FOLLOWUP_IP: epfwwfp+417b 9e40417b 8b86b8000000 mov eax,dword ptr [esi+0B8h] Link to comment Share on other sites More sharing options...
Administrators Marcos 5,228 Posted May 4, 2019 Administrators Share Posted May 4, 2019 Probably that's it. Make sure the appropriate Windows update is installed. Link to comment Share on other sites More sharing options...
Recommended Posts