BSOD after gaming with AIDA64 SensorPanel running (Asus GTX560TI + ForceWare 391.35)

[rick11]

Hi, in the last weeks I got irregularely 4 BSOD´s (WHEA 124) about 30s after I closed a game, in idle, while running the AIDA64 Sensor Panel or immeadetely starting it after playing.

AIDA64 (5.98.4800)
Windows 10 pro 64 (1809)
MB ASUS Z370-F (1412)
CPU 8700K
GPU ASUS GTX560TI with latest Driver (391.35)

All BSOD reports had in common, that they showed up the aida64.exe process.
Could this be a GPU driver related Bug, as I read about in formar posts, or might this have other reasons?
Is there anything I can do about it, to avoid crashing?

Best regards
Rick


 

[Fiery]

19 hours ago, rick11 said:

Hi, in the last weeks I got irregularely 4 BSOD´s (WHEA 124) about 30s after I closed a game, in idle, while running the AIDA64 Sensor Panel or immeadetely starting it after playing.

AIDA64 (5.98.4800)
Windows 10 pro 64 (1809)
MB ASUS Z370-F (1412)
CPU 8700K
GPU ASUS GTX560TI with latest Driver (391.35)

All BSOD reports had in common, that they showed up the aida64.exe process.
Could this be a GPU driver related Bug, as I read about in formar posts, or might this have other reasons?
Is there anything I can do about it, to avoid crashing?

Best regards
Rick

There's a known issue with ForceWare 390 Series drivers that causes such major problems like BSoD.  But since your video card is no longer supported, the only solution might be to downgrade your drivers to one that still works properly.  Once you upgrade your video cards to one that is supported by ForceWare 400 Series drivers, the problem will be gone.

[rick11]

OK. Thank you for your fast response and have a nice weekend!

[rick11]

Hi Fiery,
now I have a  new GTX1070 with actual driver built 430.86 and still I got the same issue after quitting a game...

AIDA64 (6.00.5100)
Windows 10 pro 64 (1809)
MB ASUS Z370-F (1412)
CPU 8700K
GPU ASUS GTX1070 Strix with latest Driver (430.86)

Best regards
Rick

[rick11]

Maybe I was wrong and it´s somehow different now.
It seems that the problem only exists after playing with nVidia 4x Downsampling, not in general...