3DxWare 10.9.1 causing BSOD

Questions and answers about 3Dconnexion devices on Windows.

Moderator: Moderators

Post Reply
realelwood
Posts: 2
Joined: Mon Nov 04, 2024 4:19 am

3DxWare 10.9.1 causing BSOD

Post by realelwood »

Hi Team,

I ran into an issue where i got several BSOD per day a few weeks back. I had my IT department look at it. They discovered a "kernel error".

I got a new laptop and installed alla necessary software, 3DxWare being one of them. BSOD came back, by a lot of trial and error we have come to the conclusion that the culprit was the latest 3DxWare, I've been able to re-create and solve it by swapping between latest version and previous version.

Perhaps more reports will come in for this issue...

System info

OS Name Microsoft Windows 11 Enterprise
Version 10.0.22631 Build 22631
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name IM-GOT-D221527T
System Manufacturer HP
System Model HP ZBook Fury 15.6 inch G8 Mobile Workstation PC
System Type x64-based PC
System SKU 31Z44AV
Processor 11th Gen Intel(R) Core(TM) i7-11850H @ 2.50GHz, 2496 Mhz, 8 Core(s), 16 Logical Processor(s)
BIOS Version/Date HP T95 Ver. 01.18.00, 2024-08-27
SMBIOS Version 3.3
Embedded Controller Version 82.64
BIOS Mode UEFI
BaseBoard Manufacturer HP
BaseBoard Product 8870
BaseBoard Version KBC Version 52.40.00
ngomes
Moderator
Moderator
Posts: 3405
Joined: Mon Nov 27, 2006 7:22 am
Contact:

Re: 3DxWare 10.9.1 causing BSOD

Post by ngomes »

What is the module that triggers the BSOD? It will be shown on the BSOD panel.
Nuno Gomes
realelwood
Posts: 2
Joined: Mon Nov 04, 2024 4:19 am

Re: 3DxWare 10.9.1 causing BSOD

Post by realelwood »

This is the output from a reboot a while back.


==================================================
Dump File : 101524-21531-01.dmp
Crash Time : 2024-10-15 12:58:57
Bug Check String : BAD_POOL_CALLER
Bug Check Code : 0x000000c2
Parameter 1 : 00000000`0000000d
Parameter 2 : ffffc50f`a9cf94d0
Parameter 3 : 00000000`ffffc50f
Parameter 4 : de7cc08d`ae7a5f0d
Caused By Driver : WIN32KSGD.SYS
Caused By Address : WIN32KSGD.SYS+10e8
File Description : Win32k temporary session global driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.22621.3810 (WinBuild.160101.0800)
Processor : x64
Crash Address : ntoskrnl.exe+414df0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\101524-21531-01.dmp
Processors Count : 16
Major Version : 15
Minor Version : 22621
Dump File Size : 4 462 900
Dump File Time : 2024-10-15 13:00:02
==================================================

==================================================
Dump File : 101724-20937-01.dmp
Crash Time : 2024-10-17 08:17:31
Bug Check String : BAD_POOL_CALLER
Bug Check Code : 0x000000c2
Parameter 1 : 00000000`0000000d
Parameter 2 : ffffb987`90245880
Parameter 3 : 00000000`4870f6f6
Parameter 4 : af585ff3`a907fc61
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+414df0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.22621.4317 (WinBuild.160101.0800)
Processor : x64
Crash Address : ntoskrnl.exe+414df0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\101724-20937-01.dmp
Processors Count : 16
Major Version : 15
Minor Version : 22621
Dump File Size : 4 440 668
Dump File Time : 2024-10-17 08:19:07
==================================================
ngomes
Moderator
Moderator
Posts: 3405
Joined: Mon Nov 27, 2006 7:22 am
Contact:

Re: 3DxWare 10.9.1 causing BSOD

Post by ngomes »

Bugcheck 0xc2 (BAD_POOL_CALLER) on modules WIN32KSGD.SYS and ntoskrnl.exe. The modules are part of the operating system, not 3Dconnexion software.

Microsoft very unhelpfully recommends to revert to a previous configuration of the PC.

We do not have any other reports.
ngomes
Moderator
Moderator
Posts: 3405
Joined: Mon Nov 27, 2006 7:22 am
Contact:

Re: 3DxWare 10.9.1 causing BSOD

Post by ngomes »

You're using Windows 11 22H2.

We recommend updating to version 23H2 or, if available for your system, version 24H2 and see if the BSOD (bugcheck 0xc2) is still reproducible.
Post Reply