Tech Support Forum banner
Status
Not open for further replies.

[SOLVED] Graphics Driver Stopped Responding BSOD

2K views 5 replies 2 participants last post by  Artinz 
#1 ·
· OS - Windows 8.1, 8, 7 or Vista? Windows 7
· x86 (32-bit) or x64 ? x64
· What was the original installed OS on sthe ystem? Yes
· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? OEM
· Approximate age of system (hardware) 2ish years (give or take 4 months)
· Approximate age of OS installation (if you know) Same
· Have you re-installed the OS? No

· CPU Intel Core i7 3610QM
· Video CardNvidia GeForce GTX 675M
· MotherBoard Not sure, assuming some kind of MSI. The computer is an MSI GT70, I couldn't find what came with that, so idk if that helps.
· Power Supply - brand & wattage Same situation as motherboard.

· System Manufacturer MSI
· Exact model number (if laptop, check label on bottom) GT70

Laptop or Desktop? Laptop

I've been getting blue screens on and off with my laptop, and they've been increasing lately. I got a blue screen while playing Dota 2, saying that it was my graphics driver, so I updated the driver and did a Furmark Burn in test, and got another blue screen. I tried it a couple more times after updating various drivers and doing all of the windows update stuff, and still got more blue screens.

Hopefully there is an easy fix. Thanks in advance!
 

Attachments

See less See more
#2 · (Edited)
Re: Graphics Driver Stopped Responding BSOD

Bump. I ran the Driver Verifier and did not get a BSOD, although now I'm not entirely sure I did it correctly. I followed all of the steps, I just saw no prompt or anything about the driver verifier, I have no idea if it worked or not.
 
#3 · (Edited by Moderator)
Re: Graphics Driver Stopped Responding BSOD

Hi,

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)

This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.

Code:
4: kd> .trap 0xfffff8800378b790
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8800378b9b0 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880018106fd rsp=fffff8800378b920 rbp=fffff8800378ba48
 r8=00000000ffffffbc  r9=0000000000000044 r10=0000000000000000
r11=fffffa80107888b0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
NETIO!RtlCopyBufferToMdl+0x1d:
fffff880`018106fd 448b5228        [COLOR=Red]mov     [/COLOR][COLOR=Blue]r10d[/COLOR],dword ptr [[COLOR=Purple]rdx+28h[/COLOR]] ds:00000000`00000028=????????
Failure to move the contents of the rdx register + 28h to the r10d register. NETIO!RtlCopyBufferToMdl+0x1d was part of the instruction which implies that the Network I/O Subsystem was copying a buffer to a memory descriptor list. With this said, a 3rd party software is likely causing network conflicts.

-------------------------

Remove and replace Trend Micro with MSE ASAP as it's very likely causing NETBIOS conflicts:

Trend Micro removal - Using the Trend Micro Diagnostic Toolkit to uninstall the program | Trend Micro

MSE - Microsoft Security Essentials - Microsoft Windows

Regards,

Patrick
 
#5 ·
Re: Graphics Driver Stopped Responding BSOD

VIDEO_TDR_FAILURE (116)

Attempt to reset the display driver and recover from timeout failed.

Code:
7: kd> k
Child-SP          RetAddr           Call Site
fffff880`02b3ca48 fffff880`04929134 nt!KeBugCheckEx
fffff880`02b3ca50 fffff880`048fc867 dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`02b3ca90 fffff880`04928f43 dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`02b3cb40 fffff880`1017603d dxgkrnl!TdrResetFromTimeout+0x23
fffff880`02b3cbc0 fffff800`0356173a dxgmms1!VidSchiWorkerThread+0x101
fffff880`02b3cc00 fffff800`032b68e6 nt!PspSystemThreadStartup+0x5a
fffff880`02b3cc40 00000000`00000000 nt!KxStartSystemThread+0x16
The Direct X MMS scheduled a worker thread which ultimately lead to the display driver crashing and attempting to reset itself back to a stable point with TDR. It failed, therefore the 0x116 bug check was called.

Ensure you have the latest video card drivers. If you are already on the latest video card drivers, uninstall and install a version or a few versions behind the latest to ensure it's not a latest driver only issue. If you have already experimented with the latest video card driver and many previous versions, please give the beta driver for your card a try.

If the above fails, the video card may be faulty.

Regards,

Patrick
 
#6 ·
Re: Graphics Driver Stopped Responding BSOD

I tried multiple versions of video drivers to no avail. I decided to contact the manufacturer to go about replacing the faulty part. I guess you can put this as solved for now, but I'll post again if I get another BSOD after replacing the part.
 
Status
Not open for further replies.
You have insufficient privileges to reply here.
Top