Sign in with
Sign up | Sign in
Your question

Display adapter stopped responding

Tags:
  • Graphics Cards
  • Display Adapter
  • Graphics
Last response: in Graphics & Displays
Share
March 14, 2010 10:21:07 PM

My graphics card has been working fine for about 10-15 days, then after i installed nvidia ntune i got a blue screen. After my computer recovered everytime
i start a game, it starts and then starts lagging really bad and freezes my computer. A few times i managed to recover and i saw the message
"Display adapter has stopped working but recovered". Im running windows 7 ultimate x64.

I have 2 inno3d GTX 285's running in sli.

dxdiag:


Time of this report: 3/15/2010, 00:07:11
Machine name: EVILMOSQUITO-PC
Operating System: Windows 7 Ultimate 64-bit (6.1, Build 7600) (7600.win7_rtm.090713-1255)
Language: English (Regional Setting: English)
System Manufacturer: System manufacture
System Model: System Product Name
BIOS: BIOS Date: 06/01/09 20:53:40 Ver: 08.00.15
Processor: Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz (8 CPUs), ~2.7GHz
Memory: 12288MB RAM
Available OS Memory: 12280MB RAM
Page File: 1979MB used, 22576MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
DxDiag Version: 6.01.7600.16385 32bit Unicode


Card name: NVIDIA GeForce GTX 285
Manufacturer: NVIDIA
Chip type: NVxx
DAC type: Integrated RAMDAC
Device Key: Enum\PCI\VEN_10DE&DEV_05E3&SUBSYS_070310DE&REV_A1
Display Memory: 4077 MB
Dedicated Memory: 1005 MB
Shared Memory: 3071 MB
Current Mode: 1920 x 1080 (32 bit) (60Hz)
Monitor Name: Generic PnP Monitor
Monitor Model: SyncMaster
Monitor Id: SAM060F
Native Mode: 1920 x 1080(p) (60.000Hz)
Output Type: DVI
Driver Name: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um
Driver File Version: 8.17.0011.9621 (English)
Driver Version: 8.17.11.9621
DDI Version: 10
Driver Model: WDDM 1.1
Driver Attributes: Final Retail
Driver Date/Size: 1/12/2010 05:03:33, 11862120 bytes
WHQL Logo'd: n/a
WHQL Date Stamp: n/a
Device Identifier: {D7B71E3E-46A3-11CF-FB56-08271FC2C535}
Vendor ID: 0x10DE
Device ID: 0x05E3
SubSys ID: 0x070310DE
Revision ID: 0x00A1
Rank Of Driver: 00E62001
Video Accel: ModeMPEG2_A ModeMPEG2_C ModeVC1_C ModeWMV9_C

I have the latest drivers so im sure its not that.
Overheating isnt a problem either, when lag starts its about 39-45C.

I cant play any games at all without freezing my computer.
I cant even run my Physx screensaver, it also freezes my computer :cry: 

Does anyone know what could be wrong?

More about : display adapter stopped responding

a c 242 U Graphics card
March 14, 2010 11:11:49 PM

1. Uninstall all GFX drivers and programs
2. Remove all things nVidia from registry using CCleaner
3. Reboot
4. Reinstall GFX drivers.
March 15, 2010 3:01:10 AM

Just tried that and i still get the same thing.
This time after my computer crashed, after i turned it back on i went to check
gpu temps. I found that gpu 1 was around 41C and gpu 2 was at about 61C.
I also got this message after attempting to play SWAT 4:

No Label

Crash Time: 03/15/10 04:12:54

OS: Windows NT 6.1 (Build: 7600)
CPU: GenuineIntel PentiumPro-class processor @ 3210 MHz with 4095MB RAM
Video: NVIDIA GeForce GTX 285 (9621)

UserName: EvilMosquito
ComputerName: EVILMOSQUITOPC
Application location: C:\Program Files (x86)\Sierra\SWAT 4\Content\System\

SWAT Build Number: 31973

IDirect3DVertexBuffer9::Lock failed(88760870).

History: FD3DVertexStream::Cache <- FD3DRenderInterface::SetVertexStreams <- USkeletalMeshInstance::Render <- FDynamicActor::Render [SWATofficerSMGbriefing1] <- RenderSolidScenePass <- RenderSolidScenePasses <- RenderLevel <- FLevelSceneNode::Render <- FPlayerSceneNode::Render <- UGameEngine:: Draw <- UWindowsViewport::Repaint <- UWindowsClient::Tick <- ClientTick <- UGameEngine::Tick <- UpdateWorld <- MainLoop->GenerateExtraCrashInfo [(GLevel: 'myLevel' PendingLevel: '(NULL)' NetMode: 'NM_Standalone'] <- MainLoop


March 15, 2010 1:24:18 PM

Alright i tried going back to windows xp 32 bit. Still didnt work...

Then i got the idea to switch my gpus around. I switch them around and everything works fine now.
It looks like one of my gpus failed. Ill go back to the shop and try to exchange it, or fix the problem.
!