Win7 frequent crashes


  1. Posts : 5
    Windows 7 Home Premium 64-bit
       #1

    Win7 frequent crashes


    Hi. I'm just new here and I'm not very tech savvy. I wanted to see what you guys think first about my problem(s) before I run off to a service center somewhere.

    I don't know specifically why my WIN7 crashes. It came with the Vaio VGN-FW510F I bought last Nov. It was working ok the first few weeks then it started to crash on me whenever I watched videos. Then it also started crashing on me while doing other stuff as well like using Firefox or typing in Word.

    I attached the minidump zip so you guys could have a look. If its kinda hard to fix already, could you also advise me if it'd be wiser to just let a pro do all the fixing for me? thanks!
      My Computer


  2. Posts : 5,705
    Win7 x64 + x86
       #2

    We can coach you through most repairs BUT since the system is still under warranty it'd be better to let the pro's fix it if we find hardware problems (those are covered under warranty).

    I always suggest these for starters:
    H/W Diagnostics:
    Please start by running these hardware diagnostics:
    Memory Diagnostics (read the details at the link)
    HD Diagnostic (read the details at the link)

    Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)
    Next, I see lot's of issues with your Norton/Symantec product. Please do this:
    Anti-Virus Removal:
    Please do the following:
    - download a free antivirus for testing purposes: Free AntiVirus
    - uninstall the Norton from your system
    - remove any remnants of Norton using this free tool: Download and run the Norton Removal Tool
    - IMMEDIATELY install and update the free antivirus
    - check to see if this fixes the BSOD's
    After that, I'd update your Intel wireless networking drivers because netw5v64.sys is blamed in one of the crashes.

    Finally, Please update or remove these older drivers that were loaded at the time of the crash. Don't use Windows Update or the Update drivers function of Device Manager. Please use the following instructions to locate the most current drivers:
    How To Find Updated Drivers:
    - search Google for the name of the driver
    - compare the Google results with what's installed on your system to figure out which device/program it belongs to
    - visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
    - if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
    Here's the older drivers:
    Code:
    adfs.SYS     Thu Jun 26 16:52:37 2008 - Adobe File System Driver http://www.adobe.com/downloads/
    SFEP.sys     Fri Aug 03 01:35:53 2007 - Sony Firmware Extension Parser driver                                                               http://esupport.sony.com/perl/select-system.pl
    wacommousefilter.sys Fri Feb 16 13:12:17 2007 - Wacom Mouse Filter Driver http://www.wacom.com/downloads/drivers.php
    WacomVKHid.sys Thu Feb 15 18:10:54 2007 - Wacom Virtual HID Driver http://www.wacom.com/downloads/drivers.php
    BSOD Summary:
    Code:
    BugCheck 1E, {ffffffffc0000005, fffff88003b9a778, 0, 104d}
    Probably caused by : ENG64.SYS ( ENG64+6778 )
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    BugCheck 1E, {ffffffffc0000005, fffff80002f024de, 0, 4dc}
    Probably caused by : BHDrvx64.sys ( BHDrvx64+573c )
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    BugCheck DA, {504, fffff6fc40015668, 1, 2acd}
    Probably caused by : iaStor.sys ( iaStor+4bea5 )
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    BugCheck 4E, {99, 1182b1, 2, 118280}
    Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    BugCheck 4E, {99, a09f1, 2, a09ee}
    Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    BugCheck A, {2728, d, 0, fffff800030d6bb0}
    Probably caused by : memory_corruption
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    BugCheck 19, {20, fffffa80047fd450, fffffa80047fd4d0, 4080004}
    Probably caused by : SYMEFA64.SYS ( SYMEFA64+2f48f )
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    BugCheck 1000007E, {ffffffffc0000005, fffff80003082260, fffff88002e93308, fffff88002e92b60}
    Probably caused by : memory_corruption ( nt!MiFreeExcessSegments+20 )
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    BugCheck 1E, {ffffffffc0000005, fffff80003057a5a, 1, 8}
    Probably caused by : ntkrnlmp.exe ( nt!ObpDeferObjectDeletion+12 )
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    BugCheck 3D, {fffff80000b9c1d0, 0, 0, fffff800030c52f2}
    Probably caused by : ntkrnlmp.exe ( nt!KiInterruptHandler+29 )
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    BugCheck A, {5564, d, 1, fffff80002277440}
    Probably caused by : ntkrnlmp.exe ( nt!KiInterruptDispatchNoLock+1b0 )
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    BugCheck A, {fffff300065f7640, 2, 0, fffff800030c276f}
    Probably caused by : CI.dll ( CI!SHATransform+236 )
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    BugCheck FC, {fffff88008da5c60, 8000000080c42963, fffff88008da59e0, 2}
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+42567 )
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    BugCheck 3D, {fffff8800b913200, 0, 0, fffff800030c14f5}
    Probably caused by : hardware ( nt!KiInterruptHandler+29 )
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    BugCheck 3D, {fffff80000b9c1d0, 0, 0, fffff800030854a9}
    Probably caused by : ntkrnlmp.exe ( nt!KiInterruptHandler+29 )
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    BugCheck D1, {1d, 7, 1, fffff88004547ab1}
    Probably caused by : i8042prt.sys ( i8042prt!I8042MouseInterruptService+41 )
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    BugCheck A, {ffffe8800a782ba0, d, 0, fffff800030c4452}
    Probably caused by : ntkrnlmp.exe ( nt!KiInterruptDispatchNoLock+1c2 )
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    BugCheck 3D, {fffff80000b9c180, 0, 0, fffff80003085a31}
    Probably caused by : memory_corruption
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    BugCheck 4E, {99, b0946, 0, 1}
    Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    BugCheck 19, {20, fffffa8008197760, fffffa80081977e0, 4080004}
    Probably caused by : win32k.sys ( win32k!SURFACE::bDeleteSurface+3c8 )
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    BugCheck A, {a, 2, 1, fffff80003087653}
    Probably caused by : ntkrnlmp.exe ( nt!KiCancelTimer+3 )
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    BugCheck C2, {7, 1097, 406000c, fffffa80045c1b30}
    Probably caused by : netw5v64.sys ( netw5v64+6009 )
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
    BugCheck A, {2729, d, 0, fffff800030c9bb0}
    Probably caused by : memory_corruption
      My Computer


  3. Posts : 5
    Windows 7 Home Premium 64-bit
    Thread Starter
       #3

    Thanks a lot! Will see what I can do with these first before I give up and let the pros do their work.
      My Computer


  4. Posts : 5
    Windows 7 Home Premium 64-bit
    Thread Starter
       #4

    Hi. I got a new crash dump again just a few minutes ago. I just wanted to know if this is anything new or still one of the problems mentioned earlier.

    I've already removed Norton and updated the drivers for everything (I think) except the Adobe File System Driver, which I'm having difficulty finding.

    Thanks for all the help so far!
      My Computer


  5. Posts : 28,845
    Win 8 Release candidate 8400
       #5

    r3nka said:
    Hi. I got a new crash dump again just a few minutes ago. I just wanted to know if this is anything new or still one of the problems mentioned earlier.

    I've already removed Norton and updated the drivers for everything (I think) except the Adobe File System Driver, which I'm having difficulty finding.

    Thanks for all the help so far!
    Hi and welcome

    the probable cause for this crash is the kl1.sys driver in Kaspersky. Seems like you are not having much luck with anti virus apps.


    I would un-install and try Microsoft Security essentials

    Ken J+

    Code:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\K\Desktop\011110-25240-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Machine Name:
    Kernel base = 0xfffff800`0305e000 PsLoadedModuleList = 0xfffff800`0329be50
    Debug session time: Mon Jan 11 06:52:30.822 2010 (GMT-5)
    System Uptime: 0 days 0:24:31.225
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .............................
    Loading User Symbols
    Loading unloaded module list
    ...............
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1000007E, {ffffffffc0000005, fffff8000336c4ab, fffff880037d5428, fffff880037d4c80}
    
    Unable to load image \SystemRoot\system32\DRIVERS\kl1.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for kl1.sys
    *** ERROR: Module load completed but symbols could not be loaded for kl1.sys
    Probably caused by : kl1.sys ( kl1+3a76e )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
    This is a very common bugcheck.  Usually the exception address pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this address.
    Some common problems are exception code 0x80000003.  This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG.  This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG.  This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff8000336c4ab, The address that the exception occurred at
    Arg3: fffff880037d5428, Exception Record Address
    Arg4: fffff880037d4c80, Context Record Address
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    FAULTING_IP: 
    nt!CmpReportNotifyHelper+12b
    fffff800`0336c4ab 418b4804        mov     ecx,dword ptr [r8+4]
    
    EXCEPTION_RECORD:  fffff880037d5428 -- (.exr 0xfffff880037d5428)
    ExceptionAddress: fffff8000336c4ab (nt!CmpReportNotifyHelper+0x000000000000012b)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: ffffffffffffffff
    Attempt to read from address ffffffffffffffff
    
    CONTEXT:  fffff880037d4c80 -- (.cxr 0xfffff880037d4c80)
    rax=0000000000c10004 rbx=fffff8a00020ff50 rcx=0000000000000000
    rdx=0000000000000000 rsi=0000000000000000 rdi=fffff8a000023200
    rip=fffff8000336c4ab rsp=fffff880037d5660 rbp=fffff8a000023200
     r8=002d1e4000000000  r9=0000000000000001 r10=fffff8a000023200
    r11=000000000000000f r12=000000000105d5b0 r13=fffff8a000b585b4
    r14=fffff8a004c7acc0 r15=fffff880037d57a0
    iopl=0         nv up ei ng nz na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
    nt!CmpReportNotifyHelper+0x12b:
    fffff800`0336c4ab 418b4804        mov     ecx,dword ptr [r8+4] ds:002b:002d1e40`00000004=????????
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  1
    
    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    EXCEPTION_PARAMETER1:  0000000000000000
    
    EXCEPTION_PARAMETER2:  ffffffffffffffff
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800033060e0
     ffffffffffffffff 
    
    FOLLOWUP_IP: 
    kl1+3a76e
    fffff880`03c5c76e ??              ???
    
    BUGCHECK_STR:  0x7E
    
    LAST_CONTROL_TRANSFER:  from fffff8000336c9af to fffff8000336c4ab
    
    STACK_TEXT:  
    fffff880`037d5660 fffff800`0336c9af : fffff8a0`04c7acc0 fffff8a0`00023200 00000000`00000000 00000000`00000003 : nt!CmpReportNotifyHelper+0x12b
    fffff880`037d56f0 fffff800`0336c120 : fffff8a0`0b698880 fffff880`037d5878 fffff880`00000003 fffffa80`04324250 : nt!CmSetValueKey+0x437
    fffff880`037d5830 fffff800`030cf153 : ffffffff`80000910 fffff800`033ade12 fffff880`00000000 fffff800`00000003 : nt!NtSetValueKey+0x31f
    fffff880`037d5950 fffff800`030cb6f0 : fffff880`03c5c76e ffffffff`80000910 00000000`0070006e fffff880`03c50930 : nt!KiSystemServiceCopyEnd+0x13
    fffff880`037d5b58 fffff880`03c5c76e : ffffffff`80000910 00000000`0070006e fffff880`03c50930 fffff800`00000030 : nt!KiServiceLinkage
    fffff880`037d5b60 ffffffff`80000910 : 00000000`0070006e fffff880`03c50930 fffff800`00000030 fffffa80`04324250 : kl1+0x3a76e
    fffff880`037d5b68 00000000`0070006e : fffff880`03c50930 fffff800`00000030 fffffa80`04324250 fffff880`00000008 : 0xffffffff`80000910
    fffff880`037d5b70 fffff880`03c50930 : fffff800`00000030 fffffa80`04324250 fffff880`00000008 fffff880`000e000c : 0x70006e
    fffff880`037d5b78 fffff800`00000030 : fffffa80`04324250 fffff880`00000008 fffff880`000e000c fffff880`03c509a0 : kl1+0x2e930
    fffff880`037d5b80 fffffa80`04324250 : fffff880`00000008 fffff880`000e000c fffff880`03c509a0 fffffa80`04324230 : 0xfffff800`00000030
    fffff880`037d5b88 fffff880`00000008 : fffff880`000e000c fffff880`03c509a0 fffffa80`04324230 fffffa80`05e31e60 : 0xfffffa80`04324250
    fffff880`037d5b90 fffff880`000e000c : fffff880`03c509a0 fffffa80`04324230 fffffa80`05e31e60 fffffa80`04324230 : 0xfffff880`00000008
    fffff880`037d5b98 fffff880`03c509a0 : fffffa80`04324230 fffffa80`05e31e60 fffffa80`04324230 fffff880`03c5d099 : 0xfffff880`000e000c
    fffff880`037d5ba0 fffffa80`04324230 : fffffa80`05e31e60 fffffa80`04324230 fffff880`03c5d099 00000000`00000000 : kl1+0x2e9a0
    fffff880`037d5ba8 fffffa80`05e31e60 : fffffa80`04324230 fffff880`03c5d099 00000000`00000000 fffffa80`04324230 : 0xfffffa80`04324230
    fffff880`037d5bb0 fffffa80`04324230 : fffff880`03c5d099 00000000`00000000 fffffa80`04324230 fffffa80`05e31e60 : 0xfffffa80`05e31e60
    fffff880`037d5bb8 fffff880`03c5d099 : 00000000`00000000 fffffa80`04324230 fffffa80`05e31e60 fffffa80`04324230 : 0xfffffa80`04324230
    fffff880`037d5bc0 00000000`00000000 : fffffa80`04324230 fffffa80`05e31e60 fffffa80`04324230 fffffa80`00000008 : kl1+0x3b099
    
    
    SYMBOL_STACK_INDEX:  5
    
    SYMBOL_NAME:  kl1+3a76e
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: kl1
    
    IMAGE_NAME:  kl1.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a9d0591
    
    STACK_COMMAND:  .cxr 0xfffff880037d4c80 ; kb
    
    FAILURE_BUCKET_ID:  X64_0x7E_kl1+3a76e
    
    BUCKET_ID:  X64_0x7E_kl1+3a76e
    
    Followup: MachineOwner
    ---------
      My Computer


  6. Posts : 842
    Windows 7 Ultimate 64 - OEM Service Pack 1
       #6

    Latest Kaspersky version for Win 7 can be found here

    Product Updates and Documentation: Kaspersky Internet Security


    Steve
      My Computer


  7. Posts : 5
    Windows 7 Home Premium 64-bit
    Thread Starter
       #7

    Wow okay. So I replaced a faulty antivirus with another one huh? My laptop came with microsoft security essentials too but I don't know if its doing any good because it never warns me of any threats. when I installed Kaspersky, it immediately warned me of a couple of possible threats. I have the latest version of Kaspersky for Win7 (9.0.0.736) installed as well so I don't know what the problem is anymore.

    Is there anything I could to so that I could keep on using Kaspersky? Or should I just uninstall it and rely on the microsoft security essentials instead?

    Also, I just realized that both the security essentials and kis are on right now, should i be disabling one of them?

    Thanks!
      My Computer


  8. Posts : 842
    Windows 7 Ultimate 64 - OEM Service Pack 1
       #8

    I would try uninstalling Kaspersky completely and then reinstalling it after a reboot. I had similar problems with Kaspersky because I installed the update over the original file, that said I have had no problems since and it is a great program.


    Steve
      My Computer


  9. Posts : 5
    Windows 7 Home Premium 64-bit
    Thread Starter
       #9

    Hi. reinstalled kaspersky. but there still seems to be so many more problems. Sigh. Just today, my laptop crashed several times. The crashes stopped for like a day but then it started again. I attached the latest minidumps. Could you please tell me if these are new problems or the same ones as before... thanks.
      My Computer


 

  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 08:42.
Find Us