Photoshop Causes Blue Screen Crash

Page 5 of 8 FirstFirst ... 34567 ... LastLast

  1. Posts : 35
    Windows 7
    Thread Starter
       #41

    OK I'm headed to bed and I'm just about in tears after 3 hours of work.

    Ran everything, restarted and so forth.

    -I failed to follow Anak's instructions to save to "c:\progra~2\adobe" the first time. So the reinstall resulted in the same blue screen crash.

    -I manually uninstalled the exact same way I had before and reinstalled into "c:\progra~2\adobe" same blue screen crash all over again.

    -I suspect that all traces of Photoshop were not erased as the folders "AdobeBridge" "Common" "Help" and "Stock Photos" still existed. I deleted them and reinstalled. Same blue screen crash.


    I am attaching the mini dump file.

    -I also remembered "Adobe Image Ready" a program similar to Photoshop was installed at the same time in December 2009. It's still working fine.

    Clearly we need a new game plan.

    -I propose trying to find the source of the blue screen crash.

    -Or attempting to download a 30 free trial of Photoshop CS2 from Adobe's website. At least it will get me through the next 30 days. (if it works)

    -If that doesn't work downloading a 30 free trial of Photoshop CS6.

    I'm open to any other suggestions.
      My Computer


  2. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #42

    Alright, one thing that has not yet been tried: Run a Disk Check with both boxes checked for HDDs and with Automatically fix file system errors checked if you have an SSD. Report back with the logs; you can find them with Check Disk (chkdsk) - Read Event Viewer Log. You may need to search for wininit instead of chkdsk to find the logs.

    With both boxes checked, it may take a couple hours to run, so you may choose to do so when you go to bed. :)
      My Computer


  3. Posts : 35
    Windows 7
    Thread Starter
       #43

    Thanks for not giving up on me.

    It says it cannot run while C drive is in use. I tried it with all programs closed. How can I run a disk check on the C drive?
      My Computer


  4. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #44

    You will need to schedule it to run the next time Windows starts. Alternatively:

    Use Advanced Boot Options to select Repair Your Computer and get to the System Recovery Options. Then select the command prompt. Do the following:
    chkdsk /r c:
    chkdsk /r d:
    chkdsk /r e:
    chkdsk /r f:
    .etc until you get the message that the volume could not be opened for direct access. For any drives that do not give the message:
    Windows has checked the file system and found no problems
    run chkdsk again as above. In other words, if it says:
    Windows has made corrections to the file system
    after running the disk check, run the disk check again.

    I realize you may only have one disk show up in Windows explorer, but you may have more than one disk through recovery options. This is because the system creates a hidden boot partition (which will be C: in recovery), you may have a recovery partition for your PC that is hidden (which will be D: in recovery), and you will have your primary Windows partition (which may be E: in recovery). A custom PC will likely have at least C: and D: to scan.
      My Computer


  5. Posts : 5,605
    Originally Win 7 Hm Prem x64 Ver 6.1.7600 Build 7601-SP1 | Upgraded to Windows 10 December 14, 2019
       #45

    How did CHKDSK go?

    Your latest .dmp from post #42 still points to CLASSPNP.SYS, and adobelmsvc.exe as being the cause.

    Your Belarc report states that you have Adobe Premiere Pro CS3 installed, how is that running, does it crash when opened, can you use that instead?

    I will wait until your next reply before I suggest anything more.
      My Computer


  6. Posts : 35
    Windows 7
    Thread Starter
       #46

    Sorry about my lack of posts Saturday. I dread this problem but I KNOW I must conquer it.

    Last night I ran disk check. (Only on C. I'll run D now.) There was no report at all. After the scan the desktop appeared as normal. Photoshop still doesn't work.

    How can I find the log for last night's disk check?

    Anak: Since we know these two issues may be the cause, what can we do about them?

    I'll check back hourly this Sunday afternoon.
      My Computer


  7. Posts : 35
    Windows 7
    Thread Starter
       #47

    D drive scan complete. While there was no way to save or copy and paste the report it said there were 0 problems found.

    Should I scan my external drives as well? This'll take at least 3 hours.

    Adobe Premier CS3 is like photo shop for video editing. It's still working fine. So is Adobe Acrobat and Primo, and Image Ready. Just photoshop is causing the problem.
      My Computer


  8. Posts : 35
    Windows 7
    Thread Starter
       #48

    OK as of Sunday night, running the disk check on the external drive has already taken 5 hours and it's nowhere near done. It's a full 990G so this will be an over night project.

    Anak: what do the dump files tell us?

    Unless anyone has a better suggestion tomorrow I'm going to TRY and download the 30 day trial version of CS6. Unless there are any other scans you want me to run?
      My Computer


  9. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #49

    .dmp files still indicate CLASSPNP.SYS as the cause and adobelmsvc.exe as the process running when the crash occurred. Do you have any new .dmp files from today?
      My Computer


  10. Posts : 5,605
    Originally Win 7 Hm Prem x64 Ver 6.1.7600 Build 7601-SP1 | Upgraded to Windows 10 December 14, 2019
       #50

    How can I find the log for last night's disk check?
    See: Check Disk (chkdsk) - Read Event Viewer Log

    Anak: Since we know these two issues may be the cause, what can we do about them?
    I've discussed this with writhziden, and we both feel there is something fundamentally wrong with the installer on your machine, and instead of trying to fix it piecemeal you would see better results in doing a Recover Windows 7 Operating System Using HP Recovery - HP Customer Care (United States - English)
    This would entail having backups of all your important programs, and data files which I understand the HP recovery Manager will allow you to do.

    OK as of Sunday night, running the disk check on the external drive has already taken 5 hours and it's nowhere near done. It's a full 990G so this will be an over night project.
    Don't stop that DSKCHK or you can cause irreparable damage to that external drive, and no don't run any more scans on the External Drives, the problem resides on your main HDD.

    I see writhziden posted about the causes, here's the whole report. I put the offending causes in BOLD/RED:
    Code:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\Amln0\Desktop\Dollen G\051812-44413-01\051812-44413-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
    Machine Name:
    Kernel base = 0xfffff800`02c5a000 PsLoadedModuleList = 0xfffff800`02e9e650
    Debug session time: Fri May 18 20:49:59.900 2012 (GMT-4)
    System Uptime: 0 days 0:17:50.788
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ........................
    Loading User Symbols
    Loading unloaded module list
    .....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 50, {fffff88015f71f20, 1, fffffa80065e72e6, 2}
    
    
    Could not read faulting driver name
    Probably caused by : CLASSPNP.SYS ( CLASSPNP!ServiceTransferRequest+355 )
    
    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: fffff88015f71f20, memory referenced.
    Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
    Arg3: fffffa80065e72e6, If non-zero, the instruction address which referenced the bad memory
        address.
    Arg4: 0000000000000002, (reserved)
    
    Debugging Details:
    ------------------
    
    
    Could not read faulting driver name
    
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f08100
     fffff88015f71f20 
    
    FAULTING_IP: 
    +0
    fffffa80`065e72e6 f3aa            rep stos byte ptr [rdi]
    
    MM_INTERNAL_CODE:  2
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x50
    
    PROCESS_NAME:  Adobelmsvc.exe
    
    CURRENT_IRQL:  0
    
    TRAP_FRAME:  fffff880067914c0 -- (.trap 0xfffff880067914c0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=00000000f4fcb000
    rdx=0000000000000011 rsi=0000000000000000 rdi=0000000000000000
    rip=fffffa80065e72e6 rsp=fffff88006791658 rbp=fffffa8006dd2f70
     r8=00000000f4fcb000  r9=0000000000000001 r10=fffff8800af3cd20
    r11=0000fffffffff000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    fffffa80`065e72e6 f3aa            rep stos byte ptr [rdi]
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002c81c50 to fffff80002cd6c80
    
    STACK_TEXT:  
    fffff880`06791358 fffff800`02c81c50 : 00000000`00000050 fffff880`15f71f20 00000000`00000001 fffff880`067914c0 : nt!KeBugCheckEx
    fffff880`06791360 fffff800`02cd4dae : 00000000`00000001 fffff880`15f71f20 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x43d76
    fffff880`067914c0 fffffa80`065e72e6 : fffffa80`065e77e4 00000000`00000011 fffffa80`06dd2e10 fffffa80`00000001 : nt!KiPageFault+0x16e
    fffff880`06791658 fffffa80`065e77e4 : 00000000`00000011 fffffa80`06dd2e10 fffffa80`00000001 fffffa80`06dd2f70 : 0xfffffa80`065e72e6
    fffff880`06791660 00000000`00000011 : fffffa80`06dd2e10 fffffa80`00000001 fffffa80`06dd2f70 fffffa80`00000001 : 0xfffffa80`065e77e4
    fffff880`06791668 fffffa80`06dd2e10 : fffffa80`00000001 fffffa80`06dd2f70 fffffa80`00000001 fffffa80`00000000 : 0x11
    fffff880`06791670 fffffa80`00000001 : fffffa80`06dd2f70 fffffa80`00000001 fffffa80`00000000 00000000`00000200 : 0xfffffa80`06dd2e10
    fffff880`06791678 fffffa80`06dd2f70 : fffffa80`00000001 fffffa80`00000000 00000000`00000200 00000000`00000200 : 0xfffffa80`00000001
    fffff880`06791680 fffffa80`00000001 : fffffa80`00000000 00000000`00000200 00000000`00000200 fffffa80`06dd2f70 : 0xfffffa80`06dd2f70
    fffff880`06791688 fffffa80`00000000 : 00000000`00000200 00000000`00000200 fffffa80`06dd2f70 fffffa80`06dd2e10 : 0xfffffa80`00000001
    fffff880`06791690 00000000`00000200 : 00000000`00000200 fffffa80`06dd2f70 fffffa80`06dd2e10 fffffa80`06dd2e10 : 0xfffffa80`00000000
    fffff880`06791698 00000000`00000200 : fffffa80`06dd2f70 fffffa80`06dd2e10 fffffa80`06dd2e10 fffff880`00ebe7a7 : 0x200
    fffff880`067916a0 fffffa80`06dd2f70 : fffffa80`06dd2e10 fffffa80`06dd2e10 fffff880`00ebe7a7 fffffa80`06dd2e10 : 0x200
    fffff880`067916a8 fffffa80`06dd2e10 : fffffa80`06dd2e10 fffff880`00ebe7a7 fffffa80`06dd2e10 fffffa80`06dd2e10 : 0xfffffa80`06dd2f70
    fffff880`067916b0 fffffa80`06dd2e10 : fffff880`00ebe7a7 fffffa80`06dd2e10 fffffa80`06dd2e10 fffffa80`058e47a0 : 0xfffffa80`06dd2e10
    fffff880`067916b8 fffff880`00ebe7a7 : fffffa80`06dd2e10 fffffa80`06dd2e10 fffffa80`058e47a0 fffff8a0`11a1e518 : 0xfffffa80`06dd2e10
    fffff880`067916c0 fffff880`00ec6789 : fffff880`00ee4b50 fffff880`06791878 00000000`00000200 fffffa80`06dd2f70 : ACPI!ACPIDispatchForwardIrp+0x37
    fffff880`067916f0 fffff880`00ebea3f : fffff880`00ee4b50 fffffa80`05818a90 fffffa80`06dd2e10 00000000`00000000 : ACPI!ACPIIrpDispatchDeviceControl+0x75
    fffff880`06791720 fffff880`01978445 : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00000001 : ACPI!ACPIDispatchIrp+0x12b
    fffff880`067917a0 fffff880`01978975 : fffffa80`05b71010 fffffa80`058e47a0 00000000`0001f000 fffff880`00000000 : CLASSPNP!ServiceTransferRequest+0x355
    fffff880`06791840 fffff880`00f5e0af : fffffa80`0647f270 fffffa80`0647f270 fffffa80`0647f460 fffffa80`05e875f0 : CLASSPNP!ClassReadWrite+0xd5
    fffff880`06791890 fffff800`02f413c0 : fffffa80`0647f4a8 fffffa80`0649a8d0 fffffa80`077088f0 00000000`00000000 : partmgr!PmGlobalDispatch+0x9f
    fffff880`067918c0 fffff800`02f4105d : 00000000`00000000 fffff880`067919a0 fffffa80`0647f270 fffff800`02ccc8cd : nt!RawReadWriteDeviceControl+0xa8
    fffff880`06791900 fffff880`01150bcf : fffffa80`0647f4a8 fffffa80`05349c10 00000000`00000000 fffffa80`0647f270 : nt!RawDispatch+0x7d
    fffff880`06791960 fffff880`0114f6df : fffffa80`08365de0 00000000`00000001 fffffa80`08365d00 fffffa80`0647f270 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
    fffff880`067919f0 fffff800`02fddffb : 00000000`00000000 fffffa80`077088f0 00000000`00000001 fffffa80`0647f270 : fltmgr!FltpDispatch+0xcf
    fffff880`06791a50 fffff800`02fbf8a3 : fffffa80`077088f0 fffffa80`0647f201 fffffa80`077088f0 00000000`00000002 : nt!IopSynchronousServiceTail+0xfb
    fffff880`06791ac0 fffff800`02cd5f13 : 00000000`00000118 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtReadFile+0x631
    fffff880`06791bb0 00000000`756a2e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`0051f0f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x756a2e09
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    CLASSPNP!ServiceTransferRequest+355
    fffff880`01978445 85c0            test    eax,eax
    
    SYMBOL_STACK_INDEX:  13
    
    SYMBOL_NAME:  CLASSPNP!ServiceTransferRequest+355
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: CLASSPNP
    
    IMAGE_NAME:  CLASSPNP.SYS
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7929b
    
    FAILURE_BUCKET_ID:  X64_0x50_CLASSPNP!ServiceTransferRequest+355
    
    BUCKET_ID:  X64_0x50_CLASSPNP!ServiceTransferRequest+355
    
    Followup: MachineOwner
    ---------
    If you would like to read up on a Stop 0x50 error see: BSOD Index
    The ServiceTransferRequest points to a hotfix, but if you use it, and it doesn't fix it I believe you would definitely be looking at the Recovery option.
      My Computer


 
Page 5 of 8 FirstFirst ... 34567 ... LastLast

  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 18:14.
Find Us