Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD every 10 minutes.

21 May 2009   #31
Hammerhead786

 
 

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


My System SpecsSystem Spec
.
21 May 2009   #32
Takara

Windows 7
 
 

Yep. That's the driver I have.
My System SpecsSystem Spec
21 May 2009   #33
Takara

Windows 7
 
 

Quote   Quote: Originally Posted by bhuulo View Post
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.
My System SpecsSystem Spec
.

21 May 2009   #34
Hammerhead786

 
 

I'm at a loss as to what to suggest now.
My System SpecsSystem Spec
21 May 2009   #35
torrentg

7600.20510 x86
 
 

Quote   Quote: Originally Posted by Takara View Post
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.
My System SpecsSystem Spec
21 May 2009   #36
Takara

Windows 7
 
 

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
My System SpecsSystem Spec
21 May 2009   #37
torrentg

7600.20510 x86
 
 

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...
My System SpecsSystem Spec
21 May 2009   #38
Takara

Windows 7
 
 

Quote   Quote: Originally Posted by torrentg View Post
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.
My System SpecsSystem Spec
21 May 2009   #39
bhuulo

 

Quote   Quote: Originally Posted by torrentg View Post
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...
My System SpecsSystem Spec
21 May 2009   #40
Takara

Windows 7
 
 

Ran both. Nothing wrong in either of them.
My System SpecsSystem Spec
Reply

 BSOD every 10 minutes.




Thread Tools




Similar help and support threads
Thread Forum
BSOD During Prime95, first Core #5 failed, then BSOD after few minutes
Hey, I noticed that my PC is unstable when I set ASUS Bios setting to Optimal (performance mode) and PC freezes up after few minutes, so I decided to run it in normal mode without any overclocks or anything, just plain default bios. I ran Prime95 Blend Test for 30 minutes and it failed. Then I...
BSOD Help and Support
BSOD every 20 or so minutes. what do?
My computer has been crashing randomly about 20 after I start it up for the last few days and I've barely been able to get a complete crash dump before it crashes. In fact it crashed once while I tried posting this. I think it's either a virus or bad driver but I don't know for certain any help is...
BSOD Help and Support
BSOD after a few minutes (5 to 55 minutes) with Samsung SSD 840 EVO
Hi. I have successfully cloned my existing OS over to the SSD 840 EVO using Samsung magician. My OS boots fine with the SSD 840 EVO but crashes several minutes after startup. Crashes can happen from 5 to 50+ minutes after start up. The crashing process happens slowly, starting with the mouse...
BSOD Help and Support
BSOD every 10 minutes
i get the BSOD every 15 minutes. i have attached the zip folder. please help
BSOD Help and Support
BSOD - Black Screen couple minutes before BSOD
Okay the issue I've got isn't really the Blue Screen so much as it is everything that's happening before it. I'll be using TeamViewer and running another program be it a game or a video and sometimes nothing at all and I'll get a Black Screen, sometimes if TeamViewer closes the screen will go...
BSOD Help and Support
BSOD Every 10 minutes
I started getting the BSOD today: Log files are listed below: Please help: The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007f (0x0000000000000008, 0x0000000080050033, 0x00000000000406f8, 0xfffff80002c4f798). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id:...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 02:51.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App