Unknown BSOD on Mother-in-laws system

StaticBlue · 19 Apr 2015

My In-laws live at the bottom of the earth, in the South Island of New Zealand. They are farmers and I have been maintaining their computer through Teamviewer since they first were given one; so they could see their grandchild (now children) grow up via Skype.

Their system started having a hard drive fail, with Check Disk continually running on boot. I had this resolved by my Brother-in-law placing in a new drive and back-up drive. I then placed an image back on remotely from here in Australia, and the system updated nicely. I remotely tested the system over a period of a week, before letting the in-laws have it back. They now receive random BSOD’s. I can see the mini-dumps, though I’m not able to read such a file, having no experience.

The system also now refuses to update the last 3 Windows updates.

Update for Windows 7 for x64-based Systems (KB2952664), Error details: Code 80070570
Update for Windows 7 for x64-based Systems (KB3013410), Error details: Code 80070570
Security Update for Windows 7 for x64-based Systems (KB3033929), Error details: Code 80073712

I have tried resetting permissions using the tool from “Tweaking.com”, Windows Repair. This hasn’t resolved the issue of updates failing.

Your help would be greatly appreciated.

Cheers

StaticBlue · 19 Apr 2015

When trying to run a SFC /scannow I receive the following error:

Windows Resource Protection could not perform the requested operation.

To resolve this problem, perform the System File Checker scan in safe mode, and make sure that the PendingDeletes and PendingRenames folders exist under %WinDir%\WinSxS\Temp.

https://support.microsoft.com/en-us/kb/929833/

While their system has the one Temp folder mentioned, PendingRenames, and the permissions appear to be correct. Neither I nor my In-laws have the PendingDeletes folder, and my system works perfectly.

Cheers

Edit, the folder exists, just a hidden file.

cipley · 20 Apr 2015

Hello and welcome to seven forums :)

Code:

BugCheck 1000007E, {ffffffffc0000005, fffff88008b89f8a, fffff880029c4898, fffff880029c40f0}

Probably caused by : lvrs64.sys ( lvrs64+2f8a )

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address
....

your Logitech Camera Driver is causing the BSOD. It seems pretty outdated. I suggest you update to current version.

Logitech

Code:

Image name: lvrs64.sys
    Timestamp:        Wed Jan 18 13:40:36 2012 (4F166964)

There is also indication of driver misbehavior with Intel Storage driver,

Code:

fffff880`029c43a8  fffff880`0141f4a6*** WARNING: Unable to verify timestamp for iaStorA.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStorA.sys
 iaStorA+0x34a6

and Microsoft Storage Drivers,

Code:

fffff880`029c4038  fffff880`016ea300Unable to load image \SystemRoot\system32\DRIVERS\storport.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for storport.sys
*** ERROR: Module load completed but symbols could not be loaded for storport.sys
 storport+0x4300

which has some connection with your storage...
- Try to update the Intel Storage Drivers

Intel Download Center
- Try to run Check Disk with parameters since "Normal" check disk yields no result:

chkdsk /f /r

Let's see if it helps...
We need more info though, you can see here to supply more info so we can look into it further:

BSOD Posting Instructions

StaticBlue · 20 Apr 2015

Thanks, I have already updated the Logitech Driver, and that has resolved an issue with extremely dark images on the recipients end. I’ll update the others now and see if that resolves the issue.

I’ll also try chkdsk /f /r

Cheers

cipley · 20 Apr 2015

OK...let's see if there's any improvements