Sign in with
Sign up | Sign in
Your question

Nvidia GTX660 crash to desktop, expert help needed

Last response: in Graphics & Displays
Share
a c 171 U Graphics card
February 5, 2013 7:40:27 AM

Will appreciate anyone who takes the time to help me out here, so here goes:
so having these crashes with crysis 2 and 3, when i look in windows action centre reliability monitor there are also a lot of "vieo hardware error" and "application error". Tried all sorts of drivers, old new and beta. Fully went through my pc, updated everything, bios, drivers etc, malware scan, cccleaner, defrag, chkdsk. I'm thinking there is a fault with my video card. here are the error logs from a few crashes:

"Faulting application name: Crysis 3 MP Open Beta.exe, version: 1.0.0.0, time stamp: 0x02862884
Faulting module name: d3d11.dll, version: 6.1.7601.17514, time stamp: 0x4ce7b7b0
Exception code: 0xc0000005
Fault offset: 0x000591a1
Faulting process id: 0x163c
Faulting application start time: 0x01ce02b9e373b48e
Faulting application path: C:\Program Files (x86)\Origin Games\Crysis 3 MP Open Beta\bin32\Crysis 3 MP Open Beta.exe
Faulting module path: C:\Windows\system32\d3d11.dll
Report Id: ef5a754f-6eaf-11e2-9606-bc5ff45b80fa"

"Faulting application name: Crysis 3 MP Open Beta.exe, version: 1.0.0.0, time stamp: 0x02862884
Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: 0x4ec49b8f
Exception code: 0xc0000374
Fault offset: 0x000ce6c3
Faulting process id: 0xd70
Faulting application start time: 0x01ce0130f4fd50a8
Faulting application path: C:\Program Files (x86)\Origin Games\Crysis 3 MP Open Beta\bin32\Crysis 3 MP Open Beta.exe
Faulting module path: C:\Windows\SysWOW64\ntdll.dll
Report Id: 3bb6d8ed-6d24-11e2-b481-bc5ff45b80fa"

"Faulting application name: Crysis 3 MP Open Beta.exe, version: 1.0.0.0, time stamp: 0x02862884
Faulting module name: nvwgf2um.dll, version: 9.18.13.1396, time stamp: 0x51024e15
Exception code: 0xc0000005
Fault offset: 0x006f2cb7
Faulting process id: 0x368
Faulting application start time: 0x01ce012b6a5ef5cd
Faulting application path: C:\Program Files (x86)\Origin Games\Crysis 3 MP Open Beta\bin32\Crysis 3 MP Open Beta.exe
Faulting module path: C:\Windows\system32\nvwgf2um.dll"

"The program Crysis2.exe version 1.9.0.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.
Process ID: d9c
Start Time: 01cdfd4081f69697
Termination Time: 60
Application Path: C:\Program Files (x86)\Electronic Arts\Crytek\Crysis 2\bin32\Crysis2.exe
Report Id: "

"Faulting application name: Crysis2.exe, version: 1.9.0.0, time stamp: 0x00000000
Faulting module name: CryRenderD3D9.DLL, version: 1.9.0.0, time stamp: 0x4dfa43c3
Exception code: 0xc0000005
Fault offset: 0x001b8400
Faulting process id: 0x280
Faulting application start time: 0x01cdfbaa432e78fc
Faulting application path: C:\Program Files (x86)\Electronic Arts\Crytek\Crysis 2\bin32\Crysis2.exe
Faulting module path: C:\Program Files (x86)\Electronic Arts\Crytek\Crysis 2\bin32\CryRenderD3D9.DLL
Report Id: 83bcfe01-679d-11e2-bc6b-bc5ff45b80fa"

a b U Graphics card
February 5, 2013 7:53:23 AM

is this only happening in Crysis ?
m
0
l
a c 171 U Graphics card
February 5, 2013 7:57:38 AM

that is all i have played a lot of recently. but its happening with both c2 and c3, and it only started happening when i upgraded from a AM6850 to gtx660. I did a full clean uninstall of the amd drivers before i switched to Nvidia drivers. I had played a bit of skyrim but that was only for about 45 mins. the crashes can happen within 15 mins, or can be an hour. All temps are well below max. Gpu 60c, cpu is less than 60c during gaming.
m
0
l
Related resources
a b U Graphics card
February 5, 2013 8:10:03 AM

have u OCed ur card ?
are u using monitoring apps like PricisionX or Afterburner in the background ?
when it crashes , do u get the Little balloon mentioning nvidia drivers crashing ?
m
0
l
a c 171 U Graphics card
February 5, 2013 8:39:00 AM

occasionally its nvidia diplay driver error, mostly just windows has encountered an error and can not recover. afterburner is running. No overclock. When overclocked the crashes occur way more frequently and always nvidia dispay driver errors. I actually underclocked the card a little to get better stability.
m
0
l
February 5, 2013 9:03:29 AM

"Faulting module name: d3d11.dll"
"Faulting module name: CryRenderD3D9.DLL"

seems like directX to me.
m
0
l
a b U Graphics card
February 5, 2013 9:50:56 AM

As u mentioned u already updated ur motherboard bios , so just enter ur mb setup , search for "Advance option" ,
then "System Agent Configuration" , after that
"NB PciExpress Configuration" ( have in mind that depending on you MB manufacturer these terms may differ ) ,
there u should have an option mentioning the Bandwidth of your Pciexpress card , it should have 3 or 2 option depending on again on your motherboard manufacturer ( GEN2 , GEN3 or AUTO ) , whatever its set to , change it to "GEN2" . press F10 , save and reboot , try to play Crysis to see if it did solve the problem .
m
0
l
a b U Graphics card
February 5, 2013 10:27:51 AM

iam2thecrowe said:
occasionally its nvidia diplay driver error, mostly just windows has encountered an error and can not recover. afterburner is running. No overclock. When overclocked the crashes occur way more frequently and always nvidia dispay driver errors. I actually underclocked the card a little to get better stability.



I had the exact same problem with afterburner open. Crysis warhead was crashing to desktop constantly. Like you I moved from a 5770 to a 570 and had the exact same issue. I bought an SSD a month later and did a clean install and the issue went away.

The only time I crash now is when I get greedy on the overclock, 920 core is the end of the line for my MSI ref model (once I added a cooler).

Sorry that is all I have. Clean installation resolved my identical issue.
m
0
l
a c 171 U Graphics card
February 6, 2013 7:51:06 AM

spentshells said:
I had the exact same problem with afterburner open. Crysis warhead was crashing to desktop constantly. Like you I moved from a 5770 to a 570 and had the exact same issue. I bought an SSD a month later and did a clean install and the issue went away.

The only time I crash now is when I get greedy on the overclock, 920 core is the end of the line for my MSI ref model (once I added a cooler).

Sorry that is all I have. Clean installation resolved my identical issue.

crap, i was really trying to avoid this. i have a spare hdd i will try it with and see what happens. The re-installing direct x i would like to give a shot, but i dont think you can do that? I tried re-running the installer but it says most current version is installed.
m
0
l
a b U Graphics card
February 6, 2013 3:20:02 PM

iam2thecrowe said:
crap, i was really trying to avoid this. i have a spare hdd i will try it with and see what happens. The re-installing direct x i would like to give a shot, but i dont think you can do that? I tried re-running the installer but it says most current version is installed.


maybe uninstall dx from the add/remove programs and the drivers reboot then reinstall?
m
0
l
a c 271 U Graphics card
February 6, 2013 3:21:48 PM

spentshells said:
maybe uninstall dx from the add/remove programs and the drivers reboot then reinstall?

You can reinstall DX but you cannot uninstall it.
m
0
l
a b U Graphics card
February 6, 2013 4:02:10 PM

Mousemonkey said:
You can reinstall DX but you cannot uninstall it.


No? interesting but I don't believe it can not be done just obviously not in the way I described
m
0
l
a c 271 U Graphics card
February 6, 2013 4:05:01 PM

spentshells said:
No? interesting but I don't believe it can not be done just obviously not in the way I described

You are welcome to try it but I assure you it cannot be done. You also cannot downgrade it, no DX11 back to DX10 for instance.
m
0
l
a b U Graphics card
February 6, 2013 4:21:06 PM

really? Guess I will have a look when I get home as I have a fresh build sitting there so it doesn't matter if I bang up the registry.
Will let you know
m
0
l
a c 271 U Graphics card
February 6, 2013 4:27:42 PM

spentshells said:
really? Guess I will have a look when I get home as I have a fresh build sitting there so it doesn't matter if I bang up the registry.
Will let you know

Have fun with it, do not be surprised if killing DX also kills your Windows install though! :lol: 
m
0
l
a b U Graphics card
February 6, 2013 4:46:51 PM

Mousemonkey said:
Have fun with it, do not be surprised if killing DX also kills your Windows install though! :lol: 



LOL thats the plan
m
0
l
a c 171 U Graphics card
February 7, 2013 6:36:25 PM

spentshells said:
really? Guess I will have a look when I get home as I have a fresh build sitting there so it doesn't matter if I bang up the registry.
Will let you know

i remember with XP there was a DX uninstaller, not by microsoft was a 3rd party util.
and look such a thing still exists!

http://www.pcauthorities.com/pc-maintenance/how-to-unin...

http://download.cnet.com/DirectX-Happy-Uninstall/3000-2... for $20 you can uninstall direct x 11!

Does win 7 still have te repair install option that XP did?
m
0
l
a c 592 U Graphics card
February 7, 2013 7:36:10 PM

Did you run "DXDIAG" to check your directx install?
m
0
l
a b U Graphics card
February 7, 2013 9:42:08 PM

The motherboard on the other machine sucks and it has to be rma'd
m
0
l
a b U Graphics card
February 7, 2013 9:42:57 PM

repair yes, but it doesn't work worth a ***
m
0
l
a c 171 U Graphics card
February 8, 2013 8:39:23 AM

Faulting application name: Crysis2.exe, version: 1.9.0.0, time stamp: 0x00000000
Faulting module name: nvwgf2um.dll, version: 9.18.13.1396, time stamp: 0x51024e15
Exception code: 0xc0000005
Fault offset: 0x006e6d67
Faulting process id: 0x664
Faulting application start time: 0x01ce05e46c233b4a
Faulting application path: C:\Program Files (x86)\Electronic Arts\Crytek\Crysis 2\bin32\Crysis2.exe
Faulting module path: C:\Windows\system32\nvwgf2um.dll
Report Id: 96e65c11-71da-11e2-95de-bc5ff45b80fa

another crash. a quick google and many are having issues, and its a direct x nvidia driver error. I just ran driversweeper and went through all my bios settings and changed a few things. someone suggested a memort issue. I might try dropping the memory from 2133 to 1600 as is the spec for the cpu memory controller, maybe its corrupting something in memory.
m
0
l
February 8, 2013 8:51:57 AM

If you are using beta driver you should go back to .70 whql drivers.
m
0
l
a c 592 U Graphics card
February 8, 2013 4:27:35 PM

cooldudesubho said:
If you are using beta driver you should go back to .70 whql drivers.

.90 are the latest WHQL.

I think you should reinstall Crysis 2. If you are playing on Steam, you can go to the game Properties and select "Verify the Integrity of the Game Files.." from the right-click drop down menu.
m
0
l
a c 171 U Graphics card
February 8, 2013 5:43:37 PM

17seconds said:
.90 are the latest WHQL.

I think you should reinstall Crysis 2. If you are playing on Steam, you can go to the game Properties and select "Verify the Integrity of the Game Files.." from the right-click drop down menu.

its crysis 2 and 3 that have similar errors. That is all i have been playing lately, so i dont know if it effects other games. But since i dropped the memory speed from 2133 to 1600 i havnt had an error yet. played crysis 2 for 3 hrs with no problem. Hopefully it stays that way.
m
0
l
a b U Graphics card
February 11, 2013 12:10:33 PM



iam2thecrowe said:
its crysis 2 and 3 that have similar errors. That is all i have been playing lately, so i dont know if it effects other games. But since i dropped the memory speed from 2133 to 1600 i havnt had an error yet. played crysis 2 for 3 hrs with no problem. Hopefully it stays that way.



Did i try the this ?

SkyWalker1726 said:
As u mentioned u already updated ur motherboard bios , so just enter ur mb setup , search for "Advance option" ,
then "System Agent Configuration" , after that
"NB PciExpress Configuration" ( have in mind that depending on you MB manufacturer these terms may differ ) ,
there u should have an option mentioning the Bandwidth of your Pciexpress card , it should have 3 or 2 option depending on again on your motherboard manufacturer ( GEN2 , GEN3 or AUTO ) , whatever its set to , change it to "GEN2" . press F10 , save and reboot , try to play Crysis to see if it did solve the problem .
m
0
l
a c 171 U Graphics card
February 11, 2013 6:00:21 PM

SkyWalker1726 said:
Did i try the this ?

well i did get another crash so i will try this next. I had it set to AUTO, and since changed it to "gen 3". Ill try "gen 2", Although everything in my PC supports Gen 3.....
Is this a known bug?
m
0
l
a b U Graphics card
February 11, 2013 6:33:21 PM

i had the same problem , had my GTX for almost 4 month when i decided to upgrade my MB CPU to PCI express 3.0 capable H/W ...
that's when the Black screen and driver crashes started .
but in my case , i couldn't play any game more than 15~20 minutes TOP.
then found out that it's a Common bug with ASrock and Asus Mobos , Switched it to PCIe 2.0 and worked like charm .
to be honest that was the weirdest problem that has ever happened to me .
hope that'll solve ur problem too :) 
m
0
l
a c 171 U Graphics card
February 12, 2013 7:43:50 AM

SkyWalker1726 said:
i had the same problem , had my GTX for almost 4 month when i decided to upgrade my MB CPU to PCI express 3.0 capable H/W ...
that's when the Black screen and driver crashes started .
but in my case , i couldn't play any game more than 15~20 minutes TOP.
then found out that it's a Common bug with ASrock and Asus Mobos , Switched it to PCIe 2.0 and worked like charm .
to be honest that was the weirdest problem that has ever happened to me .
hope that'll solve ur problem too :) 

ok, so i just tried going to gen2 speeds but got a crash again. now trying a much older driver, the one that came with the card on the cd, 305.27. someone else on another site suggested going to an older driver fixed their issues. After that i will try swapping out sticks of memory incse one is faulty, although crashes never happened until i upgraded to this gtx660, i think its probably a faulty card.
m
0
l
!