BSOD on shutdown

Page 2 of 2 FirstFirst 12

  1. Posts : 4,772
    Windows 7 Ultimate - 64-bit | Windows 8 Pro - 64-bit
       #11

    Hello and Welcome to SF !

    Seems like AVG and nVidia i.e. AVGIDSFilter.sys and nvoclk64.sys causing the problem here. I would recommend to uninstall AVG completely and use the Removal tool AVG - Download tools to remove the left over files. As for nVidia nVidia Driver Cleanup Guide | Captain Debugger

    You could reinstall AVG once the BSOD Stops.

    Bugcheck:

    Code:
    nable to load image \SystemRoot\system32\DRIVERS\AVGIDSFilter.Sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for AVGIDSFilter.Sys
    *** ERROR: Module load completed but symbols could not be loaded for AVGIDSFilter.Sys
    
    Could not read faulting driver name
    Probably caused by : AVGIDSFilter.Sys ( AVGIDSFilter+1406 )
    
    Followup: MachineOwner
    ---------
    
    2: 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: fffffaa00b3b6e40, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff800036f92a9, If non-zero, the instruction address which referenced the bad memory
        address.
    Arg4: 0000000000000005, (reserved)
    
    Debugging Details:
    ------------------
    
    
    Could not read faulting driver name
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800039020e0
     fffffaa00b3b6e40 
    
    FAULTING_IP: 
    nt!MmCopyToCachedPage+219
    fffff800`036f92a9 488b07          mov     rax,qword ptr [rdi]
    
    MM_INTERNAL_CODE:  5
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x50
    
    PROCESS_NAME:  Steam.exe
    
    CURRENT_IRQL:  0
    
    TRAP_FRAME:  fffff8800e5161b0 -- (.trap 0xfffff8800e5161b0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=0000000fffffffff
    rdx=fffff8000365a000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff800036f92a9 rsp=fffff8800e516340 rbp=fffff8800e516380
     r8=0000098000000000  r9=00000000126dc020 r10=0000058000000000
    r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na pe nc
    nt!MmCopyToCachedPage+0x219:
    fffff800`036f92a9 488b07          mov     rax,qword ptr [rdi] ds:00000000`00000000=????????????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff800037498c1 to fffff800036ca740
    
    STACK_TEXT:  
    fffff880`0e516048 fffff800`037498c1 : 00000000`00000050 fffffaa0`0b3b6e40 00000000`00000000 fffff880`0e5161b0 : nt!KeBugCheckEx
    fffff880`0e516050 fffff800`036c882e : 00000000`00000000 00000000`00000000 0000003d`00000000 ffffffff`dc3cba00 : nt! ?? ::FNODOBFM::`string'+0x40e8b
    fffff880`0e5161b0 fffff800`036f92a9 : 00000000`00000002 ffffffff`ffffffff 00000000`00000002 ffffffff`ffffffff : nt!KiPageFault+0x16e
    fffff880`0e516340 fffff800`036f66ce : fffff980`0523c000 00000000`126dc020 fffff880`00000000 00000000`00001000 : nt!MmCopyToCachedPage+0x219
    fffff880`0e516530 fffff800`036f6434 : fffffa80`0a73d910 00000000`126dc020 fffff880`0e516670 00000000`00000000 : nt!CcMapAndCopyInToCache+0x20e
    fffff880`0e516620 fffff880`012dffb8 : 00000000`03200000 fffffa80`063d1000 fffff880`0e516710 fffffa80`000a0000 : nt!CcCopyWrite+0x194
    fffff880`0e5166b0 fffff880`0116a132 : fffffa80`063d1070 fffff880`0116d732 fffff880`000a0000 00000000`000a0001 : Ntfs!NtfsCopyWriteA+0x208
    fffff880`0e5168a0 fffff880`0116dc2a : fffff880`0e516970 fffffa80`060689b8 00000000`12640000 00000000`000a0000 : fltmgr!FltpPerformFastIoCall+0xf2
    fffff880`0e516900 fffff880`0118b7fe : 00000000`000a0000 00000000`00000000 fffffa80`063d1070 fffff880`0e516b00 : fltmgr!FltpPassThroughFastIo+0xda
    fffff880`0e516940 fffff880`04080406 : fffffa80`063d10e4 00000000`10d2e874 00000000`00000000 fffffa80`063d10e4 : fltmgr!FltpFastIoWrite+0x1ce
    fffff880`0e5169e0 fffffa80`063d10e4 : 00000000`10d2e874 00000000`00000000 fffffa80`063d10e4 00000000`00000000 : AVGIDSFilter+0x1406
    fffff880`0e5169e8 00000000`10d2e874 : 00000000`00000000 fffffa80`063d10e4 00000000`00000000 00000000`12640020 : 0xfffffa80`063d10e4
    fffff880`0e5169f0 00000000`00000000 : fffffa80`063d10e4 00000000`00000000 00000000`12640020 fffff880`0e516b00 : 0x10d2e874
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    AVGIDSFilter+1406
    fffff880`04080406 ??              ???
    
    SYMBOL_STACK_INDEX:  a
    
    SYMBOL_NAME:  AVGIDSFilter+1406
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: AVGIDSFilter
    
    IMAGE_NAME:  AVGIDSFilter.Sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4c5896d9
    
    FAILURE_BUCKET_ID:  X64_0x50_AVGIDSFilter+1406
    
    BUCKET_ID:  X64_0x50_AVGIDSFilter+1406
    
    Followup: MachineOwner
    ---------
      My Computer


  2. Posts : 32
    Windows 7 Ultimate x64
    Thread Starter
       #12

    I removed AVG this morning, kicking and blue screening as it went but my PC still managed to error on boot up this evening.
    None of my recent BSODs with the driver verifier enabled have produced any dump files, is there something I need to do to get them as its making troubleshooting difficult with no files to upload for you guys.
      My Computer


  3. Posts : 4,772
    Windows 7 Ultimate - 64-bit | Windows 8 Pro - 64-bit
       #13

    paulmh5 said:
    I removed AVG this morning, kicking and blue screening as it went but my PC still managed to error on boot up this evening.
    None of my recent BSODs with the driver verifier enabled have produced any dump files, is there something I need to do to get them as its making troubleshooting difficult with no files to upload for you guys.
    If AVG is removed but still the dump files are showing left overs of AVG. It's hard to move forward without rule out that cause. Make sure you run the removal tool posted in that article.

    Let's rule out Hardware issues we have to run some test to conform it. Follow this article Hardware Diagnostic | Captain Debugger
      My Computer


  4. Posts : 32
    Windows 7 Ultimate x64
    Thread Starter
       #14

    I used the removal tool for AVG. The PC wouldn't boot into windows again after the tool rebooted so I had to run it via safe mode then reboot to get back in.
    The dump files that were attached are from Sunday and one from yesterday. The AVG one (if I'm reading your output right) is from the weekend and a conflict with Steam which hopefully should have been sorted with its removal. Since Saturday I must have had at least 10 BSODs that have not produced any dump files for me to upload

    I have run memtest and this is not shown any problems. I have also run WD's diagnostics on the disks with no errors showing. As it stands I can seem to run games ok, the problems seem to occur during boot, that said windows is doing some odd things as well but I can only put those down to corruption from BSODs (at a guess).
      My Computer


  5. Posts : 32
    Windows 7 Ultimate x64
    Thread Starter
       #15

    Managed to boot up with no bsod this morning however I now have the driver verifier turned off. The sfc /scannow is still reporting errors however its log file is huge and I can only pick out the below as a problem:

    Code:
     
    2011-02-16 20:58:37, Info   CSI    000001a5 [SR] Cannot repair member file [l:36{18}]"Amd64\hpk7100t.xml" of prnhp003.inf, Version = 6.1.7600.16385, 
     pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, file is missing
    2011-02-16 20:58:39, Info   CSI    000001a6 [SR] Cannot repair member file [l:36{18}]"Amd64\hpk7100t.xml" of prnhp003.inf, Version = 6.1.7600.16385, 
     pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, file is missing
    2011-02-16 20:58:39, Info   CSI    000001a7 [SR] This component was referenced by [l:186{93}]"Microsoft-Windows-Printer-Drivers-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.INF_prnhp003"
    Not sure if that means anything to anyone or if there is something better to search for in the log file? I'm still confused as to why my PC is logging dump files.
    Are there any other things I can try to look for and repair problems or is it back to formatting and starting again
      My Computer


  6. Posts : 4,772
    Windows 7 Ultimate - 64-bit | Windows 8 Pro - 64-bit
       #16

    Update the Motherboard Chipset drivers.
      My Computer


  7. Posts : 32
    Windows 7 Ultimate x64
    Thread Starter
       #17

    I've got the latest release from Nvidia for my board, 15.53 I think.
      My Computer


  8. Posts : 4,772
    Windows 7 Ultimate - 64-bit | Windows 8 Pro - 64-bit
       #18

    paulmh5 said:
    I've got the latest release from Nvidia for my board, 15.53 I think.
    I would suggest to reinstall it. If still you're getting BSOD then I guess we might need to reinstall Windows because lot of files corrupted and missing on SFC report is not a good sign.
      My Computer


  9. Posts : 32
    Windows 7 Ultimate x64
    Thread Starter
       #19

    It seems to have stopped BSODing now I've disabled the driver verifier tool.
    I'm away for the weekend so I'll look at it again Monday. Its been doing this BSOD then no BSOD thing now for a while so I think I may have to look at a clean install, I just hope its not a hardware problem after all
      My Computer


 
Page 2 of 2 FirstFirst 12

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 10:19.
Find Us