Windows 7: BSOD while running utorrent.

Suur · 04 Feb 2012

Hello!

My problem is that every time I run utorrent I get a BSOD. Sometimes within 5 minuts and sometimes it takes up to an hour. Everything was fine before I did a clean install on my windows(A few weeks back). And as you can see I the ".dmp" files are a bit different. That might be because I updated my graphics card drivers (Geforce 8800GT) and I uninstalled my network drivers(Realtek RTL8201N), so windows reinstalled an older version and I'm using those at the moment. And I don't know what happend with the last one(didn't change anything).

I also ran a Memtest86+, here's the link to a picture:
http://i.cubeupload.com/WagBUI.jpg

And here's the link to my PC's specifications(graphics card is switched to Geforce 8800GT, since the original 8600GT stopped working, way before the new installation of windows):
HP Pavilion Elite m9065.sc Desktop PC Product Specifications HP Pavilion Elite m9065.sc Desktop PC - HP Customer Care (United States - English)

And I'm using Windows 7 Ultimate 64-bit.

mgorman87 · 04 Feb 2012

Crashes are blaming your network card driver

Code:

nvm62x64.sys Fri Oct 17 17:01:06 2008 (48F8FD12)

Download the chipset drivers for your motherboard. This will update your network card along with other chipset components - NVIDIA DRIVERS 15.49 WHQL

BSOD BUGCHECK SUMMARY

Code:


Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Feb  4 14:53:36.202 2012 (UTC - 5:00)
System Uptime: 0 days 10:27:59.106
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ndis.sys - 
*** WARNING: Unable to verify timestamp for nvm62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for nvm62x64.sys
Probably caused by : nvm62x64.sys ( nvm62x64+6578 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  uTorrent.exe
FAILURE_BUCKET_ID:  X64_0xA_nvm62x64+6578
BiosReleaseDate = 10/29/2007
SystemManufacturer = Hewlett-Packard
SystemProductName = MCP61P
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Fri Feb  3 16:20:46.713 2012 (UTC - 5:00)
System Uptime: 0 days 1:22:09.633
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
*** WARNING: Unable to verify timestamp for tdx.sys
*** ERROR: Module load completed but symbols could not be loaded for tdx.sys
Probably caused by : tdx.sys ( tdx+4e72 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0xD1_tdx+4e72
BiosReleaseDate = 10/29/2007
SystemManufacturer = Hewlett-Packard
SystemProductName = MCP61P
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Thu Feb  2 02:15:25.089 2012 (UTC - 5:00)
System Uptime: 0 days 0:20:53.868
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
*** WARNING: Unable to verify timestamp for tdx.sys
*** ERROR: Module load completed but symbols could not be loaded for tdx.sys
Probably caused by : tdx.sys ( tdx+4e72 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  firefox.exe
FAILURE_BUCKET_ID:  X64_0xD1_tdx+4e72
BiosReleaseDate = 10/29/2007
SystemManufacturer = Hewlett-Packard
SystemProductName = MCP61P
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Tue Jan 31 10:01:06.713 2012 (UTC - 5:00)
System Uptime: 0 days 5:31:15.617
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ndis.sys - 
*** WARNING: Unable to verify timestamp for nvm62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for nvm62x64.sys
Probably caused by : nvm62x64.sys ( nvm62x64+6578 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  uTorrent.exe
FAILURE_BUCKET_ID:  X64_0xA_nvm62x64+6578
BiosReleaseDate = 10/29/2007
SystemManufacturer = Hewlett-Packard
SystemProductName = MCP61P
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Jan 30 15:07:51.814 2012 (UTC - 5:00)
System Uptime: 0 days 1:00:16.718
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ndis.sys - 
*** WARNING: Unable to verify timestamp for nvmf6264.sys
*** ERROR: Module load completed but symbols could not be loaded for nvmf6264.sys
Probably caused by : nvmf6264.sys ( nvmf6264+69c3 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_nvmf6264+69c3
BiosReleaseDate = 10/29/2007
SystemManufacturer = Hewlett-Packard
SystemProductName = MCP61P
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Jan 28 06:54:20.141 2012 (UTC - 5:00)
System Uptime: 0 days 0:13:12.045
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ndis.sys - 
*** WARNING: Unable to verify timestamp for nvmf6264.sys
*** ERROR: Module load completed but symbols could not be loaded for nvmf6264.sys
Probably caused by : nvmf6264.sys ( nvmf6264+69c3 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  uTorrent.exe
FAILURE_BUCKET_ID:  X64_0xA_nvmf6264+69c3
BiosReleaseDate = 10/29/2007
SystemManufacturer = Hewlett-Packard
SystemProductName = MCP61P
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Fri Jan 27 17:51:12.080 2012 (UTC - 5:00)
System Uptime: 0 days 0:12:30.984
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ndis.sys - 
*** WARNING: Unable to verify timestamp for nvmf6264.sys
*** ERROR: Module load completed but symbols could not be loaded for nvmf6264.sys
Probably caused by : nvmf6264.sys ( nvmf6264+69c3 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  uTorrent.exe
FAILURE_BUCKET_ID:  X64_0xA_nvmf6264+69c3
BiosReleaseDate = 10/29/2007
SystemManufacturer = Hewlett-Packard
SystemProductName = MCP61P
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Thu Jan 26 17:25:43.377 2012 (UTC - 5:00)
System Uptime: 0 days 0:32:37.297
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ndis.sys - 
*** WARNING: Unable to verify timestamp for nvmf6264.sys
*** ERROR: Module load completed but symbols could not be loaded for nvmf6264.sys
Probably caused by : nvmf6264.sys ( nvmf6264+69c3 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  uTorrent.exe
FAILURE_BUCKET_ID:  X64_0xA_nvmf6264+69c3
BiosReleaseDate = 10/29/2007
SystemManufacturer = Hewlett-Packard
SystemProductName = MCP61P
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Thu Jan 26 08:12:58.408 2012 (UTC - 5:00)
System Uptime: 0 days 0:41:05.312
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ndis.sys - 
*** WARNING: Unable to verify timestamp for nvmf6264.sys
*** ERROR: Module load completed but symbols could not be loaded for nvmf6264.sys
Probably caused by : nvmf6264.sys ( nvmf6264+69c3 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  uTorrent.exe
FAILURE_BUCKET_ID:  X64_0xA_nvmf6264+69c3
BiosReleaseDate = 10/29/2007
SystemManufacturer = Hewlett-Packard
SystemProductName = MCP61P
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Thu Jan 26 06:17:26.105 2012 (UTC - 5:00)
System Uptime: 0 days 13:10:47.024
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ndis.sys - 
*** WARNING: Unable to verify timestamp for nvmf6264.sys
*** ERROR: Module load completed but symbols could not be loaded for nvmf6264.sys
Probably caused by : nvmf6264.sys ( nvmf6264+69c3 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  uTorrent.exe
FAILURE_BUCKET_ID:  X64_0xA_nvmf6264+69c3
BiosReleaseDate = 10/29/2007
SystemManufacturer = Hewlett-Packard
SystemProductName = MCP61P
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Wed Jan 25 17:05:26.991 2012 (UTC - 5:00)
System Uptime: 0 days 0:08:17.895
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ndis.sys - 
*** WARNING: Unable to verify timestamp for nvmf6264.sys
*** ERROR: Module load completed but symbols could not be loaded for nvmf6264.sys
Probably caused by : nvmf6264.sys ( nvmf6264+69c3 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_nvmf6264+69c3
BiosReleaseDate = 10/29/2007
SystemManufacturer = Hewlett-Packard
SystemProductName = MCP61P
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Wed Jan 25 16:44:32.119 2012 (UTC - 5:00)
System Uptime: 0 days 0:41:07.023
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ndis.sys - 
*** WARNING: Unable to verify timestamp for nvm62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for nvm62x64.sys
Probably caused by : nvm62x64.sys ( nvm62x64+6578 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_nvm62x64+6578
BiosReleaseDate = 10/29/2007
SystemManufacturer = Hewlett-Packard
SystemProductName = MCP61P
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Suur · 05 Feb 2012

Thank you! It seems that it worked.

Suur · 05 Feb 2012

Well the BSOD finally came. After 6h. Usually it came almost instantly when I added a lot of torrents.

Here's the new ".dmp" file. If you need anything else let me know.

Add: Today I got another BSOD. That one came almost instantly. Also added the other ".dmp" file.

Suur · 06 Feb 2012

The BSOD-s are now just more inconsistent. Today I tried running uTorrent as an administrator. Didn't get a BSOD for 12 hours. Then restarted my computer and opened the uTorrent again and the BSOD came almost instantly. Does anyone have any ideas? Should I try doing a clean install on windows? Could it be caused by Windows updates?

Also I'm going to add 4 of the latest ".dmp" files.

writhziden · 07 Feb 2012

Code:


Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [F:\BSODDmpFiles\Suur\Minidump\020612-16052-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02a51000 PsLoadedModuleList = 0xfffff800`02c96670
Debug session time: Mon Feb  6 14:12:30.294 2012 (GMT-7)
System Uptime: 0 days 0:24:00.214
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {100002c, 2, 0, fffff80002a0c5d0}

Unable to load image \SystemRoot\system32\DRIVERS\nvmf6264.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvmf6264.sys
*** ERROR: Module load completed but symbols could not be loaded for nvmf6264.sys
Probably caused by : nvmf6264.sys ( nvmf6264+69c3 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 000000000100002c, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002a0c5d0, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d00100
 000000000100002c 

CURRENT_IRQL:  2

FAULTING_IP: 
hal!HalBuildScatterGatherList+1a4
fffff800`02a0c5d0 448b5f2c        mov     r11d,dword ptr [rdi+2Ch]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  uTorrent.exe

TRAP_FRAME:  fffff88009ac9880 -- (.trap 0xfffff88009ac9880)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000007c9636f0 rbx=0000000000000000 rcx=000000007c2a9800
rdx=fffffa800571cd10 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002a0c5d0 rsp=fffff88009ac9a10 rbp=fffffa800571ccd0
 r8=0000000000000000  r9=fffffa80052a97f0 r10=fffffa800571ccd0
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
hal!HalBuildScatterGatherList+0x1a4:
fffff800`02a0c5d0 448b5f2c        mov     r11d,dword ptr [rdi+2Ch] ds:ffff:00000000`0000002c=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002acd1e9 to fffff80002acdc40

STACK_TEXT:  
fffff880`09ac9738 fffff800`02acd1e9 : 00000000`0000000a 00000000`0100002c 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`09ac9740 fffff800`02acbe60 : fffffa80`01ac3010 fffffa80`01ac3010 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`09ac9880 fffff800`02a0c5d0 : fffff880`09aca090 00000000`00000000 00000000`00000000 00000001`ffffffff : nt!KiPageFault+0x260
fffff880`09ac9a10 fffff880`0150c750 : fffffa80`04d63580 fffffa80`035596b0 fffff880`09ac9df4 fffff880`02c8d1ad : hal!HalBuildScatterGatherList+0x1a4
fffff880`09ac9a80 fffff880`06a919c3 : fffffa80`031c01a0 00000000`00000000 fffffa80`04d63580 fffffa80`04d63580 : ndis!NdisMAllocateNetBufferSGList+0x110
fffff880`09ac9b20 fffffa80`031c01a0 : 00000000`00000000 fffffa80`04d63580 fffffa80`04d63580 00000000`00000000 : nvmf6264+0x69c3
fffff880`09ac9b28 00000000`00000000 : fffffa80`04d63580 fffffa80`04d63580 00000000`00000000 00000000`00000000 : 0xfffffa80`031c01a0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvmf6264+69c3
fffff880`06a919c3 ??              ???

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  nvmf6264+69c3

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvmf6264

IMAGE_NAME:  nvmf6264.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a723142

FAILURE_BUCKET_ID:  X64_0xA_nvmf6264+69c3

BUCKET_ID:  X64_0xA_nvmf6264+69c3

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

1: kd> lmvm nvmf6264
start             end                 module name
fffff880`06a8b000 fffff880`06adc500   nvmf6264 T (no symbols)           
    Loaded symbol image file: nvmf6264.sys
    Image path: \SystemRoot\system32\DRIVERS\nvmf6264.sys
    Image name: nvmf6264.sys
    Timestamp:        Thu Jul 30 17:48:18 2009 (4A723142)
    CheckSum:         0005B9A8
    ImageSize:        00051500
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Still blaming your network adapter. I see that your adapter has been updated, so I am guessing it is not the adapter causing the crashes but your antivirus software. Avast is known to cause crashes on some systems. Please remove Avast using the Avast! Uninstall Utility and replace with Microsoft Security Essentials - Free Antivirus for Windows to run with Windows firewall, at least to test.

Also, please remove Daemon Tools, as it uses a driver called dtsoftbus01.sys that is known to cause BSODs.

I prefer TotalMounter as my CD/DVD virtualization software as it allows me to burn images to a virtual CD/DVD if I just want an ISO file instead of a disc, and it is free.

Many use MagicISO - Convert BIN to ISO, Create, Edit, Burn, Extract ISO file, ISO/BIN converter/extractor/editor as well, which is also free.

Suur · 07 Feb 2012

I used daemon tools before the re-installation of windows, but it might have been a different version. It can be the cause of the problem since I see a "daemonu.exe *32" process open in the task manager. The processes user is "UpdatusUser" and the process description is "NVIDIA Setting Update Manager". Seems a bit odd. So I will try this one first.

But I can't see how avast could be the problem. Before the re-installation of windows I used avast as well and never had any problems. I also tried uninstalling it once, but I didn't use the "Avast Utility". So I'll try again.

But the main thing I still suspect is the windows updates. If I remember correctly the first BSOD came after I had done some updates. But I'm not sure.

Also what I've noticed is that when I use uTorrent with one active download, it seems to run for much longer. But when I add more downloads, I get a BSOD almost instantly.

One thing that I forgot to mention is that right before the re-installation of windows I opened up my computer to clean it and during that I removed the FireWire slot and different card readers(like Smart Media, SD, Mini etc.) from my computer(because my motherboard is placed upside down inside my computer and to improve the graphics card cooling by removing unnecessary wires above the cooler). But I don't believe that this could have anything to do with the network card, but just thought that I should mention it. We also removed the wireless network part from my computer. But it was at the time we changed my graphics card, which was way before the problems began(Last October or November I think and the problems began in January right after the re-installation of windows).

Anyways I will try out the solutions you offered later tonight and I'll let you know. Thank you for your time!

writhziden · 07 Feb 2012

One thing to remember is that antivirus software is never the same from day to day. Definition updates change how the software behaves, so while it may work one day, it may cause problems the next. Do you remember when the problems started? Do you have any restore points available for a date before that time?

System Restore (especially the NOTE: in OPTION ONE 8.)

Suur · 07 Feb 2012

I did the re-installation of window on January 24th or 25th. That's the time when when the problems began. Before things were fine.

Also I seem to remember that I did some windows updates before the problems began. But I'm not sure.

Anyways I uninstalled Avast and still got the BSOD. Now I uninstalled Daemon tools and I'm currently testing.

Also I don't think I have any restore points. At least I haven't made any. How do I check?

Add: Uninstalled Daemon tools, still got a BSOD.

writhziden · 07 Feb 2012

Does it only happen with uTorrent? If so, have you tried uninstalling uTorrent and re-installing it? Sometimes corrupted program files can cause crashes, as well. You could also try a different torrent downloader like BitTorrent.

To check for restore points, see System Restore (especially the NOTE: in OPTION ONE 8.)

Windows 7: BSOD while running utorrent.

BSOD while running utorrent. problems?