My brother's computer: Lenovo v570 laptop running Windows 7, 64-bit Intel Core i5 pro
Posted this to Reddit 4 days ago, but of course, no one responded. Anyway, here:
My brother's computer: Lenovo v570 laptop running Windows 7, 64-bit Intel Core i5 processor, 750 GB hard drive, 6 GBs of RAM, integrated graphics
I'm trying to help my brother fix his laptop, but it's nearly impossible. I'm fairly well-versed in this type of black magic, but this was so unyielding that I'm forced to post here.
"The other night I tried starting my laptop, and it asked me if I wanted to go into startup repair or boot normally, which I thought was strange, and I just chose to start normally, and it BSOD'd before the time the login screen would usually come up. I figured there might be a potential issues because I had postponed restarting my computer a couple of days after Windows updates were done. I usually keep my computer clean, protected by Kaspersky and Malwarebytes, etc. so I figured that the update would be the most likely culprit.
I tried to do a system repair off the recovery hard drive, and it didn't work. Then I tried launching into safemode, still BSOD'd; the "last known good configuration" wouldn't boot either. I tried multiple system restore points, and they gave various errors. None worked, however. Some said it couldn't read the memory at some sort of address, and others said something about setupapi.dll. It's sort of time consuming to get the exact error.
I also tried sfc /scannow and it said there was a system repair pending and to restart to complete; I did that and it didn't work. We tried deleting pending.xml in winsxs, because I read that on the Microsoft support forums I found on Google. Didn't do anything. Someone also suggested using "dism.exe /image:C:\ /cleanup-image /revertpendingactions" which only ended in an "error 32" and it said that were was an error while accessing the image.
My brother and I backed up all the important files by using a hard drive enclosure, but if it's fixable, I'd rather fix it rather than starting from scratch again like I did last year. I also want to figure out if it's some sort of hardware issue like a memory or motherboard issue, or if it's some stupid software thing that could be easily fixed. Thanks in advance."
Update: We got the sfc /scannow to work, but it says there's no "integrity violations," so I don't get it.
Posted this to Reddit 4 days ago, but of course, no one responded. Anyway, here:
My brother's computer: Lenovo v570 laptop running Windows 7, 64-bit Intel Core i5 processor, 750 GB hard drive, 6 GBs of RAM, integrated graphics
I'm trying to help my brother fix his laptop, but it's nearly impossible. I'm fairly well-versed in this type of black magic, but this was so unyielding that I'm forced to post here.
"The other night I tried starting my laptop, and it asked me if I wanted to go into startup repair or boot normally, which I thought was strange, and I just chose to start normally, and it BSOD'd before the time the login screen would usually come up. I figured there might be a potential issues because I had postponed restarting my computer a couple of days after Windows updates were done. I usually keep my computer clean, protected by Kaspersky and Malwarebytes, etc. so I figured that the update would be the most likely culprit.
I tried to do a system repair off the recovery hard drive, and it didn't work. Then I tried launching into safemode, still BSOD'd; the "last known good configuration" wouldn't boot either. I tried multiple system restore points, and they gave various errors. None worked, however. Some said it couldn't read the memory at some sort of address, and others said something about setupapi.dll. It's sort of time consuming to get the exact error.
I also tried sfc /scannow and it said there was a system repair pending and to restart to complete; I did that and it didn't work. We tried deleting pending.xml in winsxs, because I read that on the Microsoft support forums I found on Google. Didn't do anything. Someone also suggested using "dism.exe /image:C:\ /cleanup-image /revertpendingactions" which only ended in an "error 32" and it said that were was an error while accessing the image.
My brother and I backed up all the important files by using a hard drive enclosure, but if it's fixable, I'd rather fix it rather than starting from scratch again like I did last year. I also want to figure out if it's some sort of hardware issue like a memory or motherboard issue, or if it's some stupid software thing that could be easily fixed. Thanks in advance."
Update: We got the sfc /scannow to work, but it says there's no "integrity violations," so I don't get it.