• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 366
  • Last Modified:

gfx card stopping hibernation

Just upgraded my gfx card

Onboard is Intel Extreme Graphics
I had ATI Radeon 9250 series 128mb low profile agp card (not vista aero compatible)
I've now installed a NVidia Geforce 6200 series 256mb low profile agp card (now aero works)

Problem is this:

I have XP SP2 (Pro) and Vista Ultimate 32bit dual booted with no probs
But now in both OS' I can't resume from Hibernation, Sleep, etc

In XP - I turn on the PC, after a few secs the monitor turn off then the PC restarts by itself - interesting it doesn't say the resuming windows failed - it just deletes my restoration data automatically and goes to the Vista Boot Menu (of which XP is the default OS)

I Vista, I get the aura effect while resuming is taking place, then i get a blinking dos cursor, then i get two cursors, then 38 all over the screen (not blinking at this point). The monitor turns off and I have to restart the PC. I get the option to try and resume again or delete restoration data.

I uninstalled the ATI card from Device manager is both OS' before changing the card. In Vista, the drivers were installed by windows automatically and I can't install the drivers off the CD.
In XP i installed the drivers off the disc OK.
0
Ryan_R
Asked:
Ryan_R
  • 14
  • 14
1 Solution
 
johnb6767Commented:
Maybe a BIOS setting for the Video is not configured right?
0
 
Ryan_RAuthor Commented:
such as..?
0
 
johnb6767Commented:
I dont know whats in your BIOS.

AGP Voltage
AGP Aperture Size, still lower from when you had the older card.....

What kind of MOBO?

Only reason I consider BIOS first, is that it is the only constant between the 2 OS's....
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
johnb6767Commented:
Are you getting any .dmp files in Vista for the shutdowns?
0
 
johnb6767Commented:
or XP ( if it makes it that far)?
0
 
Ryan_RAuthor Commented:
PC/Mobo is a Compaq Evo D510 SFF
agp aperture is at 128mb i think which is fine by me
bus for the agp card is 4x - which is supported by my mobo i'm pretty sure
where do i look for .dmp files?
0
 
Ryan_RAuthor Commented:
0
 
johnb6767Commented:
Dont have an 8X option (assuming the card is 1,4,8X compatible, natively 8X)

Go ahead and zip all but the memory.dmp.......

0
 
johnb6767Commented:
and is there a 256 option for the aperture size?
0
 
Ryan_RAuthor Commented:
there is a 256mb aperture size available - from my research there isn't a great deal of dif between the two options when other orgs tested it out.

yeah both the mobo and card are 2x, 4x, and 8x compatible from memory

when i get home i'll upload the dumps.
0
 
Ryan_RAuthor Commented:
btw the dumps in that screenshot were all frmo vista - i didn't scan my xp HDD.
0
 
Ryan_RAuthor Commented:
When I got home and turned on my PC I noticed that I had hibernated XP again (it's a force of habit).
This time I got power to my MS USB mouse which I hadn't got the last few times (maybe coz i was moving it around) - but it actually resumed that time. I've yet to test if Vista will work now. Give me 2 mins.
0
 
Ryan_RAuthor Commented:
vista failed to resume from Sleep (which used to work)

here are the dump files:
https://filedb.experts-exchange.com/incoming/ee-stuff/3085-dumps.zip
0
 
johnb6767Commented:
Mini040307-01.dmp
VIDEO_TDR_FAILURE (116)
nvlddmkm.sys is the fault.

STACK_TEXT:  
88d83bc8 89fa5578 00000116 8459d708 89fcb640 nt!KeBugCheckEx+0x1e
88d83bec 89fa6231 89fcb640 00000000 00000002 dxgkrnl!TdrBugcheckOnTimeout+0x8d
88d83c0c 89f449a6 00000000 00000102 8ba7e670 dxgkrnl!TdrIsRecoveryRequired+0xa1
88d83c70 89f54d58 8ba7e670 000000c0 00000000 dxgkrnl!VidSchiReportHwHang+0x2e4
88d83c9c 89f54ab8 8ba7e670 00000000 00000000 dxgkrnl!VidSchiCheckHwProgress+0x69
88d83cc8 89f32193 00000002 00000000 8ba7e670 dxgkrnl!VidSchiWaitForSchedulerEvents+0x13f
88d83d58 89f54fac 8ba7e670 00000000 8ba7e670 dxgkrnl!VidSchiScheduleCommandToRun+0xac
88d83d6c 89f94af2 8ba7e670 8ba962c8 88d83dc0 dxgkrnl!VidSchiRun_PriorityTable+0xf
88d83d7c 819afbfd 8ba7e670 88d88680 00000000 dxgkrnl!VidSchiWorkerThread+0x61
88d83dc0 8189a396 89f94a91 8ba7e670 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

WD-20070403-0830.dmp
VIDEO_TDR_TIMEOUT_DETECTED (117)
The display driver failed to respond in timely fashion.
nvlddmkm.sys is the fault.

STACK_TEXT:  
88d83ce4 89fa6121 00000000 89fcb640 844f2038 dxgkrnl!TdrUpdateDbgReport+0x68
88d83d0c 89fa0592 00000000 8ba7eb34 844f2038 dxgkrnl!TdrCollectDbgInfoStage2+0x17f
88d83d48 89fa62cd 844f2038 8ba7e670 88d83d6c dxgkrnl!DXGADAPTER::Reset+0xa6
88d83d58 89fbe01d 844f2038 00000000 8ba7e670 dxgkrnl!TdrResetFromTimeout+0x12
88d83d6c 89f94af2 8ba7e670 8ba962c8 88d83dc0 dxgkrnl!VidSchiRecoverFromTDR+0x17
88d83d7c 819afbfd 8ba7e670 88d88680 00000000 dxgkrnl!VidSchiWorkerThread+0x61
88d83dc0 8189a396 89f94a91 8ba7e670 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

WD-20070403-0831.dmp
VIDEO_TDR_TIMEOUT_DETECTED (117)
The display driver failed to respond in timely fashion.
nvlddmkm.sys is the cause

STACK_TEXT:  
88d83b88 89fa5f96 00000000 89fcb640 8459d708 dxgkrnl!TdrUpdateDbgReport+0x68
88d83bf0 89fa6260 00000000 00000001 8459d708 dxgkrnl!TdrCollectDbgInfoStage1+0x656
88d83c0c 89f449a6 00000000 00000102 8ba7e670 dxgkrnl!TdrIsRecoveryRequired+0xcf
88d83c70 89f54d58 8ba7e670 000000c0 00000000 dxgkrnl!VidSchiReportHwHang+0x2e4
88d83c9c 89f54ab8 8ba7e670 00000000 00000000 dxgkrnl!VidSchiCheckHwProgress+0x69
88d83cc8 89f32193 00000002 00000000 8ba7e670 dxgkrnl!VidSchiWaitForSchedulerEvents+0x13f
88d83d58 89f54fac 8ba7e670 00000000 8ba7e670 dxgkrnl!VidSchiScheduleCommandToRun+0xac
88d83d6c 89f94af2 8ba7e670 8ba962c8 88d83dc0 dxgkrnl!VidSchiRun_PriorityTable+0xf
88d83d7c 819afbfd 8ba7e670 88d88680 00000000 dxgkrnl!VidSchiWorkerThread+0x61
88d83dc0 8189a396 89f94a91 8ba7e670 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

WD-20070404-1747.dmp
VIDEO_TDR_TIMEOUT_DETECTED (117)
The display driver failed to respond in timely fashion.
nvlddmkm.sys is the cause

STACK_TEXT:  
8aa8fce4 89ba6121 00000000 89bcb640 9aad66a0 dxgkrnl!TdrUpdateDbgReport+0x68
8aa8fd0c 89ba0592 00000000 866d9bf4 9aad66a0 dxgkrnl!TdrCollectDbgInfoStage2+0x17f
8aa8fd48 89ba62cd 9aad66a0 866d9730 8aa8fd6c dxgkrnl!DXGADAPTER::Reset+0xa6
8aa8fd58 89bbe01d 9aad66a0 00000000 866d9730 dxgkrnl!TdrResetFromTimeout+0x12
8aa8fd6c 89b94af2 866d9730 866e68a0 8aa8fdc0 dxgkrnl!VidSchiRecoverFromTDR+0x17
8aa8fd7c 819afbfd 866d9730 8aa84680 00000000 dxgkrnl!VidSchiWorkerThread+0x61
8aa8fdc0 8189a396 89b94a91 866d9730 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
0
 
johnb6767Commented:
Couple thoughts here.....

Check out this link....http://www.eggheadcafe.com/software/aspnet/29415832/display-driver-nvlddmkm-s.aspx

Alot of chatter on the web about this problem, and also a newer beta driver might resolve it....

Windows Vista 32-bit
http://www.nvidia.com/object/winvista_x86_100.65.html
0
 
johnb6767Commented:
And looking at the stack text, I a wondering if the DirectX Kernel couldnt be playing nicely with the driver, causing the problem....Both installs though, it would seem unlikely, but its a thought....

And this is just for informational purposes.....

Timeout Detection and Recovery of GPUs through WDDM
http://www.microsoft.com/whdc/device/display/wddm_timeout.mspx
0
 
Ryan_RAuthor Commented:
It seems that those drivers may have helped with Vista - although I did get one STOP error when resuming - haven't tried it enough - just thought I'd let you know.

XP is as random as anything. If I move the mouse around while resuming chances are it'll work - if I don't touch it the odds are the monitor will turn off, the PC will wait for 30 secs and then hard reboot (well I think it's a hard one - hard to tell when the monitor is off :])

any thoughts?
0
 
Ryan_RAuthor Commented:
in the nature of this question I've raised the value of it by 6 (you can figure it out)
0
 
johnb6767Commented:
nice even number...  :)

Any chances that this card just had problems from the factory?
or was it previously used.....?


I would seriously lean towards a driver or DX problem more if it was isolated to 1 OS, especially with different platform. Maybe it wasjust bad out of the box...
0
 
Ryan_RAuthor Commented:
I would hate to think that's the case, since these cards are in such short supply.

I've tested the XP theory with the mouse movement - it seems to stand as it failed to resume today when I didn't touch the mouse. I should probably still do a bit of testing on Vista to make sure those drivers fixed it.
Were there any newer drivers for XP than version 77.77? WU didn't find anything.
0
 
johnb6767Commented:
ForceWare Release 90
Version: 93.71
Release Date: November 2, 2006
WHQL Certified
http://www.nvidia.com/object/winxp_2k_93.71.html

ForceWare Release 100
Version: 100.65
Release Date: February 20, 2007
WHQL Driver
http://www.nvidia.com/object/winvista_x86_100.65.html

Actually, I thought we tried updating already...My bad...
 
 

0
 
Ryan_RAuthor Commented:
Yeah I got some for Vista - not XP (downloading them now)

I'm still having a few probs with Vista - same symptoms as XP - if I move the mouse while resuming it'll work, else the monitor will turn off before either a STOP error or hard restart.
0
 
Ryan_RAuthor Commented:
After resuming Vista failed:
-------------------------------------------------------------------------
Problem signature:
  Problem Event Name:      BlueScreen
  OS Version:      6.0.6000.2.0.0.256.1
  Locale ID:      3081

Additional information about the problem:
  BCCode:      116
  BCP1:      848E6F38
  BCP2:      8A0F36C0
  BCP3:      00000000
  BCP4:      00000002
  OS Version:      6_0_6000
  Service Pack:      0_0
  Product:      256_1

Files that help describe the problem:
  C:\Windows\Minidump\Mini041007-01.dmp
  C:\Users\Ryan Richter\AppData\Local\Temp\WER-73078-0.sysdata.xml
  C:\Users\Ryan Richter\AppData\Local\Temp\WER2AE3.tmp.version.txt

Read our privacy statement:
  http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409
-----------------------------------------------------------------------------------------------------
0
 
johnb6767Commented:
I hate to say it, but I am out of ideas......
0
 
Ryan_RAuthor Commented:
thanks for trying
0
 
johnb6767Commented:
Finally got a resolution?
0
 
Ryan_RAuthor Commented:
no

later on i might format and reinstall vista, then use it as my main os
0
 
johnb6767Commented:
Good luck with it. I appreciate the award for effort. Have a great day!!
0

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 14
  • 14
Tackle projects and never again get stuck behind a technical roadblock.
Join Now