Google has their own TLD now.
http://com.google

Here is what I have found from googling:
http://answers.microsoft.com/en-us/windows/forum/windows8_1-winapps/windows-81-memory-leak/ee9dea2f-b839-4637-bb66-c6dbf259a755#LastReply
This guy had pretty much the same problem that you are having. What caused it for him was Avira anti-virus. If that's what you use, disable it and see if your problem disappears. If that turns out to be the case and you need to find an alternative anti-virus, Avast free is pretty good (although I am not a fan of the paid version).

There is likely some program running with a memory leak. I had a similar problem on my laptop that was caused by Lenovo crapware with a slow memory leak that used up about a gigabyte a day.

To figure out what is causing the issue, open up the task manager and sort processes (I believe the tab is "processes" under windows 7, it is "details" under windows 8) by memory usage once you get to around 5GB used or so. Once you've found the culprit, uninstall it if you can. If it is a windows component such as explorer, the kernel (the "System" process), or an instance of svchost, then run an exhaustive scan for malware with your tools of choice.

Thankfully, archive.org crawled it before it was taken down.
https://web.archive.org/web/20150306113124/http://forum.utorrent.com/topic/95041-warning-epicscale-riskware-silently-installed-with-latest-utorrent/

Deluge is great. GTK+ on windows is a little clunky, but having a simple torrent client that does what you want and nothing else is well worth it.

Disclaimer: I have a fair amount of experience with troubleshooting windows by doing odd jobs over the years, but I am by no means an expert. Do your own research before doing anything drastic based off what I have to say.

What I generally use for troubleshooting blue screens is this nifty MSDN page that documents most blue screens. This subsection describes your specific bluescreen. Unfortunately, quite a few causes of that are hard drive related, so I would back up and look into getting a new hard drive if I were you. Better safe than sorry.

If you want to do your own digging or figure out what the first blue screen was, you can take a look at the event viewer. Any time windows shuts down uncleanly, it will leave a log entry which can be viewed later. This will tell you what stop code (if any) was thrown. You can view all of these logs by opening the event viewer and filtering the system log to event ID 41, as seen here:

http://puu.sh/goUYU/994a087e85.png

I like to fiddle with my system and break it regularly, so you will probably not have quite as many to dig through. Timestamp and blue screen information (called bug check in the logs) will be under the EventData tree.

Always check steamrep first. This guy was banned over a month ago. I agree with defy, the steam market is much safer to deal with in any case.

Writing a driver seems a tad out of the scope of this forum. You will probably have more luck over at MSDN.

The guy stole his avatar from a bungie.net admin who uses the alias "Achronos."
source
older source