BSOD on windows server 2012?
В продакшине есть сервер dell poweredge r720xd с windows server 2012 datacenter edition, он забсодил после того как я отправил виртуальную машину в ребут.
интересное из мини дампа:
Технические характеристики kd>! analyze -v
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is
caused by drivers that have corrupted the system pool. Run the driver
verifier against any new (or suspect) drivers, and if that doesn’t turn up
the culprit, then use gflags to enable special pool.
Arg1: 000000000000f6c8, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8016a28be15, address which referenced memory
— *** WARNING: Unable to verify timestamp for Vid.sys
*** ERROR: Module load completed but symbols could not be loaded for Vid.sys
fffff801`6a28be15 49394208 cmp qword ptr [r10+8],rax
TRAP_FRAME: fffff8800e6a9fb0 — (.trap 0xfffff8800e6a9fb0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa80629cc6d0 rbx=0000000000000000 rcx=fffffa80629cc6c0
rdx=fffffa80626d3d60 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8016a28be15 rsp=fffff8800e6aa140 rbp=fffff8800e6aa1b8
r8=fffffa80629cc6e0 r9=0000000000000000 r10=000000000000f6c0
r11=0000000000000001 r12=0000000000000000 r13=0000000000000000
iopl=0 nv up ei ng nz na po nc
fffff801`6a28be15 49394208 cmp qword ptr [r10+8],rax ds:00000000`0000f6c8=.
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff8016a096369 to fffff8016a097040
fffff880`0e6a9e68 fffff801`6a096369: 00000000`0000000a 00000000`0000f6c8 00000000`00000002 00000000`00000000: nt!KeBugCheckEx
fffff880`0e6a9e70 fffff801`6a094be0: 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`0e6a9fb0: nt!KiBugCheckDispatch+0x69
fffff880`0e6a9fb0 fffff801`6a28be15: 00000000`0001453e 00000000`00000000 00000000`00014600 fffffa80`60c47c78: nt!KiPageFault+0x260
fffff880`0e6aa140 fffff801`6a28ab48: fffff880`00000000 fffffa80`680cbac0 fffffa80`636db870 fffff880`00800008: nt!ExDeferredFreePool+0x1b5
fffff880`0e6aa1d0 fffff801`6a0dcc71: fffffa80`680cbad0 0000001d`f5615fff fffffa80`dee2d980 fffffa80`76706d4d: nt!ExFreePoolWithTag+0xb39
fffff880`0e6aa2b0 fffff801`6a483c5b: 00000000`00000000 fffff700`0003b000 0000001d`f5610000 00000000`00000001: nt!MiFreePhysicalView+0x51
fffff880`0e6aa2e0 fffff801`6a0dcac0: fffffa80`dee2d980 fffffa80`7151fb00 fffffa80`680969b0 fffffa80`dee2d980: nt!MiRemoveVadCharges+0x12b
fffff880`0e6aa320 fffff801`6a0fbe54: fffffa80`680969b0 fffffa80`69592d10 fffffa80`6db99320 00000000`00000000: nt!MiFinishVadDeletion+0x1d0
fffff880`0e6aa390 fffff801`6a1492da: fffffa80`680969b0 00000000`00000000 fffffa80`6a55cd70 0000001d`f5610000: nt!MiUnmapVad+0xf4
fffff880`0e6aa3f0 fffff880`0501637f: 00000000`00000000 00000000`00000000 0000001d`f480f270 fffffa80`70875d80: nt!MiUnmapLockedPagesInUserSpace+0xfa
fffff880`0e6aa420 00000000`00000000: 00000000`00000000 0000001d`f480f270 fffffa80`70875d80 fffff880`0e6aa600: Vid+0x1637f
fffff801`6a28be15 49394208 cmp qword ptr [r10+8],rax
Windows 2012 r2 bsod
The bugcheck was FC:
To evaluate the BSOD please post logs for troubleshooting.
Using administrative command prompt copy and paste this whole command.
Make sure the default language is English so that the logs can be scanned and read.
The command will automatically collect the computer files and place them on the desktop.
Then use 7zip to organize the files and one drive, drop box, or google drive to place share links into the thread for troubleshooting.
This command will automatically collect these files: msinfo32, mini dumps, drivers, hosts, install, uninstall, services, startup, event viewer files, etc.
Open administrative command prompt and copy and paste the whole command:
copy %SystemRoot%\minidump\*.dmp «%USERPROFILE%\Desktop\»&dxdiag /t %Temp%\dxdiag.txt© %Temp%\dxdiag.txt «%USERPROFILE%\Desktop\SFdebugFiles\»&type %SystemRoot%\System32\drivers\etc\hosts >> «%USERPROFILE%\Desktop\hosts.txt»&systeminfo > «%USERPROFILE%\Desktop\systeminfo.txt»&driverquery /v > «%USERPROFILE%\Desktop\drivers.txt» &msinfo32 /nfo «%USERPROFILE%\Desktop\msinfo32.nfo»&wevtutil qe System /f:text > «%USERPROFILE%\Desktop\eventlog.txt»® export HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall «%USERPROFILE%\Desktop\uninstall.txt»® export «HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components» «%USERPROFILE%\Desktop\installed.txt»&net start > «%USERPROFILE%\Desktop\services.txt»&REM wmic startup list full /format:htable >»%USERPROFILE%\Desktop\startup.html»&wmic STARTUP GET Caption, Command, User >»%USERPROFILE%\Desktop\startup.txt»
There are two files for you to find manually:
Use file explorer > this PC > local C: drive > right upper corner search enter the above to find results.
In the left lower corner search type: dxdiag > When the DirectX Diagnostic Tool opens click on the next page button so that each tab is opened > click on save all information > save to desktop > post one drive or drop box share link into the thread
.
.
.
.
.
Please remember to vote and to mark the replies as answers if they help.
.
.
.
.
.
Windows 2012 r2 bsod
This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.
Answered by:
Question
Im experiencing very frustrating BSODs and I would like to ask you for opinion.
I got HP microserver N54L and I was successfully running Windows 2012 on it — stable and without any issues. Im running standard config there + I got a Radeon low profile graphic card there.
I did in-place upgrade to Windows 2012 server R2 and since then I have occasional BSOD on the boot. It happens every 2-3 boot. Normally I would wait for crash dump file to be generated and then analyze it to debug a driver or identify a HW part which is causing it however crash dump is not being generated at all. System is frozen on this message:
«. we will restart the system for you (0% Complete). clock_watchdog_timeout»
and it stays at 0% forever so I have to manually shut it down by power button.
My system settings are set to «Write an event to the system log», «Automatically restart», Small memory dump (256KB), Small dump directory — %SystemRoot%\Minidump (accessible), Overwrite an existing file.
There is 16GB RAM and there is 2GB swap file on C: and system managed on E:. There is 17,3GB free space on disk C:.
I have the latest BIOS (the one which is addressing the problem with windows 2012 R2 installation) and last driver for network and graphic (radeon) card.
When I check the system log there is nothing — no error related to this boot BSOD.
Any idea why is crash dump file not being created?
Answers
Just want to inform that after several weeks of testing I can confirm this issue is caused by Windows 2012 R2 installed with Hyper-V role on HP microserver N54L.
As I was unable to find any fix for this I switched to vmware.
All replies
Based on current situation (no dump file), please refer to the following suggestions and troubleshoot.
- Please use sfc /scannow to scans all protected system files immediately.
- Use Chkdsk command to check disks status.
- Disable all security softwares temporarily and check if this issue still persists.
- Check RAM if OK.
- Perform a clean boot to troubleshoot the interference of applications or services.
By the way, CLOCK_WATCHDOG_TIMEOUT is generally considered as a hardware BSOD. Please pay attention to it.
In addition, I suggest you should 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:
Hope this helps.
—> so I have to manually shut it down by power button.
this maybe why you can’t get dump file.
N54L and N36L are almost identical if Im not mistaken there is difference in processor. Just to update you I thought this have been caused by in place update from 2012 to 2012 R2 so I reinstalled it with fresh Windows 2012 R2 but no luck — same BSOD.
Im now going to install it again and install patches one by one with 2 days testing for each patch installed. Then slowly add additional software to see when it actually starts to happen.
If that fails I will try to flash HP BIOS as Im now running last version version of custom BIOS. If that doesn’t help I don’t know what else I can try.
It should not be a memory problem (half day memtest did not find any problem) but still if system is unable to create dump file it looks like there is a problem to read memory or to write it to disk.
Yes, N36L and N54L are almost identical. Only difference is the CPU.
I have fresh install of Server 2012 R2. I also have all the latest patches and latest HP bios (october 2013). I’m still getting this BSOD randomly at boot. BSOD seems to happen only during boot, not after.
so I reinstalled OS to new 350GB HDD which I have inserted to HDD bay. Before I used 60GB SSD drive in DVD-ROM position. Running it for 2 weeks without Hyper-V and without patches and not a single BSOD. Im going to install patches now and will report here about the progress. At the moment it looks like its either caused by adding hyper-v role (which sucks as I have built it primary as virtual lab), SSD HDD in DVD rom or some patch.
I’m 99% sure Hyper-V is the cause. We both have exactly the same setups N54L, Server 2012 R2, 16GB RAM, HD5450 Gfx, SSD and DVD drive.
I can confirm that I never received these BSOD before turning on the Hyper-V role..
I’m going to follow this guide to create a 2nd boot entry with hyper-v disabled and see whether I get any Clock_watchdog errors.. http://blogs.msdn.com/b/virtual_pc_guy/archive/2008/04/14/creating-a-no-hypervisor-boot-entry.aspx
If Hyper-V is the cause surely there must be a hotfix for this somewhere.
Just want to inform that after several weeks of testing I can confirm this issue is caused by Windows 2012 R2 installed with Hyper-V role on HP microserver N54L.
As I was unable to find any fix for this I switched to vmware.
i’ve runned into the same Problem here: HP N54L with 8 GB RAM (1x 4GB ECC, 1x 4 GB Non-ECC), BIOS-Mod (2013er), Samsung Evo 250 GB as System-Partition, Hyper-V-Role on 2012/2012R2 installed.
I can confirm the following: I’ve got the N54l brand new and installed on standard-config (4GB RAM, no BIOS-Mod) Windows Server 2012 R2 on my local System-SSD. I’ve got the BSOD described by you (clock_watchdog_timeout).
Tried many things and given up — installed 2008 R2 and runned for weeks without problems. Then i’ve got some errors for vss and decided to install Windows fresh — this time with 2012, because you wrote: no problems there.
Installed 2012 non-R2, installed all updates and the AMD Legacy-Displaydriver (for onBoard Videoadapter) and the Hyper-V Role. Second reboot: clock_watchdog_timeout-BSOD.
I’ve searched the Web — and found not much; installed a Microsoft-FixIt for described BSOD (which was created for 2008 R2 — but i installed it without any error). Then i found something, that the «AMD Vision Engine», which was additional installed by the AMD-Videodriver, could lead to BSODs. I deinstalled it, because i dont need it.
I’ve now rebooted my N54l about 10-15 times without running into the above bluescreen. I don’t know if this was the final resolution — i will try to reboot some times more and will observe our BSOD-Problem in future.
Maybe, this can help on 2012R2 too — i’ve read some threads by users, that use the N54L with 2012R2 with Hyper-V without any problem — so it should be a software/driver-issue.