Asking for analysis

Page 1 of 4 123 ... LastLast

  1. Posts : 20
    windows 7 ultimate 64bit
       #1

    Asking for analysis


    Hey guys,first of all im a new user and regardless of the problem being solved or not, i wanna say thanks for keeping this community up and dealing with ppl's issues

    Now on to the problem, well long story short i had windows 7 enterprise 32 bit and decided to upgrade to windows 7 ultimate 64 bit,and then the blue screens started.After doing some research here i decided to upload my minidump files so maybe you can tell me just what the hell is wrong

    Attachment 164439

    The last file should have driver verifier enabled unless i did something wrong.

    Pls halp!
      My Computer


  2. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #2

    The Realtek NIC driver is the cause, update it
    Realtek

    ASACPI.sys the 2005 version is a huge cause of BSODs
       Information
    The 2005 version of this driver is a known BSOD cause.
    Please visit this link: ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE
    Scroll down to the Utilities category, then scroll down to the "
    ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit" (it's about the 12th item down).
    Download and install it.
    Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.sys file is date stamped from 2009 or 2010 (NOT 2005
    )

    Code:
    ASACPI.sys        fffff880`044a5000    fffff880`044ad000    0x00008000    0x42476c4c    28/03/2005 06:30:36
    Other dumps blame the AMD Radeon driver atikmdag.sys
    Reinstall the AMD driver and stop any overclocking if any
    Code:
    BugCheck D1, {0, 2, 1, fffff880045a1358}
    
    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 : dxgmms1.sys ( dxgmms1!VidSchiProcessCompletedQueuePacketInternal+430 )
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck D1, {0, 2, 0, fffff880016c14c0}
    
    Unable to load image \SystemRoot\system32\DRIVERS\Rt64win7.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for Rt64win7.sys
    *** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
    Probably caused by : Rt64win7.sys ( Rt64win7+16108 )
    
    
    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: 0000000000000000, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff880016c14c0, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d0c100
     0000000000000000 
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    tcpip!TcpTimerUpdateNextExpirationTick+0
    fffff880`016c14c0 48895c2410      mov     qword ptr [rsp+10h],rbx
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    
    BUGCHECK_STR:  0xD1
    
    PROCESS_NAME:  System
    
    TRAP_FRAME:  fffff88008234a40 -- (.trap 0xfffff88008234a40)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=fffffa800532ca60
    rdx=000000000060e198 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff880016c14c0 rsp=fffff88008234bd8 rbp=0000000000008c0e
     r8=0000000000010300  r9=000000000060e18e r10=0000000000000000
    r11=fffff88008234690 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    tcpip!TcpTimerUpdateNextExpirationTick:
    fffff880`016c14c0 48895c2410      mov     qword ptr [rsp+10h],rbx ss:0018:fffff880`08234be8=0000000000000000
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002adc2a9 to fffff80002adcd00
    
    STACK_TEXT:  
    fffff880`082348f8 fffff800`02adc2a9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    fffff880`08234900 fffff800`02adaf20 : fffff800`02ae78a5 fffffa80`05364fb8 00000000`ad4022d5 fffff880`06adeb22 : nt!KiBugCheckDispatch+0x69
    fffff880`08234a40 fffff880`016c14c0 : fffff880`016bdeab fffff880`06adeb22 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
    fffff880`08234bd8 fffff880`016bdeab : fffff880`06adeb22 00000000`00000000 00000000`00000000 fffff8a0`01d52000 : tcpip!TcpTimerUpdateNextExpirationTick
    fffff880`08234be0 fffff880`016b4b97 : fffffa80`0547f3a0 fffffa80`054813a0 fffffa80`00003cd4 00000000`00000000 : tcpip!TcpPreValidatedReceive+0x59b
    fffff880`08234cb0 fffff880`016b470a : 00000000`00000000 fffff880`017d59a0 fffff880`08234e70 fffff880`08235050 : tcpip!IppDeliverListToProtocol+0x97
    fffff880`08234d70 fffff880`016b3d09 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`08234e60 : tcpip!IppProcessDeliverList+0x5a
    fffff880`08234e10 fffff880`016b1a7f : fffff8a0`1045b000 fffffa80`0546c000 fffff880`017d59a0 00000000`05df2001 : tcpip!IppReceiveHeaderBatch+0x23a
    fffff880`08234ef0 fffff880`016b1072 : fffffa80`060bc870 00000000`00000000 fffffa80`05df2001 00000000`00000001 : tcpip!IpFlcReceivePackets+0x64f
    fffff880`082350f0 fffff880`016b050a : fffffa80`05df2010 fffff880`08235220 fffffa80`05df2010 fffff880`016b0000 : tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x2b2
    fffff880`082351d0 fffff800`02ae9668 : fffffa80`05fb0d50 00000000`00004800 fffffa80`07357a60 00000000`00000000 : tcpip!FlReceiveNetBufferListChainCalloutRoutine+0xda
    fffff880`08235220 fffff880`016b0bd2 : fffff880`016b0430 00000000`00000000 00000000`00000002 00000001`00000000 : nt!KeExpandKernelStackAndCalloutEx+0xd8
    fffff880`08235300 fffff880`015bf0eb : fffffa80`05df28d0 00000000`00000000 fffffa80`05dc91a0 00000000`00000282 : tcpip!FlReceiveNetBufferListChain+0xb2
    fffff880`08235370 fffff880`01588ad6 : fffffa80`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisMIndicateNetBufferListsToOpen+0xdb
    fffff880`082353e0 fffff880`01501cc1 : fffffa80`05dc91a0 00000000`00000002 00000000`00000001 00000000`00003402 : ndis!ndisMDispatchReceiveNetBufferLists+0x1d6
    fffff880`08235860 fffff880`05187108 : fffffa80`05d39000 fffffa80`05fac140 fffffa80`05d39610 00000000`00000000 : ndis!NdisMIndicateReceiveNetBufferLists+0xc1
    fffff880`082358b0 fffffa80`05d39000 : fffffa80`05fac140 fffffa80`05d39610 00000000`00000000 00000000`00000001 : Rt64win7+0x16108
    fffff880`082358b8 fffffa80`05fac140 : fffffa80`05d39610 00000000`00000000 00000000`00000001 fffffa80`05d39610 : 0xfffffa80`05d39000
    fffff880`082358c0 fffffa80`05d39610 : 00000000`00000000 00000000`00000001 fffffa80`05d39610 00000000`02ae0000 : 0xfffffa80`05fac140
    fffff880`082358c8 00000000`00000000 : 00000000`00000001 fffffa80`05d39610 00000000`02ae0000 00000001`00000001 : 0xfffffa80`05d39610
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    Rt64win7+16108
    fffff880`05187108 ??              ???
    
    SYMBOL_STACK_INDEX:  10
    
    SYMBOL_NAME:  Rt64win7+16108
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: Rt64win7
    
    IMAGE_NAME:  Rt64win7.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4d8750a0
    
    FAILURE_BUCKET_ID:  X64_0xD1_VRF_Rt64win7+16108
    
    BUCKET_ID:  X64_0xD1_VRF_Rt64win7+16108
    
    Followup: MachineOwner
    ---------
      My Computer


  3. Posts : 20
    windows 7 ultimate 64bit
    Thread Starter
       #3

    Ok did all u told me to do,thanks man

    Hopefully i wont see anything blue again...lol
      My Computer


  4. Posts : 20
    windows 7 ultimate 64bit
    Thread Starter
       #4

    hmm well, another blue screen

    whats the problem now pls

    Attachment 164778
      My Computer


  5. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #5

    Your PAC7302 VGA SoC PC-Camera driver needs to be updated

    Latest crash was caused the AMD Radeon driver
    Reinstall the AMD driver(if not done yet) and stop any overclocking if any
      My Computer


  6. Posts : 20
    windows 7 ultimate 64bit
    Thread Starter
       #6

    hmm well i already updated the AMD driver from before and i havent done any overclocking

    i also updated this PAC7302 VGA SoC PC-Camera driver

    meh i have a feeling ill get more blue screens
      My Computer


  7. Posts : 20
    windows 7 ultimate 64bit
    Thread Starter
       #7

    Attachment 165061

    what now

    Btw if its the AMD driver again then what am i supposed to do? the card isnt overclocked and i have the latest drivers, i also installed the card in another pc and it worked fine, the guy had no blue screens at all for days, why does this happen to me and not to him :S
      My Computer


  8. Posts : 20
    windows 7 ultimate 64bit
    Thread Starter
       #8

    any news guys? :P
      My Computer


  9. Posts : 20
    windows 7 ultimate 64bit
    Thread Starter
       #9

    And another one Attachment 165401

    This is getting annoying
      My Computer


  10. Posts : 12,177
    Windows 7 Ult x64 - SP1/ Windows 8 Pro x64
       #10

    Can you zip and attach all the files requested?
    Blue Screen of Death (BSOD) Posting Instructions
    The other information will help us to find the cause of your system crashes.

    Fill in your system specs, this will also help us.


    What is the AMD Radeon driver version?
    Try installing an older driver version and don't install CCC, just the basic driver.

    Crash code is: STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL
    Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility
    Possible Cause
    This bug check is issued if paged memory (or invalid memory) is accessed when the IRQL is too high.
    The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, or BIOS.
    If you encounter bug check 0xA while upgrading to a later version of Windows, this error might be caused by a device driver, a system service, a virus scanner, or a backup tool that is incompatible with the new version.


    Code:
     
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    IRQL_NOT_LESS_OR_EQUAL (a)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: fffffa8047b31438, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, bitfield :
     bit 0 : value 0 = read operation, 1 = write operation
     bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff80002a86dbe, address which referenced memory
    Debugging Details:
    ------------------
     
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cb0100
     fffffa8047b31438 
    CURRENT_IRQL:  2
    FAULTING_IP: 
    nt!KiDeferredReadyThread+9e
    fffff800`02a86dbe 80bff10100000e  cmp     byte ptr [rdi+1F1h],0Eh
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0xA
    PROCESS_NAME:  Wow.exe
    TRAP_FRAME:  fffff88003122600 -- (.trap 0xfffff88003122600)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000001 rbx=0000000000000000 rcx=fffffa80060a8060
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002a86dbe rsp=fffff88003122790 rbp=fffffa8006098b30
     r8=fffff880009eb301  r9=0000000000000002 r10=fffff80002a01000
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    nt!KiDeferredReadyThread+0x9e:
    fffff800`02a86dbe 80bff10100000e  cmp     byte ptr [rdi+1F1h],0Eh ds:b430:00000000`000001f1=??
    Resetting default scope
    LAST_CONTROL_TRANSFER:  from fffff80002a802a9 to fffff80002a80d00
    STACK_TEXT:  
    fffff880`031224b8 fffff800`02a802a9 : 00000000`0000000a fffffa80`47b31438 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    fffff880`031224c0 fffff800`02a7ef20 : fffffa80`051d11a0 fffff880`04489960 fffffa80`051d1050 fffffa80`060a8100 : nt!KiBugCheckDispatch+0x69
    fffff880`03122600 fffff800`02a86dbe : fffff800`02bf3e80 fffffa80`03c133a0 fffffa80`03bdd290 fffffa80`051d1050 : nt!KiPageFault+0x260
    fffff880`03122790 fffff800`02a8c587 : fffffa80`060a8120 fffffa80`060a8168 fffffa80`060a8168 00000000`00000000 : nt!KiDeferredReadyThread+0x9e
    fffff880`03122810 fffff800`02a8c3de : 0000000b`91a1e6a3 fffff880`03122e88 00000000`0004dc2e fffff880`009ebb48 : nt!KiProcessExpiredTimerList+0x157
    fffff880`03122e60 fffff800`02a8c1c7 : fffff880`009e91c1 fffffa80`0004dc2e fffffa80`051d1d40 00000000`0000002e : nt!KiTimerExpiration+0x1be
    fffff880`03122f00 fffff800`02a83765 : 00001200`00002009 fffffa80`04169350 00000000`00000000 fffff800`02b98b90 : nt!KiRetireDpcList+0x277
    fffff880`03122fb0 fffff800`02a8357c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KyRetireDpcList+0x5
    fffff880`0895ebe0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue
     
    STACK_COMMAND:  kb
    FOLLOWUP_IP: 
    nt!KiDeferredReadyThread+9e
    fffff800`02a86dbe 80bff10100000e  cmp     byte ptr [rdi+1F1h],0Eh
    SYMBOL_STACK_INDEX:  3
    SYMBOL_NAME:  nt!KiDeferredReadyThread+9e
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: nt
    IMAGE_NAME:  ntkrnlmp.exe
    DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fdd5b
    FAILURE_BUCKET_ID:  X64_0xA_nt!KiDeferredReadyThread+9e
    BUCKET_ID:  X64_0xA_nt!KiDeferredReadyThread+9e
    Followup: MachineOwner
    ---------
    With the information requested above we can proceed with analysis.
    Last edited by Dave76; 17 Jul 2011 at 07:58.
      My Computer


 
Page 1 of 4 123 ... LastLast

  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 07:10.
Find Us