Non-specific BSOD

Great, just install 1 or 2 programs at a time then test them and make sure the computer is still stable, then install another 1 or 2. That way if you start having BSODs again, you will know what program is causing it.

If you get everything installed and stable, I would suggest sitting down and having a "Father Son' discussion about where not to go and know what you are downloading and where from. Lay down the rules for him. Put some good security on the system too.

toranaboy, maybe you should run some stress tests with it occasionally. Just idling or browsing won't really tell you a lot. maybe install a game or two and play them to see what kind of reaction you get from it. That was the problem to begin with. So, test it out. If you run stress tests, keep an eye on the temps of the CPU and Graphics card. If it gets too hot, stop the test or game.

Where is the file? I don't see it.

toranaboy, Hold on a little while, I'm going to try to get someone else to look at this. I can't get much from the dump files, other than 1 indicated an NFTS file system error which could be a bad had drive. In the mean time run chkdsk on the drive Disk Check if you use option 1 check both boxes, it will take a long time if you use option 2 run chkdsk C: /f /r Also, open an elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.

I think you're right on track Steve. Looks like a disk drive may be on it's way out.

wuaueng.dll (1028) SUS20ClientDataStore: The database page read from the file "C:\Windows\SoftwareDistribution\DataStore\DataStore.edb" at offset 98304 (0x0000000000018000) (database page 2 (0x2)) for 32768 (0x00008000) bytes failed verification. Bit 126985 was corrupted and has been corrected.

This problem is likely due to faulty hardware and may continue. Transient failures such as these can be a precursor to a catastrophic failure in the storage subsystem containing this file.

The error would indicate a problem with a disk drive. This could be the actual drive or the drive controller (motherboard). Check the motherboard OEM site for driver and BIOS updates, especially Chipset drivers. Also, the drive OEM may have a firmware update.

I'm not familiar with the "comment online" so can you expand on that?