Constant Blue screens


  1. Posts : 5
    Windows 7 Ultimate 64bit
       #1

    Constant Blue screens


    Hey everyone,

    I recently purchased a Sony Vaio VPCCW21FD 14" laptop. It is an Intel Core i3 with 4gb RAM and Nvidia 310M Graphics card Running Win7 Ultimate 64bit.

    I am trying to attach a copy of my memory.dmp, but I get this error " 404 - File or directory not found.
    The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable. "

    Here are my two last bugchecks

    The computer has rebooted from a bugcheck. The bugcheck was: 0x000000b8 (0xfffffa8007c09b60, 0xfffff80003214c40,

    0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 042610-33072-01.

    The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001e (0x0000000000000000, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 042610-21247-01.
      My Computer


  2. Posts : 28,845
    Win 8 Release candidate 8400
       #2

    rlestage said:
    Hey everyone,

    I recently purchased a Sony Vaio VPCCW21FD 14" laptop. It is an Intel Core i3 with 4gb RAM and Nvidia 310M Graphics card Running Win7 Ultimate 64bit.

    I am trying to attach a copy of my memory.dmp, but I get this error " 404 - File or directory not found.
    The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable. "

    Here are my two last bugchecks

    The computer has rebooted from a bugcheck. The bugcheck was: 0x000000b8 (0xfffffa8007c09b60, 0xfffff80003214c40,

    0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 042610-33072-01.

    The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001e (0x0000000000000000, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 042610-21247-01.
    We do need the actual DMP file. try dragging it to your desktop. Use these to find and upload it. https://www.sevenforums.com/crash-loc...d-problem.html

    Ken
      My Computer


  3. Posts : 13,354
    Windows 7 Professional x64
       #3

    In addition to Ken's post, if your C:\Windows\Minidump folder is empty, upload the memory.dmp file found in C:\Windows to Rapidshare, and post a link here.
      My Computer


  4. Posts : 5
    Windows 7 Ultimate 64bit
    Thread Starter
       #4

    There we go, I've put all my mini dump files into this zip file.
    The two latest ones today at 9:39 and 10ish were the two recent ones.

    Is this what you guys need?
      My Computer


  5. Posts : 13,354
    Windows 7 Professional x64
       #5

    Pretty straightforward. Acronis True Image is causing the problem. I recommend uninstalling it completely.

    If you need an alternative backup program, see these tutorials:

    Backup and Restore

    Code:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\Jonathan\AppData\Local\Temp\Temp2_minidump.zip\041810-24242-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
    Machine Name:
    Kernel base = 0xfffff800`03004000 PsLoadedModuleList = 0xfffff800`03241e50
    Debug session time: Sun Apr 18 03:49:23.717 2010 (GMT-4)
    System Uptime: 0 days 0:09:43.982
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .....................................
    Loading User Symbols
    Loading unloaded module list
    ...
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 100000B8, {fffffa80055d3b60, fffff880009f2fc0, 0, 0}
    
    Unable to load image \SystemRoot\system32\DRIVERS\snapman.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for snapman.sys
    *** ERROR: Module load completed but symbols could not be loaded for snapman.sys
    Probably caused by : snapman.sys ( snapman+18e71 )
    
    Followup: MachineOwner
    ---------
    
    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    ATTEMPTED_SWITCH_FROM_DPC (b8)
    A wait operation, attach process, or yield was attempted from a DPC routine.
    This is an illegal operation and the stack track will lead to the offending
    code and original DPC routine.
    Arguments:
    Arg1: fffffa80055d3b60, Original thread which is the cause of the failure
    Arg2: fffff880009f2fc0, New thread
    Arg3: 0000000000000000, Stack address of the original thread
    Arg4: 0000000000000000
    
    Debugging Details:
    ------------------
    
    
    FAULTING_THREAD:  fffffa80055d3b60
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xB8
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    LAST_CONTROL_TRANSFER:  from fffff8000307b752 to fffff8000307a4da
    
    STACK_TEXT:  
    fffff880`033223e0 fffff800`0307b752 : 00000000`00000000 fffffa80`055d3b60 00000000`00000000 fffffa80`05f31000 : nt!KiSwapContext+0x7a
    fffff880`03322520 fffff800`0307d8af : fffffa80`0771aa30 00000000`00000000 0000000f`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x1d2
    fffff880`033225b0 fffff880`01b98e71 : fffff880`01bab100 fffff880`00000000 00000000`00000000 00000000`00000000 : nt!KeWaitForSingleObject+0x19f
    fffff880`03322650 fffff880`01bab100 : fffff880`00000000 00000000`00000000 00000000`00000000 fffff880`009e8180 : snapman+0x18e71
    fffff880`03322658 fffff880`00000000 : 00000000`00000000 00000000`00000000 fffff880`009e8180 fffff880`01bab140 : snapman+0x2b100
    fffff880`03322660 00000000`00000000 : 00000000`00000000 fffff880`009e8180 fffff880`01bab140 fffffa80`0550f428 : 0xfffff880`00000000
    
    
    STACK_COMMAND:  .thread 0xfffffa80055d3b60 ; kb
    
    FOLLOWUP_IP: 
    snapman+18e71
    fffff880`01b98e71 ??              ???
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  snapman+18e71
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: snapman
    
    IMAGE_NAME:  snapman.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  45265d99
    
    FAILURE_BUCKET_ID:  X64_0xB8_snapman+18e71
    
    BUCKET_ID:  X64_0xB8_snapman+18e71
    
    Followup: MachineOwner
    ---------
    
    1: kd> lmvm snapman
    start             end                 module name
    fffff880`01b80000 fffff880`01bb3000   snapman  T (no symbols)           
        Loaded symbol image file: snapman.sys
        Image path: \SystemRoot\system32\DRIVERS\snapman.sys
        Image name: snapman.sys
        Timestamp:        Fri Oct 06 09:43:53 2006 (45265D99)
        CheckSum:         000375F1
        ImageSize:        00033000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer


  6. Posts : 5
    Windows 7 Ultimate 64bit
    Thread Starter
       #6

    Uninstalled...thank you very much for your help. I'll check out the alternate options, as I've been happy with acronis...however not if it's causing me all this grief.
      My Computer


  7. Posts : 5
    Windows 7 Ultimate 64bit
    Thread Starter
       #7

    Oh one more thing,
    even though the bugcheck errors were different, it was all related to acronis?

    This was my full memory.dmp
    http://rapidshare.com/files/380460182/MEMORY.zip.html
      My Computer


  8. Posts : 13,354
    Windows 7 Professional x64
       #8

    Yep, all point to Acronis.

    Code:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\Jonathan\AppData\Local\Temp\Temp3_minidump.zip\042610-33072-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
    Machine Name:
    Kernel base = 0xfffff800`0301c000 PsLoadedModuleList = 0xfffff800`03259e50
    Debug session time: Mon Apr 26 12:38:03.138 2010 (GMT-4)
    System Uptime: 0 days 0:02:52.777
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .............................................
    Loading User Symbols
    Loading unloaded module list
    ...
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 100000B8, {fffffa8007c09b60, fffff80003214c40, 0, 0}
    
    Unable to load image \SystemRoot\system32\DRIVERS\snapman.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for snapman.sys
    *** ERROR: Module load completed but symbols could not be loaded for snapman.sys
    Probably caused by : snapman.sys ( snapman+18e71 )
    
    Followup: MachineOwner
    ---------
    Code:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\Jonathan\AppData\Local\Temp\Temp3_minidump.zip\041810-24242-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
    Machine Name:
    Kernel base = 0xfffff800`03004000 PsLoadedModuleList = 0xfffff800`03241e50
    Debug session time: Sun Apr 18 03:49:23.717 2010 (GMT-4)
    System Uptime: 0 days 0:09:43.982
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .....................................
    Loading User Symbols
    Loading unloaded module list
    ...
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 100000B8, {fffffa80055d3b60, fffff880009f2fc0, 0, 0}
    
    Unable to load image \SystemRoot\system32\DRIVERS\snapman.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for snapman.sys
    *** ERROR: Module load completed but symbols could not be loaded for snapman.sys
    Probably caused by : snapman.sys ( snapman+18e71 )
    
    Followup: MachineOwner
    ---------
      My Computer


  9. Posts : 5
    Windows 7 Ultimate 64bit
    Thread Starter
       #9

    Thanks Jonathan
      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 19:15.
Find Us