GPU-Z crashing/hard locking AMD Radeon Vega 64 pc. Have kernel dumps.

[Jeff Stokes]

8: kd> !locks
**** DUMP OF ALL RESOURCE OBJECTS ****
KD: Scanning for held locks................................................................................................................................

Resource @ 0xffffd98223b91b10    Exclusively owned
    Contention Count = 1258
    NumberOfSharedWaiters = 8
     Threads: ffffd9822c270080-01<*> ffffd9822e97a080-01    ffffd9822f8af080-01    ffffd982257ba0c0-01   
              ffffd9822fa47080-01    ffffd9822f61d080-01    ffffd98233dd9500-01    ffffd98227226400-01   
              ffffd98224fe8080-01   

Resource @ 0xffffd98223b91690    Shared 1 owning threads
     Threads: ffffd9823161a080-01<*>
KD: Scanning for held locks.

Resource @ 0xffffd9822525e8e0    Exclusively owned
     Threads: ffffd9822c270080-01<*>
KD: Scanning for held locks....................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................
55898 total locks, 3 locks currently held
8: kd> !blocksa
No export blocksa found
8: kd> !blocks

\\\   
 >>>  Blocking Lock 1 - nt!_ERESOURCE 0xffffd98223b91b10
///   

!er ffffd982`23b91b10 (in "DxgK" Pool)


Resource @ 0xffffd98223b91b10    Exclusively owned
    Contention Count = 1258
    NumberOfSharedWaiters = 8
     Threads: ffffd9822c270080-01<*> ffffd9822e97a080-01    ffffd9822f8af080-01    ffffd982257ba0c0-01   
              ffffd9822fa47080-01    ffffd9822f61d080-01    ffffd98233dd9500-01    ffffd98227226400-01   
              ffffd98224fe8080-01   
1 total locks


                                                          Cur  Bas   zContext      Kernel Time        User Time    Elapsed Ticks   Q-TSA   Thread    Wait                                      Waiting  | Overview | Start     
PROC Image Name       No.   Thread                   Id   Pri  Pri   Switches   d:hh:mm:ss.ttt   d:hh:mm:ss.ttt   d:hh:mm:ss.ttt  RrBLsrl   State  Reason  Notes        Waiting On             Function | Function | Function 

   8 Shared Waiters:
Invalid Thread(2) 00060001 Type = 0, should be 6.

   1 Exclusive Owner:
1E78 GPU-Z.exe          1   !t ffffd982`2c270080    1e7c   14    6      84445             .328            1.187            2.515  -------    Wait* Exec                 !ev ffffef05`2080d1a0  dxgmms2!VidSchWaitForEvents+0xf3


   ||
   || Blocking Locks Summary
   ||

      No.  Tag  Type Lock Addr           Waiters  Owners  Owner Thread                  Owner Wait Time   Tag  Owner Waiting On       Owner Function
        1  DxgK  !er ffffd982`23b91b10       8       1    !t ffffd982`2c270080                   2.515s        ???                    dxgmms2!VidSchWaitForEvents+0xf3

    1 blocking lock with 8 waiters found (55898 locks scanned) - for details run !blocks, !blocks <No.>, or one of the commands listed in the above summary

8: kd> !WinDE.t ffffd982`2c270080

\\\   
 >>>  Thread Dump - Thread Address ffffd9822c270080
///   

     !t ffffd982`2c270080 Thread  !tu ffffd982`2c270080   !k ffffd982`2c270080   !ku ffffd982`2c270080   !kp ffffd982`2c270080   !kpu ffffd982`2c270080 
!THREAD ffffd9822c270080  Cid 1e78.1e7c  Teb: 00000000004ca000 Win32Thread: ffffd9822cd17280 WAIT: (Executive) KernelMode Non-Alertable
    ffffef052080d1a0  SynchronizationEvent
Not impersonating
DeviceMap                 ffffc30db5793590
Owning Process            ffffd9822c27d080       Image:         GPU-Z.exe
Attached Process          N/A            Image:         N/A
Wait Start TickCount      259981         Ticks: 161 (0:00:00:02.515)
Context Switch Count      84445          IdealProcessor: 2             
UserTime                  00:00:01.187
KernelTime                00:00:00.328
Win32 Start Address 0x0000000001a27210
Stack Init ffffef052080dc90 Current ffffef052080cc30
Base ffffef052080e000 Limit ffffef0520808000 Call 0000000000000000
Priority 14 BasePriority 6 PriorityDecrement 96 IoPriority 1 PagePriority 2
Child-SP          RetAddr           : Args to Child                                                           : Call Site
ffffef05`2080cc70 fffff804`47e318c2 : ffff9e00`1d964180 ffffd982`ffffffff ffffd982`2cc2ae98 ffffd982`2c270080 : nt!KiSwapContext+0x76
ffffef05`2080cdb0 fffff804`47e30f54 : 00000000`00000002 00000000`00000000 00000000`00000000 ffff9e00`00000000 : nt!KiSwapThread+0x3f2
ffffef05`2080ce50 fffff804`47e306f5 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x144
ffffef05`2080cef0 fffff804`47e5854e : ffffef05`2080d1a0 fffff804`00000000 ffffd982`2525e400 ffffd982`00000000 : nt!KeWaitForSingleObject+0x255
ffffef05`2080cfd0 fffff804`59c5656f : ffffd982`2525e000 ffffd982`2525e670 ffffd982`2525e800 fffff804`47e20000 : nt!KeWaitForMultipleObjects+0x54e
ffffef05`2080d0e0 fffff804`59c52e5b : ffffd982`2d660010 ffffef05`2080d239 ffffd982`2525e000 00000000`00000001 : dxgmms2!VidSchWaitForEvents+0xf3
ffffef05`2080d160 fffff804`59c52a30 : ffffd982`2d660010 00000000`00000001 ffffd982`2d660010 00000000`00000000 : dxgmms2!VidSchSuspendResumeDevice+0x31b
ffffef05`2080d2a0 fffff804`59ccf1db : ffffd982`2525e000 ffffef05`2080d399 00000000`00000000 fffff804`557937d0 : dxgmms2!VidSchiSuspendResumeDevicesForPowerTransition+0x88
ffffef05`2080d300 fffff804`557c3300 : ffffd982`250d09a0 ffffd982`250d09a0 ffffc30d`00000001 00000000`00000003 : dxgmms2!VidSchSuspendAdapter+0x4b
ffffef05`2080d400 fffff804`5587b6d5 : 00000000`01000000 00000000`00002000 00000000`00000001 00000000`00000003 : dxgkrnl!ADAPTER_RENDER::SuspendScheduler+0x78
ffffef05`2080d430 fffff804`556f27d1 : ffffef05`2080d7a8 fffff804`00000003 ffffd982`00000002 ffffc30d`00000000 : dxgkrnl!DXGADAPTER::AcquireCoreResourceExclusive+0xb5519
ffffef05`2080d4a0 fffff804`556f271e : ffffef05`2080d7a0 00000000`00000000 00000000`00000000 ffffffff`ffffffff : dxgkrnl!COREACCESS::AcquireExclusive+0x61
ffffef05`2080d4e0 fffff804`55880379 : ffffd982`25220000 ffffef05`2080db80 00000000`00000000 00000000`00000001 : dxgkrnl!COREADAPTERACCESS::AcquireExclusive+0x2e
ffffef05`2080d520 fffff804`47fcde98 : ffffd982`2c270080 ffffd982`2c270080 00007ff8`3f709e50 00000000`776687f0 : dxgkrnl!DxgkEscape+0xb5729
ffffef05`2080db00 00007ff8`3f713734 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28 (TrapFrame @ ffffef05`2080db00)
00000000`0065e248 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`3f713734

     !lp ffffd982`2c27d080 Process
!PROCESS ffffd9822c27d080
    SessionId: 1  Cid: 1e78    Peb: 004c8000  ParentCid: 0584
    DirBase: 1375c7000  ObjectTable: ffffc30db6c54ac0  HandleCount: 288.
    Image: GPU-Z.exe

It's been unreliable in writing dump information. This happened after I stood up at my desk. Screen froze and pixelated. I have a new video card and MB/PS on the way because I figured one of those would be it. But then I finally got a dump to write.

 

[eidairaman1]

You having problems elsewhere?

 

[Jeff Stokes]

The gpu bios is on revision f2 and shows as most current with Gigabyte. It was working fine, I installed gpu-z, corsair wireless headphones utility and a few other apps around the time the crashes started

 

[eidairaman1]

Do a system restore before you installed all those apps, run gpu-Z.

 

[Jeff Stokes]

Graphics Card Manufacturer - Powered by AMD
Graphics Chipset - Radeon RX Vega
Device ID - 687F
Vendor ID - 1002
SubSystem ID - 2308
SubSystem Vendor ID - 1458
Revision ID - C1
Bus Type - PCI Express 3.0
Current Bus Settings - PCI Express 3.0 x16
BIOS Version - 016.001.001.000
BIOS Part Number - xxx-xxx-xxx
BIOS Date - 2018/01/10 04:52
High Bandwidth Cache Size - 8176 MB
High Bandwidth Cache Type - HBM2
High Bandwidth Cache Clock - 945 MHz
Core Clock - 1630 MHz
High Bandwidth Cache Bandwidth - 483 GByte/s
Memory Bit Rate - 1.89 Gbps
2D Driver File Path - /REGISTRY/MACHINE/SYSTEM/CurrentControlSet/Control/Class/{4d36e968-e325-11ce-bfc1-08002be10318}/0001
OpenGL® API Version - 4.6
OpenCL™ API Version - 2.0


I'm a bit embarrassed, I've forgotten who made the damn card.

Yeah if I'm going to look at system restore and add apps one at a time, I'll just rebuild when the new hardware shows up tomorrow.

The kernel dump I thought would be of interest to the developer.

Ah yeah, Gigabyte. https://www.newegg.com/Product/Product.aspx?Item=N82E16814932031

 

[W1zzard]

When does this happen? Any steps to repro?

 

[Jeff Stokes]

In the middle of Division 2 play, or one time I stood up at my desk and it did it, another I went to the kitchen to grab a drink, came back, it was dead

 

[the54thvoid]

Standing up is irrelevant to a software problem unless there's actually a loose connector (power, aux, etc) which might have been knocked if you hit the desk as you stood up. Worthwhile checking physical possibilities as well.

In fairness, I think the Corsair software is a prime suspect. Audio things, for whatever reasons, tend to be associated with numerous conflicts.

 

[Jeff Stokes]

I uninstalled CPU-Z, GPU-Z and the corsair headphone transceiver. No issues yet. I'll put gpu-z back on and see how tomorrow goes.

I mention standing up as an example purely to point out it's a random thing not prompted by input really.

Not meaning to be snarky, is what I meant

If you want a look at the dumps I have for this let me know.

I'll see how tomorrow goes without Corsair.

 

[Naki]

Standing up may mean loss of mouse/keyboard input, which is some kind of a difference/factor. Just saying!

 

[Jeff Stokes]

True true

 

[W1zzard]

I uninstalled CPU-Z, GPU-Z and the corsair headphone transceiver. No issues yet. I'll put gpu-z back on and see how tomorrow goes.

Any update on this?

 

[Jeff Stokes]

Yeah, I swapped gpu to the Radeon vii and problem went away. I think, the root of the dump analysis, after redoing it, shows that the Corsair gpu monitoring and Gpu-z monitoring were using the same method and conflicted, but could be wrong. But at root likely the Vega 64 had an issue, doing an RMA. Sorry for the false alarm

 

[John Naylor]

Well that does violate the rule of never having two apps monitoring the same thing at the same time.

 

[Jeff Stokes]

Well that does violate the rule of never having two apps monitoring the same thing at the same time.

I suppose. Post Windows 7, I can etw trace the same providers with multiple methods at once, but depends on the method used I guess.

 

[W1zzard]

Yeah, I swapped gpu to the Radeon vii and problem went away. I think, the root of the dump analysis, after redoing it, shows that the Corsair gpu monitoring and Gpu-z monitoring were using the same method and conflicted, but could be wrong. But at root likely the Vega 64 had an issue, doing an RMA. Sorry for the false alarm

So on RVII it works with both Corsair and GPU-Z running?

 

[Jeff Stokes]

Yeah, no issues. I think the card has an issue. After I posed this I had one of those weird lockups where the graphics output was all colored lines, etc.