Frequent BSOD - 6 of the last 7 I wasn't using using PC

I haven't really identified any specific cause so I'll give you the history of the computer. It's a used gaming system that I got from a friend who was upgrading. He says he didn't overclock it or anything like that. My old system had WinXP booting from the D: drive and Win7-64 Pro installed on a new C: drive. When I restored the backup of the C: drive, it wouldn't boot (obviously). So I took it to one of the PC geeks at work who does all the PC office equipment and he got my Win7 installed. I have 2 brand new Seagate 1Tb drives in the system but he insisted that I needed Win7 installed on a separate small drive so I could eventually convert to a SSD. He generously donated a Seagate that he had lying around (aka unknown age and origin). I know my old hard-drive died sometime around the end of April, the first BSOD that shows in BlueScreen Viewer is in mid-May and I've been fighting with it ever since. I thought it was Poser Pro 2014, which runs really hot, so I tried to put a better heatsync in the system, fried the motherboard, got an ASRocks Z77 Extreme4 for replacement and took the PC went back to my co-worker. That seemed to fix things for a month or so. There seem to be a few things that might have triggered the BSOD, since obviously it's not Poser Pro 2014 overheating my system. One thing I've heard, though, it that Poser Pro apparently plays nicer with NVIDIA cards but isn't supposed have problems with AMD- I'm sceptical but I'm also prejudiced since I've had problems before with my other system - it could have just been the video but putting an NVDIA card in fixed (and I do still have that card - not state of the art but not a dog - GeForce GT403 1024 Mb DDR3). I've got two additional hard-drives that are plugged into a dual-port docking station (USB 3.0). When I powered them back up and set Acronis True Image 2013 to start automatic backups, it seemd I got more BSOD then. So I powered the external drives off, forgot to turn off Acronis backups - got more BSOD (6 in a row when I wasn't even using the system). So I disabled all that and the last BSOD happened when I was just surfing the internet. I hope somebody can help. I don't want to bother the co-worker since he's been very generous with his time and refused to accept any payment. I'm pretty computer savvy but this has me stumped.

By the way, CPUID Hardware Monitor reports that my video card is Radeon HD 6870.

Welcome to Seven Forums.

Code:

Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533 
Debug session time: Thu Sep 19 08:37:10.571 2013 (UTC + 6:00) 
System Uptime: 0 days 9:21:00.398 
BugCheck A, {4dab0010, 2, 1, fffff800038bc622} 
Probably caused by : ntkrnlmp.exe ( nt!KxWaitForLockOwnerShip+12 ) 
BUGCHECK_STR:  0xA 
PROCESS_NAME:  iexplore.exe 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` 
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533 
Debug session time: Wed Sep 18 23:15:00.277 2013 (UTC + 6:00) 
System Uptime: 0 days 6:07:12.105 
BugCheck A, {4ee90010, 2, 1, fffff800038bf622} 
Probably caused by : ntkrnlmp.exe ( nt!KxWaitForLockOwnerShip+12 ) 
BUGCHECK_STR:  0xA 
PROCESS_NAME:  svchost.exe 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` 
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533 
Debug session time: Tue Sep 17 15:07:22.056 2013 (UTC + 6:00) 
System Uptime: 0 days 19:10:42.883 
BugCheck A, {326e000d, 2, 1, fffff800038fa622} 
Probably caused by : ntkrnlmp.exe ( nt!KxWaitForLockOwnerShip+12 ) 
BUGCHECK_STR:  0xA 
PROCESS_NAME:  ccsvchst.exe 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` 
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533 
Debug session time: Mon Sep 16 19:55:21.788 2013 (UTC + 6:00) 
System Uptime: 0 days 2:45:23.615 
BugCheck A, {484c0010, 2, 1, fffff80003904622} 
Probably caused by : ntkrnlmp.exe ( nt!KxWaitForLockOwnerShip+12 ) 
BUGCHECK_STR:  0xA 
PROCESS_NAME:  ccsvchst.exe 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` 
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533 
Debug session time: Mon Sep 16 17:08:48.601 2013 (UTC + 6:00) 
System Uptime: 0 days 0:57:51.428 
BugCheck A, {3a410010, 2, 1, fffff800038fa622} 
Probably caused by : ntkrnlmp.exe ( nt!KxWaitForLockOwnerShip+12 ) 
BUGCHECK_STR:  0xA 
PROCESS_NAME:  ccsvchst.exe 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` 
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533 
Debug session time: Mon Sep 16 16:09:43.110 2013 (UTC + 6:00) 
System Uptime: 0 days 2:40:14.938 
BugCheck A, {16d6c0010, 2, 1, fffff8000390a622} 
Probably caused by : ntkrnlmp.exe ( nt!KxWaitForLockOwnerShip+12 ) 
BUGCHECK_STR:  0xA 
PROCESS_NAME:  ccsvchst.exe 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` 
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533 
Debug session time: Mon Sep 16 13:27:59.064 2013 (UTC + 6:00) 
System Uptime: 5 days 7:55:31.599 
BugCheck A, {12b6070010, 2, 1, fffff800038c4622} 
Probably caused by : ntkrnlmp.exe ( nt!KxWaitForLockOwnerShip+12 ) 
BUGCHECK_STR:  0xA 
PROCESS_NAME:  ccsvchst.exe 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` 
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533 
Debug session time: Wed Sep  4 04:05:12.094 2013 (UTC + 6:00) 
System Uptime: 2 days 23:25:43.921 
BugCheck A, {2940ef0000, 2, 1, fffff800038f2622} 
Probably caused by : ntkrnlmp.exe ( nt!KxWaitForLockOwnerShip+12 ) 
BUGCHECK_STR:  0xA 
PROCESS_NAME:  SearchIndexer. 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Based on the bugchecks, I would recommend you follow and complete the steps given below:

1. If you are overclocking any hardware, please stop. Reset any changed values back to default and reset/clear CMOS: Clear CMOS - 3 Ways to Clear the CMOS - Reset BIOS. Uninstall any overclocking tool as these can also be a reason of blue screens.

2. Uninstall your current antivirus software. It is a known cause of BSOD's. Please remove it with its removal tool and use Microsoft Security Essentials in its place. Malwarebytes is a great combination with it. Go through this thread for more info.

3. Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log

4. Run SFC /SCANNOW Command - System File Checker to check windows for integrity violations. Run it up to three times to fix all errors. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.

5. Make scans with Kaspersky TDSskiller and ESET Online scanner.

6. Perform a Clean Start up, this will help avoid any problematic applications from bugging the system.

7. Use Revo Uninstaller Free to uninstall stubborn software. Opt for Advanced Mode and uninstall the software, delete the leftover registry entries.

• I would also recommend that you uninstall Acronis software for the time being.

8. Use Crystal Disk Info to upload a screenshot of your Hard Drives (s). Test your Hard Drives (s) running a Hard Drive Diag.

9. Test and Diagnose RAM issues with RAM - Test with Memtest86+. Pay close attention to Part 3 of the tutorial "If you have errors" Take the test for at least 7-10 passes. It may take up to 22 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold.

Let us know the results.

Take your time.

I started with MemTest since I had already downloaded it and prepared a flash drive. I did actually start running it last night with the PC warm and I got errors. Since the instructions said to quit, I powered the pc off. I just started the test again cold, as you advised and it's running fine. Much longer that it did last night - it's up to Pass 44%, Test 43%, Test #7 (no passes completed yet). Since it failed last night, should I just go ahead with testing each memory stick or let it run and see how far it gets before it fails?

Also I was reading my mobo manual and it only describes putting two matching memory sticks in alternating slots and says that in any other configuration, "it will be unable to activate Dual Channel Memory Technology". Is that a problem?

EDIT: pass1 completed.. I just remembered my desktop isn't connected to the internet right now, so no updates can run. I wonder if that's why Memtest isn't showing any problems. It's certainly warm enough. It's been running for 1 1/2 hours. Which bring up another question... what's the difference between starting Memtest cold and letting it run for many hours (which gets it good hot anyway) vs starting it warm?

Your machine will run better in dual chanel mode and you'll get better performance from your ram. But, you can run in single chanel mode and it will not cause problems, just lower performance. Go into bios and make sure the frequency, timings and voltage are set to the Manufacturer's specs. It will tell you on stickers on the side of the ram sticks if you don't know the specs. This is important. And make sure the Dimm voltage is correct. Having said that, I would run 1 stick at a time in each slot for 8 passes, run them 1 at a time. The reason is to check if the ram is bad or the motherboard has a bad Dimm slot. Bad ram will cause all kinds of errors. Did you go to bios and set optimized defaults? If not, do that but after doing it, set the ram again, set the sata controller to what it is right now and set the boot order.

What CPU cooler are you using and what are your CPU and GPU temps? I use Core temp for CPU temps. You cannot have Nvidia and AMD drivers installed at the same time. They will not play nice together. Unless I misunderstood, it seems that your problems got much worse when you started using Acronis. I used it once and had to do a clean install to get rid of all the problems it caused.

Back to the ram. If it were me, I would take 1 stick of ram that passes in the first slot and run it in each slot to make sure I didn't have a dimm slot problem. If it passes in all slots, RMA the ram. As far as I'm concerned if it fails it is bad. Period. I don't know what brand you have but most top rated manufacturers have lifetime warranties. But, you will be without a computer for several weeks. You should also run windows updates until there are no more.

Windows 7 is nothing like XP. If you are playing games in windows 7 that were installed from XP, that could cause issues. Windows 7 is far superior to XP. Also, when you installed windows 7, did you go to your motherboard's web site and download all drivers? If not, you really need to do that. Get the windows 7 drivers. Most of the newer boards state they will not run on anything less than XP SP 3 or later.

Most of the free programs want to install unwanted software, just uncheck the box and opt out. As far as the memory, if it failed there is a good likelihood that it most, if not all of your problems. But, a new motherboard does not rule out a bad Dimm slot. I've bought brand new ones with bad Dimm slots. I don't know who made your ram, but most major manufacturers give a lifetime warranty. If you RMA it, rma all of it to get a set of ram. Ram in sets are tested to work well together. But, that means you are out of a computer for 3 weeks or so unless they will do an advanced RMA. Individual sticks, even same specs often won't work together right. When you run memtest86+, you can stop the test as soon as you get an error. PoserPro is a 3D graphics program isn't it? (just curiosity). What type temps do you get when using it? I think I would take care of the bad ram first and then see if you still have problems. A ram error can cause false readings on other tests.

What you are doing is testing the Ram stick as well as the dimm slots. No, you will not fry your board doing that. But, the idea is if you run a stick that passes in 3 slots but fails in the 4th slot, the problem is most likely the dimm slot and not the ram. What the manual tells you is about running in dual chanel mode which is always the best way to run ram. But, for testing you can run 1 dimm at a time in any slot. But, just for your info. Each pass consists of 10 tests, eash pass tests a diferent thing. That's why 8 passes is usually recommended. It usually takes a minimum of 8 passes to fully check the ram stick. I'm waiting on them to come out with a faster test. I have 16GB and it takes forever to run it. I pitty the poor guys who have 64Gb. I imagine it would take 3 days to run 8 passes on that. Memtest86+ just came out with a newer test that says it's supposed to be faster and better.
V5.01, I don't know if it is faster but I just got some new ram yesterday so I'll know soon.