|
Post by maryloveslucy on Dec 2, 2013 21:58:45 GMT
|
|
|
Post by nickjohnson on Dec 3, 2013 16:02:16 GMT
Thanks, Steve. It seems to just be maxed out and running too hard. The blue memory dump screen keeps coming up and shutting it down. I'd just rather spend money on other things. Mary, this is no consolation but I write so as to help all who may be reading this. If your getting a "blue memory dump screen" then what is happening is actually a kernel mode stop error - popularly known as a BSOD - Blue Screen Of Death. Contrary to popular belief this is not a system "crash". It is in fact a controlled situation where some software running on your computer has attempted to write to an area of memory that it is not allowed access to. In response to the memory violation, Windows shuts down to prevent any "damage" and the memory dump is a diagnostic / forensic data source. The very first line of the dump that you may see on the screen, may or may not, give the name of the faulting module. So.... you may not need a new computer. But you do need to try and figure out what software has changed to give rise to the BSOD. It sometimes happens that apparently stable software starts to misbehave when system resources are low - but generally the more likely cause is the addition of something new. New in this context, includes new versions of existing software. Watch out for Windows updates / device drivers / changed virus scanners / whatever.
|
|
|
Post by maryloveslucy on Dec 4, 2013 0:29:30 GMT
Thanks, Steve. It seems to just be maxed out and running too hard. The blue memory dump screen keeps coming up and shutting it down. I'd just rather spend money on other things. Mary, this is no consolation but I write so as to help all who may be reading this. If your getting a "blue memory dump screen" then what is happening is actually a kernel mode stop error - popularly known as a BSOD - Blue Screen Of Death. Contrary to popular belief this is not a system "crash". It is in fact a controlled situation where some software running on your computer has attempted to write to an area of memory that it is not allowed access to. In response to the memory violation, Windows shuts down to prevent any "damage" and the memory dump is a diagnostic / forensic data source. The very first line of the dump that you may see on the screen, may or may not, give the name of the faulting module. So.... you may not need a new computer. But you do need to try and figure out what software has changed to give rise to the BSOD. It sometimes happens that apparently stable software starts to misbehave when system resources are low - but generally the more likely cause is the addition of something new. New in this context, includes new versions of existing software. Watch out for Windows updates / device drivers / changed virus scanners / whatever. Thank you, Nick. It seems to happen shortly after starting CS5. The other strange thing is that from what I have read I should have files for both 32 bit and 64 bit, but I can only find the 32 bit files and it is running 32 bit. Lightroom is running 64 bit. The on,y new things would be scheduled Windows updates. It has been going on for at least 6 months so I just don't use it, but it is the only system I have for editing. We got it in September of '09. I'll see what I can figure out...
|
|
|
Post by nickjohnson on Dec 4, 2013 9:44:38 GMT
Oh Hell - that long. If I where with you trying to fix this thing - this is what I'd do. 1) I'd make two (2) completely separate and independent copies of your hard disk - using a boot CD and something like Drive Snapshot. 2) I'd format and check the hard drive and then reload all the software - start with Windows - get it fully updated - then the virus scanner - then the apps, one by one. Now that is a daunting pile of work - but if you go get a new PC you will need to do most of that work anyway. Sorry - best I can do from this distance.
|
|
|
Post by maryloveslucy on Dec 4, 2013 11:27:13 GMT
Thank you, Ken. That's what we were thinking. No fun. Oh well...
|
|