Solved People Express Management Flight Simulator software 16 bit Windows Subsystem error when login as a local user account in Windows XP Professional SP3 x86 OS (Rev: 1.1)

After installed the People Express Management Flight Simulator (PEMFS) v1.02 on a Windows XP Professional SP3 x86 OS using an administrator account, the PEMFS can start normally. However, if we login using a local user account (jack) and try to run the PEMFS, the PEMFS will shown the below error message:

16 bit Windows Subsystem
C:\DOCUME~1\jack\LOCALS~1\TEMP
(same as C:\Documents and Settings\jack\Local Settings\Temp)
A temporary file needed for the initialization could not be created or could not be written to. Make sure that the directory path exists, and disk space is available. Choose 'Close' to terminate the application


The local user account, jack already had full access right to the C:\DOCUME~1\jack\LOCALS~1\TEMP directory. The error message is misleading because the temporary file needed for the initialization could not be created\written to the c:\WINDOWS\Temp folder, not the C:\DOCUME~1\jack\LOCALS~1\TEMP folder.

As I still have 20 pc to install the PEMFS, I have created the below "1_solved user account startup error.bat" file which is stored in my thumbdrive to solve the PEMFS "16 bit Windows Subsystem" startup error:

----------------- start 1_solved user account startup error.bat -----------------------

@echo off
rem JackNg, Rev: 1.0

rem Give local Users Modify, Read & Execute, List Folder Contents, Read and Write
rem access to %SystemRoot%\temp
rem to solve the People Express Management Flight Simulator startup error
rem when login as a local user account

c:

rem %SystemRoot% = C:\WINDOWS
rem /e = Edit ACL instead of replacing it
rem /p = Replace specified user's access rights
rem c = Change (write)
%SystemRoot%\system32\cacls %SystemRoot%\temp /e /p Users:c

----------------- end 1_solved user account startup error.bat -----------------------


Reference

[1] 16 Bit DOS Application

Solved BSOD 0x00000124 (fatal hardware error) in Windows 7 Professional SP1 OS for Lenovo ThinkPad W510 notebook (Rev: 1.0)

For the Lenovo ThinkPad W510 (type: 4391-BK1) notebook (Intel Quad Core Processor i7-720QM 1.6 Ghz, 6 MB Intel Smart Cache) with Windows 7 Professional SP1 Operating System (OS), Blue Screen Of Death (BSOD) 0x00000124 (0x00000000, 0x88B7301C, 0xF6002DC0, 0x00040150) was occasionally encountered.

If we use the Nirsoft BlueScreenView v1.47 or higher version to view BSOD 0x00000124 crash information stored in the dump files (eg: 040813-16910-01.dmp) at c:\windows\minidump, Nirsoft BlueScreenView will indicate that the BSOD 0x00000124 was caused by the  
halmacpi.dll (address in Stack is halmacpi.dll+efcd) and  
ntkrnlpa.exe (address in Stack is ntkrnlpa.exe+124d48).

Using Lenovo ThinkVantage Toolbox application to update all the related Lenovo applications to the latest version (including updating the BIOS to the latest v1.45) or using Windows Update to update all the Windows 7 patches to the latest version did not help to solve the BSOD 0x00000124 error.

If we download the Lenovo Diagnostics (Bootable CD) v1.6 or higher version to test the Lenovo ThinkPad W510 notebook memory and hardisk, the memory and hardisk test (Controller Diagnostics, Read verification & Speed Test) will pass without any error. Lenovo Service Support had changed the Lenovo ThinkPad W510 motherboard, but the BSOD 0x00000124 error still occasionally encountered.


Analysis the DMP (dump) files at c:\windows\minidump

1. Please download the Windows Driver Kit v7.1.0 (GRMWDK_EN_7600_1.ISO, 649,877,504 bytes).
   
   
   
2. You can use the freeware MagicDisc from Magic ISO Maker to mount the .iso file, GRMWDK_EN_7600_1.ISO to a virtual drive (assume it is v:\ drive).
   
   Assume you have already installed MagicDisc and had started it. On the lower RHS of the monitor screen, kindly right-click on the "MagicISO Virtual CD/DVD Manager" icon, go to "Virtual CD/DVD-ROM" -> "V: No Media" -> "Mount". At the pop-up "Mount CD/DVD image", please point to the GRMWDK_EN_7600_1.ISO file to mount the GRMWDK_EN_7600_1.ISO file to the v:\ drive.
   
   Kindly open a Windows Explorer and go to v:\ drive. Please double-click "v:\KitSetup.exe" to start the Windows Driver Kit installation process. I have only checked to install the "Debugging Tools for Windows (To install Microsoft Windows Debuggers)". I have installed the Microsoft Windows Debuggers to d:\Util\WinDBG directory.
   
   
   
3. Please open the Microsoft Windows Debuggers by double-click the d:\Util\WinDBG\Debuggers\windbg.exe file. Kindly click "File" -> "Symbol File Path ...". Please insert the below Symbol File Path:
   
   SRV*D:\Util\winDBG\symbols*http://msdl.microsoft.com/download/symbols
   
   
   
4. In the Microsoft Windows Debuggers (WinDBG), kindly click "File" -> "Open Crash Dump...", and point to the minidump file (eg: 040813-16910-01.dmp) to load it. When ask on whether to "Save information for workspace?", kindly check the "Don't ask again in this WinDbg session" and click the "Yes" button. WinDBG will now process the 040813-16910-01.dmp.
   
   At the bottom "0: kd>" prompt, please enter the below command to get detail debugging information:
   
   !analyze -v

Below are 2 examples of the Lenovo W510 notebook BSOD 0x00000124 minidump files analysis content:

---

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [E:\040813-16910-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*D:\Util\winDBG\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18044.x86fre.win7sp1_gdr.130104-1431
Machine Name:
Kernel base = 0x83254000 PsLoadedModuleList = 0x8339d4d0
Debug session time: Mon Apr  8 10:06:30.233 2013 (UTC + 8:00)
System Uptime: 0 days 0:39:17.466
Loading Kernel Symbols
...............................................................
................................................................
.....................................................
Loading User Symbols
Loading unloaded module list
..........
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 00000000, Machine Check Exception
Arg2: 88b1e01c, Address of the WHEA_ERROR_RECORD structure.
Arg3: f6001740, High order 32-bits of the MCi_STATUS value.
Arg4: 00040150, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------

BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  TmListen.exe

CURRENT_IRQL:  1f

STACK_TEXT: 
83378d0c 8322bfcd 00000124 00000000 88b1e01c nt!KeBugCheckEx+0x1e
83378d48 833257ac 88af2c31 88b1e01c 832cb740 hal!HalBugCheckSystem+0xab
83378d78 8322c27f 88afa780 83239e40 00000000 nt!WheaReportHwError+0x230
83378e8c 8322c371 88afa780 88afa7d0 00000008 hal!HalpMcaReportError+0x3b
83378eb0 8322c48d 00000000 88afa7d0 00000000 hal!HalpMceHandler+0x8b
83378ed0 8322c5d6 00000000 88afa780 83378ff0 hal!HalpMceHandlerWithRendezvous+0x4b
83378ee0 832225f5 00000000 00000000 00000000 hal!HalpHandleMachineCheck+0x34
83378ff0 8321f261 00000000 801e2000 00000000 hal!HalpMcaExceptionHandler+0x87
83378ff0 00000000 00000000 801e2000 00000000 hal!HalpMcaExceptionHandlerWrapper+0x89


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_CACHE

BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_CACHE

Followup: MachineOwner
---------

---

Loading Dump File [E:\040813-25864-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*D:\Util\winDBG\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18044.x86fre.win7sp1_gdr.130104-1431
Machine Name:
Kernel base = 0x83219000 PsLoadedModuleList = 0x833624d0
Debug session time: Mon Apr  8 09:24:41.047 2013 (UTC + 8:00)
System Uptime: 0 days 0:42:23.280
Loading Kernel Symbols
...............................................................
................................................................
....................................................
Loading User Symbols
Loading unloaded module list
.........
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 00000000, Machine Check Exception
Arg2: 88ae701c, Address of the WHEA_ERROR_RECORD structure.
Arg3: f6002240, High order 32-bits of the MCi_STATUS value.
Arg4: 00040150, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------

BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  1f

STACK_TEXT: 
8333dd0c 83639fcd 00000124 00000000 88ae701c nt!KeBugCheckEx+0x1e
8333dd48 832ea7ac 88adea39 88ae701c 83290740 hal!HalBugCheckSystem+0xab
8333dd78 8363a27f 88ade7e8 83647e40 00000000 nt!WheaReportHwError+0x230
8333de8c 8363a371 88ade7e8 88ade838 00000008 hal!HalpMcaReportError+0x3b
8333deb0 8363a48d 00000000 88ade838 00000000 hal!HalpMceHandler+0x8b
8333ded0 8363a5d6 00000000 88ade7e8 8333dff0 hal!HalpMceHandlerWithRendezvous+0x4b
8333dee0 836305f5 00000000 00000000 00000000 hal!HalpHandleMachineCheck+0x34
8333dff0 8362d261 00000000 801e2000 00000000 hal!HalpMcaExceptionHandler+0x87
8333dff0 00000000 00000000 801e2000 00000000 hal!HalpMcaExceptionHandlerWrapper+0x89


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_CACHE

BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_CACHE

Followup: MachineOwner
---------

---

All the minidump files that I had analysis all point to the same Intel CPU Cache fault (despite different PROCESS_NAME) for the BSOD 0x00000124 (fatal hardware error):

FAILURE_BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_CACHE
BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_CACHE


After Lenovo had replaced the faulty Intel Quad Core Processor i7-720QM, the BSOD 0x00000124 (fatal hardware error) is solved.


References

[1] BSOD 0x00000124 hardware seems fine

[2] Bug Check 0x124: WHEA_UNCORRECTABLE_ERROR

[3] How to open DMP files in Windows 7 ?

Solved "Windows Update cannot currently check for updates, because the service is not running. You may need to restart your computer" error in Windows 7 Professional SP1 OS (Rev: 1.1)

For the Lenovo W510 (type: 4391-BK1) ThinkPad notebook with Windows 7 Professional SP1 Operating System (OS), I had used Windows Update to check and install all the available Windows 7 patches. After that, I had also used Lenovo ThinkVantage Toolbox application to update all the Lenovo software files (including updating to latest BIOS version 1.45) for the Lenovo W510 ThinkPad notebook.

On the next day, when I try to use the Windows Update to check for Windows update again, it will show a “Windows Update cannot currently check for updates, because the service is not running. You may need to restart your computer” error. Restart the Lenovo W510 ThinkPad notebook does not solve the problem because it will still shown the same Windows Update error.

I had opened a Command Prompt to check the Background Intelligent Transfer Service (BITS) and Windows Update (wuauserv) services, and both services are already running (both the services startup type were set as "Automatic (Delayed Start)" in the Computer Management -> Services and Applications -> Services):

# sc queryex bits
SERVICE_NAME: bits
        TYPE               : 20  WIN32_SHARE_PROCESS 
        STATE              : 4  RUNNING
                                (STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN)
        WIN32_EXIT_CODE    : 0  (0x0)
        SERVICE_EXIT_CODE  : 0  (0x0)
        CHECKPOINT         : 0x0
        WAIT_HINT          : 0x0
        PID                : 1220
        FLAGS              :


# sc queryex wuauserv
SERVICE_NAME: wuauserv
        TYPE               : 20  WIN32_SHARE_PROCESS 
        STATE              : 4  RUNNING
                                (STOPPABLE, NOT_PAUSABLE, ACCEPTS_PRESHUTDOWN)
        WIN32_EXIT_CODE    : 0  (0x0)
        SERVICE_EXIT_CODE  : 0  (0x0)
        CHECKPOINT         : 0x0
        WAIT_HINT          : 0x0
        PID                : 1220
        FLAGS              :


I had also checked the Windows 7 Professional SP1 OS registry under
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\BITS,
and all the BITS and sharedAccess services registries were already existed.

Below is the export registry content of the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\BITS:

-------------- Start ------------------------------

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\BITS]
"DisplayName"="@%SystemRoot%\\system32\\qmgr.dll,-1000"
"ImagePath"=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,\
  74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,73,\
  00,76,00,63,00,68,00,6f,00,73,00,74,00,2e,00,65,00,78,00,65,00,20,00,2d,00,\
  6b,00,20,00,6e,00,65,00,74,00,73,00,76,00,63,00,73,00,00,00
"Description"="@%SystemRoot%\\system32\\qmgr.dll,-1001"
"ObjectName"="LocalSystem"
"ErrorControl"=dword:00000001
"Start"=dword:00000002
"DelayedAutoStart"=dword:00000001
"Type"=dword:00000020
"DependOnService"=hex(7):52,00,70,00,63,00,53,00,73,00,00,00,45,00,76,00,65,00,\
  6e,00,74,00,53,00,79,00,73,00,74,00,65,00,6d,00,00,00,00,00
"ServiceSidType"=dword:00000001
"RequiredPrivileges"=hex(7):53,00,65,00,43,00,72,00,65,00,61,00,74,00,65,00,47,\
  00,6c,00,6f,00,62,00,61,00,6c,00,50,00,72,00,69,00,76,00,69,00,6c,00,65,00,\
  67,00,65,00,00,00,53,00,65,00,49,00,6d,00,70,00,65,00,72,00,73,00,6f,00,6e,\
  00,61,00,74,00,65,00,50,00,72,00,69,00,76,00,69,00,6c,00,65,00,67,00,65,00,\
  00,00,53,00,65,00,54,00,63,00,62,00,50,00,72,00,69,00,76,00,69,00,6c,00,65,\
  00,67,00,65,00,00,00,53,00,65,00,41,00,73,00,73,00,69,00,67,00,6e,00,50,00,\
  72,00,69,00,6d,00,61,00,72,00,79,00,54,00,6f,00,6b,00,65,00,6e,00,50,00,72,\
  00,69,00,76,00,69,00,6c,00,65,00,67,00,65,00,00,00,53,00,65,00,49,00,6e,00,\
  63,00,72,00,65,00,61,00,73,00,65,00,51,00,75,00,6f,00,74,00,61,00,50,00,72,\
  00,69,00,76,00,69,00,6c,00,65,00,67,00,65,00,00,00,00,00
"FailureActions"=hex:80,51,01,00,00,00,00,00,00,00,00,00,03,00,00,00,14,00,00,\
  00,01,00,00,00,60,ea,00,00,01,00,00,00,c0,d4,01,00,00,00,00,00,00,00,00,00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\BITS\Parameters]
"ServiceDll"=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,\
  00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,\
  71,00,6d,00,67,00,72,00,2e,00,64,00,6c,00,6c,00,00,00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\BITS\Performance]
"Library"="bitsperf.dll"
"Open"="PerfMon_Open"
"Collect"="PerfMon_Collect"
"Close"="PerfMon_Close"
"InstallType"=dword:00000001
"PerfIniFile"="bitsctrs.ini"
"First Counter"=dword:000007d2
"Last Counter"=dword:000007e2
"First Help"=dword:000007d3
"Last Help"=dword:000007e3
"Object List"="2002"
"PerfMMFileName"="Global\\MMF_BITS_s"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\BITS\Security]
"Security"=hex:01,00,14,80,90,00,00,00,a0,00,00,00,14,00,00,00,34,00,00,00,02,\
  00,20,00,01,00,00,00,02,c0,18,00,00,00,0c,00,01,02,00,00,00,00,00,05,20,00,\
  00,00,20,02,00,00,02,00,5c,00,04,00,00,00,00,02,14,00,ff,01,0f,00,01,01,00,\
  00,00,00,00,05,12,00,00,00,00,00,18,00,ff,01,0f,00,01,02,00,00,00,00,00,05,\
  20,00,00,00,20,02,00,00,00,00,14,00,8d,01,02,00,01,01,00,00,00,00,00,05,04,\
  00,00,00,00,00,14,00,8d,01,02,00,01,01,00,00,00,00,00,05,06,00,00,00,01,02,\
  00,00,00,00,00,05,20,00,00,00,20,02,00,00,01,02,00,00,00,00,00,05,20,00,00,\
  00,20,02,00,00

-------------- End ------------------------------


Solution

In the end, the solution to solve the “Windows Update cannot currently check for updates, because the service is not running. You may need to restart your computer” error is to update the Windows Defender signature file. In Windows 7 Professional SP1 OS, you can start Windows Defender at Start -> Control Panel -> Windows Defender.

Windows Defender includes a command-line utility, MpCmdRun.exe which can be handy if you want to automate the use of Windows Defender and is located at
%ProgramFiles%\Windows Defender\MpCmdRun.exe:


# cd %programfiles%\windows defender

# mpcmdrun -signatureupdate
(To update the Windows Defender signature file)

[JackNg: If the Windows Defender signature update produces an "ERROR: Signature Update failed with hr=800106BA", please refers to 'Solved Windows Defender "ERROR: Signature Update failed with hr=800106BA" & "Windows Update cannot currently check for updates because the service is not running" errors in Acer Aspire X5900 pc with Windows 7 Home Premium x64 OS'.]


After updating the Windows Defender signature file, the “Windows Update cannot currently check for updates, because the service is not running. You may need to restart your computer” error automatically disappeared and Windows Update works normally again.