locked
Upgrade to win7 on older machine (new install) various BSOD RRS feed

  • Question

  • Added an SSD to a core2duo machine with a fresh win7 pro install and get various BSOD errors

    ntoskrnl.exe is one of the files highlighted red in each BCC

    Non-verbose crash list here

    Any ideas off the bat ?

    Saturday, February 11, 2012 6:16 AM

Answers

  • *******************************************************************************
    *                                                                             *
    *                        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: fffffa8022b86dc8, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff88001951247, If non-zero, the instruction address which referenced the bad memory
    address.
    Arg4: 0000000000000002, (reserved)


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




    Could not read faulting driver name


    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d0c100
     fffffa8022b86dc8 


    FAULTING_IP: 
    volsnap!VspWriteVolumePhase25+27
    fffff880`01951247 4c8bb398030000  mov     r14,qword ptr [rbx+398h]


    MM_INTERNAL_CODE:  2


    CUSTOMER_CRASH_COUNT:  1


    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT


    BUGCHECK_STR:  0x50


    PROCESS_NAME:  System


    CURRENT_IRQL:  0


    TRAP_FRAME:  fffff880033bea80 -- (.trap 0xfffff880033bea80)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000009b00 rbx=0000000000000000 rcx=fffffa8004293b70
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff88001951247 rsp=fffff880033bec10 rbp=fffffa8002b615f0
     r8=00000000000038f8  r9=fffff88007183c00 r10=0000000000000000
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    volsnap!VspWriteVolumePhase25+0x27:
    fffff880`01951247 4c8bb398030000  mov     r14,qword ptr [rbx+398h] ds:00000000`00000398=????????????????
    Resetting default scope


    LAST_CONTROL_TRANSFER:  from fffff80002a843f0 to fffff80002ad9c40


    STACK_TEXT:  
    fffff880`033be918 fffff800`02a843f0 : 00000000`00000050 fffffa80`22b86dc8 00000000`00000000 fffff880`033bea80 : nt!KeBugCheckEx
    fffff880`033be920 fffff800`02ad7d6e : 00000000`00000000 fffffa80`22b86dc8 00000000`00000000 fffffa80`02b86a30 : nt! ?? ::FNODOBFM::`string'+0x447c6
    fffff880`033bea80 fffff880`01951247 : 00000000`0000a9fe fffffa80`02b87c68 00000000`00000000 fffff880`01938900 : nt!KiPageFault+0x16e
    fffff880`033bec10 fffff880`01951acc : fffffa80`04293b70 fffffa80`02b615f0 fffffa80`02b86a30 fffffa80`04293bc8 : volsnap!VspWriteVolumePhase25+0x27
    fffff880`033becd0 fffff880`019389ad : fffffa80`04293bc8 fffffa80`02b615f0 fffffa80`02b61540 fffffa80`0420e088 : volsnap!VspWriteVolumePhase22+0x2c
    fffff880`033bed00 fffff800`02d74fee : fffffa80`02b87b60 00000000`00000080 fffffa80`02455890 fffffa80`02b87b60 : volsnap!VspWorkerThread+0xad
    fffff880`033bed40 fffff800`02acb5e6 : fffff880`009e8180 fffffa80`02b87b60 fffff880`009f2f40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`033bed80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16




    STACK_COMMAND:  kb


    FOLLOWUP_IP: 
    volsnap!VspWriteVolumePhase25+27
    fffff880`01951247 4c8bb398030000  mov     r14,qword ptr [rbx+398h]


    SYMBOL_STACK_INDEX:  3


    SYMBOL_NAME:  volsnap!VspWriteVolumePhase25+27


    FOLLOWUP_NAME:  MachineOwner


    MODULE_NAME: volsnap


    IMAGE_NAME:  volsnap.sys


    DEBUG_FLR_IMAGE_TIMESTAMP:  4ce792c8


    FAILURE_BUCKET_ID:  X64_0x50_volsnap!VspWriteVolumePhase25+27


    BUCKET_ID:  X64_0x50_volsnap!VspWriteVolumePhase25+27


    Followup: MachineOwner

    -----------------------------------------------------------------------------------------------------------------------------

    Bug Check Code 0x50: http://msdn.microsoft.com/en-us/library/windows/hardware/ff559023(v=vs.85).aspx

    The BSOD was caused due to volsnap.sys driver. More about it: http://www.file.net/process/volsnap.sys.html

    It may be corrupt. For that, please proceed like that:

    • Run sfc /scannow
    • Run chkdsk /r /f

    Once done, check results.

    Possible that you have HDD failures. For hardware diagnosis, contact your manufacturer Technical Support.

    You can also contact Microsoft CSS for assistance.



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

    Microsoft Student Partner 2010 / 2011
    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
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations
    Microsoft Certified IT Professional: Enterprise Administrator
    Microsoft Certified IT Professional: Server Administrator
    Microsoft Certified Trainer

    • Proposed as answer by Arthur Xie Monday, February 13, 2012 6:05 AM
    • Marked as answer by Arthur Xie Tuesday, February 21, 2012 6:16 AM
    Sunday, February 12, 2012 2:32 PM

All replies

  • Hello,

    As I see, you have multiple bug check codes.

    Please start proceeding like that:

    • Update all possible drivers you have
    • Uninstall all unused programs
    • Disable all security softwares that you have
    • Run msconfig and disable all startup items / services except Microsoft ones
    • Run memtest86+ to check if all is okay with your RAM. If an error was detected then replace the faulty RAM or contact your manufacturer Technical Support

    If problem persists then use Microsoft Skydrive to upload new dump files under c:\windpws\minidump. Once done, post  a link here.

    If you want to debug dump files by yourself, refer to that: http://support.microsoft.com/kb/315263

    You can also contact Microsoft CSS for assistance.



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

    Microsoft Student Partner 2010 / 2011
    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
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations
    Microsoft Certified IT Professional: Enterprise Administrator
    Microsoft Certified IT Professional: Server Administrator
    Microsoft Certified Trainer

    Saturday, February 11, 2012 8:48 PM
  • The above have been done, but still experiencing issues.

    DMPs here

    Thank you

    Sunday, February 12, 2012 2:02 PM
  • *******************************************************************************
    *                                                                             *
    *                        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: fffffa8022b86dc8, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff88001951247, If non-zero, the instruction address which referenced the bad memory
    address.
    Arg4: 0000000000000002, (reserved)


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




    Could not read faulting driver name


    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d0c100
     fffffa8022b86dc8 


    FAULTING_IP: 
    volsnap!VspWriteVolumePhase25+27
    fffff880`01951247 4c8bb398030000  mov     r14,qword ptr [rbx+398h]


    MM_INTERNAL_CODE:  2


    CUSTOMER_CRASH_COUNT:  1


    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT


    BUGCHECK_STR:  0x50


    PROCESS_NAME:  System


    CURRENT_IRQL:  0


    TRAP_FRAME:  fffff880033bea80 -- (.trap 0xfffff880033bea80)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000009b00 rbx=0000000000000000 rcx=fffffa8004293b70
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff88001951247 rsp=fffff880033bec10 rbp=fffffa8002b615f0
     r8=00000000000038f8  r9=fffff88007183c00 r10=0000000000000000
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    volsnap!VspWriteVolumePhase25+0x27:
    fffff880`01951247 4c8bb398030000  mov     r14,qword ptr [rbx+398h] ds:00000000`00000398=????????????????
    Resetting default scope


    LAST_CONTROL_TRANSFER:  from fffff80002a843f0 to fffff80002ad9c40


    STACK_TEXT:  
    fffff880`033be918 fffff800`02a843f0 : 00000000`00000050 fffffa80`22b86dc8 00000000`00000000 fffff880`033bea80 : nt!KeBugCheckEx
    fffff880`033be920 fffff800`02ad7d6e : 00000000`00000000 fffffa80`22b86dc8 00000000`00000000 fffffa80`02b86a30 : nt! ?? ::FNODOBFM::`string'+0x447c6
    fffff880`033bea80 fffff880`01951247 : 00000000`0000a9fe fffffa80`02b87c68 00000000`00000000 fffff880`01938900 : nt!KiPageFault+0x16e
    fffff880`033bec10 fffff880`01951acc : fffffa80`04293b70 fffffa80`02b615f0 fffffa80`02b86a30 fffffa80`04293bc8 : volsnap!VspWriteVolumePhase25+0x27
    fffff880`033becd0 fffff880`019389ad : fffffa80`04293bc8 fffffa80`02b615f0 fffffa80`02b61540 fffffa80`0420e088 : volsnap!VspWriteVolumePhase22+0x2c
    fffff880`033bed00 fffff800`02d74fee : fffffa80`02b87b60 00000000`00000080 fffffa80`02455890 fffffa80`02b87b60 : volsnap!VspWorkerThread+0xad
    fffff880`033bed40 fffff800`02acb5e6 : fffff880`009e8180 fffffa80`02b87b60 fffff880`009f2f40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`033bed80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16




    STACK_COMMAND:  kb


    FOLLOWUP_IP: 
    volsnap!VspWriteVolumePhase25+27
    fffff880`01951247 4c8bb398030000  mov     r14,qword ptr [rbx+398h]


    SYMBOL_STACK_INDEX:  3


    SYMBOL_NAME:  volsnap!VspWriteVolumePhase25+27


    FOLLOWUP_NAME:  MachineOwner


    MODULE_NAME: volsnap


    IMAGE_NAME:  volsnap.sys


    DEBUG_FLR_IMAGE_TIMESTAMP:  4ce792c8


    FAILURE_BUCKET_ID:  X64_0x50_volsnap!VspWriteVolumePhase25+27


    BUCKET_ID:  X64_0x50_volsnap!VspWriteVolumePhase25+27


    Followup: MachineOwner

    -----------------------------------------------------------------------------------------------------------------------------

    Bug Check Code 0x50: http://msdn.microsoft.com/en-us/library/windows/hardware/ff559023(v=vs.85).aspx

    The BSOD was caused due to volsnap.sys driver. More about it: http://www.file.net/process/volsnap.sys.html

    It may be corrupt. For that, please proceed like that:

    • Run sfc /scannow
    • Run chkdsk /r /f

    Once done, check results.

    Possible that you have HDD failures. For hardware diagnosis, contact your manufacturer Technical Support.

    You can also contact Microsoft CSS for assistance.



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

    Microsoft Student Partner 2010 / 2011
    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
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations
    Microsoft Certified IT Professional: Enterprise Administrator
    Microsoft Certified IT Professional: Server Administrator
    Microsoft Certified Trainer

    • Proposed as answer by Arthur Xie Monday, February 13, 2012 6:05 AM
    • Marked as answer by Arthur Xie Tuesday, February 21, 2012 6:16 AM
    Sunday, February 12, 2012 2:32 PM
  • It points to corrupt/defective solid state drive

    I'll conclude it when I find out

    Thanks everyone for the input!

    Monday, February 13, 2012 3:43 AM
  • This actually was motherboard went bad.

    Everything else was replaced with OS each time. I think one of the techs may have broke a capacitor.

    Starting getting video artifacts (new vid card too), hard freezes, and the like.

    Recommended replacing computer. We tried

    Thanks again. Learned something

    Tuesday, February 21, 2012 2:15 PM