BSODs after system restore

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by ParanoidPlumber, May 7, 2011.

  1. ParanoidPlumber

    ParanoidPlumber New Member

    Joined:
    May 6, 2011
    Messages:
    44
    Likes Received:
    0
    I ran the computer with the video card removed and using on board graphics. Still having problems.

    Now I'm having terrible errors trying to startup the computer. Still a lot of blank/black screens. Many times the computer will crash and give a black screen.

    In Event Viewer I found an error: The driver detected a controller error on \Device\Ide\IdePort0.

    So I'm thinking this is the hard drive. I actually have noticed odd loud noises on startup.

    Although, none of the HD diagnostics I've run have shown anything wrong.
     
  2. cybercore

    cybercore New Member

    Joined:
    Jul 7, 2009
    Messages:
    15,823
    Likes Received:
    321

    This is the culprit, bad motherboard or ports messed up in the bios.

    Although if HDD or it's controller is really faulty, SMART will deffinitely show errors. Run HDD Scan and HD Tune again. Check HDD cabling. Re-flash bios.
     
  3. ParanoidPlumber

    ParanoidPlumber New Member

    Joined:
    May 6, 2011
    Messages:
    44
    Likes Received:
    0
    I'm scared to flash the BIOS because of how often the crashes are. The computer crashes frequently on startup and it is rare to keep the computer running for very long without a crash. Crashing while flashing the BIOS ruins the motherboard right? Is there a good way to deal with this?
     
  4. cybercore

    cybercore New Member

    Joined:
    Jul 7, 2009
    Messages:
    15,823
    Likes Received:
    321
    Can you attach your latest crash dumps? Are they the same as before, what stop messages are you receiving this time?

    ~~~~~~~~~~~

    Diagnose your hard drive with bootable media as is well outlined here:

    HD Diagnostic

    If the hard disk or hdd controller is faulty, the test will show up. Otherwise we'll have to exclude this probability from the list of suspects.

    Also, what was the result of running chkdsk /f ?
     
  5. ParanoidPlumber

    ParanoidPlumber New Member

    Joined:
    May 6, 2011
    Messages:
    44
    Likes Received:
    0
    All the HD tests and diagnostics I've run already found nothing wrong. HDD scan and HD tune ran with nothing found wrong again.

    It must be the motherboard or BIOS. This would explain the problems I have. I will be flashing BIOS very soon. Hopefully this solves everything.


    Where do I find the results for chkdsk?

    Edit: Ok, I found it now. It looks like nothing is wrong.
     

    Attached Files:

    #25 ParanoidPlumber, May 15, 2011
    Last edited: May 15, 2011
  6. ParanoidPlumber

    ParanoidPlumber New Member

    Joined:
    May 6, 2011
    Messages:
    44
    Likes Received:
    0
    Ok, I flashed a newer version of my BIOS. We'll see if this helps.
     
    #26 ParanoidPlumber, May 16, 2011
    Last edited: May 16, 2011
  7. kaos

    kaos Senior Member

    Joined:
    May 9, 2011
    Messages:
    1,747
    Likes Received:
    33
    Code:
    
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck A, {fffffa7ffffff3e0, 2, 1, fffff80002e9b841}
    
    Probably caused by : memory_corruption ( nt!MmZeroPageThread+3c4 )
    
    Followup: MachineOwner
    ---------
    
    0: 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: fffffa7ffffff3e0, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, 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: fffff80002e9b841, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80003103100
    fffffa7ffffff3e0 
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    nt!MmZeroPageThread+3c4
    fffff800`02e9b841 f0410fba6d1000  lock bts dword ptr [r13+10h],0
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xA
    
    PROCESS_NAME:  System
    
    TRAP_FRAME:  fffff880009a9a80 -- (.trap 0xfffff880009a9a80)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=000000000000003e rbx=0000000000000000 rcx=0000000000000000
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002e9b841 rsp=fffff880009a9c10 rbp=00000000000000ff
    r8=0000000000000000  r9=0000058000000000 r10=0000000000000002
    r11=000000000000000e r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na pe nc
    nt!MmZeroPageThread+0x3c4:
    fffff800`02e9b841 f0410fba6d1000  lock bts dword ptr [r13+10h],0 ds:db60:00000000`00000010=????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002ed32a9 to fffff80002ed3d00
    
    STACK_TEXT:  
    fffff880`009a9938 fffff800`02ed32a9 : 00000000`0000000a fffffa7f`fffff3e0 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
    fffff880`009a9940 fffff800`02ed1f20 : 00000000`00000000 00000000`00000000 00000000`00000000 ffffffff`ffffffbf : nt!KiBugCheckDispatch+0x69
    fffff880`009a9a80 fffff800`02e9b841 : fffffa80`03902800 00000000`000000ff 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
    fffff880`009a9c10 fffff800`0317032e : fffffa80`039edb60 00000000`00000080 fffffa80`039ed040 fffff800`02ec5659 : nt!MmZeroPageThread+0x3c4
    fffff880`009a9d40 fffff800`02ec5666 : fffff800`03046e80 fffffa80`039edb60 fffff800`03054cc0 3a413b04`8a411474 : nt!PspSystemThreadStartup+0x5a
    fffff880`009a9d80 00000000`00000000 : fffff880`009aa000 fffff880`009a4000 fffff880`009a99b0 00000000`00000000 : nt!KiStartSystemThread+0x16
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!MmZeroPageThread+3c4
    fffff800`02e9b841 f0410fba6d1000  lock bts dword ptr [r13+10h],0
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  nt!MmZeroPageThread+3c4
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fdd5b
    
    IMAGE_NAME:  memory_corruption
    
    FAILURE_BUCKET_ID:  X64_0xA_nt!MmZeroPageThread+3c4
    
    BUCKET_ID:  X64_0xA_nt!MmZeroPageThread+3c4
    
    Followup: MachineOwner
    ---------
    
    
    2ND FILE

    Code:
    
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 3B, {c0000005, fffff8800452fc60, fffff880082dad90, 0}
    
    Probably caused by : dxgmms1.sys ( dxgmms1!VidMmTerminateAllocation+144 )
    
    Followup: MachineOwner
    ---------
    
    2: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************
    
    SYSTEM_SERVICE_EXCEPTION (3b)
    An exception happened while executing a system service routine.
    Arguments:
    Arg1: 00000000c0000005, Exception code that caused the bugcheck
    Arg2: fffff8800452fc60, Address of the instruction which caused the bugcheck
    Arg3: fffff880082dad90, Address of the context record for the exception that caused the bugcheck
    Arg4: 0000000000000000, zero.
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    FAULTING_IP: 
    dxgmms1!VidMmTerminateAllocation+144
    fffff880`0452fc60 4c8ba938010000 mov r13,qword ptr [rcx+138h]
    
    CONTEXT: fffff880082dad90 -- (.cxr 0xfffff880082dad90)
    rax=fffff8a00972e430 rbx=fffffa8005a23000 rcx=000001290000010b
    rdx=0000000000000000 rsi=0000000000150000 rdi=fffff8a002ea7b40
    rip=fffff8800452fc60 rsp=fffff880082db770 rbp=fffffa8006506800
    r8=0000000000000000 r9=0000000000000000 r10=fffff88002f64a60
    r11=fffff880082db740 r12=fffff8a002ea7be0 r13=fffff88004458a08
    r14=0000000000000001 r15=0000000000000001
    iopl=0 nv up ei pl zr na po nc
    cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
    dxgmms1!VidMmTerminateAllocation+0x144:
    fffff880`0452fc60 4c8ba938010000 mov r13,qword ptr [rcx+138h] ds:002b:00000129`00000243=????????????????
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT: 1
    
    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
    
    BUGCHECK_STR: 0x3B
    
    PROCESS_NAME: dwm.exe
    
    CURRENT_IRQL: 0
    
    LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff8800452fc60
    
    STACK_TEXT: 
    fffff880`082db770 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VidMmTerminateAllocation+0x144
    
    
    FOLLOWUP_IP: 
    dxgmms1!VidMmTerminateAllocation+144
    fffff880`0452fc60 4c8ba938010000 mov r13,qword ptr [rcx+138h]
    
    SYMBOL_STACK_INDEX: 0
    
    SYMBOL_NAME: dxgmms1!VidMmTerminateAllocation+144
    
    FOLLOWUP_NAME: MachineOwner
    
    MODULE_NAME: dxgmms1
    
    IMAGE_NAME: dxgmms1.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP: 4ce799c1
    
    STACK_COMMAND: .cxr 0xfffff880082dad90 ; kb
    
    FAILURE_BUCKET_ID: X64_0x3B_dxgmms1!VidMmTerminateAllocation+144
    
    BUCKET_ID: X64_0x3B_dxgmms1!VidMmTerminateAllocation+144
    
    Followup: MachineOwner
    ---------
    
    3RD FILE

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 50, {fffff8c004d530c7, 1, fffff88004d530e4, 5}
    
    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
    
    Could not read faulting driver name
    Probably caused by : atikmdag.sys ( atikmdag+46c0e4 )
    
    Followup: MachineOwner
    ---------
    
    3: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced.  This cannot be protected by try-except,
    it must be protected by a Probe.  Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: fffff8c004d530c7, memory referenced.
    Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
    Arg3: fffff88004d530e4, If non-zero, the instruction address which referenced the bad memory
    address.
    Arg4: 0000000000000005, (reserved)
    
    Debugging Details:
    ------------------
    
    
    Could not read faulting driver name
    
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030fe100
    fffff8c004d530c7 
    
    FAULTING_IP: 
    atikmdag+46c0e4
    fffff880`04d530e4 41c7000f65c190  mov     dword ptr [r8],90C1650Fh
    
    MM_INTERNAL_CODE:  5
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x50
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    TRAP_FRAME:  fffff88005be4a90 -- (.trap 0xfffff88005be4a90)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=000000007bbbb4ed rbx=0000000000000000 rcx=0000000000000000
    rdx=0000000000000153 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff88004d530e4 rsp=fffff88005be4c28 rbp=0000000000000400
    r8=fffff8c004d530c7  r9=fffff88005be4c70 r10=0000002c7bbbb39a
    r11=000000000000016f r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up di pl nz na po nc
    atikmdag+0x46c0e4:
    fffff880`04d530e4 41c7000f65c190  mov     dword ptr [r8],90C1650Fh ds:4ca8:fffff8c0`04d530c7=????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002e793cf to fffff80002eced00
    
    STACK_TEXT:  
    fffff880`05be4928 fffff800`02e793cf : 00000000`00000050 fffff8c0`04d530c7 00000000`00000001 fffff880`05be4a90 : nt!KeBugCheckEx
    fffff880`05be4930 fffff800`02ecce2e : 00000000`00000001 fffff8c0`04d530c7 78c98bbb`f889f100 00000000`00000004 : nt! ?? ::FNODOBFM::`string'+0x44891
    fffff880`05be4a90 fffff880`04d530e4 : fffff880`04bec5c0 00000000`00000004 cccccccc`00000000 00000000`00000000 : nt!KiPageFault+0x16e
    fffff880`05be4c28 fffff880`04bec5c0 : 00000000`00000004 cccccccc`00000000 00000000`00000000 00000000`00000000 : atikmdag+0x46c0e4
    fffff880`05be4c30 00000000`00000004 : cccccccc`00000000 00000000`00000000 00000000`00000000 fffff880`02f63180 : atikmdag+0x3055c0
    fffff880`05be4c38 cccccccc`00000000 : 00000000`00000000 00000000`00000000 fffff880`02f63180 00000000`001ec6dd : 0x4
    fffff880`05be4c40 00000000`00000000 : 00000000`00000000 fffff880`02f63180 00000000`001ec6dd 0000000e`00000198 : 0xcccccccc`00000000
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    atikmdag+46c0e4
    fffff880`04d530e4 41c7000f65c190  mov     dword ptr [r8],90C1650Fh
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  atikmdag+46c0e4
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: atikmdag
    
    IMAGE_NAME:  atikmdag.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4d40a4bc
    
    FAILURE_BUCKET_ID:  X64_0x50_atikmdag+46c0e4
    
    BUCKET_ID:  X64_0x50_atikmdag+46c0e4
    
    Followup: MachineOwner
    ---------
    
    

    4TH FILE

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 3B, {c0000005, fffff80003007a9b, fffff88003d86fc0, 0}
    
    Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+1df )
    
    Followup: Pool_corruption
    ---------
    
    3: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    SYSTEM_SERVICE_EXCEPTION (3b)
    An exception happened while executing a system service routine.
    Arguments:
    Arg1: 00000000c0000005, Exception code that caused the bugcheck
    Arg2: fffff80003007a9b, Address of the instruction which caused the bugcheck
    Arg3: fffff88003d86fc0, Address of the context record for the exception that caused the bugcheck
    Arg4: 0000000000000000, zero.
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    FAULTING_IP: 
    nt!ExDeferredFreePool+1df
    fffff800`03007a9b 4c395808        cmp     qword ptr [rax+8],r11
    
    CONTEXT:  fffff88003d86fc0 -- (.cxr 0xfffff88003d86fc0)
    rax=006d006f00720068 rbx=0000000000000000 rcx=fffffa80039614c0
    rdx=fffff8a002fc3f70 rsi=0000000000000000 rdi=fffff8a0041a3a20
    rip=fffff80003007a9b rsp=fffff88003d879a0 rbp=0000000000000000
    r8=006c006500700053  r9=fffff8a002fc39b0 r10=0000000000000001
    r11=fffff8a002fc39c0 r12=fffffa8003961140 r13=0000000000000000
    r14=000000000000001b r15=0000000000000001
    iopl=0         nv up ei pl nz na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
    nt!ExDeferredFreePool+0x1df:
    fffff800`03007a9b 4c395808        cmp     qword ptr [rax+8],r11 ds:002b:006d006f`00720070=????????????????
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x3B
    
    PROCESS_NAME:  lsass.exe
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80003007a9b
    
    STACK_TEXT:  
    fffff880`03d879a0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExDeferredFreePool+0x1df
    
    
    FOLLOWUP_IP: 
    nt!ExDeferredFreePool+1df
    fffff800`03007a9b 4c395808        cmp     qword ptr [rax+8],r11
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  nt!ExDeferredFreePool+1df
    
    FOLLOWUP_NAME:  Pool_corruption
    
    IMAGE_NAME:  Pool_Corruption
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    MODULE_NAME: Pool_Corruption
    
    STACK_COMMAND:  .cxr 0xfffff88003d86fc0 ; kb
    
    FAILURE_BUCKET_ID:  X64_0x3B_nt!ExDeferredFreePool+1df
    
    BUCKET_ID:  X64_0x3B_nt!ExDeferredFreePool+1df
    
    Followup: Pool_corruption
    ---------
    
    5TH FILE

    Code:
    
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck A, {31ffc0, 2, 0, fffff80002e60b12}
    
    Probably caused by : ntkrnlmp.exe ( nt!ExpGetLookasideInformation+1c6 )
    
    Followup: MachineOwner
    ---------
    
    0: 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: 000000000031ffc0, 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: fffff80002e60b12, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030ba100
    000000000031ffc0 
    
    CURRENT_IRQL:  0
    
    FAULTING_IP: 
    nt!ExpGetLookasideInformation+1c6
    fffff800`02e60b12 0fb741c0        movzx   eax,word ptr [rcx-40h]
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xA
    
    PROCESS_NAME:  System
    
    LAST_CONTROL_TRANSFER:  from fffff80002e94509 to fffff88003f2f7f2
    
    STACK_TEXT:  
    fffff800`0440dc98 fffff800`02e94509 : 00000000`002fb071 fffffa80`051a55d8 fffff800`0300bcc0 00000000`00000001 : 0xfffff880`03f2f7f2
    fffff800`0440dca0 fffff800`02e829fc : fffff800`02ffde80 fffff800`00000000 00000000`00000000 fffff880`00c0bf5c : nt!PoIdle+0x52a
    fffff800`0440dd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    FOLLOWUP_IP: 
    nt!ExpGetLookasideInformation+1c6
    fffff800`02e60b12 0fb741c0        movzx   eax,word ptr [rcx-40h]
    
    SYMBOL_NAME:  nt!ExpGetLookasideInformation+1c6
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fdd5b
    
    FAILURE_BUCKET_ID:  X64_0xA_nt!ExpGetLookasideInformation+1c6
    
    BUCKET_ID:  X64_0xA_nt!ExpGetLookasideInformation+1c6
    
    Followup: MachineOwner
    ---------
    
    

    6TH FILE

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 24, {1904fb, fffff88009b95918, fffff88009b95170, fffff880012d2aa4}
    
    Probably caused by : hardware ( Ntfs!NtfsCommonCreate+574 )
    
    Followup: MachineOwner
    ---------
    
    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    NTFS_FILE_SYSTEM (24)
        If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
        parameters are the exception record and context record. Do a .cxr
        on the 3rd parameter and then kb to obtain a more informative stack
        trace.
    Arguments:
    Arg1: 00000000001904fb
    Arg2: fffff88009b95918
    Arg3: fffff88009b95170
    Arg4: fffff880012d2aa4
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_RECORD:  fffff88009b95918 -- (.exr 0xfffff88009b95918)
    ExceptionAddress: fffff880012d2aa4 (Ntfs!NtfsCommonCreate+0x0000000000000574)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000001
       Parameter[1]: 0000000000002a20
    Attempt to write to address 0000000000002a20
    
    CONTEXT:  fffff88009b95170 -- (.cxr 0xfffff88009b95170)
    rax=0000000000002a20 rbx=fffff880069104a0 rcx=fffffa80044ff370
    rdx=0000000000000000 rsi=fffffa80044ff370 rdi=00000000000000a2
    rip=fffff880012d2aa4 rsp=fffff88009b95b50 rbp=fffffa8003dbd710
    r8=0000000000000000  r9=0000000000000000 r10=fffff88009b95cd0
    r11=fffff88009b95b20 r12=fffffa8003dbd710 r13=0000000000000000
    r14=0000000000000002 r15=fffff8a001930a00
    iopl=0         nv up ei pl nz na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
    Ntfs!NtfsCommonCreate+0x574:
    fffff880`012d2aa4 0000            add     byte ptr [rax],al ds:002b:00000000`00002a20=??
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  firefox.exe
    
    CURRENT_IRQL:  0
    
    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    EXCEPTION_PARAMETER1:  0000000000000001
    
    EXCEPTION_PARAMETER2:  0000000000002a20
    
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80003102100
    0000000000002a20 
    
    FOLLOWUP_IP: 
    Ntfs!NtfsCommonCreate+574
    fffff880`012d2aa4 0000            add     byte ptr [rax],al
    
    FAULTING_IP: 
    Ntfs!NtfsCommonCreate+574
    fffff880`012d2aa4 0000            add     byte ptr [rax],al
    
    BUGCHECK_STR:  0x24
    
    MISALIGNED_IP: 
    Ntfs!NtfsCommonCreate+574
    fffff880`012d2aa4 0000            add     byte ptr [rax],al
    
    LAST_CONTROL_TRANSFER:  from fffff8800123ba3d to fffff880012d2aa4
    
    STACK_TEXT:  
    fffff880`09b95b50 fffff880`0123ba3d : fffffa80`044ff370 fffffa80`03dbd710 fffff880`069104a0 00000000`00000000 : Ntfs!NtfsCommonCreate+0x574
    fffff880`09b95d30 fffff800`02eca817 : fffff880`06910410 00000000`ffffffff 00000000`0359e220 00000000`2928f0c0 : Ntfs!NtfsCommonCreateCallout+0x1d
    fffff880`09b95d60 fffff800`02eca7d1 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxSwitchKernelStackCallout+0x27
    fffff880`069102e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSwitchKernelStackContinue
    
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  Ntfs!NtfsCommonCreate+574
    
    FOLLOWUP_NAME:  MachineOwner
    
    IMAGE_NAME:  hardware
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    STACK_COMMAND:  .cxr 0xfffff88009b95170 ; kb
    
    MODULE_NAME: hardware
    
    FAILURE_BUCKET_ID:  X64_IP_MISALIGNED_Ntfs.sys
    
    BUCKET_ID:  X64_IP_MISALIGNED_Ntfs.sys
    
    Followup: MachineOwner
    ---------
    

    LATEST FILE


    Code:
    
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck A, {0, 2, 1, fffff80002ee4ec0}
    
    Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiSubmitCommandPacketToQueue+1d8 )
    
    Followup: MachineOwner
    ---------
    
    0: 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: 0000000000000000, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, 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: fffff80002ee4ec0, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80003110100
    0000000000000000 
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    nt!KeSetEvent+2ce
    fffff800`02ee4ec0 f0410fba2907    lock bts dword ptr [r9],7
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xA
    
    PROCESS_NAME:  firefox.exe
    
    TRAP_FRAME:  fffff880095717e0 -- (.trap 0xfffff880095717e0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000002 rbx=0000000000000000 rcx=fffffa80059865b8
    rdx=fffff88002f66248 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002ee4ec0 rsp=fffff88009571970 rbp=0000000000000000
    r8=fffffa80059cfc68  r9=0000000000000000 r10=fffffa80048cc8b0
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz ac po cy
    nt!KeSetEvent+0x2ce:
    fffff800`02ee4ec0 f0410fba2907    lock bts dword ptr [r9],7 ds:6010:00000000`00000000=????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002ee02a9 to fffff80002ee0d00
    
    STACK_TEXT:  
    fffff880`09571698 fffff800`02ee02a9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
    fffff880`095716a0 fffff800`02edef20 : 00000000`00000002 fffffa80`05a0d000 fffffa80`04691010 00000000`00000000 : nt!KiBugCheckDispatch+0x69
    fffff880`095717e0 fffff800`02ee4ec0 : 00000000`00000000 00000000`00000001 00000000`00000000 fffffa80`048cc801 : nt!KiPageFault+0x260
    fffff880`09571970 fffff880`045e19a0 : fffffa80`00000000 fffffa80`00000000 fffffa80`04feee00 fffff880`02f66248 : nt!KeSetEvent+0x2ce
    fffff880`095719e0 fffff880`045e46d9 : 00000000`00000001 fffffa80`048cca98 fffff880`09571c40 00000000`00000000 : dxgmms1!VidSchiSubmitCommandPacketToQueue+0x1d8
    fffff880`09571a50 fffff880`04523764 : 00000000`00000000 00000000`00000200 fffff880`09572180 00000000`00000000 : dxgmms1!VidSchSubmitCommand+0x3ad
    fffff880`09571ab0 fffff880`04522773 : fffff8a0`00000001 fffff8a0`00001400 fffff880`09572130 fffff960`00000003 : dxgkrnl!DXGCONTEXT::Render+0xadc
    fffff880`095720c0 fffff960`0026e152 : 00000000`0011c6b0 00000000`00000000 00000000`73a02450 00000000`0011d170 : dxgkrnl!DxgkRender+0x3e7
    fffff880`09572330 fffff800`02edff93 : fffffa80`057db060 00000000`fffdb000 00000000`00000020 00000000`73a3ebb8 : win32k!NtGdiDdDDIRender+0x12
    fffff880`09572360 00000000`73a5143a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`0011c688 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x73a5143a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    dxgmms1!VidSchiSubmitCommandPacketToQueue+1d8
    fffff880`045e19a0 4c8d5c2440      lea     r11,[rsp+40h]
    
    SYMBOL_STACK_INDEX:  4
    
    SYMBOL_NAME:  dxgmms1!VidSchiSubmitCommandPacketToQueue+1d8
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: dxgmms1
    
    IMAGE_NAME:  dxgmms1.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1
    
    FAILURE_BUCKET_ID:  X64_0xA_dxgmms1!VidSchiSubmitCommandPacketToQueue+1d8
    
    BUCKET_ID:  X64_0xA_dxgmms1!VidSchiSubmitCommandPacketToQueue+1d8
    
    Followup: MachineOwner
    ---------
    
    


    DRIVERS
    Code:
    start             end                 module name
    fffff800`00bcd000 fffff800`00bd7000   kdcom    kdcom.dll    Sat Feb 05 16:52:49 2011 (4D4D8061)
    fffff800`02e18000 fffff800`02e61000   hal      hal.dll      Sat Nov 20 13:00:25 2010 (4CE7C669)
    fffff800`02e61000 fffff800`0344a000   nt       ntkrnlmp.exe Sat Apr 09 05:15:23 2011 (4D9FDD5B)
    fffff880`00c04000 fffff880`00c11000   mcupdate_AuthenticAMD mcupdate_AuthenticAMD.dll Tue Jul 14 02:29:09 2009 (4A5BDF65)
    fffff880`00c11000 fffff880`00c25000   PSHED    PSHED.dll    Tue Jul 14 02:32:23 2009 (4A5BE027)
    fffff880`00c25000 fffff880`00c83000   CLFS     CLFS.SYS     Tue Jul 14 00:19:57 2009 (4A5BC11D)
    fffff880`00c83000 fffff880`00d43000   CI       CI.dll       Sat Nov 20 13:12:36 2010 (4CE7C944)
    fffff880`00d43000 fffff880`00de7000   Wdf01000 Wdf01000.sys Tue Jul 14 00:22:07 2009 (4A5BC19F)
    fffff880`00de7000 fffff880`00df6000   WDFLDR   WDFLDR.SYS   Tue Jul 14 00:19:54 2009 (4A5BC11A)
    fffff880`00e00000 fffff880`00e5c000   volmgrx  volmgrx.sys  Sat Nov 20 09:20:43 2010 (4CE792EB)
    fffff880`00e5c000 fffff880`00e63000   pciide   pciide.sys   Tue Jul 14 00:19:49 2009 (4A5BC115)
    fffff880`00e63000 fffff880`00e73000   PCIIDEX  PCIIDEX.SYS  Tue Jul 14 00:19:48 2009 (4A5BC114)
    fffff880`00e73000 fffff880`00e8d000   mountmgr mountmgr.sys Sat Nov 20 09:19:21 2010 (4CE79299)
    fffff880`00e8d000 fffff880`00ec9000   vmbus    vmbus.sys    Sat Nov 20 09:57:29 2010 (4CE79B89)
    fffff880`00eda000 fffff880`00f31000   ACPI     ACPI.sys     Sat Nov 20 09:19:16 2010 (4CE79294)
    fffff880`00f31000 fffff880`00f3a000   WMILIB   WMILIB.SYS   Tue Jul 14 00:19:51 2009 (4A5BC117)
    fffff880`00f3a000 fffff880`00f44000   msisadrv msisadrv.sys Tue Jul 14 00:19:26 2009 (4A5BC0FE)
    fffff880`00f44000 fffff880`00f77000   pci      pci.sys      Sat Nov 20 09:19:11 2010 (4CE7928F)
    fffff880`00f77000 fffff880`00f84000   vdrvroot vdrvroot.sys Tue Jul 14 01:01:31 2009 (4A5BCADB)
    fffff880`00f84000 fffff880`00f99000   partmgr  partmgr.sys  Sat Nov 20 09:20:00 2010 (4CE792C0)
    fffff880`00f99000 fffff880`00fae000   volmgr   volmgr.sys   Sat Nov 20 09:19:28 2010 (4CE792A0)
    fffff880`00fae000 fffff880`00fc2000   winhv    winhv.sys    Sat Nov 20 09:20:02 2010 (4CE792C2)
    fffff880`00fc2000 fffff880`00fcb000   atapi    atapi.sys    Tue Jul 14 00:19:47 2009 (4A5BC113)
    fffff880`00fcb000 fffff880`00ff5000   ataport  ataport.SYS  Sat Nov 20 09:19:15 2010 (4CE79293)
    fffff880`00ff5000 fffff880`01000000   amdxata  amdxata.sys  Fri Mar 19 16:18:18 2010 (4BA3A3CA)
    fffff880`01000000 fffff880`0100d000   TDI      TDI.SYS      Sat Nov 20 09:22:06 2010 (4CE7933E)
    fffff880`0100d000 fffff880`01090000   csc      csc.sys      Sat Nov 20 09:27:12 2010 (4CE79470)
    fffff880`01092000 fffff880`010de000   fltmgr   fltmgr.sys   Sat Nov 20 09:19:24 2010 (4CE7929C)
    fffff880`010de000 fffff880`010f2000   fileinfo fileinfo.sys Tue Jul 14 00:34:25 2009 (4A5BC481)
    fffff880`010f2000 fffff880`01150000   msrpc    msrpc.sys    Sat Nov 20 09:21:56 2010 (4CE79334)
    fffff880`01150000 fffff880`011c2000   cng      cng.sys      Sat Nov 20 10:08:45 2010 (4CE79E2D)
    fffff880`011c2000 fffff880`011cd000   Msfs     Msfs.SYS     Tue Jul 14 00:19:47 2009 (4A5BC113)
    fffff880`011cd000 fffff880`011de000   Npfs     Npfs.SYS     Tue Jul 14 00:19:48 2009 (4A5BC114)
    fffff880`011de000 fffff880`01200000   tdx      tdx.sys      Sat Nov 20 09:21:54 2010 (4CE79332)
    fffff880`01200000 fffff880`0120a000   Fs_Rec   Fs_Rec.sys   Tue Jul 14 00:19:45 2009 (4A5BC111)
    fffff880`0120a000 fffff880`01213000   RDPCDD   RDPCDD.sys   Tue Jul 14 01:16:34 2009 (4A5BCE62)
    fffff880`01213000 fffff880`0121c000   rdpencdd rdpencdd.sys Tue Jul 14 01:16:34 2009 (4A5BCE62)
    fffff880`0121c000 fffff880`01225000   rdprefmp rdprefmp.sys Tue Jul 14 01:16:35 2009 (4A5BCE63)
    fffff880`0122a000 fffff880`013cd000   Ntfs     Ntfs.sys     Fri Mar 11 03:39:39 2011 (4D79997B)
    fffff880`013cd000 fffff880`013e8000   ksecdd   ksecdd.sys   Sat Nov 20 09:21:15 2010 (4CE7930B)
    fffff880`013e8000 fffff880`013f9000   pcw      pcw.sys      Tue Jul 14 00:19:27 2009 (4A5BC0FF)
    fffff880`01400000 fffff880`01431000   MpFilter MpFilter.sys Wed Sep 15 01:19:28 2010 (4C901110)
    fffff880`01431000 fffff880`01438000   Beep     Beep.SYS     Tue Jul 14 01:00:13 2009 (4A5BCA8D)
    fffff880`01438000 fffff880`01446000   vga      vga.sys      Tue Jul 14 00:38:47 2009 (4A5BC587)
    fffff880`01446000 fffff880`0146b000   VIDEOPRT VIDEOPRT.SYS Tue Jul 14 00:38:51 2009 (4A5BC58B)
    fffff880`0146b000 fffff880`0147b000   watchdog watchdog.sys Tue Jul 14 00:37:35 2009 (4A5BC53F)
    fffff880`01482000 fffff880`01575000   ndis     ndis.sys     Sat Nov 20 09:23:30 2010 (4CE79392)
    fffff880`01575000 fffff880`015d5000   NETIO    NETIO.SYS    Sat Nov 20 09:23:13 2010 (4CE79381)
    fffff880`015d5000 fffff880`01600000   ksecpkg  ksecpkg.sys  Sat Nov 20 10:10:34 2010 (4CE79E9A)
    fffff880`01613000 fffff880`0163d000   cdrom    cdrom.sys    Sat Nov 20 09:19:20 2010 (4CE79298)
    fffff880`0163d000 fffff880`01646000   Null     Null.SYS     Tue Jul 14 00:19:37 2009 (4A5BC109)
    fffff880`0164c000 fffff880`01850000   tcpip    tcpip.sys    Sat Nov 20 09:25:52 2010 (4CE79420)
    fffff880`01850000 fffff880`0189a000   fwpkclnt fwpkclnt.sys Sat Nov 20 09:21:37 2010 (4CE79321)
    fffff880`0189a000 fffff880`018aa000   vmstorfl vmstorfl.sys Sat Nov 20 09:57:30 2010 (4CE79B8A)
    fffff880`018aa000 fffff880`018f6000   volsnap  volsnap.sys  Sat Nov 20 09:20:08 2010 (4CE792C8)
    fffff880`018f6000 fffff880`018fe000   spldr    spldr.sys    Mon May 11 17:56:27 2009 (4A0858BB)
    fffff880`018fe000 fffff880`01908000   speedfan speedfan.sys Sat Dec 18 11:03:51 2010 (4D0C9517)
    fffff880`01908000 fffff880`01942000   rdyboost rdyboost.sys Sat Nov 20 09:43:10 2010 (4CE7982E)
    fffff880`01942000 fffff880`01954000   mup      mup.sys      Tue Jul 14 00:23:45 2009 (4A5BC201)
    fffff880`01954000 fffff880`0195d000   hwpolicy hwpolicy.sys Sat Nov 20 09:18:54 2010 (4CE7927E)
    fffff880`0195d000 fffff880`01997000   fvevol   fvevol.sys   Sat Nov 20 09:24:06 2010 (4CE793B6)
    fffff880`01997000 fffff880`019ad000   disk     disk.sys     Tue Jul 14 00:19:57 2009 (4A5BC11D)
    fffff880`019ad000 fffff880`019dd000   CLASSPNP CLASSPNP.SYS Sat Nov 20 09:19:23 2010 (4CE7929B)
    fffff880`03e00000 fffff880`03e14000   termdd   termdd.sys   Sat Nov 20 11:03:40 2010 (4CE7AB0C)
    fffff880`03e14000 fffff880`03e65000   rdbss    rdbss.sys    Sat Nov 20 09:27:51 2010 (4CE79497)
    fffff880`03e65000 fffff880`03e71000   nsiproxy nsiproxy.sys Tue Jul 14 00:21:02 2009 (4A5BC15E)
    fffff880`03e71000 fffff880`03e7c000   mssmbios mssmbios.sys Tue Jul 14 00:31:10 2009 (4A5BC3BE)
    fffff880`03e7c000 fffff880`03e8b000   discache discache.sys Tue Jul 14 00:37:18 2009 (4A5BC52E)
    fffff880`03e8b000 fffff880`03ea9000   dfsc     dfsc.sys     Sat Nov 20 09:26:31 2010 (4CE79447)
    fffff880`03ea9000 fffff880`03eba000   blbdrive blbdrive.sys Tue Jul 14 00:35:59 2009 (4A5BC4DF)
    fffff880`03eba000 fffff880`03f43000   afd      afd.sys      Sat Nov 20 09:23:27 2010 (4CE7938F)
    fffff880`03f43000 fffff880`03f88000   netbt    netbt.sys    Sat Nov 20 09:23:18 2010 (4CE79386)
    fffff880`03f88000 fffff880`03f91000   wfplwf   wfplwf.sys   Tue Jul 14 01:09:26 2009 (4A5BCCB6)
    fffff880`03f91000 fffff880`03fb7000   pacer    pacer.sys    Sat Nov 20 10:52:18 2010 (4CE7A862)
    fffff880`03fb7000 fffff880`03fc6000   netbios  netbios.sys  Tue Jul 14 01:09:26 2009 (4A5BCCB6)
    fffff880`03fc6000 fffff880`03fe3000   serial   serial.sys   Tue Jul 14 01:00:40 2009 (4A5BCAA8)
    fffff880`03fe3000 fffff880`03ffe000   wanarp   wanarp.sys   Sat Nov 20 10:52:36 2010 (4CE7A874)
    fffff880`04200000 fffff880`04243000   ks       ks.sys       Sat Nov 20 10:33:23 2010 (4CE7A3F3)
    fffff880`04243000 fffff880`04257000   amdiox64 amdiox64.sys Thu Feb 18 15:17:53 2010 (4B7D5A21)
    fffff880`04257000 fffff880`04269000   umbus    umbus.sys    Sat Nov 20 10:44:37 2010 (4CE7A695)
    fffff880`04269000 fffff880`042c3000   usbhub   usbhub.sys   Sat Nov 20 10:44:30 2010 (4CE7A68E)
    fffff880`042c3000 fffff880`042ce000   flpydisk flpydisk.sys Tue Jul 14 01:00:54 2009 (4A5BCAB6)
    fffff880`042d0000 fffff880`042f6000   tunnel   tunnel.sys   Sat Nov 20 10:51:50 2010 (4CE7A846)
    fffff880`042f6000 fffff880`0430b000   amdppm   amdppm.sys   Tue Jul 14 00:19:25 2009 (4A5BC0FD)
    fffff880`0430b000 fffff880`04359000   atikmpag atikmpag.sys Wed Jan 26 22:13:33 2011 (4D409C8D)
    fffff880`04359000 fffff880`04374000   raspppoe raspppoe.sys Tue Jul 14 01:10:17 2009 (4A5BCCE9)
    fffff880`04374000 fffff880`04395000   raspptp  raspptp.sys  Sat Nov 20 10:52:31 2010 (4CE7A86F)
    fffff880`04395000 fffff880`043af000   rassstp  rassstp.sys  Tue Jul 14 01:10:25 2009 (4A5BCCF1)
    fffff880`043af000 fffff880`043be000   kbdclass kbdclass.sys Tue Jul 14 00:19:50 2009 (4A5BC116)
    fffff880`043be000 fffff880`043cd000   mouclass mouclass.sys Tue Jul 14 00:19:50 2009 (4A5BC116)
    fffff880`043cd000 fffff880`043e2000   NDProxy  NDProxy.SYS  Sat Nov 20 10:52:20 2010 (4CE7A864)
    fffff880`043e2000 fffff880`043fa000   rspndr   rspndr.sys   Tue Jul 14 01:08:50 2009 (4A5BCC92)
    fffff880`04400000 fffff880`04424000   HDAudBus HDAudBus.sys Sat Nov 20 10:43:42 2010 (4CE7A65E)
    fffff880`04424000 fffff880`0448e000   Rt64win7 Rt64win7.sys Wed Jan 26 13:34:03 2011 (4D4022CB)
    fffff880`0448e000 fffff880`04499000   usbohci  usbohci.sys  Tue Jul 14 01:06:30 2009 (4A5BCC06)
    fffff880`04499000 fffff880`044aa000   usbehci  usbehci.sys  Tue Jul 14 01:06:30 2009 (4A5BCC06)
    fffff880`044aa000 fffff880`044b3000   wmiacpi  wmiacpi.sys  Tue Jul 14 00:31:02 2009 (4A5BC3B6)
    fffff880`044b3000 fffff880`045a7000   dxgkrnl  dxgkrnl.sys  Sat Nov 20 09:50:50 2010 (4CE799FA)
    fffff880`045a7000 fffff880`045ed000   dxgmms1  dxgmms1.sys  Sat Nov 20 09:49:53 2010 (4CE799C1)
    fffff880`045ed000 fffff880`045fa000   fdc      fdc.sys      Tue Jul 14 01:00:54 2009 (4A5BCAB6)
    fffff880`045fa000 fffff880`045fb480   swenum   swenum.sys   Tue Jul 14 01:00:18 2009 (4A5BCA92)
    fffff880`04614000 fffff880`046dd000   HTTP     HTTP.sys     Sat Nov 20 09:24:30 2010 (4CE793CE)
    fffff880`046dd000 fffff880`046fb000   bowser   bowser.sys   Wed Feb 23 04:55:04 2011 (4D649328)
    fffff880`046fb000 fffff880`04713000   mpsdrv   mpsdrv.sys   Tue Jul 14 01:08:25 2009 (4A5BCC79)
    fffff880`04713000 fffff880`04740000   mrxsmb   mrxsmb.sys   Wed Feb 23 04:56:22 2011 (4D649376)
    fffff880`04740000 fffff880`0478d000   mrxsmb10 mrxsmb10.sys Wed Feb 23 04:55:12 2011 (4D649330)
    fffff880`0478d000 fffff880`047b1000   mrxsmb20 mrxsmb20.sys Wed Feb 23 04:55:12 2011 (4D649330)
    fffff880`047b1000 fffff880`047c1000   MpNWMon  MpNWMon.sys  Wed Sep 15 01:19:30 2010 (4C901112)
    fffff880`04800000 fffff880`0480b000   rdpbus   rdpbus.sys   Tue Jul 14 01:17:46 2009 (4A5BCEAA)
    fffff880`04815000 fffff880`05111000   atikmdag atikmdag.sys Wed Jan 26 22:48:28 2011 (4D40A4BC)
    fffff880`05111000 fffff880`05167000   USBPORT  USBPORT.SYS  Tue Jul 14 01:06:31 2009 (4A5BCC07)
    fffff880`05167000 fffff880`05173000   serenum  serenum.sys  Tue Jul 14 01:00:33 2009 (4A5BCAA1)
    fffff880`05173000 fffff880`05183000   CompositeBus CompositeBus.sys Sat Nov 20 10:33:17 2010 (4CE7A3ED)
    fffff880`05183000 fffff880`05199000   AgileVpn AgileVpn.sys Tue Jul 14 01:10:24 2009 (4A5BCCF0)
    fffff880`05199000 fffff880`051bd000   rasl2tp  rasl2tp.sys  Sat Nov 20 10:52:34 2010 (4CE7A872)
    fffff880`051bd000 fffff880`051c9000   ndistapi ndistapi.sys Tue Jul 14 01:10:00 2009 (4A5BCCD8)
    fffff880`051c9000 fffff880`051f8000   ndiswan  ndiswan.sys  Sat Nov 20 10:52:32 2010 (4CE7A870)
    fffff880`06400000 fffff880`0640d000   mouhid   mouhid.sys   Tue Jul 14 01:00:20 2009 (4A5BCA94)
    fffff880`0640d000 fffff880`0641b000   monitor  monitor.sys  Tue Jul 14 00:38:52 2009 (4A5BC58C)
    fffff880`0641b000 fffff880`06438000   usbccgp  usbccgp.sys  Sat Nov 20 10:44:03 2010 (4CE7A673)
    fffff880`06438000 fffff880`06446000   kbdhid   kbdhid.sys   Sat Nov 20 10:33:25 2010 (4CE7A3F5)
    fffff880`06446000 fffff880`06469000   luafv    luafv.sys    Tue Jul 14 00:26:13 2009 (4A5BC295)
    fffff880`06469000 fffff880`0648a000   WudfPf   WudfPf.sys   Sat Nov 20 10:42:44 2010 (4CE7A624)
    fffff880`0648a000 fffff880`0649f000   lltdio   lltdio.sys   Tue Jul 14 01:08:50 2009 (4A5BCC92)
    fffff880`064a2000 fffff880`064c2000   AtihdW76 AtihdW76.sys Mon Aug 16 11:41:02 2010 (4C6915BE)
    fffff880`064c2000 fffff880`064ff000   portcls  portcls.sys  Tue Jul 14 01:06:27 2009 (4A5BCC03)
    fffff880`064ff000 fffff880`06521000   drmk     drmk.sys     Tue Jul 14 02:01:25 2009 (4A5BD8E5)
    fffff880`06521000 fffff880`06526200   ksthunk  ksthunk.sys  Tue Jul 14 01:00:19 2009 (4A5BCA93)
    fffff880`06527000 fffff880`06583000   HdAudio  HdAudio.sys  Sat Nov 20 10:44:23 2010 (4CE7A687)
    fffff880`06583000 fffff880`0658f000   Dxapi    Dxapi.sys    Tue Jul 14 00:38:28 2009 (4A5BC574)
    fffff880`0658f000 fffff880`0659d000   crashdmp crashdmp.sys Tue Jul 14 01:01:01 2009 (4A5BCABD)
    fffff880`0659d000 fffff880`065a9000   dump_dumpata dump_dumpata.sys Tue Jul 14 00:19:47 2009 (4A5BC113)
    fffff880`065a9000 fffff880`065b2000   dump_atapi dump_atapi.sys Tue Jul 14 00:19:47 2009 (4A5BC113)
    fffff880`065b2000 fffff880`065c5000   dump_dumpfve dump_dumpfve.sys Tue Jul 14 00:21:51 2009 (4A5BC18F)
    fffff880`065c5000 fffff880`065d3000   hidusb   hidusb.sys   Sat Nov 20 10:43:49 2010 (4CE7A665)
    fffff880`065d3000 fffff880`065ec000   HIDCLASS HIDCLASS.SYS Sat Nov 20 10:43:49 2010 (4CE7A665)
    fffff880`065ec000 fffff880`065f4080   HIDPARSE HIDPARSE.SYS Tue Jul 14 01:06:17 2009 (4A5BCBF9)
    fffff880`065f5000 fffff880`065f6f00   USBD     USBD.SYS     Tue Jul 14 01:06:23 2009 (4A5BCBFF)
    fffff880`0703a000 fffff880`070e0000   peauth   peauth.sys   Tue Jul 14 02:01:19 2009 (4A5BD8DF)
    fffff880`070e0000 fffff880`070eb000   secdrv   secdrv.SYS   Wed Sep 13 14:18:38 2006 (4508052E)
    fffff880`070eb000 fffff880`0711c000   srvnet   srvnet.sys   Wed Feb 23 04:55:44 2011 (4D649350)
    fffff880`0711c000 fffff880`0712e000   tcpipreg tcpipreg.sys Sat Nov 20 10:51:48 2010 (4CE7A844)
    fffff880`0712e000 fffff880`07198000   srv2     srv2.sys     Wed Feb 23 04:56:00 2011 (4D649360)
    fffff880`07271000 fffff880`0727c000   asyncmac asyncmac.sys Tue Jul 14 01:10:13 2009 (4A5BCCE5)
    fffff880`072b2000 fffff880`0734a000   srv      srv.sys      Wed Feb 23 04:56:21 2011 (4D649375)
    fffff880`0734a000 fffff880`0735f000   NisDrvWFP NisDrvWFP.sys Wed Sep 15 01:20:25 2010 (4C901149)
    fffff880`0735f000 fffff880`07395000   fastfat  fastfat.SYS  Tue Jul 14 00:23:28 2009 (4A5BC1F0)
    fffff960`000e0000 fffff960`003f2000   win32k   win32k.sys   Thu Mar 03 03:51:40 2011 (4D6F104C)
    fffff960`005c0000 fffff960`005ca000   TSDDD    TSDDD.dll    unavailable (00000000)
    fffff960`00660000 fffff960`00687000   cdd      cdd.dll      Sat Nov 20 12:55:34 2010 (4CE7C546)
    fffff960`008c0000 fffff960`00921000   ATMFD    ATMFD.DLL    Sat Feb 19 09:00:32 2011 (4D5F86B0)
    
    Unloaded modules:
    fffff880`07200000 fffff880`07271000   spsys.sys
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  00071000
    fffff880`019dd000 fffff880`019eb000   crashdmp.sys
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  0000E000
    fffff880`019eb000 fffff880`019f7000   dump_ataport
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  0000C000
    fffff880`019f7000 fffff880`01a00000   dump_atapi.s
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  00009000
    fffff880`01600000 fffff880`01613000   dump_dumpfve
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  00013000
    
     
  8. cybercore

    cybercore New Member

    Joined:
    Jul 7, 2009
    Messages:
    15,823
    Likes Received:
    321
    Let's hope, it looks like your hardware, probably bad motherboard or bad RAM:

    BugCheck A, {fffffa7ffffff3e0, 2, 1, fffff80002e9b841}
    Probably caused by : memory_corruption ( nt!MmZeroPageThread+3c4 )

    BugCheck 24, {1904fb, fffff88009b95918, fffff88009b95170, fffff880012d2aa4}
    Probably caused by : hardware ( Ntfs!NtfsCommonCreate+574 )

    BugCheck 3B, {c0000005, fffff80003007a9b, fffff88003d86fc0, 0}
    Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+1df )
     
  9. ParanoidPlumber

    ParanoidPlumber New Member

    Joined:
    May 6, 2011
    Messages:
    44
    Likes Received:
    0
    It appears at least the BIOS update fixed startup issues for now. I'm still getting BSOD's.

    Everything points to it being the motherboard. I'll try reinstalling the components. I've also opened a support line with the manufacture.
     

    Attached Files:

  10. cybercore

    cybercore New Member

    Joined:
    Jul 7, 2009
    Messages:
    15,823
    Likes Received:
    321
    Format the partition and reinstall the system, make sure to install an official build of Windows 7, without modifications.
    If you shortly get crashes on the fresh installation, replace your motherboard.
     
  11. ParanoidPlumber

    ParanoidPlumber New Member

    Joined:
    May 6, 2011
    Messages:
    44
    Likes Received:
    0
    Actually, I've only crashed once since I flashed the BIOS. I've run 3 days straight with no crashes which is a big improvement.

    It puzzles me because that BSOD I got made it appear as if the problem hadn't been fixed.
     
  12. kaos

    kaos Senior Member

    Joined:
    May 9, 2011
    Messages:
    1,747
    Likes Received:
    33
    see how your pc works , may have been a one off,

    if you get any more

    then upload them :D
     
  13. ParanoidPlumber

    ParanoidPlumber New Member

    Joined:
    May 6, 2011
    Messages:
    44
    Likes Received:
    0
    Sure thing.

    I can't believe this flagrant problem was so easily fixed. Almost a week now with no problems.
     
  14. kaos

    kaos Senior Member

    Joined:
    May 9, 2011
    Messages:
    1,747
    Likes Received:
    33
    hows the pc ?
     
  15. ParanoidPlumber

    ParanoidPlumber New Member

    Joined:
    May 6, 2011
    Messages:
    44
    Likes Received:
    0
    11 days without any problems until this BSOD.

    It may not even be related to my previous problems. I'm pretty sure this was caused by the display drivers. About a minute before it crashed the screen flashed and refreshed and then I got a notification saying the display driver had crashed and had recovered.
     

    Attached Files:

  16. ParanoidPlumber

    ParanoidPlumber New Member

    Joined:
    May 6, 2011
    Messages:
    44
    Likes Received:
    0
    Last couple of days I've been having problems again. Blue screens and the computer fails to boot up or show an image on startup.
     

    Attached Files:

  17. ParanoidPlumber

    ParanoidPlumber New Member

    Joined:
    May 6, 2011
    Messages:
    44
    Likes Received:
    0
    Still having more errors.

    Lots of time's my computer will fail to start. Doesn't post anything, just blank screens. A few times it had to run a NTFS checker. Also windows failed to load errors that then it tries to repair startup errors. Essentially everything that was happening before (weeks ago).

    I got a BSOD that I've never seen that said: Attempt to write to read only memory failed.

    This puzzles me greatly because when I updated the BIOS it fixed all the problems. Now, suddenly they're back. I've diagnosed this before as being a BIOS/motherboard problem. Do I have a bad motherboard?
     

    Attached Files:

    #37 ParanoidPlumber, Jun 21, 2011
    Last edited: Jun 21, 2011
  18. Trouble

    Trouble Noob Whisperer

    Joined:
    Nov 30, 2009
    Messages:
    13,845
    Likes Received:
    833
    For what it's worth and just my two cents, but I've reviewed all of your dump files that you've posted within this thread, and I noticed that
    The dump file 051600-20248-01.dmp dated 5/16/2011 at 12:02 AM, did not contain this driver
    BS_I2cIo.sys dated 6/16/2008 (really kinda old for a Windows 7 driver) nor did any of your dump files posted with dates earlier than that.
    All of your subsequent dump files have included this driver. My suggestion is to see if there is something more recent from the MotherBoard Manufacturer (BioStar) for your specific hardware.
    I am guessing (and it's only a guess) that this came about the same time as when you flashed the bios. Since your four most recent dumps seem to be indicating memory issues (including page file memory), you should probably make sure that the firmware (flash) update didn't un-do, any settings that you had previously made regarding memory settings (frequency, timings, voltages) prior to the bios flash. Other than that I would say that before I decided that it was a Motherboard problem, I would look to swapping out your memory....BUT; I would also say that I (personally) have had some seemingly incurable problems with BioStar motherboards and have pretty much moved on to more mainstream manufacturers (Intel, Gigabyte, Asus, etc.,) and even those can also have their own problems but are usually a bit easier to work through using their forum boards and other manufacturer support mechanisms.
    Good luck and best wishes.
    Regards
    Randy
     
  19. ParanoidPlumber

    ParanoidPlumber New Member

    Joined:
    May 6, 2011
    Messages:
    44
    Likes Received:
    0
    Ok, your post makes a lot of sense. Thanks for the great help on the diagnostic. I'll see what I can fix.

    I just built a new computer for a friend (still sitting on my desk) and I could try swapping out his new RAM and see if that helps.

    2 months ago I would have recommended BIOSTAR for its price (worked perfectly for a full year) but now not at all. Its been very difficult to work with.
     
  20. nmsuk

    nmsuk Windows Forum Admin
    Staff Member Premium Supporter

    Joined:
    Sep 7, 2009
    Messages:
    2,695
    Likes Received:
    194
    Haven't used Biostar for awhile, we actually black listed them as we had so many problems with the damn things. Since sticking with one of the major manufacturers had barely a problem.
     

Share This Page

Loading...