Tag Archives: troubleshoot

DELL, Fujitsu, HP, IBM, Microsoft, ML110 G5, ML110 G6, ML350 G5, ML350 G6, Primergy, ProLiant, SBS 2008, Service Pack 2, Service Pack 2, Service Pack 2, Service Pack 2, Small Business Server 2008, Windows, Windows Server 2008, Windows Vista

Storport.sys – Pre Service Pack 3 Revision History for Windows Server 2008 SP2, Windows Vista SP2 and Windows Small Business Server 2008 (SBS 2008)

Leave a comment

Storport.sys – Pre Service Pack 3 Revision History for Windows Server 2008 SP2, Windows Vista SP2 and Windows Small Business Server 2008 (SBS 2008)

08-Nov-2012 – 6.0.6002.22969 – Storport.sys – x86/x64 – http://support.microsoft.com/kb/2780444 – “0x0000012E” Stop error occurs when an application sends a 12-byte SCSI opcode to an iSCSI target in Windows Vista SP2, Windows Server 2008 SP2, Windows 7 SP1, and Windows Server 2008 R2 SP1

06-Apr-2012 – 6.0.6002.22834 – Storport.sys – x86/x64 – http://support.microsoft.com/kb/2528357 – Nonpaged pool leak when you disable and enable some storage controllers in Windows Vista, in Windows 7, in Windows Server 2008 or in Windows Server 2008 R2

07-Sep-2011 – 6.0.6002.22711 – Storport.sys – x86/x64 – http://support.microsoft.com/kb/2511500 – “0x0000007E” Stop error after you perform a hot removal of a PCI device in Windows 7, in Windows Server 2008 R2, in Windows Vista or in Windows Server 2008

17-Jun-2011 – 6.0.6002.22661 – Storport.sys – x86/x64 – http://support.microsoft.com/kb/2553708 – A hotfix rollup that improves Windows Vista and Windows Server 2008 compatibility with Advanced Format disks

11-May-2010 – 6.0.6002.22402 – Storport.sys – x86/x64 – http://support.microsoft.com/kb/983554 – “0x000000BE” Stop error message when you use the Storport.sys driver to manage some storage devices in Windows Server 2008, in Windows Vista, in Windows 7 or in Windows Server 2008 R2

18-Mar-2010 – 6.0.6002.22367 – Storport.sys – x86/x64 – http://support.microsoft.com/kb/981751 – “Stop error code 0x0000007E (SYSTEM_THREAD_EXCEPTION_NOT_HANDLED) in Windows Server 2008 or in Windows Vista

02-Feb-2010 – 6.0.6002.22327 – Storport.sys – x86/x64 – http://support.microsoft.com/kb/979764 – A hotfix is available that improves the logging capabilities of the Storport.sys driver to troubleshoot poor performance issues for the disk I/O in Windows Server 2008

04-May-2009 – 6.0.6002.22128 – Storport.sys – x86/x64 – http://support.microsoft.com/kb/968675 – The storport.sys driver leaks nonpaged pool memory when volumes are scanned, mounted, or dismounted in Windows Server 2008 and Windows Vista

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

Windows Kernel Power Event ID 41 Error

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