Grey Screen Crash (Nvidia Driver Issue)

[DJESMOND]

Hi Guys.

So my adventure has been going on for quite a while at this point.
So lets get started here
 
The specs
Note: The PC was built back in November 2014

• Intel Core i5 4690k - Running stock at 3.5 GHz and cooled with a Corsair H100i
• ​MSI Gaming 7 Z97 Motherboard 
• 16 Gbs Corsair Vengeance Ram (2x 8 gb sticks) - running at 1866 Mhz
• ASUS Poseidon 780 3gb - Running at stock
• Corsair RM1000 PSU
• Samsung 840 Evo 240gb SSD
• WD Black 1tb HDD
• OS: Windows PRO(64-bit) 7/8.1/10, Mac OSX El Capitan

​The beginning
​So way back in September i experienced my first crash, grey screen.
This happened when playing CSGO on Windows (Don't remember if i had 8.1 or 10 at the time)
At first i didn't really make much of it. After all..... things crash from time to time.
I booted back up with no errors. Windows didn't even seem to detect that the crash happend.
So... I booted up CSGO again..... Crash.... reboot.... crash..... reboot.... crash..... You get the idea.
So i went to bed. Next day i wanted to fix it. So i started out by grapping the newest driver at the time (Around 34X.X i think)
After during a clean install i booted up CSGO. No issues.... for a while.... A few hours in.... Crash.... reboot.... repeat...
So next day i tried again..... Launch ARK..... crash.....
 
Alright so skipping ahead a bit.... My PC has been crashing randomly ever since. It no longer just happens in games.... but also at desktop....
Now it happens randomly.... I never know when.... Which makes my PC pretty useless. (I've settled with Fallout 4 for this time, since i didn't want
to ruin peoples games online). 
 
Here is a list of the thinks i have done

• ​Clean install driver with the Nvidia installer (No GFE)
• Safe boot into Windows and Removed drivers then installed new ones again.
• Installing both older and newer(beta) drivers.
• RMA GPU (They ran stress tests for 10 hours, no issues)
• Running a 10 hour full on stress test (CPU and GPU), no crashing.... nothing.
• Format and clean install Windows 10. (Done 4 times (yes 4)).
• Format and clean install Windows 8.1 
• Format and clean install Windows 7
• Format and clean install Mac OSX El Capitan
• BIOS Update
• Memtest
• Under clocking VRAM - no change

New things tried from comments

• Running GPU in PCIe x8 slot 
• Running with new cables from PSU
• Running from new output from PSU
• Swapping display cables (both DVI and HDMI)
• Running 1 monitor
• Stresstest in OSX (Furmark)
• Diskwarrior on both drives (All OK)
• Running on CPU graphics (No crash during testing period)

The theories i have had
Grey screen tends to be the GPU driver crashing, which is what happens.
A few times Windows have recovered and displayed that the Windows Kernal Driver crashed.
The crash has nothing to do with load, nor temps. It seems to just happen randomly... Some days i 
can use it for hours on hours.... some days i just can't.... It even crashed during a driver install on fresh windows install.
 
Now sometimes it boots to a black screen..... then reboots a few times until it reaches the OS.
 
After a while i concluded that Windows 10 most have been the issue. (The automatic windows updates includes a driver)
Some people had reported issues with this. So i defered from the updates. And forced a clean install of the newest Nvidia driver upon log in.
It worked for some time..... then it when back to crap.
 
After getting really annoyed by Windows i decided to install Mac OSX (as a Hackintosh) since i have a MacBook Pro i have a bit of experience with it.
So after installed OSX i started using the machine. Behold the crashing off the machine yet again... (This is where the images and video are from).
I don't have any screenshots from windows since i never was able to tell when it happened. 
But here is the interesting part. I was able to get the crash report from the Mac when i booted again.

 

Anonymous UUID: 43B6034D-F20D-F73A-9775-2B856D7FB145

Wed Jan 6 04:06:26 2016

*** Panic Report ***
panic(cpu 0 caller 0xffffff7f909b9165): NVRM[0/1:0:0]: Read Error 0x00000144: CFG 0x100410de 0x00100407 0xf6000000, BAR0 0xf6000000 0xffffff9200028000 0x0f1040a1, D0, P3/4
Backtrace (CPU 0), Frame : Return Address
0xffffff81d313bc70 : 0xffffff800fcde792
0xffffff81d313bcf0 : 0xffffff7f909b9165
0xffffff81d313bdb0 : 0xffffff7f90a86e64
0xffffff81d313bdf0 : 0xffffff7f90cbc48a
0xffffff81d313be10 : 0xffffff7f909bfc27
0xffffff81d313bec0 : 0xffffff7f9096dac5
0xffffff81d313bee0 : 0xffffff80102b9d75
0xffffff81d313bf10 : 0xffffff7f90548116
0xffffff81d313bf50 : 0xffffff7f9212b2be
0xffffff81d313bf60 : 0xffffff7f92133449
0xffffff81d313bf80 : 0xffffff800fdd08ec
0xffffff81d313bfd0 : 0xffffff800fdef3f9
0xffffff91fe79bf40 : 0xffffff800fcf5cfd
0xffffff91fe79bf90 : 0xffffff800fcf61f0
0xffffff91fe79bfb0 : 0xffffff800fdcbf77
Kernel Extensions in backtrace:
com.apple.iokit.IOPCIFamily(2.9)[6ADFE830-2986-35D2-8C2F-6ABEDBC94F6A]@0xffffff7f9052c000->0xffffff7f9055bfff
com.apple.driver.AppleACPIPlatform(4.0)[295F7A91-2DF7-3FFE-9550-A0C1A6F9D575]@0xffffff7f92124000->0xffffff7f92183fff
dependency: com.apple.iokit.IOACPIFamily(1.4)[CBAE26D8-0ACB-3C1F-8347-FDCA67EC40B3]@0xffffff7f90607000
dependency: com.apple.iokit.IOPCIFamily(2.9)[6ADFE830-2986-35D2-8C2F-6ABEDBC94F6A]@0xffffff7f9052c000
com.apple.nvidia.driver.NVDAResman(10.0.8)[57B619C4-A94E-341E-A276-5C4F83341C49]@0xffffff7f90967000->0xffffff7f90be0fff
dependency: com.apple.iokit.IOPCIFamily(2.9)[6ADFE830-2986-35D2-8C2F-6ABEDBC94F6A]@0xffffff7f9052c000
dependency: com.apple.iokit.IONDRVSupport(2.4.1)[814A7F4B-03EF-384A-B205-9840F0594421]@0xffffff7f90950000
dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[48AC8EA9-BD3C-3FDC-908D-09850215AA32]@0xffffff7f90909000
dependency: com.apple.AppleGraphicsDeviceControl(3.12.6)[F211EB28-182A-34BB-A610-87667618F925]@0xffffff7f90960000
com.apple.nvidia.driver.NVDAGK100Hal(10.0.8)[EB8A5980-AB59-368A-8244-60A00C7A933C]@0xffffff7f90bec000->0xffffff7f90d9afff
dependency: com.apple.nvidia.driver.NVDAResman(10.0.8)[57B619C4-A94E-341E-A276-5C4F83341C49]@0xffffff7f90967000
dependency: com.apple.iokit.IOPCIFamily(2.9)[6ADFE830-2986-35D2-8C2F-6ABEDBC94F6A]@0xffffff7f9052c000

BSD process name corresponding to current thread: kernel_task
Boot args: dart=0

Mac OS version:
15C50

Kernel version:
Darwin Kernel Version 15.2.0: Fri Nov 13 19:56:56 PST 2015; root:xnu-3248.20.55~2/RELEASE_X86_64
Kernel UUID: 17EA3101-D2E4-31BF-BDA9-931F51049F93
Kernel slide: 0x000000000fa00000
Kernel text base: 0xffffff800fc00000
__HIB text base: 0xffffff800fb00000
System model name: iMac14,2 (Mac-27ADBB7B4CEE8E61)

System uptime in nanoseconds: 81069934348
last loaded kext at 28563781264: com.apple.driver.AudioAUUC 1.70 (addr 0xffffff7f919d8000, size 32768)
loaded kexts:
com.insanelymac.AtherosE2200Ethernet 2.0.1
org.netkas.driver.FakeSMC 1394
com.apple.driver.AudioAUUC 1.70
com.apple.driver.AppleGraphicsDevicePolicy 3.7.7
com.apple.filesystems.exfat 1.4
com.apple.driver.AppleTyMCEDriver 1.0.2d2
com.apple.filesystems.autofs 3.0
com.apple.iokit.IOBluetoothSerialManager 4.4.3f4
com.apple.driver.AppleHDAHardwareConfigDriver 272.51.3
com.apple.driver.AppleHDA 272.51.3
com.apple.driver.AppleUpstreamUserClient 3.6.1
com.apple.driver.AppleMCCSControl 1.2.13
com.apple.GeForce 10.0.8
com.apple.driver.AppleOSXWatchdog 1
com.apple.driver.pmtelemetry 1
com.apple.iokit.IOUserEthernet 1.0.1
com.apple.driver.AppleFIVRDriver 4.1.0
com.apple.driver.Apple16X50ACPI 3.2
com.apple.Dont_Steal_Mac_OS_X 7.0.0
com.apple.driver.AppleHV 1
com.apple.driver.AppleIntelSlowAdaptiveClocking 4.0.0
com.apple.driver.ACPI_SMC_PlatformPlugin 1.0.0
com.apple.nvidia.NVDAStartup 10.0.8
com.apple.driver.AppleFileSystemDriver 3.0.1
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0
com.apple.BootCache 38
com.apple.iokit.IOAHCIBlockStorage 2.8.5
com.apple.driver.AppleAHCIPort 3.1.8
com.apple.driver.usb.AppleUSBEHCIPCI 1.0.1
com.apple.driver.AppleACPIButtons 4.0
com.apple.driver.AppleRTC 2.0
com.apple.driver.AppleHPET 1.8
com.apple.driver.AppleSMBIOS 2.1
com.apple.driver.AppleAPIC 1.7
com.apple.nke.applicationfirewall 163
com.apple.security.quarantine 3
com.apple.security.TMSafetyNet 8
com.apple.driver.AppleGraphicsControl 3.12.6
com.apple.kext.triggers 1.0
com.apple.driver.DspFuncLib 272.51.3
com.apple.kext.OSvKernDSPLib 525
com.apple.driver.AppleSMBusController 1.0.14d1
com.apple.iokit.IOSMBusFamily 1.1
com.apple.nvidia.driver.NVDAGK100Hal 10.0.8
com.apple.iokit.IOAcceleratorFamily2 203.14
com.apple.nvidia.driver.NVDAResman 10.0.8
com.apple.AppleGraphicsDeviceControl 3.12.6
com.apple.driver.AppleSMBusPCI 1.0.14d1
com.apple.iokit.IONDRVSupport 2.4.1
com.apple.driver.AppleHDAController 272.51.3
com.apple.iokit.IOHDAFamily 272.51.3
com.apple.iokit.IOAudioFamily 204.3
com.apple.vecLib.kext 1.2.0
com.apple.driver.Apple16X50Serial 3.2
com.apple.iokit.IOSerialFamily 11
com.apple.iokit.IOSurface 108.0.1
com.apple.iokit.IOGraphicsFamily 2.4.1
com.apple.iokit.IOBluetoothFamily 4.4.3f4
com.apple.driver.CoreCaptureResponder 1
com.apple.driver.corecapture 1.0.4
com.apple.iokit.IOSlowAdaptiveClockingFamily 1.0.0
com.apple.driver.AppleSMC 3.1.9
com.apple.driver.IOPlatformPluginLegacy 1.0.0
com.apple.driver.IOPlatformPluginFamily 6.0.0d7
com.apple.iokit.IOSCSIArchitectureModelFamily 3.7.7
com.apple.driver.usb.IOUSBHostHIDDevice 1.0.1
com.apple.driver.usb.AppleUSBHostCompositeDevice 1.0.1
com.apple.driver.usb.AppleUSBHub 1.0.1
com.apple.driver.AppleXsanScheme 3
com.apple.driver.AppleUSBMergeNub 900.4.1
com.apple.iokit.IONetworkingFamily 3.2
com.apple.iokit.IOAHCIFamily 2.8.1
com.apple.driver.usb.AppleUSBEHCI 1.0.1
com.apple.driver.usb.AppleUSBXHCIPCI 1.0.1
com.apple.driver.usb.AppleUSBXHCI 1.0.1
com.apple.iokit.IOUSBFamily 900.4.1
com.apple.iokit.IOUSBHostFamily 1.0.1
com.apple.driver.AppleUSBHostMergeProperties 1.0.1
com.apple.driver.AppleEFINVRAM 2.0
com.apple.driver.AppleEFIRuntime 2.0
com.apple.iokit.IOHIDFamily 2.0.0
com.apple.security.sandbox 300.0
com.apple.kext.AppleMatch 1.0.0d1
com.apple.driver.AppleKeyStore 2
com.apple.driver.AppleMobileFileIntegrity 1.0.5
com.apple.driver.AppleCredentialManager 1.0
com.apple.driver.DiskImages 417.1
com.apple.iokit.IOStorageFamily 2.1
com.apple.iokit.IOReportFamily 31
com.apple.driver.AppleFDEKeyStore 28.30
com.apple.driver.AppleACPIPlatform 4.0
com.apple.iokit.IOPCIFamily 2.9
com.apple.iokit.IOACPIFamily 1.4
com.apple.kec.Libm 1
com.apple.kec.pthread 1
com.apple.kec.corecrypto 1.0
Model: iMac14,2, BootROM IM142.0118.B12, 4 processors, Intel Core i5, 3,5 GHz, 16 GB, SMC 2.15f2
Graphics: Intel HD Graphics 4600, Intel HD Graphics 4600, Built-In
Memory Module: BANK0/DIMM1, 8 GB, DDR3, 1333 MHz, Corsair, CMY16GX3M2A1866C9
Memory Module: BANK1/DIMM1, 8 GB, DDR3, 1333 MHz, Corsair, CMY16GX3M2A1866C9
Network Service: Ethernet, Ethernet, en0
Serial ATA Device: Samsung SSD 840 EVO 250GB, 250,06 GB
Serial ATA Device: WDC WD1003FZEX-00MK2A0, 1 TB
USB Device: USB 2.0 Bus
USB Device: Hub
USB Device: USB 2.0 Bus
USB Device: Hub
USB Device: USB 3.0 Bus
USB Device: Razer BlackWidow Ultimate
USB Device: USB 3.0 Bus
USB Device: Integrated USB Bridge
USB Device: ASM107x
USB Device: Razer Orbweaver
USB Device: Gaming Mouse G502
Thunderbolt Bus:

 

And as you can tell its the Nvidia driver crashing. But unlike on Windows it didn't happen instantly. The screen started blinked and after a while the pc grey screen then rebooted. (See video (SPOILER ALERT ON GOTHAM SERIES )).

Shortly after the video the pc crashes. 

 

So what now.

Well.... I'm currently running the machine without the GPU as I'm writing this post (Still no crash):

Im really out of ideas as of what could be wrong.... 

Well i know that its the driver.... but i just doesn't make any sense....

It happens on all OS, even without the same driver.

So.... is it the GPU? and if so..... how can you RMA a GPU that only crashes sometimes.....

My idea is that it might be something between the CPU and GPU that gets messed up, but i dunno.

 

So guys any tips?

Btw: I currently have my dad fetching my old pc's GPU. An old ATI GPU. I will test with that to see it happens to that too if its just Nvidia....

 

I am open to ideas

 

Current status;

ATI card arrived. Not tested yet. Formated and installed Win 10 on SSD. No crashes since. (I have done nothing different this time). I will Keep it running to see if it will crash again. I can play games as well as stress test. Win 10 updates does require me to reinstall nvidia driver on boot everytime. 

 

Back to crashing. Now even after reinstalling the driver. I swapped the card with the ATI card (Radeon HD 5770). No crashing. Swapped back.... Nvidia crashes on game launch and dual monitor desktop. 

[manofsteel]

Okay first you can check by stress test CPU that it is not it or does nothing happen, second check the AIO if it does not leak and the leak didint damage CPU (i dont know how you instaled rad so that thing could happen) next stress test GPU if it crashes automaticly than rma gpu

[Elapo]

OH boy, I feel you. I had my PC restart because of nvidia drivers a while back.

 

Now, i only had these random shut downs on W10, not on every windows version, drivers really leave something to be desired on W10, but since it's happened on every windows version from the last 7-something years AND on OSX, I'm inclined to believe this might be a hardware issue.

 

Sure, it's GPU drivers crashing, but those drivers don't like things not going perfectly for the GPU

 

I'd test:

 

- Another PCIe slot, if you haven't already (you didn't list it)

- Another PSU, if you can (or other PCIe connectors)

- A BIOS update (if available)

- A memtest (really, you never know)

 

You can be fairly certain it's not the GPU, and it's not the software (seeing you tried so many combinations), So I'd start testing things related to the GPU.

 

EDIT: I forgot to mention, but do you mayhaps still have some event viewer logs or minidumps from any of the windows installations? I don't know anything about OSX, so I don't know anything about that crash log

 

Okay first you can check by stress test CPU that it is not it or does nothing happen, second check the AIO if it does not leak and the leak didint damage CPU (i dont know how you instaled rad so that thing could happen) next stress test GPU if it crashes automaticly than rma gpu

 

He already RMA'd it, they found nothing wrong with the GPU.

[DJESMOND]

Okay first you can check by stress test CPU that it is not it or does nothing happen, second check the AIO if it does not leak and the leak didint damage CPU (i dont know how you instaled rad so that thing could happen) next stress test GPU if it crashes automaticly than rma gpu

 

I have run both GPU and CPU stress test myself. one at a time and both together. The PC didnt crash. All temps are below 80 Celsius under stress test and around 40 Celcius on idle. In game the temps are between 50 and 60 depending on the game.

I've just checked the Rad. It is not leaking.

[DJESMOND]

OH boy, I feel you. I had my PC restart because of nvidia drivers a while back.

 

Now, i only had these random shut downs on W10, not on every windows version, drivers really leave something to be desired on W10, but since it's happened on every windows version from the last 7-something years AND on OSX, I'm inclined to believe this might be a hardware issue.

 

Sure, it's GPU drivers crashing, but those drivers don't like things not going perfectly for the GPU

 

I'd test:

 

- Another PCIe slot, if you haven't already (you didn't list it)

- Another PSU, if you can (or other PCIe connectors)

- A BIOS update (if available)

- A memtest (really, you never know)

 

You can be fairly certain it's not the GPU, and it's not the software (seeing you tried so many combinations), So I'd start testing things related to the GPU.

 

 

 

He already RMA'd it, they found nothing wrong with the GPU.

My motherboard only has one PCiE x16 slot. the others are x8. Don't know if that makes a difference? 

I don't have a PSU laying around, so that is hard to test. I might try and swap the cables (since its modular)

I updated the BIOS back in September, because.... you never know. It didn't change anything. 

i ran a memtest way back. Sorry for not including. But i can run one again

[manofsteel]

My motherboard only has one PCiE x16 slot. the others are x8. Don't know if that makes a difference? 

I don't have a PSU laying around, so that is hard to test. I might try and swap the cables (since its modular)

I updated the BIOS back in September, because.... you never know. It didn't change anything. 

i ran a memtest way back. Sorry for not including. But i can run one again

in worst case scenario it can be monitor like what fresh rate you have? 144 100 or 60? becasue that is the problem or in it can be cable some breaks or smth i would look into it too.

[Angrycrab]

Have you clean Installed drivers using DDU In safe mode?

[Elapo]

My motherboard only has one PCiE x16 slot. the others are x8. Don't know if that makes a difference? 

I don't have a PSU laying around, so that is hard to test. I might try and swap the cables (since its modular)

I updated the BIOS back in September, because.... you never know. It didn't change anything. 

i ran a memtest way back. Sorry for not including. But i can run one again

 

x8 is more than enough, try it!

Swapping the cables is also worth a try IMO(if your PSU has multiple connectors for PCIe, it's probably also worth trying those) if BIOS & RAM are ok, that's more we can exclude.

 

Running another memtest isn't necessary at this point, since you've done one so recently.

[DJESMOND]

in worst case scenario it can be monitor like what fresh rate you have? 144 100 or 60? becasue that is the problem or in it can be cable some breaks or smth i would look into it too.

 

I have to monitors. 1 144 and one 60. I Have tried running them both at 60 but that didn't change things. (They do that but default of new OS install). I run of of DVI and HDMI and cables are fine, since i use them for tv swell (another pc). 

 

Have you clean Installed drivers using DDU In safe mode?

 

Yes i have done i twice. once with DDU and once using another driver remover (can't remember name). I also tried the disable driver update. Did not change the crashing.

 

x8 is more than enough, try it!

Swapping the cables is also worth a try IMO(if your PSU has multiple connectors for PCIe, it's probably also worth trying those) if BIOS & RAM are ok, that's more we can exclude.

 

Running another memtest isn't necessary at this point, since you've done one so recently.

 

 

Ill give it a shot. See how it goes. Ill try with current cables then swap if need be.

Wish me me luck

[Elapo]

Ill give it a shot. See how it goes. Ill try with current cables then swap if need be.

Wish me me luck

All the luck to you, I know how infuriating problems like these are, the cause is often something stupid as well.

[manofsteel]

I have to monitors. 1 144 and one 60. I Have tried running them both at 60 but that didn't change things. (They do that but default of new OS install). I run of of DVI and HDMI and cables are fine, since i use them for tv swell (another pc). 

 

 

Yes i have done i twice. once with DDU and once using another driver remover (can't remember name). I also tried the disable driver update. Did not change the crashing.

 

 

 

Ill give it a shot. See how it goes. Ill try with current cables then swap if need be.

Wish me me luck

btw you said that you tested GPU and nothing happend but on games it does? so maybe its a HDD that is damaged and causes to not read properly a file that are need ? that can a source too (funny because it is true ).

[DJESMOND]

All the luck to you, I know how infuriating problems like these are, the cause is often something stupid as well.

 

Thanks. it hurts.

 

So new status:

 

I used the GPU in the x8 slot. (same cables)

It booted. and i ran Furmark. Instant crash (Log says driver)

I swapped it back to x16 slot and ran Furmark. 10 secs.... then crash.

Then i swapped the cables and the connector on PSU. Ran Furmark.... 2 min.... no crashing.

 

So it might have been the cable or connector. For now i can't tell for sure... Im gonna use the pc for a bit. Download a game or something and see where it goes.

 

 

btw you said that you tested GPU and nothing happend but on games it does? so maybe its a HDD that is damaged and causes to not read properly a file that are need ? that can a source too (funny because it is true ).

 

Well yes. it crashes in games, but its at random. So its hard to tell why. I've used the SSD for windows and now trying the HDD for Mac. So far the disks doesn't seem to be an issue. If the current fix doesn't work, then ill run DiskWarrior on them both.

[DJESMOND]

Thanks. it hurts.

 

So new status:

 

I used the GPU in the x8 slot. (same cables)

It booted. and i ran Furmark. Instant crash (Log says driver)

I swapped it back to x16 slot and ran Furmark. 10 secs.... then crash.

Then i swapped the cables and the connector on PSU. Ran Furmark.... 2 min.... no crashing.

 

So it might have been the cable or connector. For now i can't tell for sure... Im gonna use the pc for a bit. Download a game or something and see where it goes.

 

 

 

Well yes. it crashes in games, but its at random. So its hard to tell why. I've used the SSD for windows and now trying the HDD for Mac. So far the disks doesn't seem to be an issue. If the current fix doesn't work, then ill run DiskWarrior on them both.

 

Quick update. ..... it crashed shortly after submitting the post. (still running fur mark). Im gonna try running with individual cables for the 6 and 8 pin for GPU

 

EDIT: Crashing again..... 

[Riksland]

I had the same problem as you on my old computer that I gave to my sister. I tried to change the HDMI cable and that accually worked, it haven't crashed since that(about 8 month ago)

[DJESMOND]

I had the same problem as you on my old computer that I gave to my sister. I tried to change the HDMI cable and that accually worked, it haven't crashed since that(about 8 month ago)

 

Ill try a swap. But not hopeful

[thekeemo]

Try it in another system?

[Elapo]

I had the same problem as you on my old computer that I gave to my sister. I tried to change the HDMI cable and that accually worked, it haven't crashed since that(about 8 month ago)

 

Weird, but I guess lousy insulation could cause it to short out, and then make the GPU protect itself.

 

Quick update. ..... it crashed shortly after submitting the post. (still running fur mark). Im gonna try running with individual cables for the 6 and 8 pin for GPU

 

EDIT: Crashing again..... 

Dangit.

I can't think of anything right now. Might just be the CPU or motherboard, but that'd be weird. Or the PSU is completely busted, also unlikely...

 

Try it in another system?

 

He did! Well, the store, anyway:

Here is a list of the thinks i have done

• ​Clean install driver with the Nvidia installer (No GFE)
• Safe boot into Windows and Removed drivers then installed new ones again.
• Installing both older and newer(beta) drivers.
• RMA GPU (They ran stress tests for 10 hours, no issues)
• Running a 10 hour full on stress test (CPU and GPU), no crashing.... nothing.
• Format and clean install Windows 10. (Done 4 times (yes 4)).
• Format and clean install Windows 8.1 
• Format and clean install Windows 7
• Format and clean install Mac OSX El Capitan

 

[thekeemo]

Weird, but I guess lousy insulation could cause it to short out, and then make the GPU protect itself.

 

Dangit.

I can't think of anything right now. Might just be the CPU or motherboard, but that'd be weird. Or the PSU is completely busted, also unlikely...

 

 

He did! Well, the store, anyway:

from what I gather they don't bother to look at it if the system is turned on when the test is over its considered OK..

[manofsteel]

Wait he get RMA from some third party not from asus? man thats the biggest mistake cuz they can run stress test like you and only that but if you send it to asus they should check if its not HARDWARE related issue but if you did send it to ASUS that time i think it could be that that there just ditched you out and you need to resend it over (sorry for such post now but didnt quite read your OP on that part ). The last thing is that your GPU can have issues with dual display just unplug one of monitors and see if that helps ;P

[Evil-I]

In my experience grey screen is as you've already mentioned is usually the driver crashing due to GPU instability and in my case most regularly seen when over clocking and going too far or not having upped the voltage enough to support the overclock.

 

Given the above, I'd suggest the power supply should be your first port of call now.  Or put the card in a whole other system to see if it's stable then.

 

BTW, I notice your RAM speed is stated as 1800mhz, is this correct?  Or is it 1866mhz?  Just wondered if you were using a non standard CPU strap etc as I'd either expect 1600 or 1866 if your CPU is running at stock

 

My other thought for you, is I have had a GTX970 that was stable under heavy load, but unstable when in windows and doing other things.  it appeared to relate to the GPU down clocking and down volting causing instability.  I had a hell of a job getting the supplier to agree the card was faulty as they would typically just bang it into a test bench and run a stress test which it would of course pass.  it was only when I persuaded them to just use it like a normal desktop for a while they had the same issues as I had and agreed the card was faulty.  Just because the card has been tested by the supplier, it doesn't necessarily mean the card isn't faulty...

 

Good luck!

 

E-I

[DJESMOND]

from what I gather they don't bother to look at it if the system is turned on when the test is over its considered OK..

 

I trust in the retailer. They have never done anything to make me think otherwise. They ran multiple test. No need to list here, tough they did send me that info.

 

Wait he get RMA from some third party not from asus? man thats the biggest mistake cuz they can run stress test like you and only that but if you send it to asus they should check if its not HARDWARE related issue but if you did send it to ASUS that time i think it could be that that there just ditched you out and you need to resend it over (sorry for such post now but didnt quite read your OP on that part ). The last thing is that your GPU can have issues with dual display just unplug one of monitors and see if that helps ;P

 

I didn't send it to ASUS, i went to my retailer. I trust them. They have been great in the past. 

Im only running one monitor at the moment. for testing.... no luck.

 

 

Weird, but I guess lousy insulation could cause it to short out, and then make the GPU protect itself.

 

Dangit.

I can't think of anything right now. Might just be the CPU or motherboard, but that'd be weird. Or the PSU is completely busted, also unlikely...

 

 

He did! Well, the store, anyway:

 

Yea.... I'm out of things as well... Gonna wait for my dad to send my old ATI card..... Then i can see if its GPU/nvidia related or if its MB or PSU

 

Ill try a swap. But not hopeful

 

No luck.

[DJESMOND]

In my experience grey screen is as you've already mentioned is usually the driver crashing due to GPU instability and in my case most regularly seen when over clocking and going too far or not having upped the voltage enough to support the overclock.

 

Given the above, I'd suggest the power supply should be your first port of call now.  Or put the card in a whole other system to see if it's stable then.

 

BTW, I notice your RAM speed is stated as 1800mhz, is this correct?  Or is it 1866mhz?  Just wondered if you were using a non standard CPU strap etc as I'd either expect 1600 or 1866 if your CPU is running at stock

 

My other thought for you, is I have had a GTX970 that was stable under heavy load, but unstable when in windows and doing other things.  it appeared to relate to the GPU down clocking and down volting causing instability.  I had a hell of a job getting the supplier to agree the card was faulty as they would typically just bang it into a test bench and run a stress test which it would of course pass.  it was only when I persuaded them to just use it like a normal desktop for a while they had the same issues as I had and agreed the card was faulty.  Just because the card has been tested by the supplier, it doesn't necessarily mean the card isn't faulty...

 

Good luck!

 

E-I

ITs running at 1866 (I just didn't bother to put the last in). I runs at 1333 mhm according to OSX, but thats just a hackintosh problem. 

Ill see what the ATI card does.

if it works like a charm, ill contact the retailer and discuss what to do with them.

Thanks for you input mate.

Tough my crashing happens, both in games, and desktop. so it doesn't seem to be load issue. Regarding the GPU. i monitored it with Afterburner back in September... nothing to note. Though i did try under clocking Vram as one online post suggested.... no change.... so i went back to stock

[manofsteel]

ITs running at 1866 (I just didn't bother to put the last in). I runs at 1333 mhm according to OSX, but thats just a hackintosh problem. 

Ill see what the ATI card does.

if it works like a charm, ill contact the retailer and discuss what to do with them.

Thanks for you input mate.

Tough my crashing happens, both in games, and desktop. so it doesn't seem to be load issue. Regarding the GPU. i monitored it with Afterburner back in September... nothing to note. Though i did try under clocking Vram as one online post suggested.... no change.... so i went back to stock

He didint said that he underclock vram but the card had issue when going back from game to windows because clock were getting lower automaticly and card had problem with lower clocks so in your case underclocking vram wont do much more like if your GPU proccessor is overclocked or got too much or too little voltage than that can cause such problem.btw just in case just test that card on second monitor (this non 144) and see what happens if it crashes than both monitors are fine and we can say thats something either with mobo PSU or CPU on the worst

 

Oh and never trust retailers if they didint send to main company RMA becasue i worked in such office and know how some of them can work and i rma'd things too (my mobo that is currently in the system after purchase had an lan connector slot problem, didint catch up cable i needed to rma it 2 or 3 because for first 2 they didint solve the problem but after they send it to the GIGABYTE then GIGABYTE replace it and now wuala as you can see but still CPU or Mobo has some kind of fault that can cause crash on my system but its not as bad as in yours oh and i kinda rised that power in the system to 10% and crash never occured after so ).

[Elapo]

from what I gather they don't bother to look at it if the system is turned on when the test is over its considered OK..

 

OP's computer is flat out crashing. If it even survived a 10 hour stress test, artifacts or not I'm fairly confident the card is at least not the sole cause of the crashes.

 

In my experience grey screen is as you've already mentioned is usually the driver crashing due to GPU instability and in my case most regularly seen when over clocking and going too far or not having upped the voltage enough to support the overclock.

 

Given the above, I'd suggest the power supply should be your first port of call now.  Or put the card in a whole other system to see if it's stable then.

 

BTW, I notice your RAM speed is stated as 1800mhz, is this correct?  Or is it 1866mhz?  Just wondered if you were using a non standard CPU strap etc as I'd either expect 1600 or 1866 if your CPU is running at stock

 

My other thought for you, is I have had a GTX970 that was stable under heavy load, but unstable when in windows and doing other things.  it appeared to relate to the GPU down clocking and down volting causing instability.  I had a hell of a job getting the supplier to agree the card was faulty as they would typically just bang it into a test bench and run a stress test which it would of course pass.  it was only when I persuaded them to just use it like a normal desktop for a while they had the same issues as I had and agreed the card was faulty.  Just because the card has been tested by the supplier, it doesn't necessarily mean the card isn't faulty...

 

Good luck!

 

E-I

OP's pc has crashed both during idle and while running furmark. I'd say that's a pretty good indicator GPU load has little to do with it.

 

Also, GPU is at stock, so that would mean something is wrong with the power delivery on the card.

The card has been stress tested for 10+ hours by the retailer, so that would mean the card's power delivery is fine.

 

I really doubt it's the card at this point, but I could be totally wrong. Guess we'll have to see with the other GPU.

[DJESMOND]

He didint said that he underclock vram but the card had issue when going back from game to windows because clock were getting lower automaticly and card had problem with lower clocks so in your case underclocking vram wont do much more like if your GPU proccessor is overclocked or got too much or too little voltage than that can cause such problem.btw just in case just test that card on second monitor (this non 144) and see what happens if it crashes than both monitors are fine and we can say thats something either with mobo PSU or CPU on the worst

 

Im not using the 144 atm. Im running of a simple 60 hz monitor. No changes. It crashes no matter the monitor setup or the output cables

 

OP's computer is flat out crashing. If it even survived a 10 hour stress test, artifacts or not I'm fairly confident the card is at least not the sole cause of the crashes.

 

OP's pc has crashed both during idle and while running furmark. I'd say that's a pretty good indicator GPU load has little to do with it.

 

Also, GPU is at stock, so that would mean something is wrong with the power delivery on the card.

The card has been stress tested for 10+ hours by the retailer, so that would mean the card's power delivery is fine.

 

I really doubt it's the card at this point, but I could be totally wrong. Guess we'll have to see with the other GPU.

 

Im sorry for forgetting some of the things that i have tried (it was a long time ago.....) I have updated the post with the new stuff.

 

Now as i said. i did monitor the GPU back then. And it doesn't do anything wrong. I really don't think that its the GPU either. 

It could be the PSU or the MB.

When the other card arrives i can tell if its the GPU. 

At this point i just wanna know what the f**k is wrong.... 

I can't use my PC....