Windows 7 BSOD BCCode 1e

Upyrs07 · 20 Jul 2011

Hello seven forums I need some help from an issue I have been having. I have a self built pc of around 7-8 months old that has randomly been giving BSODS. The error usually pops up when I am either watching videos or playing a graphics intensive game. This is the error I receive:
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033

Additional information about the problem:
BCCode: 1e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF880032CA9E0
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\071911-18640-01.dmp
C:\Users\Upyrs07\AppData\Local\Temp\WER-43890-0.sysdata.xml

The OS is OEM, Windows 7 Professional and I have never reinstalled, nor has there been a different OS installed prior to this one.

yowanvista · 20 Jul 2011

Update any Acronis software, yours is obsolete

Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads
You can use MagicDisc as an alternative.

Update Marvell Yukon Network driver, it is the cause of BSODs http://www.marvell.com/support.html

Code:

sptd.sys        fffff880`01091000    fffff880`011b7000    0x00126000    0x4ad24632    12/10/2009 00:55:14

Code:

yk62x64.sys        fffff880`02ebb000    fffff880`02f20000    0x00065000    0x4c15dca4    14/06/2010 11:39:16

Code:

*******************************************************************************
*                                                                             *
*                        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: fffff880032ca9e0, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


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

FAULTING_IP: 
+0
fffff880`032ca9e0 08b92c0380f8    or      byte ptr [rcx-77FFCD4h],bh

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003ab9100
 0000000000000000 

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  System

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff880032cb908 -- (.exr 0xfffff880032cb908)
ExceptionAddress: fffff80003881f35 (nt!ExInterlockedInsertTailList+0x0000000000000005)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff880032cb9b0 -- (.trap 0xfffff880032cb9b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8007d4ed50 rbx=0000000000000000 rcx=bffffa8007c86998
rdx=fffffa8007d73370 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003881f35 rsp=fffff880032cbb40 rbp=0000000000000000
 r8=bffffa8007c869a8  r9=0000000000000000 r10=fffffa8007cc0e00
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di ng nz na pe nc
nt!ExInterlockedInsertTailList+0x5:
fffff800`03881f35 f0490fba2800    lock bts qword ptr [r8],0 ds:0008:bffffa80`07c869a8=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800039124fb to fffff80003889d00

STACK_TEXT:  
fffff880`032ca928 fffff800`039124fb : 00000000`0000001e ffffffff`c0000005 fffff880`032ca9e0 00000000`00000000 : nt!KeBugCheckEx
fffff880`032ca930 fffff800`038ddbe4 : 00000000`00000074 fffffa80`07c83f78 fffffa80`07c83f58 00000000`00000001 : nt!KipFatalFilter+0x1b
fffff880`032ca970 fffff800`038b5adc : fffffa80`07dbe030 fffffa80`07b5f050 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x83d
fffff880`032ca9b0 fffff800`038b555d : fffff800`039c9d4c fffff880`032cc440 00000000`00000000 fffff800`0380a000 : nt!_C_specific_handler+0x8c
fffff880`032caa20 fffff800`038b4335 : fffff800`039c9d4c fffff880`032caa98 fffff880`032cb908 fffff800`0380a000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`032caa50 fffff800`038c53b1 : fffff880`032cb908 fffff880`032cb160 fffff880`00000000 00000000`00000005 : nt!RtlDispatchException+0x415
fffff880`032cb130 fffff800`03889382 : fffff880`032cb908 fffffa80`07c83000 fffff880`032cb9b0 00000000`00000000 : nt!KiDispatchException+0x135
fffff880`032cb7d0 fffff800`03887c8a : fffffa80`08113bd0 fffffa80`09065e50 fffffa80`08113bd0 fffff880`02f74228 : nt!KiExceptionDispatch+0xc2
fffff880`032cb9b0 fffff800`03881f35 : 00000000`00000282 fffff880`04421ca7 fffffa80`08d202a0 00000000`00000000 : nt!KiGeneralProtectionFault+0x10a
fffff880`032cbb40 fffff880`04421ca7 : fffffa80`08d202a0 00000000`00000000 fffffa80`08d19900 fffff880`04421c04 : nt!ExInterlockedInsertTailList+0x5
fffff880`032cbb50 fffffa80`08d202a0 : 00000000`00000000 fffffa80`08d19900 fffff880`04421c04 fffffa80`07b5f1a0 : yk62x64+0x18ca7
fffff880`032cbb58 00000000`00000000 : fffffa80`08d19900 fffff880`04421c04 fffffa80`07b5f1a0 fffff880`0174d8d4 : 0xfffffa80`08d202a0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
yk62x64+18ca7
fffff880`04421ca7 ??              ???

SYMBOL_STACK_INDEX:  a

SYMBOL_NAME:  yk62x64+18ca7

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: yk62x64

IMAGE_NAME:  yk62x64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c15dca4

FAILURE_BUCKET_ID:  X64_0x1E_yk62x64+18ca7

BUCKET_ID:  X64_0x1E_yk62x64+18ca7

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

Upyrs07 · 20 Jul 2011

Ok so the outdated marvell driver and the CD virtualization software are behind those bsods. Thanks for the help, really appreciated. I will post back soon to show the results and cross my fingers in hopes that blue screens wont pop up again.:)

Upyrs07 · 21 Jul 2011

Yep, my PC has been BSOD free all day long. Thanks yowanvista for the help.