Forum Home
Press F1
 
Thread ID: 133170 2013-05-28 05:08:00 BSOD NZHawk (4093) Press F1
Post ID Timestamp Content User
1343778 2013-05-28 05:08:00 Could someone help me discern what is happening with the computer:
==================================================
Dump File : Mini052813-01.dmp
Crash Time : 5/28/2013 10:20:22 AM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x1000000a
Parameter 1 : 0xdbf46028
Parameter 2 : 0x00000002
Parameter 3 : 0x00000000
Parameter 4 : 0x8052270a
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4b70a
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.6368 (xpsp_sp3_gdr.130307-0422)
Processor : 32-bit
Crash Address : ntoskrnl.exe+4b70a
Stack Address 1 : ntoskrnl.exe+4bc7c
Stack Address 2 : ntoskrnl.exe+45b21
Stack Address 3 : ntoskrnl.exe+1c2b94
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini052813-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 90,112
==================================================

==================================================
Dump File : Mini052713-01.dmp
Crash Time : 5/27/2013 4:31:20 PM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x1000000a
Parameter 1 : 0x91f3a820
Parameter 2 : 0x00000002
Parameter 3 : 0x00000000
Parameter 4 : 0x8052270a
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4b70a
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.6368 (xpsp_sp3_gdr.130307-0422)
Processor : 32-bit
Crash Address : ntoskrnl.exe+4b70a
Stack Address 1 : ntoskrnl.exe+4bc7c
Stack Address 2 : ntoskrnl.exe+45b21
Stack Address 3 : ntoskrnl.exe+1c2b94
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini052713-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 90,112
================================================== 		NZHawk (4093)
1343779 2013-05-28 05:25:00 Perhaps your NTOSKRNL.exe file has become corrupted.
It's likely a highl;y protected OS file, so any attempts to replace it will probably have to be done from a Command Prompt.

Alternate option is to try for Safe Mode, and load from a Restore Point.

If you're running XP SP3, then try this from MS:

support.microsoft.com

When you attempt to start Windows XP, you may receive one of the following error messages:
Error message 1
Windows could not start because of a computer disk hardware configuration problem.

Could not read from the selected boot disk. Check boot path and disk hardware.

Please check the Windows documentation about hardware disk configuration and your hardware reference manuals for additional information.
Error message 2
Windows NT could not start because the following file is missing or corrupt:

Winnt_root\System32\Ntoskrnl.exe

Please re-install a copy of the above file.
Error message 3
Winnt_root\System32\Hal.dll missing or corrupt:

Please re-install a copy of the above file.
Additionally, you may experience one or more of the following behaviors:

If you start the computer to the Recovery Console, a command prompt may appear with no option to log on to the Windows installation.
If you try to access the Windows folder, you may receive the following error message:
Access denied.
If you try to perform a Repair operation from the Windows XP CD-ROM, the Windows installation is not detected and you cannot repair Windows.

Back to the top | Give Feedback
Cause
This behavior can occur if any or some of the following conditions are true:

The Default value in the [Boot Loader] section of the Boot.ini file is missing or invalid.
Windows XP is not installed in the location specified in the Boot.ini file.
The Ntoskrnl.exe file is missing or damaged.
The partition path in the Boot.ini file is not set correctly.
General hardware failure.

Back to the top | Give Feedback
Resolution
To resolve this issue, use either of the following methods.
Method 1
Edit the Boot.ini file to restore or correct the Default entry and to ensure that the other entries in the [Operating Systems] section of the Boot.ini file point to the appropriate directories.

For more information about how to edit the Boot.ini file, click the following article number to view the article in the Microsoft Knowledge Base:
289022 How to edit the Boot.ini file in Windows XP
Method 2
Use the Bootcfg utility in the Recovery Console to correct the Boot.ini file:

Use the Windows XP CD-ROM to start your computer.
When you receive the message to press R to repair Windows by using the Recovery Console, press the R key.
Select the Windows installation that you want, and then type the administrator password when prompted.
Type bootcfg /rebuild, and then press ENTER.
When the Windows installation is located, the following instructions are displayed:
Add installation to boot list? (Yes/No/All)
[Type Y in response to this message.]

Enter Load Identifier:
[This is the name of the operating system. Type Windows XP Professional or Windows XP Home Edition.]

Enter OS Load options:
[Leave this field blank, and then press ENTER].
After you perform the preceding steps, restart the computer, and then select the first item on the boot menu. This should allow Windows XP to start normally.

After Windows XP has successfully loaded, the Boot.ini can be modified to remove the incorrect entry.

For more information about how to edit the Boot.ini file, click the following article number to view the article in the Microsoft Knowledge Base:
289022 How to edit the Boot.ini file in Windows XP
Method 3

Start the computer by using your Windows XP CD-ROM. Press any key to boot from the CD.
After the setup files are finished loading press R to repair using Recovery Console.
When you are in the recovery console, select the installation to log on to (usually number 1), and then press ENTER.
Login to the Administrator account by typing the password for this account, and then press ENTER.
At the recovery console command prompt, type the following command, and then press ENTER:

For Uni-Processor systems:
expand <cd-drive>:\i386\ntoskrnl.ex_ <hd-drive>:\Windows\system32\ntoskrnl.exe
For Multi-Processor systems:
expand <cd-drive>:\i386\ntkrnlmp.ex_ <hd-drive>:\Windows\system32\ntoskrnl.exe
Note In these two commands, the <cd-drive> placeholder represents the drive letter of your CD drive, and the <hd-drive> placeholder represents the drive letter of the hard disk on which windows is installed.
If you receive a prompt to overwrite the file, press Y.
Type exit, and press ENTER at the command prompt.

Method 4
Start the computer by using the Recovery Console, and then run theCHKDSK /rcommand.

Note You do not have to include the /p switch in the Chkdsk command-line because the /r switch causes the Chkdsk utility to locate bad sectors and recover readable information. This command implies the /p switch..
Back to the top | Give Feedback
More information
If the Default value in the [Boot Loader] section of the Boot.ini file is missing, Windows XP displays a new entry, Windows (default), on the OS Loader (boot loader) menu, and then defaults to the new entry. The Windows (default) entry points to the following path to load Windows XP:
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
For more information about the Boot.ini file, click the following article number to view the article in the Microsoft Knowledge Base:
102873 Boot.ini and ARC path naming conventions and usage
For more information about Recovery Console in Windows XP, click the following article number to view the article in the Microsoft Knowledge Base:
307654 How to install and use the Recovery Console in Windows XP 		Paul.Cov (425)
1343780 2013-05-28 05:35:00 Is SP3 on it? 0x1000000a maybe memory related, test it with memtest Speedy Gonzales (78)
1343781 2013-05-28 05:38:00 Paul Cov - thank you for that thorough assistance!!
Speedy: yes SP3 - will run memtest 		NZHawk (4093)
1