Well, after completing the final parts of post #2, I found the quick scan didn't identify any issues but the full scan certainly did. I removed the malware and have been working on the computer for the last week or so, no BSODs as of late.
I didn't write down the malware (three issues, one trojan, I recall) but things seem to be back to normal. Is there any way to retrieve a report from the Windows Defender tool?
Dangit.
Can you update the BIOS to Version 1303 from ASUSTeK Computer Inc. -Support- Drivers and Download M4N78 Pro ?
_________________________________________________________________________________________________
Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {2b20, 2, 1, fffff80002ed1c42} Probably caused by : afd.sys ( afd!AfdPoll64+ba4 ) Followup: MachineOwner --------- 2: 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: 0000000000002b20, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000001, 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: fffff80002ed1c42, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030fe100 GetUlongFromAddress: unable to read from fffff800030fe1c0 0000000000002b20 Nonpaged pool CURRENT_IRQL: 2 FAULTING_IP: nt!KiInsertTimerTable+82 fffff800`02ed1c42 f0480fbaac3e0022000000 lock bts qword ptr [rsi+rdi+2200h],0 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: Samsung Link.e ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre TRAP_FRAME: fffff8800ca30630 -- (.trap 0xfffff8800ca30630) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=00000000000006ad rbx=0000000000000000 rcx=00000000000006ad rdx=0000000000000100 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002ed1c42 rsp=fffff8800ca307c0 rbp=fffff88002f63180 r8=fffffa8006dfdd80 r9=0000000000000039 r10=fffff88002f63180 r11=fffffa8008085000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz ac pe nc nt!KiInsertTimerTable+0x82: fffff800`02ed1c42 f0480fbaac3e0022000000 lock bts qword ptr [rsi+rdi+2200h],0 ds:00000000`00002200=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002ec6169 to fffff80002ec6bc0 STACK_TEXT: fffff880`0ca304e8 fffff800`02ec6169 : 00000000`0000000a 00000000`00002b20 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx fffff880`0ca304f0 fffff800`02ec4de0 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`07adcf80 : nt!KiBugCheckDispatch+0x69 fffff880`0ca30630 fffff800`02ed1c42 : fffffa80`03981bd0 d0646641`00000000 00000000`00000000 00000000`a0000003 : nt!KiPageFault+0x260 fffff880`0ca307c0 fffff800`02ed19c0 : ffffffff`ffc2f700 fffff880`02f63180 fffffa80`07adcf80 00000000`000006ad : nt!KiInsertTimerTable+0x82 fffff880`0ca30820 fffff800`02ed18c4 : fffffa80`07adcf20 ffffffff`ffc2f700 00000000`00000000 00000000`00000000 : nt!KiSetTimerEx+0xf0 fffff880`0ca308b0 fffff880`03ed2c33 : 00000000`00000000 fffffa80`06dfdc30 00000000`50646641 fffffa80`000001a4 : nt!KeSetTimer+0x14 fffff880`0ca308f0 fffff880`03ed2e59 : fffffa80`03981b10 00000000`00000000 fffffa80`07adcf00 00000000`00000000 : afd!AfdPoll64+0xba4 fffff880`0ca309e0 fffff800`031e33a7 : fffffa80`0558fc80 fffff880`0ca30ca0 fffffa80`03981d00 fffffa80`03981b10 : afd!AfdPoll+0x29 fffff880`0ca30a10 fffff800`031e3c06 : fffff880`02f63180 00000000`00000a68 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x607 fffff880`0ca30b40 fffff800`02ec5e53 : 00000000`00000000 fffff800`031aee50 fffff880`0ca30ca0 00000000`00000000 : nt!NtDeviceIoControlFile+0x56 fffff880`0ca30bb0 00000000`76d7132a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`0d0321e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76d7132a STACK_COMMAND: kb FOLLOWUP_IP: afd!AfdPoll64+ba4 fffff880`03ed2c33 488b86b8000000 mov rax,qword ptr [rsi+0B8h] SYMBOL_STACK_INDEX: 6 SYMBOL_NAME: afd!AfdPoll64+ba4 FOLLOWUP_NAME: MachineOwner MODULE_NAME: afd IMAGE_NAME: afd.sys DEBUG_FLR_IMAGE_TIMESTAMP: 52462c33 IMAGE_VERSION: 6.1.7601.18272 FAILURE_BUCKET_ID: X64_0xA_afd!AfdPoll64+ba4 BUCKET_ID: X64_0xA_afd!AfdPoll64+ba4 ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:x64_0xa_afd!afdpoll64+ba4 FAILURE_ID_HASH: {6eae9fb4-f189-fb75-a99f-07705f4e231f} Followup: MachineOwner ---------
Done, will let y'all know if BSODs persist.
Should I consider replacing my HD? I am currently under warranty with WD until 2017.
I'm going to mark this as solved, for the time being. After the BIOS update, I have not had any further BSODs.
Thanks for your help, Arc and peebee!
Quote