altibase 常见问题及解决方式_百度文库
两大类热门资源免费畅读
续费一年阅读会员，立省24元！
altibase 常见问题及解决方式
上传于||文档简介
&&a​l​t​i​b​a​s​e​常​见​问​题​及​解​决​方​式
阅读已结束，如果下载本文需要使用2下载券
想免费下载本文？
定制HR最喜欢的简历
下载文档到电脑，查找使用更方便
还剩18页未读，继续阅读
定制HR最喜欢的简历
你可能喜欢手机签到经验翻倍！快来扫一扫！
显示器驱动程序已停止响应并且已成功恢复，求大神解决！
41019浏览 / 43回复
的的新机，WIN7旗舰版，GTX650,之前运行都很好， 前后，机器在开机状态突然右下角提示：程序已停止响应并且已成功恢复。最后蓝屏，紧接着自动重启。安全模式下删除驱动后，可以正常运行，但是只要装上驱动，又出现这样的问题，尝试换过N种驱动，都不见效，系统重装之后没有出现这样的问题，但是当我调整了界面个性化，选择了Aero主题桌面后，立刻又回到之前出现问题的状况，真是立竿见影啊！显卡退回检修，送回来说没问题，个人怀疑，WIN7更新后出现这样的问题，驱动程序不兼容导致，现在求大神，同样遇到这样问题的人指导！求一行家指导交流，谢谢！
如果你安装有“鲁大师”，先将其切底清除，如无效果再去考虑其他方法，我就让这个“鲁大师”搞得不得安宁！！！
以下是微软官方给出的一些解释:
Introduction
One of the most common stability problems in graphics is when the system appears completely "frozen" or "hung" while processing an end-user command or operation. Users generally wait a few seconds and then reboot the system by pressing the Power button. Usually the graphics processing unit (GPU) is "busy" processing intensive graphical operations, typically during gameplay. This results in nothing being updated on the screen, thus appearing to the user that the system is frozen.
This paper briefly describes the timeout detection and recovery (TDR) process in Windows Vista. It also documents the registry controls so developers can easily debug problems.
What's New for Windows Vista SP1
Changes for Windows Vista SP1 to improve user experience in cases of frequent and rapidly occurring GPU hangs. New registry keys to support these changes.
Timeout Detection and Recovery
Windows Vista attempts to detect these problematic hang situations and recover a responsive desktop dynamically. In this process, the Windows Display Driver Model (WDDM) driver is reinitialized and the GPU is reset. No reboot is necessary, which greatly enhances the user experience. The only visible artifact from the hang detection to the recovery is a screen flicker, which results from resetting some portions of the graphics stack, causing a screen redraw. Some older Microsoft
applications may render to a black screen at the end of this recovery. The end user would have to restart these applications.
The following is a brief overview of the TDR process:
Timeout detection: The Video Scheduler component of the Windows Vista graphics stack detects that the GPU is taking more than the permitted quantum time to execute the particular task and tries to preempt this particular task. The preempt operation has a "wait" timeout—the actual "TDR timeout." This step is thus the "timeout detection" phase of the process. The default timeout period in Windows Vista is 2 seconds. If the GPU cannot complete or preempt the current task within the TDR timeout, then the GPU is diagnosed as hung.
Preparation for recovery: The operating system informs the WDDM driver that a timeout has been detected and it must reset the GPU. The driver is told to stop accessing memory and should not
hardware after this time. The operating system and the WDDM driver collect hardware and other state information that could be useful for post-mortem diagnosis.
Desktop recovery: The operating system resets the appropriate state of the graphics stack. The Video Memory Manager component of the graphics stack purges all allocetions from video memory. The WDDM driver resets the GPU hardware state. The graphics stack takes the final actions and restores the desktop to the responsive state. As mentioned earlier, some older DirectX applications may now render just black, and the user may be required to restart these applications. Well-written DirectX 9Ex and DirectX 10 applications that handle "Device Remove" continue to work correctly. The application must release and then recreate its Microsoft Direct3D device and all of its objects. DirectX application programmers can find more information in the Windows SDK.
Windows Vista SP1 Update
Minor changes were made in Windows Vista SP1 to improve the user experience in cases of frequent and rapidly occurring GPU hangs. Repetitive GPU hangs indicate that the graphics hardware has not recovered successfully. In these instances, the system must be shut down and restarted to fully reset the graphics hardware. If the operating system detects that six or more GPU hangs and subsequent recoveries occur within 1 minute, then the following GPU hang is treated as a system bug check.
Error Messaging
Throughout the process of GPU hang detection and recovery, the desktop is unresponsive and thus unavailable to the user. In the final stages of recovery, a brief screen
occurs that is similar to the one when the screen resolution is changed. After the desktop has been successfully recovered, the following informational message appears to the user.
The message is also logged in the Windows Vista Event Viewer. Diagnosis information is collected in the form of a debug report that is returned to Microsoft through the Online Crash Analysis (OCA) mechanism if the user opts in to provide feedback.
Registry Keys
The following registry keys are documented for testing purposes only. These registry keys should not be manipulated by any applications outside targeted testing or debugging.
The TDR-related registry keys are located under HKLMSystemCurrentControlSetControlGraphicsDrivers.
TdrLevel: REG_DWORD. The initial level of recovery. The possible values are:
TdrLevelOff (0). – Detection disabled.
TdrLevelBugcheck (1) – Bug check on detected timeout, for example, no recovery.
TdrLevelRecoverVGA (2) – Recover to VGA (not implemented).
TdrLevelRecover(3) – Recover on timeout. This is the default value.
TdrDelay: REG_DWORD. The number of seconds that the GPU is allowed to delay the preempt request from the scheduler. This is effectively the timeout threshold. The default value is 2.
TdrDdiDelay: REG_DWORD. The number of seconds that the operating system allows threads to leave the driver. After a specified time, the operating system bug checks the system with the code VIDEO_TDR_FAILURE (0x116). The default value is 5.
TdrTestMode: REG_DWORD: Internal test usage.
TdrDebugMode: REG_DWORD: The debugging-related behavior of the TDR process.
TDR_DEBUG_MODE_OFF (0) breaks to kernel debugger before the recovery to allow investigation of the timeout.
TDR_DEBUG_MODE_IGNORE_TIMEOUT (1) ignores any timeout.
TDR_DEBUG_MODE_RECOVER_NO_PROMPT (2) recovers without break into the debugger. This is the default value.
TDR_DEBUG_MODE_RECOVER_UNCONDITIONAL (3) recovers even if some recovery conditions are not met (for example, recovers on consecutive timeouts).
TdrLimitTime: REG_DWORD (Windows Vista SP1 and later versions only): The default time within which a "TdrLimitCount" number of TDRs are allowed without crashing the system.
TdrLimitCount: REG_DWORD (Windows Vista SP1 and later versions only): The default number of TDRs (0x117) that are allowed in "TdrLimitTime" without crashing the system.
Next Steps
Graphics hardware vendors:
Ensure that graphics operations (that is, DMA buffer completion) take no more than 2 seconds in end-user scenarios such as productivity and gameplay.
Graphics software vendors:
Ensure that the DirectX graphics application does not run at a low frames per second (FPS) rate. As the FPS decreases, the likelihood of the GPU getting reset increases. If the application is running at 10 FPS or lower and a complex graphics operation is about to start, then a flush can be inserted.
For running benchmark tests on low-end GPUs, use the aforementioned registry keys that control the TDR timeout. Remember that they should not be used in production systems because it would affect overall system stability and robustness. Use these keys only as a final solution.
System manufacturers:
Work with the graphics hardware vendor to diagnose the TDR debug reports.
Remember that any system that uses the aforementioned TDR registry keys to change the default values is a Windows Logo Program violation.
dewdew907 发表于
我也是这个问题 我的显卡是6950
大哥啊 我也是啊
建议超频软件降低核心频率试试
这个问题无解，我被摧残了半年，试光了网上的所有方法。不过还有一招没试，因为是（核显+独显），还没去检查硬件。
我之前也出现这个问题，我的原因是因为装了一个软件，冲突了。。我卸掉之后就没事了。。希望对LZ有帮助
装的什么软件？
问题。。刷评论了··
我之前也出现这个问题，我的原因是因为装了一个软件，冲突了。。我卸掉之后就没事了。。希望对LZ有帮助
我之前也出现这个问题，我的原因是因为装了一个软件，冲突了。。我卸掉之后就没事了。。希望对LZ有帮助
我之前也出现这个问题，我的原因是因为装了一个软件，冲突了。。我卸掉之后就没事了。。希望对LZ有帮助
我之前也出现这个问题，我的原因是因为装了一个软件，冲突了。。我卸掉之后就没事了。。希望对LZ有帮助
我之前也出现这个问题，我的原因是因为装了一个软件，冲突了。。我卸掉之后就没事了。。希望对LZ有帮助
我之前也出现这个问题，我的原因是因为装了一个软件，冲突了。。我卸掉之后就没事了。。希望对LZ有帮助
我之前也出现这个问题，我的原因是因为装了一个软件，冲突了。。我卸掉之后就没事了。。希望对LZ有帮助
我之前也出现这个问题，我的原因是因为装了一个软件，冲突了。。我卸掉之后就没事了。。希望对LZ有帮助
我之前也出现这个问题，我的原因是因为装了一个软件，冲突了。。我卸掉之后就没事了。。希望对LZ有帮助
我之前也出现这个问题，我的原因是因为装了一个软件，冲突了。。我卸掉之后就没事了。。希望对LZ有帮助
建议看看这个帖子，个人认为分析得很好：
同问，强烈蛋疼！！！影响心情，影响工作！
支持键盘翻页 ( 左右 )&
您需要登录后才可以回帖&&&|&&&&&
用户名/注册邮箱/注册手机号
其他第三方号登录