Home → Geekbench →

GB4 and GB5 crash on Windows after splash screen; where can I find logs?

• Edit

Ivan V

13 Jan, 2023 05:56 PM

Hi,

I have a Windows-To-Go installation made with Rufus from a Windows 10 install. I've installed tryout Geekbench 5.4.6, then another build of 5.4.x, then a random build of 5.3.x. I've tried tryout Geekbench 4.x. I'm trying to run this same install on a Macbook Pro 2016, Mac Mini 2012 and Steam Deck. This has run only once. I believe I have tried Geekbench 5.4.6 on another install of Windows-To-Go Windows 10 as well.

I'm trying to compare different hardware's performance with an RX6900XT used as an eGPU on different operating systems, as well as comparing the built-in GPU performance. I'm, obviously, testing primarily for compute uses.

I've had Geekbench 5.4.6 run exactly once, and after some further tweaks to get the eGPU working more smoothly and predictably, Geekbench begun to crash on start. No version of Geekbench is running for me right now.

What's the best way to collect logs? Is there a chance it's trying to detect if it is, itself, already running on the machine, and accidentally conflicting with some other software that may have gotten installed when the hardware was plugged in (not just drivers, but also utility software -- Razer Synapse seems to be pulled in by Windows when Razer keyboard/mouse get plugged in, and AMD drivers refuse to start the installation as well)? I'd like to identify what's going on, but I haven't spotted a way to get logs when Geekbench is just starting up.

1. 1 Posted by Ivan V on 13 Jan, 2023 11:23 PM

   

   Nevermind, looks like an AMD bug. From the Windows event viewer (and this is not the only app that crashes):

   Faulting application name: Geekbench 5.exe, version: 0.0.0.0, time stamp: 0x601b727f
   Faulting module name: amdvlk64.dll, version: 31.0.12029.10015, time stamp: 0x6387a9d9
   Exception code: 0xc0000005
   Fault offset: 0x0000000000303c3e
   Faulting process id: 0x928
   Faulting application start time: 0x01d927a561cc3f77
   Faulting application path: C:\Program Files (x86)\Geekbench 5\Geekbench 5.exe
   Faulting module path: C:\Windows\System32\DriverStore\FileRepositoryΆ458.inf_amd64_e0283e9e7966f704\B386218\amdvlk64.dll
   Report Id: 8732e58d-7522-4fc6-81d0-9d32683ebfe0
   Faulting package full name:
   Faulting package-relative application ID:

   • Edit

2. 2 Posted by Ivan V on 13 Jan, 2023 11:27 PM

   

   (This is Geekbench 5.3.2. )

   ...but, on the other hand, it looks like disabling the laptop's built-in Radeon Pro 460 merely moves the breakage out of amdvlk64.dll:

   Faulting application name: Geekbench 5.exe, version: 0.0.0.0, time stamp: 0x601b727f
   Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
   Exception code: 0xc000041d
   Fault offset: 0x0000000000000000
   Faulting process id: 0x35bc
   Faulting application start time: 0x01d927a619c17a7e
   Faulting application path: C:\Program Files (x86)\Geekbench 5\Geekbench 5.exe
   Faulting module path: unknown
   Report Id: 55086e43-52dc-42e0-9878-4a307d405776
   Faulting package full name:
   Faulting package-relative application ID:

   And AMD driver installer doesn't crash anymore, now it simply stops seeing the (external) RX6900XT. :sigh:

   • Edit