New fairly regular BS0D mostly when "idle", once whilst on youtube.

I've been getting a few BSODs recently.
Mostly when away from the computer, but once whilst browsing.
I have not changed any hardware.
I have moved the computer from one room to another and changed the ethernet cable connected.
I do not believe any damage could of been caused to the hardware when moving but I suppose it is a possibility. It took no noticeable bumps or shunts.

I have recently activated ssh with cygwin, which created a new privileged user. But I do not see how that should affect it.

I have also changed a setting in utorrent "Enable UPnP port mapping" and "Enable NAT-PMP port mapping" have both been activated. Again I don't see how this should cause BSOD but I'm trying to provide as much info as may be relevant.

I've attached the seven forums diag tool directory.

Thanks in advance for any help!

Not that I can weigh in on much here, but I can say that it's very unlikely that your uTorrent settings caused this; I use the same settings with no adverse effects :)

Cheers! Just wanted to include as much info as possible about anything that has changed.

I just want to also add that I've now set my dumps to capture kernel dumps in future in case this helps more. I'll upload if I've anymore.

I've had more crashes. This is the analysis of the kernel dump from my most recent:

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Machine Name:
Kernel base = 0xfffff800`02c4d000 PsLoadedModuleList = 0xfffff800`02e91670
Debug session time: Tue Sep 18 20:54:24.286 2012 (UTC + 1:00)
System Uptime: 0 days 1:30:30.987
Loading Kernel Symbols
...............................................................
................................................................
...............
Loading User Symbols

Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7E, {ffffffffc0000005, fffff80002cd5858, fffff880031bda38, fffff880031bd290}

Probably caused by : hardware ( nt!KxStartSystemThread+16 )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002cd5858, The address that the exception occurred at
Arg3: fffff880031bda38, Exception Record Address
Arg4: fffff880031bd290, Context Record Address

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!ExpWorkerThread+128
fffff800`02cd5858 0100            add     dword ptr [rax],eax

EXCEPTION_RECORD:  fffff880031bda38 -- (.exr 0xfffff880031bda38)
ExceptionAddress: fffff80002cd5858 (nt!ExpWorkerThread+0x0000000000000128)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000001
   Parameter[1]: 0000000000003c00
Attempt to write to address 0000000000003c00

CONTEXT:  fffff880031bd290 -- (.cxr 0xfffff880031bd290)
rax=0000000000003c00 rbx=fffff80002fbe610 rcx=fffffa8004de4730
rdx=0000000000000000 rsi=fffffa80039e2660 rdi=fffffa8004a03c10
rip=fffff80002cd5858 rsp=fffff880031bdc70 rbp=fffff80002e692d8
 r8=0000000000000000  r9=0000000000000000 r10=fffffa8004dcd900
r11=fffffa80039e2968 r12=fffffa8004a03c10 r13=0000000000000001
r14=0000000000000000 r15=0000000000000001
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
nt!ExpWorkerThread+0x128:
fffff800`02cd5858 0100            add     dword ptr [rax],eax ds:002b:00000000`00003c00=????????
Resetting default scope

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000001

EXCEPTION_PARAMETER2:  0000000000003c00

WRITE_ADDRESS:  0000000000003c00 

FOLLOWUP_IP: 
nt!KxStartSystemThread+16
fffff800`02cbcec6 48c7c10e000000  mov     rcx,0Eh

BUGCHECK_STR:  0x7E

MISALIGNED_IP: 
nt!ExpWorkerThread+128
fffff800`02cd5858 0100            add     dword ptr [rax],eax

LAST_CONTROL_TRANSFER:  from fffff80002f62e6a to fffff80002cd5858

STACK_TEXT:  
fffff880`031bdc70 fffff800`02f62e6a : fffffa80`039ff660 fffffa80`039e2660 00000000`00000080 fffffa80`039cd040 : nt!ExpWorkerThread+0x128
fffff880`031bdd00 fffff800`02cbcec6 : fffff880`02f63180 fffffa80`039e2660 fffff880`02f6dfc0 ffffff60`ffffff00 : nt!PspSystemThreadStartup+0x5a
fffff880`031bdd40 00000000`00000000 : fffff880`031be000 fffff880`031b8000 fffff880`031bd9a0 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KxStartSystemThread+16

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

STACK_COMMAND:  .cxr 0xfffff880031bd290 ; kb

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED

BUCKET_ID:  X64_IP_MISALIGNED

Followup: MachineOwner

I've attached the latest minidump etc.

Is there a recommended site for hosting larger memory dumps if that is necessary?

Not that I object, but mind if I ask the reasoning for the additional storage? I've a few games I can remove from the C drive and I'm well aware of the fact that my D (media) drive is massively insufficient anymore.
I intend to get a 2 or 3 TB drive down the line to replace D. But in the mean time, how much would you recommend freeing up of each?

The rest I shall try and sort out and get back.

EDIT::

If you suspect that disk drive space could be an issue, then does the increased activity of my D drive (which has very little space left) present an increased probability of BSOD? I know that this will be a lot more active (although mostly reads) due to changed settings in utorrent mentioned in the first post.