Overclock.net › Forums › Graphics Cards › NVIDIA › Can a GPU cause a BSOD?
New Posts  All Forums:Forum Nav:

Can a GPU cause a BSOD?

post #1 of 21
Thread Starter 
So i built new rig the end of last year, I previously had GTS 250 SLI setup that i brought over from my old build. I had the whole new build overclocked and stable @ 4.5 on a 2500k it was so sweet. I was actually shocked doing run after run of prime 95 and seeing no errors, no blue screens, no hiccups, truly a dream come true for me.

I came across some extra $$ after xmas and decided to upgrade to a MSI 560ti 448 core and scrap the 250s, a decent upgrade for me. However this is when the problems began to start. At the time the card was pretty new on the market, nvidia hadnt even released any drivers for it, I had to actually install the drivers off the CD (something Ive never had to do before). Maybe around the 8 hour mark after installing the new card and drivers is when I received the first BSOD. I looked up the code and it seemed, after doing research, that it was related to driver software and thats why I got the bug check.

Bascially to make a long story short even with the new nvidia drivers installed and doing over 10hours of memtest 86+ to make sure it wasnt my ram (i might go again for 12+ hours just to make 100% sure) im still getting a BSOD maybe twice a week, sometimes more, sometimes not at all and I cant pin point it down except for maybe its something with the GPU. Also, I undid the overclock and im back at stock, still got a BSOD.

Any insight?

Heres specs:

ASUS P8Z68-v Pro/gen3
Corsair Vengeance 8GB DDR3 1600
Corsair Force 3 120GB SSD
Corsair Carbide 500R White Case
XFX 850W Black Edition PSU
WD 1TB black caviar HDD
MSI GTX 560ti 448core
CM Hyper 212 EVO
post #2 of 21
Yes, a GPU or buggy video card drivers can and will cause BSODs.

Can you please navigate to C:/Windows/Minidump and zip / rar up your latest dump files? Once you've done that, please attach the zip / rar to your post by clicking the paperclip icon in the reply / post box.

If there are no files there, you may have it set to writing Kernel Memory Dumps rather than Small. If so, the DMP will be located in C:/Windows itself and named MEMORY.DMP.
post #3 of 21
Thread Starter 
minidump.zip 139k .zip file

please let me know if that worked, thanks for the speedy reply.
post #4 of 21
Hi smile.gif

Multiple different bugchecks, however all the probable causes are all core Microsoft files (likely never the actual causes as MS files are protected by the System File Checker), therefore this is a hardware related issue of a 3rd party driver that we're not seeing just yet.

*Before we begin, please return all overclocks to stock if you're overclocking as an unstable overclock can and WILL cause issues. You're more than welcome to continue overclocking after we solve your issues.

Drivers look okay, nothing really out of date or any high risk culprit drivers from what I can see.

First thing I want you to do is enable Driver Verifier so we can ensure this is or isn't driver related:
Quote:

Read the following
to enable Driver Verifier. Use Driver Second if Memtest finds nothing, as it's likely a software / driver issue, we just aren't being told what it is, and hopefully Driver Verifier will than force a crash if it finds the violating driver.

Before enabling Driver Verifier, my recommendation is to set a backup / restore point as in severe cases Driver Verifier can break your Windows. If you have difficulty getting into Windows, boot into Safe Mode and disable Driver Verifier there.

Dumps for reference:
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Icarus\Downloads\040312-13962-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`0321d000 PsLoadedModuleList = 0xfffff800`03461650
Debug session time: Tue Apr  3 12:42:16.488 2012 (UTC - 4:00)
System Uptime: 0 days 0:07:17.315
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {5100, fffff6fc80615040, 4c7, d4}

Probably caused by : win32k.sys ( win32k!AllocateObject+dd )

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000005100, The subtype of the bugcheck.
Arg2: fffff6fc80615040
Arg3: 00000000000004c7
Arg4: 00000000000000d4

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


BUGCHECK_STR:  0x1a_5100

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  spotify.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800032f2bc7 to fffff80003299d40

STACK_TEXT:  
fffff880`054269e8 fffff800`032f2bc7 : 00000000`0000001a 00000000`00005100 fffff6fc`80615040 00000000`000004c7 : nt!KeBugCheckEx
fffff880`054269f0 fffff800`032bbfa8 : 00000000`000004cf fffff880`05426b40 fffff900`c2a00000 00000000`00000600 : nt! ?? ::FNODOBFM::`string'+0xaf37
fffff880`05426b00 fffff800`033c4f86 : 00000000`004cf000 fffff880`02f03cc0 00000000`00000021 fffff880`054270d0 : nt!MiAllocatePagedPoolPages+0x4cc
fffff880`05426c20 fffff800`032b9cd0 : 00000000`004cf000 fffff880`02f03cc0 00000000`00000021 fffff800`032a2ef2 : nt!MiAllocatePoolPages+0x906
fffff880`05426d60 fffff800`033c790e : 00000000`00000000 fffff960`0011588e fffff880`00000020 00000000`004ce240 : nt!ExpAllocateBigPool+0xb0
fffff880`05426e50 fffff960`00103d49 : fffffa80`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExAllocatePoolWithTag+0x82e
fffff880`05426f40 fffff960`0010526c : fffff880`05427000 fffff880`054270e0 00000000`00000001 00000000`00000001 : win32k!AllocateObject+0xdd
fffff880`05426f80 fffff960`000dc420 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!SURFMEM::bCreateDIB+0x1f8
fffff880`05427070 fffff960`000dbf9a : 000003d8`00000500 00000000`000003d8 00000000`01080030 00000000`00000500 : win32k!hsurfCreateCompatibleSurface+0x3bc
fffff880`05427140 fffff800`03298fd3 : fffffa80`0a375b60 fffff880`054272a0 00000000`00000000 fffff900`c010d010 : win32k!GreCreateCompatibleBitmap+0x26e
fffff880`05427220 00000000`74fc2e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0008d3b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74fc2e09


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!AllocateObject+dd
fffff960`00103d49 488bd8          mov     rbx,rax

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  win32k!AllocateObject+dd

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4f2b63bd

FAILURE_BUCKET_ID:  X64_0x1a_5100_win32k!AllocateObject+dd

BUCKET_ID:  X64_0x1a_5100_win32k!AllocateObject+dd

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



Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Icarus\Downloads\040212-16926-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`03214000 PsLoadedModuleList = 0xfffff800`03458650
Debug session time: Mon Apr  2 13:27:38.769 2012 (UTC - 4:00)
System Uptime: 0 days 0:01:22.986
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, fffffa8004435470, ffff, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+355d4 )

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, The subtype of the bugcheck.
Arg2: fffffa8004435470
Arg3: 000000000000ffff
Arg4: 0000000000000000

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


BUGCHECK_STR:  0x1a_41790

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  WmiPrvSE.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800032ff610 to fffff80003290d40

STACK_TEXT:  
fffff880`095826e8 fffff800`032ff610 : 00000000`0000001a 00000000`00041790 fffffa80`04435470 00000000`0000ffff : nt!KeBugCheckEx
fffff880`095826f0 fffff800`032c3ae9 : fffff880`00000000 00000000`034d4fff fffffa80`00000000 fffff880`00000000 : nt! ?? ::FNODOBFM::`string'+0x355d4
fffff880`095828b0 fffff800`035a6f91 : fffffa80`07689890 00000000`00000000 fffffa80`09ce5a90 fffffa80`09ce5a90 : nt!MiRemoveMappedView+0xd9
fffff880`095829d0 fffff800`035a7393 : 0000007f`00000000 00000000`026e0000 fffffa80`00000001 00000000`00000001 : nt!MiUnmapViewOfSection+0x1b1
fffff880`09582a90 fffff800`0328ffd3 : 00000000`00000000 00000000`034b9898 fffffa80`0a48e7f0 00000000`00000000 : nt!NtUnmapViewOfSection+0x5f
fffff880`09582ae0 00000000`778515ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0123c278 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x778515ba


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+355d4
fffff800`032ff610 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+355d4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4ec79dd2

FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+355d4

BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+355d4

Followup: MachineOwner
---------
post #5 of 21
Thread Starter 
so i did the verifier.exe this morning and followed the on screen instructions, i have no overclock.

the PC BSOD'd like crazy, the error code was 0x000000C9

so it seems this is a driver related problem after all?
post #6 of 21
Please attach the driver verifier enabled BSODs. Disable Driver Verifier in safe mode if you cannot boot to Windows with it enabled.
post #7 of 21
Thread Starter 
i had to boot up in safe mode to disable it, where would the files be exactly, as im not 100% sure how to bring them up.
Edited by discoprince - 4/12/12 at 1:14pm
post #8 of 21
C:/Windows/Minidump and zip / rar up your latest dump files. Once you've done that, please attach the zip / rar to your post by clicking the paperclip icon in the reply / post box.

If there are no files there, you may have it set to writing Kernel Memory Dumps rather than Small. If so, the DMP will be located in C:/Windows itself and named MEMORY.DMP.
post #9 of 21
Thread Starter 
412.zip 18k .zip file

there is the latest file from the verifier
post #10 of 21
That's it, thanks smile.gif

Driver Verifier is pointing to the culprit SteelBus64.sys, which is the (from what I have read, GARBAGE driver) for the Steelseries Shift Keyboard. Please remove this driver or navigate to C:\Windows\System32\Drivers and find SteelBus64.sys. Rename .sys to .BAK and reboot the system - the driver will not load. This method will break whatever software uses this driver. Then you can uninstall that software.

Dump for reference:
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Icarus\Downloads\041212-16005-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0xfffff800`03208000 PsLoadedModuleList = 0xfffff800`0344c650
Debug session time: Thu Apr 12 11:30:47.498 2012 (UTC - 4:00)
System Uptime: 0 days 0:00:11.700
Loading Kernel Symbols
...............................................................
...........................................
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C9, {220, fffff880048a5350, fffff98004b72e10, fffffa80067aabb0}

Unable to load image \SystemRoot\system32\DRIVERS\SteelBus64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for SteelBus64.sys
*** ERROR: Module load completed but symbols could not be loaded for SteelBus64.sys
Probably caused by : SteelBus64.sys ( SteelBus64+7350 )

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

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

DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 0000000000000220, IRP_MJ_SYSTEM_CONTROL has been completed by someone other than the ProviderId.
        This IRP should either have been completed earlier or should have been passed
        down.
Arg2: fffff880048a5350, The address in the driver's code where the error was detected.
Arg3: fffff98004b72e10, IRP address.
Arg4: fffffa80067aabb0, ProviderId.

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


BUGCHECK_STR:  0xc9_220

DRIVER_VERIFIER_IO_VIOLATION_TYPE:  220

FAULTING_IP: 
SteelBus64+7350
fffff880`048a5350 4889542410      mov     qword ptr [rsp+10h],rdx

FOLLOWUP_IP: 
SteelBus64+7350
fffff880`048a5350 4889542410      mov     qword ptr [rsp+10h],rdx

IRP_ADDRESS:  fffff98004b72e10

DEVICE_OBJECT: fffffa80097dc190

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  System

CURRENT_IRQL:  2

LOCK_ADDRESS:  fffff80003482b60 -- (!locks fffff80003482b60)

Resource @ nt!PiEngineLock (0xfffff80003482b60)    Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE: 
        Lock address  : 0xfffff80003482b60
        Thread Count  : 0
        Thread address: 0x0000000000000000
        Thread wait   : 0x0

LAST_CONTROL_TRANSFER:  from fffff8000370d3dc to fffff80003284c80

STACK_TEXT:  
fffff880`037aeff8 fffff800`0370d3dc : 00000000`000000c9 00000000`00000220 fffff880`048a5350 fffff980`04b72e10 : nt!KeBugCheckEx
fffff880`037af000 fffff800`0371747a : fffff800`0370b9f0 fffff880`048a5350 fffff980`04b72e10 fffffa80`067aabb0 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`037af040 fffff800`037180ff : 00000000`00000220 fffffa80`067aabb0 fffff980`04b72e10 00000000`ffffffff : nt!ViErrorFinishReport+0xda
fffff880`037af090 fffff800`0371d6a7 : fffff980`04b72f70 fffff880`048a5350 00000000`0411d777 fffffa80`0943c000 : nt!VfErrorReport10+0x6f
fffff880`037af170 fffff800`0370d04e : fffffa80`08f99788 00000000`00000000 00000000`00000000 00000000`00000000 : nt!VfWmiVerifyIrpStackUpward+0x67
fffff880`037af1a0 fffff800`03719b2d : fffffa80`09616d60 fffffa80`08f995d0 fffff980`04b72e10 fffff980`04b72e10 : nt!VfMajorVerifyIrpStackUpward+0x6e
fffff880`037af1e0 fffff800`0372b50d : fffff980`04b72f70 fffff880`037af3d0 00000000`00000000 fffff980`04b72f70 : nt!IovpCompleteRequest2+0xad
fffff880`037af250 fffff800`032886c1 : fffff980`04b72f73 00000000`00000000 00000000`000000ff fffff800`03340e23 : nt!IovpLocalCompletionRoutine+0x9d
fffff880`037af2b0 fffff800`0372319f : fffff980`04b72e10 00000000`00000000 fffffa80`0919b000 00000000`00000000 : nt!IopfCompleteRequest+0x341
fffff880`037af3a0 fffff880`048a54a7 : fffff980`04b72e10 fffff800`03728c42 fffff980`04b72e10 fffffa80`0919b040 : nt!IovCompleteRequest+0x19f
fffff880`037af470 fffff980`04b72e10 : fffff800`03728c42 fffff980`04b72e10 fffffa80`0919b040 fffff980`04b72f70 : SteelBus64+0x74a7
fffff880`037af478 fffff800`03728c42 : fffff980`04b72e10 fffffa80`0919b040 fffff980`04b72f70 00000000`00000000 : 0xfffff980`04b72e10
fffff880`037af480 fffffa80`097f7cb0 : fffffa80`0919b040 fffff800`03729c16 fffffa80`0919b040 fffff980`04b72e10 : nt!ViFilterDispatchPower+0x62
fffff880`037af4b0 fffffa80`0919b040 : fffff800`03729c16 fffffa80`0919b040 fffff980`04b72e10 fffff980`04b72e10 : 0xfffffa80`097f7cb0
fffff880`037af4b8 fffff800`03729c16 : fffffa80`0919b040 fffff980`04b72e10 fffff980`04b72e10 fffff800`0372537e : 0xfffffa80`0919b040
fffff880`037af4c0 fffff800`03728c42 : fffff980`04b72f70 00000000`00000002 fffffa80`097dc2e0 fffffa80`097f7cb0 : nt!IovCallDriver+0x566
fffff880`037af520 fffff800`03729c16 : fffff980`04b72e10 00000000`00000002 fffffa80`097dc190 00000000`00000000 : nt!ViFilterDispatchPower+0x62
fffff880`037af550 fffff800`03728d58 : fffff980`04b72e10 fffffa80`097dc190 00000000`00000000 fffffa80`097f7750 : nt!IovCallDriver+0x566
fffff880`037af5b0 fffff800`03728e42 : fffffa80`067aabb0 00000000`00000001 fffffa80`067aabb0 00000000`00000017 : nt!VfIrpSendSynchronousIrp+0xe8
fffff880`037af620 fffff800`03715faf : fffffa80`067aa8e0 00000000`000007ff fffff800`033bd5b8 fffff800`03619a29 : nt!VfWmiTestStartedPdoStack+0x72
fffff880`037af6c0 fffff800`03330d82 : fffffa80`067aa8e0 00000000`00000000 ffffffff`ffffffff 00000000`00000016 : nt!VfMajorTestStartedPdoStack+0x5f
fffff880`037af6f0 fffff800`0366dfec : fffffa80`067aa8e0 00000000`00000001 00000000`00000000 00000000`00000002 : nt!PpvUtilTestStartedPdoStack+0x12
fffff880`037af720 fffff800`0366fbe4 : fffffa80`067aa8e0 fffffa80`067aa8e0 fffffa80`06753d90 00000000`00000001 : nt!PipProcessStartPhase3+0x55c
fffff880`037af810 fffff800`036700cc : fffff800`03480400 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PipProcessDevNodeTree+0x264
fffff880`037afa80 fffff800`03380ee2 : 00000001`00000003 00000000`00000000 00000000`32706e50 00000000`00000084 : nt!PiProcessStartSystemDevices+0x7c
fffff880`037afad0 fffff800`0328e361 : fffff800`03380be0 fffff800`0357a701 fffffa80`06735600 fffffa80`0000055a : nt!PnpDeviceActionWorker+0x302
fffff880`037afb70 fffff800`0351efda : 00000000`00000000 fffffa80`06735680 00000000`00000080 fffffa80`06699890 : nt!ExpWorkerThread+0x111
fffff880`037afc00 fffff800`032759c6 : fffff880`03565180 fffffa80`06735680 fffff880`0356ffc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`037afc40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

SYMBOL_NAME:  SteelBus64+7350

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: SteelBus64

IMAGE_NAME:  SteelBus64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4e739cd1

FAILURE_BUCKET_ID:  X64_0xc9_220_VRF_SteelBus64+7350

BUCKET_ID:  X64_0xc9_220_VRF_SteelBus64+7350

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

New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: NVIDIA
Overclock.net › Forums › Graphics Cards › NVIDIA › Can a GPU cause a BSOD?