I've had like 30 BSOD's over the past 2 days. I've checked on things and it's mainly when I start uTorrent. After a few minutes, it BSOD's. It's mainly .sys that is listed in the memory dumps. Had one .exe listed. They were nwifi.sys, nvlddmkm.sys, tcpip.sys, athrxusb.sys, ntkrnlmp.exe, pacer.sys, and memory_corruption. Any ideas? Let me know if you need more information.
I've attached a text file of the memory dumps to be more precise for you all. Sorry if I was rambling there.. xD
I've attached a text file of the memory dumps to be more precise for you all. Sorry if I was rambling there.. xD
Hi Takara welcome to the forum. It looks like you have driver issues. As a start I would suggest you remove any non native Win 7 drivers. Download the latest Win 7 GPU drivers from Nvidia and install those and the ones for your chipset as well. Report back once you have done this.
�� Quote: Originally Posted by Hammerhead786 
Finished with that.
�� Quote: Originally Posted by Takara Finished with that.
�� Quote: Originally Posted by Hammerhead786 I presume from this you mean that you have installed the chipset and gpu drivers? What devices do you have showing in device manager either with a problem or as unknown?
Is the pc still blue screening? If not keep an eye on it for a while. Btw did you do an upgrade or a clean install?
It was a clean install and yeah, it still blue screens a few minutes after starting uTorrent.
What version of Win 7 are you running? If you don't run utorrent does it still bluescreen? What wireless card are you using?
It doesn't blue screen if I don't use uTorrent, but it's the only way I can get what I need. I'm using a Belkin Wireless G USB adapter. I'm running build 7100, the official RC.
Ok it's obvious that utorrent is causing the issue. I would suggest you uninstall utorrent, reboot the pc, run windows update and then download utorrent again and install it.
If you are still getting blue screens check for any malware/viruses. Also check to see if there is another driver available from Belkin for your wireless card. I don't use any torrent software so I can't confirm/deny if utorrent works on Win 7.
If you are still getting blue screens check for any malware/viruses. Also check to see if there is another driver available from Belkin for your wireless card. I don't use any torrent software so I can't confirm/deny if utorrent works on Win 7.
Okay, give me 5 minutes and I'll let you know what it does.
So far so good. No blue screen yet. I'm thinking it MAY have been cause I was using a beta of uTorrent and not the stable one. I'll post if it blue screens later.
I spoke too soon... BSOD'ed within 10 seconds afteer that post.. x.x
Did you try another driver for your wireless card? In fact do you have another wireless card that you can try in the pc?
There isn't another driver for my wireless card. And I don't have a different one.
Don't use uTorrent for a while and see if it doesn't BSOD then the culprit is uTorrent and when u r sure that it is uTorrent then try any other torrent software like Azureus, now called Vuze or Bittorent and let us know...
Okay, I'll go ahead and uninstall uTorrent and go with another torrent app. I'll be back with the results.
Takara, I'm running out of ideas here. As bhuulo said try a different piece of torrent software. Is there any other software you have running besides utorrent? Do you have a friend whose wireless card you may be able to borrow just for testing?
Forgot to ask. Have you tested the memory to see if it is ok? Are you running the latset bios?
Forgot to ask. Have you tested the memory to see if it is ok? Are you running the latset bios?
I haven't tested my memory cause I don't have a usb stick or cd to put memtest on to run it.
I removed uTorrent and downloaded Vuze. Checking to see how it runs.
I removed uTorrent and downloaded Vuze. Checking to see how it runs.
What's the exact model of your wireless card?
F5D7050 -- Seems like Vuze takes the computer out too.
Do you know what version it is? If we can find what chipset it uses we might be able to find some better drivers for it.
Install the latest video driver for your card. If you've already done so, disable SLI and see if that has any beneficial effect, as a test.
You could also try underclocking your card slightly, like 20 or 30 MHz. Or could try upping PCI-Express speed in bios.
This thread seems to talk about the problem, or related:
http://www.driverheaven.net/vista-nv...ddmkm-sys.html
You could also try underclocking your card slightly, like 20 or 30 MHz. Or could try upping PCI-Express speed in bios.
This thread seems to talk about the problem, or related:
http://www.driverheaven.net/vista-nv...ddmkm-sys.html
I think it is some port setting in the card which is crashing the system??? and according to him that happens only when he starts some or other Torrent program... (as he said)
@Takara
Does it even crash if u don't run any torrent programs....
@Takara
Does it even crash if u don't run any torrent programs....
�� Quote: Originally Posted by Hammerhead786 Do you know what version it is? If we can find what chipset it uses we might be able to find some better drivers for it.
�� Quote: Originally Posted by bhuulo I think it is some port setting in the card which is crashing the system??? and according to him that happens only when he starts some or other Torrent program... (as he said)
@Takara
Does it even crash if u don't run any torrent programs....
@Takara
Does it even crash if u don't run any torrent programs....
�� Quote: Originally Posted by torrentg Install the latest video driver for your card. If you've already done so, disable SLI and see if that has any beneficial effect, as a test.
You could also try underclocking your card slightly, like 20 or 30 MHz. Or could try upping PCI-Express speed in bios.
This thread seems to talk about the problem, or related:
� how to solve nvlddmkm.sys
You could also try underclocking your card slightly, like 20 or 30 MHz. Or could try upping PCI-Express speed in bios.
This thread seems to talk about the problem, or related:
� how to solve nvlddmkm.sys
Can you get the fcc id off the back of the wireless card along with any other details?
Sure thing.
FCC ID: RAXWN4501H
IC: 4711A-WN4501H
Model: F5D7050
That what you're looking for?
FCC ID: RAXWN4501H
IC: 4711A-WN4501H
Model: F5D7050
That what you're looking for?
�� Quote: Originally Posted by Takara If I don't run any torrent program, it doesn't crash.
Try to change your port settings in uTorrent->Options->Preferences->Connection and try and inform us again....
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
Belkin
Yep. That's the driver I have.
�� Quote: Originally Posted by bhuulo 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....
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.
I'm at a loss as to what to suggest now.
�� Quote: Originally Posted by Takara That particular BSOD hasn't happened since I reinstalled my nvidia drivers.
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.
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
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
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...
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...
�� Quote: Originally Posted by torrentg 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...
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...
�� Quote: Originally Posted by torrentg 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...
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...
I think even though he has clean installed there were some errors during the installation and that might be giving problems...
Ran both. Nothing wrong in either of them.
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.
Okay, working on creating a new install disc. I'll let you know when that's all done..
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.
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.
�� Quote: Originally Posted by 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.
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.
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... ._.
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/s....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.
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/s....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.
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.
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.
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.
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
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
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
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
Không có nhận xét nào:
Đăng nhận xét