1. TechSpot is dedicated to computer enthusiasts and power users. Ask a question and give support. Join the community here.
    TechSpot is dedicated to computer enthusiasts and power users.
    Ask a question and give support.
    Join the community here, it only takes a minute.
    Dismiss Notice

BSOD while computer is under heavy load

By Daexx
Aug 9, 2013
Post New Reply
  1. Hi,

    Could anyone please see if possible to shed some light on this BSOD , I have been reviewing it myself but I am not sure where to go . Memory test passed, check disk fine, dust cleaned, old PSU replaced with brand new Cooler Master GX-750W .. installed new driver for motherboard even though nothing really pointed there...

    6: kd> !analyze -v
    *																			*
    *						Bugcheck Analysis									*
    *																			*
    Invalid system memory was referenced.  This cannot be protected by try-except,
    it must be protected by a Probe.  Typically the address is just plain bad or it
    is pointing at freed memory.
    Arg1: fffff8a01223ce30, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff88008bc2fe8, If non-zero, the instruction address which referenced the bad memory
    Arg4: 0000000000000002, (reserved)
    Debugging Details:
    Could not read faulting driver name
    READ_ADDRESS:  fffff8a01223ce30
    fffff880`08bc2fe8 48035020		add	rdx,qword ptr [rax+20h]
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  System
    TRAP_FRAME:  fffff8800d959740 -- (.trap 0xfffff8800d959740)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffff8a01223ce10 rbx=0000000000000000 rcx=fffffa80073b53e0
    rdx=0000000000000030 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff88008bc2fe8 rsp=fffff8800d9598d0 rbp=0000000000000000
    r8=fffffa8005120570  r9=fffff8800d959901 r10=0000000000000000
    r11=fffffa80068d7010 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0		nv up ei pl nz na po nc
    fffff880`08bc2fe8 48035020		add	rdx,qword ptr [rax+20h] ds:fffff8a0`1223ce30=????????????????
    Resetting default scope
    LAST_CONTROL_TRANSFER:  from fffff80002f5a5d4 to fffff80002eddc00
    fffff880`0d9595d8 fffff800`02f5a5d4 : 00000000`00000050 fffff8a0`1223ce30 00000000`00000000 fffff880`0d959740 : nt!KeBugCheckEx
    fffff880`0d9595e0 fffff800`02edbd2e : 00000000`00000000 fffff8a0`1223ce30 00000000`00000000 fffff8a0`0df86750 : nt! ?? ::FNODOBFM::`string'+0x43836
    fffff880`0d959740 fffff880`08bc2fe8 : fffff8a0`10abc690 fffff880`08bc2d4b 00000000`00000092 00000000`00000000 : nt!KiPageFault+0x16e
    fffff880`0d9598d0 fffff880`08bc08af : 00000000`00000000 fffffa80`0689e188 00000000`00000092 fffffa80`073604a0 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0x98
    fffff880`0d959910 fffff880`08bda65d : 00000000`00000000 fffff8a0`0223ce10 fffffa80`00000000 fffffa80`03ff5f10 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xe1b
    fffff880`0d959ae0 fffff880`08bda398 : fffff880`03118040 fffff880`08bd9d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
    fffff880`0d959cd0 fffff880`08bd9e96 : 00000000`00000000 fffffa80`07461780 00000000`00000080 fffffa80`068d7010 : dxgmms1!VidSchiSubmitQueueCommand+0x50
    fffff880`0d959d00 fffff800`0317bede : 00000000`00000000 fffffa80`03d173a0 fffffa80`039d0040 00000000`00000221 : dxgmms1!VidSchiWorkerThread+0xd6
    fffff880`0d959d40 fffff800`02ece906 : fffff880`03113180 fffffa80`03d173a0 fffff880`0311e0c0 00000000`b74af400 : nt!PspSystemThreadStartup+0x5a
    fffff880`0d959d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
    fffff880`08bc2fe8 48035020		add	rdx,qword ptr [rax+20h]
    SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+98
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: dxgmms1
    IMAGE_NAME:  dxgmms1.sys
    FAILURE_BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+98
    BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+98
    Followup: MachineOwner

    Attached Files:

  2. Tmagic650

    Tmagic650 TS Ambassador Posts: 17,244   +234

    Looks like a video driver issue...
    Daexx likes this.
  3. Daexx

    Daexx TS Rookie Topic Starter

    Thanks Tmagic.

    I will give it a go with clearing nvidia drivers using driver sweeper.
  4. Daexx

    Daexx TS Rookie Topic Starter

    Uninstalled nvidia geforce 320.49 .. after reboot and going into uninstall programs menu again .. 320.18 driver appeared there ... it seems there was duplicate driver in the system.

    In any case uninstalled all nvidia drivers, cleaned the remains in safe mode with driver sweeper, installed 320.49 again and all seems good.

    Thanks ...

Similar Topics

Add New Comment

You need to be a member to leave a comment. Join thousands of tech enthusiasts and participate.
TechSpot Account You may also...