Non-specific BSOD

Good News, I hope it works out well for you. Just tell Microsoft, your Motherboard died. Just wait awhile to make sure that's what the problem was. Let us know.

Jim, are you running on board graphics?

Before you do this create a system restore point. https://www.sevenforums.com/tutorials/697-system-restore-point-create.htmlThen I want you to leave it on for 24 hours of use. Don't just let it idle, use it. Do whatever you want. Play a game, watch you Tube Videos, watch a movie, whatever you want, just put it through it's paces. It will seem a little slow and lag a little. That's normal. Verifier puts stress on the drivers and tries to make them crash in order to identify which one is the trouble maker.

Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

What is Driver Verifier:
It puts stress on the drivers, and therefore it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How we know that DV is enabled:
It will make the system bit slow and sluggish.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there are no Restore points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

BTW, Yes, I know of Job quite well. Just be thankful you are only dealing with a computer and not what Job had to deal with. But, I understand the frustration very well too. Been there, Done that.

Good luck, my friend. I hope it tells us what we need to know.

Windows Update keeps failing due to a corrupt WcpStore.
Radar Preleaks are being reported "out the kazoo".
Appcrash is being reported on just about everything that runs.
Even Prefetch is failing.

There's so many questionable add-ons to this "new install", I don't know where to start debugging except with a Clean Install and audit every addition made to the system. It's still looking like a drive problem but there could be a faulty shell extension or Daemon tool causing file corruption.

Besides the motherboard drivers, Windows Update MUST complete before adding ANYTHING! Once the system is up to date and stable, create a restore point then add ONE item at a time and audit stability.

Forgot to mention:
Before shutting down to re-install, run TDSSKiller to make sure there's no root kits installed. A clean install will not remove those.
Get TDSSKiller from here: http://support.kaspersky.com/viruses/disinfection/5350

Ken, he ran a 'clean all' before the install. That would get rid of a root kit wouldn't it?

That should have cleaned the disk if the "all" parameter was used; Otherwise it would not.

Added: It should be done again!

The more I think about, perhaps it won't. If you read the specs on clear all, it clears partitions. BUT... some root kits will store themselves outside of a Windows partition. The TDSSKiller does direct disk I/O and looks at the disk, not at partitions per say.

He did the clean all command, see post # 35 (Non-specific BSOD) But it wouldn't hurt to run the TDSSKiller and do another Clean all.