Tag Archives: RAM

Microsoft, SBS 2008, SBS 2011, Service Pack 1, Service Pack 1, Service Pack 1, Service Pack 1, Service Pack 2, Service Pack 2, Service Pack 2, Service Pack 2, Small Business Server 2008, Small Business Server 2011, Windows, Windows 7, Windows Server 2008, Windows Server 2008 R2, Windows Vista

[RESOLVED] 32 Bit Application or Game with the /LARGEADDRESSAWARE option running on a 64 Bit Version of Windows Vista, Windows Server 2008, Windows SBS 2008, Windows 7, Windows Server 2008 R2 or Windows SBS 2011 may generate an error message

When you run a 32 Bit Application or Game with the /LARGEADDRESSAWARE option on a 64 Bit Version of Windows you may receive one of the following errors

  • WSANO_DATA
  • ERROR_NO_DATA (232)
  • ERROR_NOACCESS (998)

These errors will occur if the application consumes large amounts of memory, the kernel denies read or write access to the address and returns an error to the application.

The Microsoft Knowledgebase article KB 2588507 provides a hotfix to address these issues http://support.microsoft.com/kb/2588507/en-gb

To apply this hotfix, you must be running one of the following 64 Bit operating systems:

  • Windows Vista Service Pack 2 (SP2)
  • Windows Server 2008 Service Pack 2 (SP2)
  • Windows 7 (RTM)
  • Windows 7 Service Pack 1 (SP1)
  • Windows Server 2008 R2 (RTM)
  • Windows Server 2008 R2 Service Pack 1 (SP1)
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