Windows 7 Home (x64) BSOD RRS feed

  • Question

  • I have recently been having a lot of problems with BSOD's on a new system I've set up.

    Here is a current listing of my hardware:

    Gigabyte GA-880GM-UD2H (Rev 1.4)   - Latest bios version F8

    AMD Phenom II X4 955  - Stock settings

    GEIL DDR3 PC3-10700F (667MHz)  - Im not sure about that "10700F" but that's what CPUD says... This RAM has been through 10+ Memtests, and the Windows Memory Integrity Check, and in all cases came out clean.

     NVIDIA GeForce 8800GT  - Stock settings, latest drivers

    When I initially set up the system I let Windows run through its' natural update procedure. The system started Blue Screening, so I updated the gfx drivers from the NVIDIA website. The BSOD's continued so I downloaded and installed the chipset, audio, and LAN drivers from the Gigabyte website for my specific motherboard. The BSOD's continued to occur, seemingly randomly. I've tried to use the Microsoft debugging tool, but to be honest I've not had any experience with it and can't see anything conclusive glaring me in the face. 

    Below is a link to a RAR of my BSOD's, hopefully one of you guys can take a look for me and point me in the right direction.


    Thanks in advance,




    Tuesday, April 5, 2011 5:02 PM


  • Analyzed dump file: 040411-19468-01.dmp

    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    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.
    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) - Op ration r ussie.
    00000000`00000000 ??              ???
    EXCEPTION_PARAMETER1:  0000000000000000
    EXCEPTION_PARAMETER2:  0000000000000000
    PROCESS_NAME:  System
    EXCEPTION_RECORD:  fffff88007856608 -- (.exr 0xfffff88007856608)
    ExceptionAddress: fffff88000dbc9ae (ataport!IdePortPdoDispatch+0x000000000000006a)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000001
       Parameter[1]: 0000000000100005
    Attempt to write to address 0000000000100005
    TRAP_FRAME:  fffff880078566b0 -- (.trap 0xfffff880078566b0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffffa8003b291a0 rbx=0000000000000000 rcx=fffffa8003b4f101
    rdx=0000000000100000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff88000dbc9ae rsp=fffff88007856840 rbp=0000000000100000
     r8=fffff88007856878  r9=0000000000000001 r10=0000000000000000
    r11=fffff880078567d0 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    fffff880`00dbc9ae 884d05          mov     byte ptr [rbp+5],cl ss:0018:00000000`00100005=??
    Resetting default scope
    LAST_CONTROL_TRANSFER:  from fffff80002ed4ffe to fffff80002edd610
    fffff880`078556e8 fffff800`02ed4ffe : 00000000`00000000 00000000`00000000 00000000`00000000 fffff800`02f3425b : nt!KeBugCheck
    fffff880`078556f0 fffff800`02f08f6d : fffff800`030e2afc fffff800`030240d8 fffff800`02e5d000 fffff880`07856608 : nt!KiKernelCalloutExceptionHandler+0xe
    fffff880`07855720 fffff800`02f07d45 : fffff800`030240d0 fffff880`07855798 fffff880`07856608 fffff800`02e5d000 : nt!RtlpExecuteHandlerForException+0xd
    fffff880`07855750 fffff800`02f18dc1 : fffff880`07856608 fffff880`07855e60 fffff880`00000000 fffffa80`0444ac10 : nt!RtlDispatchException+0x415
    fffff880`07855e30 fffff800`02edccc2 : fffff880`07856608 fffffa80`03b4f060 fffff880`078566b0 fffffa80`03b4f1b0 : nt!KiDispatchException+0x135
    fffff880`078564d0 fffff800`02edb83a : 00000000`00000001 00000000`00100005 00000000`00000000 fffffa80`03b4f060 : nt!KiExceptionDispatch+0xc2
    fffff880`078566b0 fffff880`00dbc9ae : fffffa80`03b4f060 fffffa80`0444adb8 fffffa80`03a292d0 fffff880`00f2704e : nt!KiPageFault+0x23a
    fffff880`07856840 fffff880`00db84ee : fffffa80`0444ac10 00000000`00000000 fffffa80`03b23d30 fffffa80`0444ac10 : ataport!IdePortPdoDispatch+0x6a
    fffff880`07856870 fffff880`00f217a7 : fffffa80`0444ac10 00000000`00000702 fffff8a0`018f5bc0 00000000`00000008 : ataport!IdePortDispatch+0x16
    fffff880`078568a0 fffff880`00f29789 : fffff880`00f47b50 fffff8a0`018f5a90 fffffa80`04a47010 fffffa80`0444adb8 : ACPI!ACPIDispatchForwardIrp+0x37
    fffff880`078568d0 fffff880`00f21a3f : fffff880`00f47b50 fffffa80`03a292d0 fffffa80`0444ac10 fffffa80`04a451b0 : ACPI!ACPIIrpDispatchDeviceControl+0x75
    fffff880`07856900 fffff880`01963ecf : fffffa80`04a451b0 fffffa80`04a451b0 fffffa80`04a451b0 fffffa80`04a451b0 : ACPI!ACPIDispatchIrp+0x12b
    fffff880`07856980 fffff880`01953903 : fffffa80`04a451b0 fffffa80`0444ac10 fffffa80`0444ae48 fffff880`00fc42ce : CLASSPNP!ClassInternalIoControl+0x9f
    fffff880`078569b0 fffff880`00fc10af : fffffa80`0444ac10 00000000`00000100 fffffa80`0444ae48 fffff8a0`0015b5c0 : CLASSPNP!ClassReadWrite+0x63
    fffff880`07856a00 fffff880`00fd618c : fffffa80`04a47cd0 fffffa80`0444ac10 fffffa80`0444ac10 fffff880`061eb4a0 : partmgr!PmGlobalDispatch+0x9f
    fffff880`07856a30 fffff880`019032bf : 00000000`00000100 fffffa80`048dcb90 fffffa80`0444ac10 fffffa80`03e62010 : volmgr!VmReadWrite+0x11c
    fffff880`07856a70 fffff880`0190353c : fffffa80`048dcb90 00000000`035b8f89 00000000`035b8e89 fffff880`018b6083 : fvevol!FveReadWrite+0x47
    fffff880`07856ab0 fffff880`01903593 : fffffa80`048d7b10 00000000`000a0045 00000000`00000302 00000000`00000000 : fvevol!FveFilterRundownReadWrite+0x1dc
    fffff880`07856b10 fffff880`018b70c5 : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00000021 : fvevol!FveFilterRundownWrite+0x2f
    fffff880`07856b40 fffff880`018b6405 : fffffa80`048d7b10 fffffa80`0444ac10 00000000`00000000 00000000`00000000 : rdyboost!SmdProcessReadWrite+0xc8d
    fffff880`07856cb0 fffff880`0185a108 : fffffa80`0444ac10 fffff880`03193090 fffffa80`0444af68 00000000`00000000 : rdyboost!SmdDispatchReadWrite+0xd9
    fffff880`07856ce0 fffff880`0101a39a : fffff880`03193090 fffffa80`03a8c040 fffff880`03192fb8 fffffa80`0664bb60 : volsnap!VolsnapWriteFilter+0xf8
    fffff880`07856d30 fffff800`02ed5157 : fffff880`061eb690 00000000`00296230 00000000`776c45c0 00000000`00000000 : Ntfs!NtfsStorageDriverCallout+0x16
    fffff880`07856d60 fffff800`02ed5111 : 00000000`00000000 00000000`00000000 fffff880`07857000 fffff800`02eea242 : nt!KxSwitchKernelStackCallout+0x27
    fffff880`03192e80 fffff800`02eea242 : fffff880`03193040 00000000`00000002 fffff880`031933a0 fffff8a0`08fff140 : nt!KiSwitchKernelStackContinue
    fffff880`03192ea0 fffff880`01019f09 : fffff880`0101a384 00000000`0e500000 fffff6fc`00100000 00000000`00000000 : nt!KeExpandKernelStackAndCalloutEx+0x2a2
    fffff880`03192f80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : Ntfs!NtfsMultipleAsync+0xa9
    fffff880`00dbc9ae 884d05          mov     byte ptr [rbp+5],cl
    SYMBOL_NAME:  ataport!IdePortPdoDispatch+6a
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: ataport
    IMAGE_NAME:  ataport.SYS
    FAILURE_BUCKET_ID:  X64_0x1E_ataport!IdePortPdoDispatch+6a
    BUCKET_ID:  X64_0x1E_ataport!IdePortPdoDispatch+6a
    Followup: MachineOwner
    0: kd> lmvm ataport
    start             end                 module name
    fffff880`00db1000 fffff880`00ddb000   ataport    (pdb symbols)          c:\symbols\ataport.pdb\2DB8ECA26E384BE1AE9E0FD314B65FA11\ataport.pdb
        Loaded symbol image file: ataport.SYS
        Mapped memory image file: c:\symbols\ataport.SYS\4CE792932a000\ataport.SYS
        Image path: ataport.SYS
        Image name: ataport.SYS
        Timestamp:        Sat Nov 20 10:19:15 2010 (4CE79293)
        CheckSum:         000287EF
        ImageSize:        0002A000
        File version:     6.1.7601.17514
        Product version:  6.1.7601.17514
        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.7601.17514
        FileVersion:      6.1.7601.17514 (win7sp1_rtm.101119-1850)
        FileDescription:  ATAPI Driver Extension
        LegalCopyright:   © Microsoft Corporation. All rights reserved.
    I see that you have SP1 installed so I don't have a hotfix to suggest because it should be aklready instaled.
    Please have a look to this Microsoft article about Bug Check Code 0x1E: http://msdn.microsoft.com/en-us/library/ff557408(VS.85).aspx
    Try to update all your drivers, firmware, BIOS ...
    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

    • Proposed as answer by Arthur Xie Thursday, April 7, 2011 9:06 AM
    • Marked as answer by Arthur Xie Wednesday, April 20, 2011 6:30 AM
    Tuesday, April 5, 2011 10:18 PM