Bug check 0x00000116
Can anyone tell me what may be causing this bsod?
Thanks in advance
http://sdrv.ms/1gUFj3U
SHesser
This one crash was related to your 4 year old video driver. I would start by updating it to current. If this is a laptop it may also be heat.
"It's not a true crash, in the sense that the Blue Screen was initiated only because the combination of video driver and video hardware was being unresponsive, and not because of any synchronous processing exception".
Since Vista, the "Timeout Detection and Recovery" (TDR) components of the OS video subsystem have been capable of doing some truly impressive things to try to recover from issues which would have caused earlier OS's like XP to crash.
As a last resort, the TDR subsystem sends the video driver a "please restart yourself now!" command and waits a few seconds.
If there's no response, the OS concludes that the video driver/hardware combo has truly collapsed in a heap, and it fires off that stop 0x116 BSOD.
If playing with video driver versions hasn't helped, make sure the box is not overheating.
Try removing a side panel and aiming a big mains fan straight at the motherboard and GPU.
Run it like that for a few hours or days - long enough to ascertain whether cooler temperatures make a difference.
If so, it might be as simple as dust buildup and subsequently inadequate cooling.
I would download cpu-z and gpu-z (both free) and keep an eye on the video temps
For more information please read this blog http://captaindbg.com/bug-check-0x116-video_tdr_error-troubleshooting-tips/
http://msdn.microsoft.com/en-us/library/windows/hardware/ff557263%28v=vs.85%29.aspx
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18247.x86fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0x82e4b000 PsLoadedModuleList = 0x82f944d0
Debug session time: Fri Feb 7 15:58:04.589 2014 (UTC - 5:00)
System Uptime: 0 days 2:47:15.306
Loading Kernel Symbols
BugCheck 116, {86129510, 92e449b0, 0, c}
*** WARNING: Unable to verify timestamp for igdkmd32.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd32.sys
Probably caused by : igdkmd32.sys ( igdkmd32+119b0 )
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: 86129510, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: 92e449b0, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 00000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000c, Optional internal context dependent data.
Debugging Details:
FAULTING_IP:
igdkmd32+119b0
92e449b0 55 push ebp
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0x116
PROCESS_NAME: SpotifyHelper.
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
STACK_TEXT:
905cb65c 933bd0ff 00000116 86129510 92e449b0 nt!KeBugCheckEx+0x1e
905cb680 933b1ae6 92e449b0 00000000 0000000c dxgkrnl!TdrBugcheckOnTimeout+0x8d
905cb6a4 920bc92c 00129510 00000000 905cb768 dxgkrnl!TdrIsRecoveryRequired+0xb8
905cb71c 920e3d55 fffffcfb 0009d053 00000000 dxgmms1!VidSchiReportHwHang+0x3c0
905cb748 920cd471 886fa008 905cb768 00000102 dxgmms1!VidSchWaitForCompletionEvent+0x16f
905cb7e0 920ceaeb bb03afe0 00000002 00000000 dxgmms1!VIDMM_GLOBAL::xWaitForAllEngines+0x181
905cb7f8 920de881 b50732e0 88525948 85d7fab8 dxgmms1!VIDMM_GLOBAL::WaitForAllPagingEngines+0x1b
905cb810 8301a603 86105130 85d7fab8 905cb9ec dxgmms1!VIDMM_MEMORY_SEGMENT::RotateCopyCallback+0x87
905cb93c 920d7dcb 08410000 905cb984 00000000 nt!MmRotatePhysicalView+0x59c
905cb98c 920dee13 bb193580 00000002 00000000 dxgmms1!VIDMM_PROCESS_HEAP::Rotate+0xe1
905cba78 920c8ac7 b50732e0 00000001 88922838 dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+0x4b5
905cba9c 920cede8 88922840 00000000 88922824 dxgmms1!VIDMM_GLOBAL::EvictAllAllocationInList+0x2f
905cbac0 920d08b7 00000000 00000000 00000000 dxgmms1!VIDMM_GLOBAL::EvictAllReclaimedAllocation+0x2a
905cbbb8 920e7988 9d1fff00 00000000 89697e40 dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x925
905cbd18 920e8279 8970cf08 89721008 905cbd3c dxgmms1!VidSchiSubmitRenderCommand+0x1c0
905cbd28 920e8516 8970cf08 82e81b99 886fa008 dxgmms1!VidSchiSubmitQueueCommand+0x61
905cbd3c 920e85bd 886fa008 00000000 88525948 dxgmms1!VidSchiRun_PriorityTable+0x24
905cbd50 8305413d 886fa008 a12eae73 00000000 dxgmms1!VidSchiWorkerThread+0x7f
905cbd90 82efb559 920e853e 886fa008 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
igdkmd32+119b0
92e449b0 55 push ebp
SYMBOL_NAME: igdkmd32+119b0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: igdkmd32
IMAGE_NAME: igdkmd32.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a01d354
FAILURE_BUCKET_ID: 0x116_IMAGE_igdkmd32.sys
BUCKET_ID: 0x116_IMAGE_igdkmd32.sys
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x116_image_igdkmd32.sys
Wanikiya and Dyami--Team Zigzag
Similar Messages
-
Windows 8.1 rebooting overnight with a bug check
Windows 8.1 is rebooting overnight with a bug check in the system logs.
Event files saved:
https://onedrive.live.com/redir?resid=7DE1274A30A8AE63!1788&authkey=!AGhpLBq-8hDqCok&ithint=file%2c.zip
I also tried verifier to check out device drivers but could not figure out how to use it. I got it configured and started, but did not know what to do once the computer rebooted.... Sounds like I need to download a windows debugger and
so I thought I would start with the event log files. Any link on how to interpret the even logs, dump or mini dump files?
Thanks,
RossHi,
According to the Event Log:
Session "ReadyBoot" stopped due to the following error: 0xC0000188
After that:
The previous system shutdown at 7:07:39 PM on 6/3/2014 was unexpected.
This problem probably caused by ReadyBoot problem, While you needn't worry about it,
The logging of this error will not affect the operation of your computer. ReadyBoot is used by the ReadyBoost service that optimizes the boot time of your computer to a minimum.
You can refer to the link below for more details about this error:
http://support.microsoft.com/kb/2001347
In addition, I found another error message in your event log:
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000019 (0x0000000000000020, 0xffffc0016d9657f0, 0xffffc0016d966040, 0x000000000585000a). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 060314-18953-01.
If you still need assistance about this problem, please upload the memory.dmp file and share with us. We would help you try to analysize this log to find further reason of this problem.
Roger Lu
TechNet Community Support -
Odd Bug Check Event ID 18 - BCCode 124; Can anyone help?
Hello,
I understand that each bug check is different even if the codes are the same due to different real world problems but I'm stumped, granted I don't know too much. Hence I am here. I'm getting a BSOD every time I let my computer idle for 10 and half minutes.
Like clockwork it will blue screen. However, whenever I am using it, it won't blue screen at all. I have even used my computer nonstop for 13 hours and no BSOD, leave it for 10 minutes and you guessed it, blue screen.
So here's the info...
Problem signature:
Problem Event Name: BlueScreen
OS Version:
6.1.7601.2.1.0.768.3
Locale ID:
1033
Additional information about the problem:
BCCode:
124
BCP1:
0000000000000000
BCP2:
FFFFFA800CDCC028
BCP3:
00000000BF800000
BCP4:
0000000000200401
OS Version:
6_1_7601
Service Pack:
1_0
Product:
768_1
Not too helpful right? Alright, so I have updated the BIOS to latest version, all drivers are up to date, everything is as up to date as I can get it as (as far as I can perceive). I am still getting bug checks when it idles for 10 minutes. So I do a bug
check analysis...
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa800ccf7028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000bf800000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000200401, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
BUGCHECK_STR: 0x124_GenuineIntel
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: ubssrv_oc_only
CURRENT_IRQL: f
ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
STACK_TEXT:
fffff880`033dfa58 fffff800`0302da3b : 00000000`00000124 00000000`00000000 fffffa80`0ccf7028 00000000`bf800000 : nt!KeBugCheckEx
fffff880`033dfa60 fffff800`031f0463 : 00000000`00000001 fffffa80`0c484ea0 00000000`00000000 fffffa80`0c484ef0 : hal!HalBugCheckSystem+0x1e3
fffff880`033dfaa0 fffff800`0302d700 : 00000000`00000728 fffffa80`0c484ea0 fffff880`033dfe30 fffff880`033dfe00 : nt!WheaReportHwError+0x263
fffff880`033dfb00 fffff800`0302d052 : fffffa80`0c484ea0 fffff880`033dfe30 fffffa80`0c484ea0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`033dfc50 fffff800`0302cf0d : 00000000`00000004 00000000`00000001 fffff880`033dfeb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`033dfc90 fffff800`03020e88 : 00000000`00000000 00000000`00000010 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`033dfcc0 fffff800`030d84ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`033dfcf0 fffff800`030d8313 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`033dfe30 fffff800`030d07b8 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`09e9f638 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!memcpy+0x208
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: GenuineIntel
IMAGE_NAME: GenuineIntel
DEBUG_FLR_IMAGE_TIMESTAMP: 0
IMAGE_VERSION:
FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE
BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0x124_genuineintel_processor_mae
FAILURE_ID_HASH: {addebe90-d04a-b9c9-a39c-2531fe75dd4e}
Followup: MachineOwner
I should also mention that I checked hard drive for bad sectors and ram for any errors using 10 passes with Memcheck86 and nothing bad to report. If anyone can help me out with this that would be great! I can provide as many minidump files as you need, if
need be.
Note: I have previously tried resolving this issue and rather than GenuineIntel being the probable cause, it used to show netio.sys as the culprit. However, I tried using a registry cleaner and of course it wiped all previous minidumps that showed netio.sys
as probable source of error and now it just shows GenuineIntel. Interesting? Sorry I can't provide those "previous" minidump files accusing netio.sys, because the registry cleaner wiped them, but I can provide current minidump files.
Thanks for any help!!Hi,
In order to assist you, we will need the .DMP files to analyze what exactly occurred at the time of the crash, etc.
If you don't know where .DMP files are located, here's how to get to them:
1. Navigate to the %systemroot%\Minidump folder.
-- %systemroot% is the environment variable for your Windows directory. For example, C:\Windows.
2. Copy any and all .DMP files in the Minidump folder to your Desktop, create a new folder on the Desktop to put these .DMP files in, and then zip the folder. You can then either use a 3rd party tool such as 7-Zip/Winrar, or you can use Windows'
default method of zipping folders.
Compress and uncompress files (zip files).
Please note that any "cleaner" programs such as TuneUpUtilities, CCleaner, etc, by default will delete .DMP files upon use. With this said, if you've run such software, and your Minidump folder is empty, you will need
to allow the system to crash once again to generate a crash dump.
3. Upload the .ZIP containing the .DMP files to Onedrive or a hosting site of your choice and paste in your reply.
Preferred sites: Onedrive, Mediafire, Dropbox, etc. Nothing with wait-timers, download managers, etc.
4 (optional): The type of .DMP files located in the Minidump folder are known as Small Memory Dumps. In %systemroot% there will be what is known as a Kernel Memory Dump (if your system is set to generate). It is labeled MEMORY.DMP. The difference
between Small Memory Dumps and Kernel Memory Dumps in the simplest definition is a Kernel Memory Dump contains
much more information at the time of the crash, therefore allowing further debugging of your issue. If your upload speed permits it, and you aren't going against any strict bandwidth and/or usage caps, etc, the Kernel Memory Dump is
the best choice. Do note that Kernel Memory Dumps are much larger
in size due to containing much more info, which is why I mentioned upload speed, etc.
If you are going to use Onedrive but don't know how to upload to it, please visit the following:
Upload photos and files to Onedrive.
After doing that, to learn how to share the link to the file if you are unaware, please visit the following link -
Share files and folders and change permissions and view 'Get a link'.
If your computer is not generating .DMP files, please do the following:
1. Start > type %systemroot% which should show the Windows folder, click on it. Once inside that folder, ensure there is a Minidump folder created. If not, CTRL-SHIFT-N to make a New Folder and name it Minidump.
2. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Performance > Settings > Advanced > Ensure there's a check-mark for 'Automatically manage paging file size for
all drives'.
3. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Startup and Recovery > Settings > System Failure > ensure there is a check mark next to 'Write an event to the
system log'.
Ensure Small Memory Dump is selected and ensure the path is %systemroot%\Minidump.
4. Double check that the WERS is ENABLED:
Start > Search > type services.msc > Under the name tab, find Windows Error Reporting Service > If the status of the service is not Started then right click it and select Start. Also ensure that under Startup Type it is set to Automatic rather than
Manual. You can do this by right clicking it, selecting properties, and under General selecting startup type to 'Automatic', and then click Apply.
If you cannot get into normal mode to do any of this, please do this via Safe Mode.
Regards,
Patrick
“Be kind whenever possible. It is always possible.” - Dalai Lama -
Windows 2003 Memory Dump - Bug check Analysis attached
Hi all
I recently have had a Windows 2003 Standard with SP2 server crash with a memory dump
I have used WinDBG to read the file and output below
can anyone shed any light on the faults, or point me in the right direction?
* Bugcheck Analysis
KERNEL_MODE_EXCEPTION_NOT_HANDLED (8e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 8081c630, The address that the exception occurred at
Arg3: b7487c30, Trap Frame
Arg4: 00000000
Debugging Details:
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
nt!IoGetAttachedDevice+c
8081c630 8b4810 mov ecx,dword ptr [eax+10h]
TRAP_FRAME: b7487c30 -- (.trap 0xffffffffb7487c30)
ErrCode = 00000000
eax=000007f6 ebx=85e76068 ecx=000007f6 edx=00000000 esi=85e76068 edi=89d42020
eip=8081c630 esp=b7487ca4 ebp=b7487ca4 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt!IoGetAttachedDevice+0xc:
8081c630 8b4810 mov ecx,dword ptr [eax+10h] ds:0023:00000806=????????
Resetting default scope
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: DocTransport.ex
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre
LAST_CONTROL_TRANSFER: from 8082db20 to 80827f7d
STACK_TEXT:
b74877fc 8082db20 0000008e c0000005 8081c630 nt!KeBugCheckEx+0x1b
b7487bc0 8088c12a b7487bdc 00000000 b7487c30 nt!KiDispatchException+0x3a2
b7487c28 8088c0de b7487ca4 8081c630 badb0d00 nt!CommonDispatchException+0x4a
b7487ca4 8081c7e1 89d42020 b7487d64 00000000 nt!KiExceptionExit+0x186
b7487cb8 808f44c7 85e76068 b7487d64 08a9ea50 nt!IoGetRelatedDeviceObject+0x63
b7487d38 8088b658 00001e20 00000000 00000000 nt!NtReadFile+0x55
b7487d38 7c82845c 00001e20 00000000 00000000 nt!KiSystemServicePostCall
WARNING: Frame IP not in any known module. Following frames may be wrong.
08a9ea8c 00000000 00000000 00000000 00000000 0x7c82845c
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!IoGetAttachedDevice+c
8081c630 8b4810 mov ecx,dword ptr [eax+10h]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!IoGetAttachedDevice+c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 51d4c567
IMAGE_VERSION: 5.2.3790.5190
FAILURE_BUCKET_ID: 0x8E_nt!IoGetAttachedDevice+c
BUCKET_ID: 0x8E_nt!IoGetAttachedDevice+c
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x8e_nt!iogetattacheddevice+c
FAILURE_ID_HASH: {22c1c728-5bf3-efb9-fff4-40d5ae0d47e2}
Followup: MachineOwnerHi,
For Bug Check 0x8E, it
indicates that a kernel-mode application generated an exception that the error handler did not catch. For more details, please refer to following article and check if can help you.
Bug Check 0x8E: KERNEL_MODE_EXCEPTION_NOT_HANDLED
Did you remember that which operation (or any change) you do before this issue occurred? Or just the server
crashed suddenly?
Please check if all necessary updates were installed and drivers were updated.
à
PROCESS_NAME:
DocTransport.exe
Did you install any third-party application on the server? Please
perform a clean boot and monitor the result.
By the way, as you know, troubleshoot this kind of kernel crash issue, we need to analyze the crash dump file to narrow down the root cause of the issue. However, it is not
effective for us to debug the crash dump file here in the forum. If this issues is a state of emergency for you. Please contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request.
To obtain the phone numbers for specific technology request, please refer to the web site listed below:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607
Hope this helps.
Best regards,
Justin Gu -
ProLiant DL580 G5 : Abnormal Program Termination (Windows bug check, STOP: 0x0000007E
We have an ProLiant DL580 G5 server which get blue screen every few minutes. In ILO logs (IML) i get the message.
Abnormal Program Termination (Windows bug check, STOP: 0x0000007E (0xFFFFFFFFC0000005, 0xFFFFF880018B346C, 0xFFFFF88002FD93F8, 0xFFFFF88002FD8C50))
Tried booting in safe mode, but no go. Please advise.Hi:
You may also want to post your question on the HP Business Support Forum -- Proliant DL Servers section.
http://h30499.www3.hp.com/t5/ProLiant-Servers-ML-DL-SL/bd-p/itrc-264#.VCbIEnl0y9I -
Windows 2008 R2 SP1 BSOD Bug Check 0x0000003b
Hi,
I have a Win 2k8 R2 SP1 VM that keeps crashing every night for the past 2 days. Every time is the same bug check code 0x0000003b. I looked around and found 2 KBs for this specific code:
http://support.microsoft.com/kb/980932/en-gb - does not apply to my system
http://support.microsoft.com/kb/2836373/en-gb - installed the hotfix yesterday but got another crash today
The server has 30 printers installed on it and during the night only one is used so I tend to think that it is causing the crash. The printer has the latest driver installed (Konica Minolta Universal Printing Driver v2.4).
I looked through the dump files generated by every BSOD but I cannot find anything that would point me in the right direction... or I might have missed it.
Here is a bit more info on the server:
Windows 2008 R2 Standard SP1
System is a VM
IIS role installed
30 printers installed - all drivers are up to date
I have stored the dump files here: http://1drv.ms/1kpL9vh
Any help with this would be greatly appreciated.
ThanksHi gogu2008,
First , please keep the VM and Host up-to-date then check if the issue persists .
What is the Host OS ?
How much RAM does the VM have ?
If the VM is using dynamic memory , for troubleshooting you may try to configure fixed RAM for the VM.
As for the DUMP , you can change the "mini dump " to "kernel memory dump " then analysis the file after BSOD .
Hope it helps
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place. -
Can Visual Studio 2013 installed on Windows 7 cause Bug check in NTFS driver?
Hello!
I installed Visual Studio 2013 on Windows 7. Shortly after that Bug check of NTFS started periodically happen.
Does VS install any drivers and therefore may be the cause of the bug check?
Thank youHi,
Visual Studio 2013's target platform include Windows 7 Service Pack 1, Windows 8, Windows 8.1, Windows Server 2008 R2 SP1, Windows Server 2012, Windows Server 2012 R2.
For more information, please view this article:
Visual Studio 2013 Compatibility
http://www.visualstudio.com/products/visual-studio-2013-compatibility-vs
For further help, I would like to suggest you ask MSDN Visual Studio Forum:
http://social.msdn.microsoft.com/Forums/en-US/home?forum=vssetup&filter=alltypes&sort=lastpostdesc
Note: add your exact error message or symptoms.
Karen Hu
TechNet Community Support -
Need hotfix for BUG Check reboots for 2012R2
I have 5 Node cluster of 2012R2 which will go to production in next few days, but am struck with the Bug check issue, which reboots atleast 3 nodes frequently. Am aware of this bug check and know the hotfixes for 2012 and 2008. However am not able to find
the hotfix or steps to resolve this issue on 2012r2.
Need assistance to fix this problem.
Thanks in advance, below the debug report.
3: kd> !analyze -v
* Bugcheck Analysis
USER_MODE_HEALTH_MONITOR (9e)
One or more critical user mode components failed to satisfy a health check.
Hardware mechanisms such as watchdog timers can detect that basic kernel
services are not executing. However, resource starvation issues, including
memory leaks, lock contention, and scheduling priority misconfiguration,
may block critical user mode components without blocking DPCs or
draining the nonpaged pool.
Kernel components can extend watchdog timer functionality to user mode
by periodically monitoring critical applications. This bugcheck indicates
that a user mode health check failed in a manner such that graceful
shutdown is unlikely to succeed. It restores critical services by
rebooting and/or allowing application failover to other servers.
Arguments:
Arg1: ffffe8010a271900, Process that failed to satisfy a health check within the
configured timeout
Arg2: 00000000000004b0, Health monitoring timeout (seconds)
Arg3: 0000000000000005
Arg4: 0000000000000000
Debugging Details:
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work.
*** Type referenced: nt!_KPRCB
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work.
*** Type referenced: nt!_KPRCB
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work.
*** Type referenced: nt!_KPRCB
ADDITIONAL_DEBUG_TEXT:
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.
MODULE_NAME: netft
FAULTING_MODULE: fffff80021089000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 5215f788
PROCESS_OBJECT: ffffe8010a271900
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x9E
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre
LAST_CONTROL_TRANSFER: from fffff800a291ac08 to fffff800211dcfa0
STACK_TEXT:
ffffd001`d60c6938 fffff800`a291ac08 : 00000000`0000009e ffffe801`0a271900 00000000`000004b0 00000000`00000005 : nt!KeBugCheckEx
ffffd001`d60c6940 fffff800`a291a892 : 00000000`00000000 00000000`00000000 ffffd001`d601c180 ffffe001`1f716ec8 : netft+0x2c08
ffffd001`d60c6980 fffff800`210e2810 : ffffd001`d60c6b00 ffffe001`1f716ec8 ffffe001`24e7d220 ffffd001`d601c180 : netft+0x2892
ffffd001`d60c69b0 fffff800`211e0aea : ffffd001`d601c180 ffffd001`d601c180 ffffd001`d6028dc0 ffffe001`24e7d080 : nt!KeRemoveQueueEx+0x3b80
ffffd001`d60c6c60 00000000`00000000 : ffffd001`d60c7000 ffffd001`d60c1000 00000000`00000000 00000000`00000000 : nt!KeSynchronizeExecution+0x2efa
STACK_COMMAND: kb
FOLLOWUP_IP:
netft+2c08
fffff800`a291ac08 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: netft+2c08
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: netft.sys
BUCKET_ID: WRONG_SYMBOLS
FAILURE_BUCKET_ID: WRONG_SYMBOLS
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:wrong_symbols
FAILURE_ID_HASH: {70b057e8-2462-896f-28e7-ac72d4d365f8}
Followup: MachineOwner
ndrajHi,
Try to install all recommended cluster hot-fixes to stop further BSODs. Bug check ID 0x9E is recorded for this shutdown & image name netft.sys cause of server shutdown.
As suggested in
similar kind of thread netft.sys is driver of MS Cluster Virtual Adapter. Try to to update firmware/drivers of NICs.
Here is another useful link for your reference
Regards, Ravikumar P -
Updated documentation for "Bug Check 0xDA: SYSTEM_PTE_MISUSE" for Windows 7?
Hi,
I upgraded my Vista x64 (Dell Optiplex 755) to Windows 7 RTM and I'm getting the above bug check. The following site nicely describes the various bug check parameters - http://msdn.microsoft.com/en-us/library/ms796150.aspx - but I don't see an entry for parameter 1 that I'm seeing (504). I assume the 504 is new for Windows 7? If anyone has updated information on this bug check, that'd be much appreciated. From windbg:
BugCheck DA, {504, fffff6fc4002a2e0, 30, 545c}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+b47b )
Thanks
Hans
HKHi Hans
Thanks for letting us know how you resolved the problem.
Regards,
Thank You for using Windows 7
Ronnie Vernon MVP -
Event ID 1001 Bug check Occurred, After updation of Kaspersky Windows 7
Hi,
Recently I have updated my Anti Virus Kaspersky 10 on my Windows 7 Ultimate System 32 bit. After that it restart automatically again and again. Then i restore it on Last known good configuration. It resolve the issue. In event viewr i found out the
Error 1001 Bug check ..
I exactly want to know that what happened to my system . For this How can i send my dmp files to support team .
I have face the problem non my multiple systems but not all .. .
Please guide me asap .The following log occurred
The computer has rebooted from a bugcheck. The bugcheck was: 0x000000c9 (0x0000024d, 0x9047b25a, 0x8d5ed0b8, 0x00000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 041714-22230-01.
when i run verifier.exe
and select " Create standard Setting" then select "Automatically select drivers build for older version of windows" and press Next
it display the Kl1.sys driver
what does it means .. is there any problem with this file? -
Windows rebooted from a bug check..
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0x0000000000000048, 0x0000000000000002, 0x0000000000000001, 0xfffff8026303b73e).
Hello! I've been having bluescreens for about 2 months now. I thought it was my graphic card so I bought a new one and that did not work. I've formatted 4 times - running Windows 8.1 w/ all updates. Any deciphering of the bug check would be great, thanks
for your time.KMODE_EXCEPTION_NOT_HANDLED (1e)
This indicates that a kernel-mode program generated an exception which the error handler did not catch.
BugCheck 1E, {ffffffffc0000005, fffff80307127fd8, 0, ffffffffffffffff}
1: kd> ln fffff80307127fd8
(fffff803`07127ad0) nt!MiResolveProtoPteFault+0x508 | (fffff803`071283e0) nt!MiCompleteProtoPteFault
The exception occurred in nt!MiResolveProtoPteFault+0x508.
1: kd> kv
Child-SP RetAddr : Args to Child : Call Site
ffffd000`22e9ed88 fffff803`07219d47 : 00000000`0000001e ffffffff`c0000005 fffff803`07127fd8 00000000`00000000 : nt!KeBugCheckEx
ffffd000`22e9ed90 fffff803`071dabc2 : 00000000`c64430c0 fffff803`07332420 00000000`0000007d ffffe000`c5ada638 : nt! ?? ::FNODOBFM::`string'+0x3a897
ffffd000`22e9f480 fffff803`071d90fe : 00000000`0000043d 00007ffb`890e3001 ffff0000`00000001 0000ffff`fffff000 : nt!KiExceptionDispatch+0xc2
ffffd000`22e9f660 fffff803`07127fd8 : ffffe000`c9361dd8 00007ffb`890e3e88 00000001`60c4f021 ffffe000`c9361dd8 : nt!KiGeneralProtectionFault+0xfe (TrapFrame @ ffffd000`22e9f660)
ffffd000`22e9f7f0 fffff803`0712638d : fffff6e0`00da6610 00007ffb`8901a13c fffff6bf`fdc480d0 ffffe000`c9361dd8 : nt!MiResolveProtoPteFault+0x508
ffffd000`22e9f890 fffff803`070e258a : ffffe000`c94b1880 00007ffb`8901a13c ffffe000`c94b1880 ffffe000`00000000 : nt!MiDispatchFault+0x29d
ffffd000`22e9f9c0 fffff803`071d922f : 00000000`00000008 00000000`037cfb30 ffffe000`c94b1801 ffffd000`22e9fb00 : nt!MmAccessFault+0x36a
ffffd000`22e9fb00 00007ffb`8901a13c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x12f (TrapFrame @ ffffd000`22e9fb00)
00000000`206fda78 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`8901a13c
1: kd> .trap ffffd000`22e9f660
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000073752860 rbx=0000000000000000 rcx=e000c93bf5780460
rdx=0000000000165396 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80307127fd8 rsp=ffffd00022e9f7f0 rbp=0000000000000000
r8=0000058000000000 r9=ffffe000c9361dd8 r10=ffffd00022e9fb00
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!MiResolveProtoPteFault+0x508:
fffff803`07127fd8 488b3f mov rdi,qword ptr [rdi] ds:00000000`00000000=????????????????
1: kd> u @rip
nt!MiResolveProtoPteFault+0x508:
fffff803`07127fd8 488b3f mov rdi,qword ptr [rdi]
fffff803`07127fdb 4885ff test rdi,rdi
fffff803`07127fde 0f841efcffff je nt!MiResolveProtoPteFault+0x132 (fffff803`07127c02)
fffff803`07127fe4 488bc7 mov rax,rdi
fffff803`07127fe7 4883e0f8 and rax,0FFFFFFFFFFFFFFF8h
fffff803`07127feb 4883f808 cmp rax,8
fffff803`07127fef 0f840dfcffff je nt!MiResolveProtoPteFault+0x132 (fffff803`07127c02)
fffff803`07127ff5 400fb6c7 movzx eax,dil
fffff803`07127d12 0f84f0020000 je nt!MiResolveProtoPteFault+0x538 (fffff803`07128008)
fffff803`07127d18 480fbae708 bt rdi,8
fffff803`07127d1d 0f82f0020000 jb nt!MiResolveProtoPteFault+0x543 (fffff803`07128013)
fffff803`07127d23 4c8bc3 mov r8,rbx
fffff803`07127d26 49c1e805 shr r8,5
fffff803`07127d2a 4183e01f and r8d,1Fh
fffff803`07127d2e 4184d9 test r9b,bl
fffff803`07127d31 0f857c370e00 jne nt! ?? ::FNODOBFM::`string'+0x2c003 (fffff803`0720b4b3)
fffff803`07127d37 488b442448 mov rax,qword ptr [rsp+48h]
fffff803`07127d3c 488d0dade1f5ff lea rcx,[nt!MiReadWrite (fffff803`07085ef0)]
Verify Flags Level 0x0002092b
STANDARD FLAGS:
[X] (0x00000000) Automatic Checks
[X] (0x00000001) Special pool
[X] (0x00000002) Force IRQL checking
[X] (0x00000008) Pool tracking
[ ] (0x00000010) I/O verification
[X] (0x00000020) Deadlock detection
[ ] (0x00000080) DMA checking
[X] (0x00000100) Security checks
[X] (0x00000800) Miscellaneous checks
[X] (0x00020000) DDI compliance checking
We have Driver Verifier enabled at the time of the crash, yet we have a ton of memory related stuff going on, and an exception occurring in one as well. Although Memtest failed, at this point I am going to say we're either not catching a problematic low-level
driver causing corruption, or we have a RAM/motherboard problem despite Memtest passing.
1. Uninstall any/all Asus bloatware (AI Suite, PC Probe, etc... whatever you have).
2. Uninstall/disable the nVidia Streaming Service ASAP.
3. If the above fails, faulty RAM and/or motherboard. Although before definitely concluding this, I'd try a BIOS update if available.
Regards,
Patrick
“Be kind whenever possible. It is always possible.” - Dalai Lama -
Pt880 restarts caused by bug check
lately or for the last few days my system will crash due to a bug check?
1. What are the main reasons why this happens?
2. would a weak power supply cause this?
3. Also I was using 512 megs of infineon memory without any problems, but just lately I added another 512 stick of the same ram in order to get dual channel.
4. Also right now I'm using a power supply with these specs, (as my enermax in my sig was damaged when it arrived) should be here in a day or two.
3.3v 28 amps/5v 40amps/12v 18 amps
I adjusted my ram timings from cas 3, 4,4,9 to cas 2.5,3,3,8, and upped ram voltage to 2.7. I'll prolly have to wait till tomorrow for another blue screen, as it only happens once a day, usually when using winamp or media player, but once it crashed when i went to use my web browser.
I formatted to try and resolve issue but it still remains.
I can't see it being the ram, as it is on the supported list for my mobo, but if it is the ram i'm hoping different timings might help or that it is in fact the power supply.
Any suggestions?Quote
Originally posted by Billaa
I'm getting tired of saying this but my PSU won't be here till later today.
I like the 865 mainboard and they did have one in stock but not sure which one. I'm also quite happy with this board, but I don't want to go through the hassle of borrowing my friends northwood again.
I should take the bios chip off this one and put it on new one. (joking)
Any how i'll know soon enough whether it's psu or mobo. Cause it's not ram cause right now i've got it running in my K7 board at 2- 2- 2- 5 dual channel and it's stable as can be. I guess that's good timing? For Infineon
Hi Billaa,
There is no rush........mistakes might be made........
Yeah, I like the BIOS switch.......
Infineon, is under-rated...... it is good budget mem But, I did have trouble with PT880 and Infineon
We will see how everything goes.........
In the meantime........ have browse here....... Red Rockets....... MSI F@H Team
I think you would go past me very quickly...........
Will await reply
Del -
Aperture 3 will not import image files on hard drives (need bug check).
For the past several days, I've been encountering an issue where Aperture will not recognize photos on a local hard drive (internal or external) for import, but will recognize the exact same image if it is located on a flash card. In fact, I can drag an image from a card to my desktop and it will not be recognized. If I drag it back to the card, it is available for import again. It is not a 100% occurrence however, but doesn't seem to have any rhyme or reason. Restarting Aperture does not help, but this is not to say it won't be working fine the next day.
I am investigating whether anyone else has this issue for a possible bug report.
ThanksI'm having this problem right now. If I switch to a flash card reader with a card inserted, it immediately shows the thumbnails of files available for import. I just finished importing a backup folder of images and that worked as expected, but going back to other folders show nothing inside of them to import.
The File Types panel from Import Settings shows no exclusions checked and the RAW+JPEG Pairs settings do nothing (in any case, this should only apply to RAW+JPEG pairs, which I don't have).
Anybody else find anything that worked? -
<can someone help me what is the cause of it? it just happened a while ago and i got feared it will damage my pc..
n
System
Provider
[ Name]
Microsoft-Windows-WER-SystemErrorReporting
[ Guid]
{ABCE23E7-DE45-4366-8631-84FA6C525952}
[ EventSourceName]
BugCheck
EventID
1001
[ Qualifiers]
16384
Version
0
Level
2
Task
0
Opcode
0
Keywords
0x80000000000000
TimeCreated
[ SystemTime]
2014-04-20T23:40:42.000000000Z
EventRecordID
10197
Correlation
Execution
[ ProcessID]
0
[ ThreadID]
0
Channel
System
Computer
rustyevangelista
Security
EventData
param1
0x0000007e (0xffffffffc0000005, 0x0000000000000000, 0xfffff880031fbb08, 0xfffff880031fb370)
param2
C:\Windows\MEMORY.DMP
param3
042114-53539-01Hi,
In order to assist you, we will need the .DMP files to analyze what exactly occurred at the time of the crash, etc.
If you don't know where .DMP files are located, here's how to get to them:
1. Navigate to the %systemroot%\Minidump folder.
2. Copy any and all DMP files in the Minidump folder to your Desktop and then zip up these files.
3. Upload the zip containing the .DMP files to Onedrive or a hosting site of your choice and paste in your reply. Prefered sites: Onedrive, Mediafire, Dropbox, etc. Nothing with wait-timers.
4 (optional): The type of .DMP files located in the Minidump folder are known as Small Memory Dumps. In %systemroot% there will be what is known as a Kernel-Dump (if your system is set to generate). It is labeled MEMORY.DMP. The difference
between Small Memory Dumps and Kernel-Dumps in the simplest definition is a Kernel-Dump contains
much more information at the time of the crash, therefore allowing further debugging of your issue. If your upload speed permits it, and you aren't going against any strict bandwidth and/or usage caps, etc, the Kernel-Dump is the best
choice. Do note that Kernel-Dumps are much larger in size due to containing much more info, which is why I mentioned upload speed, etc.
If you are going to use Onedrive but don't know how to upload to it, please visit the following:
Upload photos and files to Onedrive.
Please note that any "cleaner" programs such as TuneUp Utilities, CCleaner, etc, by default will delete .DMP files upon use.
If your computer is not generating .DMP files, please do the following:
1. Start > type %systemroot% which should show the Windows folder, click on it. Once inside that folder, ensure there is a Minidump folder created. If not, CTRL-SHIFT-N to make a New Folder and name it Minidump.
2. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Performance > Settings > Advanced > Ensure there's a check-mark for 'Automatically manage paging file size for all
drives'.
3. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Startup and Recovery > Settings > System Failure > ensure there is a check mark next to 'Write an event to the system
log'.
Ensure Small Memory Dump is selected and ensure the path is %systemroot%\Minidump.
4. Double check that the WERS is ENABLED:
Start > Search > type services.msc > Under the name tab, find Windows Error Reporting Service > If the status of the service is not Started then right click it and select Start. Also ensure that under Startup Type it is set to Automatic rather than
Manual. You can do this by right clicking it, selecting properties, and under General selecting startup type to 'Automatic', and then click Apply.
If you cannot get into normal mode to do any of this, please do this via Safe Mode.
Regards,
Patrick
“Be kind whenever possible. It is always possible.” - Dalai Lama -
I recently set up SIP and H.323 DNS SRV records for my domain pointing to my VCS and have been testing using my Free Jabber.com account. It seems that the free jabber.com account gets "hung" in certain situations. This morning my initial test call connects fine from Free Jabber to my Polycom codec, and I end the call. I wait for a few seconds and make another call from Free Jabber to the same codec. Again, that one connects fine. My THIRD call to the codec doesn't even reach my VCS. I have no logs of the call making it to my VCS. Also, I also am not able to reach any other connections in my domain from Free Jabber, and have no logs of the attemps even reaching my VCS.
The only three things I can conclude are:
1) A DNS round-robin where one or more of the DNS servers can't resolve my target DNS domain for SIP/H.323. (unlikely)
2) Somehow and for some reason I've exhaused all of the possible outbound connections for my Free Jabber account. This could perhaps be a bug in that the tear-down of sessions with the Polycom codec, and it doesn't happen correctly, leading to resource exhaustion of my client??
3) I've exceeded some connection rate threshold for my outbound Free Jabber account, and I've been put in "time out" temporarily.
I've logged out of free Jabber and will re-try the scenario at the office and post results.
Has anyone else experienced anything similar? Is there any way to troubleshoot this further? I'm really trying to "sell" the idea of Jabber to my management team, but until it works reliably, it's a no-go.
Thoughts?
Thanks,
MattHi Matt
Yes, this is a comon issue with the CiscoJabberVideo.com solution. My best guess would be what you have mentioned, either a DNS issue or outbound connection issue within the Jabber Video cloud itself as my customers are also not receiving traffic on their VCS-Es as you have described.
There is much talk of this at the moment and the best I can answer everyone is to hold tight until a resolution
There are even two Cisco employees discussing the issue
https://supportforums.cisco.com/thread/2159328?tstart=0
I am sure that Cisco internally (or the old Tandberg guys) must know about the issue by now...
I should start a new thread, but if anyone can answer what SRV records the CiscoJabberVideo.com solution queries, that would be much appreciated
Cheers
Dave
Maybe you are looking for
-
Macbook Pro Retina (15") can't connect to wireless mouse and external USB keyboard
Hi All, I got my new MacBook Pro Retina (15 inch) about 3 weeks ago. It works fine. I got a 30" Dell screen that I am using via thunderbolt/usb adapter. Also, I am using a thunderbolt ethernet adapter. Both adapters work fine without any problems. I
-
Prior to today, when I ran my mouse over the Firefox icon on the tool bar I would get an image of whatever web page I had opened. Now, all I get is text. For example, if I had the BBC open, I could see the open web page by touching the Firefox icon w
-
Where i can find Oracle 9i Certification logo ?
-
Transferring videos to my Nokia 5800
None of the videos I transfer to my 5800 xpress music, actually play on it. Any ideas on what the problem could be? I know the problem is not incorrect format cos i tried uploading mp4 files from my laptop.
-
Hi All, I am extractomer customer related Sales data from Non-SAP.For this masters will come only from ECC.I have created DSO and then Cube to load the data.As per my requirement my reports are based on two cubes. 1. From ECC Data. 2. Non-Sap Data No