BSOD - Probably caused by amdppm.sys?!

Page 1 of 2 12 LastLast

  1. Posts : 46
    Windows 7
       #1

    BSOD - Probably caused by amdppm.sys?!


    Code:
    Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Windows\Minidump\042710-24968-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 7600 (Service Pack 2) MP (4 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.20655.x86fre.win7_ldr.100226-1909
    Machine Name:
    Kernel base = 0x82c04000 PsLoadedModuleList = 0x82d4c810
    Debug session time: Tue Apr 27 21:38:34.876 2010 (UTC + 3:00)
    System Uptime: 0 days 0:16:08.220
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .....................................
    Loading User Symbols
    Loading unloaded module list
    .......
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck A, {f6397ac, 1c, 1, 82c6fb50}
    
    Probably caused by : amdppm.sys ( amdppm!C1Halt+4 )
    
    Followup: MachineOwner
    ---------
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        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: 0f6397ac, memory referenced
    Arg2: 0000001c, IRQL
    Arg3: 00000001, 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: 82c6fb50, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82d6c718
    Unable to read MiSystemVaType memory at 82d4c160
     0f6397ac 
    
    CURRENT_IRQL:  1c
    
    FAULTING_IP: 
    nt!KeAccumulateTicks+bf
    82c6fb50 8944242c        mov     dword ptr [esp+2Ch],eax
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    
    BUGCHECK_STR:  0xA
    
    PROCESS_NAME:  System
    
    TRAP_FRAME:  87b1cb34 -- (.trap 0xffffffff87b1cb34)
    ErrCode = 00000002
    eax=00000000 ebx=00004c4b ecx=00000002 edx=00000002 esi=87b00120 edi=0002625a
    eip=82c6fb50 esp=87b1cba8 ebp=87b1cbd8 iopl=0         nv up ei pl zr na pe nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
    nt!KeAccumulateTicks+0xbf:
    82c6fb50 8944242c        mov     dword ptr [esp+2Ch],eax ss:0010:87b1cbd4=00000002
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from 82c6fb50 to 82c4a7fb
    
    STACK_TEXT:  
    87b1cb34 82c6fb50 badb0d00 00000002 a4b5f464 nt!KiTrap0E+0x2cf
    87b1cbd8 82c6f322 00004c4b 00000000 0000f200 nt!KeAccumulateTicks+0xbf
    87b1cc18 83017430 8302ea02 000000d1 87b1cd20 nt!KeUpdateRunTime+0x145
    87b1cc18 8d2473f6 8302ea02 000000d1 87b1cd20 hal!HalpClockInterruptPn+0x158
    87b1cc98 82c89649 851bcd48 87b05800 87b00000 amdppm!C1Halt+0x4
    87b1cd20 82c6c00d 00000000 0000000e 65f71bef nt!PoIdle+0x538
    87b1cd24 00000000 0000000e 65f71bef ffffffff nt!KiIdleLoop+0xd
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    amdppm!C1Halt+4
    8d2473f6 c3              ret
    
    SYMBOL_STACK_INDEX:  4
    
    SYMBOL_NAME:  amdppm!C1Halt+4
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: amdppm
    
    IMAGE_NAME:  amdppm.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bbf07
    
    FAILURE_BUCKET_ID:  0xA_VRF_amdppm!C1Halt+4
    
    BUCKET_ID:  0xA_VRF_amdppm!C1Halt+4
    
    Followup: MachineOwner
    ---------
    How to solve what's the problem? BSOD happens when heavy stress, like encoding video, but I haven't installed anything new.
      My Computer


  2. Posts : 13,354
    Windows 7 Professional x64
       #2

    Hmm... could we have the actual dmp file? https://www.sevenforums.com/crash-loc...d-problem.html

    Check out usasma's notes on your bugcheck A: BSOD Index
      My Computer


  3. Posts : 46
    Windows 7
    Thread Starter
       #3

    Here's couple minidumps if that helps.

    RapidShare: 1-CLICK Web hosting - Easy Filehosting

    What tools should I use to find the faulty driver/device?
      My Computer


  4. Posts : 13,354
    Windows 7 Professional x64
       #4

    I suggest updating your chipset drivers and BIOS.

    The lack of any information on Google for the driver a98ymif7.sys concerns me. Download a copy of Malwarebytes and run a scan.
      My Computer


  5. Posts : 46
    Windows 7
    Thread Starter
       #5

    Okay, I'll do that and run Malware check. My BIOS drivers are the latest, but I just updated mobo drivers.

    Just out of curiosity, how did you find about a98ymif7.sys? My WindDbg analyze didn't tell anything about it...
      My Computer


  6. Posts : 13,354
    Windows 7 Professional x64
       #6

    I used the lmn command. Load up the dmp in your debugger and enter that in the box at the bottom.
      My Computer


  7. Posts : 46
    Windows 7
    Thread Starter
       #7

    Okay, thanks. Any other handy commands? :)

    I did run Malwarebytes through and it found couple trojan downloaders. I'm now running Spybot, since it has helped me couple of times before.

    Just got another BSOD a while ago and now it says that probably cause is hardware.

    Here's new minidump if you'd like to check it: RapidShare: 1-CLICK Web hosting - Easy Filehosting
      My Computer


  8. Posts : 46
    Windows 7
    Thread Starter
       #8

    I've now got few times new error saying that the cause is hardware.

    Here's minidump if somebody can take a look.
      My Computer


  9. Posts : 13,354
    Windows 7 Professional x64
       #9

    Hardware often means RAM or hard drive.

    Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder. Boot from the CD, and run at least 5 passes.

    HD Diagnostic
      My Computer


  10. Posts : 46
    Windows 7
    Thread Starter
       #10

    Already did, several passes and no problems.
      My Computer


 
Page 1 of 2 12 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 16:30.
Find Us