BlueScreen error


  1. BAZ
    Posts : 78
    Windows 7 Ultimate x86
       #1

    BlueScreen error


    My system automatically restarts with BlueScreen error. It has occurred twice when I tried to install Photoshop CS5 Extended. It goes fine until about 50% installation, and then that blue screen appears, and afterwards it gives that message saying system recovered from an unexpected shut-down.

    I think my system fulfils the minimum requirements for Photoshop CS5, but now I am having some doubts because of this problem. Attached are one file and 2 pics, which I thought would help you help me.

    Thanks
      My Computer


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

    BAZ said:
    My system automatically restarts with BlueScreen error. It has occurred twice when I tried to install Photoshop CS5 Extended. It goes fine until about 50% installation, and then that blue screen appears, and afterwards it gives that message saying system recovered from an unexpected shut-down.

    I think my system fulfils the minimum requirements for Photoshop CS5, but now I am having some doubts because of this problem. Attached are one file and 2 pics, which I thought would help you help me.

    Thanks
    these were caused by your windrvNT.sys which is a component of your folderlock. I would uninstall it just to test and if it fixes it the problem uninstall it.

    Code:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\K\Desktop\Minidumps\050110-17986-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*F:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16539.x86fre.win7_gdr.100226-1909
    Machine Name:
    Kernel base = 0x82a05000 PsLoadedModuleList = 0x82b4d810
    Debug session time: Sat May  1 15:58:51.428 2010 (GMT-4)
    System Uptime: 0 days 5:00:01.753
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .............................
    Loading User Symbols
    Loading unloaded module list
    ......
    Unable to load image \??\C:\Windows\system32\windrvNT.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for windrvNT.sys
    *** ERROR: Module load completed but symbols could not be loaded for windrvNT.sys
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1000008E, {c0000005, 95aea703, af424c40, 0}
    
    Probably caused by : windrvNT.sys ( windrvNT+1703 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
    This is a very common bugcheck.  Usually the exception address pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this address.
    Some common problems are exception code 0x80000003.  This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG.  This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG.  This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: c0000005, The exception code that was not handled
    Arg2: 95aea703, The address that the exception occurred at
    Arg3: af424c40, Trap Frame
    Arg4: 00000000
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    FAULTING_IP: 
    windrvNT+1703
    95aea703 668b08          mov     cx,word ptr [eax]
    
    TRAP_FRAME:  af424c40 -- (.trap 0xffffffffaf424c40)
    ErrCode = 00000000
    eax=00000000 ebx=95aee142 ecx=00000000 edx=0077aa6e esi=0015e4a8 edi=00000000
    eip=95aea703 esp=af424cb4 ebp=af424cd4 iopl=0         nv up ei pl zr na pe nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
    windrvNT+0x1703:
    95aea703 668b08          mov     cx,word ptr [eax]        ds:0023:00000000=????
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x8E
    
    PROCESS_NAME:  Adobe AIR Appl
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from 95aee23a to 95aea703
    
    STACK_TEXT:  
    WARNING: Stack unwind information not available. Following frames may be wrong.
    af424cd4 95aee23a 00000000 00000000 c0600130 windrvNT+0x1703
    af424d18 82a4844a 00000000 0015e4ac 0015e4bc windrvNT+0x523a
    af424d18 77aa64f4 00000000 0015e4ac 0015e4bc nt!KiFastCallEntry+0x12a
    0015e4c4 00000000 00000000 00000000 00000000 0x77aa64f4
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    windrvNT+1703
    95aea703 668b08          mov     cx,word ptr [eax]
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  windrvNT+1703
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: windrvNT
    
    IMAGE_NAME:  windrvNT.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  409f405c
    
    FAILURE_BUCKET_ID:  0x8E_windrvNT+1703
    
    BUCKET_ID:  0x8E_windrvNT+1703
    
    Followup: MachineOwner
    ---------
      My Computer


  3. BAZ
    Posts : 78
    Windows 7 Ultimate x86
    Thread Starter
       #3

    That just solved that problem! Thanks a lot! I uninstalled folder lock and everything is good now.

    Thanks
      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 20:36.
Find Us