BSoD Following Photoshop Install

[MountainKing]

Windows 7 64Bit
OEM Installed about 4 weeks ago
Brand new HDD at install, the rest of the hardware is about 9 months old

Scenario:
I installed a 30 day trial of Adobe PS CS5, today was the first day of the trial.

I created an image in PS and when I went to save it my PC froze and Blue Screened the moment I clicked on the "Save" button.

Photoshop may not be the cause of the crash but if it is I am going to uninstall it right away.

Please advise,
Thanks

 

[yowanvista]

A product from Eldos seems to have caused the BSOD, please remove such software
EldoS homepage
ASACPI.sys the 2005 version is a huge cause of BSODs

   Information

The 2005 version of this driver is a known BSOD cause.
Please visit this link: ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE
Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit" (it's about the 12th item down).
Download and install it.
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.sys file is date stamped from 2009 or 2010 (NOT 2005)

ASACPI.sys        fffff880`02fe2000    fffff880`02fea000    0x00008000    0x42476c4c    [B][COLOR=Red]28/03/2005[/COLOR][/B] 06:30:36

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffffffffffffff0, 0, fffff80002f6ee03, 0}

Unable to load image \??\C:\Windows\system32\drivers\cbfs3.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for cbfs3.sys
*** ERROR: Module load completed but symbols could not be loaded for cbfs3.sys

Could not read faulting driver name
Probably caused by : cbfs3.sys ( cbfs3+2e053 )


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

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f020e8
 fffffffffffffff0 

FAULTING_IP: 
nt!RtlCompareUnicodeString+b
fffff800`02f6ee03 0fb711          movzx   edx,word ptr [rcx]

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  Photoshop.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800aeb7480 -- (.trap 0xfffff8800aeb7480)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8a001f497e8 rbx=0000000000000000 rcx=fffffffffffffff0
rdx=fffff8a001f497e8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002f6ee03 rsp=fffff8800aeb7610 rbp=fffff8a001f497e0
 r8=fffff8a00358ac01  r9=0000000000000042 r10=fffff8a015a41cca
r11=fffff8a00358ae88 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
nt!RtlCompareUnicodeString+0xb:
fffff800`02f6ee03 0fb711          movzx   edx,word ptr [rcx] ds:b100:ffffffff`fffffff0=????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c7d2ac to fffff80002cd1640

STACK_TEXT:  
fffff880`0aeb7318 fffff800`02c7d2ac : 00000000`00000050 ffffffff`fffffff0 00000000`00000000 fffff880`0aeb7480 : nt!KeBugCheckEx
fffff880`0aeb7320 fffff800`02ccf76e : 00000000`00000000 ffffffff`fffffff0 fffffa80`08fadc00 fffff8a0`01f497f8 : nt! ?? ::FNODOBFM::`string'+0x4621f
fffff880`0aeb7480 fffff800`02f6ee03 : fffff8a0`01f497f8 fffff880`0444c0d4 fffff8a0`0358ae70 fffff8a0`0ec44170 : nt!KiPageFault+0x16e
fffff880`0aeb7610 fffff880`0444c053 : fffff8a0`01f497f8 fffff8a0`01f497e0 fffff8a0`02aa2128 fffff8a0`0358ae70 : nt!RtlCompareUnicodeString+0xb
fffff880`0aeb7650 fffff8a0`01f497f8 : fffff8a0`01f497e0 fffff8a0`02aa2128 fffff8a0`0358ae70 fffffa80`08dcbbb0 : cbfs3+0x2e053
fffff880`0aeb7658 fffff8a0`01f497e0 : fffff8a0`02aa2128 fffff8a0`0358ae70 fffffa80`08dcbbb0 fffff8a0`02aa2010 : 0xfffff8a0`01f497f8
fffff880`0aeb7660 fffff8a0`02aa2128 : fffff8a0`0358ae70 fffffa80`08dcbbb0 fffff8a0`02aa2010 fffffa80`0874d950 : 0xfffff8a0`01f497e0
fffff880`0aeb7668 fffff8a0`0358ae70 : fffffa80`08dcbbb0 fffff8a0`02aa2010 fffffa80`0874d950 fffffa80`08dcbbb0 : 0xfffff8a0`02aa2128
fffff880`0aeb7670 fffffa80`08dcbbb0 : fffff8a0`02aa2010 fffffa80`0874d950 fffffa80`08dcbbb0 00000000`00000000 : 0xfffff8a0`0358ae70
fffff880`0aeb7678 fffff8a0`02aa2010 : fffffa80`0874d950 fffffa80`08dcbbb0 00000000`00000000 fffff880`0444eddd : 0xfffffa80`08dcbbb0
fffff880`0aeb7680 fffffa80`0874d950 : fffffa80`08dcbbb0 00000000`00000000 fffff880`0444eddd fffff8a0`01f496e0 : 0xfffff8a0`02aa2010
fffff880`0aeb7688 fffffa80`08dcbbb0 : 00000000`00000000 fffff880`0444eddd fffff8a0`01f496e0 fffffa80`0874d800 : 0xfffffa80`0874d950
fffff880`0aeb7690 00000000`00000000 : fffff880`0444eddd fffff8a0`01f496e0 fffffa80`0874d800 fffff8a0`01f49630 : 0xfffffa80`08dcbbb0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
cbfs3+2e053
fffff880`0444c053 ??              ???

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  cbfs3+2e053

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: cbfs3

IMAGE_NAME:  cbfs3.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4cf3f857

FAILURE_BUCKET_ID:  X64_0x50_cbfs3+2e053

BUCKET_ID:  X64_0x50_cbfs3+2e053

Followup: MachineOwner
---------

 

[MountainKing]

Thank you for your fast response.

I had no idea what Eldos was but I did some googling and found my answer. I use Jungledisk for cloudbased storage and Jungledisk uses the Eldos Callback system for something in Jungledisk.. Forum «Callback File System»

The photoshop file I was saving was being saved to a Jungledisk location, so it all makes sense that the BSoD occurred when I saved that PSD file. Unfortunately getting rid of Jungledisk is not really an option as I need it for work, my company uses it as a virtual office network share.

I am going to approach Jungledisk, which is owned by Rackspace and see if they can help me address the problem... or maybe there is just a new version I should install.

One last question; can you point out the line in the error dump that indicated to you that Eldos/Jungledisk was the problem?

 

[yowanvista]

Thank you for your fast response.

I had no idea what Eldos was but I did some googling and found my answer. I use Jungledisk for cloudbased storage and Jungledisk uses the Eldos Callback system for something in Jungledisk.. Forum «Callback File System»

The photoshop file I was saving was being saved to a Jungledisk location, so it all makes sense that the BSoD occurred when I saved that PSD file. Unfortunately getting rid of Jungledisk is not really an option as I need it for work, my company uses it as a virtual office network share.

I am going to approach Jungledisk, which is owned by Rackspace and see if they can help me address the problem... or maybe there is just a new version I should install.

One last question; can you point out the line in the error dump that indicated to you that Eldos/Jungledisk was the problem?

cbfs.sys which ia part of that software is the direct cause

FOLLOWUP_IP:  cbfs3+2e053 fffff880`0444c053 ??              ???  SYMBOL_STACK_INDEX:  4  SYMBOL_NAME:  cbfs3+2e053  FOLLOWUP_NAME:  MachineOwner  MODULE_NAME: cbfs3  IMAGE_NAME:  cbfs3.sys  DEBUG_FLR_IMAGE_TIMESTAMP:  4cf3f857  FAILURE_BUCKET_ID:  X64_0x50_cbfs3+2e053  BUCKET_ID:  X64_0x50_cbfs3+2e053

BugCheck 50, {fffffffffffffff0, 0, fffff80002f6ee03, 0}  Unable to load image \??\C:\Windows\system32\drivers\cbfs3.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for cbfs3.sys *** ERROR: Module load completed but symbols could not be loaded for cbfs3.sys  Could not read faulting driver name Probably caused by : cbfs3.sys ( cbfs3+2e053 )

 

[MountainKing]

If anyone else happens to stumble upon this thread with the same problem, here is Jungledisk's KB article on the subject:

Blue Screen in Windows : Jungle Disk Support