Blue screen of death help!

Graphics driver issue. Try Reinstalling DirectX (as DirectX was referenced) as well as your nVidia drivers. Use DDU from Guru3D to completely remove your old drivers before reinstalling the new drivers.

Code: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys

Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiFreeQueuePacket+80 )

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

6: 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: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  GTA5.exe

CURRENT_IRQL:  2

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) x86fre

DPC_STACK_BASE:  FFFFF88003146FB0

EXCEPTION_RECORD:  fffff88003146768 -- (.exr 0xfffff88003146768)
ExceptionAddress: fffff800032b35a2 (nt!KxWaitForLockOwnerShip+0x0000000000000012)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff88003146810 -- (.trap 0xfffff88003146810)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=fffff88003146a40
rdx=0020000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800032b35a2 rsp=fffff880031469a0 rbp=fffffa800da04018
 r8=fffff88003146a40  r9=fffffa8014743f58 r10=fffffa800f9a77d0
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!KxWaitForLockOwnerShip+0x12:
fffff800`032b35a2 48890a          mov     qword ptr [rdx],rcx ds:00200000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800032798be to fffff80003281e90

STACK_TEXT:  
fffff880`03145848 fffff800`032798be : fffff880`0443fe40 fffff880`0442c45e fffff880`03145fc0 fffff800`032ada00 : nt!KeBugCheck
fffff880`03145850 fffff800`032ad6cd : fffff800`03492398 fffff800`033cb22c fffff800`0320d000 fffff880`03146768 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`03145880 fffff800`032ac4a5 : fffff800`033d32c4 fffff880`031458f8 fffff880`03146768 fffff800`0320d000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`031458b0 fffff800`032bd431 : fffff880`03146768 fffff880`03145fc0 fffff880`00000000 fffff880`00000004 : nt!RtlDispatchException+0x415
fffff880`03145f90 fffff800`03281542 : fffff880`03146768 00000000`00000000 fffff880`03146810 fffff880`03117180 : nt!KiDispatchException+0x135
fffff880`03146630 fffff800`0327fe4a : fffffa80`0fb81810 fffffa80`0fb81858 fffffa80`0fb81858 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`03146810 fffff800`032b35a2 : 00000005`10000000 00000000`00000000 fffffa80`14743d50 fffffa80`0da04018 : nt!KiGeneralProtectionFault+0x10a
fffff880`031469a0 fffff800`0328be2d : 00000000`00000000 fffffa80`0f9a77a8 fffffa80`14743f48 fffffa80`14743f58 : nt!KxWaitForLockOwnerShip+0x12
fffff880`031469d0 fffff880`061b2744 : fffffa80`0da04018 00000000`00000000 fffffa80`14743f58 00000000`00000002 : nt!KeAcquireInStackQueuedSpinLock+0x8d
fffff880`03146a20 fffff880`061b1377 : fffffa80`0da04010 fffffa80`13872010 fffffa80`0fad3000 fffffa80`0fad3000 : dxgmms1!VidSchiFreeQueuePacket+0x80
fffff880`03146a70 fffff880`061b07e6 : fffffa80`00000000 fffffa80`00000000 00000000`00000002 00000000`00000000 : dxgmms1!VidSchiProcessCompletedQueuePacketInternal+0x443
fffff880`03146b30 fffff880`061afe0c : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`0567bc9e : dxgmms1!VidSchiProcessDpcCompletedPacket+0x3b6
fffff880`03146bd0 fffff880`061afc58 : fffffa80`143fc002 fffffa80`0f9a7010 00000000`00000000 fffffa80`0ebabaa8 : dxgmms1!VidSchDdiNotifyDpcWorker+0x198
fffff880`03146c20 fffff880`060b51cf : fffffa80`0ebab480 00000000`00000050 00000000`4b2164e0 00000000`00000022 : dxgmms1!VidSchDdiNotifyDpc+0x94
fffff880`03146c70 fffff880`0574970e : fffffa80`0ebab480 fffffa80`0ebab480 fffffa80`0ebabaa8 fffffa80`0eb94000 : dxgkrnl!DxgNotifyDpcCB+0x77
fffff880`03146ca0 fffffa80`0ebab480 : fffffa80`0ebab480 fffffa80`0ebabaa8 fffffa80`0eb94000 fffff880`0574969f : nvlddmkm+0xcf70e
fffff880`03146ca8 fffffa80`0ebab480 : fffffa80`0ebabaa8 fffffa80`0eb94000 fffff880`0574969f fffffa80`0eb94000 : 0xfffffa80`0ebab480
fffff880`03146cb0 fffffa80`0ebabaa8 : fffffa80`0eb94000 fffff880`0574969f fffffa80`0eb94000 00000000`00000000 : 0xfffffa80`0ebab480
fffff880`03146cb8 fffffa80`0eb94000 : fffff880`0574969f fffffa80`0eb94000 00000000`00000000 00000000`00000000 : 0xfffffa80`0ebabaa8
fffff880`03146cc0 fffff880`0574969f : fffffa80`0eb94000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`0eb94000
fffff880`03146cc8 fffffa80`0eb94000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nvlddmkm+0xcf69f
fffff880`03146cd0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`0ebab480 : 0xfffffa80`0eb94000


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VidSchiFreeQueuePacket+80
fffff880`061b2744 48393f          cmp     qword ptr [rdi],rdi

SYMBOL_STACK_INDEX:  9

SYMBOL_NAME:  dxgmms1!VidSchiFreeQueuePacket+80

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5164dc13

IMAGE_VERSION:  6.1.7601.18126

FAILURE_BUCKET_ID:  X64_0x1E_dxgmms1!VidSchiFreeQueuePacket+80

BUCKET_ID:  X64_0x1E_dxgmms1!VidSchiFreeQueuePacket+80

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x1e_dxgmms1!vidschifreequeuepacket+80

FAILURE_ID_HASH:  {d6ffb774-8284-9b53-18b0-3643901ddb4a}

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

6: kd> lmvm dxgmms1
start             end                 module name
fffff880`061a7000 fffff880`061ed000   dxgmms1    (pdb symbols)          d:\symbols\dxgmms1.pdb\93AB163000A844D5BF442A979FB6FF991\dxgmms1.pdb
    Loaded symbol image file: dxgmms1.sys
    Mapped memory image file: d:\symbols\dxgmms1.sys\5164DC1346000\dxgmms1.sys
    Image path: dxgmms1.sys
    Image name: dxgmms1.sys
    Timestamp:        Tue Apr 09 22:27:15 2013 (5164DC13)
    CheckSum:         00043C9B
    ImageSize:        00046000
    File version:     6.1.7601.18126
    Product version:  6.1.7601.18126
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.7 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     dxgmms1.sys
    OriginalFilename: dxgmms1.sys
    ProductVersion:   6.1.7601.18126
    FileVersion:      6.1.7601.18126 (win7sp1_gdr.130409-1534)
    FileDescription:  DirectX Graphics MMS
    LegalCopyright:   © Microsoft Corporation. All rights reserved.
 
How very strange, we did this already in the previous post! But alas, I shall do what you say, clearly something has been done wrong. Does DDU properly remove direct x as well? I'll get to doing it now, I just wan't it done right!
 
No, DDU doesn't do anything with DirectX. It will only touch your nVidia driver files.

I know we've done this before - that's why I suggested completely reinstalling Windows as a fresh install, install your necessary games/drivers, and we can find out if it's a software issue or hardware issue then.
 
Okay I'll take a final shot at reinstalling drivers and direct X and see how it go's. If that doesn't work, I guess a wipe is in order! What hardware pieces are you thinking could be the problem?
 
Slothraki said:
Okay I'll take a final shot at reinstalling drivers and direct X and see how it go's. If that doesn't work, I guess a wipe is in order! What hardware pieces are you thinking could be the problem?
Click to expand...

Well, either GPU, motherboard, or (maybe) CPU. Can rule RAM out since you already bought a new set, IIRC.
 
Well I done the above and still no luck. I just spoke to someone who runs a computer repair place and he seems to think its the RAM from the last minidump I sent you. At a complete loss now.
 
You must log in or register to reply here.

Similar threads

P
Blue screen error again?
2
Replies
16
Views
2K
phantom555
P
A
HELP!
Replies
0
Views
280
arncap
A
M
How to couple Desktop Gaming PC to Laptop for Streaming?
Replies
0
Views
530
motaro38
M
B
Multiple Seagate External Drives Not Working(Windows+Mac)
Replies
2
Views
413
Joe C
Joe C
L
My pc crashes when I try to play most games
2 3
Replies
23
Views
4K
PP Mguire
PP Mguire
Back
Top Bottom