BSOD shortly after logon


  1. Posts : 2
    Windows 7 Pro x64
       #1

    BSOD shortly after logon


    I am experiencing an occasional BSOD when booting the computer. This occurs shortly after logging on. A BSOD will flash very quickly so I can't really tell what's written. Then the system will reboot spontaneously, and then works fine thereafter. My previous installation (Win XP sp3 x86) also had a habit of spontaneously rebooting after very lenghty boot-up, but without showing a BSOD - on almost the same hardware.

    Since reinstalling with Win7 x64, my system has booted much more quickly and the reboot problem almost disappeared, but I still get an occasional BSOD and reboot.

    A few specs:
    Windows 7 Pro x64 (French version)
    Full version
    Clean install on brand new HDD (about 1 month old)
    Opteron 885 CPU (also tried Opteron 275 and 148 - same result)

    This is an older motherboard, so I suspect the problem might be with the hardware, but I would like to narrow down the exact source of this annoyance. I cannot afford a new mobo this year, so I have to live with this old system for the time being.

    thanks in advance.
      My Computer


  2. Posts : 306
    Windows 7 Ultimate x64
       #2

    Hello, welcome to SevenForums!

    Three bugchecks, one caused by aswSP.SYS (avast! Self Protection Driver) and other two caused by atikmdag.sys (amd/ati video driver).

    1. Uninstall / Remove Avast from your system and install Microsoft Security Essentials for testing purposes!

    2. Uninstall your current ATI drivers and install the latest version here.

    Drivers that need to be updated:
    LVUSBS64.sys - LVUSBS64 Thu Oct 11 21:39:40 2007 (Logitech Camera driver). Update here.

    CamDrL64.sys - CamDrL64 Sat Feb 03 13:17:27 2007 (Logitech QuickCam Pro 3000). Update here.

    VSTCNXT6.SYS - VSTCNXT6 Wed Oct 15 20:52:22 2008 (Conexant SoftK56 Modem Driver). Update here.

    dne64x.sys - dne64x Mon Nov 10 20:01:24 2008 (Citrix Deterministic Network Enhancer Miniport or Cisco Systems VPN Client). Update here.
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    KMODE_EXCEPTION_NOT_HANDLED (1e)
    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.
    Arguments:
    Arg1: 0000000000000000, The exception code that was not handled
    Arg2: 0000000000000000, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: 0000000000000000, Parameter 1 of the exception
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.
    
    FAULTING_IP: 
    +3061643963623765
    00000000`00000000 ??              ???
    
    EXCEPTION_PARAMETER1:  0000000000000000
    
    EXCEPTION_PARAMETER2:  0000000000000000
    
    ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0
    
    BUGCHECK_STR:  0x1E_0
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    EXCEPTION_RECORD:  fffff80003c57768 -- (.exr 0xfffff80003c57768)
    ExceptionAddress: fffff800028bfa70 (nt!DbgBreakPoint)
       ExceptionCode: 80000003 (Break instruction exception)
      ExceptionFlags: 00000000
    NumberParameters: 1
       Parameter[0]: 0000000000000000
    
    TRAP_FRAME:  fffff80003c57810 -- (.trap 0xfffff80003c57810)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000002 rbx=0000000000000000 rcx=0000000000000000
    rdx=fffffa8003f41880 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff800028bfa71 rsp=fffff80003c579a8 rbp=0000000000000000
     r8=fffffa80053137a0  r9=0000000000000000 r10=fffffa80046d7b10
    r11=fffff80003c57ac8 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz na pe nc
    nt!DbgBreakPoint+0x1:
    fffff800`028bfa71 c3              ret
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff800028bf5fe to fffff800028c7c10
    
    STACK_TEXT:  
    fffff800`03c56848 fffff800`028bf5fe : fffffa80`04b21c00 00000000`00000000 fffff800`03c56fc0 fffff800`028f3830 : nt!KeBugCheck
    fffff800`03c56850 fffff800`028f34fd : fffff800`02ad171c fffff800`02a0ec30 fffff800`0284b000 fffff800`03c57768 : nt!KiKernelCalloutExceptionHandler+0xe
    fffff800`03c56880 fffff800`028f22d5 : fffff800`02a120fc fffff800`03c568f8 fffff800`03c57768 fffff800`0284b000 : nt!RtlpExecuteHandlerForException+0xd
    fffff800`03c568b0 fffff800`02903361 : fffff800`03c57768 fffff800`03c56fc0 fffff800`00000000 fffffa80`03f41880 : nt!RtlDispatchException+0x415
    fffff800`03c56f90 fffff800`028c72c2 : fffff800`03c57768 fffffa80`03f41880 fffff800`03c57810 00000000`00000000 : nt!KiDispatchException+0x135
    fffff800`03c57630 fffff800`028c50f4 : 00000000`00000000 fffffa80`044b2170 fffffa80`05c39f30 fffff880`051217da : nt!KiExceptionDispatch+0xc2
    fffff800`03c57810 fffff800`028bfa71 : fffff880`048dc2a1 fffff800`02a3de80 fffff780`00000320 00000000`00007f50 : nt!KiBreakpointTrap+0xf4
    fffff800`03c579a8 fffff880`048dc2a1 : fffff800`02a3de80 fffff780`00000320 00000000`00007f50 fffff800`028d2497 : nt!DbgBreakPoint+0x1
    fffff800`03c579b0 fffff800`02a3de80 : fffff780`00000320 00000000`00007f50 fffff800`028d2497 fffffa80`03f41880 : aswSP+0x62a1
    fffff800`03c579b8 fffff780`00000320 : 00000000`00007f50 fffff800`028d2497 fffffa80`03f41880 fffff800`028cb021 : nt!KiInitialPCR+0x180
    fffff800`03c579c0 00000000`00007f50 : fffff800`028d2497 fffffa80`03f41880 fffff800`028cb021 fffffa80`03f41953 : 0xfffff780`00000320
    fffff800`03c579c8 fffff800`028d2497 : fffffa80`03f41880 fffff800`028cb021 fffffa80`03f41953 fffff880`0581608c : 0x7f50
    fffff800`03c579d0 fffff880`010aad6d : fffff880`03c7d010 fffff800`03c57b00 fffffa80`046d7b10 00000000`00000000 : nt!KeUpdateSystemTime+0x377
    fffff800`03c57ad0 fffff880`010aa976 : fffffa80`046d7b10 00000000`00000001 00000000`00000001 fffffa80`04693060 : storport!RaUnitAsyncError+0x26d
    fffff800`03c57bb0 fffff880`010aa553 : 00000000`00000008 00000000`00000001 00000000`ffffffed 00000135`00dbbfcd : storport!RaidUnitCompleteRequest+0x3a6
    fffff800`03c57c90 fffff800`028d30ac : fffff800`02a3de80 00000000`00000000 fffffa80`04693128 00000000`00000050 : storport!RaidpAdapterDpcRoutine+0x53
    fffff800`03c57cd0 fffff800`028bf96a : fffff800`02a3de80 fffff800`02a4bcc0 00000000`00000000 fffff880`010aa500 : nt!KiRetireDpcList+0x1bc
    fffff800`03c57d80 00000000`00000000 : fffff800`03c58000 fffff800`03c52000 fffff800`03c57d40 00000000`00000000 : nt!KiIdleLoop+0x5a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    aswSP+62a1
    fffff880`048dc2a1 ??              ???
    
    SYMBOL_STACK_INDEX:  8
    
    SYMBOL_NAME:  aswSP+62a1
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: aswSP
    
    IMAGE_NAME:  aswSP.SYS
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4ed3cab5
    
    FAILURE_BUCKET_ID:  X64_0x1E_0_aswSP+62a1
    
    BUCKET_ID:  X64_0x1E_0_aswSP+62a1
    
    Followup: MachineOwner
    
    -----------------------------------
    
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.
    Arguments:
    Arg1: fffffa80061c53a0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff88004abad9c, The pointer into responsible device driver module (e.g. owner tag).
    Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
    Arg4: 0000000000000002, Optional internal context dependent data.
    
    Debugging Details:
    ------------------
    
    
    FAULTING_IP: 
    atikmdag+12d9c
    fffff880`04abad9c 48895c2408      mov     qword ptr [rsp+8],rbx
    
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
    
    CUSTOMER_CRASH_COUNT:  1
    
    BUGCHECK_STR:  0x116
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    STACK_TEXT:  
    fffff880`041b69c8 fffff880`0507c000 : 00000000`00000116 fffffa80`061c53a0 fffff880`04abad9c 00000000`00000000 : nt!KeBugCheckEx
    fffff880`041b69d0 fffff880`0507bd0a : fffff880`04abad9c fffffa80`061c53a0 fffffa80`04fc0c00 fffffa80`05989410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
    fffff880`041b6a10 fffff880`05122f07 : fffffa80`061c53a0 00000000`00000000 fffffa80`04fc0c00 fffffa80`05989410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
    fffff880`041b6a40 fffff880`0514cb75 : 00000000`ffffffff 00000000`000003ea 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
    fffff880`041b6b20 fffff880`0514b2bb : 00000000`00000102 00000000`00000000 00000000`000003ea 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
    fffff880`041b6b50 fffff880`0511e2c6 : ffffffff`ff676980 fffffa80`05989410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
    fffff880`041b6bf0 fffff880`0514ae7a : 00000000`00000000 00000000`0000000f 00000000`00000080 fffffa80`058b5c68 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
    fffff880`041b6d00 fffff800`02b7cfee : 00000000`022582c7 fffffa80`05e084d0 fffffa80`03c6e6f0 fffffa80`05e084d0 : dxgmms1!VidSchiWorkerThread+0xba
    fffff880`041b6d40 fffff800`028d35e6 : fffff880`009e4180 fffffa80`05e084d0 fffff880`009eef40 fffff880`0121c384 : nt!PspSystemThreadStartup+0x5a
    fffff880`041b6d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    FOLLOWUP_IP: 
    atikmdag+12d9c
    fffff880`04abad9c 48895c2408      mov     qword ptr [rsp+8],rbx
    
    SYMBOL_NAME:  atikmdag+12d9c
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: atikmdag
    
    IMAGE_NAME:  atikmdag.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  49f199cd
    
    FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmdag.sys
    
    BUCKET_ID:  X64_0x116_IMAGE_atikmdag.sys
    
    Followup: MachineOwner
      My Computer


  3. Posts : 2
    Windows 7 Pro x64
    Thread Starter
       #3

    Thanks. This is interesting, since the video board is the next thing I wanted to change. I am currently using Windows 7's default drivers for this board since there aren't any newer ones from ATI's website. Yes I know, this video card is totally obsolete...
      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 04:17.
Find Us