Jump to content
IGNORED

BSOD every time i open Photoshop


Recommended Posts

my work pc dies every time i open photoshop... blue screen comes up with various warnings, mostly "BAD POOL HEADER". it started happening about 1 month ago and only happens with Pshop.

 

it's been suggested that there's an issue with memory but as far as diagnostic check suggests eveything is working ok. i've cleared temp files, defragged and disk clean-upped.

 

it's a 2 yr old HP touchsmart610 with 2gigs RAM.

 

any ideas what could be going wrong before i get some over-priced IT guy in?

jjbms1.jpg

 

  Reveal hidden contents

 

Link to comment
https://forum.watmm.com/topic/80038-bsod-every-time-i-open-photoshop/
Share on other sites

  On 8/7/2013 at 3:28 PM, patternoverlap said:

is your PS legit?

 

yup.

 

  On 8/7/2013 at 3:49 PM, Ego said:

Update your drivers. Primarily your GPU and Chipset drivers.

 

thanks, i'll try that.

jjbms1.jpg

 

  Reveal hidden contents

 

What happened about a month ago in terms of software installation/driver changes? Maybe run a system restore back to when all was well.

 

Edit - have you tried just reinstalling it?

I haven't eaten a Wagon Wheel since 07/11/07... ilovecubus.co.uk - 25ml of mp3 taken twice daily.

  On 8/7/2013 at 4:05 PM, mcbpete said:

What happened about a month ago in terms of software installation/driver changes? Maybe run a system restore back to when all was well.

 

Edit - have you tried just reinstalling it?

 

first BSOD happened after i loaded old cad software to look at some archived drawings. i un-installed this software, but it kept happening afterwards.

 

i've done a system restore to the day before loading the cad software, i've uninstalled/reinstalled pshop and i've ran anti-virus and malware checks.

 

 

  On 8/7/2013 at 4:05 PM, skibby said:

sounds like a memory or hard drive error :(

 

like irrepairable error?

jjbms1.jpg

 

  Reveal hidden contents

 

You can check for faulty ram with this - http://www.memtest86.com/

And your hard drive by running a surface scan. Best way to do that is Start -> Run -> Cmd

 

and on the command prompt type: chkdsk C: /f /r

 

It'll ask you if you want to run a scan on restart so just type 'y' and reboot.

I haven't eaten a Wagon Wheel since 07/11/07... ilovecubus.co.uk - 25ml of mp3 taken twice daily.

  On 8/7/2013 at 4:34 PM, mcbpete said:

And your hard drive by running a surface scan. Best way to do that is Start -> Run -> Cmd

 

and on the command prompt type: chkdsk C: /f /r

 

It'll ask you if you want to run a scan on restart so just type 'y' and reboot.

 

oh shit, i do not have permissions, have to run in "elevated mode?"

jjbms1.jpg

 

  Reveal hidden contents

 

Do you have the command prompt on the start menu (might be in the Accessories program group), if so right click it and press 'Run as administrator'

I haven't eaten a Wagon Wheel since 07/11/07... ilovecubus.co.uk - 25ml of mp3 taken twice daily.

try: start > cmd

sfc /scannow

 

installing older software may have overwritten a system library or something - that said a system restore should have fixed it

try rehashing your vista i/o's

 

 

  Reveal hidden contents

 

Check your event viewer for any sort of disk errors. If you go to system logs and filter it so only critical errors show.

 

You can check the application error logs too, see if they have any extra information.

 

If windows 7 right click Computer from start menu, and select manage

Expand Event Viewer on the left

Expand Windows Logs

Select System

On the right select "Filter Current Log"

Check "Error" and "Critical"

Scroll down and if you see any disk or NTFS errors, more than likely you have a bad hard drive.

  On 8/7/2013 at 4:26 PM, phling said:

 

  On 8/7/2013 at 4:05 PM, skibby said:

sounds like a memory or hard drive error :(

 

i agree, and i know this is tough but it's definitiley time to format the floppy drive.

 

8.gif

  On 8/8/2013 at 1:56 AM, goffer said:

Check your event viewer for any sort of disk errors. If you go to system logs and filter it so only critical errors show.

 

You can check the application error logs too, see if they have any extra information.

 

If windows 7 right click Computer from start menu, and select manage

Expand Event Viewer on the left

Expand Windows Logs

Select System

On the right select "Filter Current Log"

Check "Error" and "Critical"

Scroll down and if you see any disk or NTFS errors, more than likely you have a bad hard drive.

 

thanks, i need this kind of idiot-proof step by step. here's a part of the log, the critical errors seem to correspond with the BSOD's and go back to June and mostly say "user-mode driver problems"...

 

  Quote

 

 

Error 08/08/2013 09:25:06 BugCheck 1001 None
Error 08/08/2013 09:25:06 BugCheck 1005 None
Critical 08/08/2013 09:24:02 Kernel-Power 41 (63)
Error 07/08/2013 17:32:30 Service Control Manager 7006 None
Error 06/08/2013 17:33:35 Service Control Manager 7006 None
Error 06/08/2013 17:33:24 WindowsUpdateClient 20 Windows Update Agent
Error 06/08/2013 17:33:16 DistributedCOM 10010 None
Error 06/08/2013 12:22:09 BugCheck 1001 None
Error 06/08/2013 12:22:08 Service Control Manager 7006 None
Critical 06/08/2013 12:21:33 Kernel-Power 41 (63)
Critical 06/08/2013 12:17:25 DriverFrameworks-UserMode 10111 User-mode Driver problems.
Critical 06/08/2013 12:17:25 DriverFrameworks-UserMode 10110 User-mode Driver problems.

jjbms1.jpg

 

  Reveal hidden contents

 

  On 8/7/2013 at 5:27 PM, xf said:

try: start > cmd

sfc /scannow

 

installing older software may have overwritten a system library or something - that said a system restore should have fixed it

i don't have permissions to do this.

 

maybe i'll try a system restore further back. that log goffer found for me suggests the issues go further back than i thought.

jjbms1.jpg

 

  Reveal hidden contents

 

  On 8/8/2013 at 11:17 AM, keltoi said:

 

  On 8/7/2013 at 5:27 PM, xf said:

try: start > cmd

sfc /scannow

 

installing older software may have overwritten a system library or something - that said a system restore should have fixed it

i don't have permissions to do this.

 

 

when you type in "cmd" in that search field it should give you a list of programs and files somehow related to what you typed, the first in that list should be cmd.exe, right click on it and choose "run as administrator" and then try running the sfc thing.

Edited by eugene
  On 8/8/2013 at 3:12 PM, eugene said:

 

  On 8/8/2013 at 11:17 AM, keltoi said:

 

  On 8/7/2013 at 5:27 PM, xf said:

try: start > cmd

sfc /scannow

 

installing older software may have overwritten a system library or something - that said a system restore should have fixed it

i don't have permissions to do this.

 

 

when you type in "cmd" in that search field it should give you a list of programs and files somehow related to what you typed, the first in that list should be cmd.exe, right click on it and choose "run as administrator" and then try running the sfc thing.

 

 

done... it says "found no integrity violations".

jjbms1.jpg

 

  Reveal hidden contents

 

tbh reinstalling windows and all the needed software may take less time than finding the actual problem, you probably have a recovery partition if it's a legit hp desktop that'll streamline the process. you'll just have to back up some stuff before doing it.

Sorry to bump this up from the second page, but have you tried downloading the latest trial version of PS? Then you can see if its the software or your hardware.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Recently Browsing   1 Member

×
×