BSOD with uTorrent

[unclescrooge]

Hi. Just a quick thanks in advance

Never had an issue with downloading using uTorrent until the last 6-12 months. The only new hardware includes:

• Video card
• SSD
• WD 4TB Green drive

As suggested by other threads, I have:

• updated network adapter drivers
• uninstalled PC Tool's Spyware Doctor (and have MSE in its place)
• flashed the BIOS
• updated video card drivers

I've been to Google with multiple error codes and he hasn't been a very good friend as of late. The only reason I can think of is that perhaps, the PSU does not have enough juice? I am running four HDDs, an optical drive, a video card and four fans. Pretty sure it's not the issue as I encounter no problems when playing graphics-intensive games. Corsair PSUs are highly recommended as well.

I'm looking for some guidance on the source of the BSODs and would appreciate any clarity on this.

Many thanks again

 

[matts6887]

off the top of my head; it sounds like it could have something to do with the u torrent program itself. sounds like something has possibly corrupted one or more files for the u torrent. I would try uninstalling the program and reinstalling it and see what happens and we can go from there.

 

[Arc]

Hi matts6887.

For the network issue, network is being blocked by some element.

fffff880`033bc130  fffff880`04170005Unable to load image \??\C:\Windows\System32\drivers\[URL="http://www.carrona.org/drivers/driver.php?id=pctgntdi64.sys"]pctgntdi64.sys[/URL], Win32 error 0n2
*** WARNING: Unable to verify timestamp for [URL="http://www.carrona.org/drivers/driver.php?id=pctgntdi64.sys"]pctgntdi64.sys[/URL]
*** ERROR: Module load completed but symbols could not be loaded for [URL="http://www.carrona.org/drivers/driver.php?id=pctgntdi64.sys"]pctgntdi64.sys[/URL]
 pctgntdi64+0x42005

It appears that you have uninstalled PC Tools Internet Security already?

The realtek network driver is also failing.

fffff880`033bce78  fffff880`0b81b9b0Unable to load image \SystemRoot\system32\DRIVERS\Rt64win7.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for [URL="http://carrona.org/drivers/driver.php?id=Rt64win7.sys"]Rt64win7.sys[/URL]
*** ERROR: Module load completed but symbols could not be loaded for [URL="http://carrona.org/drivers/driver.php?id=Rt64win7.sys"]Rt64win7.sys[/URL]
 Rt64win7+0x1b9b0

The driver is very old. Get the first one (Win7 and WinServer 2008 R2 Driver) from Realtek. Follow http://www.sevenforums.com/tutorials/97061-driver-install-device-manager.html to install the driver.

But that is not the main issue. You are having some drastic disc failure.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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

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


[COLOR=Red]ERROR_CODE: (NTSTATUS) 0xc000009d - STATUS_DEVICE_NOT_CONNECTED[/COLOR]

[COLOR=Red]DISK_HARDWARE_ERROR: There was error with disk hardware[/COLOR]

BUGCHECK_STR:  0x7a_c000009d

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  1

LAST_CONTROL_TRANSFER:  from fffff80002cccc8c to fffff80002cd8bc0

Just noticed an almost similar issue with Corsair Force GT, here: http://www.sevenforums.com/bsod-hel...pc-sometime-error-0x0000007a.html#post2623209

Some suggestions will be applicable for you too.

Make it sure that the Corsair Force GT is running with the latest firmware. They do it via their forums: The Corsair Support Forums - Powered by vBulletin

Check your 4 TB HDD with Data Lifeguard Diagnostic for Windows.

Re-seat the sata and power cables. Re-seat the SSD too. Change the SATA cables. Apply the SATA cable to another unused SATA port on the motherboard. Make it sure that all the screws holding the HDD to the stand are tightly screwed.

• 

Let us know the results.

 

[unclescrooge]

For the network issue, network is being blocked by some element. It appears that you have uninstalled PC Tools Internet Security already?

Correct. The two older dumps were from before it was uninstalled.

The realtek network driver is also failing. The driver is very old. Get the first one (Win7 and WinServer 2008 R2 Driver) from Realtek. Follow http://www.sevenforums.com/tutorials/97061-driver-install-device-manager.html to install the driver.

Done. The dump file you are inspecting is perhaps one of the older ones... I had updated it to the one from the Gigabyte website. In this instance however, the Realtek website had a newer one so it was again updated.

But that is not the main issue. You are having some drastic disc failure.

Make it sure that the Corsair Force GT is running with the latest firmware. They do it via their forums: The Corsair Support Forums - Powered by vBulletin

Re-seat the sata and power cables. Re-seat the SSD too. Change the SATA cables. Apply the SATA cable to another unused SATA port on the motherboard. Make it sure that all the screws holding the HDD to the stand are tightly screwed.

Let us know the results.

I also suspect that this may be the main cause of the failures. There are instances when I reboot only to be greeted with "disk boot failure" during POST. I will run uTorrent overnight to see if perhaps the LAN driver is the culprit. Otherwise, I'd have to get the elbow grease going. I should have bought a larger case.. lol

Many thanks

 

[unclescrooge]

Hi Team,

Another BSOD today. Please see attached file for *.dmp file dated 18/12/12. Will proceed to unseat and replace the SATA and power cable to the SSD.

Can you kindly confirm from the latest BSOD that it's indeed a HDD issue.

Many thanks

 

[Arc]

The crash dump is not very precise about the probable cause, but indication to some display misfunctions.

Install the NVIDIA DRIVERS 314.22WHQL only, as the later versions are not very stable in all the systems.

• Uninstall All nvidia items in Control Panel > Programs and features
  • 3D Vision Control Driver
  • 3D Vision Driver
  • Graphics Driver
  • HD Audio Driver
  • PhysX
  • nvidia Update
  (Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
• Now follow Drivers - Clean Left over Files after Uninstalling
• Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:
  
  

Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept then restart.

Let us know the results.
_________________________________________________________________________________________________

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff80002cb2061, 0, ffffffffffffffff}

Probably caused by : memory_corruption ( nt!MiUnlinkFreeOrZeroedPage+181 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002cb2061, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eca100
GetUlongFromAddress: unable to read from fffff80002eca1c0
 0000000000000000 Nonpaged pool

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!MiUnlinkFreeOrZeroedPage+181
fffff800`02cb2061 48893cc2        mov     qword ptr [rdx+rax*8],rdi

BUGCHECK_STR:  0x1E_c0000005_R

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002cdd738 to fffff80002c92bc0

STACK_TEXT:  
fffff880`0bed9e28 fffff800`02cdd738 : 00000000`0000001e ffffffff`c0000005 fffff800`02cb2061 00000000`00000000 : nt!KeBugCheckEx
fffff880`0bed9e30 fffff800`02c92242 : fffff880`0beda608 fffffa80`0027d770 fffff880`0beda6b0 fffffa80`03c01388 : nt! ?? ::FNODOBFM::`string'+0x487ed
fffff880`0beda4d0 fffff800`02c90b4a : fffff880`0beda790 fffff880`1320c6c5 fffff880`0beda7a0 fffff880`1320c6c5 : nt!KiExceptionDispatch+0xc2
fffff880`0beda6b0 fffff800`02cb2061 : 00000000`00000000 fffff880`1323688b fffffa80`045c9000 fffff880`13233b7f : nt!KiGeneralProtectionFault+0x10a
fffff880`0beda840 fffff800`02cb6898 : fffff880`0beda900 00000000`0000d47d fffffa80`0027d770 fffff880`00000000 : nt!MiUnlinkFreeOrZeroedPage+0x181
fffff880`0beda8b0 fffff800`02ca2adf : 00000000`00000002 fffff880`00000002 fffffa80`066523f8 00000000`00000002 : nt!MiRemoveAnyPage+0x1d8
fffff880`0beda9d0 fffff800`02c9f3fe : 00000000`00000001 00000000`095d2000 fffff880`0bedac20 fffff680`0004ae90 : nt!MiResolveDemandZeroFault+0x54f
fffff880`0bedaac0 fffff800`02c90cee : 00000000`00000001 00000000`095d2000 fffff880`00000001 00000000`095d1fd0 : nt!MmAccessFault+0x5de
fffff880`0bedac20 00000000`64147000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`0016e5a4 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x64147000


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiUnlinkFreeOrZeroedPage+181
fffff800`02cb2061 48893cc2        mov     qword ptr [rdx+rax*8],rdi

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nt!MiUnlinkFreeOrZeroedPage+181

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  521ea035

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x1E_c0000005_R_nt!MiUnlinkFreeOrZeroedPage+181

BUCKET_ID:  X64_0x1E_c0000005_R_nt!MiUnlinkFreeOrZeroedPage+181

Followup: MachineOwner
---------

 

[unclescrooge]

Hi Arc,

Appreciate the prompt response!

As directed:

- all nVidia items have been uninstalled from the Control Panel
- DDU run in safe mode
- all items except MSE deselected on startup
- nVidia Driver 314.22WHQL installed with "Custom Installation"

Are there any further steps I should take before stress testing?

 

[Arc]

Based on the crash dump, as the "probably caused by" line is saying a memory corruption, you may test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.
If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Also, as the hint of display failure is seen, you may test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

 

[unclescrooge]

Ah, the good ol' Memtest! I'll run it tonight before I head to bed. Will return with my findings.

Regards.

 

[unclescrooge]

Memtest ran for 9 passes overnight - zero errors. Will stress-test the GPU tonight and report back with findings.

 

[Arc]

Good and releieveing news

 

[unclescrooge]

I've run Furmark multiple times and each time, I have noticed visual artefacts every 10 or so seconds in the lower portion of the screen. Is this clear evidence that the video card is defective?

 

[Arc]

I've run Furmark multiple times and each time, I have noticed visual artefacts every 10 or so seconds in the lower portion of the screen. Is this clear evidence that the video card is defective?

Unfortunately, but it is.

 

[unclescrooge]

Another BSOD. Any further information? Thanks again

 

[Arc]

Nothing new.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7A, {20, ffffffffc000009d, fffffa8004efc7c8, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+50080 )

Followup: MachineOwner
---------