What i have tried so far:
1. Install older version display driver (back to latest now)
2. Reinstall hardware graphic card and its power connector.
3. Install latest version of new Giga adapter
4. Uninstall onboard network adapter in Device Manager and disabled in BIOS
5. Ask for help in Safe Mode~
This bugcheck indicates an attempt to reset the display driver has failed within the allocation time interval.
When a TDR (Timeout Detection Recovery) is successful it comes up with the notification in the bottom right corner, when it's unsuccessful it bugchecks.
1: kd> [COLOR=Green]u fffff8800fe2a530[/COLOR]
nvlddmkm+0x14f530:
[COLOR=Green]fffff880`0fe2a530[/COLOR] 48ff25d9817100 [COLOR=Purple]jmp[/COLOR] qword ptr [nvlddmkm+0x867710 (fffff880`10542710)]
fffff880`0fe2a537 cc int 3
fffff880`0fe2a538 e94fa2f0ff jmp nvlddmkm+0x5978c (fffff880`0fd3478c)
fffff880`0fe2a53d cc int 3
fffff880`0fe2a53e cc int 3
fffff880`0fe2a53f cc int 3
fffff880`0fe2a540 48ff2589817100 jmp qword ptr [nvlddmkm+0x8676d0 (fffff880`105426d0)]
fffff880`0fe2a547 cc int 3
The faulting instruction was a jmp command which is used to transfer the flow of execution, this is done by changing to a different instruction pointer register.
You have Driver Verifier enabled...
I take it you did it yourself?
This hasn't found any violations at all which leans me towards a bad GPU.
Are you doing anything in particular when it crashes?
Download and run Furmark for around 30 minutes.
Monitor your temperatures, your GPU temp is recorded in the top left corner.
If it starts to overheat stop the test.
Watch for any artifacts or distortions which indicate a failing GPU.
If you can roll back to 314.22 as a test as it's the most stable Nvidia driver version which we mainly use for testing to see if the driver is causing the problems, it's not practical for use when gaming or other video intensive work as it's outdated and the performance can decrease compared to newer versions.
Yes, i have tried Driver Verifier before this thread but now it is disabled
For the Furmark, i did a "Burn-in test" under 1920x1080 & no MSAA
I don't know why the program crashed when i press F9 (screenshot hotkey)
(F1 & F3 are okay)
I press PrtScr and save screen capture by mspaint.exe in the second test (attachment)
[9 avg. FPS ... quite low compared with normal gameplay]
Also, the condition changed a bit.
No BSOD or system crash occur today, but in replacement,2-second system delay happen 2 times every minute. By observing the movement of mouse cursor and a sudden increase (+2X%) of CPU usage in Task Manager.
Should i redo the pressure test under 314.22(Geforce 337.88 now)?
More details on my story:
In the beginning, the "Display driver stopped..." message shown when I started a game.
Afterwards, the monitor blinks with this message just after bootup and login continuously and come by system hang.
Sometimes, it even shows "no signal" after the Windows loading screen.
It looks like a network driver for either your wireless network card or your Ethernet controller, depending on which you are using.
ndis.sys is the Network Driver Interface Specification which provides an Application Programming Interface for Network Interface Cards.
Ndis is a library of functions which hides the complexity of the hardware device and provides a standard interface between the level 3 network protocol drivers and the mac hardware drivers.
The solution should be to update your network driver for your device and see if it improves the problem.
Status
Not open for further replies.
You have insufficient privileges to reply here.
Related Threads
?
?
?
?
?
Tech Support Forum
4.7M posts
957.9K members
Since 2002
A forum community dedicated to tech experts and enthusiasts. Come join the discussion about articles, computer security, Mac, Microsoft, Linux, hardware, networking, gaming, reviews, accessories, and more!