bsod in 1 day using windows 7


  1. Posts : 2
    windows 7 ultimate x64
       #1

    bsod in 1 day using windows 7


    hi, I have windows 7 and it was working well, so I upgraded to windows 10, and was having some problems with ALL my hard drives, external and internal...couldn't tranfer big files, that it would crash or bsod would appear, and if I tried to tranfer file per file, the hard drive would disconnect and reconnect alone...even on 2.0 port, I couldn't tranfer all files together... so I get back to windows 7, and in the first day I got this bsod while I was downloading a big file to my 1tb hard drive...it is pretty clear to me that I have a problem with this hard drive, but I don't think it is a faulty hard drive, because ALL hard drives that I have are giving me some bsod or random freezing screens. I think something is causing problem to them, any driver, or memory, or energy, I really don't know, but I think this bsod could be the answer...help me please

    here is the report that windbg gave me

    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Windows\Minidump\081715-21075-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: symsrv*symsrv.dll*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows 7 Kernel Version 7600 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.17795.amd64fre.win7_gdr.150318-1623
    Machine Name:
    Kernel base = 0xfffff800`02a5f000 PsLoadedModuleList = 0xfffff800`02c9bed0
    Debug session time: Mon Aug 17 06:51:29.499 2015 (UTC - 3:00)
    System Uptime: 0 days 0:16:28.044
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ................
    Loading User Symbols
    Loading unloaded module list
    ......
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck D1, {2, d, 8, 2}

    Probably caused by : amdppm.sys ( amdppm!C1Halt+2 )

    Followup: MachineOwner
    ---------

    3: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    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: 0000000000000002, memory referenced
    Arg2: 000000000000000d, IRQL
    Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
    Arg4: 0000000000000002, address which referenced memory

    Debugging Details:
    ------------------


    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d060e0
    0000000000000002

    CURRENT_IRQL: d

    FAULTING_IP:
    +6366636330383333
    00000000`00000002 ?? ???

    PROCESS_NAME: System

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0xD1

    TRAP_FRAME: fffff88002dfd940 -- (.trap 0xfffff88002dfd940)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=5ea9e19430486700 rbx=0000000000000000 rcx=0000000000000011
    rdx=0000000000019cea rsi=0000000000000000 rdi=0000000000000000
    rip=0000000000000002 rsp=fffff88002dfdad8 rbp=fffff88002dfdb80
    r8=000000000001eb73 r9=0000000000000000 r10=0000000000023760
    r11=00000000001f0001 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei pl zr na po nc
    00000000`00000002 ?? ???
    Resetting default scope

    LAST_CONTROL_TRANSFER: from fffff80002acdda9 to fffff80002ace840

    FAILED_INSTRUCTION_ADDRESS:
    +6366636330383333
    00000000`00000002 ?? ???

    STACK_TEXT:
    fffff880`02dfd7f8 fffff800`02acdda9 : 00000000`0000000a 00000000`00000002 00000000`0000000d 00000000`00000008 : nt!KeBugCheckEx
    fffff880`02dfd800 fffff800`02acca20 : fffffa80`0e3f5010 00000000`00000000 00000000`00000000 00000000`00000001 : nt!KiBugCheckDispatch+0x69
    fffff880`02dfd940 00000000`00000002 : ffff2401`00000000 00000000`00002711 00000000`00000001 fffffa80`0a3e6050 : nt!KiPageFault+0x260
    fffff880`02dfdad8 ffff2401`00000000 : 00000000`00002711 00000000`00000001 fffffa80`0a3e6050 fffff800`02adb441 : 0x2
    fffff880`02dfdae0 00000000`00002711 : 00000000`00000001 fffffa80`0a3e6050 fffff800`02adb441 00000000`00000000 : 0xffff2401`00000000
    fffff880`02dfdae8 00000000`00000001 : fffffa80`0a3e6050 fffff800`02adb441 00000000`00000000 fffff880`02dfdb80 : 0x2711
    fffff880`02dfdaf0 fffffa80`0a3e6050 : fffff800`02adb441 00000000`00000000 fffff880`02dfdb80 fffff880`02dd5180 : 0x1
    fffff880`02dfdaf8 fffff800`02adb441 : 00000000`00000000 fffff880`02dfdb80 fffff880`02dd5180 00000000`00000001 : 0xfffffa80`0a3e6050
    fffff880`02dfdb00 fffff880`131c27f2 : fffff800`02adc2ea 00000000`00340b36 fffffa80`0a3e6788 fffff880`02de00c0 : nt!KiSecondaryClockInterrupt+0x131
    fffff880`02dfdc98 fffff800`02adc2ea : 00000000`00340b36 fffffa80`0a3e6788 fffff880`02de00c0 00000000`00000001 : amdppm!C1Halt+0x2
    fffff880`02dfdca0 fffff800`02ad6f6c : fffff880`02dd5180 fffff880`00000000 00000000`00000000 fffff880`043dc480 : nt!PoIdle+0x53a
    fffff880`02dfdd80 00000000`00000000 : fffff880`02dfe000 fffff880`02df8000 fffff880`02dfdd40 00000000`00000000 : nt!KiIdleLoop+0x2c


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    amdppm!C1Halt+2
    fffff880`131c27f2 c3 ret

    SYMBOL_STACK_INDEX: 9

    SYMBOL_NAME: amdppm!C1Halt+2

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: amdppm

    IMAGE_NAME: amdppm.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc0fd

    FAILURE_BUCKET_ID: X64_0xD1_CODE_AV_BAD_IP_amdppm!C1Halt+2

    BUCKET_ID: X64_0xD1_CODE_AV_BAD_IP_amdppm!C1Halt+2

    Followup: MachineOwner
    ---------

    3: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    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: 0000000000000002, memory referenced
    Arg2: 000000000000000d, IRQL
    Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
    Arg4: 0000000000000002, address which referenced memory

    Debugging Details:
    ------------------


    READ_ADDRESS: 0000000000000002

    CURRENT_IRQL: d

    FAULTING_IP:
    +6366636330383333
    00000000`00000002 ?? ???

    PROCESS_NAME: System

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0xD1

    TRAP_FRAME: fffff88002dfd940 -- (.trap 0xfffff88002dfd940)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=5ea9e19430486700 rbx=0000000000000000 rcx=0000000000000011
    rdx=0000000000019cea rsi=0000000000000000 rdi=0000000000000000
    rip=0000000000000002 rsp=fffff88002dfdad8 rbp=fffff88002dfdb80
    r8=000000000001eb73 r9=0000000000000000 r10=0000000000023760
    r11=00000000001f0001 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei pl zr na po nc
    00000000`00000002 ?? ???
    Resetting default scope

    LAST_CONTROL_TRANSFER: from fffff80002acdda9 to fffff80002ace840

    FAILED_INSTRUCTION_ADDRESS:
    +6366636330383333
    00000000`00000002 ?? ???

    STACK_TEXT:
    fffff880`02dfd7f8 fffff800`02acdda9 : 00000000`0000000a 00000000`00000002 00000000`0000000d 00000000`00000008 : nt!KeBugCheckEx
    fffff880`02dfd800 fffff800`02acca20 : fffffa80`0e3f5010 00000000`00000000 00000000`00000000 00000000`00000001 : nt!KiBugCheckDispatch+0x69
    fffff880`02dfd940 00000000`00000002 : ffff2401`00000000 00000000`00002711 00000000`00000001 fffffa80`0a3e6050 : nt!KiPageFault+0x260
    fffff880`02dfdad8 ffff2401`00000000 : 00000000`00002711 00000000`00000001 fffffa80`0a3e6050 fffff800`02adb441 : 0x2
    fffff880`02dfdae0 00000000`00002711 : 00000000`00000001 fffffa80`0a3e6050 fffff800`02adb441 00000000`00000000 : 0xffff2401`00000000
    fffff880`02dfdae8 00000000`00000001 : fffffa80`0a3e6050 fffff800`02adb441 00000000`00000000 fffff880`02dfdb80 : 0x2711
    fffff880`02dfdaf0 fffffa80`0a3e6050 : fffff800`02adb441 00000000`00000000 fffff880`02dfdb80 fffff880`02dd5180 : 0x1
    fffff880`02dfdaf8 fffff800`02adb441 : 00000000`00000000 fffff880`02dfdb80 fffff880`02dd5180 00000000`00000001 : 0xfffffa80`0a3e6050
    fffff880`02dfdb00 fffff880`131c27f2 : fffff800`02adc2ea 00000000`00340b36 fffffa80`0a3e6788 fffff880`02de00c0 : nt!KiSecondaryClockInterrupt+0x131
    fffff880`02dfdc98 fffff800`02adc2ea : 00000000`00340b36 fffffa80`0a3e6788 fffff880`02de00c0 00000000`00000001 : amdppm!C1Halt+0x2
    fffff880`02dfdca0 fffff800`02ad6f6c : fffff880`02dd5180 fffff880`00000000 00000000`00000000 fffff880`043dc480 : nt!PoIdle+0x53a
    fffff880`02dfdd80 00000000`00000000 : fffff880`02dfe000 fffff880`02df8000 fffff880`02dfdd40 00000000`00000000 : nt!KiIdleLoop+0x2c


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    amdppm!C1Halt+2
    fffff880`131c27f2 c3 ret

    SYMBOL_STACK_INDEX: 9

    SYMBOL_NAME: amdppm!C1Halt+2

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: amdppm

    IMAGE_NAME: amdppm.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc0fd

    FAILURE_BUCKET_ID: X64_0xD1_CODE_AV_BAD_IP_amdppm!C1Halt+2

    BUCKET_ID: X64_0xD1_CODE_AV_BAD_IP_amdppm!C1Halt+2

    Followup: MachineOwner
    ---------

    3: kd> lmvm amdppm
    start end module name
    fffff880`131bf000 fffff880`131d4000 amdppm (pdb symbols) c:\symbols\amdppm.pdb\AB154B73C6884E70807CA6407175368D1\amdppm.pdb
    Loaded symbol image file: amdppm.sys
    Mapped memory image file: c:\symbols\amdppm.sys\4A5BC0FD15000\amdppm.sys
    Image path: \SystemRoot\system32\DRIVERS\amdppm.sys
    Image name: amdppm.sys
    Timestamp: Mon Jul 13 20:19:25 2009 (4A5BC0FD)
    CheckSum: 0001EA42
    ImageSize: 00015000
    File version: 6.1.7600.16385
    Product version: 6.1.7600.16385
    File flags: 0 (Mask 3F)
    File OS: 40004 NT Win32
    File type: 3.7 Driver
    File date: 00000000.00000000
    Translations: 0409.04b0
    CompanyName: Microsoft Corporation
    ProductName: Microsoft® Windows® Operating System
    InternalName: amdppm.sys
    OriginalFilename: amdppm.sys
    ProductVersion: 6.1.7600.16385
    FileVersion: 6.1.7600.16385 (win7_rtm.090713-1255)
    FileDescription: Processor Device Driver
    LegalCopyright: © Microsoft Corporation. All rights reserved.
    3: kd> .trap 0xfffff88002dfd940
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=5ea9e19430486700 rbx=0000000000000000 rcx=0000000000000011
    rdx=0000000000019cea rsi=0000000000000000 rdi=0000000000000000
    rip=0000000000000002 rsp=fffff88002dfdad8 rbp=fffff88002dfdb80
    r8=000000000001eb73 r9=0000000000000000 r10=0000000000023760
    r11=00000000001f0001 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei pl zr na po nc
    00000000`00000002 ?? ???
      My Computer


  2. Posts : 205
    Windows 7 Home Premium
       #2

    May b u can install the drivers like usb3 or catalyst, that came with ur comp in win 10 ... for ne the drivers were in c:/windows/drivers
    N on another they were in c:/swsetup folder
      My Computer


  3. Posts : 2
    windows 7 ultimate x64
    Thread Starter
       #3

    they're already instaled
      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 05:08.
Find Us