Display driver nvlddmkm stopped responding and has successfully recovered.

S

Scarecreaux

Member
Joined
Mar 11, 2018
Posts
7
· OS - Windows 10, 8.1, 8, 7, Vista ? Windows 7
· x86 (32-bit) or x64 ? X64
· What was original installed OS on system? Windows 7
· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? Full retail
· Age of system (hardware) 5-6 years
· Age of OS installation - have you re-installed the OS? 5-6 years and have not been reinstalled

· CPU - i7-3770 @3.40 GHz
· Video Card - Asus NVIDIA Gtx 660 ti
· MotherBoard - ASROCK Z77 Extreme 6
· Power Supply - brand & wattage Strike-X 600 Watts

· System Manufacturer
· Laptop or Desktop? Desktop

==========

Each time I play games (especially ARK), the graphic driver crashes after 30-40 mins. Other games like EuroTruck 2 will last an hour 30 before it crashes.

T\S done:

Uninstalled GPU driver using DDU - Tried numerous drivers from the NVIDIA site.
Ran the memtest for 2 passes and no errors found.
Added a Tdrdelay(20) in the registry.
Set power option to best performance in the control panel
Flashed the GPU bios
Applied new temp paste on both cpu and gpu (cleaned them as well)
Also adjusted the Nvidia 3d settings to best performance.



 

Attachments

All of the dump files show the same bugcheck code:
Code: 
6: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

[COLOR=#ff0000]PAGE_FAULT_IN_NONPAGED_AREA (50)[/COLOR]
Invalid system memory was referenced.  This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: fffff8800db00eb8, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff8800afb39b4, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000002, (reserved)

The automated analysis suggests the culprit is IOMap64.sys:
Code: 
Could not read faulting driver name
[COLOR=#ff0000]Probably caused by : IOMap64.sys[/COLOR] ( IOMap64+19b4 )

which is likely a component of a GPU tweaking utility that came with your graphics card according to this page. I'd recommend uninstalling the utility or at least undoing any overclocking it might be applying to the GPU.

Please let us know whether or not the problem continues after addressing the above.
 
cwsink said:
All of the dump files show the same bugcheck code:
Code: 
6: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

[COLOR=#ff0000]PAGE_FAULT_IN_NONPAGED_AREA (50)[/COLOR]
Invalid system memory was referenced.  This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: fffff8800db00eb8, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff8800afb39b4, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000002, (reserved)

The automated analysis suggests the culprit is IOMap64.sys:
Code: 
Could not read faulting driver name
[COLOR=#ff0000]Probably caused by : IOMap64.sys[/COLOR] ( IOMap64+19b4 )

which is likely a component of a GPU tweaking utility that came with your graphics card according to this page. I'd recommend uninstalling the utility or at least undoing any overclocking it might be applying to the GPU.

Please let us know whether or not the problem continues after addressing the above.
Click to expand...
 
I'm not as technical as the other members here, but I'll do my best to give you what you need.

I did uninstall the ASUS GPU tweak and restarted the PC, but the crashing still occurs. I remember getting a BSOD for IOMap. Should I flash the GPU BIOS again to its original state?

Thanks!
 
So you're no longer getting bugchecks but the display driver is resetting after a timeout detection and recovery event? If so, that can be caused by many different things including a failing GPU. I'd probably try removing the Nvidia GPU and using the system with the onboard graphics if possible. The graphics performance will be terrible but it might tell us whether the Nvidia GPU is to blame.

I'd hold off on flashing the GPU for now.
 
It's sad to think that it might be a failing GPU, but I've already tried using the onboard graphics, and ran a game for 30-45 minutes without a crash. Anything else that I can try?
 
Based on the age it might be worth trying a different PSU. Honestly, though, I think it will end up being that the GPU is failing.
 
I see. Does deleting the IOMap64.sys from C:\Windows\System32\drivers help? :) sorry if it sound like a dumb question. haha
 
It was causing bugchecks but the last one was on March 6th. I'd guess that's the day you uninstalled the software (or shortly afterwards) so it's likely the driver is not loading anymore.
 
I really can't confirm as I'm struggling to fix this issue for some time now, and reinstalled the GPU driver using DDU several times, but I've noticed that after the crash GPU-Z, Msi Afterburner and Speccy will not recognize or detect the driver.

The odd thing is some games takes a while before it crashes and I can still hear the game running on the background.

These are the file locations where the IOMAP are located:

C:\Program Files (x86)\ASUS\UEFI
C:\Windows\System32\drivers
 
I'm not sure which driver you're talking about when you say those tools don't detect it after a crash. The Nvidia driver is getting reset if it's a TDR error so it wouldn't surprise me if those tools get confused when it happens. Or are you talking about IOMap64.sys?

You can run autoruns and look under the Drivers tab to see if IOMap64.sys is getting loaded.
 
Sorry, talking about the GPU driver.

I did run autoruns and I do see IOMAP, not sure if its the same as IOMap 64. Also I get a yellow line for VGPU, eaglex64, synth3dvsc and tsushub. Not sure if it's related, but I just want to mention just in case.

Is there something else that I can try?
 
I'd uninstall MSI Afternburner as I've seen it cause problems on some systems. It might actually be what's loading the IOMap driver. As a last ditch effort I'd try doing a format/reload, loading as little software as necessary, and see if the problems continue. However, since it sounds like it's not an issue with the onboard graphics I doubt that would change anything.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top