• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.

2.9.0 causing BSOD (minidump analysis attached)

Forceflow

New Member
Joined
May 13, 2018
Messages
8 (0.12/day)
Likes
3
#1
Can't really pin down when it happens, but I've experienced some hard crashes using the latest GPU-Z and the latest Nvidia Drivers. I can usually trigger it by launching Vermintide 2 with GPU-Z open.

Here's the WinDBG analysis. I can provide minidump file if needed.

Code:
Microsoft (R) Windows Debugger Version 10.0.17134.1 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\jerba\Downloads\051318-6937-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 17134 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 17134.1.amd64fre.rs4_release.180410-1804
Machine Name:
Kernel base = 0xfffff801`77614000 PsLoadedModuleList = 0xfffff801`779d11d0
Debug session time: Sun May 13 16:39:02.591 2018 (UTC + 2:00)
System Uptime: 0 days 0:01:23.473
Loading Kernel Symbols
...............................................................
................................................................
........................................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, fffff80179f3de50, ffffc28235838fc0, fffff8017766e92f}

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+1fa953 )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: fffff80179f3de50
Arg3: ffffc28235838fc0
Arg4: fffff8017766e92f

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


KEY_VALUES_STRING: 1


TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  17134.1.amd64fre.rs4_release.180410-1804

SYSTEM_MANUFACTURER:  MSI

SYSTEM_PRODUCT_NAME:  MS-7A12

SYSTEM_SKU:  Default string

SYSTEM_VERSION:  1.0

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  1.90

BIOS_DATE:  01/25/2018

BASEBOARD_MANUFACTURER:  MSI

BASEBOARD_PRODUCT:  Z170A GAMING PRO CARBON (MS-7A12)

BASEBOARD_VERSION:  1.0

DUMP_TYPE:  2

BUGCHECK_P1: 8

BUGCHECK_P2: fffff80179f3de50

BUGCHECK_P3: ffffc28235838fc0

BUGCHECK_P4: fffff8017766e92f

BUGCHECK_STR:  0x7f_8

TRAP_FRAME:  fffff80179f3de50 -- (.trap 0xfffff80179f3de50)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffc28235839180 rbx=0000000000000000 rcx=ffffc28235839060
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8017766e92f rsp=ffffc28235838fc0 rbp=0000000000000000
 r8=0000000000000020  r9=0000000000000000 r10=0000000000000091
r11=ffffc282358390c8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!EtwWriteEx+0x4f:
fffff801`7766e92f e8cc111500      call    nt!memset (fffff801`777bfb00)
Resetting default scope

CPU_COUNT: 8

CPU_MHZ: fa8

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 5e

CPU_STEPPING: 3

CPU_MICROCODE: 6,5e,3,0 (F,M,S,R)  SIG: BE'00000000 (cache) BE'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXPNP: 1 (!blackboxpnp)


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  GPU-Z.2.9.0.exe

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  CORELLIA

ANALYSIS_SESSION_TIME:  05-13-2018 18:15:17.0940

ANALYSIS_VERSION: 10.0.17134.1 amd64fre

STACK_OVERFLOW: Stack Limit: ffffc28235839000. Use (kF) and (!stackusage) to investigate stack usage.

LAST_CONTROL_TRANSFER:  from fffff801777be829 to fffff801777ab670

STACK_TEXT: 
fffff801`79f3dd08 fffff801`777be829 : 00000000`0000007f 00000000`00000008 fffff801`79f3de50 ffffc282`35838fc0 : nt!KeBugCheckEx
fffff801`79f3dd10 fffff801`777b93ec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff801`79f3de50 fffff801`7766e92f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0x32c
ffffc282`35838fc0 fffff801`7766e8cc : 00000000`00000000 00000000`00000000 00000000`00000000 fffff801`7766e9bf : nt!EtwWriteEx+0x4f
ffffc282`358390d0 fffff80f`07e5a953 : 00000000`00000000 00000000`00000000 000000dc`04010401 00000000`207c0080 : nt!EtwWrite+0x2c
ffffc282`35839120 00000000`00000000 : 00000000`00000000 000000dc`04010401 00000000`207c0080 ffffc282`35839180 : nvlddmkm+0x1fa953


THREAD_SHA1_HASH_MOD_FUNC:  20e2fc4436fdad8b1b950799298da9a5844b9cba

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  600086b9554c4d7a7f3a703bf2dda5841bc916ae

THREAD_SHA1_HASH_MOD:  f2113cf119696bbdf4b93f6a6ccb797757579413

FOLLOWUP_IP:
nvlddmkm+1fa953
fffff80f`07e5a953 4883c438        add     rsp,38h

FAULT_INSTR_CODE:  38c48348

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  nvlddmkm+1fa953

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5af0a4c9

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  1fa953

FAILURE_BUCKET_ID:  0x7f_8_nvlddmkm!unknown_function

BUCKET_ID:  0x7f_8_nvlddmkm!unknown_function

PRIMARY_PROBLEM_CLASS:  0x7f_8_nvlddmkm!unknown_function

TARGET_TIME:  2018-05-13T14:39:02.000Z

OSBUILD:  17134

OSSERVICEPACK:  48

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  784

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE: 

USER_LCID:  0

OSBUILD_TIMESTAMP:  2018-04-28 05:58:00

BUILDDATESTAMP_STR:  180410-1804

BUILDLAB_STR:  rs4_release

BUILDOSVER_STR:  10.0.17134.1.amd64fre.rs4_release.180410-1804

ANALYSIS_SESSION_ELAPSED_TIME:  172b3

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x7f_8_nvlddmkm!unknown_function

FAILURE_ID_HASH:  {1e2b201d-3868-7883-c455-91a3ec283c76}

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: fffff80179f3de50
Arg3: ffffc28235838fc0
Arg4: fffff8017766e92f

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

W1zzard

Administrator
Staff member
Joined
May 14, 2004
Messages
17,855 (3.45/day)
Likes
19,421
Processor Core i7-4790K
Memory 16 GB
Video Card(s) GTX 1080
Display(s) 30" 2560x1600 + 19" 1280x1024
Software Windows 7
#2
That's a crash in the Nvidia driver. Is it repeatable? If yes maybe report to Nvidia, I'm sure they'd be interested in it, and their support does take things seriously
 

Forceflow

New Member
Joined
May 13, 2018
Messages
8 (0.12/day)
Likes
3
#3
That's a crash in the Nvidia driver. Is it repeatable? If yes maybe report to Nvidia, I'm sure they'd be interested in it, and their support does take things seriously
Having a hard time reproducing it. I've never had it without GPU-Z running, but that might just be luck (hence: probably not GPU-Z's fault, but I thought I'd report anyway). I've triggered it a second time, minidump showed same results.

After that, I've run Memtest86 (just to be sure it's nothing RAM-related), then I've DDU'ed and re-installed the latest Nvidia driver (which I was already running, anyway), and since then I've been unable to reproduce at all.

Edit: Just reproduced it again: reboot -> launch GPU-Z -> launch Vermintide 2 -> crash
Doing the same without launching GPU-Z = smooth sailing.
 
Last edited:
Joined
Aug 20, 2007
Messages
9,139 (2.29/day)
Likes
8,230
System Name Pioneer
Processor Intel i7 8700k @ 4.8 GHz All-Core + Uncore & AVX Offset @ 0
Motherboard ASRock Z370 Taichi
Cooling Noctua NH-U14S + A whole lotta Sunon and Corsair Maglev blower fans...
Memory G.SKILL TridentZ Series 32GB (4 x 8GB) DDR4-3200 @ 14-14-14-34-2T
Video Card(s) NVIDIA Titan XP Star Wars Collectors Edition (Galactic Empire)
Storage HGST UltraStar 7K6000 3.5" HDD 2TB 7200 RPM (w/128MBs of Cache)
Display(s) BenQ BL3200PT (a 1440p VA Panel with decent latency)
Case Thermaltake Core X31
Audio Device(s) Onboard Toslink to Schiit Modi Multibit to Asgard 2 Amp to AKG K7XX Ruby Red Massdrop Headphones
Power Supply Seasonic PRIME 750W 80Plus Titanium
Mouse ROCCAT Kone EMP
Keyboard WASD CODE 104-Key w/ Cherry MX Green Keyswitches, Doubleshot Vortex PBT White Keycaps, Blue legends
Software Windows 10 Enterprise (From former workplace, yay no telemetry)
Benchmark Scores FSExt/TS: FSExt 14625:https://www.3dmark.com/fs/15253894 TS 10496:https://www.3dmark.com/spy/3557134
#4
Having a hard time reproducing it. I've never had it without GPU-Z running, but that might just be luck (hence: probably not GPU-Z's fault, but I thought I'd report anyway). I've triggered it a second time, minidump showed same results.

After that, I've run Memtest86 (just to be sure it's nothing RAM-related), then I've DDU'ed and re-installed the latest Nvidia driver (which I was already running, anyway), and since then I've been unable to reproduce at all.

Just reproduced it again: reboot -> launch GPU-Z -> launch Vermintide 2 -> crash
Doing the same without launching GPU-Z = smooth sailing.
Sounds like a reproducible driver bug to me. Very interesting and report worthy...
 
Joined
Feb 18, 2005
Messages
1,497 (0.31/day)
Likes
799
Location
South Africa
System Name Firelance
Processor i7-3770K @ 4.6GHz / 1.23V
Motherboard Gigabyte Z77X-UD5H @ F16h mod BIOS
Cooling Corsair H105 + 4x Gentle Typhoon 1850
Memory 2x 8GB Crucial Ballistix Sport DDR3-1600 CL9 @ CL7
Video Card(s) MSI GTX 1070 Armor OC with Gaming X BIOS @ 2000 core / 2300 mem
Storage 2x 256GB 840 Pro (RAID-0) + 3TB Deskstar 7K3000 + 512GB BX300 + 8TB WD Purple
Display(s) Dell U2713HM (25x14) + Acer P243W (19x12)
Case Thermaltake Core X31
Audio Device(s) Corsair VOID Wireless
Power Supply Seasonic SS-760XP² Platinum
Mouse Logitech G400
Keyboard Logitech G19
Software Windows 7 Professional x64 Service Pack 1
#5
Double fault is generally a stack overflow IIRC. Subbing to see what comes of this, it would be pretty cool if you found a driver and/or GPU-Z bug!
 

Forceflow

New Member
Joined
May 13, 2018
Messages
8 (0.12/day)
Likes
3
#6
I've been doing the reboot + immediately launch game dance all day (like ... 20+ times), and the only way I can get it to reliably crash is when I launch GPU-Z first.

Here's a Dropbox folder with a bunch of minidumps to analyse: https://www.dropbox.com/sh/r60u7e5o49seeyl/AADfHOLnVIPngpiQPSp_ENrLa?dl=0

Note that it doesn't always lists GPU-Z as active process when it crashes, but it's always the nvidia driver sys, though.

I've mailed all of this to driverfeedback at nvidia.com, and reported it in the Driver Feedback Thread on the Geforce forums too.
 
Last edited:

Forceflow

New Member
Joined
May 13, 2018
Messages
8 (0.12/day)
Likes
3
#7
Just an update: I've swapped out the card (MSI GTX 1070TI Gaming X) I had for an identical one which arrived, reinstalled drivers.
Can still reproduce the issue, so I think we can rule out hardware failure or other shenanigans.

Minidumps here: https://www.dropbox.com/sh/r60u7e5o49seeyl/AADfHOLnVIPngpiQPSp_ENrLa?dl=0

Slight change: I'm triggering DPC_WATCHDOG_VIOLATION's too, although at a lesser rate than UNEXPECTED_KERNEL_TRAP's.

WinDBG is my friend nowadays, at least I'm learning :)
 

Forceflow

New Member
Joined
May 13, 2018
Messages
8 (0.12/day)
Likes
3
#9
Of course, IDA is my friend too :)

Yeah, those MS info pages are pretty generic info pages, thanks. Not really much I can do without debug symbols for the nvidia driver, and even then, it would probably be impenetrable for an outsider like me.

Again, I'd like to stress that this - as far as I can see - only reliably happens after a fresh boot + running GPU-Z + starting a game (I test with Vermintide 2) combo. It is rather specific, and otherwise my system is running fine, I've put in a couple hours of Far Cry 5, Fortnite and Battlefront 2 over the last few days without any problems.

Other things I've tried:
  • Triggering the issue with other "monitoring" tools: Afterburner, HwMon, ... cannot reproduce.
  • As said: swapping out the card for a fresh, identical model: same problem. The GPU itself is 100% fine.
  • Disabling G-Sync
I'll keep you guys posted, but for now I'm not gonna keep BSOD'ing my system on purpose :)
 
Joined
May 29, 2007
Messages
26 (0.01/day)
Likes
1
Processor P D920 model 6 step 2 rev b1 @ 3730
Motherboard asus p5wd2-e premium rev 1.xx i975x rev c0
Cooling zalman 9500cu-led thermalright hr-05
Memory kingston Hyperx pc6400 cl5 512 x2
Video Card(s) asus en8800gts 640mb stock
Storage 3x 250gb 1 sata / 2 sata2 raid 5 (466gb volume)
Display(s) lacie electron blue 22"
Case termaltake matrix vx
Audio Device(s) onboard alc 88x
Power Supply raidmax 650w
Software win2000 pro sp4 (untill vista x64 works)
#10
seems a bad ram chip.. too much 000000000000000000.
 
Joined
Feb 18, 2005
Messages
1,497 (0.31/day)
Likes
799
Location
South Africa
System Name Firelance
Processor i7-3770K @ 4.6GHz / 1.23V
Motherboard Gigabyte Z77X-UD5H @ F16h mod BIOS
Cooling Corsair H105 + 4x Gentle Typhoon 1850
Memory 2x 8GB Crucial Ballistix Sport DDR3-1600 CL9 @ CL7
Video Card(s) MSI GTX 1070 Armor OC with Gaming X BIOS @ 2000 core / 2300 mem
Storage 2x 256GB 840 Pro (RAID-0) + 3TB Deskstar 7K3000 + 512GB BX300 + 8TB WD Purple
Display(s) Dell U2713HM (25x14) + Acer P243W (19x12)
Case Thermaltake Core X31
Audio Device(s) Corsair VOID Wireless
Power Supply Seasonic SS-760XP² Platinum
Mouse Logitech G400
Keyboard Logitech G19
Software Windows 7 Professional x64 Service Pack 1
#11
Just an update: I've swapped out the card (MSI GTX 1070TI Gaming X) I had for an identical one which arrived, reinstalled drivers.
Can still reproduce the issue, so I think we can rule out hardware failure or other shenanigans.

Minidumps here: https://www.dropbox.com/sh/r60u7e5o49seeyl/AADfHOLnVIPngpiQPSp_ENrLa?dl=0

Slight change: I'm triggering DPC_WATCHDOG_VIOLATION's too, although at a lesser rate than UNEXPECTED_KERNEL_TRAP's.

WinDBG is my friend nowadays, at least I'm learning :)
I assume you're also a software developer? As it's pretty rare to come across an ordinary end user who knows what bugchecks are, never mind how to troubleshoot them. :)
 

Forceflow

New Member
Joined
May 13, 2018
Messages
8 (0.12/day)
Likes
3
#12
I assume you're also a software developer? As it's pretty rare to come across an ordinary end user who knows what bugchecks are, never mind how to troubleshoot them. :)
I'm an engineer / computer scientist, and write 3D rendering software. So yeah, I have some knowledge about debugging. If something breaks, I want to know why. Out of interest, and because it nags me :)

And @krull : That's ... not how it works :) Did a memtest86+, multiple passes, my RAM is fine.
 

joesik

New Member
Joined
Jun 16, 2018
Messages
20 (0.59/day)
Likes
6
#13
Hello! I've got the same problem, too. Even though here are no nvidia drivers installed on my PC, I still have the issue, like freezing especially in Steam.
I don't know exactly why GPU-Z works like that... With no GPU-Z, there are no freezes.
If you understand it, please let me know.
 

Forceflow

New Member
Joined
May 13, 2018
Messages
8 (0.12/day)
Likes
3
#14
Hello! I've got the same problem, too. Even though here are no nvidia drivers installed on my PC, I still have the issue, like freezing especially in Steam.
I don't know exactly why GPU-Z works like that... With no GPU-Z, there are no freezes.
If you understand it, please let me know.
AFAIK (and understand), the problem is that tools like GPU-Z call the Nvidia API in some way that is broken/bugged on the latest sets of Nvidia drivers. I haven't tried in a while, since BSOD'ing my PC on purpose isn't exactly my idea of a fun time. For now, I just avoid running tools like GPU-Z / other monitoring software for extended periods of time.
 
Joined
Apr 28, 2011
Messages
542 (0.21/day)
Likes
66
Location
Botevgrad, Bulgaria, Europe
System Name Main PC/OldPC/3rd PC
Processor Intel Core i7-3770K Ivy Bridge/Core i5-3470 Ivy Bridge/Core i3-4330 Haswell
Motherboard ASUS P8Z77-V/ASRock Z68 Pro3 Gen1/ASUS H81M2
Cooling Cooler Master Hyper 212 EVO
Memory 32GB Corsair Vengeance/32GB ADATA/16GB ADATA
Video Card(s) SAPPHIRE R9 290 Tri-X OC 4GB/MSI RX 480 8GB/SAPPHIRE R9 390 8GB
Storage 2xCorsair SSDs in RAID0+3 HDDs/2xIntel SSDs in RAID0+3 HDDs/Intel 480GB SSD+5+3TB HDDs
Display(s) Philips 274E5QHAB@HDMI + Philips 273EQH@DVI (both 27")
Case Fractal Design Define R4 Titanium
Audio Device(s) Kenwood Mini HiFi system/Microlab speakers/Philips HDMI (main)+LG TV monitor HDMI + Apple headphones
Power Supply Cooler Master Silent ProM 600 W (modular)
Mouse Microsoft Ergonomic Sculpt Desktop 2.0 (combo)@Razer Goliath mousepad (Medium speed)
Keyboard Microsoft Ergonomic Sculpt Desktop 2.0 (combo)
Software Windows 10 Pro 64-bit Ver.1709 Fall Creators Update (Build 17025.1000, Insider Preview)
#15
@Forceflow - please fill in your PC's specs.
Your BSOD issues may or may not be coming from GPU-Z/those other sysinfo apps you use.

What nVidia card do you use? Which Windows OS?
BSODs may possibly indicate a hardware or software issue on your PC (or not).
IF you have hardware issues, you should usually try to check for these with some CPU/GPU/RAM testing/benchmarking tools, and decide which component may be faulty according to the results of tests.
Software issues could be caused by lots of things, such as Windows Updates installed in recent weeks/months, GPU driver updates or even buggy and overzealous antivirus/etc.

RE BSODs not being fun, exactly same here! :) On my main PC, a BSOD leads (led? unsure) to major issues as there is some obscure Windows 10 startup hang/freeze issue due to my USB 3.0 disk(s) attached (on this PC only - I have several, the rest have no issues with startup).
(It is better now with less freezing, but with Windows 10, you never know...)
 
Last edited:
Joined
Apr 28, 2011
Messages
542 (0.21/day)
Likes
66
Location
Botevgrad, Bulgaria, Europe
System Name Main PC/OldPC/3rd PC
Processor Intel Core i7-3770K Ivy Bridge/Core i5-3470 Ivy Bridge/Core i3-4330 Haswell
Motherboard ASUS P8Z77-V/ASRock Z68 Pro3 Gen1/ASUS H81M2
Cooling Cooler Master Hyper 212 EVO
Memory 32GB Corsair Vengeance/32GB ADATA/16GB ADATA
Video Card(s) SAPPHIRE R9 290 Tri-X OC 4GB/MSI RX 480 8GB/SAPPHIRE R9 390 8GB
Storage 2xCorsair SSDs in RAID0+3 HDDs/2xIntel SSDs in RAID0+3 HDDs/Intel 480GB SSD+5+3TB HDDs
Display(s) Philips 274E5QHAB@HDMI + Philips 273EQH@DVI (both 27")
Case Fractal Design Define R4 Titanium
Audio Device(s) Kenwood Mini HiFi system/Microlab speakers/Philips HDMI (main)+LG TV monitor HDMI + Apple headphones
Power Supply Cooler Master Silent ProM 600 W (modular)
Mouse Microsoft Ergonomic Sculpt Desktop 2.0 (combo)@Razer Goliath mousepad (Medium speed)
Keyboard Microsoft Ergonomic Sculpt Desktop 2.0 (combo)
Software Windows 10 Pro 64-bit Ver.1709 Fall Creators Update (Build 17025.1000, Insider Preview)
#16
AFAIK (and understand), the problem is that tools like GPU-Z call the Nvidia API in some way that is broken/bugged on the latest sets of Nvidia drivers. I haven't tried in a while, since BSOD'ing my PC on purpose isn't exactly my idea of a fun time. For now, I just avoid running tools like GPU-Z / other monitoring software for extended periods of time.
Don't think so. Only a few users have come saying they have issues, thus this directly means hundreds or thousands of Nvidia users with no such problems. :)

Also, @W1zzard has not said GPU-Z has any issues with recent Nvidia drivers. If he knew there are, he would mention that.
 
Joined
May 13, 2018
Messages
8 (0.12/day)
Likes
3
#17
@Forceflow - please fill in your PC's specs.
Your BSOD issues may or may not be coming from GPU-Z/those other sysinfo apps you use.

What nVidia card do you use? Which Windows OS?
BSODs may possibly indicate a hardware or software issue on your PC (or not).
IF you have hardware issues, you should usually try to check for these with some CPU/GPU/RAM testing/benchmarking tools, and decide which component may be faulty according to the results of tests.
Software issues could be caused by lots of things, such as Windows Updates installed in recent weeks/months, GPU driver updates or even buggy and overzealous antivirus/etc.

RE BSODs not being fun, exactly same here! :) On my main PC, a BSOD leads (led? unsure) to major issues as there is some obscure Windows 10 startup hang/freeze issue due to my USB 3.0 disk(s) attached (on this PC only - I have several, the rest have no issues with startup).
(It is better now with less freezing, but with Windows 10, you never know...)
As you can read from my previous posts, I'm using a GTX 1070 TI on a Windows 10 system. I've already ran a plethora of system tests. Memcheck86 returned no errors, SFC /scannow returned no issues with my Windows install, which is pretty fresh to start with.
 
Joined
Apr 28, 2011
Messages
542 (0.21/day)
Likes
66
Location
Botevgrad, Bulgaria, Europe
System Name Main PC/OldPC/3rd PC
Processor Intel Core i7-3770K Ivy Bridge/Core i5-3470 Ivy Bridge/Core i3-4330 Haswell
Motherboard ASUS P8Z77-V/ASRock Z68 Pro3 Gen1/ASUS H81M2
Cooling Cooler Master Hyper 212 EVO
Memory 32GB Corsair Vengeance/32GB ADATA/16GB ADATA
Video Card(s) SAPPHIRE R9 290 Tri-X OC 4GB/MSI RX 480 8GB/SAPPHIRE R9 390 8GB
Storage 2xCorsair SSDs in RAID0+3 HDDs/2xIntel SSDs in RAID0+3 HDDs/Intel 480GB SSD+5+3TB HDDs
Display(s) Philips 274E5QHAB@HDMI + Philips 273EQH@DVI (both 27")
Case Fractal Design Define R4 Titanium
Audio Device(s) Kenwood Mini HiFi system/Microlab speakers/Philips HDMI (main)+LG TV monitor HDMI + Apple headphones
Power Supply Cooler Master Silent ProM 600 W (modular)
Mouse Microsoft Ergonomic Sculpt Desktop 2.0 (combo)@Razer Goliath mousepad (Medium speed)
Keyboard Microsoft Ergonomic Sculpt Desktop 2.0 (combo)
Software Windows 10 Pro 64-bit Ver.1709 Fall Creators Update (Build 17025.1000, Insider Preview)
#19
As you can read from my previous posts, I'm using a GTX 1070 TI on a Windows 10 system. I've already ran a plethora of system tests. Memcheck86 returned no errors, SFC /scannow returned no issues with my Windows install, which is pretty fresh to start with.
Please check your SSDs/HDDs health too.

Also, what "plethora" would that be, please?
Did you test with latest 3DMark, Unigine Valley, Unigine Superposition, Unigine Heaven?
If not, please try and carefully observe the tests, looking for any strange looking colors, shimmers, wrongly rendered parts of screen, big occasional slowdowns (decreases) in FPS/etc or maybe even a system crash (restart, BSOD) or freeze.
If you see none of those while testing, and there is no crash/freeze/restart, then this usually means the video card (GPU) is fine. :)
 
Top