locked
Windows 7 64 bit issue RRS feed

Answers

  • Crashed during a video game, eh?

    Do you have the latest Catalyst driver package from ATI?  As of right now that's Catalyst version 11.12.  If not, visit the AMD web site and download and install Catalyst 11.12.  They make driver updates about every month, and the release notes always list lots of games for which bugs are fixed.

    If you ARE runnning the latest driver package, may I suggest downloading Catalyst 11.7 from earlier this year - that version seemed especially stable.  You'll need to uninstall the latest version manually, which will cause Windows to revert back to basic out-of-the-box drivers, then install Catalyst 11.7, as the package will not do an integrated downgrade as far as I know.

     

    -Noel


    Detailed how-to in my new eBook: Configure The Windows 7 "To Work" Options


    • Edited by Noel Carboni Sunday, January 1, 2012 3:18 PM corrected typo
    • Marked as answer by Cloud_TS Thursday, January 5, 2012 2:38 AM
    Sunday, January 1, 2012 3:16 PM

All replies

  • Hi,
     
    For minidump analysis you could start here,
     
     
    I saw MEMORY_MANAGEMENT, BAD_POOL_HEADER, KMODE_EXCEPTION_NOT_HANDLED,
    and PAGE_FAULT_IN_NONPAGED_AREA
     
    To troubleshoot, let's rule out a memory problem,
     
     
    Then enable driver verifier and upload/analyze the latest dumps after
    the next few system crashes
     
     

    -- Mike Burr
    Technology
    Friday, December 30, 2011 6:08 PM
  • Do you have any diagnostics you can run on the computer system?  From your very brief description it sounds like you may have hardware problems.  What kind of machine is it?

     

    -Noel


    My new eBook: Configure The Windows 7 "To Work" Options

    Friday, December 30, 2011 9:56 PM
  • Just ran memtest. no bad sticks. tested each one individually then tested all 4 came out clean.

    AMD Phenom II X4 955/8 gigs ram/HD5870/windows 7 pro



    *edit* not sure if i did this right. ran verifier> followed the blog steps> reboot. Restarted Windows no blue screen. 
    • Edited by ron_swanson Saturday, December 31, 2011 8:57 AM
    Saturday, December 31, 2011 2:54 AM
  • Saturday, December 31, 2011 3:05 AM
  • *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    MEMORY_MANAGEMENT (1a)
        # Any other values for parameter 1 must be individually examined.
    Arguments:
    Arg1: 0000000000005003, The subtype of the bugcheck.
    Arg2: fffff780c0000000
    Arg3: 000000000000776c
    Arg4: 000077780000eeda
    Debugging Details:
    ------------------
    BUGCHECK_STR:  0x1a_5003
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  swtor.exe
    CURRENT_IRQL:  0
    LAST_CONTROL_TRANSFER:  from fffff80002b3232f to fffff80002ac6c40
    STACK_TEXT:  
    fffff880`08fb3358 fffff800`02b3232f : 00000000`0000001a 00000000`00005003 fffff780`c0000000 00000000`0000776c : nt!KeBugCheckEx
    fffff880`08fb3360 fffff800`02add083 : fffff6fc`c011a1e8 00000000`00000001 fffff880`00000003 fffffa80`01df5f50 : nt! ?? ::FNODOBFM::`string'+0x2aa69
    fffff880`08fb34d0 fffff800`02ab5c1e : fffff980`2340c000 00000000`000bf000 00000000`00000000 fffffa80`072d0c00 : nt!MmCheckCachedPageStates+0x4a3
    fffff880`08fb3680 fffff800`02db0e10 : 00000000`00000000 00000000`0b04cdb3 fffffa80`07027070 00000000`c6261250 : nt!CcFetchDataForRead+0x10e
    fffff880`08fb36e0 fffff880`012c7f08 : fffff880`00000000 00000000`00000005 fffffa80`0003324d fffffa80`000bd301 : nt!CcCopyRead+0x180
    fffff880`08fb37a0 fffff880`010cc098 : fffffa80`07027070 fffffa80`072d0b98 fffffa80`070270c0 fffffa80`07027001 : Ntfs!NtfsCopyReadA+0x1a8
    fffff880`08fb3980 fffff880`010cf8ba : fffff880`08fb3a50 00000000`c6261203 00000000`c6261200 fffffa80`07027000 : fltmgr!FltpPerformFastIoCall+0x88
    fffff880`08fb39e0 fffff880`010ed630 : fffffa80`07027070 00000000`00000000 fffff880`08fb3b40 00000000`000bd31e : fltmgr!FltpPassThroughFastIo+0xda
    fffff880`08fb3a20 fffff800`02db0949 : fffffa80`07027070 fffff800`00000001 fffffa80`06a1e7b0 fffffa80`07027070 : fltmgr!FltpFastIoRead+0x1d0
    fffff880`08fb3ac0 fffff800`02ac5ed3 : 00000000`000004f8 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtReadFile+0x417
    fffff880`08fb3bb0 00000000`735a2e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`0cbeecc8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x735a2e09
    STACK_COMMAND:  kb
    FOLLOWUP_IP: 
    nt! ?? ::FNODOBFM::`string'+2aa69
    fffff800`02b3232f cc              int     3
    SYMBOL_STACK_INDEX:  1
    SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+2aa69
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: nt
    IMAGE_NAME:  ntkrnlmp.exe
    DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3
    FAILURE_BUCKET_ID:  X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+2aa69
    BUCKET_ID:  X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+2aa69
    Followup: MachineOwner
    ---------
    ----------------------------------------------------------------
    Please start by proceeding like that:
    • Update all possible drivers
    • Uninstall all unused programs
    • Disable all security softwares you have
    • Run msconfig and disable all startup items / services except Microsoft ones

    Once done, check results.

    If this does not help, consider uploading the full dump MEMORY.DMP under c:\windows\ and then post a link here.

    You can also contact Microsoft CSS for assistance.



    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. 

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations
    Microsoft Certified IT Professional: Enterprise Administrator
    Microsoft Certified IT Professional: Server Administrator
    Microsoft Certified Trainer

    Saturday, December 31, 2011 2:56 PM
  • Sunday, January 1, 2012 9:17 AM
  • Crashed during a video game, eh?

    Do you have the latest Catalyst driver package from ATI?  As of right now that's Catalyst version 11.12.  If not, visit the AMD web site and download and install Catalyst 11.12.  They make driver updates about every month, and the release notes always list lots of games for which bugs are fixed.

    If you ARE runnning the latest driver package, may I suggest downloading Catalyst 11.7 from earlier this year - that version seemed especially stable.  You'll need to uninstall the latest version manually, which will cause Windows to revert back to basic out-of-the-box drivers, then install Catalyst 11.7, as the package will not do an integrated downgrade as far as I know.

     

    -Noel


    Detailed how-to in my new eBook: Configure The Windows 7 "To Work" Options


    • Edited by Noel Carboni Sunday, January 1, 2012 3:18 PM corrected typo
    • Marked as answer by Cloud_TS Thursday, January 5, 2012 2:38 AM
    Sunday, January 1, 2012 3:16 PM
  • Kind of an odd one, can you enable driver verifier and post the next
    couple of dumps?
     
    0: 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:
    ------------------
     EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.
     
    FAULTING_IP:
    +6135316230383632
    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:  swtor.exe
     
    CURRENT_IRQL:  2
     
    EXCEPTION_RECORD:  fffff80000ba25d8 -- (.exr 0xfffff80000ba25d8)
    ExceptionAddress: fffff80002a9b4f9 (nt!KiProcessExpiredTimerList+0x0000000000000129)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: ffffffffffffffff
    Attempt to read from address ffffffffffffffff
     
    TRAP_FRAME:  fffff80000ba2680 -- (.trap 0xfffff80000ba2680)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffffa800a0af168 rbx=0000000000000000 rcx=f7fffa800a0af168
    rdx=0000000000000102 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002a9b4f9 rsp=fffff80000ba2810 rbp=fffffa8007b6c508
     r8=fffff80002c08001  r9=0000000000000002 r10=0000000000000082
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    nt!KiProcessExpiredTimerList+0x129:
    fffff800`02a9b4f9 48894108        mov     qword ptr [rcx+8],rax ds:1200:f7fffa80`0a0af170=????????????????
    Resetting default scope
     
    LAST_CONTROL_TRANSFER:  from fffff80002a875fe to fffff80002a8fc10
     
    STACK_TEXT:
    fffff800`00ba16b8 fffff800`02a875fe : 00000000`00000000 fffffa80`0a7ec790 fffff800`00ba1e30 fffff800`02abb830 : nt!KeBugCheck
    fffff800`00ba16c0 fffff800`02abb4fd : fffff800`02c9971c fffff800`02bd6c30 fffff800`02a13000 fffff800`00ba25d8 : nt!KiKernelCalloutExceptionHandler+0xe
    fffff800`00ba16f0 fffff800`02aba2d5 : fffff800`02bda028 fffff800`00ba1768 fffff800`00ba25d8 fffff800`02a13000 : nt!RtlpExecuteHandlerForException+0xd
    fffff800`00ba1720 fffff800`02acb361 : fffff800`00ba25d8 fffff800`00ba1e30 fffff800`00000000 fffffa80`0a0af160 : nt!RtlDispatchException+0x415
    fffff800`00ba1e00 fffff800`02a8f2c2 : fffff800`00ba25d8 fffffa80`07b6c508 fffff800`00ba2680 00000000`00000000 : nt!KiDispatchException+0x135
    fffff800`00ba24a0 fffff800`02a8dbca : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000003 : nt!KiExceptionDispatch+0xc2
    fffff800`00ba2680 fffff800`02a9b4f9 : fffffa80`07b6c4c0 fffffa80`0ae76c68 fffffa80`0ae76c68 00000000`00000102 : nt!KiGeneralProtectionFault+0x10a
    fffff800`00ba2810 fffff800`02a9b37e : 00000073`65cf56ad fffff800`00ba2e88 00000000`00307a82 fffff800`02c092c8 : nt!KiProcessExpiredTimerList+0x129
    fffff800`00ba2e60 fffff800`02a9b167 : fffff800`02c05ec1 fffffa80`00307a82 fffffa80`081d0d40 00000000`00000082 : nt!KiTimerExpiration+0x1be
    fffff800`00ba2f00 fffff800`02a92765 : 00000000`00000000 fffffa80`0b60e060 00000000`00000000 fffff880`0440ddb0 : nt!KiRetireDpcList+0x277
    fffff800`00ba2fb0 fffff800`02a9257c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KyRetireDpcList+0x5
    fffff880`03961030 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue
     STACK_COMMAND:  kb
     
    FOLLOWUP_IP:
    nt!KiKernelCalloutExceptionHandler+e
    fffff800`02a875fe 90              nop
     
    SYMBOL_STACK_INDEX:  1
     
    SYMBOL_NAME:  nt!KiKernelCalloutExceptionHandler+e
     
    FOLLOWUP_NAME:  MachineOwner
     
    MODULE_NAME: nt
     
    IMAGE_NAME:  ntkrnlmp.exe
     
    DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3
     
    FAILURE_BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e
     
    BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e
     
    Followup: MachineOwner
    ---------
     

    -- Mike Burr
    Technology
    Sunday, January 1, 2012 5:26 PM