BSOD every 10 minutes.

Hammerhead786 · 21 May 2009

Takara, I've had a look and your wireless card is the F5D7050 version 4, which uses the Zydas chipset. I presume these were the drivers that you downloaded from Belkin:?

Belkin

Takara · 21 May 2009

Yep. That's the driver I have.

Takara · 21 May 2009

bhuulo said:

I can surely say it is a port setting which a torrent program tries to access to connect to internet Whether it was uTorrent or Vuze or may be any other....

Try to change your port settings in uTorrent->Options->Preferences->Connection and try and inform us again....

o.o Hmms... I've changed the port...so far no BSOD.

*EDIT* Nope, that didn't work.

Hammerhead786 · 21 May 2009

I'm at a loss as to what to suggest now.

torrentg · 21 May 2009

Takara said:

That particular BSOD hasn't happened since I reinstalled my nvidia drivers.

Cool. So maybe post a brand new dump if you can. I'll have a look and since I probably won't be able to help you lol, someone else might.

It's not any torrent client settings. No matter how poorly set it would be, it should not produce a bsod unless there is a system or driver problem...and obviously there is.

Takara · 21 May 2009

Here's a list of my BSOD using the app WhoCrashed: FYI, the nvidia issue has been fixed already.

On Thu 5/21/2009 1:07:35 PM your computer crashed
This was likely caused by the following module: usbehci.sys
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002BFF4EC, 0xFFFFF80000BA29C8, 0xFFFFF80000BA2220)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\usbehci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: EHCI eUSB Miniport Driver
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.

On Thu 5/21/2009 10:47:14 AM your computer crashed
This was likely caused by the following module: tdx.sys
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88003A7ECD8, 0xFFFFF88002FCE8A8, 0xFFFFF88002FCE100)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\tdx.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TDI Translation Driver
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.

On Thu 5/21/2009 9:40:59 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002BF24EC, 0xFFFFF88008EE5DC0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.

On Thu 5/21/2009 9:08:30 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002A84BE2, 0xFFFFF88002FB28A8, 0xFFFFF88002FB2100)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.

On Thu 5/21/2009 8:44:51 AM your computer crashed
This was likely caused by the following module: nvstor64.sys
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8800402F51D, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\nvstor64.sys
product: NVIDIA nForce(TM) SATA Driver
company: NVIDIA Corporation
description: NVIDIA® nForce(TM) Sata Performance Driver

On Thu 5/21/2009 8:29:27 AM your computer crashed
This was likely caused by the following module: tcpip.sys
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8800360AFC0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.

On Thu 5/21/2009 6:46:02 AM your computer crashed
This was likely caused by the following module: wdf01000.sys
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002B42D60, 0xFFFFF88002FB91F8, 0xFFFFF88002FB8A50)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Mode Driver Framework Runtime
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.

On Thu 5/21/2009 12:54:54 AM your computer crashed
This was likely caused by the following module: nvlddmkm.sys
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88004DC7E44, 0xFFFFF88002EF79D8, 0xFFFFF88002EF7230)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 185.85
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 185.85

On Wed 5/20/2009 10:51:11 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002B8286F, 0xFFFFF88008951C50, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.

On Wed 5/20/2009 9:37:41 PM your computer crashed
This was likely caused by the following module: tcpip.sys
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80000B99CB0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.

On Wed 5/20/2009 7:57:30 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x3D (0xFFFFF80000BA1DB0, 0x0, 0x0, 0xFFFFF80002A8006E)
Error: INTERRUPT_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.

On Wed 5/20/2009 7:37:30 PM your computer crashed
This was likely caused by the following module: athrxusb.sys
Bugcheck code: 0x3D (0xFFFFF80004065020, 0x0, 0x0, 0xFFFFF88001EAAE17)
Error: INTERRUPT_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\athrxusb.sys
product: Driver for Atheros Wireless USB Network Adapter
company: Atheros Communications, Inc.
description: Atheros Extensible Wireless LAN device driver

On Wed 5/20/2009 7:11:25 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8800B185380, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.

On Wed 5/20/2009 12:17:58 PM your computer crashed
This was likely caused by the following module: nvlddmkm.sys
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88004C9D230, 0xFFFFF88002EFAD18, 0xFFFFF88002EFA570)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 185.85
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 185.85

On Wed 5/20/2009 11:42:25 AM your computer crashed
This was likely caused by the following module: nvlddmkm.sys
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88004DCA5C7, 0xFFFFF8800315C2D8, 0xFFFFF8800315BB30)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 185.85
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 185.85

On Wed 5/20/2009 11:19:47 AM your computer crashed
This was likely caused by the following module: nvlddmkm.sys
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF880048C1A84, 0xFFFFF8800382B7C8, 0xFFFFF8800382B020)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 185.85
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 185.85

On Wed 5/20/2009 7:11:43 AM your computer crashed
This was likely caused by the following module: nwifi.sys
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF88001E08767, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\nwifi.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NativeWiFi Miniport Driver
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.

On Wed 5/20/2009 6:59:20 AM your computer crashed
This was likely caused by the following module: nvlddmkm.sys
Bugcheck code: 0xC2 (0xB, 0xFFFFFA8003FF6A70, 0x0, 0xFFFFFA8003FF79F0)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 185.85
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 185.85

torrentg · 21 May 2009

Two things I can think of, since you say you already have proper drivers -

From elevated command prompt, run to ensure system file integrity:

sfc /scannow

then if that completes well

chkdsk /f

Also, reboot the computer with only the usb devices attached that you need. Like mouse, keyboard, wireless. Remove anything else like a printer, game pad etc...

Takara · 21 May 2009

torrentg said:

Two things I can think of, since you say you already have proper drivers -

From elevated command prompt, run to ensure system file integrity:

sfc /scannow

then if that completes well

chkdsk /f

Also, reboot the computer with only the usb devices attached that you need. Like mouse, keyboard, wireless. Remove anything else like a printer, game pad etc...

Starting that. I'll let you know when it's all finished.

bhuulo · 21 May 2009

torrentg said:

Two things I can think of, since you say you already have proper drivers -

From elevated command prompt, run to ensure system file integrity:

sfc /scannow

then if that completes well

chkdsk /f

Also, reboot the computer with only the usb devices attached that you need. Like mouse, keyboard, wireless. Remove anything else like a printer, game pad etc...

Now that's a wise move because everytime system crash due to separate file and even ntoskrnl.exe is giving problem...

I think even though he has clean installed there were some errors during the installation and that might be giving problems...

Takara · 21 May 2009

Ran both. Nothing wrong in either of them.