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 Using utorrent BCCode: d1

07 Jan 2013   #1

Windows 7 Ultimate x64
 
 
BSOD Using utorrent BCCode: d1

Hi,
I did some reading on my issue and it seems others have had similar problems to mine, yet different error codes. When using utorrent the BSOD will appear. It tends to occur not long after starting. Some suggestions I have read involve anti-virus software which I don't have, and issues with the wireless driver. I suspect this could be the issue but am not smart enough to know for sure. The following is a copy of the action center report:
Source
Windows

Summary
Shut down unexpectedly

Date
‎11/‎24/‎2012 3:26 PM

Status
Not reported

Problem signature
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033

Files that help describe the problem
112112-25318-01.dmp
sysdata.xml
WERInternalMetadata.xml

Extra information about the problem
BCCode: d1
BCP1: 0000000000000331
BCP2: 0000000000000002
BCP3: 0000000000000001
BCP4: FFFFF8800211776E
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Other notes: This is my first solo computer build. I'm fairly confidant that all the hardware is compatible. The wireless adapter was kind of cheap, an encore electronics usb adapter N150. I am in the process of finding an updated version of this driver. I also run two hard drives, a solid state for OS and a regular where torrent downloads go. At times I hear a clicking sound when I access my downloads files.

Thanks for the help

My System SpecsSystem Spec
07 Jan 2013   #2

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64Bit
 
 

Welcome to SevenForums.

Please post the following report:Your recent .dmp file comes with BCC 116. Go through this thread on how to troubleshoot:
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800f10f010, fffff8800ffe6354, 0, d}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+156354 )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800f10f010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800ffe6354, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 000000000000000d, Optional internal context dependent data.

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


FAULTING_IP: 
nvlddmkm+156354
fffff880`0ffe6354 4883ec28        sub     rsp,28h

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`01f4e988 fffff880`10b49cbc : 00000000`00000116 fffffa80`0f10f010 fffff880`0ffe6354 00000000`00000000 : nt!KeBugCheckEx
fffff880`01f4e990 fffff880`10b49a43 : fffff880`0ffe6354 fffffa80`0f10f010 fffffa80`0e857c00 fffffa80`0ef55280 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`01f4e9d0 fffff880`0fe0ff07 : fffffa80`0f10f010 00000000`00000000 fffffa80`0e857c00 fffffa80`0ef55280 : dxgkrnl!TdrIsRecoveryRequired+0x21f
fffff880`01f4ea00 fffff880`0fe39b75 : 00000000`ffffffff 00000000`000015ca 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`01f4eae0 fffff880`0fe382bb : 00000000`00000102 00000000`00000000 00000000`000015ca 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`01f4eb10 fffff880`0fe0b2c6 : ffffffff`ff676980 fffffa80`0ef55280 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`01f4ebb0 fffff880`0fe37e7a : 00000000`00000000 fffffa80`0e857c00 00000000`00000080 fffffa80`0ef55280 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`01f4ecc0 fffff800`02f79166 : 00000000`fffffc32 fffffa80`0ef574d0 fffffa80`0cd5f040 fffffa80`0ef574d0 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`01f4ed00 fffff800`02cb4486 : fffff800`02e4ee80 fffffa80`0ef574d0 fffff800`02e5cc40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`01f4ed40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+156354
fffff880`0ffe6354 4883ec28        sub     rsp,28h

SYMBOL_NAME:  nvlddmkm+156354

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d27c6da

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

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

6: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0fe90000 fffff880`10aead00   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Sat Jan 08 08:07:22 2011 (4D27C6DA)
    CheckSum:         00C5F2DA
    ImageSize:        00C5AD00
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
Check for an update on this driver:
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {331, 2, 1, fffff880060d676e}

*** WARNING: Unable to verify timestamp for RTL8192cu.sys
*** ERROR: Module load completed but symbols could not be loaded for RTL8192cu.sys
Probably caused by : RTL8192cu.sys ( RTL8192cu+8c76e )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000331, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff880060d676e, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ec60e0
GetUlongFromAddress: unable to read from fffff80002ec6198
 0000000000000331 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
RTL8192cu+8c76e
fffff880`060d676e 80a331030000fd  and     byte ptr [rbx+331h],0FDh

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TAG_NOT_DEFINED_c000000f:  FFFFF80000BA2FB0

TRAP_FRAME:  fffff80000b9c5c0 -- (.trap 0xfffff80000b9c5c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa80106c3018 rbx=0000000000000000 rcx=fffffa800f35d000
rdx=fffffa800f88a148 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880060d676e rsp=fffff80000b9c750 rbp=fffffa800f35d000
 r8=0000000000000000  r9=0000000000000880 r10=0000000000000001
r11=fffff80000b9c7c8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
RTL8192cu+0x8c76e:
fffff880`060d676e 80a331030000fd  and     byte ptr [rbx+331h],0FDh ds:00000000`00000331=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c8f469 to fffff80002c8ff00

STACK_TEXT:  
fffff800`00b9c478 fffff800`02c8f469 : 00000000`0000000a 00000000`00000331 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff800`00b9c480 fffff800`02c8e0e0 : fffffa80`00000000 00000000`00000000 fffffa80`00000000 fffff880`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`00b9c5c0 fffff880`060d676e : fffffa80`0f354b80 fffff800`02c7b04a 00000000`00000000 fffffa80`0f33f5f0 : nt!KiPageFault+0x260
fffff800`00b9c750 fffffa80`0f354b80 : fffff800`02c7b04a 00000000`00000000 fffffa80`0f33f5f0 fffffa80`0f35d000 : RTL8192cu+0x8c76e
fffff800`00b9c758 fffff800`02c7b04a : 00000000`00000000 fffffa80`0f33f5f0 fffffa80`0f35d000 fffffa80`0f35d000 : 0xfffffa80`0f354b80
fffff800`00b9c760 fffff800`00b9c780 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`0f32e300 : nt!IoReuseIrp+0x3a
fffff800`00b9c790 00000000`00000000 : 00000000`00000000 00000000`00000000 fffffa80`0f32e300 fffffa80`0f35d000 : 0xfffff800`00b9c780


STACK_COMMAND:  kb

FOLLOWUP_IP: 
RTL8192cu+8c76e
fffff880`060d676e 80a331030000fd  and     byte ptr [rbx+331h],0FDh

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  RTL8192cu+8c76e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: RTL8192cu

IMAGE_NAME:  RTL8192cu.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c174e98

FAILURE_BUCKET_ID:  X64_0xD1_RTL8192cu+8c76e

BUCKET_ID:  X64_0xD1_RTL8192cu+8c76e

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

0: kd> lmvm RTL8192cu
start             end                 module name
fffff880`0604a000 fffff880`0615c000   RTL8192cu T (no symbols)           
    Loaded symbol image file: RTL8192cu.sys
    Image path: \SystemRoot\system32\DRIVERS\RTL8192cu.sys
    Image name: RTL8192cu.sys
    Timestamp:        Tue Jun 15 15:57:44 2010 (4C174E98)
    CheckSum:         000BFA37
    ImageSize:        00112000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
My System SpecsSystem Spec
Reply

 BSOD Using utorrent BCCode: d1





Thread Tools



Similar help and support threads for2: BSOD Using utorrent BCCode: d1
Thread Forum
Solved three different BSOD during 2 nights bccode 1A and bccode 24 and D1 BSOD Help and Support
BSOD:: BCCode: 116; BCCode: f4 (mostly f4) BSOD Help and Support
BSOD after using utorrent! Please help! BSOD Help and Support
BSOD during high bandwith situations. Bccode a, bccode b1. BSOD Help and Support
BSOD from new memory card, BCCode:d1 & BCCode:fc BSOD Help and Support
BSOD occurs randomly (maybe caused by uTorrent?), BCCode: d1 BSOD Help and Support
BSOD Internet Explorer,MSE, uTorrent, etc. BCCode: be 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:01 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