Bluescreen Problem nach Symantec Systemrecovery 2013 und Windows Update Installationen

[Dirk-HH-83 14]

Hallo, 

1. bei einem SBS 2008 64bit gibt es seit ca. 15 neu installierten Windows Sicherheitsupdates und Installation von Symantec System Recovery 2013 sporadisch u.g. Bluescreens 1-2 täglich. (nicht während der Backupjobs)
2. Bei der alten Backupsoftware Acronis Backup Recovery 10 waren die Dienste bisher nicht deaktiviert.
3. Ob Servicepack 2 bei einem neuen Symantec SSR 2013 Install-Image intergriert ist weiß ich nicht.
4. Dieses Hotfix läßt sich nicht installieren: https://support.microsoft.com/de-de/kb/980932  (haben auch kein Firewire Gerät angeschlossen)
5. Im Erreignislog sind keine auffälligen Fehler
6. auf dem SBS ist ansonsten installiert: DATEV, Kaspersky 

Verstehe es so, das dies im Grunde die Ursache mitteilt: 0x3B (0xC0000005, 0xFFFFF80004A2090D, 0xFFFFFA600CEA8190, 0x0) - allerdings ist im Google dazu nichts zu finden.

 

Danke/Gruß

Dirk

 

 

 

 

Crash Dump Analysis

 

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Fri 14.08.2015 02:22:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini081415-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x55010)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80004A2090D, 0xFFFFFA600CEA8190, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Thu 13.08.2015 01:36:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini081315-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x55010)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000481290D, 0xFFFFFA600C35A190, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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.

 

 

Conclusion

 

2 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

 

bearbeitet 14. August 2015 von Dirk-HH-83

[Nobbyaushb 1.371]

Und was spricht der Support dazu?

 

Im Moment ggf. schwierig zu erreichen wegen der Trennung Veritas - Symantec

 

;)

[Dirk-HH-83 14]

Symantec Support ist wegen Webex eigentlich ganz ok, wäre nur interessant ob man Symantec Support auch online veranlassen kann weil es telefonisch immer mit Rückruf ist.

 

Ja, haben SSR 2013 deinstalliert und kein Bluescreen mehr.

 

Melde mich wieder mit der Lösung.

[Dirk-HH-83 14]

stimmt es lag am Symantec.

[Dirk-HH-83 14]

bei dem anderen Server mit Symantec Installation Problem war dies die Ursache: ZIP Datei mittels Rechtsklick nicht "entsperrt" (der windows zip extrahierer) extrahiert offenbar unsauber. So dass WINRAR besser gewesen wäre.

[Nobbyaushb 1.371]

Ich nehme nur noch 7zip...

 

:D