BSODs when watching flash movies, playing games, installing drivers...

... or looking at computer funny.

Reports attached.

System specs in my profile.

Here's a public link to a GDocs Spreadsheet with the relevant info:
https://docs.google.com/spreadsheet/...CNbUl48J#gid=0

Mobo: ASRock H61M/U3S3 LGA 1155 Intel H61 HDMI SATA 6Gb/s USB 3.0 Micro ATX Intel Motherboard
CPU: Intel Core i3-2100 3.1GHz Dual-Core 65W LGA1155
Memory: G.SKILL Value Series 8GB (2 x 4GB) 240-Pin DDR3 SDRAM DDR3 1333 (PC3 10600) Desktop Memory Model F3-10600CL9D-8GBNT
Video card: Sapphire Radeon HD 5850
OS: Win7 64-bit; student discount version (so I guess full retail?)

I'm stuck using a USB wireless adapter because there isn't space inside for a PCI ethernet card, and because the router is located somewhat far away (downstairs on other side of house).

Age: built summer 2011.
I've tried re-installing the OS from scratch a couple times.


There's really no rhyme or reason that I can discern. I've tried running CCleaner and such, to no avail.

Example of random crashing:
* Every now and then, shockwave will stop working in Chrome; sometimes I get a "memory referenced at ____________" type error, and a "click OK to close the program" box (which just turns off the shockwave plugin until I reload windows)
* I recently got a blue screen (I think from flash) and when I turned my computer back on, the wireless usb adapter wasn't loading. I reinstalled it. The first attempt to reinstall it produced a bluescreen, and it worked on the second try (after it rebooted). In retrospect, I probably could have just unplugged it and plugged it back in.

It's not BSODing so much that it's totally unusable, but even BSODing just several times a day is problematic. I get the feeling this is a driver problem, but I don't know how to identify the bad/redundant drivers and get rid of them.

Appears to be a "memory corruption" problem. This could be a memory module fault, wrong drivers loaded, corrupt system store or a virus. (or a combination) I would start by running spf scannow followed by Malwarebytes Anti-Malware (free version) in safe mode. If neither will run, run a memory test. Some corrupt system store errors showed up so you may end up having to do a Repair install of Windows.

carwiz said:

Appears to be a "memory corruption" problem. This could be a memory module fault, wrong drivers loaded, corrupt system store or a virus. (or a combination) I would start by running spf scannow followed by Malwarebytes Anti-Malware (free version) in safe mode. If neither will run, run a memory test. Some corrupt system store errors showed up so you may end up having to do a Repair install of Windows.

Thanks for the advice!

I ran scannow and Malwarebytes from a Safe Mode reboot. Malwarebytes didn't pick up anything, but scannow did indeed report some errors it couldn't fix. I've attached the log to this post.

I tried starting up with the Windows disc to do a repair, but it said the version on the disc couldn't repair the version on the drive.

Looks like there were a lot of Windows patches/updates that it couldn't resolve. There's also some pre-sp1 modules that were loaded. Did you remove updates to save space? Right click on the Action Center (flag in lower right) and click on Windows Update then Check for Updates.

Another thought came to mind. Have you been loading modules or programs individually in an attempt to fix a problem? There seems to be a lot of version mismatches. Now that you've run the sfc /scannow, re-run but use "sfc /verifyonly" (no quotes). This should list mis-matches.

sfc, sfc, sfc.... I'll get the letters straight sooner or later. I just noticed my first post. Glad you understood what I really meant.

carwiz said:

Did you remove updates to save space? Right click on the Action Center (flag in lower right) and click on Windows Update then Check for Updates.

I didn't remove any updates. Windows Update doesn't report any new updates.

A piece of background: I'm visiting home after some time away; I applied all new updates shortly after getting back.

carwiz said:

Another thought came to mind. Have you been loading modules or programs individually in an attempt to fix a problem? There seems to be a lot of version mismatches. Now that you've run the sfc /scannow, re-run but use "sfc /verifyonly" (no quotes). This should list mis-matches.

Loading modules or programs individually? I'm not sure I understand. I've tried reinstalling a few drivers, like ATI's graphics drivers. I also ran Driver Sweeper and CCleaner.

I ran the new SFC command, and have attached the results.

carwiz said:

sfc, sfc, sfc.... I'll get the letters straight sooner or later. I just noticed my first post. Glad you understood what I really meant.

Haha, no problem. Google straightened me out pretty quick when I checked.


I'm actually going to be leaving for a few weeks starting tomorrow, but after that I'll be back at this computer. I might bump the thread back up at that point. I won't be able to run any new tests until then, but I would be very curious to hear any theories you have as to how I might go about fixing this comp.

And once again, thank you! I'm blown away by your generosity.

I would plan on backing up any data you want to save. It looks like a Clean Windows Install is in your future. It looks to me that Windows store and shadow versions aren't matching for some reason. This could be why the Repair Install wouldn't run.

Bring this thread back up when you get back. By then, someone else might have a look and we can figure out the best approach.

carwiz said:

I would plan on backing up any data you want to save. It looks like a Clean Windows Install is in your future. It looks to me that Windows store and shadow versions aren't matching for some reason. This could be why the Repair Install wouldn't run.

Bring this thread back up when you get back. By then, someone else might have a look and we can figure out the best approach.

Thanks! Fortunately, I have DropBox running, so that should cover pretty much everything.

I'll bump this back up when I'm back and have access to my computer once again. It'll be wonderful if I can end this problem once and for all.

Thanks again for the help. +1'd.

carwiz said:

Bring this thread back up when you get back. By then, someone else might have a look and we can figure out the best approach.

I am home again and bumping this as suggested.