Random BSOD's since upgrading pc


  1. Posts : 7
    Windows 7 Professional x64bit
       #1

    Random BSOD's since upgrading pc


    I upgraded my pc a month ago with a serveral parts:

    Asus P8Z68-V Pro
    Intel I7-2600K
    8 GB Geil 1333
    OCZ SSD agility 3, 120 GB
    Western Digital 1000GB Caviar Black

    Also my pc has:

    GTX480
    Soundblaster Xi-Fi Platinum

    Since the beginning i upgraded my pc it started to give random BSOD's. After updating the firmware of the SSD and the bios of the motherboard the period between BSOD's became longer but still they happen.

    The BSOD's are looking random, sometimes in game, sometimes when watching a movie, sometimes when installing something, when playing music, etc

    i included the minidumps of this week
    Please help me =(
      My Computer


  2. Posts : 6,668
    Windows 7 x64
       #2

    I'm getting a memory corruption message here.

    I suggest testing overnight with memtest86 - instructions at link
    RAM - Test with Memtest86+
    You should let it run overnight or for 5 to 7 passes before reaching any conclusions... unless it just starts spitting out errors right away.

    Code:
    Probably caused by : memory_corruption ( nt!MiPfnShareCountIsZero+77 )
    
    Followup: MachineOwner
    ---------
    
    4: 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: fffff80002e9cad7, Address of the instruction which caused the bugcheck
    Arg3: fffff88009e2baf0, 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!MiPfnShareCountIsZero+77
    fffff800`02e9cad7 0fb6511a        movzx   edx,byte ptr [rcx+1Ah]
    
    CONTEXT:  fffff88009e2baf0 -- (.cxr 0xfffff88009e2baf0)
    rax=000fffffffffffff rbx=fffffa8003e1fd50 rcx=0005fa8002136720
    rdx=0000000000000000 rsi=fffff68000062850 rdi=0000000000000000
    rip=fffff80002e9cad7 rsp=fffff88009e2c4d0 rbp=0000058000000000
     r8=00002000000b1226  r9=0000000000000006 r10=fffff8a004fc8060
    r11=0000058000000000 r12=2aaaaaaaaaaaaaab r13=0000000000000000
    r14=fffffa8003ae1170 r15=0000000000000000
    iopl=0         nv up ei pl nz na pe nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
    nt!MiPfnShareCountIsZero+0x77:
    fffff800`02e9cad7 0fb6511a        movzx   edx,byte ptr [rcx+1Ah] ds:002b:0005fa80`0213673a=??
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x3B
    
    PROCESS_NAME:  avgrsa.exe
    
    CURRENT_IRQL:  2
    
    LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002e9cad7
    
    STACK_TEXT:  
    fffff880`09e2c4d0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiPfnShareCountIsZero+0x77
    
    
    FOLLOWUP_IP: 
    nt!MiPfnShareCountIsZero+77
    fffff800`02e9cad7 0fb6511a        movzx   edx,byte ptr [rcx+1Ah]
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  nt!MiPfnShareCountIsZero+77
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3
    
    STACK_COMMAND:  .cxr 0xfffff88009e2baf0 ; kb
    
    IMAGE_NAME:  memory_corruption
    
    FAILURE_BUCKET_ID:  X64_0x3B_nt!MiPfnShareCountIsZero+77
    
    BUCKET_ID:  X64_0x3B_nt!MiPfnShareCountIsZero+77
    
    Followup: MachineOwner
    ---------
      My Computer


  3. Posts : 7
    Windows 7 Professional x64bit
    Thread Starter
       #3

    I got Memtest Ready to use, any recommended settings for the test, or just follow the standard test ?
      My Computer


  4. Posts : 6,668
    Windows 7 x64
       #4

    I have always used 'recommended' unless they have changed the format for it, it has admittedly been several months since I used it myself.
      My Computer


  5. Posts : 7
    Windows 7 Professional x64bit
    Thread Starter
       #5

    Did not do the memtest yet, still busy on pc, got another random bluescreen, (was having a movie on pause before it even played) and a program opened. I will post the dump again, if you can check if this is also related to the memory

    Thanks!
      My Computer


  6. Posts : 6,668
    Windows 7 x64
       #6

    yeah still saying memory corruption, and it actually looks like it may be causing issues with windows itself at this point.
    Is probably best that you run that test tonight, though given what I've seen here unless you have a overclock in play I'm getting pretty confident you're going to find a problem with the memory.

    Code:
    Probably caused by : memory_corruption ( nt!MiMapPageInHyperSpaceWorker+1b )
    
    Followup: MachineOwner
    ---------
    
    4: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    CACHE_MANAGER (34)
        See the comment for FAT_FILE_SYSTEM (0x23)
    Arguments:
    Arg1: 0000000000050853
    Arg2: fffff8800394d478
    Arg3: fffff8800394ccd0
    Arg4: fffff80002ec0f1f
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_RECORD:  fffff8800394d478 -- (.exr 0xfffff8800394d478)
    ExceptionAddress: fffff80002ec0f1f (nt!MiMapPageInHyperSpaceWorker+0x000000000000001b)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: ffffffffffffffff
    Attempt to read from address ffffffffffffffff
    
    CONTEXT:  fffff8800394ccd0 -- (.cxr 0xfffff8800394ccd0)
    rax=0000058000000000 rbx=fffffa800243fd50 rcx=00002000000c4b11
    rdx=0000000000000000 rsi=0000000000000080 rdi=fffffa800243fd50
    rip=fffff80002ec0f1f rsp=fffff8800394d6b8 rbp=0000000000000001
     r8=0005fa80024e1330  r9=0000000000000000 r10=0000000000000002
    r11=fffff8800394d7a0 r12=0000058000000000 r13=0000000000000001
    r14=2aaaaaaaaaaaaaab r15=0000000000000002
    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!MiMapPageInHyperSpaceWorker+0x1b:
    fffff800`02ec0f1f 458a481a        mov     r9b,byte ptr [r8+1Ah] ds:002b:0005fa80`024e134a=??
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    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:  0000000000000000
    
    EXCEPTION_PARAMETER2:  ffffffffffffffff
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030bd100
     ffffffffffffffff 
    
    FOLLOWUP_IP: 
    nt!MiMapPageInHyperSpaceWorker+1b
    fffff800`02ec0f1f 458a481a        mov     r9b,byte ptr [r8+1Ah]
    
    FAULTING_IP: 
    nt!MiMapPageInHyperSpaceWorker+1b
    fffff800`02ec0f1f 458a481a        mov     r9b,byte ptr [r8+1Ah]
    
    BUGCHECK_STR:  0x34
    
    LAST_CONTROL_TRANSFER:  from fffff80002e735cb to fffff80002ec0f1f
    
    STACK_TEXT:  
    fffff880`0394d6b8 fffff800`02e735cb : fffffa80`024264f0 00000000`00000000 00000000`00000080 fffff800`02fb990e : nt!MiMapPageInHyperSpaceWorker+0x1b
    fffff880`0394d6c0 fffff800`02ed87ad : 00000000`00000002 00000000`00000001 fffffa80`0243fd50 00000000`00000001 : nt!MiRestoreTransitionPte+0x7b
    fffff880`0394d750 fffff800`02e4f29f : fa800deb`a83004c0 fa800deb`a83004c0 fffff880`0394d840 00000000`0000006a : nt!MiRemoveLowestPriorityStandbyPage+0x1d5
    fffff880`0394d7d0 fffff800`031274ea : fffffa80`0e00e000 fffffa80`00000001 fffffa80`0e00e000 00000000`00000005 : nt!MiPfPutPagesInTransition+0x826
    fffff880`0394d940 fffff800`02e36d37 : fffffa80`0e00e000 00000000`0bf38000 00000000`0bf38000 fffff800`0302b260 : nt!MmPrefetchForCacheManager+0x8e
    fffff880`0394d990 fffff800`02ed098e : fffffa80`06af1070 fffffa80`00000000 fffff880`00000005 fffff880`04bcb701 : nt!CcPerformReadAhead+0x2f3
    fffff880`0394dac0 fffff800`02e95001 : fffffa80`06a904f0 fffff800`03181901 fffff800`0308c8d0 fffff800`00000005 : nt!CcWorkerThread+0x21e
    fffff880`0394db70 fffff800`03125fee : 00000000`00000000 fffffa80`06a9e040 00000000`00000080 fffffa80`06a16b30 : nt!ExpWorkerThread+0x111
    fffff880`0394dc00 fffff800`02e7c5e6 : fffff880`03789180 fffffa80`06a9e040 fffff880`037940c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`0394dc40 00000000`00000000 : fffff880`0394e000 fffff880`03948000 fffff880`0394d540 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  nt!MiMapPageInHyperSpaceWorker+1b
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3
    
    STACK_COMMAND:  .cxr 0xfffff8800394ccd0 ; kb
    
    IMAGE_NAME:  memory_corruption
    
    FAILURE_BUCKET_ID:  X64_0x34_nt!MiMapPageInHyperSpaceWorker+1b
    
    BUCKET_ID:  X64_0x34_nt!MiMapPageInHyperSpaceWorker+1b
    
    Followup: MachineOwner
    ---------
      My Computer


  7. Posts : 7
    Windows 7 Professional x64bit
    Thread Starter
       #7

    i stopped the test after 6 hours and 38 minutes, 6 times pass, 0 errors
      My Computer


  8. Posts : 7
    Windows 7 Professional x64bit
    Thread Starter
       #8

    got another BSOD.... what does it say ?
    thnx again
      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 04:39.
Find Us