Hello all, my computer recently has been acting up so I decided to reformat it and did a fresh install of Windows 7. After using it for couple days, I started getting several BSOD repeatedly, and each time it refers to different hardward. I think. Well here are the mini dumps and related files. If anyone can help me out that would greatly appreciated.
Thank you in advance.
Your old Avast Antivirus is the cause, please remove it and use MSE instead
Upgrade to the newest version of Avast if you don't want to use MSE
Code:aswFsBlk.SYS fffff880`03bb1000 fffff880`03bba000 0x00009000 0x4c86506d 07/09/2010 18:47:09 aswFW.SYS fffff880`04187000 fffff880`041a9000 0x00022000 0x4c86521c 07/09/2010 18:54:20 aswMonFlt.sys fffff880`03b77000 fffff880`03bb1000 0x0003a000 0x4c865084 07/09/2010 18:47:32 aswNdis.sys fffff880`017e5000 fffff880`017ec000 0x00007000 0x4b48f37b 10/01/2010 01:22:03 aswNdis2.sys fffff880`01660000 fffff880`016a1000 0x00041000 0x4c8651f3 07/09/2010 18:53:39 aswRdr.SYS fffff880`04350000 fffff880`0435a000 0x0000a000 0x4c865093 07/09/2010 18:47:47 aswSnx.SYS fffff880`0405b000 fffff880`040d2000 0x00077000 0x4c865210 07/09/2010 18:54:08 aswSP.SYS fffff880`04512000 fffff880`04535000 0x00023000 0x4c865197 07/09/2010 18:52:07 aswTdi.SYS fffff880`041a9000 fffff880`041b9000 0x00010000 0x4c8651ab 07/09/2010 18:52:27Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 50, {fffff88003bec7e9, 8, fffff88003bac7e9, 0} 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 Could not read faulting driver name Probably caused by : aswMonFlt.sys ( aswMonFlt+357e9 ) 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: fffff88003bec7e9, memory referenced. Arg2: 0000000000000008, value 0 = read operation, 1 = write operation. Arg3: fffff88003bac7e9, If non-zero, the instruction address which referenced the bad memory address. Arg4: 0000000000000000, (reserved) Debugging Details: ------------------ Could not read faulting driver name WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cb30e0 fffff88003bec7e9 FAULTING_IP: aswMonFlt+357e9 fffff880`03bac7e9 483bfb cmp rdi,rbx MM_INTERNAL_CODE: 0 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x50 PROCESS_NAME: rundll32.exe CURRENT_IRQL: 0 TRAP_FRAME: fffff88009d1bc20 -- (.trap 0xfffff88009d1bc20) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=00000000c0000225 rbx=0000000000000000 rcx=0000000000000010 rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000 rip=fffff88003bac7e9 rsp=fffff88009d1bdb0 rbp=0000000000000000 r8=fffffa80083b2c60 r9=fffff88009d1bdf8 r10=fffffa8005e80cc8 r11=fffff88009d1bd50 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na pe nc aswMonFlt+0x357e9: fffff880`03bac7e9 483bfb cmp rdi,rbx Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002afc024 to fffff80002a7b700 STACK_TEXT: fffff880`09d1bab8 fffff800`02afc024 : 00000000`00000050 fffff880`03bec7e9 00000000`00000008 fffff880`09d1bc20 : nt!KeBugCheckEx fffff880`09d1bac0 fffff800`02a797ee : 00000000`00000008 00000000`00000000 fffffa80`043dfc00 fffff800`02a7dd26 : nt! ?? ::FNODOBFM::`string'+0x427f7 fffff880`09d1bc20 fffff880`03bac7e9 : fffffa80`05e80cc0 00000000`00000000 fffff880`09d1bf18 fffff880`09d1bf18 : nt!KiPageFault+0x16e fffff880`09d1bdb0 fffffa80`05e80cc0 : 00000000`00000000 fffff880`09d1bf18 fffff880`09d1bf18 fffffa80`043df930 : aswMonFlt+0x357e9 fffff880`09d1bdb8 00000000`00000000 : fffff880`09d1bf18 fffff880`09d1bf18 fffffa80`043df930 fffff800`02a8ab7c : 0xfffffa80`05e80cc0 STACK_COMMAND: kb FOLLOWUP_IP: aswMonFlt+357e9 fffff880`03bac7e9 483bfb cmp rdi,rbx SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: aswMonFlt+357e9 FOLLOWUP_NAME: MachineOwner MODULE_NAME: aswMonFlt IMAGE_NAME: aswMonFlt.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4c865084 FAILURE_BUCKET_ID: X64_0x50_aswMonFlt+357e9 BUCKET_ID: X64_0x50_aswMonFlt+357e9 Followup: MachineOwner ---------
Thank you for replying. I did what you said, uninstalled Avast. But then BSODs still occurs. I have attached the new ones after Avast was uninstalled. Seems like I only get BSOD while playing games.
Edited: Attached more dump files
Last edited by monsteranh; 06 Jun 2011 at 04:30.
This time your Nvidia driver is blamed, remove it and use Driver Sweeper to remove leftover nvidia driver files
Then reinstall the latest Nvidia driver
NVIDIA DRIVERS 275.33 WHQL
Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck D1, {200000017, 2, 8, 200000017} Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys Probably caused by : nvlddmkm.sys ( nvlddmkm+24b377 ) DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) 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 kernel debugger is available get stack backtrace. Arguments: Arg1: 0000000200000017, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000008, value 0 = read operation, 1 = write operation Arg4: 0000000200000017, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cfe100 0000000200000017 CURRENT_IRQL: 2 FAULTING_IP: +0 00000002`00000017 ?? ??? PROCESS_NAME: System CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 TRAP_FRAME: fffff80000b9c810 -- (.trap 0xfffff80000b9c810) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=fffffa8007242300 rbx=0000000000000000 rcx=fffffa8007242300 rdx=0000000000000048 rsi=0000000000000000 rdi=0000000000000000 rip=0000000200000017 rsp=fffff80000b9c9a0 rbp=0000000000000000 r8=0000000000000000 r9=0000000000000000 r10=000000000000000a r11=fffff80000b9ca20 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc 00000002`00000017 ?? ??? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002ace2a9 to fffff80002aced00 FAILED_INSTRUCTION_ADDRESS: +0 00000002`00000017 ?? ??? STACK_TEXT: fffff800`00b9c6c8 fffff800`02ace2a9 : 00000000`0000000a 00000002`00000017 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx fffff800`00b9c6d0 fffff800`02accf20 : fffffa80`07b72550 fffff880`0f37ac29 00000000`00324ae8 fffffa80`07242310 : nt!KiBugCheckDispatch+0x69 fffff800`00b9c810 00000002`00000017 : fffff880`0f47c377 fffff800`00b9c9b0 00000000`00000000 fffff880`0f484e32 : nt!KiPageFault+0x260 fffff800`00b9c9a0 fffff880`0f47c377 : fffff800`00b9c9b0 00000000`00000000 fffff880`0f484e32 fffff800`00b9cad0 : 0x2`00000017 fffff800`00b9c9a8 fffff800`00b9c9b0 : 00000000`00000000 fffff880`0f484e32 fffff800`00b9cad0 fffff880`0f417bc4 : nvlddmkm+0x24b377 fffff800`00b9c9b0 00000000`00000000 : fffff880`0f484e32 fffff800`00b9cad0 fffff880`0f417bc4 00000000`00000048 : 0xfffff800`00b9c9b0 STACK_COMMAND: kb FOLLOWUP_IP: nvlddmkm+24b377 fffff880`0f47c377 ?? ??? SYMBOL_STACK_INDEX: 4 SYMBOL_NAME: nvlddmkm+24b377 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nvlddmkm IMAGE_NAME: nvlddmkm.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4dd73a68 FAILURE_BUCKET_ID: X64_0xD1_CODE_AV_BAD_IP_nvlddmkm+24b377 BUCKET_ID: X64_0xD1_CODE_AV_BAD_IP_nvlddmkm+24b377 Followup: MachineOwner ---------
here is all the dumps I have up till now.
Anh
Seems like a hardware error related to your graphic card, test your Graphics card and RAM
https://www.sevenforums.com/tutorials...test-occt.html
RAM - Test with Memtest86+
Do you have any external USB devices such as TV-receivers?
Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3D, {fffff880069f5110, 0, 0, fffff80002a924d4} Probably caused by : hardware ( nt!KiInterruptHandler+29 ) INTERRUPT_EXCEPTION_NOT_HANDLED (3d) Arguments: Arg1: fffff880069f5110 Arg2: 0000000000000000 Arg3: 0000000000000000 Arg4: fffff80002a924d4 Debugging Details: ------------------ CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3D PROCESS_NAME: Wow.exe CURRENT_IRQL: d EXCEPTION_RECORD: fffff880069f58b8 -- (.exr 0xfffff880069f58b8) ExceptionAddress: fffff80002a924d4 (nt!KeUpdateSystemTime+0x0000000000000394) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: ffffffffffffffff Attempt to read from address ffffffffffffffff TRAP_FRAME: fffff880069f5960 -- (.trap 0xfffff880069f5960) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=3cf8cf8adef3e700 rbx=0000000000000000 rcx=0000000000000011 rdx=00000000000072fd rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002a924d4 rsp=fffff880069f5af0 rbp=fffff78000000300 r8=00000000000088dc r9=0000000000000000 r10=0000000000000000 r11=fffff880069f5b40 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc nt!KeUpdateSystemTime+0x394: fffff800`02a924d4 0000 add byte ptr [rax],al ds:3cf8cf8a`def3e700=?? Resetting default scope MISALIGNED_IP: nt!KeUpdateSystemTime+394 fffff800`02a924d4 0000 add byte ptr [rax],al LAST_CONTROL_TRANSFER: from fffff80002a872a9 to fffff80002a87d00 STACK_TEXT: fffff880`069f4858 fffff800`02a872a9 : 00000000`0000003d fffff880`069f5110 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx fffff880`069f4860 fffff800`02a835e9 : 00000000`00000001 00000000`459f0000 fffff880`069f5110 fffff800`02ab3890 : nt!KiBugCheckDispatch+0x69 fffff880`069f49a0 fffff800`02ab355d : fffff800`0301e8d0 fffff800`030145cc fffff800`02ff1000 fffff880`069f58b8 : nt!KiInterruptHandler+0x29 fffff880`069f49d0 fffff800`02ab2335 : fffff800`02bcef3c fffff880`069f4a48 fffff880`069f58b8 fffff800`02a08000 : nt!RtlpExecuteHandlerForException+0xd fffff880`069f4a00 fffff800`02ac33b1 : fffff880`069f58b8 fffff880`069f5110 fffff880`00000000 fffff800`02bfae80 : nt!RtlDispatchException+0x415 fffff880`069f50e0 fffff800`02a87382 : fffff880`069f58b8 00000000`00123bd4 fffff880`069f5960 00000000`00002710 : nt!KiDispatchException+0x135 fffff880`069f5780 fffff800`02a85c8a : fffff880`0f1d3a48 fffffa80`056d3000 fffffa80`046855d0 fffffa80`0440f5b0 : nt!KiExceptionDispatch+0xc2 fffff880`069f5960 fffff800`02a924d4 : 00000000`0023ec40 fffff800`02bfae80 00000000`00002710 00000000`0023ec40 : nt!KiGeneralProtectionFault+0x10a fffff880`069f5af0 fffff800`02ffb895 : fffff800`030213c0 fffff880`069f5ca0 fffff800`030213c0 fffff800`00000000 : nt!KeUpdateSystemTime+0x394 fffff880`069f5bf0 fffff800`02a84233 : 00000000`3736dc38 00000000`00002601 fffffa80`04da0180 fffffa80`046678f0 : hal!HalpHpetClockInterrupt+0x8d fffff880`069f5c20 00000000`012ae460 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x163 00000000`0015e45c 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x12ae460 STACK_COMMAND: kb FOLLOWUP_IP: nt!KiInterruptHandler+29 fffff800`02a835e9 90 nop SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: nt!KiInterruptHandler+29 FOLLOWUP_NAME: MachineOwner IMAGE_NAME: hardware DEBUG_FLR_IMAGE_TIMESTAMP: 0 MODULE_NAME: hardware FAILURE_BUCKET_ID: X64_IP_MISALIGNED BUCKET_ID: X64_IP_MISALIGNED Followup: MachineOwner ---------
Last edited by yowanvista; 07 Jun 2011 at 05:35.
Quote