Bug Check

-

hello.

i have a windows server 2008 r2 enterprise, which has restarted unexpectedly, showing dsod. when i review events generated as follows:

the computer has rebooted bugcheck.  bugcheck was: 0x00000101 (0x0000000000000019, 0x0000000000000000, 0xfffff8800213f180, 0x0000000000000004). dump saved in: c:\windows\memory.dmp. report id: 080511-50996-01.this may related to?

thanks

*******************************************************************************
*                                                                             *
*                        bugcheck analysis                                    *
*                                                                             *
*******************************************************************************
clock_watchdog_timeout (101)
an expected clock interrupt not received on secondary processor in an
mp system within allocated interval. indicates specified
processor hung , not processing interrupts.
arguments:
arg1: 0000000000000019, clock interrupt time out interval in nominal clock ticks.
arg2: 0000000000000000, 0.
arg3: fffff8800213f180, prcb address of hung processor.
arg4: 0000000000000004, 0.
debugging details:
------------------
bugcheck_str:  clock_watchdog_timeout_8_proc
customer_crash_count:  1
default_bucket_id:  driver_fault_server_minidump
process_name:  system
current_irql:  d
stack_text:  
fffff800`02d62a28 fffff800`01629473 : 00000000`00000101 00000000`00000019 00000000`00000000 fffff880`0213f180 : nt!kebugcheckex
fffff800`02d62a30 fffff800`01683de7 : fffffa80`00000000 fffff800`00000004 00000000`00026160 00000000`00000008 : nt! ?? ::fnodobfm::`string'+0x4d8e
fffff800`02d62ac0 fffff800`01bf1895 : fffff800`01c16460 fffff800`02d62c70 fffff800`01c16460 fffff880`00000000 : nt!keupdatesystemtime+0x377
fffff800`02d62bc0 fffff800`01677bf3 : 00000000`00000000 00000000`00000000 fffffa80`06d76010 fffff880`0170bc16 : hal!halphpetclockinterrupt+0x8d
fffff800`02d62bf0 fffff800`01683ec2 : fffff800`017f5e80 fffff800`00000002 00000000`00000002 fffff880`00000000 : nt!kiinterruptdispatchnolock+0x163
fffff800`02d62d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!kiidleloop+0x32
stack_command:  kb
symbol_name:  analysis_inconclusive
followup_name:  machineowner
module_name: unknown_module
image_name:  unknown_image
debug_flr_image_timestamp:  0
failure_bucket_id:  x64_clock_watchdog_timeout_8_proc_analysis_inconclusive
bucket_id:  x64_clock_watchdog_timeout_8_proc_analysis_inconclusive
followup: machineowner
---------
----------------------------------------------------------------------------------------------------------------------------------
you have problem processor. contact manufacturer technical support or replace it.
this posting provided "as is" no warranties or guarantees , , confers no rights.

microsoft student partner 2010 / 2011
microsoft certified professional
microsoft certified systems administrator: security
microsoft certified systems engineer: security
microsoft certified technology specialist: windows server 2008 active directory, configuration
microsoft certified technology specialist: windows server 2008 network infrastructure, configuration
microsoft certified technology specialist: windows server 2008 applications infrastructure, configuration
microsoft certified technology specialist: windows 7, configuring
microsoft certified professional: enterprise administrator
microsoft certified professional: server administrator 



Windows Server  >  Server Core



Comments

Post a Comment

Popular posts from this blog

WIMMount (HSM) causing cluster storage to go redirected (2012r2 DC)

-
looking options resolve error , prevent in future. thanks help. hardware: 2 node dell hv cluster running2012r2 dc 8 nic/ea in multiplex mode 4x hyper-v 4x hosts storage: 2x synology nas, accessed through iscsi hosts , cluster relevant logs: log name:      microsoft-windows-failoverclustering/diagnostic source:        microsoft-windows-failoverclustering date:          event id:      2050 task category: none level:         warning keywords:       user:          system computer:      l description: [dcm] filter wimmount found @ unsafe altitude 180700 log name:      system source:        microsoft-windows-failoverclustering date:         event id:      5125 task category: cluster shared volume level:         warning keywords:       user:          system computer: description: cluster shared volume 'volume1' ('cluster disk 1') has identified 1 or more active filter drivers on device stack interfere csv operatio
Read more

Failed to delete the test record dcdiag-test-record in zone test.com

-
ps c:\users\administrator.test> dcdiag /test:dns directory server diagnosis performing initial setup:    trying find home server...    home server = dc02    * identified ad forest.    done gathering initial info. doing initial required tests    testing server: default-first-site-name\dc02       starting test: connectivity          ......................... dc02 passed test connectivity doing primary tests    testing server: default-first-site-name\dc02       starting test: dns          dns tests running , not hung. please wait few minutes...          ......................... dc02 passed test dns    running partition tests on : forestdnszones    running partition tests on : domaindnszones    running partition tests on : schema    running partition tests on : configuration    running partition tests on : test    running enterprise tests on : test.com       starting test: dns          test results domain
Read more

Azure MFA with Azure AD and RDS

-
i have setup following lab in azure , need help. a server (domain controller) , remote desktop services. and server multi factor authentication server. i have setup following one http://www.rdsgurus.com/uncategorized/step-by-step-using-windows-server-2012-r2-rd-gateway-with-azure-multifactor-authentication/ and when im connecting got following error. the user "domain\username", on client computer "xxx.xxx.xxx.xxx", did not meet connection authorization policy requirements , therefore not authorized access rd gateway server. authentication method used was: "ntlm" , connection protocol used: "rpc-http". following error occurred: "23003". also on security log i've got following authentication details: connection request policy name: ts gateway authorization policy network policy name: - authentication provider: radius proxy authentication server: test.test.local authentication type: - eap t
Read more