Jump to content


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.


blue screen, crash dump analysis

  • Please log in to reply
No replies to this topic

#1 Valsimot


  • Members
  • 1 posts
  • Local time:12:43 PM

Posted 11 May 2014 - 10:37 AM

Hello Community,

first post - and it's an emergency of sorts. To touch briefly on the backstory, I recently downgraded from Windows 8 to Win 7 Professional as I couldn't stand Metro any more and a 8 year old hard drive failed (I had  backups of my family pictures, so no data loss - backup early, backup often or so the saying goes).

I started setting up a dual-boot with Ubuntu 14, left 50% of my SSD hard drive, but for some reason I couldn't burn the iso. On the first attempt, my DVD ROM had an E/A error, the second one it couldn't verify, then the drive vanished from my hardware configuration completely. This is when I thought, I should've installed the main board drivers. So I started doing that. I downloaded all drivers for the gigabyte z87x ud4h and started installing them one by one. During mb_driver_chipset_intel_8series.exe did its thing, I got a blue screen, restart, mouse and keyboard gone. I redid the setup successfully (? - at least there were no more bluescreens) and installed the rest of the drivers. Then I looked at the errors.


Here's the basic system information.


OS Name Microsoft Windows 7 Professional
Version 6.1.7601 Service Pack 1 Build 7601
Additional OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name HOME - PC
System Manufacturer Gigabyte Technology Co. , Ltd. .
System model Z87X - UD4H
System Type x64 -based PC
Processor Intel (R ) Core ( TM) i5- 4670K CPU@3.40GHz , 3401 MHz , 4 core (s ) , 4 logical (r ) processor (s)
BIOS-Version/-Datum American Megatrends Inc. F5 , 16/05/2013
SMBIOS Version 2.7
Windows directory C: \ Windows
System Directory C : \ Windows \ system32
Boot Device \ Device \ HarddiskVolume4
Locale Germany
Hardware Abstraction Layer Version = " 6.1.7601.17514 "
Username home- pc \ ****
Time zone Central European Summer Time
Installed Physical Memory (RAM) 8.00 GB
Total Physical Memory 7.89 GB
Available Physical Memory 5.45 GB
Total Virtual Memory 15.8 GB
Available Virtual Memory 13.1 GB
Paging file size 7.89 GB
Page File C : \ pagefile.sys


The system information/components/problematic now devices gives me this:


Standardkeyboard (PS/2)    ACPI\PNP0303\4&34575EFB&0    This device is either not present, not working properly, or does not have all the drivers installed.


Which is about right: If I connect my mouse via a USB->PS/2 dongle to save a USB port, it won't work. The keyboard works fine, but only when windows is loaded, I can't access my BIOS anymore.

Next the minidump. The event manager stated a critical error:


0x00000116 (0xfffffa80083db4e0, 0xfffff8800f42fe20, 0x0000000000000000, 0x0000000000000002)


Here's the Microsoft Debugging Tool summary and analysis:


Microsoft ® Windows Debugger Version 6.3.9600.17029 AMD64
Copyright © Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\****\Downloads\2014-05-11-bluescreen\051114-18985-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*c:\symbols*http://msdl.microsoft.com/downloads/symbols
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/downloads/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`0304f000 PsLoadedModuleList = 0xfffff800`032926d0
Debug session time: Sun May 11 16:04:14.539 2014 (UTC + 2:00)
System Uptime: 0 days 0:04:22.507
Loading Kernel Symbols

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

Loading User Symbols
Loading unloaded module list
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa80083db4e0, fffff8800f42fe20, 0, 2}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+153e20 )

Followup: MachineOwner

1: kd> !analyze -v
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

Attempt to reset the display driver and recover from timeout failed.
Arg1: fffffa80083db4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800f42fe20, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000002, Optional internal context dependent data.

Debugging Details:

OVERLAPPED_MODULE: Address regions for 'nvlddmkm' and 'nvlddmkm.sys' overlap

fffff880`0f42fe20 803dc20a750000  cmp     byte ptr [nvlddmkm+0x8a48e9 (fffff880`0fb808e9)],0






ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre

fffff880`0a241888 fffff880`042ed140 : 00000000`00000116 fffffa80`083db4e0 fffff880`0f42fe20 00000000`00000000 : nt!KeBugCheckEx
fffff880`0a241890 fffff880`042ece4a : fffff880`0f42fe20 fffffa80`083db4e0 fffffa80`07911d50 fffffa80`07fdf010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`0a2418d0 fffff880`04393f13 : fffffa80`083db4e0 00000000`00000000 fffffa80`07911d50 fffffa80`07fdf010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`0a241900 fffff880`043bdcf1 : 00000000`ffffffff 00000000`00004132 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`0a2419e0 fffff880`043bc437 : 00000000`00000102 00000000`00000006 00000000`00004132 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`0a241a10 fffff880`0438f2d2 : ffffffff`ff676980 fffffa80`07fdf010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`0a241ab0 fffff880`043bbff6 : 00000000`00000000 fffffa80`09b7f800 00000000`00000080 fffffa80`07fdf010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`0a241bc0 fffff800`033612ea : fffff8a0`fffffc32 fffffa80`09ce7640 fffffa80`06cec5a0 fffff8a0`00000002 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`0a241c00 fffff800`030b58e6 : fffff880`031d7180 fffffa80`09ce7640 fffff880`031e1fc0 fffffa80`073a4970 : nt!PspSystemThreadStartup+0x5a
fffff880`0a241c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16

STACK_COMMAND:  .bugcheck ; kb

fffff880`0f42fe20 803dc20a750000  cmp     byte ptr [nvlddmkm+0x8a48e9 (fffff880`0fb808e9)],0

SYMBOL_NAME:  nvlddmkm+153e20

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys


FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys


FAILURE_ID_HASH_STRING:  km:x64_0x116_image_nvlddmkm.sys

FAILURE_ID_HASH:  {1f9e0448-3238-5868-3678-c8e526bb1edc}

Followup: MachineOwner



I can't really say what went wrong, but I still can't burn anything with my DVD drive. Here's the system info about it


Drive G:
Description CD-ROM drive
Charged media Yes
Media Type DVD Writer
Name HL-DT-ST DVD-RAM GH22NS30 SCSI CdRom Device
Manufacturer (Standard CD-ROM drives)
Status OK
Transfer rate 335.06 KB / s
SCSI target ID 1
PNP Device ID SCSI \ CDROM & VEN_HL-DT-ST & PROD_DVD-RAM_GH22NS30 \ 5 & 118F0ADD & 0 & 000100
Driver c: \ windows \ system32 \ drivers \ cdrom.sys (6.1.7601.17514, 144.00 KB (147,456 bytes), 08.05.2014 19:49)

LG offers firmware, but I can't install it as the drive is not found.

There seems to be a problem with nvlddmkm.sys, but I'm a complete newbie with all things tech so I can't really say what to do. The graphics drivers are up to date. Here's the system information/components/display


Name Intel ( R) HD Graphics 4600
PNP Device ID PCI \ VEN_8086 & DEV_0412 & REV_06 & SUBSYS_D0001458 \ 3 & 11583659 & 0 & 10
Adapter Type Intel ( R) HD Graphics Family , Intel Corporation compatible
Adapter Description Intel ( R) HD Graphics 4600
Adapter RAM ( 2,080,374,784 ) bytes
Installed driver igdumdim64.dll , igd10iumd64.dll , igd10iumd64.dll , igdumdim32 , igd10iumd32 , igd10iumd32
Driver version
Inf file oem9.inf (Section iHSWD_w7 )
Color planes not available
Color Table Entries 4294967296
Resolution 1920 x 1080 x 60 Hz
Bits / pixel 32
Memory address 0xDE400000 - 0xDE7FFFFF
Memory address 0xC0000000 - 0xCFFFFFFF
I / O port 0x0000FF80 - 0x0000FFBF
IRQ Channel IRQ 4294967294
Driver c : \ windows \ system32 \ drivers \ igdkmd64.sys ( , 4.03 MB ( 4,221,440 bytes ) , 01/25/2014 01:22 )

Name NVIDIA GeForce GTX 560 Ti
PNP Device ID PCI \ VEN_10DE & DEV_1200 & SUBSYS_15673842 & ​​REV_A1 \ 4 & 1286464 & 0 & 0008
Adapter Type GeForce GTX 560 Ti, NVIDIA compatible
Adapter Description NVIDIA GeForce GTX 560 Ti
Adapter RAM 1.00 GB ( 1,073,741,824 bytes )
Installed driver nvd3dumx.dll , nvwgf2umx.dll , nvwgf2umx.dll , nvd3dum , nvwgf2um , nvwgf2um
Driver version
Inf file oem4.inf ( Section030 section )
Color planes not available
Color Table Entries 4294967296
Resolution 1280 x 1024 x 60 Hz
Bits / pixel 32
Memory address 0xDC000000 - 0xDDFFFFFF
Memory address 0xD0000000 - 0xDE0FFFFF
Memory address 0xD8000000 - 0xDBFFFFFF
I / O port 0x0000E000 - 0x0000EFFF
IRQ Channel IRQ 16
I / O port 0x000003B0 - 0x000003BB
I / O port 0x000003C0 - 0x000003DF
Memory address 0xA0000 - 0xBFFFF
Driver c : \ windows \ system32 \ drivers \ nvlddmkm.sys ( , 12.12 MB ​​( 12,708,128 bytes) 08.05.2014 12:55 )


I upgraded the graphics drivers to 337.50 beta, although I had to do it twice. The first time (reinstalling every part of the Nvidia drivers) my system went black and I had to restart and reinitiate the install. Unfortunately, I still can't get usb keyboard/mouse during boot back to work again. Any hints how to proceed are highly appreciated.

best regards,




update 1: googletranslated the info above to EN

Edited by Valsimot, 11 May 2014 - 01:19 PM.

BC AdBot (Login to Remove)


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users