Solved BSOD at random events but mostly when image processing

[OLJensa]

I have got BSOD at random times, but mostly when using a lot of memory in image processing and then opening another program or so.

Reformated the HDD and reinstalled everything. Updated everything to new drivers, but has got two BSOD:s after that (in like 3 days)

Can anyone of you experts please help me decode the attached log files and I'd be super happy!!

Thanks!!!

 

[YoYo155]

OLJensa , the dumps sometimes tell half the story.
please follow :: http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html

 

[OLJensa]

OLJensa , the dumps sometimes tell half the story.
please follow :: http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html

Just saw that, sorry, will do...

 

[OLJensa]

Sorry dont quite understand what kind of dump-file I should make, Kernel or mini or something else??

 

[YoYo155]

Obviously you PC is configured to generate dump file, just start with step number two.

2. Download and run the SF_Diagnostic_Tool.exe file to use the Grab All button as instructed in the tutorial link below.

 

[OLJensa]

Ok, here is the new and hopefully correct zip-file... Once again thanks a million!!!

 

[YoYo155]

The Bugcheck usually points to OS corruption / Disk issue:

NTFS_FILE_SYSTEM (24)

Arguments:
Arg1: 00000000001904fb
Arg2: fffff8800bf95ff8
Arg3: fffff8800bf95850
Arg4: fffff800030fbff3

FAILURE_BUCKET_ID:  X64_0x24_NULL_IP_nt!MmCopyToCachedPage+223

fffff880`0bf95028  fffff880`0122ec29 Ntfs! ?? ::FNODOBFM::`string'+0x11e6
fffff880`0bf952a8  fffff880`00dd2564 ataport!IdeStartDeviceRequest+0x1c0
fffff880`0bf955c8  fffff880`00db418c volmgr!VmReadWrite+0x11c

-==================================-


I'm seeing a driver that might be causing an issue:

fffff880`0bf95ba8  fffff880`0424f61a [COLOR=Red][U][B]avgidsdrivera[/B][/U][/COLOR]+0x1861a
fffff880`0bf959a8  fffff880`04247eb5 [COLOR=Red][B][U]avgidsdrivera[/U][/B][/COLOR]+0x10eb5
 [COLOR=Red][U][B]avgidsdrivera[/B][/U][/COLOR]+0x10eb5

• avgidsdrivera.sys :: Driver Reference Table

1. Remove AVG using, AVG Remover.
2. Install Microsoft Security Essentials for Windows instead.

-==================================-




A very old driver, part of Datacolor Spyder 3:

    Image path: \SystemRoot\system32\DRIVERS\Spyder3.sys
    Image name: Spyder3.sys
    Timestamp:        [COLOR=Red][U][B]Mon Sep 10 16:13:46 2007[/B][/U][/COLOR] (46E5430A)

• Spyder3.sys :: Driver Reference Table

Remove the software!
​

-==================================-



Use the SFC /scannow Command to identify and fix any corrupt OS files.

• http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

-==================================-




If problems persists update your SSD's firmware:

• Force 3 5.05a Firmware Update - Corsair Support
  

 

[OLJensa]

Wow!

Thanks Yoyo, you're awesome!

When running SFC /scannow I get to 9% and then get an error message, please see attached screen dump.
Sorry, this is in swedish, but it says: 'Damaged files where found, but some of them couldn't be repaired. Information can be found in CBS.log...'

Also attached the CBS log files (ziped)

Once again thanks!!

 

[OLJensa]

Found it further down on the sfc /scannow instructions page...

 

[OLJensa]

Ok, now I have replaced the one file manualy that I saw in the sfcdetailes file, and that seemes to be ok now.

But the sfc /scannow still stops at 9% reporting the same problem. Looking in the log-file the problem seemes to be described in the last four rows. What can you make out of it?

Thanks!!

Log-file attached...

 

[YoYo155]

Haha thanks for that, but we are not done yet.

I went though the CBS log you uploaded and it's not looking good unfortunately.
You appear to have problems with Windows Updates, errors such of these are difficult to recover from
and even if you do it will never work a 100% right, like it should.

My first step would be to backup ALL of your important data onto a reliable storage solution.
Once that is done do a System Restore and follow the SFC /SCANNOW Command tutorial again.
If errors are still found try a different restore point (although I doubt it will make a difference) and run SFC /scannow
once more. If the system is still not fixed I say a Clean Install is inorder.

Good luck!
Keep me posted.

 

[OLJensa]

Hi Yoyo!

Sorry for my late reply, I have been kind of busy trying to fix this darned computer of mine

Just wanted to say that I am very greatful for your help. I really appreciate it!!!!

Finally, after a few clean installs I stumbled upon a program called memtest86+, you probably know about it of course... Anyway, it clearly showed that something was very wrong with my hardware, and after a little testing I found out that it was one of the RAM modules that was corrupt... Removed the broken memorycard and after a new clean install everything worked perfectly.

Once again, thanks! A LOT!!!

 

[YoYo155]

Great to hear.
Thank you for updating with the cause .