Frequent W7 64bit freeze on Lenovo e520


  1. Posts : 3
    Windows 7 professional 64bit
       #1

    Frequent W7 64bit freeze on Lenovo e520


    Hi guys,

    I have problem, which I canīt manage...I will be very thankful for any reply.

    I made fresh installation on my new Lenovo E520, but it freezes 3x per day. Mouse is moving, but nothing more, task manager canīt be started. It happens with various applications. But normally, no BSOD is displayed.

    I looked at topics:
    "Using Driver Verifier to identify issues with Drivers",
    "Driver Verifier - Enable and Disable"
    "Windows 7 - Blue Screen of Death (BSOD) Posting Instructions"

    I turned on verifier and before system launched, BSOD appeared. I run BSOD Dump & System File Collection app and I exported report in perfmon - both attached.

    I have W7 professional, 64bit, full retail
    Laptop and system installation are new.


    Thank you for reading the post:) and for your replies!! Tom
      My Computer


  2. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #2

    Problem Devices:
    Code:
    Cisco Systems VPN Adapter for 64-bit Windows	ROOT\NET\0000	This device is disabled.

    Antivirus Software:
    Code:
    avastsvc.exe	c:\program files\avast software\avast\avastsvc.exe	1440	8	200	1380	5.3.2012 15:15	7.0.1407.0	43,72 KB (44*768 bytes)	24.2.2012 10:53
    avastui.exe	c:\program files\avast software\avast\avastui.exe	4052	8	200	1380	5.3.2012 15:15	7.0.1407.0	3,84 MB (4*031*368 bytes)	24.2.2012 10:53

    Possible out of date drivers:
    Code:
    psadd	fffff880`08051000	fffff880`0805c000	Mon Feb 19 11:56:37 2007 (45d9f2e5)	0000f656		psadd.sys
    dne64x	fffff880`089d3000	fffff880`089ff000	Mon Nov 10 18:01:24 2008 (4918d964)	000359da		dne64x.sys
    psadd.sys
    dne64x.sys


    Code:
    Loading Dump File [D:\Kingston\BSODDmpFiles\tommy5\Windows_NT6_BSOD_jcgriff2\030512-22167-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
    Machine Name:
    Kernel base = 0xfffff800`02c0a000 PsLoadedModuleList = 0xfffff800`02e4f670
    Debug session time: Mon Mar  5 02:00:05.778 2012 (UTC - 7:00)
    System Uptime: 0 days 0:00:11.949
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .
    Loading User Symbols
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck C9, {23e, fffff88001401324, fffff98008c2aee0, 0}
    
    Unable to load image \SystemRoot\system32\DRIVERS\dtsoftbus01.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for dtsoftbus01.sys
    *** ERROR: Module load completed but symbols could not be loaded for dtsoftbus01.sys
    Probably caused by : dtsoftbus01.sys ( dtsoftbus01+1324 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
    The IO manager has caught a misbehaving driver.
    Arguments:
    Arg1: 000000000000023e, A driver has marked an IRP pending but didn't return STATUS_PENDING.
    Arg2: fffff88001401324, The address in the driver's code where the error was detected.
    Arg3: fffff98008c2aee0, IRP address.
    Arg4: 0000000000000000, Status code.
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0xc9_23e
    
    DRIVER_VERIFIER_IO_VIOLATION_TYPE:  23e
    
    FAULTING_IP: 
    dtsoftbus01+1324
    fffff880`01401324 4053            push    rbx
    
    FOLLOWUP_IP: 
    dtsoftbus01+1324
    fffff880`01401324 4053            push    rbx
    
    IRP_ADDRESS:  fffff98008c2aee0
    
    DEVICE_OBJECT: fffffa80062cb4f0
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    LOCK_ADDRESS:  fffff80002e85b80 -- (!locks fffff80002e85b80)
    
    Resource @ nt!PiEngineLock (0xfffff80002e85b80)    Available
    
    WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.
    
    
    WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.
    
    1 total locks
    
    PNP_TRIAGE: 
    	Lock address  : 0xfffff80002e85b80
    	Thread Count  : 0
    	Thread address: 0x0000000000000000
    	Thread wait   : 0x0
    
    LAST_CONTROL_TRANSFER:  from fffff800031103dc to fffff80002c86c40
    
    STACK_TEXT:  
    fffff880`02fd9968 fffff800`031103dc : 00000000`000000c9 00000000`0000023e fffff880`01401324 fffff980`08c2aee0 : nt!KeBugCheckEx
    fffff880`02fd9970 fffff800`0311a47a : fffff800`0310e9f0 fffff880`01401324 fffff980`08c2aee0 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
    fffff880`02fd99b0 fffff800`0311b34e : 00000000`0000023e 00000000`00000000 fffff980`08c2aee0 00000000`ffffffff : nt!ViErrorFinishReport+0xda
    fffff880`02fd9a00 fffff800`0312671f : fffffa80`06a22c30 fffffa80`059fec50 fffffa80`059fed08 fffff880`01405228 : nt!VfErrorReport6+0x6e
    fffff880`02fd9ad0 fffff800`03126b63 : fffffa80`059fec50 00000000`00000002 fffffa80`062cb4f0 fffff880`014013f4 : nt!IovpCallDriver2+0x13f
    fffff880`02fd9b30 fffff800`0312cc2e : fffff980`08c2aee0 fffff980`08c2aee0 00000000`00000002 fffffa80`062cb4f0 : nt!VfAfterCallDriver+0x353
    fffff880`02fd9b80 fffff880`00ed20c2 : fffff880`00f4b7c0 fffffa80`063f76e0 00000000`00000025 fffffa80`059fec50 : nt!IovCallDriver+0x57e
    fffff880`02fd9be0 fffff880`00ee759f : fffffa80`0604a450 00000000`00000000 fffff880`00000000 fffff880`0119a5d5 : Wdf01000!FxIoTarget::SubmitSync+0x24a
    fffff880`02fd9c90 fffff880`011aee95 : fffffa80`00000020 fffffa80`0604a450 fffffa80`063f76e0 00000000`00000001 : Wdf01000!imp_WdfRequestSend+0x24b
    fffff880`02fd9ce0 fffff880`011af2f4 : 00000000`00000000 00000000`00000024 00000000`00000001 fffff880`02fd9ea0 : cdrom!DeviceSendRequestSynchronously+0xc9
    fffff880`02fd9d40 fffff880`011adf04 : 0000057f`f9c0a7e8 fffff880`02fd9ea0 fffffa80`073936a0 00000000`00000024 : cdrom!DeviceSendSrbSynchronously+0x3ec
    fffff880`02fd9e70 fffff880`011ac825 : fffffa80`00000002 fffffa80`063f5b80 fffff880`011a43b8 0000057f`f9c0a7e8 : cdrom!DeviceCacheDeviceInquiryData+0xbc
    fffff880`02fd9f40 fffff880`00f3c9d4 : 00000000`00000000 fffff880`00000010 00000000`0000000c fffff880`00f45620 : cdrom!DeviceEvtSelfManagedIoInit+0x105
    fffff880`02fd9f80 fffff880`00f3c94e : fffffa80`063f3450 00000000`0000000c fffff880`00f45620 fffff880`00f45600 : Wdf01000!FxSelfManagedIoMachine::Init+0x34
    fffff880`02fd9fb0 fffff880`00f30b9b : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`00f45620 : Wdf01000!FxSelfManagedIoMachine::ProcessEvent+0x14a
    fffff880`02fda020 fffff880`00f306eb : 00000000`00000312 00000000`00000000 fffff880`00f45600 fffff6fc`c0046d30 : Wdf01000!FxPkgPnp::PowerD0StartingStartSelfManagedIo+0x2f
    fffff880`02fda050 fffff880`00f3038e : fffffa80`063f34e0 00000000`00000040 fffff880`00f453e0 00000000`00000040 : Wdf01000!FxPkgPnp::PowerEnterNewState+0x1db
    fffff880`02fda180 fffff880`00f3006c : 00000000`00000000 00000000`00000040 00000000`00000501 fffffa80`063f34e0 : Wdf01000!FxPkgPnp::PowerProcessEventInner+0x13e
    fffff880`02fda1f0 fffff880`00f3db5e : 00000000`00000000 00000000`00000501 00000000`00000000 00000000`00000501 : Wdf01000!FxPkgPnp::PowerProcessEvent+0x1d4
    fffff880`02fda280 fffff880`00f3dabb : 00000000`00000501 00000000`00000000 00000000`00000500 fffff800`0312b5ec : Wdf01000!FxPkgPnp::NotPowerPolOwnerStarting+0xe
    fffff880`02fda2b0 fffff880`00f39950 : fffffa80`063f34e0 00000000`00000001 00000000`00000000 fffff880`00f41ff0 : Wdf01000!FxPkgPnp::NotPowerPolicyOwnerEnterNewState+0x1c7
    fffff880`02fda330 fffff880`00f39372 : 00000000`00000000 00000000`00000001 00000000`00000000 fffffa80`063f7c70 : Wdf01000!FxPkgPnp::PowerPolicyProcessEventInner+0x3f8
    fffff880`02fda3a0 fffff880`00f35a45 : 00000000`00000000 fffffa80`063f7c70 00000000`00000108 00000000`00000000 : Wdf01000!FxPkgPnp::PowerPolicyProcessEvent+0x1e2
    fffff880`02fda430 fffff880`00f35841 : 00000000`00000101 00000000`00000108 00000000`00000108 fffff800`0000000c : Wdf01000!FxPkgPnp::PnpEventHardwareAvailable+0x111
    fffff880`02fda470 fffff880`00f354fe : fffffa80`063f34e0 fffff880`02fda5a0 00000000`00000004 fffff880`00f44390 : Wdf01000!FxPkgPnp::PnpEnterNewState+0x1a5
    fffff880`02fda4e0 fffff880`00f35201 : 00000000`00000000 00000000`00000002 00000000`00000000 fffffa80`063f34e0 : Wdf01000!FxPkgPnp::PnpProcessEventInner+0x122
    fffff880`02fda550 fffff880`00f2cd9c : 00000000`00000000 fffffa80`063f34e0 00000000`00000002 00000000`00000000 : Wdf01000!FxPkgPnp::PnpProcessEvent+0x1b1
    fffff880`02fda5e0 fffff880`00f2bdd6 : fffffa80`05b05540 00000000`00000002 00000000`00000000 fffffa80`063f34e0 : Wdf01000!FxPkgPnp::_PnpStartDevice+0x20
    fffff880`02fda610 fffff880`00efb245 : fffff980`08d5ce50 fffff980`08d5ce50 fffffa80`063f7c70 00000000`00000000 : Wdf01000!FxPkgPnp::Dispatch+0x1b2
    fffff880`02fda680 fffff880`00efb14b : fffff880`02fda768 fffff980`08d5ce50 00000000`00000002 fffffa80`063f7c70 : Wdf01000!FxDevice::Dispatch+0xa9
    fffff880`02fda6b0 fffff800`0312cc16 : fffff980`08d5ce50 00000000`00000002 fffffa80`063f7c70 fffffa80`063f7c70 : Wdf01000!FxDevice::DispatchWithLock+0x93
    fffff880`02fda6f0 fffff800`0303fd6e : fffff980`08d5ce50 fffffa80`0642d420 fffffa80`063f7c70 fffffa80`05b27990 : nt!IovCallDriver+0x566
    fffff880`02fda750 fffff800`02d7787d : fffffa80`062cb4f0 fffffa80`0642d420 fffff800`02d80fa0 00000000`00000000 : nt!PnpAsynchronousCall+0xce
    fffff880`02fda790 fffff800`0304f0b6 : fffff800`02e85940 fffffa80`063f1a40 fffffa80`0642d420 fffffa80`063f1be8 : nt!PnpStartDevice+0x11d
    fffff880`02fda850 fffff800`0304f354 : fffffa80`063f1a40 fffffa80`03d4002a fffffa80`03d45010 00000000`00000001 : nt!PnpStartDeviceNode+0x156
    fffff880`02fda8e0 fffff800`03072a86 : fffffa80`063f1a40 fffffa80`03d45010 00000000`00000002 00000000`00000000 : nt!PipProcessStartPhase1+0x74
    fffff880`02fda910 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PipProcessDevNodeTree+0x296
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    SYMBOL_NAME:  dtsoftbus01+1324
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: dtsoftbus01
    
    IMAGE_NAME:  dtsoftbus01.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4f10358a
    
    FAILURE_BUCKET_ID:  X64_0xc9_23e_VRF_dtsoftbus01+1324
    
    BUCKET_ID:  X64_0xc9_23e_VRF_dtsoftbus01+1324
    
    Followup: MachineOwner
    ---------
    Please remove Daemon Tools, as it uses a driver called dtsoftbus01.sys that is known to cause BSODs.

    I prefer TotalMounter as my CD/DVD virtualization software as it allows me to burn images to a virtual CD/DVD if I just want an ISO file instead of a disc, and it is free.

    Many use MagicISO - Convert BIN to ISO, Create, Edit, Burn, Extract ISO file, ISO/BIN converter/extractor/editor as well, which is also free.


    Also, in the future if you have crashes, please do not use Ccleaner, Windows disk cleanup, etc. to do any file cleaning afterward. These delete the .dmp files that can be analyzed to determine the causes of crashes.
      My Computer


  3. Posts : 3
    Windows 7 professional 64bit
    Thread Starter
       #3

    Thank you for a response, Writhziden. I uninstalled Daemon Tools, but problem persists, any other idea?
      My Computer


  4. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #4

    Do you still have Verifier enabled? Disable through an Elevated Command Prompt by typing
    verifier /reset

    Remove Avast and replace with or the
    If you still have problems, Troubleshoot Application Conflicts by Performing a Clean Startup to see if it is an application or service causing the hangs.

    If problems persist, it may be a corrupted user profile. Fix a corrupted user profile
      My Computer


  5. Posts : 3
    Windows 7 professional 64bit
    Thread Starter
       #5

    I removed Avast and Spyware terminator, I installed Microsoft Essentials and system is stable. Itīs already a week, so everything looks OK!:) Thank you very much for great advices and wish a nice day!
      My Computer


  6. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #6

    You are very welcome. Glad it was resolved by switching to Microsoft Security Essentials. :)
      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 23:58.
Find Us