BSoD while playing CS:GO - HWiNFO 5.58-3255

[KaleidonKep99]

My system crashed while I was playing CS:GO.
[img=544x408]https://cdn.discordapp.com/attachme...401943924342804/IMG_20171021_225707.jpg[/img]

BlueScreenView report:

I analyzed the dump file with Visual Studio, and it points out to HWiNFO64.EXE.
Here's its full log:

Spoiler

Windows 8 Kernel Version 16299 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 16299.15.amd64fre.rs3_release.170928-1534
Machine Name:
Kernel base = 0xfffff802`ca89e000 PsLoadedModuleList = 0xfffff802`cabfffd0
Debug session time: Sat Oct 21 16:56:22.602 2017 (UTC - 4:00)
System Uptime: 2 days 5:47:50.329
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff802256f8297, Address of the instruction which caused the bugcheck
Arg3: ffff948a47755480, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP:
nvlddmkm+2c8297
fffff802`256f8297 44885820        mov     byte ptr [rax+20h],r11b

CONTEXT:  ffff948a47755480 -- (.cxr 0xffff948a47755480)
rax=0000000000000000 rbx=ffff9d8158ffac38 rcx=ffff9d8158ffac40
rdx=ffff9d8158ffac90 rsi=ffff9d8158ffacb8 rdi=ffff9d8158ffac90
rip=fffff802256f8297 rsp=ffff948a47755e70 rbp=0000000000000001
r8=ffff9d8158ffac40  r9=ffff9d8158ffac90 r10=ffff9d8158ffac40
r11=0000000000000000 r12=00000000c1d001c0 r13=ffffc58386342000
r14=ffffc58389312020 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
nvlddmkm+0x2c8297:
fffff802`256f8297 44885820        mov     byte ptr [rax+20h],r11b ds:002b:00000000`00000020=??
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  HWiNFO64.EXE

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff802256f8297

STACK_TEXT:  
ffff948a`47755e70 00000000`00000000 : ffffc583`89312020 ffffc583`89313258 ffff948a`47755fc0 00000000`00000000 : nvlddmkm+0x2c8297


FOLLOWUP_IP:
nvlddmkm+2c8297
fffff802`256f8297 44885820        mov     byte ptr [rax+20h],r11b

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nvlddmkm+2c8297

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  59d76902

STACK_COMMAND:  .cxr 0xffff948a47755480 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_nvlddmkm+2c8297

BUCKET_ID:  X64_0x3B_nvlddmkm+2c8297

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

 

[Martin]

Which GPU do you have? I assume it's NVIDIA.

 

[KaleidonKep99]

Which GPU do you have? I assume it's NVIDIA.

It's a NVIDIA GeForce GTX 760 (4GB), yeah.

I'm using the ForceWare 387.92 drivers.

 

[Martin]

HWiNFO is using only NVIDIA-provided interfaces to access the GPU, so if this is causing the BSOD, then the problem must be somewhere in their drivers.
I see you're running the latest drivers, was this happening with earlier versions too ?

 

[KaleidonKep99]

HWiNFO is using only NVIDIA-provided interfaces to access the GPU, so if this is causing the BSOD, then the problem must be somewhere in their drivers.
I see you're running the latest drivers, was this happening with earlier versions too ?

Nope, I've never had this issue until now. I've been using the latest NVIDIA drivers (387.92) for quite some time, together with HWiNFO, this is the first time this happened.
Maybe it was just a random glitch in the driver, I'm not sure.

I'll keep an eye on my system, to see if it happens again.

 

[Martin]

Let me know if you see this again. It would also be great to catch the BSOD when HWiNFO is running in Debug Mode, but since this happens so rare, the debug file produced would be huge.