Windows Server 2008 R2 Dump sorunları hk.

Merhabalar,

 

Hyper-V üzerinde additional domain ve dns kurulu WS 2008 R2 işletim sistemim var. Makineye konsoldan veya RDP'den bağlanmaya çalışığımda masaüstü geliyor yaklaşık 40 sn sonra mavi ekran verip kapatıyor. Cihazı güvenli modda masaüstünü getirebiliyorum sorun yok hata vermiyor. Güvenli modda iken çalışan servislerin haricindekileri kapatıp denedim olmadı, Local admin ve Domain admin ile login oldum olmadı, CPU ve Ram arttırımı sağlandı olmadı, Hyper-V sunucusunu restart ettim olmadı, Memtest yapamadım hata verdi. Çözüm olarak farklı addc kurmak istemedim. Dump analysis'deki rapor aşağıdaki gibidir. Yardımlarınız için şimdiden teşekkürler

 

Master Domain: WS 2012 R2

 

 

--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Mon 10.12.2018 12:05:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121018-38359-01.dmp
uptime: 00:01:58
This was probably caused by the following module: ntoskrnl.exe (nt+0x939A0)
Bugcheck code: 0x51 (0x1, 0xFFFFF8A000024010, 0x99F000, 0x374)
Error: REGISTRY_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe registry error has occurred.
This bug check indicates there is a problem related to your registry.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

On Mon 10.12.2018 12:05:23 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
uptime: 00:01:58
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x51 (0x1, 0xFFFFF8A000024010, 0x99F000, 0x374)
Error: REGISTRY_ERROR
Bug check description: This indicates that a severe registry error has occurred.
This bug check indicates there is a problem related to your registry.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

On Mon 10.12.2018 11:34:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121018-38656-01.dmp
uptime: 05:41:16
This was probably caused by the following module: Unknown (0xFFFFF8000169D9A0)
Bugcheck code: 0x50 (0xFFFFF8A00763F000, 0x0, 0xFFFFF8000190BDF0, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error.
Google query: PAGE_FAULT_IN_NONPAGED_AREA

 

On Mon 10.12.2018 05:50:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121018-38906-01.dmp
uptime: 00:15:03
This was probably caused by the following module: ntoskrnl.exe (nt+0x939A0)
Bugcheck code: 0x50 (0xFFFFF8A011617000, 0x0, 0xFFFFF80001917DF0, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

On Mon 10.12.2018 05:34:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121018-26343-01.dmp
uptime: 00:03:31
This was probably caused by the following module: ntoskrnl.exe (nt+0x939A0)
Bugcheck code: 0x50 (0xFFFFF8A003499000, 0x0, 0xFFFFF8000191ADF0, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

On Mon 10.12.2018 05:29:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121018-41421-01.dmp
uptime: 00:04:14
This was probably caused by the following module: ntoskrnl.exe (nt+0x939A0)
Bugcheck code: 0x50 (0xFFFFF8A00F2E5000, 0x0, 0xFFFFF80001912DF0, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

On Mon 10.12.2018 05:23:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121018-35281-01.dmp
uptime: 00:20:32
This was probably caused by the following module: ntoskrnl.exe (nt+0x939A0)
Bugcheck code: 0x50 (0xFFFFF8A011640000, 0x0, 0xFFFFF8000190ADF0, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

On Mon 10.12.2018 05:00:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121018-46750-01.dmp
uptime: 09:31:29
This was probably caused by the following module: ntoskrnl.exe (nt+0x939A0)
Bugcheck code: 0x51 (0x1, 0xFFFFF8A000024010, 0x99F000, 0x374)
Error: REGISTRY_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe registry error has occurred.
This bug check indicates there is a problem related to your registry.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

On Sun 09.12.2018 19:28:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120918-21953-01.dmp
uptime: 00:02:34
This was probably caused by the following module: ntoskrnl.exe (nt+0x939A0)
Bugcheck code: 0x51 (0x1, 0xFFFFF8A000024010, 0x99F000, 0x374)
Error: REGISTRY_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe registry error has occurred.
This bug check indicates there is a problem related to your registry.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

On Sun 09.12.2018 18:52:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120918-46812-01.dmp
uptime: 00:05:00
This was probably caused by the following module: ntoskrnl.exe (nt+0x939A0)
Bugcheck code: 0x51 (0x1, 0xFFFFF8A000024010, 0x99F000, 0x374)
Error: REGISTRY_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe registry error has occurred.
This bug check indicates there is a problem related to your registry.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

 

--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

16 crash dumps have been found and analyzed. Only 10 are included in this report.
Read the topic general suggestions for troubleshooting system crashes for more information.