BSOD with Adobe Software

Sir Stiggington

Well-Known Member
Joined
May 24, 2006
Messages
3,885
Location
Cambridge, UK
Car(s)
McLaren Mercedes MP4/23 :P
Hey guys, I have returned with another problem :p

Every time I open Adobe Acrobat, Adobe Premeire Elements 7, or Photoshop CS3, I get intermittent BSODs. Sometimes it works for 1 minute, sometimes it doesn't work at all.

I really think it's the Adobe software that's causing it cause it only happens then. The BSOD says it's a "disk.sys" error.

Specs:

Intel i7 920
6GB RAM
Asus GTX260
1TB SATA HD
Asus P6T
Windows Xp Pro 64 bit

Any ideas? Thanks ;)
 
Windows Xp Pro 64 bit

Problem right there :p

jokes aside, have you memtested your ram and hdd check for faults?

I don't think it's the program, but you can always re-install it to double check..

It's either the OS, memory, hdd or mobo ICH (south bridge) problem.
 
How about what BSOD code you're getting?

Are they always the same?
 
Yeah I think so, and it's always disk.sys

I'm pretty sure it's the program though, cause it does it 2-3 seconds after I launch any Adobe program, and never does it any other time...
 
Yeah I think so, and it's always disk.sys

I'm pretty sure it's the program though, cause it does it 2-3 seconds after I launch any Adobe program, and never does it any other time...

have you tried re-installing it? and just because it doesnt happen with other programmes, doesnt elminate the potential of a hardware problem.
 
So I let the thing do a memtest86 for the night, and no errors....now what, the BSODs are still happening...
 
okay, have you tried re-installing the program?

And can you post a screenshot of the BSOD? Or try google the exact error code and see if any other XP 64 bit users are getting the same problem.
 
Hate to ask, are you using legal versions? If not, that's probably the problem..

Why? If the pirated copies were problematic, many people would notice and complain... and nobody would share the torrent and it would eventually die off.
 
Why? If the pirated copies were problematic, many people would notice and complain... and nobody would share the torrent and it would eventually die off.


My point was, the pirated versions are usually full of virii and trojans. Plus, not everyone looks at comments or could download a keygen with crap on it.

I do find it slightly odd that only Adobe software has this problem.
 
They're all illegal, but they all come from different torrents, so I doubt that's the problem...and because of that, I doubt reinstalling it would do anything either...
 
still havnt been able to get that BSOD error code?
 
WHich one do you mean_ The big number with all the zeros?

And is there a place where the PC stores a log of the BSOD so I don't need to write the thing down and then type it back out?
 
Right guys, I ran the windows debugger to read the .dmp files created by the BSOD, and here is the report:

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini060609-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff800`01000000 PsLoadedModuleList = 0xfffff800`011d4140
Debug session time: Sat Jun 6 12:00:58.515 2009 (GMT+2)
System Uptime: 0 days 0:01:40.250
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
....
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffffadf918c5769, 0, fffffadf5c9e0290, 0}


Could not read faulting driver name
*** WARNING: Unable to verify timestamp for disk.sys
Probably caused by : disk.sys ( disk!DiskDeviceControl+3180 )

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

Hope you guys can point me in some direction, cause it's all gibberish to me ;)
 
I'm gonna be a huge asshole here and say I know exactly what all that means and could tell you what's going on....but since you bothered to pirate the Adobe crap, it's not going to happen.
 
I'm gonna be a huge asshole here and say I know exactly what all that means and could tell you what's going on....but since you bothered to pirate the Adobe crap, it's not going to happen.

When did Microsoft merge with Adobe? :rolleyes:
 
Top