Tag Archives: reboot

11.5.1, 11.5.1, 11.5.1, 11.5.1, 11.5.1, 11.5.1, 11.5.1, 11.5.1, 11.5.1, 11.5.1, 11.5.1, 21, 22, 23, 330, 505, 510, 520, 530, 810, 820, 830, CSP4, CSP4, CSP4, CSP4, CSP4, CSP4, CSP4, CSP4, CSP4, CSP4, CSP4, Watchguard, XTM

Watchguard XTM 2 Series, XTM 3 Series, XTM 5 Series, XTM 8 Series – Fireware XTM OS 11.5.1 – CSP4 Build # 335367

03/02/2012 Stuart Davey

Watchguard XTM 2 Series, XTM 3 Series, XTM 5 Series, XTM 8 Series – Fireware XTM OS 11.5.1 – CSP4 Build # 335367

11.5.1 – CSP4 Build # 335367 Resolves the following issues:

BUG64669: Resolved a Firebox crash and reboot when using FireCluster.

BUG63793: Improved proxy debug logging when using FireCluster.

BUG63574: Proxy connections fail with logs showing: “failed to create new traffic spec” and “insert_tspec:XX index inuse?

BUG65026: Iked stack trace eip=0x080c4013 caused by Mobile VPN with IPSec connection.

BUG63860: snmpd memory leak

You can request 11.5.1 – CSP4 Build # 335367 from Watchguard Support by logging a support case online, they should then be able to provide an ftp download link and appropriate credentials.

Please note that Watchguard CSP releases are cumulative so you should only need to apply the latest to ensure that you also have any previous fixes.

11.5.1, 11.5.1, 11.5.1, 11.5.2, 11.5.2, 11.5.2, 21, 22, 23, FireBox, Watchguard, XTM

[RESOLVED] – Watchguard Fireware 11.5.1 – XTM 2 Series Appliance Locksup, Stops Responding to Login Requests and/or outbound traffic rejected

16/12/2011 Stuart Davey

Please be aware that Watchguard Fireware OS 11.5.1 and 11.5.2 have a very recently identified issue where by an XTM 2 Series unit will randomly not respond to Login requests and will not route outbound traffic. I have been informed by Watchguard support that this is still not fully resolved in 11.5.2 so we have had to downgrade many of our units to 11.4.2 to avoid them locking up and requiring a physical restart (pull power cord out). An updated release of 11.5.1 can now be requested from Watchguard support that should resolve the lockups. This updated 11.5.1 release is tagged as a debug build so other issues may be present. A CSP Service Pack release is due for 11.5.2 to resolve this issue and a permanant fix is expected to be in the 11.5.3 release of the XTM OS.

Please request Fireware XTM OS 11.5.2 – CSP1 Build # 338385 for the XTM 2 Series from Watchguard, this 11.5.2 CSP release resolves the lockups that were first introduced with 11.5.1.

Lockup Fixes included within 11.5.2 CSP1:

Multiple bug #s: changes to resolve file system writing error introduced in v11.5.1 on XTM 21-23 models. The file system error caused several problems such as; management access stops, wireless stops working, new connections through the Firebox may fail.

More detail can be found here http://aidinit.com/2012/03/watchguard-xtm-2-series-xtm-3-series-xtm-5-series-xtm-8-series-fireware-xtm-os-11-5-2-csp1-build-338385/

BSOD, SBS 2011, Small Business Server 2011, Windows, Windows 7, Windows Server 2008 R2

Windows Kernel Power Event ID 41 Error

24/10/2011 Stuart Davey Leave a comment

Windows 7 or Windows Server 2008 R2 may restart unexpectedly, you may get a brief glimpse of a BSOD (Blue Screen of Death) and then find yourself back at the Windows login prompt. When you inspect the Windows Event Log you will find the following event logged

Log Name: System
Source: Microsoft-Windows-Kernel-Power
Event ID: 41
Level: Critical
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

The additional info under the event is important because the various bug check codes can indicate different causes.

EventData
BugcheckCode          0
BugcheckParameter1    0x0
BugcheckParameter2    0x0
BugcheckParameter3    0x0
BugcheckParameter4    0x0

Having faced this error recently it eventually turned out that the problem was due to incompatible memory (not faulty memory). The batch of machines in question were all branded but due to an error with the manufacturers memory compatability matrix had been supplied with the wrong additional memory modules. When we reverted the machines to the standard 2GB module that was already installed they operated perfectly, we eventually arranged for the additional modules to be swapped and that was the end of the issue.

An important thing to remember is that a memory checker will not show that your memory is faulty if it just incompatible with your particular system or mainboard.

Your system or mainboard manufacturers support should be able to confirm memory compatability and advise on the correct upgrade/type for your system

Aid In IT

Tag Archives: reboot

Watchguard XTM 2 Series, XTM 3 Series, XTM 5 Series, XTM 8 Series – Fireware XTM OS 11.5.1 – CSP4 Build # 335367

Windows Kernel Power Event ID 41 Error

IT – Software and Hardware Support Resources