Question about HP PC Desktops

3 Answers

My computer crashed and will not boot back up. It says File\minint\system32\ntkrn1mp.exe could not be loaded. Error code 32768. my computer is an HP that I purchased from costco and it did not come with windows xp discs. they were already loaded when I purchased it.

Posted by on

3 Answers

  • Level 2:

    An expert who has achieved level 2 by getting 100 points

    All-Star:

    An expert that got 10 achievements.

    MVP:

    An expert that got 5 achievements.

    Vice President:

    An expert whose answer got voted for 100 times.

  • Expert
  • 344 Answers

Most HP computers if you press F11 right after the bios screen , it should go into the system recovery partition

Posted on Nov 13, 2008

  • Level 2:

    An expert who has achieved level 2 by getting 100 points

    MVP:

    An expert that got 5 achievements.

    Governor:

    An expert whose answer got voted for 20 times.

    Scholar:

    An expert who has written 20 answers of more than 400 characters.

  • Expert
  • 69 Answers

Hi wiredstone,

Unfortunately it is very likely that you will need to reinstall windows. I understand that you don't have the windows disks but there are other disks called restore disks that should have come with the pc. WARNING when you do this then everything on your hard drive will be gone and it will be as clean as the day you bought it.

If you don't have any of these disks you will need to buy windows or take it to a pro for reformatting (they get reformatting licenses)

If you don't have backups of your information and need the data on your hard drive you can backup the hard drive by removing it and connecting it to another pc Or getting a pro to do it.

that said its possible that some of your hardware has failed.
As to why this happened could be due to many many factors like software conflicts, overheating, viruses.. etc.

I'm sorry to give you bad news but it happens.

Posted on Nov 13, 2008

  • Level 2:

    An expert who has achieved level 2 by getting 100 points

    Hot-Shot:

    An expert who has answered 20 questions.

    Corporal:

    An expert that has over 10 points.

    Mayor:

    An expert whose answer got voted for 2 times.

  • Expert
  • 57 Answers

Hp should have an option on your boot menu (viewed by pressing f8) to boot to system partition. Try that and see what kind of options are there.

Posted on Nov 13, 2008

Add Your Answer

Uploading: 0%

my-video-file.mp4

Complete. Click "Add" to insert your video. Add

×

Loading...
Loading...

Related Questions:

1 Answer

How to fix \minint\system32\kdcom file cannot load error 4 Emachine


Download this file to your computer and burn it to a CD:
http://majorgeeks.com/downloadget.php?id=6501&file=1&evp=ef4247319d4b536cb88b74d1ae4842b0

If you don't have an app that can easily burn .iso files to a CD then get this awesome little FREE app and install it:
http://www.majorgeeks.com/downloadget.php?id=4870&file=9&evp=0636b68877cb69b15faa3374cb1dcd89

The Bootable CD you burn should fix your computer. It's really easy to use. Just follow the instructions from page 15 to page 33 in this pdf:
http://support.kaspersky.com/downloads/guides/kasp10.0_rescuedisk_en.pdf

You basically want to update the virus definitions and select all of the checkable boxes to scan and run the scan and then allow it to delete or quarantine the bad files.

Sep 01, 2012 | E-Machines eMachines Desktop PC

Tip

Boot problems and their possible causes & resolutions


Symptoms:
Black screen
"Invalid Partition Table"
"Error loading operating system"
"Missing operating system"


Cause:
Corrupt Master Boot Record (MBR)

Resolution:
Boot into Recovery Console and run "fixmbr" to repair the MBR

--

Symptoms:
"A disk read error occurred"
"NTLDR is missing"
"NTLDR is compressed"


Cause:
Corrupt boot sector

Resolution:
Boot into Recovery Console and run "fixboot" to repair the boot sector

--

Symptoms:
"BOOT.INI is missing or corrupt"
"Boot device inaccessible"
"Windows could not start because the following file is missing or corrupt:
<Windows root>\system32\hal.dll"


Cause:
BOOT.INI missing, corrupt or out of date as a partition has been inserted

Resolution:
Boot into Recovery Console and run "bootcfg /rebuild" to repair the BOOT.INI

--

Symptoms:
"Windows could not start not start because the following file is missing or corrupt:
\WINDOWS\SYSTEM32\CONFIG\SYSTEM"


Cause:
Corrupt/missing system hive

Resolution:
1. Boot into Recovery Console and run "chkdsk C: /f" to check the system disk for errors and fix them, then reboot.
2. If the error continues and System Restore is enabled, copy the system hive from the last restore point into \WINDOWS\SYSTEM32\CONFIG
3. If the error continues, copy the system hive from \WINDOWS\REPAIR into \WINDOWS\SYSTEM32\CONFIG
4. If the error continues, perform a repair installation by booting from the Windows installation media


--

Symptoms:
"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."


Cause:
Boot volume (with Windows folder) is not accessible as defined in BOOT.INI

Resolution:
Check the boot volume is accessible

--

Symptoms:
Dual-boot 32-bit Windows and 64-bit Windows system reports "NTOSKRNL.EXE is corrupt" trying to boot into 64-bit Windows

Cause:
System volume contains an older boot loader than the boot volume requires - e.g. XP SP2 installed after XP x64

Resolution:
Copy NTDETECT.COM and NTLDR from XP x64 installation media to the root of the system volume

on May 03, 2010 | PC Desktops

1 Answer

C:\minint\system32\restore.log mising


Restore points are located in C:/Windows/system32/restore.
You have an unusual error message which talks about C:/minint folder. Seems like this is a virus issue. It would be better if you run virus scan for your computer.
Also run a system utility software RegInOut to refresh your PC.

Dec 13, 2011 | PC Desktops

1 Answer

Windows problem?


just reinstall your Oeratuing System

Dec 09, 2008 | Sony VAIO RB30C (VGCRB30) PC Desktop

1 Answer

My computer won't load. It's asking me to insert the windows vista installation disc. Under that, it says: "File:\windows\system32\winload.exe status:0xc000000f" please help me!


You may need to change the boot order in your bios so it starts the CD drive first. You will need to use your manual to do this because there are different bios's. When Vista boots hit repair and it should repair it. Are you, or, were you dual booting your computer with Linux or XP? This can sometimes cause that error.

Nov 29, 2008 | PC Desktops

1 Answer

Error: windows root>\system32\ntoskrnl.exe


Issue: NTOSKRNL.EXE is missing or corrupt.
Related errors:
Below is a listing of the full error message that may be related to this error.
Windows NT could not start because the below file is missing or corrupt:
C:\Winnt\System32\Ntoskrnl.exe
Cause:
  1. Keyboard issue
  2. Miscellaneous corruption
  3. Corrupt boot.ini file.
  4. Missing boot.ini file.
  5. Missing or corrupt ntoskrnl.exe file.
  6. Windows NT installed on a partition bigger then 7.8GB
  7. Corrupted hard disk drive or severely corrupted Windows.
Solution: Keyboard issue This issue has also been known to be caused by a short in the ground wire in the keyboard cable. Make sure this is not the cause of your error by replacing the keyboard with a different keyboard or simply just disconnecting the keyboard from the computer.
Miscellaneous corruption Before trying any of the below recommendations it's recommend that you attempt to load the last known good configuration. Additional information about doing this can be found on document CH000626.
Corrupt boot.ini file This issue is often caused when the boot.ini is missing or improperly configured. This issue often arises after a user has recently added or removed an operating system on the computer or added or removed hard disk drives in the computer. Make sure the line pointing to the operating system and it's drive and partition is properly configured in the [boot loader] and [operating systems] section. Additional information about boot.ini can be found on document CH000492.
Missing boot.ini file Microsoft Windows XP users: If the boot.ini is severely corrupted or missing a user running Microsoft Windows XP can rebuild the boot.ini to resolve this issue. Additional information about rebuilding the boot.ini can be found on document CH000648. Microsoft Windows NT and Windows 2000 users: To restore the original boot.ini file in Microsoft Windows NT or Windows 2000 you will need an ERD and follow the below steps. If you do not have an ERD you will be unable to follow these steps.
  1. Boot the computer with your Windows NT three setup diskettes or the Windows 2000 setup disc.
  2. In the setup menu, type R to start the repair.
  3. When prompted for the ERD diskette insert the diskette and inspect the startup environment.
Missing or corrupt ntoskrnl.exe file If the ntoskrnl.exe file is corrupt or missing this can also generate the error. To restore this file follow the below steps.
  1. Insert the Microsoft Windows XP CD. Note: If you have a recovery CD or a restore CD and not a Microsoft Windows XP CD it is likely the below steps will not resolve your issue.
  2. Reboot the computer, as the computer is starting you should see a message to press any key to boot from the CD. When you see this message press any key.
  3. In the Microsoft Windows XP setup menu press the R key to enter the recovery console.
  4. Select the operating system you wish to fix, and then enter the administrator password.
  5. Type expand d:\i386\ntoskrnl.ex_ c:\windows\system32
  6. You will then be prompted if you wish to overwrite the file type Y and press enter to overwrite the file.
  7. Type exit to reboot the computer.
Windows NT installed on a partition bigger then 7.8GB If you are running Microsoft windows NT 4.0 on a partition larger than 7.8GB this issue can occur if the boot files are located outside this limitation. When this error occurs your computer will have the error message as shown below. OS Loader v4.01
Disk I/O error status=00000001
Windows NT could not start because the below file is missing or corrupt: winnt\system32\Ntoskrnl.exe
Please reinstall a copy of the above file. If your system partition is larger than 7.8GB you will need to delete the partition and recreate the partition to 7.8GB or less. Additional information about this issue can be found on Microsoft KB Q224526.
Corrupted hard disk drive or severely corrupted Windows Attempt to check the hard disk drive for any errors by running the chkdsk error. To do this follow the below steps.
  1. Insert the Microsoft Windows XP CD. Note: If you have a recovery CD or a restore CD and not a Microsoft Windows XP CD it is likely the below steps will not resolve your issue.
  2. Reboot the computer, as the computer is starting you should see a message to press any key to boot from the CD. When you see this message press any key.
  3. In the Microsoft Windows XP setup menu press the R key to enter the recovery console.
  4. Select the operating system you wish to fix, and then enter the administrator password.
  5. Once at the recovery console type chkdsk /r
  6. Once completed type exit and see if issue is resolved.
If after trying all of the above steps you are still encountering the same issue it's likely that Windows is severely corrupted and it is recommended you attempt to reinstall Windows. Additional information about erasing the computer and starting over can be found on document CH000186. Finally, if during the Windows installation you encounter errors it's likely that your hard disk drive is bad.

Oct 18, 2008 | PC Desktops

2 Answers

How do I...


NTOSKRNL.EXE is missing or corrupt.

Related errors:

Below is a listing of the full error message that may be related to this error.

Windows NT could not start because the below file is missing or corrupt:
C:\Winnt\System32\Ntoskrnl.exe

Cause:
Keyboard issue
Miscellaneous corruption
Corrupt boot.ini file.
Missing boot.ini file.
Missing or corrupt ntoskrnl.exe file.
Windows NT installed on a partition bigger then 7.8GB
Corrupted hard disk drive or severely corrupted Windows.
Solution:
Keyboard issue
This issue has also been known to be caused by a short in the ground wire in the keyboard cable. Make sure this is not the cause of your error by replacing the keyboard with a different keyboard or simply just disconnecting the keyboard from the computer.

Miscellaneous corruption
Before trying any of the below recommendations it's recommend that you attempt to load the last known good configuration. Additional information about doing this can be found on document CH000626.

Corrupt boot.ini file
This issue is often caused when the boot.ini is missing or improperly configured. This issue often arises after a user has recently added or removed an operating system on the computer or added or removed hard disk drives in the computer.
Make sure the line pointing to the operating system and it's drive and partition is properly configured in the [boot loader] and [operating systems] section. Additional information about boot.ini can be found on document CH000492.

Missing boot.ini file
Microsoft Windows XP users:
If the boot.ini is severely corrupted or missing a user running Microsoft Windows XP can rebuild the boot.ini to resolve this issue. Additional information about rebuilding the boot.ini can be found on document CH000648.

Microsoft Windows NT and Windows 2000 users:

To restore the original boot.ini file in Microsoft Windows NT or Windows 2000 you will need an ERD and follow the below steps. If you do not have an ERD you will be unable to follow these steps.
Boot the computer with your Windows NT three setup diskettes or the Windows 2000 setup disc.
In the setup menu, type R to start the repair.
When prompted for the ERD diskette insert the diskette and inspect the startup environment.
Missing or corrupt ntoskrnl.exe file
If the ntoskrnl.exe file is corrupt or missing this can also generate the error. To restore this file follow the below steps.
Insert the Microsoft Windows XP CD. Note: If you have a recovery CD or a restore CD and not a Microsoft Windows XP CD it is likely the below steps will not resolve your issue.
Reboot the computer, as the computer is starting you should see a message to press any key to boot from the CD. When you see this message press any key.
In the Microsoft Windows XP setup menu press the R key to enter the recovery console.
Select the operating system you wish to fix, and then enter the administrator password.
Type expand d:\i386\ntoskrnl.ex_ c:\windows\system32
You will then be prompted if you wish to overwrite the file type Y and press enter to overwrite the file.
Type exit to reboot the computer.
Windows NT installed on a partition bigger then 7.8GB
If you are running Microsoft windows NT 4.0 on a partition larger than 7.8GB this issue can occur if the boot files are located outside this limitation. When this error occurs your computer will have the

error message as shown below.

OS Loader v4.01
Disk I/O error status=00000001
Windows NT could not start because the below file is missing or corrupt: winnt\system32\Ntoskrnl.exe
Please reinstall a copy of the above file.

If your system partition is larger than 7.8GB you will need to delete the partition and recreate the partition to 7.8GB or less. Additional information about this issue can be found on Microsoft KB Q224526.

Corrupted hard disk drive or severely corrupted Windows
Attempt to check the hard disk drive for any errors by running the chkdsk error. To do this follow the below steps.

Insert the Microsoft Windows XP CD. Note: If you have a recovery CD or a restore CD and not a Microsoft Windows XP CD it is likely the below steps will not resolve your issue.
Reboot the computer, as the computer is starting you should see a message to press any key to boot from the CD. When you see this message press any key.
In the Microsoft Windows XP setup menu press the R key to enter the recovery console.
Select the operating system you wish to fix, and then enter the administrator password.
Once at the recovery console type chkdsk /r
Once completed type exit and see if issue is resolved.
If after trying all of the above steps you are still encountering the same issue it's likely that Windows is severely corrupted and it is recommended you attempt to reinstall Windows. Additional information about erasing the computer and starting over can be found on document CH000186.
Finally, if during the Windows installation you encounter errors it's likely that your hard disk drive is bad.

Oct 09, 2008 | Dell OptiPlex GX110 PC Desktop

3 Answers

Configuration error code purple


1. Load the system recovery disk into CD-ROM
2. Press F10 repeatedly at boot screen to load the Recovery Menu
3. Press R for the recover console
4. Select "Advanced Options"
5. Press Alt + D to bring up the command prompt
6. type "cd h:\" to enter the root directory
7. type "dir /w" to view the directory in wide view
8. open the master.log file (or something along those lines), this should bring up a prompt asking you what program to open it with, you should only be able to select notepad.
9. open the file with notepad and when it appears select the File>Open
10. in the file name box type in "C:\hp\bin\configcheck\run.py"
11. once the file opens clear the contents and select save as then save the file as run.p_
12. close the notepad program
13. delete the original file by typing "del C:\hp\bin\configcheck\run.py"
14. reboot system

After a reboot the windows screen might flash a few times and take a little longer to load, be patient and you should be able to continue with the windows set-up without that damned code purple error message.

Oct 02, 2008 | PC Desktops

1 Answer

ACER DESKTOP COMPUTER


Issue: NTOSKRNL.EXE is missing or corrupt.
Related errors:
Below is a listing of the full error message that may be related to this error.
Windows NT could not start because the below file is missing or corrupt:
C:\Winnt\System32\Ntoskrnl.exe
Cause:
  1. Keyboard issue
  2. Miscellaneous corruption
  3. Corrupt boot.ini file.
  4. Missing boot.ini file.
  5. Missing or corrupt ntoskrnl.exe file.
  6. Windows NT installed on a partition bigger then 7.8GB
  7. Corrupted hard disk drive or severely corrupted Windows.
Solution: Keyboard issue This issue has also been known to be caused by a short in the ground wire in the keyboard cable. Make sure this is not the cause of your error by replacing the keyboard with a different keyboard or simply just disconnecting the keyboard from the computer.
Miscellaneous corruption Before trying any of the below recommendations it's recommend that you attempt to load the last known good configuration. Additional information about doing this can be found on document CH000626.
Corrupt boot.ini file This issue is often caused when the boot.ini is missing or improperly configured. This issue often arises after a user has recently added or removed an operating system on the computer or added or removed hard disk drives in the computer. Make sure the line pointing to the operating system and it's drive and partition is properly configured in the [boot loader] and [operating systems] section. Additional information about boot.ini can be found on document CH000492.
Missing boot.ini file Microsoft Windows XP users: If the boot.ini is severely corrupted or missing a user running Microsoft Windows XP can rebuild the boot.ini to resolve this issue. Additional information about rebuilding the boot.ini can be found on document CH000648. Microsoft Windows NT and Windows 2000 users: To restore the original boot.ini file in Microsoft Windows NT or Windows 2000 you will need an ERD and follow the below steps. If you do not have an ERD you will be unable to follow these steps.
  1. Boot the computer with your Windows NT three setup diskettes or the Windows 2000 setup disc.
  2. In the setup menu, type R to start the repair.
  3. When prompted for the ERD diskette insert the diskette and inspect the startup environment.
Missing or corrupt ntoskrnl.exe file If the ntoskrnl.exe file is corrupt or missing this can also generate the error. To restore this file follow the below steps.
  1. Insert the Microsoft Windows XP CD. Note: If you have a recovery CD or a restore CD and not a Microsoft Windows XP CD it is likely the below steps will not resolve your issue.
  2. Reboot the computer, as the computer is starting you should see a message to press any key to boot from the CD. When you see this message press any key.
  3. In the Microsoft Windows XP setup menu press the R key to enter the recovery console.
  4. Select the operating system you wish to fix, and then enter the administrator password.
  5. Type expand d:\i386\ntoskrnl.ex_ c:\windows\system32
  6. You will then be prompted if you wish to overwrite the file type Y and press enter to overwrite the file.
  7. Type exit to reboot the computer.
Windows NT installed on a partition bigger then 7.8GB If you are running Microsoft windows NT 4.0 on a partition larger than 7.8GB this issue can occur if the boot files are located outside this limitation. When this error occurs your computer will have the error message as shown below. OS Loader v4.01
Disk I/O error status=00000001
Windows NT could not start because the below file is missing or corrupt: winnt\system32\Ntoskrnl.exe
Please reinstall a copy of the above file. If your system partition is larger than 7.8GB you will need to delete the partition and recreate the partition to 7.8GB or less. Additional information about this issue can be found on Microsoft KB Q224526.
Corrupted hard disk drive or severely corrupted Windows Attempt to check the hard disk drive for any errors by running the chkdsk error. To do this follow the below steps.
  1. Insert the Microsoft Windows XP CD. Note: If you have a recovery CD or a restore CD and not a Microsoft Windows XP CD it is likely the below steps will not resolve your issue.
  2. Reboot the computer, as the computer is starting you should see a message to press any key to boot from the CD. When you see this message press any key.
  3. In the Microsoft Windows XP setup menu press the R key to enter the recovery console.
  4. Select the operating system you wish to fix, and then enter the administrator password.
  5. Once at the recovery console type chkdsk /r
  6. Once completed type exit and see if issue is resolved.
If after trying all of the above steps you are still encountering the same issue it's likely that Windows is severely corrupted and it is recommended you attempt to reinstall Windows. Additional information about erasing the computer and starting over can be found on document CH000186. Finally, if during the Windows installation you encounter errors it's likely that your hard disk drive is bad.

best regards wish u give me a good rate ^^

Aug 15, 2008 | Acer PC Desktops

Not finding what you are looking for?
PC Desktops Logo

Related Topics:

116 people viewed this question

Ask a Question

Usually answered in minutes!

Top HP PC Desktops Experts

Fred Sops

Level 2 Expert

271 Answers

john smith

Level 2 Expert

366 Answers

Gavindu Dileepa

Level 1 Expert

10 Answers

Are you a HP PC Desktop Expert? Answer questions, earn points and help others

Answer questions

Manuals & User Guides

Loading...