BSOD - While Downloading on Utorrent

[gmatbr]

Hello guys, I'm getting BSOD everytime I download a big file on Utorrent. I just attached the file as in the tutorial. I hope you guys have time to help me. Thank you.

 

[Thedoctor44]

I would run memtest86 for a start as there seems to be some memory corruption. http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

I would run this first as this seems to be the most obvious cause, then if that fails try these suggestions.

The other obvious cause are bad files on a HDD. Please run a disk check

http://www.sevenforums.com/tutorials/433-disk-check.html

If that finds no errors then I would run a samsung hard drive testing tool to see if the HDD is failing

http://support-us.samsung.com/cyber...leshooting_fr.jsp?idx=42990&modelname=SV0411N
The crash dumps don't contain that much information, most of these dumps can't find the driver responsible. So please run driver verifier as it will help find the cause of the problem.

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

You also seem to have a lot of programs launching on start up. Please visit here to turn them some off.
http://www.sevenforums.com/tutorials/1401-startup-programs-change.html
I would also download and run malwarebytes seen as you use programs like Utorrent.
https://www.malwarebytes.org/free/

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff6fc400947c8, 0, fffff80002a996d8, 9}


Could not read faulting driver name
Probably caused by : [COLOR="Red"]memory_corruption[/COLOR] ( nt!MiLockProtoPoolPage+38 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff6fc400947c8, [COLOR="red"]memory referenced.[/COLOR]
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80002a996d8, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000009, (reserved)