locked
bluescreen issues window 7 RRS feed

Answers

  • *******************************************************************************
    *                                                                             *
    *                        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: aaaa6870, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000000, value 0 = read operation, 1 = write operation
    Arg4: 8c4a0fb6, address which referenced memory
    Debugging Details:
    ------------------
    READ_ADDRESS: GetPointerFromAddress: unable to read from 831a4700
    Unable to read MiSystemVaType memory at 831840c0
     aaaa6870 
    CURRENT_IRQL:  2
    FAULTING_IP: 
    ataport!IdeLogCrbActive+94
    8c4a0fb6 a5              movs    dword ptr es:[edi],dword ptr [esi]
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0xD1
    PROCESS_NAME:  System
    TRAP_FRAME:  80de19ec -- (.trap 0xffffffff80de19ec)
    ErrCode = 00000000
    eax=8832c008 ebx=868eac60 ecx=aaaa6840 edx=00000000 esi=aaaa6870 edi=868eac60
    eip=8c4a0fb6 esp=80de1a60 ebp=80de1a6c iopl=0         nv up ei ng nz na po nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010282
    ataport!IdeLogCrbActive+0x94:
    8c4a0fb6 a5              movs    dword ptr es:[edi],dword ptr [esi] es:0023:868eac60=???????? ds:0023:aaaa6870=????????
    Resetting default scope
    LAST_CONTROL_TRANSFER:  from 8c4a0fb6 to 8307db3b
    STACK_TEXT:  
    80de19ec 8c4a0fb6 badb0d00 00000000 85de3f40 nt!KiTrap0E+0x2cf
    80de1a6c 8c4a90e8 8832c008 85c73390 00000000 ataport!IdeLogCrbActive+0x94
    80de1a90 8c473074 8832c008 80de1ac8 83012a2e ataport!IdeStartIoCallBack+0x5c
    80de1a9c 83012a2e 868ce680 00000000 8832c064 PCIIDEX!BmReceiveScatterGatherList+0x1e
    80de1ac8 8c473199 8832c064 868ce680 85c73370 hal!HalBuildScatterGatherList+0x1ba
    80de1b04 8c4a8b46 868ce738 8832c008 8832c000 PCIIDEX!BmSetup+0x3d
    80de1b20 8c4a9041 85bac0e0 8832c000 8832c008 ataport!IdePortSetupScatterGatherList+0x2a
    80de1b38 8c4a7a12 85bac0e0 8832c008 85f734fa ataport!IdeDispatchChannelRequest+0x59
    80de1b50 8c4a7c6a 85bac0e0 8832c008 85f73270 ataport!IdeStartChannelRequest+0x42
    80de1b64 8c4a92a0 85baa6c8 85f73270 85bac0e0 ataport!IdeStartNextDeviceRequest+0x22
    80de1bd8 8c4a966b 85bac0e0 85f73270 86855008 ataport!IdeProcessCompletedRequests+0xd8
    80de1c2c 83a2b894 85bac09c 85bac028 00000000 ataport!IdePortCompletionDpc+0xab
    WARNING: Stack unwind information not available. Following frames may be wrong.
    80de1c78 8309a775 85bac09c 85bac028 00000000 sptd+0x11894
    80de1cd4 8309a5d8 80dc5120 80dca800 00000000 nt!KiExecuteAllDpcs+0xf9
    80de1d20 8309a3f8 00000000 0000000e 85b7e160 nt!KiRetireDpcList+0xd5
    80de1d24 00000000 0000000e 85b7e160 85b7e160 nt!KiIdleLoop+0x38
    STACK_COMMAND:  kb
    FOLLOWUP_IP: 
    ataport!IdeLogCrbActive+94
    8c4a0fb6 a5              movs    dword ptr es:[edi],dword ptr [esi]
    SYMBOL_STACK_INDEX:  1
    SYMBOL_NAME:  ataport!IdeLogCrbActive+94
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: ataport
    IMAGE_NAME:  ataport.SYS
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bbf16
    FAILURE_BUCKET_ID:  0xD1_ataport!IdeLogCrbActive+94
    BUCKET_ID:  0xD1_ataport!IdeLogCrbActive+94
    Followup: MachineOwner
    ---------
    1: kd> lmvm ataport
    start    end        module name
    8c49f000 8c4c2000   ataport    (pdb symbols)          downstreamstore\ataport.pdb\7AC193B7BDE242239273B5CD16763D751\ataport.pdb
        Loaded symbol image file: ataport.SYS
        Mapped memory image file: DownstreamStore\ataport.SYS\4A5BBF1623000\ataport.SYS
        Image path: \SystemRoot\system32\DRIVERS\ataport.SYS
        Image name: ataport.SYS
        Timestamp:        Tue Jul 14 01:11:18 2009 (4A5BBF16)
        CheckSum:         0002F425
        ImageSize:        00023000
        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:     0000.04b0
        CompanyName:      Microsoft Corporation
        ProductName:      Microsoft® Windows® Operating System
        InternalName:     ataport.sys
        OriginalFilename: ataport.sys
        ProductVersion:   6.1.7600.16385
        FileVersion:      6.1.7600.16385 (win7_rtm.090713-1255)
        FileDescription:  ATAPI Driver Extension
        LegalCopyright:   © Microsoft Corporation. All rights reserved.
    __________________________________________________________________________
    Check your disks cables and run chkdsk /r /f and sfc /scannow. If this does not help, contact your manufacturer Technical Support.

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

    Microsoft Student Partner
    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

    • Marked as answer by Miya Yao Friday, May 6, 2011 7:12 AM
    Wednesday, April 27, 2011 9:53 AM
  • Thank you for replying but i find it quite hard to understand all these technical terms, right now ill run chkdsk /r /f and sfc /scannow, any instruction would be nice

    This is the only part of his post you need to read :)

    Check your disks cables and run chkdsk /r /f and sfc /scannow. If this does not help, contact your manufacturer Technical Support.


    Oops forgot to add instructions :)

    to use check disk you need to open a command prompt click start and type cmd in the text box at bottom of menu. This will open the command window in "non administrator mode" then type the chkdsk commands just like MrX stated. you will be told you can't run it in that mode would you like to run it on the next start up type Y then reboot your system and it will take over from there.

    The other command he told you to run can be run from that same command prompt but does not require a reboot to run it.

    • Marked as answer by Miya Yao Friday, May 6, 2011 7:12 AM
    Friday, April 29, 2011 6:43 PM

All replies

  • *******************************************************************************
    *                                                                             *
    *                        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: aaaa6870, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000000, value 0 = read operation, 1 = write operation
    Arg4: 8c4a0fb6, address which referenced memory
    Debugging Details:
    ------------------
    READ_ADDRESS: GetPointerFromAddress: unable to read from 831a4700
    Unable to read MiSystemVaType memory at 831840c0
     aaaa6870 
    CURRENT_IRQL:  2
    FAULTING_IP: 
    ataport!IdeLogCrbActive+94
    8c4a0fb6 a5              movs    dword ptr es:[edi],dword ptr [esi]
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0xD1
    PROCESS_NAME:  System
    TRAP_FRAME:  80de19ec -- (.trap 0xffffffff80de19ec)
    ErrCode = 00000000
    eax=8832c008 ebx=868eac60 ecx=aaaa6840 edx=00000000 esi=aaaa6870 edi=868eac60
    eip=8c4a0fb6 esp=80de1a60 ebp=80de1a6c iopl=0         nv up ei ng nz na po nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010282
    ataport!IdeLogCrbActive+0x94:
    8c4a0fb6 a5              movs    dword ptr es:[edi],dword ptr [esi] es:0023:868eac60=???????? ds:0023:aaaa6870=????????
    Resetting default scope
    LAST_CONTROL_TRANSFER:  from 8c4a0fb6 to 8307db3b
    STACK_TEXT:  
    80de19ec 8c4a0fb6 badb0d00 00000000 85de3f40 nt!KiTrap0E+0x2cf
    80de1a6c 8c4a90e8 8832c008 85c73390 00000000 ataport!IdeLogCrbActive+0x94
    80de1a90 8c473074 8832c008 80de1ac8 83012a2e ataport!IdeStartIoCallBack+0x5c
    80de1a9c 83012a2e 868ce680 00000000 8832c064 PCIIDEX!BmReceiveScatterGatherList+0x1e
    80de1ac8 8c473199 8832c064 868ce680 85c73370 hal!HalBuildScatterGatherList+0x1ba
    80de1b04 8c4a8b46 868ce738 8832c008 8832c000 PCIIDEX!BmSetup+0x3d
    80de1b20 8c4a9041 85bac0e0 8832c000 8832c008 ataport!IdePortSetupScatterGatherList+0x2a
    80de1b38 8c4a7a12 85bac0e0 8832c008 85f734fa ataport!IdeDispatchChannelRequest+0x59
    80de1b50 8c4a7c6a 85bac0e0 8832c008 85f73270 ataport!IdeStartChannelRequest+0x42
    80de1b64 8c4a92a0 85baa6c8 85f73270 85bac0e0 ataport!IdeStartNextDeviceRequest+0x22
    80de1bd8 8c4a966b 85bac0e0 85f73270 86855008 ataport!IdeProcessCompletedRequests+0xd8
    80de1c2c 83a2b894 85bac09c 85bac028 00000000 ataport!IdePortCompletionDpc+0xab
    WARNING: Stack unwind information not available. Following frames may be wrong.
    80de1c78 8309a775 85bac09c 85bac028 00000000 sptd+0x11894
    80de1cd4 8309a5d8 80dc5120 80dca800 00000000 nt!KiExecuteAllDpcs+0xf9
    80de1d20 8309a3f8 00000000 0000000e 85b7e160 nt!KiRetireDpcList+0xd5
    80de1d24 00000000 0000000e 85b7e160 85b7e160 nt!KiIdleLoop+0x38
    STACK_COMMAND:  kb
    FOLLOWUP_IP: 
    ataport!IdeLogCrbActive+94
    8c4a0fb6 a5              movs    dword ptr es:[edi],dword ptr [esi]
    SYMBOL_STACK_INDEX:  1
    SYMBOL_NAME:  ataport!IdeLogCrbActive+94
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: ataport
    IMAGE_NAME:  ataport.SYS
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bbf16
    FAILURE_BUCKET_ID:  0xD1_ataport!IdeLogCrbActive+94
    BUCKET_ID:  0xD1_ataport!IdeLogCrbActive+94
    Followup: MachineOwner
    ---------
    1: kd> lmvm ataport
    start    end        module name
    8c49f000 8c4c2000   ataport    (pdb symbols)          downstreamstore\ataport.pdb\7AC193B7BDE242239273B5CD16763D751\ataport.pdb
        Loaded symbol image file: ataport.SYS
        Mapped memory image file: DownstreamStore\ataport.SYS\4A5BBF1623000\ataport.SYS
        Image path: \SystemRoot\system32\DRIVERS\ataport.SYS
        Image name: ataport.SYS
        Timestamp:        Tue Jul 14 01:11:18 2009 (4A5BBF16)
        CheckSum:         0002F425
        ImageSize:        00023000
        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:     0000.04b0
        CompanyName:      Microsoft Corporation
        ProductName:      Microsoft® Windows® Operating System
        InternalName:     ataport.sys
        OriginalFilename: ataport.sys
        ProductVersion:   6.1.7600.16385
        FileVersion:      6.1.7600.16385 (win7_rtm.090713-1255)
        FileDescription:  ATAPI Driver Extension
        LegalCopyright:   © Microsoft Corporation. All rights reserved.
    __________________________________________________________________________
    Check your disks cables and run chkdsk /r /f and sfc /scannow. If this does not help, contact your manufacturer Technical Support.

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

    Microsoft Student Partner
    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

    • Marked as answer by Miya Yao Friday, May 6, 2011 7:12 AM
    Wednesday, April 27, 2011 9:53 AM
  • Thank you for replying but i find it quite hard to understand all these technical terms, right now ill run chkdsk /r /f and sfc /scannow, any instruction would be nice

    Wednesday, April 27, 2011 12:38 PM
  • Thank you for replying but i find it quite hard to understand all these technical terms, right now ill run chkdsk /r /f and sfc /scannow, any instruction would be nice

    This is the only part of his post you need to read :)

    Check your disks cables and run chkdsk /r /f and sfc /scannow. If this does not help, contact your manufacturer Technical Support.


    Oops forgot to add instructions :)

    to use check disk you need to open a command prompt click start and type cmd in the text box at bottom of menu. This will open the command window in "non administrator mode" then type the chkdsk commands just like MrX stated. you will be told you can't run it in that mode would you like to run it on the next start up type Y then reboot your system and it will take over from there.

    The other command he told you to run can be run from that same command prompt but does not require a reboot to run it.

    • Marked as answer by Miya Yao Friday, May 6, 2011 7:12 AM
    Friday, April 29, 2011 6:43 PM