BSOD on new PC

Page 1 of 2 12 LastLast

  1. Posts : 87
    Windows 7 Home Premium x64
       #1

    BSOD on new PC


    Hi guys,

    Could you have a look at my dump files please.

    New PC arrived on Saturday morning, installed W7 and drivers. I had a couple of BSOD yesterday so reinstalled last night. Loaded motherboard drivers first then graphics. Seemed ok for the remainder of last night and today but I've just had another.

    64 bit W7
    System came without operating system. Full retail copy installed.

    Thanks in advance
      My Computer


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

    Flik said:
    Hi guys,

    Could you have a look at my dump files please.

    New PC arrived on Saturday morning, installed W7 and drivers. I had a couple of BSOD yesterday so reinstalled last night. Loaded motherboard drivers first then graphics. Seemed ok for the remainder of last night and today but I've just had another.

    64 bit W7
    System came without operating system. Full retail copy installed.

    Thanks in advance

    This crash was fairly straight forward. Its cause, your video driver.
    When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper

    When it is removed then download and install the fresh copy.

    Let us know if you need further assistance with this



    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\Windows7_BSOD_jcgriff2\080110-13884-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;srv*e:\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.16539.amd64fre.win7_gdr.100226-1909
    Machine Name:
    Kernel base = 0xfffff800`02e50000 PsLoadedModuleList = 0xfffff800`0308de50
    Debug session time: Sun Aug  1 15:46:33.098 2010 (GMT-4)
    System Uptime: 0 days 11:03:35.622
    Loading Kernel Symbols
    .
    
    Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
    Run !sym noisy before .reload to track down problems loading symbols.
    
    ..............................................................
    ................................................................
    .....................
    Loading User Symbols
    Loading unloaded module list
    .....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1E, {0, 0, 0, 0}
    
    Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    Probably caused by : atikmdag.sys ( atikmdag+4a179 )
    
    Followup: MachineOwner
    ---------
    
    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        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:
    ------------------
    
    
    OVERLAPPED_MODULE: Address regions for 'WUDFRd' and 'spsys.sys' overlap
    
    EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.
    
    FAULTING_IP: 
    +5ba2952f03b3dd40
    00000000`00000000 ??              ???
    
    EXCEPTION_PARAMETER1:  0000000000000000
    
    EXCEPTION_PARAMETER2:  0000000000000000
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x1E
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  b
    
    EXCEPTION_RECORD:  fffff88002d1acd8 -- (.exr 0xfffff88002d1acd8)
    ExceptionAddress: fffff88003b0c179 (atikmdag+0x000000000004a179)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: ffffffffffffffff
    Attempt to read from address ffffffffffffffff
    
    TRAP_FRAME:  fffff88002d1ad80 -- (.trap 0xfffff88002d1ad80)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffff88003e12f10 rbx=0000000000000000 rcx=fffffa8005d12720
    rdx=fffffa8004fd01c0 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff88003b0c179 rsp=fffff88002d1af10 rbp=fffff88002d1afb0
     r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
    r11=fffff88002d1afb0 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    atikmdag+0x4a179:
    fffff880`03b0c179 ??              ???
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002eb832e to fffff80002ec05d0
    
    STACK_TEXT:  
    fffff880`02d19dc8 fffff800`02eb832e : 00000000`00000008 fffffa80`0563e680 fffff880`02d1a540 fffff800`02eed524 : nt!KeBugCheck
    fffff880`02d19dd0 fffff800`02ee62ed : fffff800`030ceb88 fffff800`03007a40 fffff800`02e50000 fffff880`02d1acd8 : nt!KiKernelCalloutExceptionHandler+0xe
    fffff880`02d19e00 fffff800`02eed950 : fffff800`0300fb24 fffff880`02d19e78 fffff880`02d1acd8 fffff800`02e50000 : nt!RtlpExecuteHandlerForException+0xd
    fffff880`02d19e30 fffff800`02efa8df : fffff880`02d1acd8 fffff880`02d1a540 fffff880`00000000 fffffa80`00000004 : nt!RtlDispatchException+0x410
    fffff880`02d1a510 fffff800`02ebfc42 : fffff880`02d1acd8 00000000`00000000 fffff880`02d1ad80 fffff880`02d1b388 : nt!KiDispatchException+0x16f
    fffff880`02d1aba0 fffff800`02ebe54a : fffffa80`0509d000 fffff880`03b45241 fffffa80`0509d000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
    fffff880`02d1ad80 fffff880`03b0c179 : fffffa80`05346730 0000000f`008e8000 00000000`00000000 00000000`00000001 : nt!KiGeneralProtectionFault+0x10a
    fffff880`02d1af10 fffffa80`05346730 : 0000000f`008e8000 00000000`00000000 00000000`00000001 00000000`00000000 : atikmdag+0x4a179
    fffff880`02d1af18 0000000f`008e8000 : 00000000`00000000 00000000`00000001 00000000`00000000 fffffa80`04ff0740 : 0xfffffa80`05346730
    fffff880`02d1af20 00000000`00000000 : 00000000`00000001 00000000`00000000 fffffa80`04ff0740 00000000`c0000001 : 0xf`008e8000
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    atikmdag+4a179
    fffff880`03b0c179 ??              ???
    
    SYMBOL_STACK_INDEX:  7
    
    SYMBOL_NAME:  atikmdag+4a179
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: atikmdag
    
    IMAGE_NAME:  atikmdag.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4c33da58
    
    FAILURE_BUCKET_ID:  X64_0x1E_atikmdag+4a179
    
    BUCKET_ID:  X64_0x1E_atikmdag+4a179
    
    Followup: MachineOwner
    ---------
    Old drivers

    Code:
    speedfan.sys        fffff880`014dd000    fffff880`014e4000    0x00007000    0x45168798    9/24/2006 09:26:48                        
    usbfilter.sys        fffff880`04262000    fffff880`0426e000    0x0000c000    0x49d5f587    4/3/2009 07:39:51                        
    AtiPcie.sys        fffff880`015f2000    fffff880`015fa000    0x00008000    0x4a005486    5/5/2009 11:00:22                        
    spldr.sys        fffff880`014d5000    fffff880`014dd000    0x00008000    0x4a0858bb    5/11/2009 12:56:27                        
    amdxata.sys        fffff880`00c2a000    fffff880`00c35000    0x0000b000    0x4a12f2eb    5/19/2009 13:56:59
      My Computer


  3. Posts : 87
    Windows 7 Home Premium x64
    Thread Starter
       #3

    Thank you for the quick reply.

    The latest video driver is installed. As this was a new PC this was the first and only driver installed. I shall remove and then run drive sweeper and reinstall and report back.

    Is it worth trying an earler driver version if I still get the same?
      My Computer


  4. Posts : 87
    Windows 7 Home Premium x64
    Thread Starter
       #4

    I removed video drivers last night ran drive sweeper and installed newest ones.

    On boot up this morning everything froze so had to do a restart. On booting I had another blue screen.

    Dumps attached.
      My Computer


  5. Posts : 1,598
    Microsoft Window 7 Professional 32 bit
       #5

    Go to C:\Windows\Minidump and copy all of the dmp files to the desktop. Select all>right-click on one>Send to>New Compressed folder. Then attach the zip file to your next post by use of the paperclip icon in the advanced editor.
    Do that instead!
      My Computer


  6. Posts : 87
    Windows 7 Home Premium x64
    Thread Starter
       #6

    ttran said:
    Go to C:\Windows\Minidump and copy all of the dmp files to the desktop. Select all>right-click on one>Send to>New Compressed folder. Then attach the zip file to your next post by use of the paperclip icon in the advanced editor.
    Do that instead!
    Ok, here you go. Apologies if I didn't do it correctly the last time.
      My Computer


  7. Posts : 1,598
    Microsoft Window 7 Professional 32 bit
       #7

    What antivirus software are you using?
    Code:
    System Uptime: 0 days 0:00:29.948
    It occur when you start your computer, please try to do a clean boot to see if it helps:
    How to troubleshoot a problem by performing a clean boot in Windows Vista or in Windows 7

    Although I'm not so sure about this, but you might want to uninstall ATi catalyst control center. It is known for causing BSODs on some system.
    -Download the driver ONLY (not the whole Catalyst Control Center program) from http://www.ati.com
    -Uninstall all your ATI stuff from Control Panel...Programs...Uninstall a program
    -Install the downloaded driver

    BUGCHECK SUMMARY:
    Code:
    Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\TUANTR~1\AppData\Local\Temp\Rar$DI00.036\080210-14040-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*e:\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.16539.amd64fre.win7_gdr.100226-1909
    Machine Name:
    Kernel base = 0xfffff800`02e5e000 PsLoadedModuleList = 0xfffff800`0309be50
    Debug session time: Mon Aug  2 14:19:21.527 2010 (UTC + 7:00)
    System Uptime: 0 days 0:00:29.948
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ..............
    Loading User Symbols
    Loading unloaded module list
    ....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck A, {0, 2, 1, fffff80002eaa723}
    
    Probably caused by : hardware ( nt!AlpcpLookasidePacketCallbackRoutine+73 )
    
    Followup: MachineOwner
    ---------
    Regard,

    Tuan
      My Computer


  8. Posts : 87
    Windows 7 Home Premium x64
    Thread Starter
       #8

    I'm using MSE.

    I've only had 1 BSOD on startup all the rest have been after I've been using the PC for quite a few hours.

    A couple of times I've had the screen freeze and the display go to what I can only discribe as various shades of blue lines covering the entire screen then the BSOD.

    I know it's a new system but could the graphics card be damaged? Or would it just not work at all if it was that?

    Thanks again for your help.

    *Edit*
    I've uninstalled the catalyst control centre, ran drive sweeper and reinstalled just the video driver.
    Last edited by Flik; 02 Aug 2010 at 07:17. Reason: Additional info
      My Computer


  9. Posts : 1,598
    Microsoft Window 7 Professional 32 bit
       #9

    Good! let us know if you need more help
      My Computer


  10. Posts : 87
    Windows 7 Home Premium x64
    Thread Starter
       #10

    Just had another, thats with just the video driver installed.

    Files attached.
      My Computer


 
Page 1 of 2 12 LastLast

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 20:48.
Find Us