BSOD every 10 minutes.

[Hammerhead786]

One final suggestion. Do a clean install, install all drivers and windows updates. Install only utorrent and then see what happens. If you are still getting BSOD's post them here. Do not install any other apps or external devices whatsoever apart from your wireless card and post back here with the results.

 

[Takara]

Okay, working on creating a new install disc. I'll let you know when that's all done..

 

[usasma]

Most of the dump files point to an nVidia networking driver, with some of them pointing to your Atheros wireless driver, and a few to internet applications.

First off, disable one or the other device (wired or wireless) in Device Manager, then try uTorrent. If it blue screens, try the other one with uTorrent. This will rule out the individual drivers.

But if both Blue Screen, then it's most likely the torrent application - otherwise it's the one (wired or wireless) that blue screened when you were disabling the other.

 

[Takara]

Most of the dump files point to an nVidia networking driver, with some of them pointing to your Atheros wireless driver, and a few to internet applications.

First off, disable one or the other device (wired or wireless) in Device Manager, then try uTorrent. If it blue screens, try the other one with uTorrent. This will rule out the individual drivers.

But if both Blue Screen, then it's most likely the torrent application - otherwise it's the one (wired or wireless) that blue screened when you were disabling the other.

Okay, only things I have installed is my wireless driver and the windows debugging tool to view my crash dumps.. oh and Vuze.

Crashed within 2 minutes of starting uTorrent. Working on these suggestions. Also, I'll post the dump it just did when the OS gives me permission to view the file... ._.

 

[Takara]

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

Loading Dump File [C:\Windows\Minidump\052109-35989-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols;SRV*c:\symbols*http://msdl.microsoft.com/download/
Executable search path is:
Windows 7 Kernel Version 7100 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7100.0.amd64fre.winmain_win7rc.090421-1700
Machine Name:
Kernel base = 0xfffff800`02660000 PsLoadedModuleList = 0xfffff800`02899e90
Debug session time: Thu May 21 16:05:30.533 2009 (GMT-4)
System Uptime: 0 days 0:44:11.687
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff800026c616a, fffff8800a28b440, 0}
Invalid relocation block size 0x0
Probably caused by : memory_corruption ( nt!MiGetPreviousNode+53 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff800026c616a, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff8800a28b440, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
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!MiGetPreviousNode+53
fffff800`026c616a 488b4910 mov rcx,qword ptr [rcx+10h]
CONTEXT: fffff8800a28b440 -- (.cxr 0xfffff8800a28b440)
rax=8ca01366b115e92c rbx=000000007efd2000 rcx=8ca01366b115e92c
rdx=000000000007ef95 rsi=000000000007efd5 rdi=0000000000000001
rip=fffff800026c616a rsp=fffff8800a28be28 rbp=000000000007efd2
r8=fffffffffffff000 r9=fffffa800201f410 r10=0000000000003000
r11=fffffa800201f410 r12=000000007efd5000 r13=fffffa80042a71f0
r14=fffffa80042a71f0 r15=000000007efd5000
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00210282
nt!MiGetPreviousNode+0x53:
fffff800`026c616a 488b4910 mov rcx,qword ptr [rcx+10h] ds:002b:8ca01366`b115e93c=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: iexplore.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002983e22 to fffff800026c616a
STACK_TEXT:
fffff880`0a28be28 fffff800`02983e22 : fffff880`0a28c4c0 00000000`00000000 00000000`7efde000 fffffa80`01e0e340 : nt!MiGetPreviousNode+0x53
fffff880`0a28be30 fffff800`02968adb : ffffffff`ffffffff fffffa80`04980f70 fffffa80`042a7408 00000000`000007ff : nt!MiFindEmptyAddressRangeDownTree+0x102
fffff880`0a28be60 fffff800`0296b1ec : fffffa80`042a71f0 00000000`00000000 00000000`00002fe4 fffff880`0a28bf80 : nt!MiCreatePebOrTeb+0x2bb
fffff880`0a28bef0 fffff800`029683f0 : 00000000`00000000 00000000`00001000 00000000`00000000 00000000`00000000 : nt!MmCreateTeb+0x5c
fffff880`0a28bf80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PspAllocateThread+0x360

FOLLOWUP_IP:
nt!MiGetPreviousNode+53
fffff800`026c616a 488b4910 mov rcx,qword ptr [rcx+10h]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!MiGetPreviousNode+53
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 49ee9439
STACK_COMMAND: .cxr 0xfffff8800a28b440 ; kb
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0x3B_nt!MiGetPreviousNode+53
BUCKET_ID: X64_0x3B_nt!MiGetPreviousNode+53
Followup: MachineOwner
---------


It restarted again after this blue screen, but it didn't run a memory dump for some reason. Working on the with/without wireless running.

 

[Takara]

Okay, I switched it over to a wired connection temporarily. No BSOD with Vuze with it. So, I guess it's the wireless and torrent clients. Just not sure what to do with it. Can't stay on the wired connection since I'm borrowing it for troubleshooting this.

 

[Hammerhead786]

Sorry Takara, I was bitten by the sleep bug last night and hence failed to make it back here. I was going to suggest trying a wired lan connection, but you've beaten me to it and done it.

I have this nagging feeling that it is your wireless lan card that's causing the issue, hence a lot of the questions relating to it earlier. One way to conclusively prove it is to find a friend and temporarily borrow theirs (as long as it isn't the same one) for testing or bite the bullet and buy another card.

You could try contacting Belkin to see if they are going to be supporting this in Win 7, but I wouldn't hold my breath, however, I could be wrong. I think we've ruled out pretty much everything else. Good luck and keep us posted.

 

[Takara]

Contacted Belkin and they just said it wasn't compatible with Windows 7 and that was it. No new information. Tried Atheros website but I don't know the chipset of it so that does no good. Belkin has 3 or so different chipsets it uses for the USB adapter. If I knew it, I could try the Atheros ones.

Okay found out the device uses the chipset Zydas 1211. Now trying to search if there's a workaround.

I've decided to just not use torrent clients for a little bit. Thanks for the help guys.

Okay, for anyone looking for a possible workaround if they have this issue like me, I'm using Frostwire for torrents. No BSOD's at all. That's all for now. =D

 

[Pillow Talk]

The problem is caused by the driver for your wireless adapter.

I used to have the same issue. It would BSOD with random errors every time. At the time, I gave up on Windows 7 (it was only a RC at the time). But now I have the full retail version. Everything works fine as long as I don't install the driver for the adapter, or I unplug the device.

Try uninstalling your network adapter and then use the machine as normal (obviously no internet though, unless you can connect directly) and see if you get any more BSODs. My guess is that you won't.

edit: It seems you already found this out. Next time I will read the last page too XD