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 when using bittorrent

15 Jun 2011   #1

windows7 home premium 32bit
 
 
BSOD when using bittorrent

hi i am getting constant BSOD when using torrent programs, i have attached all requested info,

system is lenovo g555
Windows 7 . . .
- x86 (32-bit) or x64 ? 32 bit home premium
- the original installed OS on the system? as above
- an OEM or full retail version? OEM
- OEM = came pre-installed on system
- Full Retail = you purchased it from retailer

- What is the age of system (hardware)? bought jan 2011
- What is the age of OS installation (have you re-installed the OS?) bought jan 2011

My System SpecsSystem Spec
.

15 Jun 2011   #2

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by tez1982 View Post
hi i am getting constant BSOD when using torrent programs, i have attached all requested info,

system is lenovo g555
Windows 7 . . .
- x86 (32-bit) or x64 ? 32 bit home premium
- the original installed OS on the system? as above
- an OEM or full retail version? OEM
- OEM = came pre-installed on system
- Full Retail = you purchased it from retailer

- What is the age of system (hardware)? bought jan 2011
- What is the age of OS installation (have you re-installed the OS?) bought jan 2011

Virtually identical and all related to your Norton.

I would remove and replace with Microsoft security essentials

Download and run the Norton Removal Tool to uninstall your Norton product | Norton Support

Virus, Spyware & Malware Protection | Microsoft Security Essentials
My System SpecsSystem Spec
16 Jun 2011   #3

windows7 home premium 32bit
 
 

thanks for the idea but it didn't work having removed norton and installed ms security bittorrent still caused BSOD within 5 mins of starting, i have updated the 2 previous zip files
My System SpecsSystem Spec
.


16 Jun 2011   #4

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by tez1982 View Post
thanks for the idea but it didn't work having removed norton and installed ms security bittorrent still caused BSOD within 5 mins of starting, i have updated the 2 previous zip files

Finally I think the true cause has revealed itself.

The requested page of kernel data could not be read in. Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.

I would run a chkdsk to find out whihc

A- CHKDSK /R /F:

Run CHKDSK /R /F from an elevated (Run as administrator) Command Prompt.

Do this for each hard drive on your system.

When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter.

Then reboot and let the test run.

It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors.

See "CHKDSK LogFile" below in order to check the results of the test.


B- Elevated Command Prompt:


Go to Start and type in "cmd.exe" (without the quotes)

At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"


C-CHKDSK LogFile:


Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter

Expand the Windows logs heading, then select the Application log file entry.

Double click on the Source column header.

Scroll down the list until you find the Chkdsk entry (wininit for Windows 7) (winlogon for XP).

Copy/paste the results into your next post.


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


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\061611-19515-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*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17592.x86fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0x82a4f000 PsLoadedModuleList = 0x82b984d0
Debug session time: Thu Jun 16 06:39:58.271 2011 (GMT-4)
System Uptime: 0 days 0:36:55.019
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
.......
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in.  Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: c0416060, lock type that was held (value 1,2,3, or PTE address)
Arg2: c0000185, error status (normally i/o status code)
Arg3: 19cc8860, current process (virtual address for lock type 3, or PTE)
Arg4: 82c0cd31, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

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

GetPointerFromAddress: unable to read from 82bb8830

ERROR_CODE: (NTSTATUS) 0xc0000185 - The I/O device reported an I/O error.

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR:  0x7a_c0000185

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  8a113c68 -- (.trap 0xffffffff8a113c68)
ErrCode = 00000010
eax=8544d870 ebx=00000000 ecx=00000009 edx=00000000 esi=00000314 edi=85e412a8
eip=82c0cd31 esp=8a113cdc ebp=8a113d00 iopl=0         nv up ei ng nz na po cy
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010283
nt!PiProcessReenumeration:
82c0cd31 0000            add     byte ptr [eax],al          ds:0023:8544d870=??
Resetting default scope

LOCK_ADDRESS:  82bb5be0 -- (!locks 82bb5be0)

Resource @ nt!PiEngineLock (0x82bb5be0)    Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE: 
    Lock address  : 0x82bb5be0
    Thread Count  : 0
    Thread address: 0x00000000
    Thread wait   : 0x0

LAST_CONTROL_TRANSFER:  from 82af2e35 to 82b2df2c

STACK_TEXT:  
8a113acc 82af2e35 0000007a c0416060 c0000185 nt!KeBugCheckEx+0x1e
8a113b3c 82af6716 8a113b90 82bb92c0 8a113bb0 nt!MiWaitForInPageComplete+0x302
8a113bcc 82adf967 82bb92c0 82c0cd31 855c29b8 nt!MiIssueHardFault+0x3b3
8a113c50 82a903d8 00000008 82c0cd31 00000000 nt!MmAccessFault+0x2656
8a113c50 82c0cd31 00000008 82c0cd31 00000000 nt!KiTrap0E+0xdc
8a113d00 82accaab 00000000 00000000 847144c0 nt!PiProcessReenumeration
8a113d50 82c57f64 00000001 900d4fa4 00000000 nt!ExpWorkerThread+0x10d
8a113d90 82b00219 82acc99e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    82c0c000-82c0c004  5 bytes - nt!PipProcessDevNodeTree+348
    [ fe ff ff e9 c9:00 00 00 00 00 ]
    82c0c008-82c0c00c  5 bytes - nt!PipProcessDevNodeTree+34b (+0x08)
    [ 8b c7 e8 22 0f:00 00 00 00 00 ]
    82c0c00f-82c0c017  9 bytes - nt!PipProcessDevNodeTree+352 (+0x07)
    [ 8b f0 c7 85 58 fe ff ff:00 00 00 00 00 00 00 00 ]
    82c0c01b-82c0c029  15 bytes - nt!PipProcessDevNodeTree+35e (+0x0c)
    [ e9 4d fe ff ff 39 9d 54:00 00 00 00 00 00 00 00 ]
    82c0c02c - nt!PipProcessDevNodeTree+36f (+0x11)
    [ 40:00 ]
    82c0c02e-82c0c032  5 bytes - nt!PipProcessDevNodeTree+371 (+0x02)
    [ 74 07 be 2d 02:00 00 00 00 00 ]
    82c0c034-82c0c046  19 bytes - nt!PipProcessDevNodeTree+377 (+0x06)
    [ c0 eb 42 ff 75 1c 33 db:00 00 00 00 00 00 00 00 ]
    82c0c04d-82c0c05c  16 bytes - nt!PipProcessDevNodeTree+390 (+0x19)
    [ 01 8b f0 74 12 8b 47 10:00 00 00 00 00 00 00 00 ]
    82c0c060-82c0c067  8 bytes - nt!PipProcessDevNodeTree+3a3 (+0x13)
    [ ff ff ff fe 81 fe 03 01:00 00 00 00 00 00 00 00 ]
    82c0c06a-82c0c086  29 bytes - nt!PipProcessDevNodeTree+3ad (+0x0a)
    [ 75 0b 89 9d 54 fe ff ff:00 00 00 00 00 00 00 00 ]
    82c0c08a-82c0c095  12 bytes - nt!PipProcessDevNodeTree+3cd (+0x20)
    [ 8b f7 85 db 7d 2d 33 c0:00 00 00 00 00 00 00 00 ]
    82c0c097-82c0c09e  8 bytes - nt!PipProcessDevNodeTree+3da (+0x0d)
    [ c0 0f 94 c0 8d 04 85 0a:00 00 00 00 00 00 00 00 ]
    82c0c0a2-82c0c0a8  7 bytes - nt!PipProcessDevNodeTree+3e5 (+0x0b)
    [ 50 32 c0 e8 ef 19 10:00 00 00 00 00 00 00 ]
    82c0c0aa-82c0c0ad  4 bytes - nt!PipProcessDevNodeTree+3ed (+0x08)
    [ 83 bf 3c 01:00 00 00 00 ]
    82c0c0b1-82c0c0bf  15 bytes - nt!PipProcessDevNodeTree+3f4 (+0x07)
    [ 74 14 ff 77 10 e8 b0 e7:00 00 00 00 00 00 00 00 ]
    82c0c0c2-82c0c0d6  21 bytes - nt!PipProcessDevNodeTree+405 (+0x11)
    [ e8 d2 7d e5 ff 8b f3 85:00 00 00 00 00 00 00 00 ]
    82c0c0d8-82c0c0e2  11 bytes - nt!PipProcessDevNodeTree+41b (+0x16)
    [ e9 90 fd ff ff 83 a5 3c:00 00 00 00 00 00 00 00 ]
    82c0c0e4-82c0c0f1  14 bytes - nt!PipProcessDevNodeTree+427 (+0x0c)
    [ 33 ff 47 57 57 8d b5 48:00 00 00 00 00 00 00 00 ]
    82c0c0f4-82c0c0f9  6 bytes - nt!PipProcessDevNodeTree+437 (+0x10)
    [ 83 a5 54 fe ff ff:00 00 00 00 00 00 ]
    82c0c0fb-82c0c129  47 bytes - nt!PipProcessDevNodeTree+43e (+0x07)
    [ 57 ff 75 1c ff 75 18 ff:00 00 00 00 00 00 00 00 ]
    82c0c12b-82c0c160  54 bytes - nt!PipProcessDevNodeTree+46e (+0x30)
    [ 56 ff 71 18 8d 85 5c fe:00 00 00 00 00 00 00 00 ]
    82c0c162-82c0c166  5 bytes - nt!PipProcessDevNodeTree+4a5 (+0x37)
    [ 57 e8 83 fe 01:00 00 00 00 00 ]
    82c0c168-82c0c184  29 bytes - nt!PipProcessDevNodeTree+4ab (+0x06)
    [ 8d 85 5c fe ff ff 50 8d:00 00 00 00 00 00 00 00 ]
    82c0c186-82c0c18a  5 bytes - nt!PipProcessDevNodeTree+4c9 (+0x1e)
    [ 85 c0 0f 84 9d:00 00 00 00 00 ]
    82c0c18e-82c0c190  3 bytes - nt!PipProcessDevNodeTree+4d1 (+0x08)
    [ 8b 80 b0:00 00 00 ]
    82c0c194-82c0c1fe  107 bytes - nt!PipProcessDevNodeTree+4d7 (+0x06)
    [ 8b 78 14 89 bd 50 fe ff:00 00 00 00 00 00 00 00 ]
    82c0c202-82c0c213  18 bytes - nt!PipProcessDevNodeTree+545 (+0x6e)
    [ 39 95 30 fe ff ff 0f 85:00 00 00 00 00 00 00 00 ]
    82c0c215-82c0c226  18 bytes - nt!PipProcessDevNodeTree+558 (+0x13)
    [ 74 1b 8b b5 34 fe ff ff:00 00 00 00 00 00 00 00 ]
    82c0c228-82c0c22c  5 bytes - nt!PipProcessDevNodeTree+56b (+0x13)
    [ fb ff ff b8 01:00 00 00 00 00 ]
    82c0c22f-82c0c234  6 bytes - nt!PipProcessDevNodeTree+572 (+0x07)
    [ c0 eb 1a 83 7d 20:00 00 00 00 00 00 ]
    82c0c236-82c0c25b  38 bytes - nt!PipProcessDevNodeTree+579 (+0x07)
    [ 75 0e 8b 85 40 fe ff ff:00 00 00 00 00 00 00 00 ]
    82c0c25d-82c0c2d2  118 bytes - nt!PipProcessDevNodeTree+5a0 (+0x27)
    [ 90 cf bd c0 82 01 be c0:00 00 00 00 00 00 00 00 ]
    82c0c2d5-82c0c2d7  3 bytes - nt!PnpDeviceCompletionProcessCompletedRequests+3e (+0x78)
    [ 3d ce 02:00 00 00 ]
    82c0c2d9-82c0c2e1  9 bytes - nt!PnpDeviceCompletionProcessCompletedRequests+42 (+0x04)
    [ c0 75 03 89 45 fc c7 06:00 00 00 00 00 00 00 00 ]
    82c0c2e5-82c0c2f4  16 bytes - nt!PnpDeviceCompletionProcessCompletedRequests+4e (+0x0c)
    [ e8 19 7c e5 ff 85 c0 74:00 00 00 00 00 00 00 00 ]
    82c0c2f6-82c0c300  11 bytes - nt!PnpDeviceCompletionProcessCompletedRequests+5f (+0x11)
    [ 90 90 90 90 90 8b 49 10:00 00 00 00 00 00 00 00 ]
    82c0c304-82c0c32b  40 bytes - nt!PiCheckForActiveDependencies+9 (+0x0e)
    [ 32 c0 83 c1 34 8b 11 eb:00 00 00 00 00 00 00 00 ]
    82c0c32f-82c0c339  11 bytes - nt!PipCallDriverAddDevice+e (+0x2b)
    [ 53 8b 5d 08 56 33 f6 83:00 00 00 00 00 00 00 00 ]
    82c0c33c-82c0c34d  18 bytes - nt!PipCallDriverAddDevice+1b (+0x0d)
    [ ff 57 89 74 24 1c 89 74:00 00 00 00 00 00 00 00 ]
    82c0c34f-82c0c359  11 bytes - nt!PipCallDriverAddDevice+2e (+0x13)
    [ 89 74 24 24 89 74 24 20:00 00 00 00 00 00 00 00 ]
    82c0c35d-82c0c368  12 bytes - nt!PipCallDriverAddDevice+3c (+0x0e)
    [ 39 35 28 6c b8 82 74 52:00 00 00 00 00 00 00 00 ]
    82c0c36c-82c0c370  5 bytes - nt!PipCallDriverAddDevice+4b (+0x0f)
    [ 50 8d 84 24 c0:00 00 00 00 00 ]
    82c0c374-82c0c389  22 bytes - nt!PipCallDriverAddDevice+53 (+0x08)
    [ 50 8d 44 24 34 50 6a 04:00 00 00 00 00 00 00 00 ]
    82c0c38b-82c0c393  9 bytes - nt!PipCallDriverAddDevice+6a (+0x17)
    [ 85 c0 7c 28 81 7c 24 2c:00 00 00 00 00 00 00 00 ]
    82c0c397-82c0c3b4  30 bytes - nt!PipCallDriverAddDevice+76 (+0x0c)
    [ 77 1e 8d 44 24 38 50 ff:00 00 00 00 00 00 00 00 ]
    82c0c3b7-82c0c3ba  4 bytes - nt!PipCallDriverAddDevice+96 (+0x20)
    [ 83 bb 6c 01:00 00 00 00 ]
    82c0c3bd-82c0c3cd  17 bytes - nt!PipCallDriverAddDevice+9c (+0x06)
    [ ff 6a fe 59 75 1b 8b 43:00 00 00 00 00 00 00 00 ]
    82c0c3d0-82c0c3d3  4 bytes - nt!PipCallDriverAddDevice+af (+0x13)
    [ 89 83 6c 01:00 00 00 00 ]
    82c0c3d6-82c0c3db  6 bytes - nt!PipCallDriverAddDevice+b5 (+0x06)
    [ eb 06 89 8b 6c 01:00 00 00 00 00 00 ]
    82c0c3de-82c0c3e1  4 bytes - nt!PipCallDriverAddDevice+bd (+0x08)
    [ 8b 83 6c 01:00 00 00 00 ]
WARNING: !chkimg output was truncated to 50 lines. Invoke !chkimg without '-lo [num_lines]' to view  entire output.
3541 errors : !nt (82c0c000-82c0cffe)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  LARGE_4096

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_LARGE_4096

BUCKET_ID:  MEMORY_CORRUPTION_LARGE_4096

Followup: memory_corruption
---------
My System SpecsSystem Spec
16 Jun 2011   #5

windows7 home premium 32bit
 
 

hi below is the CHKDSK info as requested

Checking file system on C:
The type of the file system is NTFS.
A disk check has been scheduled.
Windows will now check the disk.
CHKDSK is verifying files (stage 1 of 5)...
172544 file records processed. File verification completed.
730 large file records processed. 0 bad file records processed. 0 EA records processed. 44 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)...
221544 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)...
172544 file SDs/SIDs processed. Cleaning up 814 unused index entries from index $SII of file 0x9.
Cleaning up 814 unused index entries from index $SDH of file 0x9.
Cleaning up 814 unused security descriptors.
Security descriptor verification completed.
24501 data files processed. CHKDSK is verifying Usn Journal...
33939544 USN bytes processed. Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
172528 files processed. File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
96366307 free clusters processed. Free space verification is complete.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.
442304511 KB total disk space.
56453052 KB in 145719 files.
99852 KB in 24502 indexes.
0 KB in bad sectors.
286375 KB in use by the system.
65536 KB occupied by the log file.
385465232 KB available on disk.
4096 bytes in each allocation unit.
110576127 total allocation units on disk.
96366308 allocation units available on disk.
Internal Info:
00 a2 02 00 f9 98 02 00 2e cf 04 00 00 00 00 00 ................
1f 11 00 00 2c 00 00 00 00 00 00 00 00 00 00 00 ....,...........
58 91 29 00 50 01 28 00 80 1d 28 00 00 00 28 00 X.).P.(...(...(.
Windows has finished checking your disk.
Please wait while your computer restarts.
My System SpecsSystem Spec
16 Jun 2011   #6

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by tez1982 View Post
hi below is the CHKDSK info as requested

Checking file system on C:
The type of the file system is NTFS.
A disk check has been scheduled.
Windows will now check the disk.
CHKDSK is verifying files (stage 1 of 5)...
172544 file records processed. File verification completed.
730 large file records processed. 0 bad file records processed. 0 EA records processed. 44 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)...
221544 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)...
172544 file SDs/SIDs processed. Cleaning up 814 unused index entries from index $SII of file 0x9.
Cleaning up 814 unused index entries from index $SDH of file 0x9.
Cleaning up 814 unused security descriptors.
Security descriptor verification completed.
24501 data files processed. CHKDSK is verifying Usn Journal...
33939544 USN bytes processed. Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
172528 files processed. File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
96366307 free clusters processed. Free space verification is complete.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.
442304511 KB total disk space.
56453052 KB in 145719 files.
99852 KB in 24502 indexes.
0 KB in bad sectors.
286375 KB in use by the system.
65536 KB occupied by the log file.
385465232 KB available on disk.
4096 bytes in each allocation unit.
110576127 total allocation units on disk.
96366308 allocation units available on disk.
Internal Info:
00 a2 02 00 f9 98 02 00 2e cf 04 00 00 00 00 00 ................
1f 11 00 00 2c 00 00 00 00 00 00 00 00 00 00 00 ....,...........
58 91 29 00 50 01 28 00 80 1d 28 00 00 00 28 00 X.).P.(...(...(.
Windows has finished checking your disk.
Please wait while your computer restarts.
So chkdsk found errors and repaired them. Next step is to go to the HD mfr's site and download their diagnostic tool and run it on the hd.
My System SpecsSystem Spec
Reply

 BSOD when using bittorrent




Thread Tools



Similar help and support threads for2: BSOD when using bittorrent
Thread Forum
BSOD when using a BitTorrent Client. BSOD Help and Support
Solved BSOD when using a BitTorrent Client. BSOD Help and Support
Solved BSOD while downloading via Bittorrent BSOD Help and Support
Solved BSOD when downloading with u-/bittorrent BSOD Help and Support
BSOD when using UTorrent or Bittorrent BSOD Help and Support
BSOD while running uTorrent or BitTorrent BSOD Help and Support
BSOD when open bittorrent 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 01:21 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33